Coordination of M2M device operation by M2M device managers in a LAN

• US 9,049,104 B2
• Filed: 07/19/2011
• Issued: 06/02/2015
• Est. Priority Date: 07/19/2011
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Zhu, Zhongwen
• Primary Examiner(s): BAROT, BHARAT
• Application Number:
  US13/186,196
• Publication Number:
  US 20130024556A1
• Time in Patent Office: 1,414 Days
• Field of Search: 709223-226, 726 1- 2, 726 26- 29, 370/238
• US Class Current: 1/1
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
• CPC Class Codes: Y04S 40/18 Network protocols supporting networked applications, e.g. including control of end-device applications over a network

Abstract

Teachings herein include a first machine-to-machine (M2M) device manager in a local area network (LAN). The first manager receives operating information for a first M2M device managed by the first manager. This operating information may indicate, for example, the operating state (e.g., on or off) of the first device. Responsive to receiving this operating information, the first manager coordinates operation of a second M2M device that is managed by a second M2M device manager in the LAN. The first manager effectively does so by evaluating the received operating information according to a set of policy-based rules, generating control signaling according to that evaluation, and then sending the generated control signaling to the second manager. Because this control signaling is sent horizontally between different M2M device managers, rather than vertically to some centralized server, such operation coordination can occur across M2M devices that would not otherwise be inter-operable.

Claims

1. A method implemented by a first machine-to-machine (M2M) device manager in a local area network (LAN), the first M2M device manager comprising one or more processing circuits, wherein the method comprises:

receiving, at the first M2M device manager, operating information for a first M2M device that is in the LAN and that is managed by the first M2M device manager; and

at the first M2M device manager, coordinating operation of a second M2M device that is in the LAN and that is managed by a second M2M device manager in the LAN, by;

evaluating at least said operating information for the first M2M device according to a set of policy-based rules;

generating control signaling according to that evaluation, wherein the control signaling is either;

said operating information for the first M2M device to assist the second M2M device manager in managing the second M2M device;

or a command related to operation of the second M2M device; and

sending said control signaling from the first M2M device manager to the second M2M device manager.

2. The method of claim 1, wherein said control signaling indicates said operating information for the first M2M device to the second M2M device manager.

3. The method of claim 1, wherein said control signaling directs the second M2M device manager to respond with operating information for the second M2M device, wherein said receiving further comprises receiving operating information for the second M2M device from the second M2M device manager responsive to said control signaling, and wherein said coordinating further comprises:

evaluating said operating information for the first and second M2M devices according to the set of policy-based rules;

generating, based on that evaluation, additional control signaling which directs the second M2M device manager to manage the second M2M device in accordance with the set of policy-based rules; and

sending that additional control signaling to the second M2M device manager.

4. The method of claim 1, further comprising receiving one or more rule definitions and dynamically initializing or modifying the set of policy-based rules according to those one or more rule definitions.

5. The method of claim 1, wherein the operating information indicates an operating state of the first M2M device, and wherein said coordinating comprises coordinating an operating state of the second M2M device.

6. The method of claim 1, wherein the first and second M2M device managers belong to a first hierarchy of M2M device managers, wherein different M2M device managers in the first hierarchy manage different groups of one or more M2M devices.

7. The method of claim 6, wherein the different groups either include M2M devices of different types, M2M devices of different types, M2M devices in different locations, or M2M devices that use different communication protocols.

8. The method of claim 6, wherein at least one of:

the operating information comprises operating information aggregated for a group of M2M devices managed by the first M2M device manager, including the first M2M device; and

said coordinating comprises coordinating the collective operation of a group of M2M devices managed by the second M2M device manager, including the second M2M device.

9. The method of claim 6, further comprising reporting the operating information for the first M2M device to a central M2M device management system via a gateway to a telecommunications network, the gateway being identified in the telecommunications network by an identity that is common to all M2M device managers in the first hierarchy.

10. The method of claim 6, further comprising coordinating operation of a third M2M device managed by a third M2M device manager that is in another LAN and that belongs to a second hierarchy of M2M device managers, by evaluating said operating information according to a set of policy based rules, generating control signaling according to that evaluation, and sending said control signaling by the third M2M device manager via first and second gateways to a telecommunications network, wherein the first gateway is identified in the telecommunications network by a first identity that is common to all M2M device managers in the first hierarchy and the second gateway is identified in the telecommunications network by a second identity that is common to all M2M device managers in the second hierarchy.

