Thing discovery and configuration for an internet of things integrated developer environment
US-2016357524-A1 · Dec 8, 2016 · US
US10958726B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10958726-B2 |
| Application number | US-201715858646-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 29, 2017 |
| Priority date | Nov 16, 2017 |
| Publication date | Mar 23, 2021 |
| Grant date | Mar 23, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure provides a device list synchronizing method and apparatus, a device and a computer storage medium, wherein the method comprises: after obtaining a user instruction instructing to discover devices, a smart network system sending, to a developer system, a DeviceDiscoveryRequest including first authorization information; the developer system storing the first authorization information; after obtaining information of update of a device list on a developer side, carrying the first authorization information to invoke an interface of the smart network system to trigger the smart network system to send the DeviceDiscoveryRequest to the developer system. In the manners provided by the present disclosure, it is possible to implement automatic synchronization of the cloud user data of the smart network system after the device list on the developer side is subsequently updated, in a way that the user only needs to initiatively trigger discovering devices once, needless to initiatively trigger discovering devices each time.
Opening claim text (preview).
What is claimed is: 1. A device list synchronizing method, wherein the method comprises: receiving a DeviceDiscoveryRequest including first authorization information and second authorization information by a developer system, the DeviceDiscoveryRequest including the first authorization information and the second authorization information being sent by a smart network system to the developer system after obtaining a user instruction instructing to discover devices, wherein the first authorization information is provided by the smart network system and the second authorization information is provided by the developer system; storing a correspondence relationship of the first authorization information and the second authorization information by the developer system; and in response to obtaining information of update of a device list on a developer side corresponding to the second authorization information, carrying, by the developer system according to the correspondence relationship, the first authorization information to invoke an interface of the smart network system to trigger the smart network system to send the DeviceDiscoveryRequest to the developer system. 2. The method according to claim 1 , comprising: after receiving the DeviceDiscoveryRequest, the developer system obtaining the device list on the developer side corresponding to the second authorization information, and returning the device list on the developer side to the smart network system. 3. The method according to claim 1 , wherein the first authorization information comprises user identification information or encrypted user identifier information. 4. A device list synchronizing method, wherein the method comprises: after obtaining, by a smart network system, a user instruction instructing to discover devices, the smart network system sending, to a developer system, a DeviceDiscoveryRequest including first authorization information and second authorization information so that the developer system stores a correspondence relationship of the first authorization information and the second authorization information, wherein the first authorization information is provided by the smart network system and the second authorization information is provided by the developer system; and in response to receiving, by the smart network system, an invocation including the first authorization information and sent by the developer system in response to obtaining information about a device list on a developer side corresponding to the second authorization information is updated and according to the correspondence relationship, sending the DeviceDiscoveryRequest to the developer system. 5. The method according to claim 4 , wherein the method further comprises: after the smart network system receives the device list on the developer side from the developer system, using the device list on the developer side to update cloud user data of the smart network system. 6. The method according to claim 5 , wherein the method further comprises: returning a message about success or failure of update to user equipment sending the user instruction, according to an update result of the cloud user data of the smart network system. 7. The method according to claim 4 , wherein the first authorization information comprises user identification information or encrypted user identifier information. 8. A device for synchronizing a device list for a developer system, comprising one or more processors; a memory; one or more programs stored in the memory and configured to execute the following operation when executed by the one or more processors: receiving a DeviceDiscoveryRequest including first authorization information and second authorization information, the DeviceDiscoveryRequest including the first authorization information and the second authorization information being sent by a smart network system to the developer system after obtaining a user instruction instructing to discover devices, wherein the first authorization information is provided by the smart network system and the second authorization information is provided by the developer system; storing a correspondence relationship of the first authorization information and the second authorization information; and in response to obtaining information of update of a device list on a developer side corresponding to the second authorization information, carrying the first authorization information according to the correspondence relationship to invoke an interface of the smart network system to trigger the smart network system to send the DeviceDiscoveryRequest to the developer system. 9. A non-transitory computer storage medium in which one or more programs are stored, when said one or more programs are executed by a developer system, the developer system being enabled to execute the following operations: receiving a DeviceDiscoveryRequest including first authorization information and second authorization information, the DeviceDiscoveryRequest including the first authorization information and the second authorization information being sent by a smart network system to the developer system after obtaining a user instruction instructing to discover devices, wherein the first authorization information is provided by the smart network system and the second authorization information is provided by the developer system; storing a correspondence relationship of the first authorization information and the second authorization information; and in response to obtaining information of update of a device list on a developer side corresponding to the second authorization information, carrying the first authorization information according to the correspondence relationship to invoke an interface of the smart network system to trigger the smart network system to send the DeviceDiscoveryRequest to the developer system. 10. The device according to claim 8 , wherein the operation further comprises: after receiving the DeviceDiscoveryRequest, obtaining the device list on the developer side corresponding to the second authorization information, and returning the device list on the developer side to the smart network system. 11. The device according to claim 8 , wherein the first authorization information comprises user identification information or encrypted user identifier information. 12. A device for synchronizing a device list for a smart network system, comprising one or more processors; a memory; one or more programs stored in the memory and configured to execute the following operation when executed by the one or more processors: after obtaining a user instruction instructing to discover devices, sending, to a developer system, a DeviceDiscoveryRequest including first authorization information and second authorization information so that the developer system stores a correspondence relationship of the first authorization information and the second authorization information, wherein the first authorization information is provided by the smart network system and the second authorization information is provided by the developer system; in response to receiving an invocation including the first authorization information and sent by the developer system in response to obtaining information about a device list on a developer side corresponding to the second authorization information is updated and according to the correspondence relationship, sending the DeviceDiscoveryRequest to the developer system. 13. The device according to claim 12 , wherein the operation further comprises: after the smart network system receives the device list on the developer side from the d
Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration · CPC title
Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title
Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title
for controlling access to devices or network resources · CPC title
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.