Network allocation vector setting and updating during transmit opportunity

Abstract

The invention relates to network allocation vector setting and updating during a transmit opportunity. An apparatus is configured to generate, for transmission, an initial control frame (ICF) for a transmit opportunity (TXOP), the initial control frame (ICF) including a first duration set based on a time required by a TXOP responder station to respond to the ICF with an initial control response (ICR) and a short inter-frame spacing (SIFS), and a second duration set based on a time required by the TXOP responder station to respond to the ICF with a short inter-frame spacing (SIFS). And wherein the second duration is set based on a time required to transmit data to the TXOP responder site; processing the ICR based on a signaling received from the TXOP responder station; and generating one or more data transmissions during the TXOP for transmission to the TXOP responder site.

Description

[0001] Priority / Citation

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 700,164, filed September 27, 2024, entitled “Network Allocation Vector Setting and Updating During a Transmission Opportunity,” the entire contents of which are incorporated herein by reference. Background Technology

[0003] IEEE 802.11 networks can operate using both sites with the latest IEEE 802.11 communication protocol and sites operating using the legacy IEEE 802.11 communication protocol. Because the latest IEEE 802.11 communication protocol typically improves site performance, there may be scenarios where sites operating using the legacy IEEE 802.11 communication protocol are treated unfairly within the network. Since the IEEE 802.11 communication protocol aims for backward compatibility, such unfair treatment of legacy sites should be avoided. Summary of the Invention

[0004] Some example embodiments relate to an apparatus having processing circuitry coupled to a memory, wherein the processing circuitry is configured to: generate an initial control frame (ICF) for transmission opportunity (TXOP) for transmission, the initial control frame (ICF) including a first duration and a second duration, wherein the first duration is set based on the time required for a TXOP responder site to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS), and wherein the second duration is set based on the time required to transmit data to the TXOP responder site; process the ICR based on signaling received from the TXOP responder site; and generate one or more data transmissions during the TXOP for transmission to the TXOP responder site.

[0005] Other example embodiments relate to an apparatus having processing circuitry coupled to a memory, wherein the processing circuitry is configured to: process an initial control frame (ICF) for a TXOP based on signaling received from a transmission opportunity (TXOP) holder site, the initial control frame (ICF) including a first duration and a second duration, wherein the first duration is set based on the time required to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS), and wherein the second duration is set based on the time required for the TXOP holder site to transmit data; generate the ICR for transmission to the TXOP holder site, wherein the ICR includes the second duration; and process one or more data transmissions during the TXOP based on signaling received from the TXOP holder site.

[0006] Another example embodiment relates to an apparatus having processing circuitry coupled to a memory, wherein the processing circuitry is configured to: process an initial control frame (ICF) for a TXOP designated for a TXOP responder site based on signaling received from a transmit opportunity (TXOP) holder site, the ICF including a first duration and a second duration, wherein the apparatus is not the TXOP responder site, wherein the first duration is set based on the time required to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS), and wherein the second duration is set based on the time required for the TXOP holder site to transmit data to the TXOP responder site; and set a network allocation vector (NAV) duration based on the first duration and the second duration, wherein the apparatus does not contend for the channel during the NAV duration.

[0007] The additional example embodiment relates to an apparatus having processing circuitry coupled to a memory, wherein the processing circuitry is configured to: process an Initial Response Frame (ICR) for a TXOP designated for a TXOP holder station based on signaling received from a Transmission Opportunity (TXOP) responder station, the TXOP being designated for a TXOP holder station, the ICR including a first duration, wherein the apparatus is not the TXOP holder station, wherein the first duration is set based on the time required for the TXOP holder station to transmit data to the TXOP responder station; and set a Network Allocation Vector (NAV) duration based on the first duration, wherein the apparatus does not contend for the channel during the NAV duration.

[0008] Further example embodiments relate to an apparatus having processing circuitry coupled to a memory, wherein the processing circuitry is configured to: process an initial control frame (ICF) for a TXOP designated for a TXOP responder site based on signaling received from a TXOP holder site, the TXOP including a first duration, wherein the apparatus is not the TXOP responder site, wherein the first duration is set based on the time required to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS); and set a network allocation vector (NAV) duration based on the first duration, wherein the apparatus does not contend for the channel during the NAV duration. Attached Figure Description

[0009] Figure 1 An example arrangement of components in an 802.11 network according to various example implementations is shown.

[0010] Figure 2 It shows Figure 1 Example timing diagram of uplink transmission in example layout.

[0011] Figure 3 An example arrangement of components in an 802.11 network according to various example implementations is shown.

[0012] Figure 4 It shows Figure 3 Example timing diagram of downlink transmission in example layout.

[0013] Figure 5 Example sequence diagrams are shown, illustrating a first site as the TXOP holder and a second site as the TXOP responder, based on various example implementations.

[0014] Figure 6 An example layout including multiple sites is shown according to various example implementation schemes.

[0015] Figure 7 Example timing diagrams are shown for communication between TXOP holders and TXOP responders when other sites are 802.11bn sites, according to various example implementations.

[0016] Figure 8 Example timing diagrams are shown illustrating communication between TXOP holders and TXOP responders when other sites are traditional sites, according to various example implementation schemes.

[0017] Figure 9 Example timing diagrams are shown illustrating communication between TXOP holders and TXOP responders when other sites are 802.11bn sites and the Network Allocation Vector (NAV) is updated, according to various example implementations.

[0018] Figure 10 Example wireless communication devices according to various example implementation schemes are shown. Detailed Implementation

