Service Settings

The power-saving configuration and northbound push management are available.

Power-Saving Configuration	Parameter Description
Working Mode	The IoT platform supports three working modes for NB-IoT devices: PSM, DRX, and eDRX. The timeout interval for command delivery varies by working mode. If the IoT platform does not receive a command execution result during the timeout period, the task state changes to timeout. PSM: The default timeout interval is 300 seconds. A device does not receive downstream data during the non-service period. It can receive downstream data cached by the IoT platform only after sending upstream data (MO data) to the platform. This mode is suitable for services that have no platform-to-device data delay limit. Devices in this mode have low power consumption and are powered by batteries. An example service is meter reading. DRX: The default timeout interval is 300 seconds. Downstream service data can reach devices at any time. In each DRX cycle (1.28s, 2.56s, 5.12s, or 10.24s), a device detects whether there is a downstream service. This mode is suitable for services that require low delay. Generally, devices in this mode are powered by a wired current. An example service is street lamps. eDRX: The default timeout interval is 2 x eDRX cycle + 120 seconds. In each eDRX cycle, a device can receive downstream data only during the preset paging time window (PTW); otherwise, it remains in the dormant state and does not receive downstream data. This mode balances between service delay and power consumption. An example service is remote gas shut-off. Click Set on the right of the page to set the working mode. NOTE: The IoT platform does not deliver the configuration to the network or device. Before configuration, obtain the working mode and parameters of the device from the carrier.
Downstream Message Direction	When this function is enabled, if the IoT platform has a pending command to deliver to a device using the PSM mode, the platform includes the hasMore field in the response to a data reporting message sent from the device. After detecting this field in the response, the device does not enter the dormant mode immediately.
Northbound Push Management	Parameter Description
Push Service Control	To prevent an NA from occupying excessive resources due to an exception, the IoT platform uses flow control for push services. After confirming that an exception occurs, you can temporarily disable the push service. After the exception is resolved, you can enable it again. Maximum Concurrent Messages per Second: specifies the maximum number of messages pushed by the IoT platform to NAs per second over HTTP. You can change the maximum number based on service requirements. Maximum Connections per Second: specifies the maximum number of connections per second when the IoT platform uses MQTT to push messages to NAs.
Subscription/Push Service (HTTP/HTTPS)	The IoT platform supports query of northbound push configuration and the callback URL list. If the IoT platform fails to push messages to a callback URL 10 consecutive times within 180 seconds, the callback URL is automatically set to invalid. The IoT platform periodically checks whether the callback URL is restored. If so, the platform sets the status of the callback URL to valid.
Subscription/Push Service (MQS)	The IoT platform pushes data reported by devices to the big data platform through the message queue service (MQS) for analysis and processing. The MQS is a third-party component provided by Huawei. Interworking data between the IoT platform and MQS must be configured in advance. iPaaS Address: address of the MQS Namesrv. The format is IP:port, for example, 10.10.11.11:8965. Username: user name for accessing the MQS. Password: password for accessing the MQS. (Obtain iPaaS Address, Username and Password from the MQS administrator.) Encryption: whether messages sent from the IoT platform to the MQS are encrypted. You are advised to select Enable. Topic: topic name, for example, To_Bigdata. Different topics are used to process different message types. Currently, only one topic can be configured, indicating that all information is sent to the same topic for processing. Obtain the value from the MQS administrator.
Subscription/Push Service (MQTT)	The IoT platform uses MQTT to push messages to an NA. You can set the subscribed-to message type on the SP portal. Currently, data reporting is supported.
Subscription/Push Service (ROMA)	The ROMA service is an enterprise business integration platform and is to be launched. NOTE: After the IoT platform is connected with ROMA, you must configure data forwarding rules to forward data to ROMA. For details on how to set a rule, see Rules.