Time synchronization for delay-sensitive traffic over wireless network
By adopting an enhanced synchronization mode in wireless communication systems, the problem that it is difficult to meet the low-latency application requirements when synchronizing between STA and AP in a multi-link environment is solved. By frequently sending synchronization frames to indicate TSF offset, we ensure that STA and AP are The timing synchronization avoids unintentional access or interference, and improves the reliability of the communication link and the performance of delay-sensitive services.
Patent Information
- Application Number
- CN202380031395.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-11
- Filing Date
- 2023-03-06
- Publication Date
- 2024-11-29
AI Technical Summary
Existing wireless communication systems are difficult to meet the strict delay, throughput and timing requirements of low-latency applications when maintaining synchronization between STA and AP, especially in multi-link environments, the impact of TSF offset due to clock drift. The accuracy of the r-TWT SP results in the STA that may unintentionally access or interfere with the communication link.
Using enhanced synchronization mode, synchronization frames are sent more frequently on the communication link associated with the AP than TBTT, indicating the TSF offset between the AP and the STA to ensure timing synchronization between the STA and the AP and avoid unintentional connections. Incoming or interference, combining TWT SP or r-TWT SP to establish synchronization, rejecting association requests from STAs that do not support enhanced synchronization mode.
Improves synchronization accuracy between STA and AP, ensures that STA terminates TXOP before the start time of r-TWT SP, avoids unintentional access or interference, and improves the reliability of delay-sensitive services and predictability of communication links. .
Smart Images