[0019] The example implementation can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The example implementation relates to setting or resetting the Network Assignment Vector (NAV) of a third-party site based on information included in the Initial Control Frame (ICF) of the Transmission Opportunity (TXOP), the Initial Control Response (ICR) of the TXOP, or the data transmission of the TXOP. The example implementation provides operations for setting the NAV by both legacy sites and current sites.

[0020] Referring to the example implementation described in IEEE 802.11, IEEE 802.11 provides a communication protocol for devices to communicate via a wireless connection. Multiple versions of the 802.11 protocol exist (e.g., 802.11ax, 802.11be, 802.11bn, etc.). References to 802.11 in the example implementation may refer to any version of the 802.11 protocol unless a specific version is identified in the description.

[0021] The exemplary embodiments are described with reference to wireless communication devices. Generally, a wireless communication device in an 802.11 network may be referred to as a station (or STA). In the example embodiments, a station may refer to an endpoint device, such as a mobile phone, tablet, desktop computer, smartphone, embedded device, wearable device, Internet of Things (IoT) device, video game controller, media player, entertainment device, smart speaker, smart TV, streaming media device, etc. The station may also refer to an intermediate point in an 802.11 network, including access points (APs), routers, switches, etc. Therefore, any reference to a station or wireless communication device in the example embodiments may refer to any device capable of wireless communication using the 802.11 protocol.

[0022] Referring to the example implementation described in IEEE 802.11, IEEE 802.11 provides a communication protocol for devices to communicate via wireless connections. Multiple versions of the 802.11 protocol exist (e.g., 802.11ax, 802.11be, 802.11bn, etc.). References to 802.11 in the example implementation may refer to any version of the 802.11 protocol unless a specific version is identified in the description. In the description, the current protocol may be considered the 802.11bn version. Other versions may be considered legacy versions. However, as the 802.11 standard evolves, new versions may exist, and the example implementation can also be applied to these newer versions.

[0023] Reference is also made to various duration descriptions of example implementations. Some example implementations and figures illustrate specific time values ​​for these durations. These specific time values ​​are merely examples for illustrative purposes. Other time values ​​may be present for the various durations when implementing the example implementations.

[0024] The example implementation provides an operation for a third-party site to set up a NAV based on information included in the ICF, ICR, or data transmission of the TXOP holder or TXOP responder. Specifically, the ICF, ICR, or data transmission may include one or more durations in the Media Access Control (MAC) header or Physical (PHY) layer header, which the third-party site can use to set up the NAV. This NAV setting may include initial setting of the NAV for a TXOP, setting of multiple NAVs during a TXOP (e.g., for a legacy site), or resetting the NAV. The NAV setting can be applied differentially to sites operating using the current version of the 802.11 communication protocol and sites operating using a legacy version of the 802.11 communication protocol. Each of these example aspects will be described in more detail below.

[0025] Figure 1 An example arrangement 100 of components in an 802.11 network according to various example implementations is shown. Arrangement 100 includes an 802.11bn site 110, an 802.11ax / be site 120, an 802.11bn AP 130, an Overlay Basic Services Set (OBSS) AP 140, and an OBSS site 150. This example arrangement illustrates an uplink (UL) scenario in which the 802.11bn site 110 attempts to transmit data to the 802.11bn AP 130.

[0026] Example arrangement 100 illustrates sites 110 to 140 communicating using an 802.11 access network. Sites 110 to 140 can represent any type of electronic component capable of wireless communication using the 802.11 communication protocol. Specific examples include, but are not limited to, mobile phones, tablets, desktop computers, smartphones, embedded devices, wearable devices, Internet of Things (IoT) devices, video game controllers, media players, entertainment devices, smart speakers, smart TVs, streaming media devices, etc. Sites 110 to 140 can include access points (APs), routers, switches, etc. Therefore, sites 110 to 140 can have Industrial, Scientific, and Medical (ISM) chipsets for communicating using the 802.11 communication protocol. Any association process can be performed to interconnect sites 110 to 140 within the 802.11 access network 130.

[0027] Figure 2 It shows Figure 1Example timing diagram 200 for uplink transmission in the example setup. As described above, uplink transmission occurs between 802.11bn site 110 and 802.11bn AP 130. Figure 1 In the configuration 100, the 802.11bn site 110 and the 802.11ax / be site 120 may be hidden from OBSS transmission; for example, they may be unaware that an OBSS transmission is occurring. After the backoff period, the 802.11bn site 110 may send an Initial Control Frame (ICF) 210 to the 802.11bn AP 130 to initiate a Transmission Opportunity (TXOP). However, due to the OBSS transmission, the 802.11bn AP 130 may not respond with an Initial Control Response (ICR), such as... Figure 2 As shown.

[0028] In this scenario, 802.11ax / be site 120 can set the Network Allocation Vector (NAV) 220 based on ICF 210. The NAV is the period during which 802.11ax / be site 120 can avoid contention for the channel, because 802.11ax / be site 120 assumes that 802.11bn site 110 will transmit during duration 230, which is set based on the information in ICF 210. On the other hand, 802.11bn site 110 and 802.11bn AP 130 can implement NAV reset for ICF 210. This means that 802.11bn site 110 and 802.11bn AP 130 can access the medium during duration 23 after 802.11bn AP 130 fails to respond to ICF 210 with ICR. Figure 2 In the example, the media access is shown as a downlink transmission from 802.11bn AP 130 to 802.11bn site 110. For example, 802.11bn AP 130 sends ICF 240 to 802.11bn site 110 to initiate a TXOP. The TXOP responder, 802.11bn site 110, responds with ICR 250. Then, the TXOP holder, 802.11bn AP 130, sends data 260 (e.g., Physical Layer Protocol Data Unit (PPDU)) to 802.11bn site 110, which then responds with Block Acknowledgment (BA) 270.

