FAQ of NB-IoT-registration related questions
1.The terminal can’t establish a connection with OneNET.
2.SDK initialization module fails.
3.The device can’t be connected to the platform and returns to 4.03.
4.Use of the automatic subscription and manual subscription of the platform (device level)）
5.How the device judges the subscription succeeds?
6.Use of automatic discovery and manual discovery of the platform
7.Under which occasions, the platform will delete the subscription?
| Module related questions |
1.The terminal can’t establish a connection with OneNET?
Answer: Please first of all confirm whether the terminal is normally attahced to NB network. If network attachment is normal, please check if the terminal connection message and authorization code are normal. If both of them can work normally, plesae call 4001-100-866-3 to consult the platform technologist.
2.SDK initialization module fails？
Answer: When SKD is started, it will first of all configure the working mode of the current module to make it attach to NB network through a series of AT instructions. One other thing to note is that the module needs certain time to process each AT instruction, so it’s suggested that a couple of seconds shall be delayed between AT instructions; otherwise, the initialization process will fail.
| Authentication failure |
3.The device can’t be connected to the platform and returns to 4.03?
Answer: 4.03 Forb dden means the failure of authorization of access machine; the device authorization rules on the access machine side are as follows: * If the device fails to set Authcode, it will authorize according to ep, and incorrect ep will cause the failure of authorization * If the device sets Authodcode, it will authorize through ep+ Authcode, and incorrect ep and Authcode or lack of Authcode parameters will all cause the failure of authorization; * Users on the IP blacklist of the platform will also have authorization failure. > Remark: Endpoint-Name (format: imei; imsi), ep for short in the above| Observer and discover |
4.Use of the automatic subscription and manual subscription of the platform？ (device level)
Answer: The use of automatic subscription and manual subscription is as follows:
- Automatic subscription: When the device is online, the platform will actively send the subscription command to the device.
- Manual subscription: After the device is online, the subscription command needs to be released manually, and the command is valid within one cycle of online operation; subscription is required again if the device is online next time.
Remark: The device can report data only after subscription.
5.How the device judges the subscription succeeds?
Answer: The platform will send read 3/0 operation after all subscription operations are finished; if the device receives READ command, it means all subscription operations are successful.
6.Use of automatic discovery and manual discovery of the platform？
Answer: The specific resource list can be checked through resource discovery. Because the terminal resource list is not likely to change, for the sake of low-power dissipation, the platform will cancel the automatic discovery function by default for newly created product, so that it’s unnecessary to relesae Discover command in each registration. If the user wants to see the real-time resource list on the platform, the user can release the Discover command manually.
Remark: Start/close of automatic discovery can be set at the product level; manual release of Discover command is for a specific Instance of the corresponding Object.
7.Under which occasions, the platform will delete the subscription?
Answer: It will be deleted during registration and in offline state.
If the resource is deleted in Update message, the platform will also remove subscription and delete Instance. If the user subscribes a certain Resource through the platform, the device will separately delete the corresponding Resource during registration and in the offline state.