# US 10,764,252 B2 · Communicating with machine to machine devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,764,252 B2 - Document ID: US10764252B2 - Status: Granted - Kind: B2 - Application number: 15/496,860 - Filed: 2017-04-25 - Published: 2017-10-12 - Granted: 2020-09-01 - Earliest claimed: 2013-09-13 - Assignees: Vodafone IP Licensing Limited - Applicants: Vodafone IP Licensing Limited - Inventors: Nick Bone; Simone Ferrara - Web page: https://patentgrep.com/patent/US10764252B2 ## CPC - G06F 13/1689: {Synchronisation and timing concerns (synchronisation on a memory bus G06F13/4234)} - G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57) - G06F 13/28: using burst mode transfer, e.g. direct memory access {DMA}, cycle steal (G06F13/32 takes precedence) - G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)} - G06F 21/606: {by securing the transmission between two devices or processes} - G06F 21/71: to assure secure computing or processing of information - H04B 1/3816: Mechanical arrangements for accommodating identification devices, e.g. cards or chips; with connectors for programming identification devices - H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords} - H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes} - H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/0442: {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)} - H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)} - H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)} - H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint} - H04L 63/10: {for controlling access to devices or network resources} - H04L 63/166: {at the transport layer} - H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)} - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 67/125: involving control of end-device applications over a network - H04W 4/12: Messaging; Mailboxes; Announcements - H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] - H04W 4/50: Service provisioning or reconfiguring - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04W 8/04: Registration at HLR or HSS [Home Subscriber Server] - H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] - H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA] - H04W 12/0431: Key distribution or pre-distribution; Key agreement - H04W 12/06: Authentication - H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications - H04W 52/0229: {where the received signal is a wanted signal} - H04W 80/06: Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless {(transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16)} - H04W 88/02: Terminal devices - H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals - H04L 63/0838: {using one-time-passwords} - H04L 2463/061: applying further key derivation, e.g. deriving traffic keys from a pair-wise master key - Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management - Y02D 30/70: in wireless communication networks - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04B: TRANSMISSION - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE ## Abstract 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. ## Claims ### Claim 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. ### Claim 2 (depends on 1) The method according to claim 1, wherein the second communications channel is secure and has a different security architecture to the first communications channel. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) The method according to claim 1, wherein the message is SMS or mobile terminated SMS, SMS-MT, WAP-push, or OMA-push. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) The method according to claim 1, wherein the managed device is in a dormant state until the message is received. ### Claim 7 (depends on 1) 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. ### Claim 8 (depends on 1) 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. ### Claim 9 (depends on 1) The method according to claim 1, wherein the first communication channel is used to establish cryptographic material to secure the second communication channel. ### Claim 10 (depends on 1) The method according to claim 1, wherein the managed device is a machine to machine (M2M) device. ### Claim 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. ### Claim 12 (depends on 11) The system of claim 11, wherein the second communications interface is secure and has a different security architecture to the first communications interface. ### Claim 13 (depends on 11) 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.