SYSTEMS AND METHODS FOR EVENT NOTIFICATION FRAMEWORK IN A MACHINE-TO-MACHINE (M2M) CONTEXT

• US 20130262576A1
• Filed: 04/03/2012
• Published: 10/03/2013
• Est. Priority Date: 04/03/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Foti, George
• Granted Patent: US 9,113,283 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• 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

Systems and methods provide for managing subscriptions to changes in resources in a Machine-to-Machine (M2M) system at a communications node. A method for such includes receiving, at an interface, a first subscription request from a first user to an application event; determining, by a processor, if other devices are subscribed to the application event; reading, by the communications node, the first subscription request including data, semantics and syntax; storing, in a memory, binding information for the first user and the application event; and transmitting, by the interface, if, based on said step of determining, no other devices are subscribed to the application event a second subscription message toward an M2M application server (AS).

Claims

1. A system for managing subscriptions to changes in resources in a Machine-to-Machine (M2M) system, wherein the resources are associated with M2M devices, the system comprising:

an event notification platform configured to receive subscription requests from users to application events in an M2M environment, the event notification platform including;

an interface configured to receive a first subscription request from a first user to an application event;

a processor configured to determine if other devices are subscribed to the application event;

the event notification platform configured to read the contents of the first subscription message request including data, semantics and syntax;

a memory configured to store binding information for the first user and the application event; and

the interface configured to transmit if, based on said step of determining, no other devices are subscribed to the application event a second subscription message toward an M2M application server (AS);

the M2M AS configured to receive the second subscription message and notification messages from an M2M service capabilities platform (SCP), configured to subscribe to the M2M SCP, and configured to determine if information in a received first notification message includes a change to the application event in the M2M environment which triggers transmitting a second notification message toward the event notification platform; and

an M2M SCP configured to identify an equivalent extensible markup language (XML) configuration access protocol (XCAP) resource associated with an M2M device based on a received third subscription message from the M2M AS.

2. A method for managing subscriptions to changes in resources in a Machine-to-Machine (M2M) system at a communications node, the method comprising:

receiving, at an interface, a first subscription request from a first user to an application event;

determining, by a processor, if other devices are subscribed to the application event;

reading, by the communications node, the first subscription request including data, semantics and syntax;

storing, in a memory, binding information for the first user and the application event; and

transmitting, by the interface, if, based on said step of determining, no other devices are subscribed to the application event a second subscription message toward an M2M application server (AS).

3. The method of claim 2, wherein the communications node is an event notification platform.

4. The method of claim 2, further comprising:

receiving, at the interface, a third subscription request from a second user to the application event;

determining, by the processor, if other devices are subscribed to the application event; and

storing, in the memory, binding information for the second user and the application event.

5. The method of claim 4, wherein the binding information for the first user and the application event and the binding information for the second user and the application event is stored in a table in the memory.

6. The method of claim 2, further comprising:

receiving a notification message which includes change information associated with the application event;

determining which users are associated with the application event received in the notification message; and

transmitting the change information associated with the application event to the users.

7. The method of claim 6, wherein transmitting the change information associated with the application event to the users includes transmitting to an entity which was identified in the first subscription request associated with the application event, wherein the entity is not the user which transmitted the first subscription request.

8. The method of claim 2, wherein the communications node is a stand-alone node.

9. The method of claim 2, wherein the communications node is collocated on a node with at least one other function.

10. The method of claim 2, further comprising:

storing, by the memory, a list of which application servers support which application events.

11. The method of claim 2, further comprising:

determining, based on said step of reading said first subscription message, whether to reject said first subscription request or perform said steps of storing and transmitting.

12. The method of claim 2, further comprising:

performing the duties of a security gateway including stopping denial of service attacks.

13. The method of claim 2, wherein the interface includes a first communications interface and a second communications interface, wherein communications between the communications node and the first user is over the first communications interface and communications between the communications node and the M2M AS are over the second communications interface, wherein the first communications interface and the second communications interface are different.

14. A communications node for managing subscriptions to changes in resources in a Machine-to-Machine (M2M) system, the communications node comprising:

an interface configured to receive a first subscription request from a first user to an application event;

a processor configured to determine if other devices are subscribed to the application event;

the communications node configured to read the first subscription message request including data, semantics and syntax;

a memory configured to store binding information for the first user and the application event; and

the interface configured to transmit if, based on said step of determining, no other devices are subscribed to the application event a second subscription message toward an M2M application server (AS).

15. The communications node of claim 14, wherein the communications node is an event notification platform.

16. The communications node of claim 14, further comprising:

the interface configured to receive a third subscription request from a second user to the application event;

the processor configured to determine if other devices are subscribed to the application event; and

the memory configured to store binding information for the second user and the application event.

17. The communications node of claim 16, wherein the binding information for the first user and the application event and the binding information for the second user and the application event is stored in a table in the memory.

18. The communications node of claim 14, further comprising:

the interface configured to receive a notification message which includes change information associated with the application event;

the processor configured to determine which users are associated with the application event received in the notification message; and

the interface configured to transmit the change information associated with the application event to the users.

19. The communications node of claim 18, wherein transmitting the change information associated with the application event to the users includes transmitting to an entity which was identified in the first subscription request associated with the application event, wherein the entity is not the user which transmitted the first subscription request.

20. The communications node of claim 14, wherein the communications node is a stand-alone node.

21. The communications node of claim 14, wherein the communications node is collocated on a node with at least one other function.

22. The communications node of claim 14, further comprising:

the memory configured to store a list of which application servers support which application events.

23. The communications node of claim 14, wherein based on reading said first subscription message, determining whether to reject said first subscription request or perform said steps of storing and transmitting.

24. The communications node of claim 14, wherein the communications node performs the duties of a security gateway including stopping denial of service attacks.

25. The communications node of claim 14, wherein the interface includes a first communications interface and a second communications interface, wherein communications between the communications node and the first user is over the first communications interface and communications between the communications node and the M2M AS are over the second communications interface, wherein the first communications interface and the second communications interface are different.