Communicating with a machine to machine device

Patent metadata

Field	Value
Publication number	US-10439991-B2
Application number	US-201415021873-A
Country	US
Kind code	B2
Filing date	Sep 12, 2014
Priority date	Sep 13, 2013
Publication date	Oct 8, 2019
Grant date	Oct 8, 2019

Abstract

The present disclosure provides a bootstrapping server, a network application function (NAF), a system and methods for establishing secure communication between a machine to machine (M2M) device and a NAF. A method for establishing secure communication between the NAF and M2M device comprises receiving a first data object, tunneling the first data object to the M2M device, via an interface between the NAF and the M2M device, for enabling the M2M device to derive first information to establish said secure communication, receiving a second data object and deriving second information for use in establishing said secure communication with the M2M device.

First claim

The invention claimed is:

1. A computing system comprising:
a network application function (NAF) for establishing secure communication between the NAF and a machine to machine (M2M) device;
at least one processor; and
a computer readable hardware storage device having stored thereon computer-executable instructions which, when executed by the at least one processor, cause the computing system to perform the following:
receive a first data object;
in response to determining that the M2M device is registered for push services, use a push message to tunnel the first data object to the M2M device via an interface between the NAF and the M2M device, the first data object enabling the M2M device to derive first information to establish said secure communication, wherein determining that the M2M device is registered for push services is performed by the M2M device sending a notification to the NAF to inform the NAF the M2M device is registered and at least one of:
the NAF, which includes a pre-established table that is based on M2M information, checking the pre-established table to determine whether the M2M device is registered; or
the NAF refraining from checking whether the M2M device is registered and instead relying on a response from a bootstrapping server function (BSF), where the BSF determines whether the M2M device is registered and informs the NAF in the response;

receive a second data object; and
derive second information for use in establishing said secure communication with the M2M device.

2. The computing system of claim 1 , wherein:
the second data object is a new shared secret;
the new shared secret is derivable at least in part from at least part of a third data object;
the third data object is derived from an existing shared secret; and
the existing shared secret is shared between a network data store and the M2M device.

3. The computing system of claim 1 , wherein execution of the computer-executable instructions further causes the computing system to:
receive, via the interface between the NAF and the M2M device, a tunneled request for the first data object, the tunneled request comprising an identifier of the M2M device; and
provide the tunneled request for the first data object to a bootstrapping server function.

4. The computing system of claim 1 , being further configured to:
receive a transaction identifier from a bootstrapping server function; and
tunnel the transaction identifier to the M2M device via the interface between the NAF and the M2M device.

5. The computing system of claim 1 , being further configured to:
receive, via the interface between the M2M device and the NAF, a tunnelled authentication data object; and
provide the authentication data object to a bootstrapping server function.

6. The computing system of claim 1 , being further configured to:
receive from a bootstrapping server function a notification of successful authentication; and
tunnel the notification of successful authentication to the M2M device via the interface between the M2M device and the NAF.

Assignees

• Vodafone Ip Licensing Ltd

Inventors

• Bone Nick
• Snape Tim

Classifications

• H04W80/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)} · CPC title

• H04W12/06

  Authentication · CPC title

• H04W88/02

  Terminal devices · CPC title

• H04L63/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) · CPC title

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title