Configuration process in nrf_mesh APP

Question

Hi, I'm provisioning mesh nodes using nrf_mesh APP. After I finished it and added device into mesh network, I have some questions in configuration process. 
 In nrf_mesh APP we can see the procedure while provisioning,and it shows these data app send and reveive also we can find it in GATT provisioning and Proxy file.But I dno't know how the node received data then it need to add/bind app key ,set pulication/subscribtion address to itself.I can't find the function calls to it.Could you please tell me where to realize it? 
 The another qestion is that when I config node it can reinitialize and reconnect to APP ,they send much data and I don't understand them because I can find it have any connection about appkey and pulication/subscribtion address . 
 Any help will be thanked advanced. 
 Best Regards! 
 ZhengRui.

Roshan Rajaratnam · Answer

Hi zhengrui , If you are using nRF Mesh Library for Android you don't have to worry about sending/receiving block acknowledgements. This is something that is handled by the library. Usually block acknowledgements are sent/received when sending/receiving segmented mesh messages. This will confirm that certain messages are sent/received and based on this some messages are retransmitted ensuring all messages are sent/received. Whatever you see in the UI here is just displayed as information for the user based on what messages are sent and received. There are callbacks for sending/receiving block acknowledgements and based on this the UI is updated accordingly. 
 Just as a note nRF Mesh app autmates a few configuration steps right after the provisioning completes, so that it becomes a little bit easier for the user to not go through all the configuration steps. Based on the diagram you have attached the composition data get, app key add messages are sent right after the provisioning is completed as I mentioned above. They are all segmented messages and are sent in multiple segments. The library will respond automatically to the node with block acknowledgements to ensure each segment is received and you don't have to handle block acknowledgments yourself. 
 Hope this clarifies