Patent Grant
9927858
1. Technical Field
Embodiments of the invention relate to waking a sleeping computerized device, and in particular to waking a sleeping device remotely using a multicast packet.
2. Discussion of Related Art
Some computers are configured to save power by transitioning to a low power state during a period of inactivity. For example, if a user leaves a computer idle for a period of time, the computer may transition into a low-power state. The computer may transition back into a normal-power state in response to receiving user input, such as a button press or mouse movement. When the computer is in the low power state, it is said to be “asleep,” and when the computer is in a state powered for normal operation, the computer is said to be “awake.”
A problem can arise when a user wishes to remotely access a computer that is asleep. For example, a person who is at home may wish to remotely access an office computer to obtain a file stored on the office computer. If the office computer is asleep, the office computer may not be able to communicate with other computers. Since the user is remote from the office computer, the user is unable to press a button or move the mouse on the office computer to wake it up.
One prior technique for waking up a computer remotely is to program the computer's network adapter to wake up the computer upon reception of an address resolution protocol (ARP) request directed to the computer.
The Applicants have appreciated that the above-described prior technique for remotely waking up a sleeping computer over a network may lead to frequently waking up the computer unintentionally, as common network traffic, not intended to wake up a computer, may unintentionally cause the computer to wake up. Unintentionally waking up a computer can lessen the power savings achievable by setting the computer to a low power state during a period of inactivity.
One embodiment relates to waking a sleeping device using a multicast packet. A device for which it is desired to enable remote waking may be joined to a multicast group. To wake up the device, a packet may be sent to the multicast address of the multicast group, and the packet may be distributed to each of the devices in the multicast group. The packet may include an identifier for one or more particular device(s) in the multicast group, which, when received by the device(s), causes the device(s) to wake up. The other devices in the multicast group may not wake up because they may determine, based on the identifier(s) included in the packet, that the packet was not intended for them.
Another embodiment relates to least one computer readable medium having computer executable instructions stored thereon. When executed, they perform a method that may be used by a first device to change the first device from a sleeping state of the first device to an awake state of the first device. The first device may be a member of a multicast group, and may receive a multicast packet sent to at least two devices that are members of the multicast group. The first device may determine whether the multicast packet includes an identifier of the first device. If so, the first device may change from the sleeping state of the first device to the awake state of the first device.
Yet another embodiment relates to a method, for use by a second device, for changing a first device from a sleeping state of the first device to an awake state of the first device. The first device may be a member of a multicast group that includes at least two devices. The second device may receive a first packet sent to an address of the multicast group. The first packet may include an identifier of the first device. In response to receiving the first packet, a multicast packet may be sent to the at least two devices that are members of the multicast group. The multicast packet may include the identifier of the first device to indicate that the first device should be changed from the sleeping state of the first device to the awake state of the first device.
A further embodiment relates to a device that includes a processor configured to change from a sleeping state of the processor to an awake state of the processor in response to receiving a wake-up signal from a network communication module that is in communication with the processor. The device also includes a network communication module that receives a multicast packet sent to devices that are members of a multicast group. The network communication module determines whether the multicast packet includes an identifier of the first device, and if so, provides a wake-up signal to the processor.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In the drawings, each identical or nearly identical component that is illustrated in various figures is represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:
The Applicants have appreciated that the above-described prior technique for remotely waking a sleeping device may lead to a significant number of unintended device wakings caused by receiving common network traffic. These “false positives” may cause devices on a network to wake up unintentionally. The Applicants have appreciated that unintended device wakings may happen with great frequency on some networks. Unintended device wakings may lead to excess power usage and/or battery drain, and decrease the potential power savings that is achievable by having a computer go to sleep during idle periods. Some embodiments relate to techniques for remotely waking a sleeping device that may reduce the number of unintended device wakings.
One embodiment relates to remote waking of a sleeping device using a multicasting technique. A device may be joined to a multicast group that may be dedicated to waking up sleeping devices over a network. To wake up a sleeping device, the sleeping device and any other devices belonging to the same multicast group may be sent a multicast “wake-up packet” that includes information identifying the device to be woken up. In response to receiving the wake-up packet, the sleeping device may examine the identifying information in the wake-up packet and determine that the wake-up packet is intended for that device, and the sleeping device may wake up. The other devices in the multicast group that receive the multicast wake-up packet may not wake up (if they are asleep), but may discard the packet in response to determining that the wake-up packet is not intended for them.
Another embodiment, the wake-up packet may identify any number of devices to be woken up, and not just a single device. For example, a multicast wake-up packet may include identifiers for a plurality of devices, which, when received by the plurality of devices, cause them to wake up.
In yet another embodiment, every device in a multicast group may be woken up by a multicast wake-up packet. For example, multiple multicast wake-up groups may be formed (e.g., within an organization) so that the granularity of control over the number of devices woken up may be based on the number of devices in a multicast group.
In one embodiment, a user may be using device 14 (e.g., the user's home computer or any other computer), and may wish to remotely access device 2 (e.g., the user's office computer or any other computer) for any purpose (e.g., to obtain a file stored on device 2). The user may attempt to gain access to device 2 remotely via network 15 (e.g., the Internet or any other suitable network) and routers 16 and 18. However, the user may not be able to achieve the desired access (e.g., to obtain the desired file) while device 2 is asleep. In accordance with one embodiment, to wake up device 2, the user's device 14 may initiate the sending of a packet to the multicast group (e.g., at a multicast address) of which device 2 is a member. The sending can be initiated in any suitable way (e.g., the device 14 may send the packet itself, or may communicate with another device in the system which may send the packet).
Multicasting refers to a family of techniques in which a packet that is sent to a multicast address is forwarded to multiple final destination devices. For example, if devices 2, 4 and 6 are members of a multicasting group, each of devices 2, 4 and 6 may be sent a copy of packets that are sent to the address for the multicasting group. Any suitable multicasting protocol may be used (such as the Internet Group Management Protocol Multicast Listener Discovery Protocol (IGMP/MLD), for example) as the techniques described herein are not limited in this respect. In one embodiment, device 2 may be joined to a “remote wake-up” multicast group, which may be a multicast group dedicated to enabling remote waking of the devices that are members of the group. Any suitable network device may send the multicast packet to members of the multicast group, such as a router (e.g., router 16). In this embodiment, the remote wake-up multicast group includes devices 2, 4 and 6 which are members of the same subnet, however, this is merely an example and any other suitable combination of devices may join a multicast group. A device may join the multicast group in any suitable way. For example, device 2 itself may be used to join the appropriate group directly, or a system administrator may configure the multicast group to include device 2 by using any other computer.
When the user wishes to wake up device 2 (e.g., from a remote device), device 14 or any other device may initiate the sending of one or more packets to the address for the remote wake-up multicast group to which device 2 belongs. When router 16 receives the packet(s) it may multicast (e.g., send) the packet(s) to each of the devices that are members of the remote wake-up multicast group (e.g., devices 2, 4 and 6). To wake up device 2, the packet(s) initiated by device 14 and forwarded by router 16 may include an identifier for device 2. When device 2 receives the multicast packet, it may examine the contents of the multicast packet and determine that the packet was intended for device 2, upon recognition of the identifier for device 2. Any suitable identifier can be used, examples of which are discussed below. In response to determining that the packet is intended for device 2, device 2 may transition from a sleeping state to a waking state in any suitable manner (examples of which are described below). Other devices (e.g., devices 4 and 6) may also receive the multicast packet, examine its contents, and determine that the packet is not intended for them, for example, because the packet does not contain an identifier for either of devices 4 or 6, and they may discard the packet, and will not transition to a waking state (if they are asleep).
In act 31, a device (e.g., device 2) may be joined to a multicasting group to enable the device to be woken up remotely via a network connection. Any number of devices may be included as members of the multicasting group. As one example, the devices on the same subnet (e.g., devices 2, 4 and 6) that have remote waking enabled may be joined to the same multicasting group. In one aspect, the multicasting group may be dedicated to waking devices via a network connection. However the techniques described herein are not so limited, as packets sent to the address of the multicasting group may also be used for other purposes. Once a device has been joined to the multicasting group, the device may be woken up remotely by sending the device an appropriate wake-up packet.
In act 32, the device e.g., device 2) may go to sleep. As used herein, the terms “asleep,” “awake,” “sleeping,” and the like refer to the power state of the device. On average, a device and/or processor that is asleep may consume less power than a device and/or processor that is awake. A device that is asleep may have reduced functionality due to one or more components of the device having their power reduced or turned off completely. The techniques described herein are not limited as to the particular components of the device that have their power reduced or turned off while the device is asleep, as any suitable components may be powered down. In some embodiments, a network communication module 412 associated with a device may remain awake so that it is capable of receiving a wake-up packet. Network communication module 41 is discussed in further detail below with reference to
In act 33, the device (e.g., device 2) may receive a multicast wake-up packet. In response to receiving the wake-up packet, the device may examine the contents (e.g., the payload) of the packet network. For example, network communication module 412 may examine the contents of the packet, in act 34, the network communication module 412 any other suitable component) may determine whether or not the packet includes one or more identifiers for the device (e.g., device 2). If the packet includes an identifier (e.g., an IP address, MAC address and/or other identifier) for the device, the network communication module 412 may send a signal to a processor associated with the device to wake up the processor. In one embodiment, the processor may be a central processing unit (CPU) for the device, although the signal may be sent, additionally or alternatively, to any other processor, in one embodiment, the device may also check authentication information included in the packet prior to waking up the device, although authentication need not be used in embodiments.
In act 35, the device (e.g., device) may change from a state of being asleep to a state of being awake. For example, the device may include a processor that receives the wake-up signal from the network communication module 412. In response to receiving the wake-up signal, the processor may transition from a sleeping state to an awake state. The device may turn on and/or increase power to one or more components (e.g., the monitor, hard drive, etc, of the device that were previously asleep.
In one embodiment, the user's device (e.g., device 14) may attempt to communicate with the sleeping device (e.g., device 2) via network 15, if the user's device (e.g., device 14) does not receive a response from the sleeping device (e.g., device 2), the user's device may initiate sending one or more wake-up packets 20 to the multicast address to wake up the sleeping device. The user's device (e.g., device 14) may use any suitable criteria to determine when to initiate sending a wake-up packet 20. For example, the user's device may try to communicate with the sleeping device a predetermined number of times, after which the wake-up packet 20 may be sent. As another example, the user's device may wait a predetermined period of time after attempting to communicate with the sleeping device, after which the wake-up packet 20 may be sent. Any suitable software (e.g., an operating system) and/or hardware associated with device 14 may make the determination that communication with device 2 has failed and initiate the sending of wake-up packet 20. In some embodiments, the user's device (e.g., device 14) may initiate sending a wake-up packet 20 in response to receiving a user's command to do so. However, any other device or component (e.g., a network component) may detect a communication failure with the sleeping device (e.g., device 2), and any other device may send a wake-up packet, as the techniques described herein are not limited as to the device that initiates the sending of the packet or determines when communication has failed
With some multicast protocols, a router (e.g., router 16) may periodically send a query to devices in the multicast group (e.g., devices 2, 4 and 6) to determine whether at least one device is still in the group. In some embodiments, at least one device in the multicasting group may stay awake to respond to these queries so that the router continues to send multicast traffic to the group. For example, one device could be dedicated to remain awake all the time to respond. As another example, a device that is about to go to sleep may first query other devices in the multicasting group to make sure that another device is still awake to respond to the router's queries and only go to sleep if another device is awake, if not other device is awake, the device may stay awake and check back periodically until it detects that another device is awake, at which point it may go to sleep. However, any suitable technique may be used to ensure that the router (e.g., router 16) that forwards the multicast traffic continues to do so.
With reference to
Device 400 may include at least some form of computer readable media. By way of example, and not limitation, computer readable media may comprise computer storage media. For example, device 400 rimy also include storage removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in
Device 400 may also have input device(s) 414 such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 416 such as a display, speakers, printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here.
It should be appreciated that the techniques described herein are not limited to executing on any particular system or group of systems. For example, embodiments may run on one device or on a combination of devices. Also, it should be appreciated that the techniques described herein are not limited to any particular architecture, network, or communication protocol.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This techniques described herein are not limited in their application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The techniques described herein are capable of other embodiments and of being practiced or of being carried out in various ways. Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having,” “containing,” “involving,” and variations thereof herein, is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
This Application is a Continuation of, and claims benefit from, U.S. patent application Ser. No. 11/653,681 that was filed on Jan. 16, 2007, and that is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5742833 | Dea | Apr 1998 | A |
| 5826015 | Schmidt | Oct 1998 | A |
| 5884323 | Hawkins | Mar 1999 | A |
| 5973613 | Reis | Oct 1999 | A |
| 6003084 | Green et al. | Dec 1999 | A |
| 6047378 | Garrett | Apr 2000 | A |
| 6049885 | Gibson | Apr 2000 | A |
| 6052779 | Jackson et al. | Apr 2000 | A |
| 6101608 | Schmidt | Aug 2000 | A |
| 6272190 | Campana, Jr. | Aug 2001 | B1 |
| 6292508 | Hong | Sep 2001 | B1 |
| 6339792 | Allison | Jan 2002 | B1 |
| 6526507 | Cromer | Feb 2003 | B1 |
| 6591368 | Ryu | Jul 2003 | B1 |
| 6606709 | Connery et al. | Aug 2003 | B1 |
| 6697383 | Li | Feb 2004 | B1 |
| 6745240 | Denman | Jun 2004 | B1 |
| 6795450 | Mills | Sep 2004 | B1 |
| 6915346 | Kato et al. | Jul 2005 | B1 |
| 6938040 | Allison | Aug 2005 | B2 |
| 6993670 | Weng et al. | Jan 2006 | B2 |
| 7047428 | Bui | May 2006 | B2 |
| 7324518 | Dai | Jan 2008 | B2 |
| 7779451 | Eldar | Aug 2010 | B2 |
| 9319225 | Garg | Apr 2016 | B2 |
| 20020077995 | Allison | Jun 2002 | A1 |
| 20020194498 | Blight | Dec 2002 | A1 |
| 20030026240 | Eyuboglu | Feb 2003 | A1 |
| 20030109972 | Tak | Jun 2003 | A1 |
| 20030206564 | Mills | Nov 2003 | A1 |
| 20030235168 | Sharma et al. | Dec 2003 | A1 |
| 20040101046 | Yang | May 2004 | A1 |
| 20040158872 | Kobayashi | Aug 2004 | A1 |
| 20040246961 | Dai | Dec 2004 | A1 |
| 20040259574 | Daniels | Dec 2004 | A1 |
| 20050005026 | Brown et al. | Jan 2005 | A1 |
| 20050086460 | Huang | Apr 2005 | A1 |
| 20050091331 | Brown | Apr 2005 | A1 |
| 20050108407 | Johnson et al. | May 2005 | A1 |
| 20050135334 | Rajkotia | Jun 2005 | A1 |
| 20050143056 | Iyer | Jun 2005 | A1 |
| 20050144493 | Cromer | Jun 2005 | A1 |
| 20050166213 | Cromer | Jul 2005 | A1 |
| 20050181815 | Shostak | Aug 2005 | A1 |
| 20050220063 | Hong | Oct 2005 | A1 |
| 20050223248 | Lim | Oct 2005 | A1 |
| 20050233735 | Karaoguz | Oct 2005 | A1 |
| 20050254444 | Meier et al. | Nov 2005 | A1 |
| 20050276237 | Segal | Dec 2005 | A1 |
| 20060034318 | Fernandes | Feb 2006 | A1 |
| 20060036678 | Rhim | Feb 2006 | A1 |
| 20060039373 | Nakamura | Feb 2006 | A1 |
| 20060188864 | Shah | Aug 2006 | A1 |
| 20060209751 | Hsu | Sep 2006 | A1 |
| 20070050645 | Siegmund | Mar 2007 | A1 |
| 20070067445 | Vugenfirer | Mar 2007 | A1 |
| 20070115827 | Boehnke | May 2007 | A1 |
| 20070130289 | Defazio | Jun 2007 | A1 |
| 20070211725 | Kawata et al. | Sep 2007 | A1 |
| 20070230441 | Sethi | Oct 2007 | A1 |
| 20070234401 | Eldar | Oct 2007 | A1 |
| 20080089338 | Campbell | Apr 2008 | A1 |
| 20080101445 | Ho | May 2008 | A1 |
| 20080137591 | Hirano | Jun 2008 | A1 |
| 20080160017 | Baker | Jul 2008 | A1 |
| 20100158000 | Muramoto | Jun 2010 | A1 |
| 20150095680 | Gossain | Apr 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 20050005026 | Jan 2005 | KR |
| Entry |
|---|
| Lieberman Software Corporation, White Paper: Wake on LAN Technology, 9 pages, Revision 2, Jun. 1, 2006. http://www.lanicu.com/whitepapers/pdf_files/Wake_On_LAN.pdf. |
| L. F. Polio and I. Jansch-Porto, A Network-Oriented Power Management Architecture, pp. 693-706, In Proceedings of the IFIP/IEEE Eighth International Symposium on Integrated Network Management, Mar. 24-28, 2003. |
| OvisLink, Corp., “Wake-On-LAN PCI Fast Ethernet Adapter”, 2 pages, as archived on web.archive.org on Sep. 10, 2006. |
| Windows Hardware Developer Central, Network Device Class: Version 2.0 Oct. 12, 2000, 7 pages, http://www.microsoft.com/whdc/resources/respec/specs/pmref/PMnetwork.mspx Uploaded Dec. 4, 2001. |
| U.S. Appl. No. 11/653,681, filed Jan. 16, 2007, Garg. |
| U.S. Appl. No. 15/062,108, filed Mar. 5, 2016, Garg. |
| “Final Office Action Issued in U.S. Appl. No. 15/062,108”, dated Oct. 26, 2017, 19 Pages. |
| “Non Final Office Action Issued in U.S. Appl. No. 15/062,108”, dated Jan. 10, 2018, 21 Pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160182243 A1 | Jun 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11653681 | Jan 2007 | US |
| Child | 15057119 | US |
