Enabling IP-communication with a machine to machine unit
US-9369378-B2 · Jun 14, 2016 · US
US10764252B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10764252-B2 |
| Application number | US-201715496860-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 25, 2017 |
| Priority date | Sep 13, 2013 |
| Publication date | Sep 1, 2020 |
| Grant date | Sep 1, 2020 |
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.
A method and system for communicating between a managed device and a device manager is provided by sending the managed device a message over a first communications channel, and then initiating communication between the managed device and the device manager over a second communications channel in response to the message, wherein the first communications channel and the second communications channel are of different types.
Opening claim text (preview).
The invention claimed is: 1. A method for communicating between a managed device and a device manager, the method comprising: sending a message that is secured using Generic Bootstrapping Architecture (GBA) information or includes GBA push information to the managed device over a first communications channel; and in response to the message, initiating communication between the managed device and the device manager over a second communications channel that is of a different type than the first communications channel, wherein the first communications channel is a cellular channel and the second communications channel is non-cellular channel; wherein receipt of the message at the managed device additionally causes communications between the managed device and the device manager over a third communications channel to cease and switch to the second communications channel, wherein the third communications channel is different to the second communications channel; and wherein the message is sent to the managed device in response to: an increase in data volume; a request to send the managed device a file over a predetermined threshold; a request for a firmware or software update; an increase in electrical power used by the managed device over a predetermined threshold; and a decrease in data transfer rate below a predetermined threshold. 2. The method according to claim 1 , wherein the second communications channel is secure and has a different security architecture to the first communications channel. 3. The method according to claim 1 , wherein the first communications channel is within a first communications system and the second communications channel is within a second communications system different to the first communications system. 4. The method according to claim 1 , wherein the message is SMS or mobile terminated SMS, SMS-MT, WAP-push, or OMA-push. 5. The method according to claim 1 , wherein communications between the managed device and the device manager over the second communications channel are suspended until the message is received. 6. The method according to claim 1 , wherein the managed device is in a dormant state until the message is received. 7. The method according to claim 1 , wherein the message is a secured SMS message, and wherein the SMS message is secured using information established by GBA. 8. The method according to claim 1 , wherein the message is an unsecured SMS messaged containing GBA push information, wherein the method further comprises confirming authenticity of the message using the push GBA information, and wherein communication between the managed device and the device manager over the second communications channel is initiated following successful authentication. 9. The method according to claim 1 , wherein the first communication channel is used to establish cryptographic material to secure the second communication channel. 10. The method according to claim 1 , wherein the managed device is a machine to machine (M2M) device. 11. A system for communicating between a managed device and a device manager, the system comprising: a device manager; a first communications channel; a second communications channel that is different from the first communications channel; and logic configured to: send a message that is secured using Generic Bootstrapping Architecture (GBA) information or includes GBA push information to a managed device over the first communications channel; and in response to the message, initiate communications between the managed device and the device manager over the second communications channel, wherein the first communications channel is a cellular channel and the second communications channel is non-cellular channel; wherein receipt of the message at the managed device additionally causes communications between the managed device and the device manager over a third communications channel to cease and switch to the second communications channel, wherein the third communications channel is different to the second communications channel; and wherein the message is sent to the managed device in response to: an increase in data volume; a request to send the managed device a file over a predetermined threshold; a request for a firmware or software update; an increase in electrical power used by the managed device over a predetermined threshold; and a decrease in data transfer rate below a predetermined threshold. 12. The system of claim 11 , wherein the second communications interface is secure and has a different security architecture to the first communications interface. 13. The system of claim 11 , wherein the first communications interface is configured to communicate with a first communications system and the second communications interface is configured to communicate with a second communications system different to the first communications system.
for providing a confidential data exchange among entities communicating through data packet networks · CPC title
Synchronisation and timing concerns (synchronisation on a memory bus G06F13/4234) · CPC title
Security arrangements; Authentication; Protecting privacy or anonymity · CPC title
Key management, e.g. using generic bootstrapping architecture [GBA] · CPC title
at the transport layer · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.