Help Center> IoT Device Access> FAQs> Device Integration> Why Was a 513 Message Reported During the Connection of an NB-IoT Device?
Why Was a 513 Message Reported During the Connection of an NB-IoT Device?
After being powered on, devices initiate a TUP registration flow to the IoT platform. TUP is a Huawei proprietary protocol over CoAP. It is similar to LWM2M. HiSilicon chipsets require that the TUP registration not take more than 4s.
When a 513 message is reported, do as follows:
- If a 513 message is reported due to poor network performance, contact the NB-IoT network carrier to check the network status.
- You are advised to restart the device and run AT+NMGS. When you send service data by running AT+NMGS, registration is triggered. If the subscription to the t/d resources (resources for receiving and sending service data) is not received within 4 seconds, an error is returned, but the registration is continued based on the CoAP-layer retransmission. Only when the subscription to the t/d resources is not received within 160 seconds, will the registration fail. However, 160 seconds are basically sufficient for device registration to complete. Even if an error message is returned after 4 seconds, only the data of the first packet is discarded and the registration will not be affected.
You can run AT+NMSTATUS? to query registration status. If +NMSTATUS:MO_DATA_ENABLED is returned, the registration is successful.
Parent topic: Device Integration
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.