> 2.6 | Monitoring

> There are two approaches to set up an application for permanent monitoring:

> • | One approach is polling, where the application keeps sending the same AT command at regular intervals. Throughout this document this method is referred to as cyclic monitoring. Typical examples are provided in Section 2.6.2. Polling is easy to implement, but may have disadvantages: The application consumes power when polling (the faster the polling rate the higher is the overall power consumption of the application). Checks are done when nothing happens. The information is not up to date, particularly, if refreshed at the beginning of a long polling cycle.

> • | The other way is an event-driven or alert-driven notification based on Unsolicited Result Codes (URCs) and referred to as event monitoring. In this case, the ME will send a message to the application whenever a status change occurs. The advantage over polling is significantly lower power consumption. Therefore, if possible, priority should be given to event monitoring. Typical examples are provided in Section 2.6.3.

> Figure 26: Monitoring