[0029] Therefore, in this scenario, 802.11bn site 110 and 802.11bn AP 130 may have more opportunities to access the medium, resulting in performance degradation for other legacy 11ax / be sites (e.g., 802.11ax / be site 120) that do not have NAV reset capability for ICF.

[0030] Figure 3 An example arrangement 300 of components in an 802.11 network according to various example implementations is shown. Arrangement 300 again includes 802.11bn site 110, 802.11ax / be site 120, 802.11bn AP 130, OBSS AP 140, and OBSS site 150. This example arrangement illustrates a downlink (DL) scenario in which 802.11bn AP 130 attempts to transmit data to 802.11bn site 110.

[0031] Figure 4 It shows Figure 3 Example timing diagram 400 for downlink transmission in the example deployment. As described above, downlink transmission occurs between 802.11bn AP 130 and 802.11bn site 110. Figure 1 In the deployment 300, the 802.11bn AP 130 may be hidden from OBSS transmissions; for example, the 802.11bn AP 130 may be unaware that an OBSS transmission is occurring. After the backoff period, the 802.11bn AP 130 may send an ICF 410 to the 802.11bn site 110 to initiate a TXOP. However, due to the OBSS transmission, the 802.11bn site 110 may not respond with an ICR, such as... Figure 4 As shown.

[0032] In this scenario, 802.11ax / be site 120 can configure Network Assignment Vector (NAV) 420 based on ICF 410. Similarly, 802.11bn site 110 and 802.11bn AP 130 can perform NAV resets for ICF 210. This means that 802.11bn site 110 and 802.11bn AP 130 can access the medium for duration 430 after 802.11bn site 110 fails to respond to ICF 410 with an ICR. Figure 4In the example, this media access is shown as a downlink transmission from 802.11bn AP 130 to 802.11bn site 110. For example, 802.11bn AP 130 transmits ICF 440 to 802.11bn site 110. 802.11bn site 110 responds with ICR 450. Then, 802.11bn AP 130 sends data 460 (e.g., PPDU) to 802.11bn site 110, which then responds with BA 470.

[0033] Therefore, in the same scenario, 802.11bn site 110 and 802.11bn AP 130 may have more opportunities to access the medium, resulting in performance degradation for other legacy 11ax / be sites (e.g., 802.11ax / be site 120) that do not have NAV reset capability for ICF.

[0034] The example implementation involves operations that address the problems described above. Specifically, the example implementation involves incremental NAV updates based on timing information included in the ICF and ICR. See below for reference. Figures 5 to 9 The example implementation scheme is described in more detail.

[0035] Figure 5 An example timing diagram 500 is shown, illustrating a first site 502 as a TXOP holder and a second site 504 as a TXOP responder according to various example implementations. Figure 5 In the example, a TXOP holder site 502 can be an AP site or a non-AP site. Similarly, a TXOP responder site 504 can be an AP site or a non-AP site. This will be described in more detail below. Figure 5 In the example above, the exchange between TXOP holder 502 and TXOP responder 504 was successful. Therefore, the above is relative to... Figure 2 and Figure 4 The described problem may not occur because the original TXOP responder responds with an ICR. However, as will be described below, when the TXOP responder does not send an ICR in response to an ICF sent by the TXOP holder, refer to... Figure 5 The described exchange between TXOP holder 502 and TXOP responder 504 can resolve Figure 2 and Figure 4 The problem.

[0036] After the backoff period, TXOP holder site 502 may send ICF 510. ICF 510 may include, for example, indications of two durations in the Media Access Control (MAC) header and / or frame body. The first duration (A) may be set to the time used to send the ICR plus the Short Interframe Spacing (SIFS). SIFS allows TXOP holder site 502 to switch from transmit mode to receive mode. In this example, this time is 0.1 ms, as shown in ICF 510 and the timeline. In this example, ICF 510 may also include a second duration (B). This second duration (B) may be set to the time used by the TXOP holder to perform data transmission with the TXOP responder. Figure 5 In the example, the duration B could be 2ms, but this is just an example. The use of this second duration B in the MAC header or frame body of ICF 510 is described in further detail below. Furthermore, other stations receiving ICF 510 can set the NAV based on the ICF. The methods by which other stations can set the NAV are described in more detail below.

[0037] exist Figure 5 In the example, TXOP responder site 504 sends ICR 520 in response to ICF 510. In this case, TXOP holder site 502 can hold the channel for the entire duration of the TXOP to perform transmissions with TXOP responder site 504. Therefore, TXOP responder site 504 can send duration B in the MAC header of ICR 520. As described above, ICF 510 also includes duration B, and TXOP responder site 504 receives duration B when processing ICF 510. For example, TXOP responder site 504 may not know how long the TXOP duration will be, but instead relies on information sent by TXOP holder site 502 to set that value. Therefore, when TXOP responder site 504 sends ICR 520 in response to ICF 510, TXOP responder site 504 includes duration B in the MAC header of ICR 520, allowing other sites to set NAV.

[0038] Continuing with the timing diagram 500, the TXOP holder site 502 sends data to the TXOP responder site 504 during duration B, as shown in data transmissions 530 and 540 and BA 550 transmitted by the TXOP responder site 504 in response to data transmissions 530 and 540.

