System and method for power management

• US 7,769,362 B2
• Filed: 06/22/2007
• Issued: 08/03/2010
• Est. Priority Date: 06/23/2006
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Olympus Corporation
• Inventors: Heidari-Bateni, Ghobad, Muqattash, Alaa
• Primary Examiner(s): Trinh; Sonny
• Application Number:
  US11/767,342
• Publication Number:
  US 20070295259A1
• Time in Patent Office: 1,138 Days
• Field of Search: 455/343.1, 455/127.1, 455/127.5, 455/572, 455/574, 455/343.2, 455/343.4, 455/343.5, 370/311, 370/338
• US Class Current: 455/343.4
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• CPC Class Codes: H04L 2012/2841 Wireless
• CPC Class Codes: H04L 2012/2849 Audio/video appliances
• CPC Class Codes: H04W 52/0216 using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0219 where the power saving management affects multiple terminals
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

The present invention provides a method for managing power of devices on a network. The method comprises: transmitting a first weighted value and a first anchor status of a first device on the network to a second device on the network, wherein the second device is a neighboring device to the first device; receiving a second weighted value and a second anchor status from the second device; and setting one of the devices as an anchor device based on one or more of weighted values and the anchor statuses, wherein the anchor device is configured to either wake up at predetermined times or to remain active.

Claims

1. A method for managing power of a plurality of devices on a network, comprising:

transmitting a first weighted value and a first anchor status of a first device on the network to a second device on the network, wherein the second device is a neighboring device to the first device;

receiving a second weighted value and a second anchor status from the second device; and

assigning an anchor status to one of the devices based on one or more of the weighted values and the anchor statuses, wherein the anchor device is configured to either wake up at predetermined times or to remain active.

2. The method of claim 1, wherein each weighted value comprises a number of cycles a respective device has not been an anchor.

3. The method of claim 2, wherein each weighted value is further based on one or more of a device characteristics such as the device function, type, power characteristics, location in the network, importance ranking, and communication partners.

4. The method of claim 3, further comprising:

assigning either the first or second device as a dedicated anchor device for the network based on the first and second weighted values.

5. The method of claim 1, wherein the anchor is configured to go into a partial hibernation when it is not in active mode.

6. The method of claim 1, wherein assigning an anchor status further comprising:

selecting the first device as the anchor device if only the first anchor status is positive;

selecting the second device as the anchor device for the first device if only the second anchor status is positive;

selecting the first or second device as the anchor device based on the weighted value of each respective device if both the first and second anchor statuses are the same; and

selecting the first or second device as the anchor device based on a beacon slot value of each respective device if both the first and second weighted values are the same.

7. The method of claim 6, wherein a device with a higher beacon slot value is selected as the anchor device.

8. The method of claim 1, wherein the anchor device serves as the anchor for itself and for one or more neighboring devices.

9. The method of claim 1, further comprising:

receiving a third weighted value and a third anchor status from a third device on the network.

10. The method of claim 9, wherein assigning an anchor status further comprising:

a) receiving a weighted value and an anchor status from each neighboring device;

b) selecting one of the devices to be a non-anchor device if all of its neighboring devices have weighted values higher than its own weighted value or if none of its neighboring devices have lower weighted values and all of the neighboring devices with equal weighted values have beacon slot values higher than a beacon slot value of the device;

c) selecting one of the devices as the anchor device if all of its neighboring devices have lower weighted values or if none of its neighboring devices have higher weighted values and all of the neighboring devices with weighted values equal to its own weighted value have beacon slot values lower than a beacon slot value of the device;

d) setting one of the devices as undecided status if none of the devices is selected in steps b and c; and

e) sending a status update of the device to each neighboring device.

11. The method of claim 10, further comprising:

for a non-anchor device, choosing a neighboring device with the undecided status and with a highest weighted value as an anchor device.

12. A system having a plurality of devices connected to a network, the system comprising:

a first device on the network configured to transmit a first weighted value and a first anchor status to a neighboring device; and

a second device on the network configured to transmit a second weighted value and a second anchor status to the first device, wherein the second device is the neighboring device to the first device;

wherein the first and second device are configured to select one of the devices as an anchor device based on one or more of weighted values and the anchor statuses, wherein the anchor device is configured to either wake up at predetermined times or to remain active.

13. The system of claim 12, wherein each weighted value comprises a number of cycles a respective device has not been an anchor.

14. The system of claim 13, wherein each weighted value is further based on one or more of a device characteristics such as the device function, type, power characteristics, location in the network, importance ranking, and communication partners.

15. The system of claim 14, wherein the first or second device is configured to assign either the first or second device as a dedicated anchor device for the network based on one or more of the weighted values.

16. The system of claim 12, wherein the anchor is configured to go into a partial hibernation when it is not in active mode.

17. The system of claim 12, wherein:

the first device is configured to select itself as the anchor device if only the first anchor status is positive,

the second device is configured to select itself as the anchor device if only the second anchor status is positive,

the first or second device is configured to select itself as the anchor device based on the weighted value of each respective device if both the first and second anchor statuses are the same, and

wherein the first or second device is configured to select itself as the anchor device based on a beacon slot value of each respective device if both the first and second weighted values are the same.

18. The system of claim 17, wherein the device with a higher beacon slot value is selected as the anchor device.

19. The system of claim 17, wherein the device with a higher weighted value is selected as the anchor device.

20. The system of claim 19, wherein:

one or more of the devices are configured to select one of the devices to be a non-anchor device if all of its neighboring devices have weighted values higher than its own weighted value or if none of its neighboring devices have lower weighted values and all of the neighboring devices with equal weighted values have beacon slot values higher than a beacon slot value of the device,

one or more of the devices are configured to select one of the devices as the anchor device if all of its neighboring devices have lower weighted values or if none of its neighboring devices have higher weighted values and all of the neighboring devices with weighted values equal to its own weighted value have beacon slot values lower than a beacon slot value of the device, and

wherein one or more of the devices are configured to set one of the devices as undecided status if the device is not set as the non-anchor or anchor device.

21. The system of claim 20, wherein the non-anchor device is configured to choose a neighboring device with the undecided status and with a highest weighted value as the anchor device.

22. The system of claim 17, wherein each device must receive a weighted value or anchor status from all neighboring devices prior to selecting itself as the anchor device.

23. The system of claim 12, wherein the anchor device serves as the anchor for itself and for one or more neighboring devices.

24. The system of claim 12, further comprising:

a third device on the network configured to transmit a third weighted value and a third anchor status to a neighboring device.