| MCR1 |
If permissible for the IoT Service, any IoT Service Platform which communicates to multiple IoT Devices shall avoid synchronized behaviour and employ a randomized pattern for accessing the IoT Devices within the IoT Service Platform’s domain. |
| MCR2 |
If the (U)SIM subscription associated with an IoT Device is to be placed in a temporarily inactive state (i.e. the subscription is to be disabled for a fixed period of time), the IoT Service Provider shall first ensure that the IoT Device is temporarily disabled to restrict the device from trying to register to the network once the SIM is disabled.Before the (U)SIM subscription associated with an IoT Device is changed to a permanently terminated state, the IoT Service Provider shall ensure that the IoT Device is permanently disabled to stop the device from trying to register to the network once the SIM is permanently disabled.Note: The IoT Service Provider should carefully consider permanently terminating IOT devices which are not easily serviceable as it would require manual intervention (i.e. a service call) to re-enable the IoT Device. |
| MCR3 |
If the IoT Service Platform uses SMS triggers to wake up its IoT Devices, the IoT Service Platform should avoid sending multiple SMS triggers when no response is received within a certain time period. |
| MCR4 |
The IoT Service Platform should be aware of the state of the IoT Device and only send ‘wake up’ triggers when the IoT Device is known to be attached to the mobile network. |