[0039] Figure 6An example arrangement 600 comprising multiple sites is shown according to various example implementations. Arrangement 600 includes a first site 610 and a second site 620 for exchanging ICFs and ICRs; for example, the first site 610 is a TXOP holder, and the second site 620 is a TXOP responder. For example, the first site 610 as a TXOP holder can operate in a manner similar to the TXOP holder site 502 described above. Similarly, the second site 620 as a TXOP responder can operate in a manner similar to the TXOP responder site 504 described above.

[0040] Arrangement 600 also includes the third station 630 and the fourth station 640. Stations 630 and 640 can be those mentioned above. Figure 5 Other stations mentioned in the description. In the example of arrangement 600, the third station 630 can be considered hidden from the second station 620; for example, the third station 630 may not decode any transmissions made by the second station 620. Similarly, the fourth station 640 is hidden from the first station 610; for example, the fourth station 640 may not decode any transmissions made by the first station 610. Refer to the description of arrangement 600. Figures 7 to 9 The timing diagram.

[0041] Figure 7 Example timing diagram 700 illustrates communication between a TXOP holder and a TXOP responder when other sites are 802.11bn sites, according to various example implementations. In this example implementation, the timing of TXOP holder site 610, TXOP responder site 620, and other sites 630 and 640 is shown. In this example, other sites 630 and 640 are 802.11bn sites.

[0042] After the backoff period, the TXOP holder site 610 sends an ICF 710 including duration A and duration B as described above. The TXOP responder site 620 may receive the ICF 710 and send an ICR 720 in response. The ICR 720 may include duration B in the MAC header of the ICR, as described above.

[0043] In this example, another site 630 can also receive ICF 710. Site 630 will understand that the ICF is not destined for site 630 based on the information in ICF 710. However, site 630 can set NAV based on the information in ICF 710. Because site 630 is an 802.11bn site, site 630 understands the meaning of duration A and duration B. Therefore, as Figure 7 As shown, site 630 can set NAV based on adding duration A and duration B from ICF 710.

[0044] As described above, the other station 640 is hidden from station 610 and therefore does not receive ICF 710, and therefore does not set NAV. The other station 640 does receive ICR 720, which includes duration B in the MAC header of ICR 720. The other station 640 can set NAV based on duration B in ICR 720.

[0045] The remaining operations between TXOP holder site 610 and TXOP responder site 620 (e.g., data sending 730 and 740 and BA 750) are the same as those mentioned above. Figure 5 The examples described are similar and will not be described again.

[0046] exist Figure 7 In the example, if TXOP responder 620 does not transmit ICR 720, this is not a problem for other sites 630 and 640. For site 630, which sets up the NAV based on ICF 710, since site 630 is an 802.11bn site, it has the ability to reset the NAV. For example, if site 630 does not receive the PHY-RXEARLYSIG.indication or PHY-RXSTART.indication primitive associated with data transmission 730 during the NAV timeout period after setting up the NAV according to ICF 710, site 630 can reset the NAV. Site 640 never sets up the NAV because it does not receive ICF 710 and therefore does not perform any additional actions.

[0047] Figure 8 Example timing diagram 800 illustrates communication between a TXOP holder and a TXOP responder when the other site is a legacy site, according to various example implementations. In this example implementation, the timing of a TXOP holder site 610, a TXOP responder site 620, and another site 630 is shown. In this example, the other site 630 is a legacy site, such as an 802.11ax / be site.

[0048] Following the backoff period, TXOP holder site 610 sends ICF 810, which includes duration A and duration B as described above. TXOP responder site 620 may receive ICF 810 and send ICR 820 in response. ICR 820 may include duration B, as described above.

[0049] In this example, another site 630 can also receive ICF 810. Site 630 will understand, based on the information in ICF 810, that ICF 810 is not destined for site 630. However, site 630 can set NAV based on the information in ICF 810. Because site 630 is a legacy site in this example, site 630 may not understand the meaning of duration B. Another site 630 may only understand the meaning of duration A, and therefore, as... Figure 8 As shown, site 630 can set NAV 815 based on duration A in ICF 810.

[0050] In this example, if the TXOP responder site 620 does not send ICR 820, then because the other site 630 sets NAV 815 based solely on duration A, the other site 630 can attempt to access the channel without waiting for the full TXOP duration, e.g., duration A plus duration B. Therefore, the issue can be resolved as described in the reference. Figure 2 and Figure 4 The issue described is unfair to traditional websites.

[0051] However, if the TXOP responder 620 does indeed transmit ICR 820, the other site 630 needs to set NAV for the remaining duration of the TXOP. In this example, the TXOP data transmission 830 can be a High Efficiency (HE) PPDU, an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU. The other site 630 can decode the Physical (PHY) layer header of the PPDU. The PHY layer header may include a TXOP duration field that can be understood by the conventional other site 630. Figure 8 In the example, this duration is shown as duration C in data transmission 830. Another site 630 can use this duration C to set NAV835 for TXOP.

[0052] The remaining operations between TXOP holder site 610 and TXOP responder site 620 (e.g., data sending 840 and BA 850) are the same as those mentioned above. Figure 5 The examples described are similar and will not be described again.

[0053] Figure 9 Example timing diagram 900 illustrates communication between a TXOP holder and a TXOP responder when another site is an 802.11bn site and the NAV is updated, according to various example implementations. In this example implementation, the timing of a TXOP holder site 610, a TXOP responder site 620, and another site 630 is shown. In this example, the other site 630 is an 802.11bn site.

