IP Library Granted Patent US 9,635,057
Granted Patent B2
US 9,635,057 · App. 15/021,910 · Granted Apr 25, 2017

Communicating with machine to machine devices

Inventors: Nick Bone (Newbury Berkshire, GB); Simone Ferrara (Newbury Berkshire, GB)
Assignee: VODAFONE IP LICENSING LTD
H04L63/20G06F13/1689G06F13/28G06F13/4027G06F21/606G06F21/71H04B1/3816H04L9/0861H04L63/029H04L63/04H04L63/0428H04L63/0442H04L63/061H04L63/062H04L63/08H04L63/0823H04L63/0869H04L63/0876H04L63/10H04L63/166H04L67/1095H04L67/125H04L67/42H04W4/001H04W4/005H04W4/12H04W4/14H04W8/04H04W12/02H04W12/04H04W12/06H04W28/08H04W52/0229H04W80/06H04W88/02H04W88/06H04L63/0838H04L2463/061Y02B60/1228Y02B60/1235
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,635,057
App. No.
15/021,910
Granted
Apr 25, 2017
Kind
B2
Abstract

Method and system for communicating between a managed device and a device manager comprising sending the managed device a message over a first communications channel. 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.

Claims (31)

1. A method for communicating between a managed device and a device manager, the method comprising the steps of:

sending the managed device a message over a first communications channel; and

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;

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/or wherein the communications are switched to the third communications channel from the second communications automatically;

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 first communications channel is a cellular channel and the second communications channel is non-cellular channel, and/or the first communications channel is secure or the message is secured.

3. The method according to claim 1 , wherein the second communications channel is secure and has a different security architecture to the first communications channel, and/or 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 the second communications channel is any one of: transmission control protocol, TCP; user datagram protocol, UDP; cellular; wireless; WiFi; WiMax; wired; fixed line; and telephone line.

6. 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.

7. The method according to claim 1 , wherein the managed device is in a dormant state until the message is received.

8. The method according to claim 1 , wherein the message is a secured SMS message, and/or the SMS is secured using information established by generic bootstrapping architecture, GBA.

9. The method according to claim 1 , wherein the message is an unsecured message, and/or the message is an unsecured SMS messaged containing generic bootstrapping architecture, GBA, push information.

10. The method according to claim 9 further comprising the step of 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 channels is initiated following successful authentication.

11. The method according to claim 1 , wherein the message is an SMS message, the method further comprising the step of determining if the SMS message is sent over a secured SMS channel, and/or the first communication channel is used to establish cryptographic material to secure the second communication channel.

12. The method according to claim 1 , wherein the managed device is a machine to machine, M2M, device.

13. The method according to claim 1 , wherein the communications between the managed device and the device manager originate at the managed device.

14. A system for communicating with one or more managed device comprising: a device manager;

a first communications interface;

a second communications interface, different to the first communications interface; and

logic configured to:

send to a managed device a message using the first communications interface; and

initiate communications between the managed device and the device manager using the second communications interface in response to the message;

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/or wherein the communications are switched to the third communications channel from the second communications automatically;

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 redetermined threshold.

15. The system according to claim 14 , wherein the first communications interface is a cellular interface and the second communications interface is non-cellular interface, and/or the first communications interface is secure or the message is secured, and/or the second communications interface is secure and has a different security architecture to the first communications interface.

16. The system according to claim 14 , 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.

17. The system according to claim 14 , wherein the first communications interface is SMS, SMS-MT, WAP-push, or OMA-push, and/or the second communications interface is any one of: transmission control protocol, TCP; user datagram protocol, UDP; cellular; wireless; WiFi; WiMax; wired; fixed line; and telephone line.

18. The system according to claim 14 , further comprising a third communications interface different to the second communications interface, and wherein receipt of the message at the managed device causes communications between the managed device and the device manager using the third communications channel to cease and switch to the second communications interface.

Assignments (1)
COMBINED DECLARATION AND ASSIGNMENT Recorded Aug 19, 2016
From: BONE, NICK; FERRARA, SIMONE
To: VODAFONE IP LICENSING LTD
Reel/Frame 039754/0243 →
Priority Claims (10)
GB 1316370.4 · Sep 13, 2013 · national
GB 1318339.7 · Oct 16, 2013 · national
GB 1409641.6 · May 30, 2014 · national
GB 1409643.2 · May 30, 2014 · national
GB 1409652.3 · May 30, 2014 · national
GB 1409663.0 · May 30, 2014 · national
GB 1414997.5 · Aug 22, 2014 · national
GB 1414999.1 · Aug 22, 2014 · national
GB 1415003.1 · Aug 22, 2014 · national
GB 1415925.5 · Sep 9, 2014 · national
Continuity (1)
Related Publication 20160234686A1 · Aug 11, 2016