Power save mechanism for peer-to-peer communication networks

• US 9,832,725 B2
• Filed: 05/29/2015
• Issued: 11/28/2017
• Est. Priority Date: 03/06/2012
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Ponmudi, Kayalvizhi, Chandrasekar, Karthick Raja
• Primary Examiner(s): Choudhury, Zahid
• Application Number:
  US14/726,123
• Publication Number:
  US 20150264646A1
• Time in Patent Office: 914 Days
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04W 52/0216 using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0229 where the received signal is a wanted signal
• CPC Class Codes: H04W 76/14 Direct-mode setup
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A group owner of a peer-to-peer communication network is configured to determine whether all client devices associated with the peer-to-peer communication network support direct data communication. The group owner is configured to implement an awake mode for a portion of each beacon interval when all the associated client devices support direct data communication. The group owner is configured to implement a sleep mode for a remaining portion of each beacon interval to save power at the group owner without interrupting communications between the associated client devices.

Claims

1. A method comprising:

determining, at a network coordinator device of a peer-to-peer communication network, whether all of a subset of client devices associated with the peer-to-peer communication network support direct data communication; and

in response to determining that all of the subset of client devices support direct data communication,

initiating an awake mode at the network coordinator device at a start time of a beacon interval associated with the network coordinator device, wherein the network coordinator device is to be awake for a predefined time period of the beacon interval, and

in response to detecting that a client request has not been fulfilled during the predefined time period, persisting the network coordinator device as awake past the predefined time period.

2. The method of claim 1, wherein the network coordinator device is a group owner of the peer-to-peer communication network.

3. The method of claim 1, further comprising:

placing the network coordinator device in a sleep mode after the predefined time period and persisting the network coordinator device in the sleep mode until completion of the beacon interval when a client device is in awake mode.

4. The method of claim 1, wherein a time period for persisting the network coordinator device as awake is based, at least in part, on a type of the client request.

5. The method of claim 1, wherein a time period for persisting the network coordinator device as awake is based, at least in part, on a number of pending client requests.

6. The method of claim 1, further comprising placing the network coordinator device to sleep in response to determining the client request has been fulfilled.

7. The method of claim 1, further comprising, in response to completing handshake operations with a new client device and determining the new client device has connected to the peer-to-peer communication network via the network coordinator device, determining whether the new client device supports direct data communication.

8. The method of claim 7, wherein, in response to determining that the new client device does not support direct data communication, implementing a conventional power save mechanism at the network coordinator device.

9. The method of claim 1, wherein the client request comprises a request by a new client device to join the peer-to-peer communication network.

10. The method of claim 1, wherein, in response to determining at least one of the subset of client devices does not support direct data communication, implementing a conventional power save mechanism at the network coordinator device.

11. A network coordinator device comprising:

a processor; and

a memory coupled with the processor, the memory having stored thereon executable instructions that, when executed by the processor, cause the network coordinator device to;

determine whether all of a subset of client devices associated with a peer-to-peer communication network support direct data communication;

in response to a determination that all of the subset of client devices support direct data communication,

initiate an awake mode at the network coordinator device at a start time of a beacon interval associated with the network coordinator device, wherein the network coordinator device is to be awake for a predefined time period of the beacon interval,

detect that a client request has not been fulfilled during maintenance of the awake mode, and

persist the network coordinator device as awake past the predefined time period in response to detection that the client request has not been fulfilled.

12. The network coordinator device of claim 11, wherein the network coordinator device is a group owner of a peer-to-peer communication network.

13. The network coordinator device of claim 11, wherein the instructions further include instructions to cause the network coordinator device to:

place the network coordinator device in a sleep mode after the predefined time period and persist the network coordinator device in the sleep mode until completion of the beacon interval when a client device is in awake mode.

14. The network coordinator device of claim 11, wherein a time period to persist the network coordinator device as awake is based, at least in part, on a type of the client request.

15. The network coordinator device of claim 11, wherein a time period to persist the network coordinator device as awake is based, at least in part, on a number of pending client requests.

16. The network coordinator device of claim 11, wherein the instructions further comprise instructions to place the network coordinator device to sleep in response to a determination that the client request has been fulfilled.

17. The network coordinator device of claim 11, wherein the instructions further cause the network coordinator device to determine whether a new client device supports direct data communication, in response to completion of handshake operations with the new client device and a determination that the new client device has connected to the peer-to-peer communication network.

18. The network coordinator device of claim 17, wherein the instructions further cause the network coordinator device to implement a conventional power save mechanism at the network coordinator device in response to a determination that the new client device does not support direct data communication.

19. The network coordinator device of claim 11, wherein the client request comprises a request by a new client device to join the peer-to-peer communication network.

20. The network coordinator device of claim 11, wherein the instructions further cause the network coordinator device to implement a conventional power save mechanism at the network coordinator device in response to a determination that at least one of the subset of client devices does not support direct data communication.

21. A non-transitory machine-readable medium having instructions stored therein that, when executed by one or more processors, cause a network coordinator device to perform operations that comprise:

determining whether all of a subset of client devices associated with a peer-to-peer communication network support direct data communication; and

in response to determining that all of the subset of client devices support direct data communication,

initiating an awake mode at the network coordinator device at a start time of a beacon interval associated with the network coordinator device is to be awake for a predefined time period of the beacon interval, and

in response to detecting that a client request has not been fulfilled during the predefined time period, persisting the network coordinator device as awake past the predefined time period.

22. The non-transitory machine-readable medium of claim 21, wherein the network coordinator device is a group owner of the peer-to-peer communication network.

23. The non-transitory machine-readable medium of claim 21, wherein the operations further comprise:

placing the network coordinator device in a sleep mode after the predefined time period and persisting the network coordinator device in the sleep mode until completion of the beacon interval when a client device is in awake mode.

24. The non-transitory machine-readable medium of claim 21, wherein a time period for persisting the network coordinator device as awake is based, at least in part, on a type of the client request.

25. The non-transitory machine-readable medium of claim 21, wherein a time period for persisting the network coordinator device as awake is based, at least in part, on a number of pending client requests.

26. The non-transitory machine-readable medium of claim 21, wherein the operations further comprise placing the network coordinator device to sleep in response to determining the client request has been fulfilled.

27. The non-transitory machine-readable medium of claim 21, wherein the operations further comprise, in response to completing handshake operations with a new client device and determining the new client device has connected to the peer-to-peer communication network via the network coordinator device, determining whether the new client device supports direct data communication.

28. The non-transitory machine-readable medium of claim 27, wherein the operations further comprise, in response to determining that the new client device does not support direct data communication, implementing a conventional power save mechanism at the network coordinator device.

29. The non-transitory machine-readable medium of claim 21, wherein the client request comprises a request by a new client device to join the peer-to-peer communication network.

30. The non-transitory machine-readable medium of claim 21, wherein the instructions further comprise:

in response to determining at least one of the subset of client devices does not support direct data communication, implementing a conventional power save mechanism at the network coordinator device.