[0054] Following the backoff period, TXOP holder site 610 sends ICF 910, which includes duration A and duration B as described above. TXOP responder site 620 may receive ICF 910 and send ICR 920 in response. ICR 720 may include duration B, as described above.

[0055] In this example, another site 630 can also receive ICF 910. Site 630 will understand that the ICF is not destined for site 630 based on the information in ICF 910. Site 630 can set NAV 915 based on adding duration A and duration B from ICF 910.

[0056] exist Figure 9 In the example, TXOP responder site 620 may experience a coexistence (COEX) scenario. This COEX scenario could mean that TXOP responder site 620 becomes unavailable for a period of time during the TXOP duration, for example, because TXOP responder site 620 is performing Bluetooth communication. This unavailability period 970... Figure 9 As shown in the diagram. The ICR 920 transmitted by the TXOP responder site 620 may include duration B in the MAC header as described above, but may also include the availability duration, for example, the difference between duration B and when unavailability 970 begins.

[0057] Based on the availability duration in ICR 920, TXOP holder site 610 can determine that the TXOP duration will be shorter than duration B; for example, the TXOP may end at the start of the unavailability duration 970. Therefore, in this example, TXOP holder site 610 can include duration C in the TXOP field of the header in data transmission 930. This duration C can be the amount of time that TXOP holder site 610 intends to hold the channel during the TXOP, but less than the original TXOP duration. In this scenario, TXOP holder site 610 is not required to relinquish time in the TXOP. For example, if TXOP holder site 610 is an AP site, the AP can send to other sites during the unavailability period of the TXOP responder site 620.

[0058] However, in Figure 9 In the example, it can be assumed that the TXOP holder site 610 will end the TXOP early. This can be accomplished by the TXOP holder site 610 transmitting a contention-free (CF) end frame 960 after data transmissions 930 and 940 and the corresponding BA 950. The CF end frame 960 indicates to other sites that the contention-free period has ended and that other sites may attempt to access the channel.

[0059] In this example, another station 630 may also receive a data transmission 930 with a duration C in the header (e.g., a PHY-RXSTART indication primitive). As described above, the other station 630 may initially set NAV 915 based on durations A and B in ICF 910. The example implementation allows the other station 630 to update the NAV using duration C in the data transmission 930. Therefore, the other station 630 may update the NAV to NAV 935 based on duration C. In this way, the other station 630 can compete for the station after the TXOP holder station 610 transmits the CF end frame 960, instead of waiting for the original NAV 915 to expire.

[0060] When a third-party site is a non-HE site and is hidden from the TXOP responder, the third-party site may not set NAV for the entire TXOP duration, thus allowing the third-party site to access the medium after the subsequent SIFS of the data frame. In such cases, if the 802.11bn AP detects multiple non-HE sites that may cause interference, the AP can define rules to disable the incremental NAV update. The incremental NAV update mechanism can be used when the AP enables the proposed incremental NAV update mechanism. For example, when the HT protection field in the HT operation element transmitted in the beacon frame is set to 0 (unprotected mode), the AP can declare the enabling of incremental NAV updates in the UHR operation element.

[0061] Figure 10 An example site 1000 according to various example implementation schemes is shown. Example site 1000 may represent, for example... Figure 1 and Figure 3 Sites 110 to 140 or Figure 6 Sites 610 to 640. Although various components are described below for site 1000, it is not required that the site have all the described components. For example, an AP will typically not include a display device.

[0062] Station 1000 may include a processor 1005, a memory arrangement 1010, a display device 1015, an input / output (I / O) device 1020, a transceiver 1025, and other components 1030. Other components 1030 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, and ports for electrically connecting station 1000 to other electronic devices.

[0063] Processor 1005 can be configured to execute multiple engines of site 1000. For example, these engines may include NAV engine 1035. NAV engine 1035 can be configured to perform operations related to setting NAVs during a TXOP. These operations may include those performed by the TXOP holder, TXOP responder, or a third-party site. Examples of these operations are described in detail above.

[0064] The engines cited above, as applications (e.g., programs) executed by processor 1005, are merely examples. The functionality associated with these engines can also be represented as separate integrated components of site 1000, or as modular components coupled to site 1000, such as integrated circuits with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine can also be embodied as one or more separate applications. Furthermore, in some sites, the functionality described for processor 205 is split among two or more processors (such as a baseband processor and an application processor). Example implementations can be implemented according to any of these or other configurations of the wireless communication device.

[0065] Memory arrangement 1010 may be a hardware component configured to store data related to operations performed by station 1000. Display device 1015 may be a hardware component configured to display data to a user, while I / O device 1020 may be a hardware component enabling the user to input data. Display device 1015 and I / O device 1020 may be separate components or may be integrated together (such as a touchscreen).

[0066] Transceiver 1025 may be a hardware component configured to establish a connection with a wirelessly locatable tag or any other wireless communication device. Therefore, transceiver 1025 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). For example, the transceiver may be configured to operate on frequencies associated with the IEEE 802.11 protocol to exchange signals with other sites operating on these protocols. Transceiver 1025 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals may be encoded using information used to implement any of the methods described herein. Processor 1005 may be operatively coupled to transceiver 1025 and configured to receive signals from and / or transmit signals to transceiver 1025. Processor 1005 may be configured to encode, decode, and / or process signals for use in implementing any of the methods described herein.

[0067] Example

