SWRU455M February 2017 – October 2020 CC3120 , CC3120MOD , CC3130 , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3230S , CC3230SF , CC3235MODAS , CC3235MODASF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF
The entire provisioning process (adding profiles, confirming profiles, and delivering confirmation results to the user) is executed internally by the networking subsystem. The host application is responsible only for initiating the process. Once the process is started, no further actions are needed.
Figure 17-2 depicts the host application during a provisioning process.
After a provisioning process is started, the host should wait for the networking subsystem to send it the profile confirmation result. During this time, the host application should not perform any networking activity that may interrupt the ongoing provisioning process. The confirmation result is sent after the end-user has configured a profile and the networking subsystem has finished confirming it.
Possible confirmation result values:
If the received confirmation result is successful (that is, a profile was configured, connection was successful, and feedback was delivered to the user), the provisioning process automatically stops, and the host should wait for the provisioning-stopped event before it may continue with its activities. If the profile confirmation failed, the provisioning process continues, to let the user configure another profile. If no profile was configured by the user for some time (inactivity time-out), the provisioning process automatically stops, and a provisioning-stopped event is sent to the host.
Updates regarding the progress of the provisioning process are constantly sent by the networking subsystem to the host.