A first wireless device determines, while a first and second wireless transceiver are powered off, start of a service period. The first wireless transceiver is turned on in response to the determination to enable the first wireless device to establish communication via a LP wireless channel while the second wireless transceiver is off. The first wireless device receives a request frame from a second wireless device and a time of a timing function is updated based on the request frame.
|
1. A method comprising:
determining, by a first wireless device and while a first and second wireless transceiver are powered off, start of a service period (SP) interval based on a timing function;
turning on the first wireless transceiver in response to the determination of the start of the service period to enable the first wireless device to establish communication with a second wireless device via a low power (LP) wireless channel while the second wireless transceiver is powered off;
receiving, by the first wireless device, a request frame from the second wireless device; and
updating a time of the timing function based on the request frame.
19. An apparatus comprising:
a first wireless transceiver;
a second wireless transceiver;
circuitry configured to:
determine, by a first wireless device and while the first and the second wireless transceiver are powered off, start of a service period (SP) interval based on a timing function;
turn on the first wireless transceiver in response to the determination of the start of the service period to enable the first wireless device to establish communication with a second wireless device via a low power (LP) wireless channel while the second wireless transceiver is powered off;
receive, by the first wireless device, a request frame from the second wireless device; and
update a time of the timing function based on a time in a timing function time field of the request frame.
12. Apparatus comprising:
a local timing function;
a processor;
memory;
program code stored in the memory and executable by the processor to perform one or more functions which include:
based on the local timing function, determining start of a service period (SP) interval at a wireless device, wherein the wireless device powers on a first wireless transceiver of the wireless device in response to the start of the service period interval to enable the wireless device to establish communication with the apparatus via a low power (LP) wireless channel while a second wireless transceiver of the wireless device is powered off; and
sending a request frame to the wireless device to cause the wireless device to update a time of a remote timing function associated with the wireless device based on the request frame.
3. The method of
4. The method of
5. The method of
6. The method of
based on the difference being greater than one half of the maximum time, determining whether the time in the timing function time field is less than or greater than the least significant portion and respectively incrementing or decrementing most significant bits of the time of the timing function; and
replacing the least significant portion with the time in the timing function time field.
7. The method of
8. The method of
recording a first time when the request frame is received based on the first timing function;
turning on the second wireless transceiver in response to receiving the request frame, wherein turning on the second wireless transceiver enables the first wireless device to receive an additional frame from the second wireless device;
receiving, by the second wireless transceiver, the additional frame, wherein the additional frame defines a second time when the request frame was sent based on a second timing function associated with the second wireless device; and
adjusting the time of the first timing function based on a difference between the first time and the second time.
9. The method of
10. The method of
11. The method of
14. The apparatus of
15. The apparatus of
16. The apparatus of
17. The apparatus of
determine whether a difference between the least significant portion and the time in the timing function time field is greater than or less than one half of a maximum time represented by the timing function time field;
based on the difference being greater than one half of the maximum time, determine whether the time in the timing function time field is less than or greater than the least significant portion and respectively incrementing or decrementing most significant bits of the time of the remote timing function; and
replace the least significant portion with the time in the timing function time field.
18. The apparatus of
20. The apparatus of
|
This disclosure claims the benefit of priority of U.S. Provisional Application Ser. No. 62/505,426 filed May 12, 2017, entitled, “LOW POWER WAKEUP RADIO (WUR) SYNCHRONIZATION” and U.S. Provisional Application Ser. No. 62/635,407 filed Feb. 26, 2018, entitled, “TIMING SYNCHRONIZATION FUNCTION (TSF) TIME IN LOW POWER SYNC”, the contents each of which is incorporated herein by reference in its entirety.
This disclosure relates to wireless networking systems and techniques, namely employing low-power (LP) antennas to implement frame exchange between wireless devices, such as wireless stations (STAs) and access points (APs). The techniques disclosed within this disclosure can also be used in wireless networks that employ long-range low-power (LRLP) wireless communication technologies mentioned herein.
Wireless communication, particularly wireless local area network (WLAN) technology, has become ubiquitous in the mobile computing environment. Some existing wireless networking standards, for example, WiFi protocol IEEE (Institute of Electrical and Electronics Engineers) 802.11 can be used to provide close-proximity wireless connectivity between wireless devices. As an example, WiFi routers operating on a traditional 2.4 GHz band can reach up to 150 feet (46 m) indoors and 300 feet (92 m) outdoors. Newer long range low power (LRLP) wireless networking technologies, such as IEEE 802.11ah, have also been developed to operate at longer ranges and lower power. These LRLP wireless technologies extend the communication range of legacy IEEE 802.11 wireless technologies, for example, by approximately 10 dB and distance by approximately 500 m and have comparatively lower device power consumption.
This disclosure relates to wireless networking systems and techniques, namely timing synchronization between wireless devices, such as STAs and APs in wireless networks that employ LRLP wireless communication technologies mentioned herein.
According to an aspect of the described system and techniques, a method comprises determining, by a first wireless device and while a first and second wireless transceiver are powered off, start of a service period (SP) interval based on a timing function; turning on the first wireless transceiver in response to the determination of the start of the service period to enable the first wireless device to establish communication with a second wireless device via a low power (LP) wireless channel while the second wireless transceiver is powered off; receiving, by the first wireless device, a request frame from the second wireless device; and updating a time of the timing function based on the request frame.
According to an aspect of the described system and techniques, an apparatus comprises: a local timing function; a processor; memory; program code stored in the memory and executable by the processor to perform one or more functions which include: based on the local timing function, determining start of a service period (SP) interval at a wireless device, wherein the wireless device powers on a first wireless transceiver of the wireless device in response to the start of the service period interval to enable the wireless device to establish communication with the apparatus via a low power (LP) wireless channel while a second wireless transceiver of the wireless device is powered off; sending a request frame to the wireless device to cause the wireless device to update a time of a remote timing function associated with the wireless device based on the request frame.
According to yet another aspect of the described system and techniques, an apparatus comprises a first wireless transceiver; a second wireless transceiver; circuitry configured to: determine, by a first wireless device and while a first and second wireless transceiver are powered off, start of a service period (SP) interval based on a timing function; turn on the first wireless transceiver in response to the determination of the start of the service period to enable the first wireless device to establish communication with a second wireless device via a low power (LP) wireless channel while the second wireless transceiver is powered off; receive, by the first wireless device, a request frame from the second wireless device; and update a time of the timing function based on a time in a timing function time field of the request frame.
In this regard, mechanisms are provided for maintaining synchronization of timing synchronization functions (TSF) associated with an STA and AP that indicate when a transceiver of the STA is powered off to save power.
Like reference symbols in the various drawings indicate like elements.
This disclosure provides examples and details for synchronizing timing between wireless devices such as wireless stations (STAs) and access points (APs) employing low-power (LP) antennas.
The wireless communication system 100 includes a wireless network 102 such as a WLAN and one or more wireless devices. The wireless devices may take the form a wireless station (STA) 106 and access point (AP) 108.
The STA 106 and AP 108 may be configured to include two distinct wireless antennas: a high power wireless antenna 110 usable for wireless communications 114 at standard legacy 802.11 WiFi network frequencies (e.g., 2.4 GHz and 5 GHz frequencies); and a LP antenna 112 using LRLP networking technologies to establish wireless communication 114 at low power. As an example, a LP antenna 112 utilizes low power wireless communication channels to operate at frequencies associated with LRLP network capabilities (e.g., 900 MHz). In some implementations, the LP antenna 112 is also capable of supporting communication using legacy 802.11 WiFi network frequencies, for example, in an additional mode of operation. The antennas 110, 112 are used to communicate between the wireless devices, such as STA and AP and other components of the wireless communication system 100. The high power antenna 110 and LP antenna 112 are illustrated as separate antennas, but in some examples, the high power antenna 110 and LP antenna 112 may be a same antenna.
AP 108 can be connected to additional network devices, such as routers and modems, for example, to further connect wireless devices to a wide area network (WAN), such as the Internet. The AP 108 can be employed to register STAs, such as STA 106, thereby allowing the wireless devices to receive wireless communication services. The wireless communication system 100 can includes multiple STAs and APs. In some implementations, AP 108 implements direct communications between the STA, such as point-to-point communication, where a channel is allocated for the devices to communicate directly. Likewise, the STAs, such as STA 106 can also implement direct communications with one or more other wireless communication devices and/or the AP 108.
The STA 106 includes circuitry that can be understood in three main parts: 802.11 transceiver electronics 116 (also referred to herein as a “802.11 radio” or “0.11” radio) to send and receive wireless signals over one or more 802.11 (e.g., high power) antennas 110; low power transceiver electronics 118 (also referred to herein as an “LP radio” which can be compliant with 802.11 but operates at a lower power) to send and receive wireless signals over one or more LP antennas 112, and processor electronics 120 to effect the wireless communications using the 802.11 transceiver electronics 116 and low power transceiver electronics 118. The STA 106 communicates with the AP 108 via its LP antenna 112 and 802.11 antenna 110. In this regard, the AP 108 may have also similar electronics (not shown) for enabling the LP antenna 112 and 802.11 antenna 110 on the AP 108 to transmit and/or receive wireless signals.
The LP transceiver electronics 118 enable transmission and/or reception of wireless signals via low power wireless communication channels using LPLR protocols such as IEEE 802.11ah. Similarly, the 802.11 transceiver electronics 116 enable transmission and/or reception of wireless signals via legacy 802.11 WiFi communication channels. The processor electronics 120 can include one or more processors, such as a digital baseband processor and one or more additional dedicated processing units (e.g., a power management unit and audio codec) to coordinate operation of the 802.11 transceiver electronics 116 and low power transceiver electronics 118. As an example, the processor electronics 120 can include a Digital Signal Processor (DSP), a MicroController Unit (MCU), at least one memory device, or any combination thereof.
The STA 106 may turn off (e.g., power off) its the 802.11 transceiver electronics 116 and LP transceiver electronics 118 to save power based on one or more timers associated with the STA 106. Each of the one or more timers may be a clock which counts in increments/decrements based on a clocking mechanism. The one or more timers are used to track when the 802.11 transceiver electronics 116 and LP transceiver electronics 118 are powered on or turned on (e.g., capable of transmitting and/or receiving signals via the low power antenna 112 and/or 802.11 antenna 110) or powered off or turned off (e.g., not capable of transmitting and/or receiving signals via the low power antenna 112 and/or 802.11 antenna 110). The one or more timers may take the form of a timing synchronization function (TSF) defined by 802.11 (also referred to as timing function). The STA 106 may have a TSF 122. The TSF 122 may take the form of two separate TSFs, one for keeping track of when the 802.11 transceiver 116 is on or off (referred to as an 0.11 TSF) and one for keeping track of when the LP transceiver electronics 118 is on and off (referred to as an LP TSF). The 0.11 TSF may be 8 octets with 1 microsecond of granularity while the LP TSF may be 6 or 8 octets with 1 or 4 microseconds of granularity. The AP 108 may also maintain a TSF 124. The TSF 124 may take the form of a 0.11 TSF and LP TSF with same octet and granularity which is synchronized to the corresponding 0.11 TSF and LP TSF on the STA.
The TSF 122, 124 associated with the AP 108 and STA 106 may be further synchronized. LP timing synchronization frames 124 as discussed in further detail below are exchanged between the AP 108 and STA 106 to facilitate this synchronization so that both the AP 108 and STA 106 know when the other's 802.11 transceiver electronics 116 and LP transceiver electronics 118 are on and off so that wireless signals can be transmitted and received via the wireless network 102.
A TSF 204, i.e., LP TSF, associated with the STA may indicate a start time 206 of the SP duration 202 and an end time 208 of the SP duration 202. Based on the start time 206 of the SP duration 202, the STA may turn on the LP radio while the 802.11 radio is off. Then, when the LP TSF associated with the STA indicates the end time 208 of the SP duration 202, the STA may turn off the LP radio and 802.11 radio to save power. This process may be repeated for a plurality of SP intervals 200. In this regard, the LP TSF 204 may also indicate one or more of the start/end times 206, 208 of the plurality of SP intervals 200 similar to how the start/end of the SP duration 202 is indicated.
The one or more parameters associated with when the 0.11 radio and/or LP radio is on or off may be negotiated between the AP and STA. For example, the SP interval 200, SP duration 202, and start time 206 of the SP duration may be negotiated between the AP and STA. The negotiation may be a frame exchange via the 802.11 radio, e.g., using an 802.11 management frame. Alternatively, the parameters may be announced by the AP to the STA via the 802.11 radio. The announcement may be included in legacy 802.11 frames such as beacons transmitted by the AP, probes transmitted by the AP, or an association process between the AP and STA. The announcement may be broadcast to a plurality of STAs which are to use the same SP interval 200 and/or SP duration 202 for communication over the LP wireless channel or unicast to a specific STA.
Further, the LP TSF associated with the STA and AP may be synchronized. The AP may transmit to the STA an announcement, i.e., frame, with the LP TSF time at the AP via the LP radio. Additionally, or alternatively, the AP may transmit to the STA an announcement, i.e., frame, with the LP TSF time at the AP via the 802.11 radio. The STA may adjust its LP TSF time to be synchronized to that of the AP based on the LP TSF time indicated in the announcement. For example, the STA may replace the LP TSF time of the LP TSF at the STA with the LP TSF time indicated in the announcement. Alternatively, LP TSF time may be announced in terms of a 0.11 TSF time and difference between the LP TSF time and 0.11 TSF time at the AP. The STA may calculate the LP TSF time at the AP based on the announcement and adjust its LP TSF time to be synchronized to that of the AP based on the announcement. The STA may then turn on and off its 0.11 radio and/or LP radio in accordance with the LP TSF and negotiated SP interval 200, SP duration 202, and/or start time 206. The AP will then communicate with the STA via the LP radio when it determines that the LP radio at the STA is on based on its synchronized LP TSF.
The time indicated by the LP TSF at the AP and STA may drift over time and no longer be synchronized with each other after the initial synchronization. The times may not be synchronized when the LP TSF time at the AP is not indicative of the LP TSF time at the STA (there is an unknown difference in time). This may be due to temperature change, clock quality, stability of a power source, etc. To resynchronize the LP TSFs, the AP may trigger a resynchronization so that the LP TSF time at the AP and STA are synchronized again.
In some examples, the STA may turn on its LP radio for reasons other than based on the start of the SP duration. Subsequent processing is not limited by the means by which the LP radio is turned on.
While the LP radio is on, the AP can transmit via its LP radio and the STA can receive via its LP radio a low power trigger. The AP may know that the STA has turned on its LP radio based on the LP TSF at the AP indicating the start of the SP duration, i.e., start of the SP duration may be detected by the AP when the current time on the LP TSF at the AP also matches the start time. The AP is configured to transmit the low power trigger using its LP antenna during the time that the LP radio on the STA is on to communicate with the STA, for example to transmit data frames and perform TSF synchronization. The low power trigger may take the form of an LP wakeup frame sent by the AP to the STA while the LP radio of the STA is on. The LP wakeup frame may indicate the LP TSF time at AP when the LP wakeup frame was sent. In some examples, the LP wakeup frame may be sent periodically by the AP based on a negotiation between the AP and STA. The negotiation may be a frame exchange via the 802.11 radio.
Referring back to
The low power trigger may also cause activation, or powering on, of the 802.11 radio by the STA to allow the AP to transmit frames to the STA via the 802.11 radio. The frames may include an announcement frame such as an 802.11 Action frame which contains the LP TSF time at the AP. The LP TSF time may be announced as the LP TSF time at the AP or as the 0.11 TSF time and a difference between the LP TSF time and 0.11 TSF time at the AP, among others. The STA may also receive this frame via its 802.11 radio and adjust its LP TSF time based on the LP TSF time in the frame.
Referring back, at 506, the STA 106 receives the LP wakeup frame via the LP radio. At 508, the STA 106 may record the LP TSF time at the STA when the LP wakeup frame is received. At 510, the STA 106 turns on its 802.11 radio based on the received LP wakeup frame. At 512, the STA 106 receives an announcement frame via its 802.11 radio. The announcement frame may be unicast if the LP wakeup frame is unicast and broadcast if the LP wakeup frame is broadcast. The announcement frame may indicate a token and an LP TSF time. The token may be copied over from the LP wakeup frame. In this regard, the token in the LP wakeup frame matches a token in the announcement frame to indicate that the LP wakeup frame is related to the announcement frame. Alternatively, the token in the announcement frame does not match that in the LP wakeup frame but the token in the announcement frame is deterministically related to the token in the LP wakeup frame. In either case, it can be confirmed that the announcement frame is associated with the LP wakeup frame and if the token in the announcement frame is not related to the token in the LP wakeup frame, the announcement frame is ignored.
At 514, the STA 106 adjusts its LP TSF time based on a difference calculated between the LP TSF time indicated in the announcement frame and the LP TSF time recorded when the LP wakeup frame was received. When a next LP wakeup frame is sent, the token in the LP wakeup frame and corresponding announcement frame may be adjusted, e.g., incremented or decremented. This way the STA may not record a TSF time for an LP wakeup frame with one token value and use announcement frame with another token value in updating the LP TSF time.
Ratio=(AP TSF2−AP TSF1)/(STA TSF2−STA TSF 1)
Then, an increment of the timer associated with the LP TSF is adjusted by the ratio rather the adjustment to actual LP TSF time described above. For example, instead of the timer being incremented by 1 each clock cycle, the timer may be incremented by 1*CFO to resynchronize the LP TSF at the STA with that of the AP.
The LP wakeup frame may be transmitted periodically. In some cases, the STA may lose synchronization with the AP such that it does not receive an LP wakeup frame in one or more SP durations. The STA may maintain a count of a number of SP durations where the STA does not receive the LP wakeup frame. The reason that the STA may not receive the LP wakeup frame may be that the LP TSF time at the STA may not be synchronized with LP TSF time at the AP such that the LP radio at the STA may be on, but the AP may think it is off and/or the LP radio at the STA may be off, but the AP may think it is on and send the LP wakeup frame. In either case, a LP wireless channel cannot be established between the AP and STA. In this situation, when the LP radio is already on, the STA may power on its 802.11 radio and send a resynchronization request to the AP via the 802.11 radio. The AP will then responsively send an LP wakeup frame with the TSF time and/or an announcement of the LP TSF time associated with the AP. The STA may adjust its LP TSF to resynchronize with the LP TSF associated with the AP.
In some examples, the STA may maintain a single TSF such as a 0.11 TSF rather than a separate 0.11 TSF and LP TSF. The 0.11 TSF may be used to keep track of when the 802.11 transceiver 116 and LP transceiver 118 is to be on and off. The STA may not have a separate LP TSF. The SP interval, start time, and SP duration may be negotiated and/or based on the 0.11 TSF time using the 0.11 radio. Further, the 0.11 TSF at the AP and STA would need to be synchronized in a manner similar to how the LP TSF is synchronized. The process for synchronization is the same as described above, but instead a 0.11 TSF time is used to synchronize a 0.11 TSF rather than a LP TSF time used to synchronize a LP TSF.
To illustrate, the AP may send an announcement of the 0.11 TSF time (rather than announcement of an LP TSF time) to the STA to achieve synchronization of the 0.11 TSF at the STA and AP. Additionally, or alternatively, the AP may insert an 0.11 TSF time rather than a LP TSF time in the LP wakeup frame in
In some examples, a sync frame such as the LP wakeup request frame, announcement frame, or any other frame which carries a TSF time, may have a partial TSF time. The partial TSF time may a portion of the bits of the TSF at the AP. For example, the TSF time may be 64 bits but the TSF time included in the LP wakeup request frame show in
The synchronization process may begin at 902 with the STA 106 receiving a sync frame. The sync frame may have a partial TSF time of least significant bits (LSB) of the TSF time associated with the AP. For example, the partial TSF time may be 12 bits which correspond to [0:11] of the STA TSF. At 904, a determination is made by the STA 106 whether a difference between the least significant bits TSF time associated with the STA TSF (e.g., [0:11]) and the partial TSF time (e.g., 12 bits) is greater than ½ of a maximum partial TSF time, e.g., the most significant bit of the TSF time of the least significant bits TSF time and the partial TSF time are different. For example, a partial TSF time may be 12 bits and ½ the maximum partial TSF time may be ½*212=211. If the difference between the least significant 12 bit TSF time associated with the STA and the 12 bit partial TSF time is less than/equal to ½ of a maximum partial TSF time, then at 904, the most significant 52 bits of the TSF associated with the STA TSF (e.g., [12:63]) is not changed and processing proceeds to 908 described below. If the difference between the least significant bits TSF time associated with the STA (e.g., [0:11]) and the partial TSF time is greater than ½ of a maximum partial TSF time, then at 906, a determination is made by the STA 106 whether the partial TSF is less than, greater than, or equal to the least significant bits of the TSF time associated with the STA (e.g., [0:11]). If the partial TSF is less than the least significant bits of the TSF time associated with the STA (e.g., [0:11]), then at 912 the most significant bits of the TSF time associated with the STA TSF (e.g., [12:63]) may be increased by one by the STA 106. If the partial TSF is greater than the least significant bits of the TSF time associated with the STA (e.g., [0:11]), then at 910 the most significant bits of the TSF time associated with the STA TSF (e.g., [12:63]) may be decreased by one by the STA 106. If the partial TSF is equal to the least significant bits of the TSF time associated with the STA (e.g., [0:11]), then the most significant bits of TSF time are not changed. At 908, the partial TSF time is copied into the LSB of the TSF associated with the STA TSF [0:11] by the STA 106. In this manner, the TSF associated with the AP and STA are synchronized when the TSF associated with the STA drift by more than half of a maximum partial TSF time. Any drift less than this amount will be accounted for when the partial TSF time is copied into the LSB of the TSF associated with the STA at 908 without further change to the MSBs of the TSF associated with the STA.
To illustrate application of the functions 900, suppose the interval between two low power wakeup request frames is 1 ms. Further, assume that the STA's clock is faster, i.e. if AP TSF time is increased by 1 ms, STA TSF time is increased by 1 ms+50 us. After STA sets its TSF time per the received (n−1) th low power wakeup request frame, both AP and STA TSF time have the same value with TSF[12:63]=0x123456789ABCD and TSF[0:11]=0xDF8. When transmitting nth low power wakeup request frame after 1 ms, AP TSF time's MSB 52 bits and LSB 12 bits are TSF[12:63]=0x123456789ABCD, TSF[0:11]=0xFF8. Right before receiving the nth low power wakeup request frame, STA's TSF time's MSB 52 bits and LSB 12 bits are TSF[12:63]=0x123456789ABCE, TSF[0:11]=0x012 which is 50 us faster than the AP TSF time. After the reception of nth low power wakeup request frame, the STA TSF time's MSB 52 bits and LSB 12 bits should be TSF[12:63]=0x123456789ABCD, TSF[0:11]=0xFF8. This is the example that STA's TSF [12:63] is decreased by 1 when the partial TSF time [0:11] is copied into the TSF associated with the STA.
If the partial TSF takes the form of bits 4:15 of the TSF time of the AP rather than bits [0:11] of the TSF time of the AP, then the most significant bits of the TSF time associated with the STA will be TSF[16:63] instead of TSF[12:63] in the functions 900. Further, the least significant bits of the TSF time associated with the STA may be TSF[0:15] and the max partial TSF time will be ½ of 216 or 215 in the functions 900. The partial TSF may take other bit lengths as well or groups of bits within the TSF time. Further, if the time drift indicated by the partial TSF time in successive sync frames is greater than ½ the maximum partial TSF time, then the AP may send an 802.11 beacon or probe request via the 802.11 radio with a full TSF time rather than a partial TSF time. For example, if a most significant bit of successive sync frames changes from a 0 to 1 or 1 to 0, then the AP may send an 802.11 beacon or probe request via the 802.11 radio with a full TSF time for updating the TSF. The full TSF time may be 64 bits. Other variations are also possible.
A few implementations have been described in detail above, and various modifications are possible. For example, functions performed at the STA described above may also be additionally or alternatively performed at the AP. The disclosed subject matter, including the functional operations described in this specification, can be implemented in electronic circuitry, computer hardware, firmware, software, or in combinations of them, such as the structural means disclosed in this specification and structural equivalents thereof: including potentially a program operable to cause one or more data processing apparatus to perform the operations described (such as a program encoded in a non-transitory computer-readable medium, which can be a memory device, a storage device, a machine-readable storage substrate, or other physical, machine readable medium, or a combination of one or more of them).
A program (also known as a computer program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
While this specification contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations.
Other implementations fall within the scope of the following claims.
Lou, Hui-Ling, Zhang, Hongyuan, Chu, Liwen
Patent | Priority | Assignee | Title |
10912024, | Dec 29 2017 | Intel Corporation | Apparatus, system and method of a wake-up radio (WUR) |
11051260, | Jan 07 2019 | Motorola Mobility LLC | Asynchronous quick connect for low-latency transitions of content presentation between two devices |
11184845, | Dec 29 2017 | Intel Corporation | Apparatus, system and method of a wake-up radio (WUR) |
Patent | Priority | Assignee | Title |
7546149, | Mar 08 2005 | Google Technology Holdings LLC | Deep sleep mode for portable communication device |
20140314068, | |||
20150245282, | |||
20180020410, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 04 2018 | ZHANG, HONGYUAN | MARVELL SEMICONDUCTOR, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 045902 | /0068 | |
May 11 2018 | Marvell International Ltd. | (assignment on the face of the patent) | / | |||
May 17 2018 | CHU, LIWEN | MARVELL SEMICONDUCTOR, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 045902 | /0068 | |
May 17 2018 | LOU, HUI-LING | MARVELL SEMICONDUCTOR, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 045902 | /0068 | |
May 23 2018 | MARVELL SEMICONDUCTOR, INC | MARVELL INTERNATIONAL LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 045902 | /0087 | |
Dec 31 2019 | MARVELL INTERNATIONAL LTD | CAVIUM INTERNATIONAL | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 052918 | /0001 | |
Dec 31 2019 | CAVIUM INTERNATIONAL | MARVELL ASIA PTE, LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 053475 | /0001 |
Date | Maintenance Fee Events |
May 11 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
Jul 25 2023 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Feb 04 2023 | 4 years fee payment window open |
Aug 04 2023 | 6 months grace period start (w surcharge) |
Feb 04 2024 | patent expiry (for year 4) |
Feb 04 2026 | 2 years to revive unintentionally abandoned end. (for year 4) |
Feb 04 2027 | 8 years fee payment window open |
Aug 04 2027 | 6 months grace period start (w surcharge) |
Feb 04 2028 | patent expiry (for year 8) |
Feb 04 2030 | 2 years to revive unintentionally abandoned end. (for year 8) |
Feb 04 2031 | 12 years fee payment window open |
Aug 04 2031 | 6 months grace period start (w surcharge) |
Feb 04 2032 | patent expiry (for year 12) |
Feb 04 2034 | 2 years to revive unintentionally abandoned end. (for year 12) |