[0068] In a first embodiment, a method includes: generating an initial control frame (ICF) for transmission opportunity (TXOP) for transmission, the initial control frame (ICF) including a first duration and a second duration, wherein the first duration is set based on the time required for a TXOP responder site to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS), and wherein the second duration is set based on the time required to send data to the TXOP responder site; processing the ICR based on signaling received from the TXOP responder site; and generating one or more data transmissions during the TXOP for transmission to the TXOP.

[0069] In the second embodiment, according to the method of the first embodiment, the first duration and the second duration are included in the Media Access Control (MAC) header of the ICF.

[0070] In a third embodiment, according to the method of the first embodiment, the first data transmission in the one or more data transmissions includes a third duration, the third duration indicating the remaining time in the second duration after the first data transmission in the one or more data transmissions.

[0071] In the fourth embodiment, according to the method of the third embodiment, the first data transmission in the one or more data transmissions includes a High Efficiency (HE) Physical Layer Protocol Data Unit (PPDU), an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU, wherein the third duration is included in the physical (PHY) layer header of the first data transmission in the one or more data transmissions.

[0072] In a fifth embodiment, according to the method of the first embodiment, the ICR includes an availability duration for the TXOP responder site during the TXOP, wherein the availability duration is less than the second duration.

[0073] In a sixth embodiment, according to the method of the fifth embodiment, the first data transmission in one or more data transmissions includes a third duration, the third duration indicating a time less than the second duration, wherein the third duration is based on the availability duration.

[0074] In a seventh embodiment, according to the method of the sixth embodiment, the method further includes generating a contention-free (CF) end frame for transmission, the contention-free (CF) end frame indicating the end of the contention-free period of the TXOP, wherein the CF end frame is transmitted at the end of the third duration.

[0075] In the eighth embodiment, according to the method of the first embodiment, the device includes an IEEE 802.11bn access point (AP) site or an IEEE 802.11bn non-AP site.

[0076] In a ninth embodiment, a processor is configured to perform any of the methods described according to the first to eighth embodiments.

[0077] In a tenth embodiment, a wireless communication device is configured to perform any of the methods described according to the first to eighth embodiments.

[0078] In an eleventh embodiment, a method includes: processing an initial control frame (ICF) for a TXOP based on signaling received from a transmission opportunity (TXOP) holder site, the initial control frame (ICF) including a first duration and a second duration, wherein the first duration is set based on the time required to respond to the ICF with an initial control response (ICR) and a short inter-frame interval (SIFS), and wherein the second duration is set based on the time required for the TXOP holder site to transmit data; generating the ICR for transmission to the TXOP holder site, wherein the ICR includes the second duration; and processing one or more data transmissions during the TXOP based on signaling received from the TXOP holder site.

[0079] In the twelfth embodiment, according to the method of the eleventh embodiment, the first duration and the second duration are included in the Media Access Control (MAC) header of the ICF.

[0080] In the thirteenth embodiment, according to the method of the eleventh embodiment, the second duration is included in the Media Access Control (MAC) header of the ICR.

[0081] In the fourteenth embodiment, according to the method of the eleventh embodiment, the first data transmission in the one or more data transmissions includes a third duration, the third duration indicating the remaining time in the second duration after the first data transmission in the one or more data transmissions.

[0082] In the fifteenth embodiment, according to the method of the fourteenth embodiment, the first data transmission in the one or more data transmissions includes a High Efficiency (HE) Physical Layer Protocol Data Unit (PPDU), an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU, wherein the third duration is included in the physical (PHY) layer header of the first data transmission in the one or more data transmissions.

[0083] In the sixteenth embodiment, according to the method of the eleventh embodiment, the ICR further includes an availability duration during the TXOP, wherein the availability duration is less than the second duration.

[0084] In the seventeenth embodiment, according to the method of the sixteenth embodiment, the first data transmission in the one or more data transmissions includes a third duration, the third duration indicating a time less than the second duration.

[0085] In the eighteenth embodiment, according to the method of the seventeenth embodiment, the method further includes processing a contention-free (CF) end frame based on signaling received from the TXOP holder site, the contention-free (CF) end frame indicating the end of a contention-free period of the TXOP, wherein the CF end frame is sent at the end of the third duration.

[0086] In the nineteenth embodiment, according to the method of the eleventh embodiment, the device includes an IEEE 802.11bn access point (AP) site or an IEEE 802.11bn non-AP site.

[0087] In the twentieth embodiment, a processor is configured to perform any of the methods described according to the eleventh to nineteenth embodiments.

[0088] In the twenty-first embodiment, a wireless communication device is configured to perform any of the methods described according to the eleventh to nineteenth embodiments.

[0089] In a twenty-second embodiment, a method includes: processing an initial control frame (ICF) for a TXOP based on signaling received from a Transmission Opportunity (TXOP) holder site, the TXOP being designated for a TXOP responder site, the ICF including a first duration and a second duration, wherein the means is not the TXOP responder site, wherein the first duration is set based on the time required to respond to the ICF with an Initial Control Response (ICR) and a Short Interframe Spacing (SIFS), and wherein the second duration is set based on the time required for the TXOP holder site to transmit data to the TXOP responder site; and setting a Network Allocation Vector (NAV) duration based on the first duration and the second duration, wherein the means does not contend for the channel during the NAV duration.

[0090] In the twenty-third embodiment, according to the method of the twenty-second embodiment, the first duration and the second duration are included in the Media Access Control (MAC) header of the ICF.

