Hello Bernd,
Are you using the the ANT+ library as well or just the ANT library? If you are working with just the ANT library probably the best way to handle a ANT+ master device is similar to the TxCounter example and drive your messages off the Tx event. In that case you will have to handle all the profile bit twiddling yourself for parsing message data. From there is mostly handling edge cases that cause the pattern to deviate (e.g. message requests from the slave device.)
Ah good you did find my WIP. Make sure you are looking at the branch, as I have done a lot more work there and just not merged it yet as I have not fully tested it. Here is the header for the profile class, you can kind of get the idea behind the class.
My plan for the ant+ library is to use the TX event to generate callbacks to user code to populate messages in the transmission sequence and have the profile handle all the transmissions sequence coordinating.
If you want to integrate your profile into antplus I will gladly open a LEV branch and take in pull requests, just be aware you may come across bugs in the base master profile that need to be fixed still. I am just tying up some core router features first (dynamic channels and open rx searching) then I will turn my attention back to profiles.
Hopefully I was able to answer your questions. Let me know if you have any more.
Curtis