Machine-to-machine network assisted bootstrapping

US9344888B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9344888-B2
Application numberUS-201414285397-A
CountryUS
Kind codeB2
Filing dateMay 22, 2014
Priority dateMay 22, 2013
Publication dateMay 17, 2016
Grant dateMay 17, 2016

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.

The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.

First claim

Opening claim text (preview).

What is claimed: 1. A user equipment comprising: a processor; and a memory coupled to the processor, the memory having stored thereon executable instructions that when executed by the processor cause the processor to effectuate operations comprising: providing a first Extensible Authentication Protocol (EAP) message to a network node, the first EAP message comprising a machine to machine service provider identifier and a proposed user equipment machine-to-machine service layer identifier; and receiving a second EAP message from the network node, the second EAP message comprising an assigned user equipment machine-to-machine service layer identifier and a network service layer identifier. 2. The user equipment of claim 1 , wherein the memory further comprises executable instructions that when executed by the processor cause the processor to effectuate operations comprising: deriving an encryption key based on the second EAP message, the encryption key used when the user equipment communicates with the machine-to-machine server service layer. 3. The user equipment of claim 1 , wherein the service provider identifier comprises: a name of the company that provides service layers that the user equipment wants to connect with; or a name of a service layer that the user equipment wants to connect with. 4. The user equipment of claim 1 , wherein the network node is a trusted non-3GPP access point. 5. The user equipment of claim 1 , wherein the first EAP message further comprises an access network identifier of the user equipment, or a request for a particular application identifier to be assigned to the user equipment. 6. The user equipment of claim 1 , wherein the data comprises a random challenge, a network authentication vector, or a message authentication code. 7. The user equipment of claim 1 , wherein the second EAP message further comprises: an identifier of an application on the user equipment, the identifier of the application assigned to the application by a machine-to-machine server. 8. The user equipment of claim 1 , wherein the providing of the first EAP messages is responsive to receiving a request for the identity of the user equipment from the network node. 9. A method comprising: providing a first Extensible Authentication Protocol (EAP) message to a network node, the first EAP message comprising a machine to machine service provider identifier and proposed user equipment service layer identifier; and receiving a second EAP message from the network node, the second EAP message comprising an assigned user equipment machine-to-machine service layer identifier and a network service layer identifier. 10. The method of claim 9 , wherein the memory further comprises executable instructions that when executed by the processor cause the processor to effectuate operations comprising: deriving an encryption key based on the second EAP message, the encryption key used when the user equipment communicates with the a machine-to-machine server service layer. 11. The method of claim 9 , wherein the service provider identifier comprises: a name of the company that provides service layers that the device wants to connect with; or a name of a service layer that the device wants to connect with. 12. The method of claim 9 , wherein the network node is a trusted non-3GPP access point. 13. The method of claim 9 , wherein the first EAP message further comprises an access network identifier of the device, or a request for a particular application identifier to be assigned to the device. 14. The method of claim 9 , wherein the data comprises a random challenge, a network authentication vector, or a message authentication code. 15. The method of claim 9 , wherein the second EAP message further comprises: an identifier of an application on the device, the identifier of the application assigned to the application by a machine-to-machine server. 16. The method of claim 9 , wherein the providing of the first EAP messages is responsive to receiving a request for the identity of the device from the network node. 17. A computer readable storage medium comprising computer executable instructions that when executed by a computing device cause the computing device to perform the instructions comprising: providing a first Extensible Authentication Protocol (EAP) message to a network node, the first EAP message comprising a machine to machine service provider identifier and a proposed user equipment machine-to-machine service layer identifier; and receiving a second EAP message from the network node, the second EAP message comprising an assigned user equipment machine-to-machine service layer identifier and a network service layer identifier. 18. The computer readable storage medium of claim 17 , wherein the first EAP message further comprises an access network identifier of the computing device, or a request for a particular application identifier to be assigned to the computing device. 19. The computer readable storage medium of claim 17 , wherein the data comprises a random challenge, a network authentication vector, or a message authentication code. 20. The computer readable storage medium of claim 17 , wherein the second EAP message further comprises: an identifier of an application on the computing device, the identifier of the application assigned to the application by a machine-to-machine server.

Assignees

Inventors

Classifications

  • involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

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

  • Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

  • for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838) · CPC title

  • H04W12/06Primary

    Authentication · 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 US9344888B2 cover?
The service layer may leverage the access network infrastructure so that applications on a device may bootstrap with a machine-to-machine server without requiring provisioning beyond what is already required by the access network.
Who is the assignee on this patent?
Convida Wireless LLC, Convida Wireless LLC
What technology area does this patent fall under?
Primary CPC classification H04L63/0876. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 17 2016 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 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).