IP Library › Granted Patent US 9,681,444
Granted Patent B2
US 9,681,444 · App. 14/819,361 · Granted Jun 13, 2017

Wireless router or residential gateway capable of distinguishing power-sensitive wireless sensors and providing separate treatment thereto

Inventors: Peiman Amini (Mountain View, CA); Joseph Amalan Arul Emmanuel (Cupertino, CA); Arms Yongyuth (Cupertino, CA)
Assignee: NETGEAR, INC.
H04W72/0446H04W36/06H04W52/0209H04W72/0406H04W72/10H04W76/02H04W76/045H04W88/16H04W72/04H04W84/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,681,444
App. No.
14/819,361
Granted
Jun 13, 2017
Kind
B2
Abstract

Techniques are disclosed for a wireless router or residential gateway to distinguish power-sensitive wireless sensors and provide separate treatments thereto for low power consumption connections. In some embodiments, a network device includes a wireless network circuit, and control circuitry coupled to the network circuit and configured to, upon receipt of a request of connection from a client, identify whether the client is power-sensitive. The network device can further cause, if the client is identified as power-sensitive, the power-sensitive client to connect using a low-power connection while maintaining a regular connection to other regular clients. The low-power connection can be operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated.

Claims (119)

1. A network device, comprising:

control circuitry coupled to one or more wireless network circuits and configured to:

upon receipt of a request of connection from a client, identify whether the client is power-sensitive; and

if the client is identified as power-sensitive, cause the power-sensitive client to connect using a low-power connection while maintaining a regular connection to other regular clients,

wherein the low-power connection has a relaxed connection maintenance standard relative to the regular connection, and

wherein the relaxed connection maintenance standard expects to receive keep alive messages at a frequency less than default.

2. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, and wherein the control circuitry is further configured to:

switch, for data traffic from the power-sensitive client, the power-sensitive client from the first channel to the second channel for a duration of the traffic.

3. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, and wherein the control circuitry is further configured to:

discover whether a connected client is power-sensitive; and

shift the connected client from the second channel to the first channel if the connected client is power-sensitive.

4. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, and wherein the client is initially connected to the network device on the second channel.

5. The network device of claim 1 , wherein the control circuitry is further configured to:

operate a first virtual access point (AP) for the low-power connection; and

operate a second virtual AP for the regular connection,

wherein the first and second APs use different service set identifiers (SSIDs).

6. The network device of claim 1 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client so as to anticipate when there is data traffic from the power-sensitive client; and

adjust the network circuits based on the anticipation.

7. The network device of claim 1 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client regarding what resource the power-sensitive client needs for transmitting data traffic to the network device;

arrange a time slot based on the information; and

convey information to the power-sensitive client regarding the time slot.

8. The network device of claim 1 , wherein the control circuitry is further configured to:

give priority to the power-sensitive client when there is data traffic from the power-sensitive client.

9. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, and wherein the first channel is employed by a network circuit different from a second network circuit by which the second channel is employed.

10. The network device of claim 1 , further comprising:

a buffer configured to accommodate a uplink transmission rate slower than that of the regular connection from the power-sensitive client.

11. The network device of claim 1 , wherein the control circuitry is further configured to:

broadcast information about the network device's ability of low-power connection.

12. The network device of claim 1 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client regarding a wake-up schedule of the power-sensitive client.

13. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated.

14. The network device of claim 1 , wherein the low-power connection has a longer keep alive expiration period than the regular connection so that the network device does not disassociate the power-sensitive client after a regular keep alive expiration period expires.

15. The network device of claim 1 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, and wherein the control circuitry is further configured to:

select the first and second channels, respectively, from available channels based on one or more connection environment parameters.

16. The network device of claim 15 , wherein the connection environment parameters include one or more of: channel noise, channel cross-interference, number of overlapping basic service sets (OBSS), a number of power-sensitive clients currently connected, or a number of regular clients currently connected.

17. A method, comprising:

upon receipt of a request of connection from a client, identifying, using a network device, whether the client is power-sensitive; and

if the client is identified as power-sensitive, causing the power-sensitive client to connect using a low-power connection while maintaining a regular connection to other regular clients,

wherein the low-power connection has a longer keep alive expiration period than the regular connection so that the network device does not disassociate the power-sensitive client after a regular keep alive expiration period expires.

18. The method of claim 17 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, the method further comprising:

switching, for data traffic from the power-sensitive client, the power-sensitive client from the first channel to the second channel for a duration of the traffic.

19. The method of claim 17 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, the method further comprising:

discovering whether a connected client is power-sensitive; and

shifting the connected client from the second channel to the first channel if the connected client is power-sensitive,

wherein the client is initially connected to the network device on the second channel.

20. The method of claim 17 , further comprising:

operating a first virtual access point (AP) for the low-power connection; and

operating a second virtual AP for the regular connection,

wherein the first and second APs use different service set identifiers (SSIDs).

21. The method of claim 17 , further comprising:

receiving information from the power-sensitive client so as to anticipate when there is data traffic from the power-sensitive client; and

adjusting the network circuits based on the anticipation.

22. The method of claim 17 , further comprising:

receiving information from the power-sensitive client regarding what resource the power-sensitive client needs for transmitting data traffic to the network device;

arranging a time slot based on the information; and

conveying information to the power-sensitive client regarding the time slot.

23. The method of claim 17 , further comprising:

giving priority to the power-sensitive client when there is data traffic from the power-sensitive client.

24. A network device, comprising:

control circuitry coupled to one or more wireless network circuits and configured to:

upon receipt of a request of connection from a client, identify whether the client is power-sensitive; and

if the client is identified as power-sensitive, cause the power-sensitive client to connect using a low-power connection while maintaining a regular connection to other regular clients,

wherein the low-power connection has a longer keep alive expiration period than the regular connection so that the network device does not disassociate the power-sensitive client after a regular keep alive expiration period expires.

25. The device of claim 24 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, the control circuitry further configured to:

switch, for data traffic from the power-sensitive client, the power-sensitive client from the first channel to the second channel for a duration of the traffic.

26. The device of claim 24 , wherein the low-power connection is operated on a first channel different from but in a same frequency band as a second channel on which the regular connection is operated, the control circuitry further configured to:

discover whether a connected client is power-sensitive; and

shift the connected client from the second channel to the first channel if the connected client is power-sensitive,

wherein the client is initially connected to the network device on the second channel.

27. The device of claim 24 , the control circuitry further configured to:

operate a first virtual access point (AP) for the low-power connection; and

operate a second virtual AP for the regular connection,

wherein the first and second APs use different service set identifiers (SSIDs).

28. The device of claim 24 , the control circuitry further configured to:

receive information from the power-sensitive client so as to anticipate when there is data traffic from the power-sensitive client; and

adjust the network circuits based on the anticipation.

29. The device of claim 24 , the control circuitry further configured to:

receive information from the power-sensitive client regarding what resource the power-sensitive client needs for transmitting data traffic to the network device;

arrange a time slot based on the information; and

convey information to the power-sensitive client regarding the time slot.

30. The device of claim 24 , the control circuitry further configured to:

give priority to the power-sensitive client when there is data traffic from the power-sensitive client.

31. A network device, comprising:

control circuitry coupled to one or more wireless network circuits and configured to:

upon receipt of a request of connection from a client, identify whether the client is power-sensitive; and

if the client is identified as power-sensitive, cause the power-sensitive client to connect using a low-power connection while maintaining a regular connection to other regular clients,

operate a first virtual access point (AP) for the low-power connection; and

operate a second virtual AP for the regular connection,

wherein the first and second APs use different service set identifiers (SSIDs).

32. The network device of claim 31 , wherein the control circuitry is further configured to:

switch, for data traffic from the power-sensitive client, the power-sensitive client from the first channel to the second channel for a duration of the traffic.

33. The network device of claim 31 , wherein the control circuitry is further configured to:

discover whether a connected client is power-sensitive; and

shift the connected client from the second channel to the first channel if the connected client is power-sensitive.

34. The network device of claim 31 , wherein the client is initially connected to the network device on the second channel.

35. The network device of claim 31 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client so as to anticipate when there is data traffic from the power-sensitive client; and

adjust the network circuits based on the anticipation.

36. The network device of claim 31 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client regarding what resource the power-sensitive client needs for transmitting data traffic to the network device;

arrange a time slot based on the information; and

convey information to the power-sensitive client regarding the time slot.

37. The network device of claim 31 , wherein the control circuitry is further configured to:

give priority to the power-sensitive client when there is data traffic from the power-sensitive client.

38. The network device of claim 31 , wherein the first channel is employed by a network circuit different from a second network circuit by which the second channel is employed.

39. The network device of claim 31 , further comprising:

a buffer configured to accommodate a uplink transmission rate slower than that of the regular connection from the power-sensitive client.

40. The network device of claim 31 , wherein the control circuitry is further configured to:

broadcast information about the network device's ability of low-power connection.

41. The network device of claim 31 , wherein the control circuitry is further configured to:

receive information from the power-sensitive client regarding a wake-up schedule of the power-sensitive client.

42. The network device of claim 31 , wherein the low-power connection has a relaxed connection maintenance standard relative to the regular connection, and

wherein the relaxed connection maintenance standard expects to receive keep alive messages at a frequency less than default.

43. The network device of claim 31 , wherein the low-power connection has a longer keep alive expiration period than the regular connection so that the network device does not disassociate the power-sensitive client after a regular keep alive expiration period expires.

44. The network device of claim 31 , wherein the control circuitry is further configured to:

select the first and second channels, respectively, from available channels based on one or more connection environment parameters.

45. The network device of claim 44 , wherein the connection environment parameters include one or more of: channel noise, channel cross-interference, number of overlapping basic service sets (OBSS), a number of power-sensitive clients currently connected, or a number of regular clients currently connected.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 13, 2016
From: AMINI, PEIMAN; EMMANUEL, JOSEPH AMALAN ARUL; YONGYUTH, ARMS
To: NETGEAR, INC.
Reel/Frame 040728/0310 →
Continuity (3)
Continuation 14106690 · Dec 13, 2013
Provisional Application 61888692 · Oct 9, 2013
Related Publication 20150341932A1 · Nov 26, 2015