[0091] In the 24th embodiment, according to the method of the 22nd embodiment, the method further includes: processing a first data transmission in one or more data transmissions during the TXOP based on signaling received from the TXOP holder site, the first data transmission including a third duration, the third duration indicating a time less than the second duration; and resetting the NAV duration based on the third duration.

[0092] In the twenty-fifth embodiment, according to the method of the twenty-fourth embodiment, the first data transmission in the one or more data transmissions includes a High Efficiency (HE) Physical Layer Protocol Data Unit (PPDU), an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU, wherein the third duration is included in the physical (PHY) layer header of the first data transmission in the one or more data transmissions.

[0093] In the twenty-sixth embodiment, according to the method of the twenty-fourth embodiment, the method further includes processing a contention-free (CF) end frame based on signaling received from the TXOP holder site, the contention-free (CF) end frame indicating the end of a contention-free period of the TXOP, wherein the CF end frame is sent at the end of the third duration.

[0094] In the twenty-seventh embodiment, according to the method of the twenty-second embodiment, the device includes an IEEE 802.11bn access point (AP) site or an IEEE 802.11bn non-AP site.

[0095] In the twenty-eighth embodiment, a processor is configured to perform any of the methods described according to the twenty-second to twenty-seventh embodiments.

[0096] In the twenty-ninth embodiment, a wireless communication device is configured to perform any of the methods described according to the twenty-second to twenty-seventh embodiments.

[0097] In a thirtieth embodiment, a method includes: processing an Initial Response Frame (ICR) for a TXOP based on signaling received from a Transmission Opportunity (TXOP) responder site, the TXOP being designated for a TXOP holder site, the ICR including a first duration, wherein the means is not the TXOP holder site, wherein the first duration is set based on the time required for the TXOP holder site to transmit data to the TXOP responder site; and setting a Network Allocation Vector (NAV) duration based on the first duration, wherein the means does not contend for the channel during the NAV duration.

[0098] In the thirty-first embodiment, according to the method of the thirty-first embodiment, the first duration is included in the Media Access Control (MAC) header of the ICR.

[0099] In the thirty-second embodiment, according to the method of the thirty-first embodiment, the method further includes: processing a first data transmission in one or more data transmissions during the TXOP based on signaling received from the TXOP holder site, the first data transmission including a second duration, the second duration indicating a time less than the first duration; and resetting the NAV duration based on the second duration.

[0100] In the thirty-third embodiment, according to the method of the thirty-second embodiment, the first data transmission in the one or more data transmissions includes a High Efficiency (HE) Physical Layer Protocol Data Unit (PPDU), an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU, wherein the second duration is included in the physical (PHY) layer header of the first data transmission in the one or more data transmissions.

[0101] In the thirty-fourth embodiment, according to the method of the thirty-second embodiment, the method further includes processing a contention-free (CF) end frame based on signaling received from the TXOP holder site, the contention-free (CF) end frame indicating the end of a contention-free period of the TXOP, wherein the CF end frame is sent at the end of the second duration.

[0102] In the thirty-fifth embodiment, according to the method of the thirtyth embodiment, the device includes an IEEE 802.11bn access point (AP) site or an IEEE 802.11bn non-AP site.

[0103] In the thirty-sixth embodiment, a processor is configured to perform any of the methods described according to the thirty-fifth embodiments.

[0104] In the thirty-seventh embodiment, a wireless communication device is configured to perform any of the methods described according to the thirty-fifth embodiments.

[0105] In a thirty-eighth embodiment, a method includes: processing an initial control frame (ICF) for a TXOP based on signaling received from a Transmission Opportunity (TXOP) holder site, the TXOP being designated for a TXOP responder site, the ICF including a first duration, wherein the means is not the TXOP responder site, wherein the first duration is set based on the time required to respond to the ICF with an Initial Control Response (ICR) and a Short Interframe Spacing (SIFS); and setting a Network Allocation Vector (NAV) duration based on the first duration, wherein the means does not contend for the channel during the NAV duration.

[0106] In the thirty-ninth embodiment, according to the method of the thirty-eighth embodiment, the first duration is included in the Media Access Control (MAC) header of the ICF.

[0107] In the fortieth embodiment, according to the method of the thirty-eighth embodiment, the method further includes: processing a first data transmission in one or more data transmissions during the TXOP based on signaling received from the TXOP holder site after the first duration, the first data transmission including a second duration, the second duration being set based on the time required for the TXOP holder site to send data to the TXOP responder site; and setting a second NAV duration based on the second duration, wherein the means does not contend for the channel during the second NAV duration.

[0108] In the forty-first embodiment, according to the method of the forty-first embodiment, the first data transmission in the one or more data transmissions includes a High Efficiency (HE) Physical Layer Protocol Data Unit (PPDU), an Extremely High Throughput (EHT) PPDU, or an Ultra High Reliability (UHR) PPDU, wherein the second duration is included in the physical (PHY) layer header of the first data transmission in the one or more data transmissions.

[0109] In the forty-second embodiment, according to the method of the thirty-eighth embodiment, the apparatus includes a conventional IEEE 802.11 access point (AP) site or a conventional IEEE 802.11 non-AP site.

[0110] In the forty-third embodiment, a processor is configured to perform any of the methods described according to the thirty-eighth to forty-second embodiments.

[0111] In the forty-fourth embodiment, a wireless communication device is configured to perform any of the methods described according to the thirty-eighth to forty-second embodiments.