Figure CN119054358A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. patent application No. 17 / 717,791, filed by NAIK et al. on April 11, 2022, and entitled “TIME SYNCHRONIZATION OVER A WIRELESS NETWORK FOR LATENCY-SENSITIVE TRAFFIC,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to wireless communications, and more particularly to maintaining synchronization between a wireless station (STA) and each of a plurality of access points (APs) of a device. Background Art
[0004] A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless medium for use by several client devices, such as wireless stations (STAs). The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID), which is announced by the AP in beacon frames that are periodically broadcast over the wireless medium, so that STAs within the wireless range of the AP can associate with the AP and establish a wireless communication link with the WLAN.
[0005] Some wireless communication devices may be associated with low-latency applications that have strict end-to-end latency, throughput, and timing requirements for data traffic. Example low-latency applications include, but are not limited to, real-time gaming applications, video communications, and augmented reality (AR) and virtual reality (VR) applications (collectively referred to as extended reality (XR) applications). Such low-latency applications may specify various latency, throughput, and timing requirements for wireless communication systems that provide connectivity for these applications. Therefore, it is desirable to ensure that WLANs can meet the various latency, throughput, and timing requirements of such low-latency applications. Summary of the invention
[0006] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0007] An innovative aspect of the subject matter described in the present disclosure may be implemented in a wireless device. The wireless device may include at least one processor and at least one memory communicatively coupled to the at least one processor. In some specific implementations, the memory stores processor-readable code, which is configured to send an indication of an enhanced synchronization mode to at least one wireless station (STA) on a first communication link associated with a first access point (AP) of the device when executed by at least one processor. The execution of the processor-readable code is configured to send multiple synchronization frames more frequently than a target beacon transmission time (TBTT) associated with the first communication link on the first communication link during the enhanced synchronization mode, and each of the multiple synchronization frames indicates a timing synchronization function (TSF) offset between the first AP and the second AP of the device. In some aspects, each of the multiple synchronization frames may also indicate a TSF value of the first AP. In some instances, the indication may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake-up time (TWT) response frame sent on the first communication link.
[0008] In various specific implementations, the device may be an AP multi-link device (MLD) including a first AP and a second AP, the first AP being associated with a first communication link, the second AP being associated with a second communication link, the second communication link occupying a frequency band different from the first communication link. In some specific implementations, the enhanced synchronization mode may be established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link. In some instances, at least one of the multiple synchronization frames may be a fast initial link establishment (FILS) discovery frame carrying a TSF value of the first AP and a TSF offset value of the second AP. In other instances, the time period between consecutive transmissions of the synchronization frames may be approximately 20 milliseconds. In various aspects, the multiple synchronization frames may be transmitted at a data rate greater than a basic data rate associated with the transmission of beacon frames on the first communication link.
[0009] In various specific implementations, execution of the processor readable code may be configured to terminate the enhanced synchronization mode in response to an indication of timing synchronization between the first AP and each of the plurality of STAs participating in the enhanced synchronization mode. In some instances, termination of the enhanced synchronization mode may be further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
[0010] In some other implementations, execution of the processor readable code may be configured to receive a request to initiate an enhanced synchronization mode from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
[0011] In some implementations, execution of the processor readable code may be configured to indicate to at least one STA the start time of the enhanced synchronization mode. In some instances, the indicated start time may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame sent on the first communication link.
[0012] In other specific implementations, execution of the processor readable code may be configured to indicate to at least one STA whether the first AP and the second AP share a common clock or a common TSF value across the first AP and the second AP of the device. In some instances, the indication of the common clock or the common TSF value across the first AP and the second AP of the device may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a synchronization frame.
[0013] In some other specific implementations, execution of the processor readable code may be configured to: obtain a TSF offset between the first AP and each of the plurality of STAs, and indicate to each of the plurality of STAs whether participation in the enhanced synchronization mode is mandatory or voluntary based at least in part on the TSF offset. In some instances, whether participation in the enhanced synchronization mode is mandatory or voluntary for at least some of the plurality of STAs may be further based on an indication of latency-sensitive traffic on the first communication link. In some aspects, execution of the processor readable code may be configured to reject association requests from STAs that do not support the enhanced synchronization mode during a time period starting before a start time of the enhanced synchronization mode.
[0014] In various specific implementations, execution of the processor-readable code may be configured to receive a frame from at least one STA indicating one or more of the following: an amount of clock drift between the at least one STA and a first AP during each beacon interval, whether the at least one STA participates in an enhanced synchronization mode, whether the at least one STA receives beacon frames on a first communication link or on a second communication link associated with a second AP, or the frequency with which the at least one STA receives beacon frames or synchronization frames indicating TSF information of the first AP. Execution of the processor-readable code may be configured to schedule one or more TWT SPs or one or more r-TWT SPs for delay-sensitive services on the first communication link based at least in part on one or more indications received from the at least one STA.
[0015] Another innovative aspect of the subject matter described in the present disclosure may be implemented as a method for wireless communication by a device. In some specific implementations, the method includes sending an indication of an enhanced synchronization mode to at least one STA on a first communication link associated with a first AP of the device. The method includes sending multiple synchronization frames on the first communication link during the enhanced synchronization mode more frequently than the TBTT associated with the first communication link, each of the multiple synchronization frames indicating a TSF offset between the first AP and the second AP of the device. In some aspects, each of the multiple synchronization frames may also indicate a TSF value of the first AP. In some instances, the indication may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame sent on the first communication link.
[0016] In various specific implementations, the device may be an AP MLD including a first AP and a second AP, the first AP being associated with a first communication link, the second AP being associated with a second communication link, the second communication link occupying a frequency band different from the first communication link. In some specific implementations, the enhanced synchronization mode may be established in conjunction with one or more TWT SPs or one or more restricted r-TWT SPs scheduled on the first communication link. In some instances, at least one of the multiple synchronization frames may be a FILS discovery frame carrying a TSF value of the first AP and a TSF offset value of the second AP. In other instances, the time period between consecutive transmissions of synchronization frames may be approximately 20 milliseconds. In various aspects, the multiple synchronization frames may be transmitted at a data rate greater than a basic data rate associated with the transmission of beacon frames on the first communication link.
[0017] In various specific implementations, the method may also include terminating the enhanced synchronization mode in response to an indication of timing synchronization between the first AP and each of the plurality of STAs participating in the enhanced synchronization mode. In some instances, the termination of the enhanced synchronization mode may be further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
[0018] In some other specific implementations, the method may also include receiving a request to initiate an enhanced synchronization mode from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
[0019] In some implementations, the method may also include indicating to at least one STA a start time of the enhanced synchronization mode. In some instances, the indicated start time may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame sent on the first communication link.
[0020] In other specific implementations, the method may also include indicating to at least one STA whether the first AP and the second AP share a common clock or a common TSF value of the first AP and the second AP across the device. In some instances, the indication of the common clock or the common TSF value of the first AP and the second AP across the device may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a synchronization frame.
[0021] In some other specific implementations, the method may also include: obtaining a TSF offset between the first AP and each of the plurality of STAs, and indicating to each of the plurality of STAs whether participation in the enhanced synchronization mode is mandatory or voluntary based at least in part on the TSF offset. In some instances, whether participation in the enhanced synchronization mode is mandatory or voluntary for at least some of the plurality of STAs may be further based on an indication of latency-sensitive traffic on the first communication link. In some aspects, the method may also include rejecting association requests from STAs that do not support the enhanced synchronization mode during a time period starting before a start time of the enhanced synchronization mode.
[0022] In various specific implementations, the method may also include receiving a frame from at least one STA indicating one or more of the following: an amount of clock drift between the at least one STA and the first AP during each beacon interval, whether the at least one STA participates in an enhanced synchronization mode, whether the at least one STA receives beacon frames on a first communication link or on a second communication link associated with a second AP, or the frequency with which the at least one STA receives beacon frames or synchronization frames indicating TSF information of the first AP. The method may also include scheduling one or more TWT SPs or one or more r-TWT SPs for delay-sensitive services on the first communication link based at least in part on one or more indications received from the at least one STA.
[0023] Details of one or more specific implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Note that the relative dimensions in the drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] Figure 1 A schematic diagram of an example wireless communication network is shown.
[0025] Figure 2A Example protocol data units (PDUs) that may be used for communications between an access point (AP) and one or more wireless stations (STAs) are shown.
[0026] Figure 2B Shows Figure 2AExample fields in a PDU.
[0027] Figure 3A Another example PDU that may be used for communication between an AP and one or more STAs is shown.
[0028] Figure 3B Another example PDU that may be used for communication between an AP and one or more STAs is shown.
[0029] Figure 4 A block diagram of an example wireless communication device is shown.
[0030] Figure 5A A block diagram of an example access point (AP) is shown.
[0031] Figure 5B A block diagram of an example station (STA) is shown.
[0032] Figure 6 An example communication system including an access point (AP) multi-link device (MLD) and a non-AP MLD is shown.
[0033] Figure 7 A timing diagram depicting an example wireless communication is shown.
[0034] Fig. 8A A timing diagram depicting an example beacon frame transmission is shown.
[0035] Figure 8B A timing diagram depicting example wireless communications between devices is shown.
[0036] Figure 8C Another timing diagram depicting an example beacon frame transmission is shown.
[0037] Fig.8D Another timing diagram depicting example wireless communications between devices is shown.
[0038] Fig. 9 A timing diagram is shown depicting example wireless communications supporting enhanced synchronization mode according to some implementations.
[0039] Fig.10 A timing diagram is shown depicting example wireless communications supporting enhanced synchronization mode according to some implementations.
[0040] Figures 11 to 18 A flow chart illustrating example operations for wireless communications supporting enhanced synchronization mode according to some implementations is shown.
[0041] Figure 19 to Figure 20 A flow chart illustrating example operations for wireless communications supporting enhanced synchronization mode according to some other implementations is shown.
[0042] Fig.21 A block diagram of an example wireless communication device is shown.
[0043] Fig. 22 A block diagram of another example wireless communication device is shown.
[0044] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION
[0045] The following description is directed to some specific implementations in order to describe the innovative aspects of the present disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to one or more of the following: Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards published by the 3rd Generation Partnership Project (3GPP), the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or as defined by the Bluetooth Special Interest Group (SIG). Standards, etc. The described implementations may be implemented in any device, system, or network capable of sending and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), single user (SU) multiple input multiple output (MIMO), and multi-user (MU) MIMO. The described implementations may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless wide area network (WWAN), a wireless personal area network (WPAN), a wireless local area network (WLAN), or an Internet of Things (IOT) network.
[0046] The IEEE 802.11be revision of the IEEE 802.11 standard describes a restricted target wake-up time (r-TWT) service period (SP) that can be allocated for delay-sensitive services. As used herein, the term "non-legacy STA" refers to any wireless station (STA) that supports the IEEE 802.11be revision of the IEEE 802.11 standard or a later version, and the term "low-latency STA" refers to any non-legacy STA that has delay-sensitive services to transmit or receive. In contrast, the term "legacy STA" may refer to any STA that only supports IEEE 802.11ax or earlier generations of the IEEE 802.11 standard. Non-legacy STAs that support r-TWT operation and obtain a transmit opportunity (TXOP) outside of an r-TWT SP must terminate their corresponding TXOP before the start of any r-TWT SP of which they are not a member. Therefore, the r-TWT SP can provide more predictable delays, reduced worst-case delays, or reduced jitter, and have higher reliability for delay-sensitive services.
[0047] Aspects of the present disclosure recognize that the benefits of r-TWT operation may depend on the ability of a STA operating on a communication link to obtain accurate timing information of an AP responsible for scheduling an r-TWT SP on the communication link. For example, in order to avoid accessing a wireless link during an r-TWT SP associated with a given communication link, a non-member STA should be configured to have information that (relatively accurately) indicates the start time of the r-TWT SP. According to existing versions of the IEEE 802.11 standard, the start time of the r-TWT SP is expressed as an integer value associated with the timing synchronization function (TSF) timer of the AP (or BSS) that schedules the r-TWT SP. The AP broadcasts a beacon frame carrying the current value of the TSF timer based on the scheduled target beacon transmit time (TBTT). STAs (and other APs) receiving beacon frames can use the current TSF value to synchronize the corresponding local TSF timers of these STAs.
[0048] Defects in the clock used by the AP and the AP's associated STAs (and other APs) to implement the corresponding TSF timers of the associated STAs may cause clock drift between the AP and the associated STAs. The TSF offset between the AP and the AP's associated STAs caused by the clock drift may affect the accuracy with which the associated STA estimates the start time of the r-TWT SP on the communication link. The IEEE 802.11 standard specifies a beacon interval of 185,234,501 microseconds (μs) and allows a maximum clock drift of ±100 parts per million (ppm) between the AP and the AP's associated STAs. Thus, the clock drift between the AP and the AP's associated STAs may be as high as ±20μs per beacon interval. A STA in power saving (PS) mode may remain in a sleep state during multiple beacon intervals and may therefore not listen to beacon frames at every TBTT. For example, a STA in PS mode associated with Delivery Traffic Indication Map (DTIM) = 4 wakes up at every 4th TBTT to listen for beacon frames, and thus will miss 3 consecutive beacon frame transmissions during each DTIM period. Therefore, the clock drift between a STA in PS mode and its associated AP in the case of DTIM = 4 can be as high as ±4*20μs = 80μs per DTIM period.
[0049] Some wireless devices may be capable of multi-link operation (MLO). Devices with MLO capabilities may be referred to as multi-link devices (MLDs). For example, an access point (AP) MLD may include multiple APs configured to communicate with non-AP MLDs (also referred to as "STA MLDs") on multiple respective communication links. Similarly, a non-AP MLD may include multiple STAs, each of which is configured to communicate on a respective one of the multiple communication links associated with the AP MLD. Some non-AP MLDs may communicate concurrently with the AP MLD on each of the communication links, for example, according to a multi-link multi-radio (MLMR) simultaneous transmit and receive (STR) or MLMR non-STR (NSTR) operating mode. Other non-AP MLDs may communicate with the AP MLD on only one of the communication links at any given time, for example, according to a multi-link single radio (MLSR) or enhanced MLSR (EMLSR) operating mode.
[0050] When APs included in or associated with an AP MLD use different clocks for the respective TSF timers of the AP, clock drift between the respective clocks may cause TSF offsets between the APs of the AP MLD. The IEEE 802.11 standard allows a maximum clock drift of ±30 μs between the APs of the AP MLD. Thus, for a STA in PS mode associated with the first AP of the AP MLD in the case of DTIM=4, the clock drift between the STA and the other APs of the AP MLD may be as high as 30 μs+80 μs=±110 μs. Therefore, when the STA relies on beacon frames communicated in the beacon interval for synchronization (especially when one or more beacons are skipped), the clock drift between the STA and the other APs of the AP MLD may exceed an acceptable level. Therefore, it is necessary to maintain stricter synchronization between the STA and the associated AP, and more specifically, between the STA and each AP in the AP MLD, to ensure that the TSF offset between the STA and the associated AP (or each AP in the AP MLD) does not allow the STA to unintentionally continue to maintain the TXOP after the start time of the r-TWT SP, or does not allow the STA to unintentionally access the communication link just before the start time of the r-TWT SP due to the TSF offset.
[0051] The specific implementation described herein provides an enhanced synchronization mode that allows synchronization messages to be communicated between the AP and the STA more frequently than the TBTT associated with the communication link. More specifically, the device may send an indication of the enhanced synchronization mode to the STA on a first communication link associated with a first AP device. The device may then send multiple synchronization frames on the first communication link during the enhanced synchronization mode more frequently than the TBTT associated with the first communication link, wherein each of the multiple synchronization frames indicates a TSF offset between the first AP and the second AP of the device. In this way, relative to relying on synchronization at the TBTT, the STA may be able to maintain tighter synchronization with the AP to ensure (e.g., help increase the incidence) that the STA terminates any TXOP obtained outside the r-TWT SP before the r-TWT SP on the communication link starts, and / or ensure that the STA does not attempt to gain access to the communication link immediately before the r-TWT SP on the communication link starts. In this way, the enhanced synchronization mode may allow r-TWT SP operation to provide more predictable latency, reduced worst-case latency, or reduced jitter, with higher reliability for latency-sensitive services.
[0052] Specific implementations of the subject matter described in the present disclosure may be used to synchronize the timing between a STA and an AP in a manner that prevents a STA operating on a communication link from inadvertently interfering with one or more r-TWT SPs scheduled on the communication link. Specifically, in various specific implementations, a device including a first AP may establish an enhanced synchronization mode, during which a participating STA receives timing information of one or more associated or nearby APs with sufficient periodicity to ensure that the TSF offset between the STA and the AP does not exceed a value that allows the STA to inadvertently access or occupy the shared wireless medium during the r-TWT SP scheduled on the shared wireless medium. For example, in some specific implementations, the device may send an indication of an enhanced synchronization mode to one or more STAs associated with the device on a first communication link associated with the first AP of the device. In some instances, the indication may be in response to the presence of a delay-sensitive service on the first communication link. In some other instances, the indication may be in response to a request from one or more STAs. In some aspects, the indication may also indicate the start time of the enhanced synchronization mode. In other aspects, the indication may also indicate whether participation in the enhanced synchronization mode is mandatory or voluntary for each of the one or more STAs.
[0053] In some instances, the device may be an AP multi-link device (MLD) including a first AP and a second AP. The first AP may be associated with a first communication link, and the second AP may be associated with a second communication link, the second communication link occupying a different frequency band than the first communication link. For example, the first communication link may be a wireless channel located in one of the 2.4 GHz frequency band, the 5 GHz frequency band, or the 6 GHz frequency band, and the second communication link may be a wireless channel located in another of the 2.4 GHz frequency band, the 5 GHz frequency band, or the 6 GHz frequency band.
[0054] During the enhanced synchronization mode, the device may send multiple synchronization frames on the first communication link more frequently than the TBTT associated with the first communication link. Each of the synchronization frames may indicate the TSF value of the first AP and the TSF offset between the first AP and the second AP of the device. The frequency of sending the synchronization frame on the first communication link may be associated with the timing accuracy level that prevents the participating STA from occupying or accessing the first communication link during one or more r-TWT SPs scheduled on the first communication link. For example, in some instances, the synchronization frames may be sent at intervals of approximately 20 μs (but other suitable intervals may be used). STAs participating in the enhanced synchronization mode may use the TSF information indicated in the synchronization frame to synchronize their respective local TSF timers with the TSF timers of the first AP and the second AP of the device, for example, without receiving a beacon frame from the second AP. In some specific implementations, the enhanced synchronization mode may be established in conjunction with one or more TWT SPs or r-TWT SPs on the first communication link. In some aspects, the device may reject association requests from STAs that do not support enhanced synchronization mode during a time period that begins before a start time of the enhanced synchronization mode and ends at a termination of the enhanced synchronization mode.
[0055] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. By synchronizing the TSF timer of the STA with the corresponding TSF timer of the first AP and the second AP of the device more frequently than the TBTT of the first AP and the second AP, various aspects of the present disclosure may, for example, reduce the TSF offset between the STA and each of the first AP and the second AP compared to the STA that relies on beacon frame transmissions to obtain the TSF information of the AP. In addition, by indicating the TSF offset between the first AP and the second AP of the device in the synchronization frame, various aspects of the present disclosure may allow STAs operating on the first communication link to synchronize their corresponding TSF timers with the TSF timer of the second AP without receiving beacon frames broadcast by the second AP on the second communication link. In this way, a single-radio device (such as an MLSR device or an EMLSR device) may synchronize the TSF timer of the device with the corresponding TSF timer of both the first AP and the second AP of the device without switching between the first communication link and the second communication link to receive beacon frame transmissions from each of the first AP and the second AP of the device.
[0056] In addition, by participating in the enhanced synchronization mode disclosed herein, the STA may be able to maintain the TSF offset associated with the first AP and the second AP of the device at or below a value associated with the timing accuracy level to avoid inadvertently occupying or attempting to access the first communication link during one or more TWT SPs or r-TWT SPs scheduled on the first communication link. Specifically, the increased timing synchronization achieved by using the enhanced synchronization mode disclosed herein can ensure that participating STAs terminate TXOPs obtained outside the r-TWT SP before the start of the r-TWT SP of which they are not members. In addition, the increased timing synchronization provided by the enhanced synchronization mode disclosed herein can ensure that participating STAs do not perform channel access operations that may cause overlap with the r-TWT SP and thereby interfere with the TXOP of the r-TWT SP before the start time of the r-TWT SP. In this way, the enhanced synchronization mode disclosed herein can allow the r-TWT SP to provide more predictable latency, reduced worst-case latency, or reduced jitter, with higher reliability for latency-sensitive services.
[0057] Figure 1 A block diagram of an example wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will be referred to as WLAN 100 hereinafter). For example, the WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of standards such as those defined by the IEEE 802.11-2016 specification or amendments thereof, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. The WLAN 100 may include numerous wireless communication devices such as an access point (AP) 102 and a plurality of stations (STAs) 104. Although only one AP 102 is shown, the WLAN 100 may also include a plurality of APs 102.
[0058] Each STA 104 may also be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, etc. STA 104 may represent a variety of devices, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., TVs, computer monitors, navigation systems, etc.), music or other audio or stereo equipment, remote control devices (“remote controls”), printers, kitchen or other home appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.
[0059] A single AP 102 and the associated set of STAs 104 may be referred to as a basic service set (BSS), which is managed by the corresponding AP 102 . Figure 1 Additionally shown is an example coverage area 106 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. The BSS may be identified to users by a service set identifier (SSID) and to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP 102. The AP 102 periodically broadcasts a beacon frame (“beacon”) including the BSSID to enable any STA 104 within the wireless range of the AP 102 to “associate” or reassociate with the AP 102 to establish or maintain a corresponding communication link 108 (hereinafter also referred to as a “Wi-Fi link”) with the AP 102. For example, the beacon may include an identification of a primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide access to external networks to various STAs 104 in the WLAN via corresponding communication links 108.
[0060] To establish a communication link 108 with the AP 102, each STA 104 is configured to perform passive or active scanning operations ("scanning") on frequency channels in one or more frequency bands (eg, 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). To perform passive scanning, the STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals, referred to as target beacon transmission times (TBTTs), measured in time units (TUs), where one TU may be equal to 1024 microseconds (μs). To perform active scanning, the STA 104 generates probe requests and sequentially transmits these probe requests on each channel to be scanned, and listens for probe responses from the AP 102. Each STA 104 may be configured to identify or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 108 with the selected AP 102. The AP 102 assigns an association identifier (AID) to the STA 104 at the end of the association operation, and the AP 102 uses the association identifier (AID) to track the STA 104.
[0061] As wireless networks become more and more common, STA 104 may have the opportunity to select one of many BSSs within the range of the STA or to select among multiple APs 102 that together form an extended service set (ESS) (including multiple connected BSSs). The extended network station associated with WLAN 100 may be connected to a wired or wireless distribution system that allows multiple APs 102 to be connected in such an ESS. In this way, STA 104 may be covered by more than one AP 102 and may be associated with different APs 102 at different times for different transmissions. Additionally, after associating with AP 102, STA 104 may also be configured to periodically scan the surrounding environment of the STA to find a more appropriate AP 102 to associate with it. For example, a STA 104 that is moving relative to the STA's associated AP 102 may perform a "roaming" scan to find another AP 102 with a more suitable network characteristic (such as a larger received signal strength indicator (RSSI) or a reduced traffic load).
[0062] In some cases, STA 104 may form a network without AP 102 or other equipment other than STA 104 itself. An example of such a network is a self-organizing (ad hoc) network (or wireless self-organizing network). A self-organizing network may alternatively be referred to as a mesh network or a peer-to-peer (P2P) network. In some cases, a self-organizing network may be implemented within a larger wireless network (such as WLAN 100). In such a specific implementation, although STA 104 may be able to communicate with each other through AP 102 using communication link 108, STA 104 may also communicate directly with each other via direct communication link 110. Additionally, two STA 104 may communicate via direct communication link 110, regardless of whether the two STA 104 are associated with the same AP 102 and served by the same AP. In such a self-organizing system, one or more STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as a group owner (GO) and may coordinate the transmission within the self-organizing network. Examples of direct communication link 110 include a Wi-Fi direct connection, a connection established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.
[0063] The AP 102 and the STA 104 may operate and communicate (via corresponding communication links 108) in accordance with the IEEE 802.11 family of standards, such as those defined by the IEEE 802.11-2016 specification or its amendments, including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. These standards define WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The AP 102 and the STA 104 send and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") to and from each other in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs). The AP 102 and STA 104 in the WLAN 100 may send PPDUs on an unlicensed spectrum, which may be a portion of a spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5.0 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some implementations of the AP 102 and STA 104 described herein may also communicate in other frequency bands, such as the 6.0 GHz band, that may support both licensed and unlicensed communications. The AP 102 and STA 104 may also be configured to communicate on other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.
[0064] Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs that comply with the IEEE 802.11n, 802.11ac, and 802.11ax standard amendments may be sent on 2.4 GHz and 5.0 GHz frequency bands, where each frequency band is divided into multiple 20 MHz channels. In this way, these PPDUs are sent on a physical channel with a minimum bandwidth of 20 MHz, but larger channels may be formed through channel bonding. For example, a PPDU may be sent on a physical channel with a bandwidth of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.
[0065] Each PPDU is a composite structure including a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In an instance where the PPDU is sent on a bound channel, the preamble field can be copied and sent in each of a plurality of component channels. The PHY preamble may include both a legacy part (or "legacy preamble") and a non-legacy part (or "non-legacy preamble"). Legacy preambles can be used for packet detection, automatic gain control, and channel estimation, as well as other purposes. Legacy preambles can also generally be used to maintain compatibility with legacy devices. The format, decoding, and information provided therein of the non-legacy part of the preamble are based on the specific IEEE 802.11 protocol to be used to send the payload.
[0066] Figure 2A An example protocol data unit (PDU) 200 that may be used for wireless communication between an AP 102 and one or more STAs 104 is shown. For example, the PDU 200 may be configured as a PPDU. As shown, the PDU 200 includes a PHY preamble 202 and a payload 204. For example, the preamble 202 may include a legacy portion that itself includes a legacy short training field (L-STF) 206 that may consist of two BPSK symbols, a legacy long training field (L-LTF) 208 that may consist of two BPSK symbols, and a legacy signal field (L-SIG) 210 that may consist of two BPSK symbols. The legacy portion of the preamble 202 may be configured according to the IEEE 802.11a wireless communication protocol standard. The preamble 202 may also include a non-legacy portion including one or more non-legacy fields 212 that comply with, for example, an IEEE wireless communication protocol, such as IEEE 802.11ac, 802.11ax, 802.11be, or a later wireless communication protocol.
[0067] L-STF 206 generally enables the receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. L-LTF 208 generally enables the receiving device to perform fine timing and frequency estimation, and can also perform initial estimation of the wireless channel. L-SIG 210 generally enables the receiving device to determine the duration of the PDU and use the determined duration to avoid sending on the PDU. For example, L-STF 206, L-LTF 208 and L-SIG 210 can be modulated according to a binary phase shift keying (BPSK) modulation scheme. Payload 204 can be modulated according to a BPSK modulation scheme, an orthogonal BPSK (Q-BPSK) modulation scheme, an orthogonal amplitude modulation (QAM) modulation scheme, or another appropriate modulation scheme. Payload 204 may include a PSDU including a data field (DATA) 214, which in turn may carry, for example, a medium access control (MAC) protocol data unit (MPDU) or higher layer data in the form of an aggregated MPDU (A-MPDU).
[0068] Figure 2B Shows Figure 2A 2. The example L-SIG 210 in the PDU 200 of FIG. L-SIG 210 includes a data rate field 222, a reserved bit 224, a length field 226, a parity bit 228, and a tail field 230. The data rate field 222 indicates the data rate (note that the data rate indicated in the data rate field 222 may not be the actual data rate of the data carried in the payload 204). The length field 226 indicates the packet length, for example, in symbols or bytes. The parity bit 228 can be used to detect bit errors. The tail field 230 includes a tail bit that can be used by a receiving device to terminate the operation of a decoder (e.g., a Viterbi decoder). The receiving device can use the data rate and length indicated in the data rate field 222 and the length field 226 to determine the packet duration, for example, in microseconds (μs) or other time units.
[0069] Figure 3A Another example PDU 300 that can be used for wireless communication between an AP and one or more STAs is shown. The PDU 300 can be used for SU, OFDMA, or MU-MIMO transmission. The PDU 300 can be formatted as a high-efficiency (HE) WLAN PPDU according to the IEEE 802.11ax amendment to the IEEE 802.11 wireless communication protocol standard. The PDU 300 includes a PHY preamble that includes a legacy portion 302 and a non-legacy portion 304. The PDU 300 may also include a payload 306 (e.g., in the form of a PSDU including a data field 324) after the preamble.
[0070] The legacy portion 302 of the preamble includes an L-STF 308, an L-LTF 310, and an L-SIG 312. The non-legacy portion 304 includes a repetition of the L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, an HE short training field (HE-STF) 320, and one or more HE long training fields (or symbols) (HE-LTF) 322. For OFDMA or MU-MIMO communications, the non-legacy portion 304 also includes a second HE signal field (HE-SIG-B) 318 that is encoded separately from the HE-SIG-A 316. As with the L-STF 308, L-LTF 310, and L-SIG 312, in instances involving the use of bonded channels, the information in the RL-SIG 314 and HE-SIG-A 316 may be replicated and sent in each component 20 MHz channel. In contrast, the content in HE-SIG-B 318 may be unique to each 20 MHz channel and target specific STA 104 .
[0071] The RL-SIG 314 may indicate to the HE-compatible STA 104 that the PDU 300 is a HE PPDU. The AP 102 may use the HE-SIG-A 316 to identify multiple STAs 104 and inform the multiple STAs that the AP has scheduled UL or DL resources for them. For example, the HE-SIG-A 316 may include a resource allocation subfield indicating resource allocation for the identified STA 104. The HE-SIG-A 316 may be decoded by each HE-compatible STA 104 served by the AP 102. For MU transmission, the HE-SIG-A 316 also includes information that can be used by each identified STA 104 to decode the associated HE-SIG-B 318. For example, the HE-SIG-A 316 may indicate the frame format (including the location and length of the HE-SIG-B 318), the available channel bandwidth, and the modulation and coding scheme (MCS), among other examples. The HE-SIG-A 316 may also include HE WLAN signaling information that can be used by STAs 104 other than the identified STA 104.
[0072] HE-SIG-B 318 may carry STA-specific scheduling information, such as, for example, STA-specific (or "user-specific") MCS values and STA-specific RU allocation information. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding resource unit (RU) in the associated data field 324. Each HE-SIG-B 318 includes a common field and at least one STA-specific field. The common field may indicate RU allocations (including RU assignments in the frequency domain) to multiple STAs 104, indicating which RUs are allocated for MU-MIMO transmissions and which RUs correspond to MU-OFDMA transmissions, as well as the number of users in the allocation and other examples. The common field may be encoded with common bits, CRC bits, and tail bits. User-specific fields are assigned to a specific STA 104 and may be used to schedule a specific RU and indicate the scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields containing information for two corresponding STAs to decode their corresponding RU payloads in the data field 324 .
[0073] Figure 3B Another example PPDU 350 that can be used for wireless communication between an AP and one or more STAs is shown. PDU 350 can be used for SU, OFDMA, or MU-MIMO transmission. PDU 350 can be formatted as an extremely high throughput (EHT) WLAN PPDU according to the IEEE 802.11be amendment to the IEEE 802.11 wireless communication protocol standard, or can be formatted as a PPDU that complies with any future (post-EHT) version of a new wireless communication protocol (complying with future IEEE 802.11 wireless communication protocol standards or other wireless communication standards). PDU 350 includes a PHY preamble that includes a legacy portion 352 and a non-legacy portion 354. PDU 350 may also include a PHY payload 356 (e.g., in the form of a PSDU including a data field 376) after the preamble.
[0074] The legacy portion 352 of the preamble includes an L-STF 358, an L-LTF 360, and an L-SIG 362. The non-legacy portion 354 of the preamble includes an RL-SIG 364 and a plurality of wireless communication protocol version-related signal fields following the RL-SIG 364. For example, the non-legacy portion 354 may include a universal signal field 366 (referred to herein as "U-SIG 366") and an EHT signal field 368 (referred to herein as "EHT-SIG 368"). One or both of the U-SIG 366 and the EHT-SIG 368 may be configured to be used for other wireless communication protocol versions above the EHT and carry information related to the version. The non-legacy portion 354 also includes an additional short training field 372 (referred to herein as "EHT-STF 372", but may also be constructed to be used for and carry version-related information for other wireless communication protocol versions above EHT) and one or more additional long training fields 374 (referred to herein as "EHT-LTF 374", but they may be constructed to be used for and carry version-related information for other wireless communication protocol versions above EHT). As with the L-STF 358, L-LTF 360, and L-SIG 362, in instances involving the use of bonded channels, the information in the U-SIG 366 and the EHT-SIG 368 may be replicated and sent in each component 20 MHz channel. In some implementations, the EHT-SIG 368 may additionally or alternatively carry information in one or more non-primary 20 MHz channels that is different from the information carried in the primary 20 MHz channel.
[0075] The EHT-SIG 368 may include one or more jointly encoded symbols and may be encoded in a different block from the block in which the U-SIG 366 is encoded. The EHT-SIG 368 may be used by the AP to identify multiple STAs 104 and notify the multiple STAs that the AP has scheduled UL or DL resources for them. The EHT-SIG 368 may be decoded by each compatible STA 104 served by the AP 102. The EHT-SIG 368 may be used by the receiving device to interpret the bits in the data field 376. For example, the EHT-SIG 368 may include RU allocation information, spatial stream configuration information, and per-user signaling information (such as MCS) and other examples. The EHT-SIG 368 may also include a cyclic redundancy check (CRC) (e.g., four bits) and a tail (e.g., 6 bits) that may be used for a binary convolutional code (BCC). In some implementations, the EHT-SIG 368 may include one or more code blocks each including a CRC and a tail. In some aspects, each code block may be encoded separately.
[0076] The EHT-SIG 368 may carry STA-specific scheduling information, such as, for example, user-specific MCS values and user-specific RU allocation information. The EHT-SIG 368 may be used by a receiving device to interpret bits in the data field 376. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 376. Each EHT-SIG 368 may include a common field and at least one user-specific field. The common field may indicate the RU distribution to multiple STAs 104, indicate the RU assignment in the frequency domain, indicate which RUs are allocated for MU-MIMO transmission and which RUs correspond to MU-OFDMA transmission, and the number of users in the allocation and other examples. The common field may be encoded with a common bit, a CRC bit, and a tail bit. The user-specific field is assigned to a specific STA 104 and may be used to schedule a specific RU and indicate the schedule to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include, for example, two user fields containing information for two corresponding STAs to decode their corresponding RU payloads.
[0077] The presence of the RL-SIG 364 and the U-SIG 366 may indicate to the EHT or later version compatible STA 104 that the PPDU 350 is an EHT PPDU or any later (post-EHT) version of a PPDU that complies with a new wireless communication protocol (complying with future IEEE 802.11 wireless communication protocol standards). For example, the U-SIG 366 may be used by a receiving device to interpret bits in one or more of the EHT-SIG 368 or the data field 376.
[0078] Figure 4 4 shows a block diagram of an example wireless communication device 400. In some implementations, the wireless communication device 400 may be a wireless communication device for a STA (such as the one described above). Figure 1 In some implementations, the wireless communication device 400 may be an example of a device in an AP (such as one of the STAs 104 described above). Figure 1The wireless communication device 400 is an example of a device in the described AP 102). The wireless communication device 400 is capable of sending (or outputting for sending) and receiving wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device 400 can be configured to send and receive packets in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs) and medium access control (MAC) protocol data units (MPDUs) that comply with the IEEE 802.11 standard (such as the standard defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).
[0079] The wireless communication device 400 may be or may include a chip, system on chip (SoC), chipset, package, or device including one or more modems 402 (e.g., Wi-Fi (IEEE 802.11 compliant) modems). In some implementations, one or more modems 402 (collectively, “modems 402”) additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compatible modem). In some implementations, the wireless communication device 400 also includes one or more radio components 404 (collectively, “radio components 404”). In some implementations, the wireless communication device 400 also includes one or more processors, processing blocks, or processing elements (collectively, “processor 406”) and one or more memory blocks or elements (collectively, “memory 408”).
[0080] The modem 402 may include an intelligent hardware block or device, such as, for example, an application specific integrated circuit (ASIC) or the like. The modem 402 is configured to implement the PHY layer. For example, the modem 402 is configured to modulate packets and output the modulated packets to the radio component 404 for transmission over a wireless medium. Similarly, the modem 402 is configured to obtain the modulated packets received by the radio component 404 and demodulate the packets to provide the demodulated packets. In addition to the modulator and demodulator, the modem 402 may also include a digital signal processing (DSP) circuit, an automatic gain control (AGC), a decoder, a decoder, a multiplexer, and a demultiplexer. For example, when in a transmit mode, the data obtained from the processor 406 is provided to a decoder, which encodes the data to provide the encoded bits. The encoded bits are then mapped to points in the modulation constellation (using the selected MCS) to provide the modulated symbols. The modulated symbols can then be mapped to a number N SS spatial streams or the number N STSThe modulated symbols in the corresponding spatial stream or space-time stream may then be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuit for Tx windowing and filtering. The digital signal may then be provided to a digital-to-analog converter (DAC). The resulting analog signal may then be provided to an upconverter and provided to the radio component 404. In a specific implementation involving beamforming, the modulated symbols in the corresponding spatial stream may be pre-coded via a steering matrix before being provided to the IFFT block.
[0081] When in receive mode, a digital signal received from the radio component 404 is provided to a DSP circuit configured to acquire the received signal, for example, by detecting the presence of a signal and estimating an initial timing and frequency offset. The DSP circuit is further configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correcting I / Q imbalance), and applying digital gain to obtain a narrowband signal. The output of the DSP circuit may then be fed to an AGC configured to use information extracted from the digital signal (e.g., in one or more received training fields) to determine an appropriate gain. The output of the DSP circuit is also coupled to a demodulator configured to extract the modulated symbols from the signal and, for example, calculate a log-likelihood ratio (LLR) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which may be configured to process the LLRs to provide decoded bits. The decoded bits from all spatial streams are then fed to a demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 406) for processing, evaluation, or interpretation.
[0082] The radio 404 includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which may be combined into one or more transceivers. For example, the RF transmitter and receiver may include various DSP circuits, including at least one power amplifier (PA) and at least one low noise amplifier (LNA), respectively. The RF transmitter and receiver may in turn be coupled to one or more antennas. For example, in some implementations, the wireless communication device 400 may include or be coupled to multiple transmit antennas (each transmit antenna having a corresponding transmit chain) and multiple receive antennas (each receive antenna having a corresponding receive chain). The symbols output from the modem 402 are provided to the radio 404, which then transmits the symbols via the coupled antennas. Similarly, the symbols received via the antennas are obtained by the radio 404, which then provides the symbols to the modem 402.
[0083] The processor 406 may include an intelligent hardware block or device designed to perform the functions described herein, such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD) (such as a field programmable gate array (FPGA)), a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof. The processor 406 processes information received through the radio component 404 and the modem 402, and processes information to be output by the modem 402 and the radio component 404 to be sent through the wireless medium. For example, the processor 406 may implement a control plane and a MAC layer, which is configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform or facilitate the coding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, and other operations or techniques. In some specific implementations, the processor 406 may control the modem 402 to cause the modem to perform the various operations described above.
[0084] The memory 408 may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM) or a combination thereof. The memory 408 may also store non-transitory processor or computer executable software (SW) code containing instructions that, when executed by the processor 406, cause the processor to perform various operations described herein for wireless communication, including generation, transmission, reception, and interpretation of MPDUs, frames, or packets. For example, the various functions of the various components disclosed herein or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein may be implemented as one or more modules of one or more computer programs.
[0085] Figure 5A 5 shows a block diagram of an example AP 502. For example, AP 502 may be a reference Figure 1 The AP 102 is described in detail with reference to an example implementation. The AP 502 includes a wireless communication device (WCD) 510. For example, the wireless communication device 510 may be a wireless communication device (WCD) 510. Figure 4The example implementation of the wireless communication device 400 described. The AP 502 also includes a plurality of antennas 520 coupled to the wireless communication device 510 to send and receive wireless communications. In some implementations, the AP 502 additionally includes an application processor 530 coupled to the wireless communication device 510 and a memory 540 coupled to the application processor 530. The AP 502 also includes at least one external network interface 550 that enables the AP 502 to communicate with a core network or a backhaul network to gain access to an external network including the Internet. For example, the external network interface 550 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Components of the above components may communicate directly or indirectly with other components of the components via at least one bus. The AP 502 also includes a housing that surrounds the wireless communication device 510, the application processor 530, the memory 540, and at least portions of the antennas 520 and the external network interface 550.
[0086] Figure 5B 5 shows a block diagram of an example STA 504. For example, STA 504 may be a reference Figure 1 The example implementation of STA 104 is described. STA 504 includes a wireless communication device 515. For example, the wireless communication device 515 may be a reference Figure 4 An example implementation of the wireless communication device 400 described. The STA 504 also includes one or more antennas 525 coupled to the wireless communication device 515 to send and receive wireless communications. The STA 504 additionally includes an application processor 535 coupled to the wireless communication device 515 and a memory 545 coupled to the application processor 535. In some implementations, the STA 504 also includes a user interface (UI) 555 (such as a touch screen or keyboard) and a display 565, which can be integrated with the UI 555 to form a touch screen display. In some implementations, the STA 504 may also include one or more sensors 575, such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Components of the above components can communicate directly or indirectly with other components of the components through at least one bus. The STA 504 also includes a housing that surrounds the wireless communication device 515, the application processor 535, the memory 545, and at least portions of the antenna 525, the UI 555, and the display 565.
[0087] Figure 6 An example communication system 600 is shown that includes an AP MLD 610 and a non-AP MLD 620. In some implementations, the AP MLD 610 may be Figure 1 AP 102 Figure 4The non-AP MLD 720 may be an example of any of the wireless communication devices 400 of FIG. 5 or the AP 502 of FIG. Figure 1 STA 104 Figure 4 An example of either the wireless communication device 400 of FIG. 5 or the STA 504 of FIG. 5 .
[0088] AP MLD 610 includes a plurality of APs 612-616 associated with (or operating on) communication links 602-606, respectively. Figure 6 In the example of FIG. 6 , the AP MLD 610 is shown as including only three APs. However, in some implementations, the AP MLD 610 may include more than Figure 6 6. Although APs 612-616 may share a common association context (via AP MLD 610), each of APs 612-616 may establish a respective BSS on the AP's associated communication link. APs 612-616 may also establish their respective communication links 602-606 on different frequency bands. For example, AP 612 may operate on a 2.4 GHz band, AP 614 may operate on a 5 GHz band, and AP 616 may operate on a 6 GHz band.
[0089] The non-AP MLD 620 includes a plurality of STAs 622-626 that may be configured to communicate on communication links 602-606, respectively. Thus, STA 622 may operate on the 2.4 GHz band, STA 624 may operate on the 5 GHz band, and STA 626 may operate on the 6 GHz band. Figure 6 In the example of FIG. 6 , the non-AP MLD 620 is shown as including only three STAs. However, in some implementations, the non-AP MLD 620 may include more than Figure 6 The IEEE 802.11be revision of the IEEE 802.11 standard defines several modes in which a non-AP MLD can operate. The various operating modes depend on the number of radio devices associated with the non-AP MLD and the ability of the non-AP MLD to communicate (such as by sending or receiving) concurrently on multiple communication links.
[0090] In some implementations, the non-AP MLD 620 may include a single radio or may otherwise be capable of communicating on only one link at a time. In such implementations, the non-AP MLD 620 may operate in a multi-link single radio (MLSR) mode or an enhanced MLSR (EMLSR) mode. A non-AP MLD operating in the EMLSR mode may concurrently listen to a particular type of communication (such as a buffer status report poll (BSRP) frame or a multi-user request to transmit (MU-RTS) frame) on multiple communication links, but may only be able to send or receive on one communication link at any given time. For example, STAs 622 and 624 may concurrently listen to their respective links 602 and 604 during a listening interval. However, if STA 622 detects a BSRP frame on link 602, the non-AP MLD 620 then tunes each of the antennas of the non-AP MLD (including the antenna used by STA 624 during the listening interval) to operate on link 602. In contrast, a non-AP MLD operating in MLSR mode can only listen to one communication link and can only transmit or receive on one communication link at any given time.For example, STA 622 must be in power save mode any time STA 624 is active.
[0091] In some other implementations, the non-AP MLD 620 may include multiple radio components and may be capable of concurrent communication on each of these links. In such implementations, the non-AP MLD 620 may operate in a multi-link multi-radio (MLMR) simultaneous transmit and receive (STR) mode or a multi-link multi-radio non-STR (NSTR) mode. A non-AP MLD operating in the MLMRSTR mode may transmit and receive simultaneously (or concurrently) on multiple communication links. For example, STA 622 may transmit or receive on link 602, while STA 624 concurrently transmits or receives on link 604. More specifically, such communications may be asynchronous. In other words, STA 622 may transmit on link 602, while STA 624 receives on link 604. In contrast, a non-AP MLD operating in the MLMR NSTR mode may transmit and receive simultaneously on multiple communication links, provided that such communications are synchronous. For example, STAs 624 and 626 may transmit concurrently on links 604 and 606, and may receive concurrently on links 604 and 606. However, STA 624 may not transmit on link 604 while STA 626 is receiving on link 606.
[0092] Further, the non-AP MLD may include multiple radio components, but may be capable of concurrent communication only on a subset of links. In such specific implementations, the non-AP MLD 620 may operate in an enhanced MLMR (EMLMR) mode or a hybrid EMLSR mode. A non-AP MLD operating in the EMLMR mode supports MLMR STR operation between certain communication link pairs. For example, STAs 622 and 624 may communicate concurrently on their respective links 602 and 604 according to the MLMR STR operation mode.
[0093] Figure 7 A timing diagram 700 is shown depicting an example of wireless communications between devices belonging to a BSS. Figure 7 In the example of FIG. 1 , the BSS may include multiple non-legacy STAs 702 and 704 that support r-TWT operation. More specifically, STA 702 may be a low-latency STA that is a member of an r-TWT SP that spans a time period between time t3 and t8, and STA 704 may be a non-member STA. In some implementations, each of STAs 702 and 704 may be a Figure 1 STA 104 Figure 4 The wireless communication device 400 or Figure 5B An example of any of the STAs 504. Although in actual implementations Figure 7 Only two non-legacy STAs 702 and 704 are shown in the example of FIG. 1 , but the BSS may include any number of legacy or non-legacy STAs.
[0094] The non-member STA 704 attempts to access the shared wireless channel before starting the r-TWT SP at time t3. More specifically, the non-member STA 704 senses that the channel is idle within a threshold duration from time t0 to t1 based on a channel sensing operation (such as a clear channel assessment (CCA)), and further counts down a random backoff (RBO) duration from time t1 to t2 before attempting to acquire a TXOP. For example, the threshold duration (from time t0 to t1) may be an arbitration inter-frame space (AIFS) duration associated with a specific access category (AC) for data traffic. Therefore, the RBO duration (from time t1 to t2) may be randomly selected from an RBO range spanning a contention window associated with the AC. At time t2, the non-member STA 704 senses that the wireless channel is still idle, and continues to acquire a TXOP, for example, by initiating a transmission on a shared channel. Figure 7In the example of , the desired TXOP may be longer than the duration remaining before the r-TWT SP starts at time t3. However, since existing rules regarding r-TWT operation require non-member STAs to terminate their TXOPs before the start of the r-TWT SP, the non-member STA 704 must truncate its TXOP between time t2 and t3.
[0095] The low-latency STA 702 attempts to access the shared wireless channel at the beginning of the r-TWT SP. Figure 7 In the example of FIG. 7 , the low-latency STA 702 senses that the channel is idle for the AIFS duration from time t3 to t4, and further counts down the RBO duration from time t4 to t6 before attempting to acquire a TXOP. Figure 7 As shown, non-member STA 704 also attempts to access the shared wireless channel at the beginning of the r-TWT SP. For example, non-member STA 704 senses that the channel is idle within the AIFS duration from time t3 to t5, and further counts down the RBO duration starting at time t5. In some specific implementations, the data service associated with the low-latency STA 702 may be assigned to an AC with a higher priority than the data service associated with the non-member STA 704. Therefore, the AIFS or RBO duration associated with the low-latency STA 702 may be shorter than the AIFS or RBO duration associated with the non-member STA 704, respectively. Therefore, the low-latency STA 702 wins access to the wireless channel at time t6, and obtains a TXOP, for example, by initiating a transmission on a shared channel.
[0096] The non-member STA 704 senses that the wireless channel is busy at time t6 and avoids accessing the shared channel for the duration of the TXOP (from time t6 to t8). After the TXOP has terminated, at time t8, the non-member STA 704 may attempt to access the wireless channel again. In this way, r-TWT operation may prioritize delay-sensitive traffic in the BSS, for example, by requiring non-member STAs to terminate their TXOPs before the start of any r-TWT SP of which they are not members. Additionally, the AP (not shown for simplicity) may suppress all traffic from legacy STAs associated with the BSS by scheduling a silent interval to overlap with at least a portion of the r-TWT SP, such as one or more time units (TUs) starting at time t3. For example, the duration of the silent interval may be indicated by one or more silent elements included in a management frame (such as a beacon frame or a probe response frame) sent by the AP before the start of the r-TWT SP.
[0097] As discussed, aspects of the present disclosure recognize that the benefits of r-TWT operation may depend on non-legacy STAs (such as Figure 7 The non-member STA 702 and 704) has the ability to obtain accurate timing information of the AP responsible for scheduling the r-TWT SP on the communication link. Specifically, in order to avoid interfering with the r-TWT SP scheduled on the communication link, the non-member STA must know the start time of the r-TWT SP relatively accurately. However, because the start time of the r-TWT SP is expressed as an integer value based on the TSF timer of the AP that schedules the r-TWT SP on the communication link, the TSF offset between the non-member STA and the scheduling AP may cause the non-member STA to incorrectly calculate the r-TWT SP start time and inadvertently occupy the communication link during at least a portion of the r-TWT SP.
[0098] Fig. 8A A timing diagram 800A depicting an example beacon frame transmission is shown. The timing diagram 800A shows a first AP 810 operating on a first communication link (Link 1) and a second AP 820 operating on a second communication link (Link 2). The APs 810 and 820 may be Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 In some implementations, APs 810 and 820 may be part of or associated with an AP MLD configured to communicate over a plurality of different communication links. For example, although for simplicity in Fig. 8A Only two APs 810 and 820 are shown in FIG. 1 , but the AP MLD may include one or more other APs configured to operate on one or more other corresponding communication links. In some other aspects, Link 1 may be a wireless channel located in one of the 2.4 GHz band, the 5 GHz band, or the 6 GHz band, and Link 2 may be a wireless channel located in another of the 2.4 GHz band, the 5 GHz band, or the 6 GHz band.
[0099] AP 810 broadcasts a plurality of first beacon frames B11-B31 on link 1 at corresponding times TBTT(1)1-TBTT(3)1, and AP 820 broadcasts a plurality of second beacon frames B12-B32 on link 2 at corresponding times TBTT(1)2-TBTT(3)2. Each of the first beacon frames B11-B31 broadcast on link 1 may include a current TSF value of AP 810 and a TSF offset between AP 810 and AP 820, and each of the second beacon frames B12-B32 broadcast on link 2 may include a current TSF value of AP 820 and a TSF offset between AP 820 and AP 810. In some instances, the TSF timer of AP 810 may be used as a reference for the TSF offset between AP 810 and AP 820, and the beacon interval associated with AP 810 (and therefore the corresponding transmission time TBTT(1)1-TBTT(3)1) may be used as a reference for the timing offset between AP 810 and AP 820.
[0100] exist Fig. 8A In the example of , AP 820 has a slower clock than AP 810 (or AP 810 has a faster clock than AP 820), which may cause the time offset between the beacon transmission time TBTT(1)1-TBTT(3)1 associated with AP 810 and the beacon transmission time TBTT(1)2-TBTT(3)2 associated with AP 820 to continue to increase. For example, when the transmission of the first beacon frame B11 on link 1 is aligned with the transmission of the first beacon frame B12 on link 2, the transmission of the second beacon frame B21 on link 1 occurs before the transmission of the second beacon frame B22 on link 2 by a time period equal to Δt, the transmission of the third beacon frame B31 on link 1 occurs before the transmission of the third beacon frame B32 on link 2 by a time period of Δ2t, and so on. Thus, beacon transmission times TBTT(1)1-TBTT(3)1 associated with AP 810 may occur increasingly earlier than beacon transmission times TBTT(1)2-TBTT(3)2 associated with AP 820.
[0101] Figure 8B A timing diagram 800B is shown depicting an example wireless communication between devices. The timing diagram 800B includes Fig. 8A AP 820 and STA 830. STA 830 can be any suitable device, such as Figure 1 STA 104 Figure 4 A wireless communication device 400, Figure 5B STA 504 or Figure 6In some implementations, the STA 830 may be part of a non-AP MLD configured to communicate over multiple different communication links. For example, although for simplicity in Figure 8B Only one STA 830 is shown in FIG. 8 , but the non-AP MLD may include one or more other STAs configured to operate on one or more other corresponding communication links.
[0102] exist Figure 8B In the example of FIG. 8 , STA 830 operates as a non-legacy STA on Link 2 and receives a Fig. 8A STA 830 obtains TSF information from beacon frames TBTT(1)1-TBTT(3)1 broadcasted by AP 810 on link 1. Specifically, STA 830 does not listen to and does not receive beacon frames TBTT(1)2-TBTT(3)2 broadcasted by AP 820 on link 2. Thus, STA 830 does not receive the current TSF value of AP 820 from the beacon frame transmission, and thus can estimate the current TSF value of AP 820 based on the current TSF value of AP 810 and the TSF offset between AP 810 and AP 820, for example, as indicated in beacon frames TBTT(1)2-TBTT(3)2 broadcasted by AP 820 on link 2.
[0103] AP 820 schedules r-TWT SP 840 on link 2 between times t4 and t6. Figure 8B In the example of , STA 830 is not a member of r-TWT SP 840 and therefore must end any TXOP obtained outside of r-TWT SP 840 before the start time of r-TWT SP 840, for example, as specified in the 802.11be revision to the IEEE 802.11 standard. As discussed, AP 820 has a slower clock than AP 810, and STA 830 synchronizes its local TSF timer based on the current TSF value of AP 810 obtained from beacon frames TBTT(1)1-TBTT(3)1 broadcast on link 1. The TSF offset between STA 830 and AP 820 (which includes the TSF offset between STA 830 and AP 820 and the TSF offset between AP 810 and AP 820) enables STA 830 to determine a start time of r-TWT SP 840 that is earlier than the start time determined by AP 820.
[0104] For example, after obtaining the current TSF value of AP 810 from the beacon frame transmission on link 1, STA 830 may perform a CCA operation on link 2. Specifically, between time t0 and t1, STA 830 senses that link 2 is idle for the AIFS duration, and counts down the RBO duration before attempting to obtain a TXOP on link 2. At time t1, STA 830 senses that link 2 is still idle, and obtains a TXOP on link 2. The TXOP obtained by STA 830 is longer than the duration remaining before the r-TWT SP 840 starts, and therefore STA 830 must end the TXOP before the r-TWT SP 840 on link 2 starts. As discussed, the TSF offset between STA 830 and AP 820 causes STA 830 to incorrectly determine that the start time of r-TWT SP 840 occurs at time t2, rather than at the correct start time, which occurs at time t4. Therefore, STA 830 ends the TXOP prematurely at time t2.
[0105] For example, existing rules regarding r-TWT SP allow non-member STAs (such as STA 830) to access the communication link before the start time of the r-TWT SP as long as the non-member STA ends any acquired TXOPs before the start of the r-TWT SP. Figure 8B In the example of FIG. 8 , after prematurely ending the TXOP at time t2, STA 830 senses that link 2 is idle for the AIFS+RBO duration between time t2 and t3, and obtains another TXOP 845 on link 2 at time t3. As discussed, STA 830 determines that r-TWT SP 840 starts at time t2 (rather than starting at time t4), and does not end TXOP 840. As shown, TXOP 845 spans the duration between time t3 and t5, thereby preventing any member STA from accessing link 2 during at least a portion of r-TWT SP 840.
[0106] Figure 8C Another timing diagram 850 depicting an example beacon frame transmission is shown. The timing diagram 850 shows Fig. 8AAPs 810 and 820 broadcast beacon frames on link 1 and link 2, respectively. Specifically, AP 810 broadcasts beacon frames B11-B31 on link 1 at corresponding times TBTT(1)1-TBTT(3)1, and AP 820 broadcasts beacon frames B12-B32 on link 2 at corresponding times TBTT(1)2-TBTT(3)2. Each of the beacon frames B11-B31 broadcast on link 1 may include a current TSF value of AP 810 and a TSF offset between AP 810 and AP 820, and each of the beacon frames B12-B32 broadcast on link 2 may include a current TSF value of AP 820 and a TSF offset between AP 820 and AP 810. As discussed, the TSF timer of AP810 can be used as a reference for the TSF offset between AP 810 and AP 820, and the beacon interval associated with AP 810 (and therefore the corresponding transmission time TBTT(1)1-TBTT(3)1) can be used as a reference for the timing offset between AP 810 and AP 820.
[0107] exist Figure 8C In the example of , AP 820 has a slower clock than AP 810 (or AP 810 has a faster clock than AP 820), which may cause beacon transmission times TBTT(1)1-TBTT(3)1 associated with AP 810 to occur at increasingly later times than corresponding beacon transmission times TBTT(1)2-TBTT(3)2 associated with AP 820. For example, when the respective transmissions of the first beacon frame B11 on link 1 and the first beacon frame B12 on link 2 are aligned with each other (and therefore have the same TBTT), the transmission of the second beacon frame B22 on link 2 occurs before the transmission of the second beacon frame B21 on link 1 by an offset = Δt, the transmission of the third beacon frame B32 on link 2 occurs before the transmission of the third beacon frame B31 on link 1 by an offset = Δ2t, and so on. Thus, the second beacon sending time TBTT(2)1 associated with link 1 occurs a time period equal to Δt after the corresponding second beacon sending time TBTT(2)2 associated with link 2, and the third beacon sending time TBTT(3)1 associated with link 1 occurs a time period equal to Δ2t after the corresponding third beacon sending time TBTT(3)2 associated with link 2.
[0108] Fig.8D A timing diagram 850B is shown depicting an example wireless communication between devices. The timing diagram 850B includes Figure 8C820 and STA 830. As discussed, STA 830 operates as a non-legacy STA on link 2 and obtains TSF information from beacon frames TBTT(1)1-TBTT(3)1 broadcast by AP 810 on link 1. STA 830 does not receive the current TSF value of AP 820 from the beacon frame transmission, but estimates the current TSF value of AP 820 based on the current TSF value of AP 810 and the TSF offset between AP 810 and AP 820, for example, as indicated in beacon frames TBTT(1)2-TBTT(3)2 broadcast by AP 820 on link 2.
[0109] AP 820 schedules r-TWT SP 860 on link 2 between times t2 and t6. Fig.8D In the example of , STA 830 is not a member of r-TWT SP 860, and therefore must end any TXOP obtained outside of r-TWT SP 860 before the start time of r-TWT SP 860. As discussed, AP 810 has a slower clock than AP 820, and STA 830 synchronizes its local TSF timer based on the current TSF value of AP 810 obtained from beacon frames TBTT(1)1-TBTT(3)1 broadcast on link 1. The TSF offset between STA 830 and AP 820 causes STA 830 to determine a start time of r-TWT SP 860 that is later than the start time determined by AP 820.
[0110] For example, after obtaining the current TSF value of AP 810 from the beacon frame transmission on link 1, STA 830 may perform a CCA operation on link 2. Specifically, between time t0 and t1, STA 830 senses that link 2 is idle within the AIFS duration, and counts down the RBO duration before attempting to obtain a TXOP on link 2. At time t1, STA 830 senses that link 2 is still idle, and obtains a TXOP on link 2. The TXOP obtained by STA 830 is longer than the duration remaining before the r-TWT SP 860 starts, and therefore STA 830 ends the TXOP at time t3 in an effort to comply with existing rules regarding r-TWT operations. However, because AP 810 has a slower clock than AP 820, the startup time of r-TWT SP 860 estimated by STA 830 (i.e., time t3) occurs after the correct startup time of r-TWT SP 860 (i.e., t2). Therefore, although STA 830 ends the TXOP early, the TXOP maintained by STA 830 overlaps with r-TWT SP 860 between time t2 and t3, thereby preventing any member STA from accessing link 2 during at least a portion of the r-TWT SP 860 spanning from time t2 to t3. Therefore, as discussed above, it is necessary to maintain stricter synchronization between the AP and the STAs associated with the AP, and more specifically between the STAs and the AP of the AP MLD to ensure that TSF offsets caused by clock drift do not cause non-member STAs to maintain a TXOP or attempt to obtain a TXOP during the r-TWT SP scheduled on the shared wireless medium.
[0111] Specific implementations of the subject matter described in the present disclosure may be used to synchronize the timing between a STA and an AP in a manner that prevents a STA operating on a communication link from inadvertently interfering with one or more r-TWT SPs scheduled on the communication link. Specifically, in various specific implementations, a device including a first AP may establish an enhanced synchronization mode, during which a participating STA receives timing information of one or more associated or nearby APs with sufficient periodicity to ensure that the TSF offset between the STA and the AP does not exceed a value that allows the STA to inadvertently access or occupy the shared wireless medium during the r-TWT SP scheduled on the shared wireless medium. For example, in some specific implementations, the device may send an indication of an enhanced synchronization mode to one or more STAs associated with the device on a first communication link associated with the first AP of the device. In some instances, the indication may be in response to the presence of a delay-sensitive service on the first communication link. In some other instances, the indication may be in response to a request from one or more STAs. In some aspects, the indication may also indicate the start time of the enhanced synchronization mode. In other aspects, the indication may also indicate whether participation in the enhanced synchronization mode is mandatory or voluntary for each of the one or more STAs.
[0112] During the enhanced synchronization mode, the device may send multiple synchronization frames on the first communication link more frequently than the TBTT associated with the first communication link. Each of the synchronization frames may indicate the TSF value of the first AP and the TSF offset between the first AP and the second AP of the device. The frequency of sending the synchronization frame on the first communication link may be associated with the timing accuracy level that prevents the participating STA from occupying or accessing the first communication link during one or more r-TWT SPs scheduled on the first communication link. For example, in some instances, the synchronization frames may be sent at intervals of approximately 20 μs (but other suitable intervals may be used). STAs participating in the enhanced synchronization mode may use the TSF information indicated in the synchronization frame to synchronize their respective local TSF timers with the TSF timers of the first AP and the second AP of the device, for example, without receiving a beacon frame from the second AP. In some specific implementations, the enhanced synchronization mode may be established in conjunction with one or more TWT SPs or r-TWT SPs on the first communication link. In some aspects, the device may reject association requests from STAs that do not support enhanced synchronization mode during a time period that begins before a start time of the enhanced synchronization mode and ends at a termination of the enhanced synchronization mode.
[0113] Fig. 9A timing diagram depicting an example wireless communication 900 supporting enhanced synchronization mode according to some specific implementations is shown. The wireless communication device 900 may be executed between an AP 910, an AP 920, and a STA 930. The APs 910 and 920 may be part of or associated with an AP MLD configured to communicate on a plurality of different communication links. Specifically, the AP 910 may be configured to operate on a first communication link, and the AP 920 may be configured to operate on a second communication link different from the first communication link. In some instances, the first communication link may be a wireless channel located in one of a 2.4 GHz band, a 5 GHz band, or a 6 GHz band, and the second communication link may be a wireless channel located in another of the 2.4 GHz band, the 5 GHz band, or the 6 GHz band.
[0114] In some implementations, APs 910 and 920 may be Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 An example of an AP MLD 610 and a STA 930 may be Figure 1 STA 104 Figure 4 A wireless communication device 400, Figure 5B STA 504 or Figure 6 930 is an example of any of the non-AP MLDs 620. Although not shown for simplicity, the STA 930 may be part of or associated with a STA MLD that includes one or more other STAs operable on one or more other communication links of the AP MLD.
[0115] exist Fig. 9In the example of , AP 910 establishes or schedules an enhanced synchronization mode for a STA operating on a first communication link, and STA 930 operates as a non-legacy STA supporting r-TWT SP operation. AP 910 sends a frame carrying an indication of the enhanced synchronization mode to STA 930 on the first communication link. The frame may be one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake-up time (TWT) response frame sent on the first communication link. In some specific implementations, the frame may also indicate whether participation in the enhanced synchronization mode is mandatory or voluntary for STA 930 (and for other STAs associated with the first communication link). For example, in some instances, AP 910 may obtain a TSF offset between a TSF timer of the AP and corresponding TSF timers of multiple STAs (including STA 930) operating on the first communication link, and may determine whether participation in the enhanced synchronization mode is mandatory or voluntary based at least in part on the TSF offset. In some aspects, whether participation in enhanced synchronization mode is mandatory or voluntary for at least some STAs may also be based on an indication of delay-sensitive traffic on the first communication link. For example, when there is delay-sensitive traffic on the first communication link, the AP 910 may be more likely to consider participation in enhanced synchronization mode to be mandatory.
[0116] AP 910 may also indicate to STA 930 the start time of the enhanced synchronization mode. In some aspects, the indicated start time may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame sent on the first communication link. STA 930 receives an indication of the enhanced synchronization mode, the start time of the enhanced synchronization mode, and whether STA 930's participation in the enhanced synchronization mode is mandatory or voluntary. Based on the indication of the enhanced synchronization mode, STA 930 may monitor multiple synchronization frames on the first communication link more frequently than the TBTT associated with the first communication link and / or prepare to receive multiple synchronization frames on the first communication link. STA 930 may start monitoring multiple synchronization frames and / or prepare to receive multiple synchronization frames (e.g., enter or initiate enhanced synchronization mode) based on the start time of the enhanced synchronization mode indicated by AP 910. When participation of the STA 930 in the enhanced synchronization mode is mandatory, the STA 930 may be prepared to receive, for example, a plurality of synchronization frames sent on the first communication link, and adjust the local TSF timer of the STA based on the received TSF information. When participation of the STA 930 in the enhanced synchronization mode is voluntary, the STA 930 may participate in the enhanced synchronization mode, for example, based on one or more of the following: the presence of delay-sensitive traffic on one or more communication links, an indication that the STA 930 is to receive or is associated with delay-sensitive traffic, an indication that the TSF offset between the STA 930 and the AP 910 is greater than a first amount, or an indication that the TSF offset between the STA 930 and the AP 920 is greater than a second amount, the second amount being different from the first amount.
[0117] In some instances, the AP 910 may indicate to the STA 930 whether the APs 910 and 920 share a common clock or a common TSF value across the APs 910 and 920. In some aspects, the indication of the common clock or the common TSF value is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a synchronization frame. The STA 930 receives the indication and may determine whether timing synchronization with the AP 920 is required. For example, if the APs 910 and 920 share the same clock or share the same TSF value, timing synchronization with both the APs 910 and 920 may be achieved based on synchronization between the respective TSF values of the AP 910 and the STA 930. For another example, if the APs 910 and 920 do not share the same clock or do not share the same TSF value, the STA 930 may voluntarily participate in an enhanced synchronization mode, for example, to ensure that the TSF offset between the STA 930 and each of the first AP 910 and the second AP 920 is less than a value.
[0118] During the enhanced synchronization mode, the AP 910 sends multiple synchronization frames on the first communication link more frequently than, for example, the TBTT associated with the first communication link, so that multiple synchronization frames can be sent to the STA 930 during each beacon interval of the AP 910. In various specific implementations, the synchronization frame can be a FILS discovery frame that can be sent on the first communication link at a data rate greater than the basic data rate associated with the beacon frame transmission from the AP 910. In some aspects, the AP 910 can send synchronization frames on the first communication link at intervals of approximately 20 milliseconds. In other aspects, the AP 910 can send synchronization frames on the first communication link at other suitable intervals that are shorter than the beacon interval of the AP 910. In some specific implementations, the AP 910 can establish an enhanced synchronization mode in conjunction with one or more TWT SPs or one or more r-TWT SPs scheduled on the first communication link.
[0119] In some implementations, each of the synchronization frames may indicate, for example, a TSF offset between the AP 910 and the AP 920, so that the STA 930 may synchronize the TSF timer of the STA with the current TSF values of the AP 910 and the AP 920. In some aspects, each of the plurality of synchronization frames may also indicate the TSF value of the AP 910. In some instances, the AP 910 may send an indication of the enhanced synchronization mode in response to the presence of delay-sensitive traffic on the first communication link. In other instances, the AP 910 may send an indication of the enhanced synchronization mode in response to a request from the STA 930 (or one or more other STAs associated with the first communication link).
[0120] In various aspects, the AP 910 may reject association requests from a legacy STA 940 that does not support the enhanced synchronization mode during a time period that begins before the start time of the enhanced synchronization mode and ends at or after the termination of the enhanced synchronization mode. For example, when the legacy STA 940 sends an association request frame to the AP 910 that includes a request for the AP 910 to perform association and authentication operations with the legacy STA 940, the AP 910 responds by sending an association response frame carrying a rejection of the association request to the legacy STA 940. In this way, the AP 910 may prevent legacy devices from gaining access to the first communication link during the enhanced synchronization mode. Rejecting such association requests during the enhanced synchronization mode may also prevent legacy devices that do not support r-TWT operations from attempting to obtain a TXOP that may interfere with the r-TWT SP scheduled on the first communication link.
[0121] In some implementations, the STA 930 may send a frame indicating one or more of the following to the AP 910: an amount of clock drift between at least one STA and the first AP during each beacon interval, whether the at least one STA participates in an enhanced synchronization mode, whether the at least one STA receives beacon frames on a first communication link or on a second communication link associated with a second AP, or the frequency with which the at least one STA receives beacon frames indicating TSF information of the first AP. The AP 910 receives the frame and may establish one or more TWT SPs or one or more r-TWT SPs for delay-sensitive services on the first communication link based at least in part on the one or more indications received from the at least one STA.
[0122] In some instances, the AP 910 may terminate the enhanced synchronization mode in response to an indication of timing synchronization between the first AP and each of the plurality of STAs participating in the enhanced synchronization mode. In some instances, one or more of the plurality of STAs may transmit the indication of timing synchronization to the AP 910. In some aspects, termination of the enhanced synchronization mode may be further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
[0123] Fig.10 A timing diagram 1000 is shown depicting an example wireless communication supporting enhanced synchronization mode according to some other implementations. The timing diagram 1000 includes reference FIG. 8A to FIG. 8B AP 810 and STA 830 described. As discussed, the TSF offset between STA 830 and AP 810 caused by clock drift may cause the STA to incorrectly estimate the start time of the r-TWT SP 1060 as time t2, rather than the correct start time t3. In some implementations, the AP 810 may obtain a time period associated with the TSF offset (e.g., the time offset between time t2 and t3), and may schedule a protection SP at the beginning of the r-TWT SP 1060. Specifically, the protection SP may span the time period between time t3 and t4, for example to prevent STA 830 from attempting to access link 1 during the r-TWT SP 1060. For example, the non-member STA 830 senses that link 1 is idle for the AIFS duration, and counts down the RBO duration from time t0 to t1 before attempting to obtain a TXOP. At time t1, the non-member STA 830 senses that link 1 is still idle, and obtains a TXOP on link 1. Figure 8BIn the example of , the TXOP obtained by the non-member STA 830 may be longer than the duration remaining before the r-TWT SP 860 starts, and the non-member STA 830 ends the TXOP at time t3 in an effort to comply with existing rules regarding r-TWT operations. However, because the clock of AP 810 is faster than the clock of AP 820, the start time t3 of the r-TWT SP 860 estimated by the non-member STA 830 occurs after the correct start time t4 of the r-TWT SP 860. Specifically, the TXOP truncated by the non-member STA 830 extends to the portion of the r-TWT SP 860 from time t2 to t3, thereby preventing any member STA from accessing link 1 during at least a portion of the r-TWT SP 860 spanning time t2 to t3.
[0124] Fig.11 A flow chart illustrating example operations 1100 for wireless communication supporting enhanced synchronization mode according to some implementations is shown. Operations 1100 may be performed by a wireless device (such as the wireless device described above). Figure 4 In some examples, operations 1100 may be performed by a wireless device operating as an AP or within an AP, such as a wireless device 400 described herein. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0125] For example, at 1102, the device sends an indication of an enhanced synchronization mode to at least one wireless station (STA) on a first communication link associated with a first access point (AP) of the device. At 1104, the device sends multiple synchronization frames more frequently than a target beacon transmission time (TBTT) associated with the first communication link during the enhanced synchronization mode on the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) value of the first AP and a TSF offset between the first AP and the second AP of the device. In some instances, the indication may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake-up time (TWT) response frame sent on the first communication link. In some aspects, the time period between consecutive transmissions of synchronization frames may be approximately 20 milliseconds. In other aspects, multiple synchronization frames may be sent at a data rate greater than a basic data rate associated with the transmission of beacon frames on the first communication link.
[0126] In some specific implementations, the device can be an AP multi-link device (MLD) including a first AP and a second AP, the first AP is associated with a first communication link, and the second AP is associated with a second communication link, and the second communication link occupies a different frequency band from the first communication link. In some instances, at least one of the multiple synchronization frames can be a fast initial link establishment (FILS) discovery frame carrying a TSF value of the first AP and a TSF offset value of the second AP. In various aspects, an indication of an enhanced synchronization mode may be sent based on an indication of a delay-sensitive service on at least the first communication link. In some aspects, the enhanced synchronization mode may be established in conjunction with one or more TWT service periods (SPs) scheduled on the first communication link or one or more restricted TWT (r-TWT) SPs.
[0127] Fig.12 1 is a flowchart illustrating example operations 1200 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 1200 may be performed by a wireless device (such as the wireless device described above). Figure 4 In some examples, operations 1200 may be performed by a wireless device operating as an AP or within an AP, such as a wireless device 400 described herein. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0128] In some examples, operation 1200 may be performed at Fig.11 The device may terminate the enhanced synchronization mode in response to an indication of timing synchronization between the first AP and each of the plurality of STAs participating in the enhanced synchronization mode. In some aspects, the termination of the enhanced synchronization mode is further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
[0129] Fig.13 1 is a flowchart illustrating example operations 1300 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 1300 may be performed by a wireless communication device (such as the one described above with reference to FIG. Figure 4 In some implementations, the operations 1300 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0130] In some examples, operation 1300 may be performed at Fig.11 The method may be performed before sending an indication of the enhanced synchronization mode at 1102. For example, at block 1302, the device receives a request to initiate the enhanced synchronization mode from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
[0131] Fig.14 A flow chart illustrating example operations 1400 for wireless communication supporting enhanced synchronization mode according to some implementations is shown. Operations 1400 may be performed by a wireless communication device (such as the one described above with reference to FIG. Figure 4 In some implementations, operations 1400 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0132] In some examples, operation 1400 may be performed at Fig.11 The method may be performed before sending a plurality of synchronization frames at 1104 of the device. For example, at block 1402, the device indicates to the at least one STA a start time of the enhanced synchronization mode. In some instances, the indicated start time may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame sent on the first communication link.
[0133] Fig.15 1 is a flowchart illustrating example operations 1500 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 1500 may be performed by a wireless communication device (such as the wireless communication device described above). Figure 4 In some implementations, the operations 1500 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0134] In some examples, operation 1500 may be performed at Fig.11The device may be configured to receive a first AP and each of the plurality of STAs from the first AP and / or the second AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP. The device may be configured to receive a first AP and / or the second AP from the first AP.
[0135] Fig.16 1 is a flowchart illustrating example operations 1600 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 1600 may be performed by a wireless communication device (such as the one described above with reference to FIG. Figure 4 In some implementations, the operations 1600 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0136] In some examples, operation 1600 may be performed at Fig.11 1100 is performed at any time before, during, or after operation 1100 of the device. For example, at box 1602, the device indicates to the at least one STA whether the first AP and the second AP share a common clock or a common TSF value across the first AP and the second AP of the device. In some instances, the indication of the common clock or the common TSF value across the first AP and the second AP of the device may be carried in one or more of a beacon frame, a probe response frame, and a broadcast action frame. In other instances, the indication of the common clock or the common TSF value across the first AP and the second AP may be carried in a synchronization frame. The at least one STA may use the indication to determine whether to use participation in the enhanced synchronization mode to maintain a certain level of timing synchronization with the second AP of the device. For example, if the first AP and the second AP of the device share a common clock or a common TSF value, there may not be any TSF offset between the first AP and the second AP of the device. Thus, the at least one STA may be able to maintain sufficient timing synchronization with the first AP to avoid interfering with the r-TWTSP without participating in the enhanced synchronization mode.
[0137] Fig.17 1 is a flowchart illustrating example operations 1700 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 1700 may be performed by a wireless communication device (such as the one described above with reference to FIG. Figure 4In some implementations, operations 1700 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0138] In some examples, operation 1700 may be performed at Fig.11 The device may be performed at any time during operation 1100 of . For example, at block 1702, the device rejects association requests from STAs that do not support the enhanced synchronization mode during a time period starting before the start time of the enhanced synchronization mode. For example, the device may reject association requests from legacy devices on the first communication link to prevent such legacy devices from being able to contend for access to the first communication link during any r-TWT SP scheduled on the first communication link.
[0139] Fig.18 A flowchart illustrating example operations 1800 for wireless communication supporting enhanced synchronization mode according to some implementations is shown. Operations 1800 may be performed by a wireless communication device (such as the wireless communication device described above). Figure 4 In some implementations, operations 1800 may be performed by a wireless communication device (such as a wireless communication device 400) operating as an AP or within an AP. Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 The AP MLD 610) is used for execution.
[0140] In some implementations, operation 1800 may be performed at Fig.11 The method may be performed at any time before, during, or after operation 1100 of . For example, at box 1802, the device receives a frame from the at least one STA indicating one or more of the following: an amount of clock drift between the at least one STA and the first AP during each beacon interval, whether the at least one STA participates in an enhanced synchronization mode, whether the at least one STA receives beacon frames on the first communication link or on a second communication link associated with the second AP, or the frequency with which the at least one STA receives beacon frames or synchronization frames indicating TSF information of the first AP. At 1804, the device schedules one or more TWT SPs or r-TWT SPs for delay-sensitive services on the first communication link based at least in part on the one or more indications received from the at least one STA.
[0141] Fig.19A flow chart illustrating example operations 1900 for wireless communication supporting enhanced synchronization mode according to some implementations is shown. Operations 1900 may be performed by a wireless device (such as the wireless device described above). Figure 4 In some examples, operations 1900 may be performed by a wireless device operating as a STA or within a STA, such as a wireless device 400. Figure 1 STA 104 Figure 4 A wireless communication device 400, Figure 5B STA 504 or Figure 6 The non-AP MLD 620) is used for execution.
[0142] For example, at 1902, the device receives an indication of an enhanced synchronization mode from a first AP on a first communication link associated with a first AP of an access point (AP) multi-link device (MLD). At 1904, the device receives multiple synchronization frames more frequently than a target beacon transmission time (TBTT) associated with the first communication link on the first communication link during the enhanced synchronization mode, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and the second AP of the AP MLD. In some specific implementations, each of the multiple synchronization frames may also indicate a TSF value of the first AP. In some instances, the indication may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame received on the first communication link. In some aspects, the time period between consecutive receptions of synchronization frames may be approximately 20 milliseconds. In other aspects, multiple synchronization frames may be received at a data rate greater than a basic data rate associated with the transmission of beacon frames on the first communication link.
[0143] In various specific implementations, the device may be a non-AP MLD including a plurality of STAs configured to operate on a plurality of corresponding communication links. In some instances, at least one of the plurality of synchronization frames may be a FILS discovery frame carrying a TSF value of a first AP. In various aspects, an indication of an enhanced synchronization mode may be received based on an indication of a delay-sensitive service on at least the first communication link. In some aspects, the enhanced synchronization mode may be established in conjunction with one or more TWT SPs or one or more r-TWT SPs scheduled on the first communication link.
[0144] In some implementations, the device can send a request to the AP MLD to initiate enhanced synchronization mode at 1906. In some examples, an indication of enhanced synchronization mode can be received from the AP MLD based on the request.
[0145] In other specific implementations, at 1908, the device may receive an indication of a start time of the enhanced synchronization mode from the AP MLD at 1908. In some instances, the indication of the enhanced synchronization mode may be received from the AP MLD based on the request. In some instances, the indicated start time may be carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a TWT response frame received on the first communication link.
[0146] In some other specific implementations, at 1910, the device may receive from the AP MLD an indication of whether participation in the enhanced synchronization mode is mandatory or voluntary for the device based at least in part on the TSF offset between the first AP and each of the plurality of STAs. In some instances, an indication of a common clock or a common TSF value across the first AP and the second AP of the device may be carried in one or more of a beacon frame, a probe response frame, or a broadcast action frame. In other instances, an indication of a common clock or a common TSF value across the first AP and the second AP may be carried in a synchronization frame. In some aspects, the device may use the indication to determine whether to use participation in the enhanced synchronization mode to maintain a certain level of timing synchronization with the second AP of the AP MLD. For example, if the first AP and the second AP of the AP MLD share a common clock or a common TSF value, there may not be any TSF offset between the first AP and the second AP of the AP MLD. Thus, the device may be able to maintain sufficient timing synchronization with the first AP to avoid interfering with the r-TWT SP without participating in the enhanced synchronization mode.
[0147] In some examples, at 1912, the device can receive an indication from the AP MLD whether the first AP and the second AP share a common clock or a common TSF value across the first AP and the second AP of the device.
[0148] Fig. 20 2 is a flowchart illustrating example operations 2000 for wireless communication supporting enhanced synchronization mode according to some implementations. Operations 2000 may be performed by a wireless communication device (such as the one described above with reference to FIG. Figure 4 In some implementations, the operations 2000 may be performed by a wireless device (such as a wireless device 400) operating as a STA or within a STA. Figure 1 STA 104 Figure 4 A wireless communication device 400, Figure 5B STA 504 or Figure 6 The non-AP MLD 620) is used for execution.
[0149] In some examples, operation 2000 may be performed at Fig.19, performed after operation 1900. For example, at 2002, the device sends a frame to the AP MLD indicating one or more of the following: an amount of clock drift between the device and the first AP during each beacon interval, whether the device participates in enhanced synchronization mode, whether the device receives beacon frames on a first communication link or on a second communication link associated with a second AP, or the frequency with which the device receives beacon frames or synchronization frames indicating TSF information of the first AP. At 2004, the device receives from the AP MLD an indication of one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs for delay-sensitive services on the first communication link based at least in part on one or more indications provided by the device.
[0150] Fig.21 1 shows a block diagram of an example wireless communication device 1900. In some implementations, the wireless communication device 2100 may be configured to perform respective references to Fig.12 , Fig.13 , Fig.14 , Fig.15 , Fig.16 , Fig.17 and Fig.18 The described operations 1200, 1300, 1400, 1500, 1600, 1700, and 1800. The wireless communication device 2100 may be Figure 1 AP 102 Figure 4 A wireless communication device 400, Figure 5A AP 502 or Figure 6 In some implementations, the wireless communication device 2100 may be an example of an AP MLD. More specifically, the wireless communication device 2100 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem).
[0151] The wireless communication device 2100 includes a receiving component 2110, a communication manager 2120, and a transmitting component 2130. The communication manager 2120 also includes an enhanced synchronization mode component 2121, a synchronization frame component 2122, a TSF offset component 2123, a multilink component 2124, and a TWT component 2125. Portions of one or more of the components 2121-2125 may be implemented at least in part in hardware or firmware. In some specific implementations, one or more of the components 2121-2125 are implemented at least in part as stored in a memory (such as Figure 4For example, parts of one or more of components 2121-2125 may be implemented as software that can be executed by a processor such as Figure 4 The processor 406 of the device 408 executes non-transitory instructions (or "code") to perform the functions or operations of the corresponding components.
[0152] The receiving component 2110 is configured to receive RX signals from one or more other wireless communication devices, and the sending component 2130 is configured to send TX signals to one or more other wireless communication devices. The communication manager 2120 is configured to manage wireless communication with one or more other wireless communication devices. In some specific implementations, the enhanced synchronization mode component 2121 can establish an enhanced synchronization mode on one or more communication links associated with the wireless communication device 2100. The synchronization frame component 2122 can send multiple synchronization frames to one or more other wireless communication devices (such as STA, non-AP MLD and client device). The TSF offset component 2123 can determine or obtain the TSF offset between multiple APs within or associated with the wireless communication device 2100. The multi-link component 2124 can establish multiple communication links associated with the wireless communication device 2100. The TWT component 2125 can schedule one or more TWT SPs or one or more r-TWT SPs for delay-sensitive services on one or more communication links associated with the wireless communication device 2100.
[0153] Fig. 22 1 shows a block diagram of an example wireless communication device 1900. In some implementations, the wireless communication device 2200 may be configured to perform respective references to Fig.19 and Fig. 20 The wireless communication device 2200 may be Figure 1 STA 104 Figure 4 A wireless communication device 400, Figure 5B STA 504 or Figure 6 620. In some implementations, the wireless communication device 2200 may be an example of a STA MLD. More specifically, the wireless communication device 2200 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem).
[0154] The wireless communication device 2200 includes a receiving component 2210, a communication manager 2220, and a sending component 2230. The communication manager 2220 also includes an enhanced synchronization mode component 2221, a synchronization frame component 2222, a TSF offset component 2223, a multilink component 2224, and a TWT component 2225. Portions of one or more of the components 2221-2225 may be implemented at least in part in hardware or firmware. In some specific implementations, one or more of the components 2221-2225 are implemented at least in part as stored in a memory (such as Figure 4 For example, parts of one or more of components 2221-2225 may be implemented as software that can be executed by a processor such as Figure 4 The processor 406 of the device 408 executes non-transitory instructions (or "code") to perform the functions or operations of the corresponding components.
[0155] The receiving component 2210 is configured to receive RX signals from one or more other wireless communication devices, and the sending component 2230 is configured to send TX signals to one or more other wireless communication devices. The communication manager 2220 is configured to manage wireless communications with one or more other wireless communication devices. In some specific implementations, the enhanced synchronization mode component 2221 can coordinate the participation of the wireless communication device 2200 in one or more enhanced synchronization modes established on the communication link. The synchronization frame component 2222 can receive multiple synchronization frames from one or more APs of the AP MLD. The TSF offset component 2223 can determine or obtain the TSF offset between the wireless communication device 2200 and one or more other devices. The multi-link component 2224 can establish multiple communication links associated with the wireless communication device 2200. The TWT component 2225 can schedule one or more TWT SPs or one or more r-TWT SPs for delay-sensitive services on one or more communication links associated with the wireless communication device 2200.
[0156] Specific implementation examples are described in the following numbered clauses:
[0157] 1. A device, comprising:
[0158] at least one processor; and
[0159] at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to:
[0160] An indication of an enhanced synchronization mode is sent to at least one wireless station (STA) on a first communication link associated with a first access point (AP) of the device; and during the enhanced synchronization mode, multiple synchronization frames are sent on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the device.
[0161] 2. The apparatus of clause 1, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value for the first AP.
[0162] 3. An apparatus according to any one or more of clauses 1 to 2, wherein the time period between consecutive transmissions of the synchronization frame is approximately 20 milliseconds.
[0163] 4. An apparatus as described in any one or more of clauses 1 to 3, wherein the plurality of synchronization frames are transmitted at a data rate greater than a basic data rate associated with beacon frame transmissions on the first communication link.
[0164] 5. A device according to any one or more of clauses 1 to 4, wherein the device includes an AP multi-link device (MLD), the AP multi-link device (MLD) includes the first AP and the second AP, the first AP is associated with the first communication link, the second AP is associated with a second communication link, and the second communication link occupies a frequency band different from that of the first communication link.
[0165] 6. An apparatus according to any one or more of clauses 1 to 5, wherein the indication is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame sent on the first communication link.
[0166] 7. The apparatus of any one or more of clauses 1 to 6, wherein execution of the processor readable code is further configured to:
[0167] The enhanced synchronization mode is terminated in response to an indication of timing synchronization between the first AP and each of a plurality of STAs participating in the enhanced synchronization mode.
[0168] 8. The apparatus of clause 7, wherein termination of the enhanced synchronization mode is further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
[0169] 9. An apparatus according to any one or more of clauses 1 to 8, wherein the indication of the enhanced synchronization mode is sent based on an indication of delay-sensitive traffic on at least the first communication link.
[0170] 10. The apparatus of any one or more of clauses 1 to 9, wherein execution of the processor readable code is further configured to:
[0171] A request to initiate the enhanced synchronization mode is received from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
[0172] 11. The apparatus of any one or more of clauses 1 to 10, wherein execution of the processor readable code is further configured to:
[0173] The start time of the enhanced synchronization mode is indicated to the at least one STA.
[0174] 12. An apparatus according to clause 11, wherein the indicated start time is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame sent on the first communication link.
[0175] 13. The apparatus of any one or more of clauses 1 to 12, wherein execution of the processor readable code is further configured to:
[0176] Obtaining a TSF offset between the first AP and each STA in a plurality of STAs; and
[0177] Whether participation in the enhanced synchronization mode is mandatory or voluntary is indicated to each of a plurality of STAs based at least in part on the TSF offset.
[0178] 14. The apparatus of clause 13, wherein whether participation in the enhanced synchronization mode is mandatory or voluntary for at least some of the plurality of STAs is further based on an indication of delay-sensitive traffic on the first communication link.
[0179] 15. An apparatus according to any one or more of clauses 1 to 14, wherein the enhanced synchronization mode is established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link.
[0180] 16. The apparatus of any one or more of clauses 1 to 15, wherein execution of the processor readable code is further configured to:
[0181] Indicating to the at least one STA whether the first AP and the second AP share a common clock or a common TSF value of the first AP and the second AP across the device.
[0182] 17. A device according to clause 16, wherein the indication of the common clock or the common TSF value of the first AP and the second AP across the device is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or the synchronization frame.
[0183] 18. The apparatus of any one or more of clauses 1 to 17, wherein execution of the processor readable code is further configured to:
[0184] Association requests from STAs that do not support the enhanced synchronization mode are rejected during a time period starting before a start time of the enhanced synchronization mode.
[0185] 19. The apparatus of any one or more of clauses 1 to 18, wherein execution of the processor readable code is further configured to:
[0186] receiving, from the at least one STA, a frame indicating one or more of the following:
[0187] an amount of clock drift between the at least one STA and the first AP during each beacon interval,
[0188] whether the at least one STA participates in the enhanced synchronization mode,
[0189] The at least one STA receives a beacon frame on the first communication link or on a second communication link associated with the second AP, or
[0190] A frequency at which the at least one STA receives a beacon frame or a synchronization frame indicating TSF information of the first AP; and
[0191] One or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs for delay-sensitive services on the first communication link are scheduled based at least in part on one or more indications received from the at least one STA.
[0192] 20. A method for wireless communication by a device, the method comprising:
[0193] sending an indication of an enhanced synchronization mode to at least one wireless station (STA) over a first communication link associated with a first access point (AP) of the device; and
[0194] During the enhanced synchronization mode, multiple synchronization frames are sent on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the device.
[0195] 21. The method of clause 20, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value for the first AP.
[0196] 22. A method according to any one or more of clauses 20 to 21, wherein the device includes an AP multi-link device (MLD), the AP multi-link device (MLD) includes the first AP and the second AP, the first AP is associated with the first communication link, the second AP is associated with a second communication link, and the second communication link occupies a frequency band different from the first communication link.
[0197] 23. A method according to any one or more of clauses 20 to 22, wherein the indication of the enhanced synchronization mode is sent based on an indication of delay sensitive traffic on at least the first communication link.
[0198] 24. The method according to any one or more of clauses 20 to 23, further comprising:
[0199] A request to initiate the enhanced synchronization mode is received from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
[0200] 25. The method according to any one or more of clauses 20 to 24, further comprising:
[0201] The start time of the enhanced synchronization mode is indicated to the at least one STA.
[0202] 26. The method according to any one or more of clauses 20 to 25, further comprising:
[0203] Obtaining a TSF offset between the first AP and each STA in a plurality of STAs; and
[0204] Whether participation in the enhanced synchronization mode is mandatory or voluntary is indicated to each of a plurality of STAs based at least in part on the TSF offset.
[0205] 27. The method of clause 26, wherein whether participation in the enhanced synchronization mode is mandatory or voluntary for at least some of the plurality of STAs is further based on an indication of delay-sensitive traffic on the first communication link.
[0206] 28. A method according to any one or more of clauses 20 to 27, wherein the enhanced synchronization mode is established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link.
[0207] 29. The method according to any one or more of clauses 20 to 28, further comprising:
[0208] Indicating to the at least one STA whether the first AP and the second AP share a common clock or a common TSF value of the first AP and the second AP across the device.
[0209] 30. The method according to any one or more of clauses 20 to 29, further comprising:
[0210] receiving, from the at least one STA, a frame indicating one or more of the following:
[0211] an amount of clock drift between the at least one STA and the first AP during each beacon interval,
[0212] whether the at least one STA participates in the enhanced synchronization mode,
[0213] The at least one STA receives a beacon frame on the first communication link or on a second communication link associated with the second AP, or
[0214] A frequency at which the at least one STA receives a beacon frame or a synchronization frame indicating TSF information of the first AP; and
[0215] One or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs for delay-sensitive services on the first communication link are scheduled based at least in part on one or more indications received from the at least one STA.
[0216] 31. A device, comprising:
[0217] at least one processor; and
[0218] at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to:
[0219] receiving an indication of enhanced synchronization mode from a first access point (AP) multi-link device (MLD) over a first communication link associated with the first AP; and
[0220] During the enhanced synchronization mode, multiple synchronization frames are received on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the AP MLD.
[0221] 32. The apparatus of clause 31, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value for the first AP.
[0222] 33. Apparatus according to any one or more of clauses 31 to 32, wherein the time period between successive receptions of the synchronization frames is approximately 20 milliseconds.
[0223] 34. An apparatus as described in any one or more of clauses 31 to 33, wherein the plurality of synchronization frames are received at a data rate greater than a basic data rate associated with beacon frame transmissions on the first communication link.
[0224] 35. An apparatus as described in any one or more of clauses 31 to 34, wherein the indication is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame received on the first communication link.
[0225] 36. Apparatus according to any one or more of clauses 31 to 35, wherein the indication of the enhanced synchronization mode is received based on an indication of delay sensitive traffic on at least the first communications link.
[0226] 37. An apparatus according to any one or more of clauses 31 to 36, wherein execution of the processor readable code is further configured to:
[0227] A request to initiate the enhanced synchronization mode is sent to the AP MLD, wherein the indication of the enhanced synchronization mode is received based on the request.
[0228] 38. The apparatus of any one or more of clauses 31 to 37, wherein execution of the processor readable code is further configured to:
[0229] An indication of a start time of the enhanced synchronization mode is received from the AP MLD.
[0230] 39. An apparatus according to clause 38, wherein the indicated start time is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame received on the first communication link.
[0231] 40. The apparatus of any one or more of clauses 31 to 39, wherein execution of the processor readable code is further configured to:
[0232] An indication is received from the APMLD as to whether participation in the enhanced synchronization mode is mandatory or voluntary for the device based at least in part on a TSF offset between the first AP and each of a plurality of STAs.
[0233] 41. The apparatus of clause 40, wherein whether participation in the enhanced synchronization mode is mandatory or voluntary for the apparatus is further based on an indication of delay-sensitive traffic on the first communication link.
[0234] 42. An apparatus according to any one or more of clauses 31 to 41, wherein the enhanced synchronization mode is established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link.
[0235] 43. The apparatus of any one or more of clauses 31 to 42, wherein execution of the processor readable code is further configured to:
[0236] An indication is received from the AP MLD as to whether the first AP and the second AP share a common clock or a common TSF value for the first AP and the second AP across the device.
[0237] 44. The device of clause 43, wherein the indication of the common clock or the common TSF value for the first AP and the second AP across the device is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or the synchronization frame.
[0238] 45. The apparatus of any one or more of clauses 31 to 44, wherein execution of the processor readable code is further configured to:
[0239] Sending a frame to the AP MLD indicating one or more of the following:
[0240] an amount of clock drift between the device and the first AP during each beacon interval,
[0241] whether the device participates in the enhanced synchronization mode,
[0242] whether the device receives a beacon frame on the first communication link or on a second communication link associated with the second AP, or
[0243] A frequency at which the device receives a beacon frame or a synchronization frame indicating TSF information of the first AP; and
[0244] Receiving from the AP MLD an indication of one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs for delay-sensitive services on the first communication link based at least in part on one or more indications provided by the device.
[0245] 46. A method for wireless communication by a device, the method comprising:
[0246] receiving an indication of enhanced synchronization mode from a first access point (AP) multi-link device (MLD) over a first communication link associated with the first AP; and
[0247] During the enhanced synchronization mode, multiple synchronization frames are received on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the AP MLD.
[0248] 47. The method of clause 46, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value for the first AP.
[0249] 48. A method according to any one or more of clauses 46 to 47, wherein the time period between successive transmissions of the synchronization frames is approximately 20 milliseconds.
[0250] 49. A method as described in any one or more of clauses 46 to 48, wherein the plurality of synchronization frames are received at a data rate greater than a base data rate associated with beacon frame transmissions on the first communications link.
[0251] 50. A method according to any one or more of clauses 46 to 49, wherein the indication is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame or a target wake time (TWT) response frame received on the first communication link.
[0252] 51. A method as described in any one or more of clauses 46 to 50, wherein the indication of the enhanced synchronization mode is received based on an indication of delay sensitive traffic on at least the first communication link.
[0253] 52. The method according to any one or more of clauses 46 to 51, further comprising:
[0254] A request to initiate the enhanced synchronization mode is sent to the AP MLD, wherein the indication of the enhanced synchronization mode is received based on the request.
[0255] 53. The method according to any one or more of clauses 46 to 52, further comprising:
[0256] An indication of a start time of the enhanced synchronization mode is received from the AP MLD.
[0257] 54. A method according to clause 53, wherein the indicated start time is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame received on the first communication link.
[0258] 55. The method according to any one or more of clauses 46 to 54, further comprising:
[0259] An indication is received from the APMLD as to whether participation in the enhanced synchronization mode is mandatory or voluntary for the device based at least in part on a TSF offset between the first AP and each of a plurality of STAs.
[0260] 56. The method of clause 55, wherein whether participation in the enhanced synchronization mode is mandatory or voluntary for the device is further based on an indication of delay-sensitive traffic on the first communication link.
[0261] 57. A method according to any one or more of clauses 46 to 56, wherein the enhanced synchronization mode is established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link.
[0262] 58. The method according to any one or more of clauses 46 to 57, further comprising:
[0263] An indication is received from the AP MLD as to whether the first AP and the second AP share a common clock or a common TSF value for the first AP and the second AP across the device.
[0264] 59. A method according to clause 58, wherein the indication of the common clock or the common TSF value of the first AP and the second AP across the device is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or the synchronization frame.
[0265] 60. The method according to any one or more of clauses 46 to 59, further comprising:
[0266] Sending a frame to the AP MLD indicating one or more of the following:
[0267] an amount of clock drift between the device and the first AP during each beacon interval,
[0268] whether the device participates in the enhanced synchronization mode,
[0269] whether the device receives a beacon frame on the first communication link or on a second communication link associated with the second AP, or
[0270] A frequency at which the device receives a beacon frame or a synchronization frame indicating TSF information of the first AP; and
[0271] receiving, from the APMLD, one or more target wake time (TWT) service periods (SPs) or one or more restricted TWTs (r-TWTs) for delay-sensitive traffic on the first communication link based at least in part on one or more indications provided by the device;
[0272] TWT)SP instructions.
[0273] As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c. As used herein, "based on" is intended to be interpreted in an inclusive sense unless otherwise expressly indicated. For example, "based on" can be used interchangeably with "based at least in part on," unless otherwise expressly indicated. Specifically, unless the phrase in the context refers to "based only on 'one'" or an equivalent, whether it is "based on 'one'" or "based at least in part on 'one'" can be based on "one" alone or on a combination of "one" and one or more other factors, conditions, or information.
[0274] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of their functionality and exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.
[0275] Various modifications to the specific implementations described in this disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.
[0276] Additionally, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, individual features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subcombination. Thus, although features may be described above as functioning in a particular combination, and even initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and a claimed combination may be directed to a subcombination or a variation of a subcombination.
[0277] Similarly, although operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart or a flow diagram. However, other operations not depicted can be incorporated into the example processes schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously or between any operations in the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of each system component in the specific implementation described above should not be understood as requiring such separation in all specific implementations, but it should be understood as described program components and systems can usually be integrated together in a single software product, or be packaged in multiple software products.
Claims
1. A device, comprising: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to: sending an indication of an enhanced synchronization mode to at least one wireless station (STA) over a first communication link associated with a first access point (AP) of the device; as well as During the enhanced synchronization mode, multiple synchronization frames are sent on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the device.
2. The apparatus of claim 1, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value of the first AP.
3. The apparatus of claim 1, wherein a time period between successive transmissions of the synchronization frame is approximately 20 milliseconds.
4. The apparatus of claim 1, wherein the plurality of synchronization frames are transmitted at a data rate greater than a base data rate associated with beacon frame transmissions on the first communication link.
5. The device of claim 1, wherein the device comprises an AP multi-link device (MLD), the AP multi-link device (MLD) comprising the first AP and the second AP, the first AP being associated with the first communication link, the second AP being associated with a second communication link, the second communication link occupying a frequency band different from that of the first communication link.
6. The apparatus of claim 1, wherein the indication is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame sent on the first communication link.
7. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: The enhanced synchronization mode is terminated in response to an indication of timing synchronization between the first AP and each of a plurality of STAs participating in the enhanced synchronization mode.
8. The apparatus of claim 7, wherein termination of the enhanced synchronization mode is further based on an indication of timing synchronization between the second AP and each of the plurality of STAs participating in the enhanced synchronization mode.
9. The apparatus of claim 1, wherein the indication of the enhanced synchronization mode is sent based on an indication of delay-sensitive traffic on at least the first communication link.
10. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: A request to initiate the enhanced synchronization mode is received from one or more STAs, wherein the indication of the enhanced synchronization mode is sent based on the request.
11. The apparatus of claim 1 , wherein execution of the processor readable code is further configured to: A start time of the enhanced synchronization mode is indicated to the at least one STA.
12. The apparatus of claim 11, wherein the indicated start time is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame sent on the first communication link.
13. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: Obtaining a TSF offset between the first AP and each STA in a plurality of STAs; and Based at least in part on the TSF offset, indicating to each of a plurality of STAs whether participation in the enhanced synchronization mode is mandatory or voluntary.
14. The apparatus of claim 13, wherein whether participation in the enhanced synchronization mode is mandatory or voluntary for at least some of the plurality of STAs is further based on an indication of delay-sensitive traffic on the first communication link.
15. The apparatus of claim 1, wherein the enhanced synchronization mode is established in conjunction with one or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs scheduled on the first communication link.
16. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: Indicating to the at least one STA whether the first AP and the second AP share a common clock or a common TSF value of the first AP and the second AP across the device.
17. The device of claim 16, wherein the indication of the common clock or the common TSF value of the first AP and the second AP across the device is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or the synchronization frame.
18. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: Association requests from STAs that do not support the enhanced synchronization mode are rejected during a time period starting before a start time of the enhanced synchronization mode.
19. The apparatus of claim 1, wherein execution of the processor readable code is further configured to: receiving, from the at least one STA, a frame indicating one or more of the following: an amount of clock drift between the at least one STA and the first AP during each beacon interval, whether the at least one STA participates in the enhanced synchronization mode, The at least one STA receives a beacon frame on the first communication link or on a second communication link associated with the second AP, or A frequency at which the at least one STA receives a beacon frame or a synchronization frame indicating TSF information of the first AP; and One or more target wake time (TWT) service periods (SPs) or one or more restricted TWT (r-TWT) SPs for delay-sensitive services on the first communication link are scheduled based at least in part on one or more indications received from the at least one STA.
20. A method for wireless communication by a device, the method comprising: sending an indication of an enhanced synchronization mode to at least one wireless station (STA) over a first communication link associated with a first access point (AP) of the device; as well as During the enhanced synchronization mode, multiple synchronization frames are sent on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the device.
21. A device, comprising: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to: receiving an indication of an enhanced synchronization mode from a first access point (AP) multi-link device (MLD) over a first communication link associated with the first AP; as well as During the enhanced synchronization mode, multiple synchronization frames are received on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the AP MLD.
22. The apparatus of claim 21, wherein at least one of the plurality of synchronization frames comprises a Fast Initial Link Setup (FILS) discovery frame carrying a TSF value of the first AP.
23. The apparatus of claim 21, wherein a time period between successive receptions of the synchronization frames is approximately 20 milliseconds.
24. The apparatus of claim 21, wherein the plurality of synchronization frames are received at a data rate greater than a base data rate associated with beacon frame transmissions on the first communication link.
25. The apparatus of claim 21, wherein the indication is carried in one or more of a beacon frame, a probe response frame, a broadcast action frame, or a target wake time (TWT) response frame received on the first communication link.
26. The apparatus of claim 21, wherein the indication of the enhanced synchronization mode is received based on an indication of delay-sensitive traffic on at least the first communications link.
27. The apparatus of claim 21, wherein execution of the processor readable code is further configured to: A request to initiate the enhanced synchronization mode is sent to the AP MLD, wherein the indication of the enhanced synchronization mode is received based on the request.
28. The apparatus of claim 21, wherein execution of the processor readable code is further configured to: An indication of a start time of the enhanced synchronization mode is received from the AP MLD.
29. The apparatus of claim 21, wherein execution of the processor readable code is further configured to: An indication is received from the AP MLD as to whether the first AP and the second AP share a common clock or a common TSF value for the first AP and the second AP across the AP MLD.
30. A method for wireless communication by a device, the method comprising: receiving an indication of an enhanced synchronization mode from a first access point (AP) multi-link device (MLD) over a first communication link associated with the first AP; as well as During the enhanced synchronization mode, multiple synchronization frames are received on the first communication link more frequently than a target beacon transmit time (TBTT) associated with the first communication link, each of the multiple synchronization frames indicating a timing synchronization function (TSF) offset between the first AP and a second AP of the AP MLD.
Citation Information
Patent Citations
Time synchronization over a wireless network for latency-sensitive traffic
US20230328669A1
