Device Triggering

• US 20140330952A1
• Filed: 05/06/2014
• Published: 11/06/2014
• Est. Priority Date: 05/06/2013
• Status: Active Grant

• Current Assignee: Convida Wireless LLC
• Original Assignee: Convida Wireless LLC
• Inventors: Starsinic, Michael F., Seed, Dale N.
• Granted Patent: US 9,800,621 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Service layer and application triggering may be used in a machine-to-machine environment. In an embodiment, an existing service layer procedure, such as registration, may allow a device or gateway service layer or application to indicate to a machine-to-machine server what port is listened to for triggers. In another embodiment, triggering may be used to provide bootstrapping instructions, including temporary bootstrapping identifiers, in trigger requests. In another embodiment, triggering may be used to assist with event notification. Service layer or application instructions may be embedded inside of trigger payloads. A trigger payload format is defined.

Claims

1. A method comprising:

providing, by a first machine-to-machine services capabilities layer entity, a first message for registering with a second machine-to-machine services capabilities layer entity,

the first message for registering with the second machine-to-machine services capabilities layer entity comprising instructions for communicating with an application of the first machine-to-machine services capabilities layer entity,

the instructions for communicating with the application of the first machine-to-machine services capabilities layer entity comprising an access network device identifier and a port number; and

listening for a second message based on the provided instructions for communicating with the first machine-to-machine services capabilities layer entity,

the second message indicative of being sent by the second machine-to-machine services capabilities layer entity.

2. The method of claim 1, wherein the second message is sent over a control plane.

3. The method of claim 1, further comprising:

receiving, by the first machine-to-machine services capabilities layer entity, the second message based on the provided instructions for registering with the first machine-to-machine services capabilities layer entity comprising the port number.

4. The method of claim 3, wherein the second message comprises:

an indication that a purpose of the second message is an event notification, and

a universal resource indicator that directs the first machine-to-machine services capabilities layer entity to details of the event.

5. The method of claim 1, wherein the first machine-to-machine services capabilities layer entity periodically provides an update of the port number or the access network device identifier to the second machine-to-machine services capabilities layer entity.

6. The method of claim 1, further comprising:

receiving the second message via the control plane, the second message comprising a temporary identifier for the first machine-to-machine services capabilities layer entity to use when communicating with the second machine-to-machine services capabilities layer entity via a user plane.

7. The method of claim 1, wherein the first machine-to-machine services capabilities layer entity is a server, a user equipment, an application, or a service layer.

8. A first machine-to-machine services capabilities layer entity in a communication network 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 message for registering with a second machine-to-machine services capabilities layer entity,

the first message for registering with the second machine-to-machine services capabilities layer entity comprising instructions for communicating with the first machine-to-machine services capabilities layer entity,

the instructions for communicating with the first machine-to-machine services capabilities layer entity comprising an access network device identifier and a port number; and

listening for a second message based on the provided instructions for communicating with the first machine-to-machine services capabilities layer entity,

the second message indicative of being sent by the second machine-to-machine services capabilities layer entity.

9. The first machine-to-machine services capabilities layer entity in the communication network of claim 8, wherein the second message is sent over a control plane.

10. The first machine-to-machine services capabilities layer entity in the communication network of claim 8, wherein the operations further comprise:

receiving, by the first machine-to-machine services capabilities layer entity, the second message based on the provided instructions for communicating with the first machine-to-machine services capabilities layer entity comprising the port number.

11. The first machine-to-machine services capabilities layer entity in the communication network of claim 10, wherein the second message comprises:

an indication that a purpose of the first message is an event notification, and a universal resource indicator that directs the first machine first machine-to-machine services capabilities layer entity to details of the event.

12. The first machine-to-machine services capabilities layer entity in the communication network of claim 8, wherein the first machine-to-machine services capabilities layer entity periodically provides an update of the port number or the access network device identifier to the second machine-to-machine services capabilities layer entity.

13. The first machine-to-machine services capabilities layer entity in the communication network of claim 8, wherein the operations further comprise:

receiving the second message via the control plane, the second message comprising a temporary identifier for the first machine-to-machine services capabilities layer entity to use when communicating with the second machine-to-machine services capabilities layer entity via a user plane.

14. The first machine-to-machine services capabilities layer entity in the communication network of claim 8, wherein the first machine-to-machine services capabilities layer entity is a server, a user equipment, an application, or a service layer.

15. A first machine-to-machine services capabilities layer entity in a communication network 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;

receiving a first message comprising instructions for bootstrapping with a second machine-to-machine services capabilities layer entity,

the instructions for bootstrapping with the second machine-to-machine services capabilities layer entity comprising a temporary identifier for the first machine-to-machine services capabilities layer entity to use when initiating bootstrapping and

bootstrapping with the second machine-to-machine services capabilities layer entity using the temporary identifier for the first machine-to-machine services capabilities layer entity received in the first message.

16. The first machine-to-machine services capabilities layer entity of claim 15, wherein the bootstrapping with the second machine-to-machine services capabilities layer entity using the temporary identifier for the first machine-to-machine services capabilities layer entity occurs over a user plane.

17. The first machine-to-machine services capabilities layer entity of claim 15, wherein the first message is received over a control plane.

18. The first machine-to-machine services capabilities layer entity of claim 15, wherein the first machine-to-machine services capabilities layer entity is a server, a user equipment, an application, or a service layer.

19. The first machine-to-machine services capabilities layer entity of claim 15, wherein the second machine-to-machine services capabilities layer entity retains a mapping of the temporary identifier to a permanent device identifier of the first machine-to-machine services capabilities layer entity.

20. The first machine first machine-to-machine services capabilities layer entity of claim 15, wherein the first message comprises instructions for registering.