[0112] Those skilled in the art will understand that the example embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Example hardware platforms for implementing the example embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. Example embodiments of the methods described above may be embodied as programs containing lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0113] Although this application describes various embodiments that have different features in various combinations, those skilled in the art will understand that any feature of one embodiment can be combined with features of other embodiments in any way that is not expressly denied or that is not functionally or logically inconsistent with the operation of the device or the specified function of the disclosed embodiment.

[0114] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0115] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An apparatus comprising processing circuitry coupled to a memory, wherein the processing circuitry is configured to: generate, for transmission, an initial control frame (ICF) for a transmit opportunity (TXOP), the initial control frame (ICF) comprising a first duration and a second duration, wherein the first duration is set based on a time required for a TXOP responder station to respond to the ICF with an initial control response (ICR) and a short interframe space (SIFS), and wherein the second duration is set based on a time required to transmit data to the TXOP responder station; process the ICR based on signaling received from the TXOP responder station; and generate, for transmission, one or more data transmissions to the TXOP responder station during the TXOP.

2. The apparatus of claim 1, wherein the first duration and the second duration are included in a medium access control (MAC) header of the ICF.

3. The apparatus of claim 1, wherein a first data transmission of the one or more data transmissions comprises a third duration indicating a time remaining in the second duration after transmitting the first data transmission of the one or more data transmissions.

4. The apparatus of claim 3, wherein the first data transmission of the one or more data transmissions comprises a high efficiency (HE) physical layer protocol data unit (PPDU), an extremely high throughput (EHT) PPDU, or an ultra-high reliability (UHR) PPDU, wherein the third duration is included in a physical (PHY) layer header of the first data transmission of the one or more data transmissions.

5. The apparatus of claim 1, wherein the ICR comprises an availability duration for the TXOP responder station during the TXOP, wherein the availability duration is less than the second duration.

6. The apparatus of claim 5, wherein a first data transmission of the one or more data transmissions comprises a third duration indicating a time less than the second duration, wherein the third duration is based on the availability duration.

7. The apparatus of claim 6, wherein the processing circuitry is further configured to: generate, for transmission, a contention free (CF) end frame indicating an end of a contention free period of the TXOP, wherein the CF end frame is transmitted at an end of the third duration.

8. The apparatus of claim 1, wherein the apparatus comprises an IEEE 802.1 lbn access point (AP) station or an IEEE 802.1 lbn non-AP station.

9. An apparatus comprising processing circuitry coupled to a memory, wherein the processing circuitry is configured to: processing an initial control frame (ICF) for a transmit opportunity (TXOP) based on signaling received from a TXOP holder station, the ICF including a first duration and a second duration, wherein the first duration is set based on a time required to respond to the ICF with an initial control response (ICR) and a short interframe space (SIFS), and wherein the second duration is set based on a time required to transmit data by the TXOP holder station; generating the ICR for transmission to the TXOP holder station, wherein the ICR includes the second duration; and processing one or more data transmissions during the TXOP based on signaling received from the TXOP holder station.

10. The apparatus of claim 9, wherein the first duration and the second duration are included in a medium access control (MAC) header of the ICF.

11. The apparatus of claim 9, wherein the second duration is included in a medium access control (MAC) header of the ICR.

12. The apparatus of claim 9, wherein a first data transmission of the one or more data transmissions includes a third duration, the third duration indicating a time remaining in the second duration after transmitting the first data transmission of the one or more data transmissions.

13. The apparatus of claim 9, wherein the ICR further includes an availability duration during the TXOP, wherein the availability duration is less than the second duration.

14. The apparatus of claim 13, wherein a first data transmission of the one or more data transmissions includes a third duration, the third duration indicating a time less than the second duration.

15. The apparatus of claim 14, wherein the processing circuitry is further configured to: process a contention free (CF) end frame based on signaling received from the TXOP holder station, the CF end frame indicating an end of a contention free period of the TXOP, wherein the CF end frame is transmitted at an end of the third duration.

16. The apparatus of claim 9, wherein the apparatus comprises an IEEE 802.1 lbn access point (AP) station or an IEEE 802.1 lbn non-AP station.

17. An apparatus comprising processing circuitry coupled to a memory, wherein the processing circuitry is configured to: process an initial control frame (ICF) for a transmit opportunity (TXOP) based on signaling received from a TXOP holder station, the TXOP designated for a TXOP responder station, the ICF including a first duration and a second duration, wherein the apparatus is not the TXOP responder station, wherein the first duration is set based on a time required to respond to the ICF with an initial control response (ICR) and a short interframe space (SIFS), and wherein the second duration is set based on a time required to transmit data by the TXOP holder station; wherein the second duration is set based on a time required for transmitting data by the TXOP holder station to the TXOP responder station; and setting a network allocation vector (NAV) duration based on the first duration and the second duration, wherein the apparatus does not contend for a channel during the NAV duration.

18. The apparatus of claim 17, wherein the first duration and the second duration are included in a medium access control (MAC) header of the ICF.

19. The apparatus of claim 17, wherein the processing circuitry is further configured to: process a first data transmission of one or more data transmissions during the TXOP based on signaling received from the TXOP holder station, the first data transmission including a third duration, the third duration indicating a time less than the second duration; and reset the NAV duration based on the third duration.

20. The apparatus of claim 19, wherein the processing circuitry is further configured to: process a contention free (CF) end frame based on signaling received from the TXOP holder station, the contention free (CF) end frame indicating an end of a contention free period of the TXOP, wherein the CF end frame is transmitted at an end of the third duration.

Images