Remote Upgrade OTA
Product Introduction
Product Charge
User guideline
Device development
Upgrade Task Push
API authentication
API List
1- Report Version
2- Detect Device Upgrade Task
3- Detect if token is valid
4- Download Resources
5- Report upgrade status
Other API
Instructions for use of OTA - SDK
Best practice
Common problems
Update log
Frequently asked questions about OTA-others
1. Ip and ports for access at OTA device side？
2. Why report state return is failed? Is there no permission?
3. Will the task detection update the version number recorded for the device on the platform?
5. What is the OTA charging standard?
1.Ip and ports for access at OTA device side？
A: 183.230.40.50: 80, the ip and port are connected via tcp of device side, and then data are posted and gotten in http way.2.Why report state return is failed? Is there no permission?
A: The process for token verification shall not be ignored. Otherwise, the status report will fail. Status report cannot be completed by upgrade report directly (201). It needs to report download firmware first (101).3. Will the task detection update the version number recorded for the device on the platform?
A: The version number carried when checking the task will be used to update the version number of the device recorded on the platform.4. If firmware information (md5), len and other information is not saved in case of power outage during firmware upgrading, is the information must be saved?
A: (1) The information can be saved into device storage chip when the firmware information is acquired for the first time.(2) Alternatively, task details may be gotten after power outage of the device at http:///ota/south/tasking.