Wireless router or residential gateway capable of distinguishing power-sensitive wireless sensors and providing separate treatment thereto
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.
1. 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 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 method of claim 1 , wherein the low-power connection is operated on a first channel different from a second channel on which the regular connection is operated.
3. The method of claim 2 , wherein the first channel is employed by a network circuit different from a second network circuit by which the second channel is employed.
4. The method of claim 2 , 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.
5. The method of claim 2 , 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.
6. The method of claim 1 , further comprising:
operating a first virtual access point (AP) for the low-power connection; and
operating a second virtual AP for the regular connection.
7. The method of claim 6 , wherein the first and second APs use different service set identifiers (SSIDs).
8. The method of claim 1 , 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.
9. The method of claim 1 , 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.
10. The method of claim 1 , further comprising:
giving priority to the power-sensitive client when there is data traffic from the power-sensitive client.
11. The method of claim 1 , further comprising:
utilizing a buffer to accommodate a uplink transmission rate slower than that of the regular connection from the power-sensitive client.
12. The method of claim 1 , further comprising:
broadcasting information about the network device's ability of low-power connection.
13. The method of claim 1 , further comprising:
receiving information from the power-sensitive client regarding a wake-up schedule of the power-sensitive client.
14. The method 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 method of claim 1 , wherein the low-power connection is operated on a first channel different from a second channel on which the regular connection is operated, and wherein the method further comprising:
selecting the first and second channels, respectively, from available channels based on one or more connection environment parameters.
16. The method 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:
operating a first virtual access point (AP) for a low-power connection;
operating a second virtual AP for a regular connection;
upon receipt of a request of connection from a client, identifying whether the client is power-sensitive; and
if the client is identified as power-sensitive, causing the power-sensitive client to connect using the low-power connection while maintaining the regular connection to other regular clients,
wherein the first and second APs use different service set identifiers (SSIDs).
18. The method of claim 17 , wherein the low-power connection is maintained on the same channel as the regular connection.
19. The method of claim 18 , wherein communication packets different than those used in the regular connection are used for the low-power connection.
20. The method of claim 19 , wherein the communication packets include beacons.
21. The method of claim 20 , wherein the communication packets further include management and control packets.
22. The method of claim 17 , further comprising:
transmitting management and control packets uniquely designated for the power-sensitive client.
23. The method of claim 17 , further comprising:
transmitting beacons uniquely designated for the power-sensitive client on a same channel as beacons for regular clients.
24. The method of claim 17 , 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 method of claim 17 , further comprising:
discovering whether a connected client is power-sensitive; and
shifting the connected client from the second virtual AP to the first virtual AP if the connected client is power-sensitive,
wherein the client is initially connected to the network device on the second virtual AP.
26. The method of claim 17 , further comprising:
switching, for data traffic from the power-sensitive client, the power-sensitive client from the first virtual AP to the second virtual AP for a duration of the traffic.
27. 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.
28. 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.
29. The method of claim 17 , further comprising:
giving priority to the power-sensitive client when there is data traffic from the power-sensitive client.
30. A method, comprising:
operating a first virtual access point (AP) for a low-power connection;
operating a second virtual AP for a regular connection;
upon receipt of a request of connection from a client, identifying whether the client is power-sensitive; and
if the client is identified as power-sensitive, causing the power-sensitive client to connect using the low-power connection while maintaining the 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.