11. The method of claim 1, wherein coordinating operation of the second M2M device includes controlling the consumption of a utility by the second M2M device.

12. The method of claim 1, wherein the first M2M device and the first M2M device manager reside in a first home, wherein the first M2M device generates an excess of a utility, and wherein the method further comprises coordinating operation of a third M2M device managed by a third M2M device manager in another LAN, wherein the third M2M device and the third M2M device manager reside in a second home, and wherein coordinating operation of the third M2M device comprises providing the excess of said utility to the third M2M device in the second home.

13. A first machine-to-machine (M2M) device manager in a local area network (LAN), comprising:

a communications interface configured to receive operating information for a first M2M device that is in the LAN and that is managed by the first M2M device manager;

a memory configured to store a set of policy-based rules; and

one or more processing circuits configured to coordinate operation of a second M2M device that is in the LAN and that is managed by a second M2M device manager in the LAN, by;

evaluating at least said operating information for the first M2M device according to the set of policy-based rules;

generating control signaling according to that evaluation, wherein the control signaling is either;

said operating information for the first M2M device to assist the second M2M device manager in managing the second M2M device;

or a command related to operation of the second M2M device; and

sending said control signaling to the second M2M device manager.

14. The first M2M device manager of claim 13, wherein said control signaling indicates said operating information for the first M2M device to the second M2M device manager.

15. The first M2M device manager of claim 13, wherein said control signaling directs the second M2M device manager to respond with operating information for the second M2M device, wherein said communications interface is further configured to receive operating information for the second M2M device from the second M2M device manager responsive to said control signaling, and wherein said one or more processing circuits are further configured to:

evaluate said operating information for the first and second M2M devices according to the set of policy-based rules;

generate, based on that evaluation, additional control signaling which directs the second M2M device manager to manage the second M2M device in accordance with the set of policy-based rules; and

send that additional control signaling to the second M2M device manager.

16. The first M2M device manager of claim 13, wherein the communications interface is further configured to receive one or more rule definitions and wherein the one or more processing circuits are configured to dynamically initialize or modify the set of policy-based rules according to those one or more rule definitions.

17. The first M2Mdevice manager of claim 13, wherein the operating information indicates an operating state of the first M2M device, and wherein said one or more processing circuits are configured to coordinate an operating state of the second M2M device.

18. The first M2M device manager of claim 13, wherein the first and second M2M device managers belong to a first hierarchy of M2M device managers, wherein different M2M device managers in the first hierarchy marage different groups of one or more M2M devices.

19. The first M2M device manager of claim 18, wherein the different groups either include M2M devices of different types, M2M devices in different locations or M2M devices that use different communication protocols.

20. The first M2M device manager of claim 18, wherein at least one of:

the operating information comprises operating information aggregated for a group of M2M devices managed by the first M2M device manager, including the first M2M device; and

said one or more processing circuits are configured to coordinate the collective operation of a group of M2M devices managed by the second M2M device manager, including the second M2M device.

21. The first M2M device manager of claim 18, wherein said one or more processing circuits are further configured to report the operating information for the first M2M device to a central M2M device management system via a gateway to a telecommunications network, the gateway being identified in the telecommunications network by an identity that is common to all M2M device managers in the first hierarchy.

22. The first M2M device manager of claim 18, wherein said one or more processing circuits are further configured to coordinate operation of a third M2M device managed by a third M2M device manager that is in another LAN and that belongs to a second hierarchy of M2M device managers, by evaluating said operating information according to a set of policy-based rules, generating control signaling according to that evaluation, and sending said control signaling to the third M2M device manager via first and second gateways to a telecommunications network, wherein the first gateway is identified in the telecommunications nework by a first identity that is common to all M2M device managers in the first hierarchy and the second gateway is identified in the telecommunications network by a second identity that is common to all M2M device managers in the second hierarchy.

23. The first M2M device manager of claim 13, wherein said one or more processing circuits are configured to coordinate operation of the second M2M device by controlling the consumption of a utility by the second M2M device.

24. The first M2M device manager of claim 13, wherein the first M2M device and the first M2M device manager reside in a first home, wherein the first M2M device generates an excess of a utility, and wherein said one or more processing circuits are further configured to coordinate operation of a third M2M device managed by a third M2M device manager in another LAN, wherein the third M2M device and the third M2M device manager reside in a second home, and wherein the one or more processing circuits are configured to coordinate operation of the third M2M device by providing the excess of said utility to the third M2M device in the second home.