LISA-C2 series and FW75-C200 - System Integration Manual
UBX-13000620 - R21
Early Production Information
Features description
Page 77 of 103
Applications should not attempt to re-establish the connection until the OMA-DM session has completed. The
+UOMASTAT URC should be monitored to determine if an OMA-DM session is in progress.
Device management sessions can also be Client Initiated (CI). In general, the initiation of such sessions are
triggered by the Host Application, but they can also be triggered by events external to the OMA-DM Client, for
example:
•
Asynchronous actions (e.g. reporting status of some action on device)
•
After a firmware update
•
Extensible exec operations (per-device)
•
After a PRL upgrade
•
Device initiated sessions
•
Diagnostic events
•
Business logic driven (DSS, etc.)
•
Periodic (monthly, quarterly, etc.)
Applications should not attempt to establish a connection until the OMA-DM session has completed. The
+UOMASTAT URC should be monitored to determine if an OMA-DM session is in progress. Client initiated
attempts will fail if an OMA-DM session is already in progress.
3.5.2.8
Best practices
Host applications should not initiate data calls or power down / cycle the module while an OMA-DM session is
active. Specifically:
•
Applications should monitor the +UOMASTAT URC to determine if an OMA-DM session is in progress.
•
Applications should wait a minimum 15 seconds after power-on before initiating a data call as asynchronous
operations may be triggered by the OMA-DM Client (e.g. processing a queued NIA or performing HFA).
•
Applications should wait approximately 30 seconds after the completion of an OMA-DM session (e.g.
+UOMASTAT:1,1,0 or +UOMASTAT:2,1,0) before initiating a data call as additional asynchronous operations
may be triggered by the OMA-DM Client.
In an event that the module is in factory default state and no +UOMASTAT URC is received after 60
seconds of the module’s power up, then it is recommended to execute the AT+UOMADMCLEAN=0
command.
The module is considered in factory default state if:
•
AT$MDN? Returns : 000000XXXX
•
AT$MSID? Returns : 000000XXXX
•
AT$QCMIPGETP=1 : Returns : [email protected]
The flow diagram in Figure 42 describes how to use the AT+UOMADMCLEAN=0 command.
