Managing machine to machine devices

US10412052B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10412052-B2
Application numberUS-201415021888-A
CountryUS
Kind codeB2
Filing dateSep 12, 2014
Priority dateSep 13, 2013
Publication dateSep 10, 2019
Grant dateSep 10, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

System and method for managing devices comprising a memory store having memory locations, wherein each memory location stores one or more attributes associated with one or more devices. Device manager arranged to execute commands to take an action on the one or more attributes stored in the memory locations, and to receive from the one or more devices values of the corresponding one or more attributes. Synchronizer configured to maintain synchronization between the attributes stored in the memory store and the attributes associated with the devices.

First claim

Opening claim text (preview).

The invention claimed is: 1. A system for managing one or more device(s) and for analyzing attributes of those one or more device(s) to indirectly infer a usage of a resource, the system comprising: a memory store having memory locations, wherein each memory location stores one or more attribute(s) associated with the one or more device(s); a device manager arranged to execute commands to take an action on the one or more attribute(s) stored in the memory locations and to receive from the one or more device(s) values corresponding to the one or more attribute(s) such that the one or more device(s) also monitor corresponding one or more attribute(s) that correspond to the one or more attribute(s) stored in the memory locations, wherein the commands executed by the device manager include a first set-based command; and a synchroniser configured to maintain synchronisation between the one or more attribute(s) stored in the memory store and the corresponding one or more attribute(s) of the one or more device(s), wherein the one or more device(s) share an indirect relationship with the resource, the indirect relationship being established as a result of the resource not being directly measured by the one or more device(s) and as a result of the corresponding one or more attribute(s) of the one or more device(s) being only indirectly associated with the resource, and wherein the system is configured to: perform an analysis on the one or more attribute(s) stored in the memory store to generate an output indicating the inferred usage of the resource such that the inferred usage is calculated based on the one or more attribute(s) stored in the memory store as opposed to being measured directly. 2. The system of claim 1 , wherein the commands are defined as declarative commands. 3. The system of claim 1 , wherein the executed commands are set-based operations. 4. The system of claim 3 , wherein the set-based operations comprise any one or more of: SQL, procedural, data manipulation, configuration management, insert, select, update, create, read, write, erase, and search. 5. The system of claim 1 further comprising one or more interface(s) for communicating with each device of the one or more device(s). 6. The system of claim 5 , wherein the device manager is further configured to communicate with each device over a first interface or the one or more interface(s). 7. The system of claim 5 , wherein the synchroniser is further configured to operate when communication with the one or more device(s) over the one or more interface(s) is available. 8. The system of claim 5 , wherein the synchroniser is further configured to initiate a communication with the one or more device(s) when no communication with the one or more device(s) over the one or more interface is available. 9. The system according to claim 1 , wherein the synchroniser is further configured to operate at intervals. 10. The system according to claim 1 , wherein the synchroniser maintains synchronisation between the one or more attribute(s) stored in the memory locations and the corresponding one or more attribute(s) of the one or more device(s) by controlling the corresponding one or more attribute(s) of the one or more device(s). 11. A method for managing one or more device(s) and for analyzing attributes of those one or more device(s) to indirectly infer a usage of a resource, the method comprising: storing, in a memory store, one or more attribute(s) associated with the one or more device(s); taking an action on the one or more attribute(s) stored in the memory store, the action includes a first set-based command; receiving, from the one or more device(s), values for the one or more attribute(s) stored in the memory locations such that the one or more device(s) also monitor corresponding one or more attribute(s) that correspond to the one or more attribute(s) stored in the memory locations; and maintaining synchronisation between the one or more attribute(s) stored in the memory store and the corresponding one or more attribute(s) of the one or more device(s), wherein the one or more device(s) share an indirect relationship with the resource, the indirect relationship being established as a result of the resource not being directly measured by the one or more device(s) and as a result of the corresponding one or more attribute(s) of the one or more device(s) being only indirectly associated with the resource, and performing an analysis on the one or more attribute(s) stored in the memory store to generate an output indicating the inferred usage of the resource such that the inferred usage is calculated based on the one or more attribute(s) stored in the memory store as opposed to being measured directly. 12. The method of claim 11 , further comprising: receiving a command to change an attribute of the one or more device(s), wherein the command is received in a first form conforming to a data structure of the one or more attribute(s) stored in the memory locations, wherein maintaining the synchronisation further comprises converting the received command into a form conforming to a data structure of the one or more device(s). 13. The method of claim 12 , wherein the command is received over a first interface and wherein the converted command is communicated to the one or more device(s) over a second interface. 14. The method of claim 11 further comprising receiving a command defining a sequence of steps for changing the corresponding one or more attribute(s) of the one or more device(s), wherein taking the action on the one or more attribute(s) stored in the memory locations is performed according to the sequence of steps. 15. The method of claim 14 further comprising updating firmware or other executable code component of the one or more device(s) after the corresponding one or more attribute(s) of the one or more device(s) are synchronised according to the sequence of steps. 16. The method of claim 14 , wherein different commands defining different sequences of steps are received for different device types. 17. The method of claim 14 , wherein devices are updated to different versions of firmware or another executable code component dependent on the stored one or more attribute(s) stored in the memory locations. 18. The method of claim 17 , further comprising receiving data models for each version of the firmware or other executable code component and then using the data models to define how to transition between versions. 19. The method of claim 11 , wherein the one or more attribute(s) stored in the memory locations are stored in a single data structure for different device types. 20. The method of claim 19 , wherein maintaining synchronisation between the one or more attribute(s) stored in the memory locations and the corresponding one or more attribute(s) of the one or more device(s) further comprises converting the corresponding one or more attribute(s) of the one or more device(s) before updating the one or more device(s). 21. The method of claim 11 , wherein the method further includes: when a particular device included among the one or more device(s) is in a dormant state, transmitting a wake-up message to the particular device to cause the particular device to transition out of the dormant state, wherein, in addition to a command used to wake-up the particular device, the wake-up message also includes one or more secure parameter(s) that cause the particular device to switch from using a first network connection to using a second

Assignees

Inventors

Classifications

  • wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30) · CPC title

  • for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819) · CPC title

  • based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title

  • Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title

  • by securing the transmission between two devices or processes · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10412052B2 cover?
System and method for managing devices comprising a memory store having memory locations, wherein each memory location stores one or more attributes associated with one or more devices. Device manager arranged to execute commands to take an action on the one or more attributes stored in the memory locations, and to receive from the one or more devices values of the corresponding one or more att…
Who is the assignee on this patent?
Vodafone Ip Licensing Ltd
What technology area does this patent fall under?
Primary CPC classification G06F13/1689. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Sep 10 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).