Methods, devices, storage media, and program products for communication

Abstract

Embodiments of the present disclosure provide a method, device, storage medium and program product for communication. In the communication method of the present disclosure, an access point device obtaining a transmission opportunity (TXOP) in a wireless local area network allocates a first time period in the TXOP to a non-access point device for data transmission. The access point device receives a first frame in the first time period, and an access address or a sending address of the first frame is associated with the non-access point device. The method further comprises maintaining, by the access point device, a network allocation vector (NAV) unchanged based on the first frame. The method improves the trigger-based TXOP sharing mechanism, so that the access node can avoid or reduce the case that the access node cannot perform data transmission in the remaining time of the TXOP due to updating the NAV. In this way, the resource efficiency of the communication network can be improved, and the system performance and communication quality can be ensured.

Description

Technical Field

[0001] Embodiments of this disclosure primarily relate to the field of communications, and more particularly to methods, apparatus, storage media, and program products for setting network allocation vectors. Background Technology

[0002] Wireless Local Area Network (WLAN) technology has evolved through several generations, from the 802.11a / g, 802.11n, 802.11ac, and 802.11ax standards to the current 802.11be standard. Accompanying this evolution is a continuous increase in data throughput; therefore, the 802.11ax standard is also known as a High Efficiency (HE) wireless standard, and the 802.11be standard can be called an Extremely High Throughput (EHT) wireless standard. WLAN systems are typically deployed on unlicensed spectrum, allowing multiple stations within the network to compete for channel resources.

[0003] In the commonly used Enhanced Distributed Channel Access (EDCA) contention mechanism, a station needs to listen to whether other stations are transmitting data before sending data. If the channel listening result is busy, the station's transmission will be temporarily suspended until the channel becomes idle. After the channel becomes idle, channel backoff is required before transmitting data to handle collisions between multiple potential transmitting stations. After channel backoff is completed, the station can transmit data. Before actually transmitting data, the station can also interact with other stations in the network using short control frames, such as Request To Send (RTS) / Clear To Send (CTS). If the short control frame interaction is successful, it means that the channel contention is successful, and the station can then reserve a time period for data transmission. This time period is called the Transmission Opportunity (TXOP). The station that successfully reserves a TXOP is called the TXOP holder. Within the TXOP, only the TXOP holder is allowed to actively transmit data, while other stations can only receive data or send corresponding response frames. If a collision occurs during the interaction of short control frames, the station can avoid transmitting subsequent long data frames and re-perform channel backoff. This prevents the entire data frame from failing to transmit, thereby further reducing throughput loss due to the collision. Summary of the Invention

[0004] In general, embodiments of this disclosure provide methods, apparatus, and computer-readable storage media for communication.

[0005] In a first aspect of this disclosure, a method for communication is provided. The method includes: an access point device that obtains a transmission opportunity (TXOP) in a wireless local area network (WLAN) allocates a first time period within the TXOP to a non-access point device for data transmission; the access point device receives a first frame during the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and the access point device, based on the first frame, keeps the network allocation vector (NAV) unchanged.

[0006] In a first implementation of the first aspect, the access point device maintains a single NAV including the NAV.

[0007] In the second implementation of the first aspect, the access address or transmission address of the first frame is the Media Access Control (MAC) address of the non-access point device.

[0008] In the third implementation of the first aspect, the access point device allocates the first time period to the non-access point device by sending a transmission opportunity sharing trigger frame MU-RTS TXS TF via a multi-user request.

[0009] In a fourth implementation of the first aspect, the method further includes: before transmitting data, the access point device sends a request to transmit an RTS frame to at least one receiving device; the access point device receives a clear transmit CTS frame from at least one receiving device; and the access point device transmits data to at least one receiving device.

[0010] In the fifth implementation of the first aspect, the access point device maintains two NAVs, including an Intra-BSS NAV within the basic service set, and in this method, the access point device updates the Intra-BSS NAV based on the fulfillment of certain conditions. These conditions include: the first frame is an Intra-BSS frame; the first duration for data transmission included in the first frame is greater than the second duration indicated by the Intra-BSS NAV currently maintained by the access point device; the receive address of the first frame is not the Media Access Control (MAC) address of the access point device; and the access address or send address of the first frame is not associated with a non-access point device.

[0011] In a sixth implementation of the first aspect, the access point device maintains two NAVs, including a basic NAV, and in this method, the access point device updates the basic NAV based on the following conditions being met: the first frame is an inter-BSS frame between basic service sets, or the first frame is not identified by either an inter-BSS or an intra-BSS within the basic service set; the first duration for data transmission included in the first frame is greater than the second duration indicated by the basic NAV currently maintained by the access point device; the receive address of the first frame is not the media access control MAC address of the access point device; and the access address or send address of the first frame is not associated with a non-access point device.

[0012] In the seventh implementation of the first aspect, keeping the NAV unchanged further includes: the access point device determining the received energy of the physical layer protocol data unit (PPDU) used to carry the first frame; and the access point device keeping the NAV unchanged based on the received energy not exceeding a predetermined energy threshold.

[0013] In the eighth implementation of the first aspect, the access point device is an ultra-high throughput EHT access point.

[0014] According to the communication scheme of this disclosure, the access point (AP) holding a TXOP can conditionally refrain from updating the NAV. In other words, under predetermined conditions, the AP can, during the allocated time period shared with other non-AP sites or for the remainder of the TXOP, not update its maintained NAV based on the duration field in the received radio frames. This avoids or reduces the problem of the TXOP holder being unable to transmit data during the TXOP due to a non-zero NAV. Based on this approach, the technical solution of this disclosure can fully utilize the spectrum resources of the communication system, improve resource efficiency, and ensure system performance and communication quality.

[0015] In a second aspect of this disclosure, a method for communication is provided. The method includes: an access point device that obtains a transmission opportunity (TXOP) in a wireless local area network (WLAN) allocates a first time period within the TXOP to a non-access point device for data transmission; the access point device receives a first frame during the first time period; and the access point device updates a network allocation vector (NAV) if the following conditions are met: a first duration for data transmission included in the first frame is greater than a second duration indicated by a currently maintained NAV of the access point device; the receive address of the first frame is not the media access control (MAC) address of the access point device; and the access address or transmission address of the first frame is not associated with a non-access point device.

[0016] In the first implementation of the second aspect, the NAV is at least one of the Intra-BSS NAV and the basic NAV within the basic service set.

[0017] In the second implementation of the second aspect, the condition further includes that the first frame is an Intra-BSS frame within the basic service set, and that the access point device update NAV includes the access point device update Intra-BSS NAV.

[0018] In the third implementation of the second aspect, the conditions further include that the first frame is an Inter-BSS frame between basic service sets, or the first frame is not identified by either the Inter-BSS or the Intra-BSS within the basic service set, and the access point device update NAV includes the access point device update basic NAV.

[0019] In the fourth implementation of the second aspect, the access point device maintains a single NAV including the NAV.

[0020] In a fifth implementation of the second aspect, the method further includes: before transmitting data, the access point device sends a request to transmit an RTS frame to at least one receiving device; the access point device receives a clear transmit CTS frame from at least one receiving device; and the access point device transmits data to at least one receiving device.

[0021] The communication scheme disclosed herein improves the trigger-based transmission opportunity sharing mechanism, enabling access nodes to avoid or reduce situations where data transmission is impossible for the remaining time of the TXOP due to NAV updates. This improves the resource efficiency of the communication network and ensures system performance and communication quality.

[0022] In a third aspect of this disclosure, a method for communication is provided. The method includes: an access point device that has obtained a transmission opportunity (TXOP) in a wireless local area network (WLAN) allocating a first time period within the TXOP to a non-access point device for data transmission; the access point device receiving a first frame during the first time period; the access point device updating its maintained network allocation vector (NAV) based on the first frame; and if the access address or transmission address of the first frame is associated with a non-access point device and the value of the TXNAV timer is not equal to 0, the access point device determining that the channel is idle based on virtual carrier sensing.

[0023] In the first implementation of the third aspect, the access point device maintains a single NAV including the NAV.

[0024] In the second implementation of the third aspect, the access point device maintains two NAVs, including the NAV, and the NAV is an Intra-BSS NAV within the basic service set. The access point device determines that the channel is idle based on virtual carrier sensing, which includes: if the value of the basic NAV in the two NAVs is equal to 0, the access point device determines that the channel is idle based on virtual carrier sensing.

[0025] In the third implementation of the third aspect, the access point device maintains two NAVs, including the NAV itself, and the NAV is a basic NAV. The access point device determines that the channel is idle based on virtual carrier sensing, which includes: if the value of the Intra-BSS NAV in the basic service set of the two NAVs is equal to 0, then the access point device determines that the channel is idle based on virtual carrier sensing.

[0026] In the fourth implementation of the third aspect, the access point device allocates the first time period to the non-access point device by sending a transmission opportunity sharing trigger frame MU-RTS TXS TF through a multi-user request.

[0027] In the fifth implementation of the third aspect, in this method, before sending data, the access point device sends a request to send an RTS frame to at least one receiving device; the access point device receives a clear send CTS frame from at least one receiving device; and the access point device sends data to at least one receiving device.

[0028] In the sixth implementation of the third aspect, the access point device is an ultra-high throughput EHT access point.

[0029] According to the communication scheme disclosed herein, the AP, as the TXOP holder, can conditionally ignore updates to the NAV. Specifically, under predetermined conditions, the AP can continue data transmission while updating the NAV during the allocated time period or TXOP shared with other non-AP sites. This avoids or reduces the problem of the TXOP holder being unable to send data during the TXOP due to a non-zero NAV. Based on this approach, the technical solution of this disclosure can fully utilize the spectrum resources of the communication system, improve resource efficiency, and ensure system performance and communication quality.

[0030] In a fourth aspect of this disclosure, a communication device is provided. The communication device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the communication device to: allocate a first time period in a TXOP (Transmission Opportunity for Partition) to a non-access point device for data transmission; receive a first frame in the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and based on the first frame, keep the network allocation vector (NAV) unchanged.

[0031] In a fifth aspect of this disclosure, a communication device is provided. The communication device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the communication device to: allocate a first time period in a TXOP (Transmission Opportunity for Data Transfer) to a non-access point device for data transmission; receive a first frame during the first time period; and update a network allocation vector (NAV) if the following conditions are met: a first duration for data transmission included in the first frame is greater than a second duration indicated by a currently maintained NAV of the access point device; the receive address of the first frame is the media access control (MAC) address of the access point device; and the access address or transmission address of the first frame is associated with the non-access point device.

[0032] In a sixth aspect of this disclosure, the communication device includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the communication device to: allocate a first time period in the TXOP to a non-access point device for data transmission; receive a first frame in the first time period; update its maintained network allocation vector NAV based on the first frame; and determine that the channel is idle based on virtual carrier sensing if the access address or transmission address of the first frame is associated with a non-access point device and the TXNAV is not equal to 0.

[0033] In a seventh aspect of this disclosure, a communication device is provided. The communication device includes: components for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; components for receiving a first frame during the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and components for keeping the network allocation vector (NAV) unchanged based on the first frame.

[0034] In an eighth aspect of this disclosure, a communication device is provided. The communication device includes: components for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; components for receiving a first frame during the first time period; and components for updating a network allocation vector (NAV) if conditions are met, the conditions including: a first duration for data transmission included in the first frame is greater than a second duration indicated by a currently maintained NAV of the access point device; a receiving address of the first frame is a media access control (MAC) address of the access point device; and an access address or transmission address of the first frame is associated with the non-access point device.

[0035] In a ninth aspect of this disclosure, a communication apparatus is provided. The communication apparatus includes: components for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; components for receiving a first frame during the first time period; components for updating a maintained network allocation vector (NAV) based on the first frame; and components for determining that a channel is idle based on virtual carrier sensing if the access address or transmission address of the first frame is associated with a non-access point device and TXNAV is not equal to 0.

[0036] In a tenth aspect of this disclosure, a communication device is provided. The communication device includes: an allocation unit for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; a receiving unit for receiving a first frame during the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and an updating unit for keeping the network allocation vector (NAV) unchanged based on the first frame.

[0037] In the eleventh aspect of this disclosure, a communication device is provided. The communication device includes: an allocation unit for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; a receiving unit for receiving a first frame during the first time period; and an updating unit for updating a network allocation vector (NAV) if conditions are met, the conditions including: a first duration for data transmission included in the first frame is greater than a second duration indicated by a NAV currently maintained by the access point device; the receiving address of the first frame is the media access control (MAC) address of the access point device; and the access address or sending address of the first frame is associated with the non-access point device.

[0038] In a twelfth aspect of this disclosure, a communication device is provided. The communication device includes: an allocation unit for allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; a receiving unit for receiving a first frame during the first time period; an updating unit for updating a maintained network allocation vector (NAV) based on the first frame; and a determining unit for determining that the channel is idle based on virtual carrier sensing if the access address or transmission address of the first frame is associated with a non-access point device and TXNAV is not equal to 0.

[0039] In a thirteenth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When executed by a processor, the program implements: allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; receiving a first frame during the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and, based on the first frame, keeping the network allocation vector (NAV) unchanged.

[0040] In a fourteenth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When executed by a processor, the program implements: allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; receiving a first frame during the first time period; and, if a condition is met, updating the network allocation vector (NAV) of the access point device, the condition including: a first duration for data transmission included in the first frame being greater than a second duration indicated by a NAV currently maintained by the access point device; a receiving address of the first frame being the media access control (MAC) address of the access point device; and an access address or transmission address of the first frame being associated with the non-access point device.

[0041] In a fifteenth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When executed by a processor, the program implements: allocating a first time slot in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; the access point device receiving a first frame during the first time slot; the access point device updating its maintained network allocation vector (NAV) based on the first frame; and if the access address or transmission address of the first frame is associated with a non-access point device and TXNAV is not equal to 0, the access point device determining that the channel is idle based on virtual carrier sensing.

[0042] In a sixteenth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions. When executed by a processor, the computer-executable instructions implement a method comprising: allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; receiving a first frame during the first time period, the access address or transmission address of the first frame being associated with the non-access point device; and, based on the first frame, keeping the network allocation vector (NAV) unchanged.

[0043] In a seventeenth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions. When executed by a processor, the computer-executable instructions implement a method comprising: allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; receiving a first frame during the first time period; and, if a condition is met, updating the network allocation vector (NAV) of the access point device, the condition comprising: a first duration for data transmission included in the first frame being greater than a second duration indicated by a currently maintained NAV of the access point device; a receiving address of the first frame being a media access control (MAC) address of the access point device; and an access address or transmission address of the first frame being associated with the non-access point device.

[0044] In an eighteenth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions. When executed by a processor, the computer-executable instructions implement a method comprising: allocating a first time period in a acquired transmission opportunity (TXOP) to a non-access point device for data transmission; the access point device receiving a first frame during the first time period; the access point device updating a maintained network allocation vector (NAV) based on the first frame; and if the access address or transmission address of the first frame is associated with the non-access point device and TXNAV is not equal to 0, then the access point device determining that the channel is idle based on virtual carrier sensing.

[0045] The summary section is provided to present the chosen concepts in a simplified form, which will be further described in the detailed description below. The summary section is not intended to identify key or essential features of this disclosure, nor is it intended to limit the scope of this disclosure. Attached Figure Description

[0046] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0047] Figure 1 A schematic diagram of a communication environment in which embodiments of the present disclosure may be implemented is shown;

[0048] Figure 2A schematic diagram of a trigger-based transmission opportunity sharing mechanism according to an embodiment of the present disclosure is shown;

[0049] Figure 3 A flowchart of a communication method according to an embodiment of the present disclosure is shown;

[0050] Figure 4 A flowchart of a communication method according to an embodiment of the present disclosure is shown;

[0051] Figure 5 A flowchart of a communication method according to an embodiment of the present disclosure is shown;

[0052] Figure 6 A schematic block diagram of a communication device according to an embodiment of the present disclosure is shown;

[0053] Figure 7 A schematic block diagram of a communication device according to an embodiment of the present disclosure is shown; and

[0054] Figure 8 A simplified block diagram of an example device suitable for implementing some embodiments of this disclosure is shown.

[0055] In the various figures, the same or similar reference numerals represent the same or similar elements. Detailed Implementation

[0056] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0057] The technical solutions of this application embodiment can be applied to wireless local area network (WLAN) systems, as well as other communication systems, such as Long Term Evolution (LTE) systems, 5G systems, and other future communication systems. Taking a WLAN system as an example, Access Points (APs) and Stations (STAs) are the basic components of a WLAN system. An AP is the access point for mobile users to access a wired network, mainly deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters; it can also be deployed outdoors. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, an AP can be a device with a WiFi (Wireless Fidelity) chip, such as a terminal device or network device with a WiFi chip. Optionally, the AP can be a device that supports the 802.11ax standard; alternatively, the AP can also be a device that supports multiple WLAN standards such as 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. Furthermore, the AP can also be a device that supports 802.11be and other future 802.11 standard WLAN standards. This application does not limit the types of standards supported by the AP.

[0058] A STA, also known as a non-AP device, is generally a terminal device in a WLAN system. STAs can be mobile or fixed, and are the most basic component of a wireless local area network (WLAN). STAs can be wireless communication chips, wireless sensors, or wireless communication terminals, such as mobile phones, tablets, set-top boxes, smart TVs, smart wearable devices, in-vehicle communication devices, and computers that support WiFi communication. Similarly, an STA can be a device supporting the 802.11ax standard, and it can also be a device supporting multiple WLAN standards such as 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. Furthermore, an STA can also be a device supporting 802.11be and other future 802.11 standards. This application does not limit the types of standards supported by the STA.

[0059] The term "comprising" and similar expressions used herein should be understood as open-ended inclusion, meaning "including but not limited to". Unless otherwise stated, the term "or" means "and / or". The term "based on" means "at least partially based on". The terms "example embodiment" and "some embodiments" mean "at least one example embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0060] IEEE 802.11 is one of the mainstream wireless access standards and has been widely used in commercial applications over the past decade. Figure 1 A schematic diagram is shown of a communication environment 100 in which embodiments of the present disclosure may be implemented. For example... Figure 1 As shown, communication environment 100 includes access point AP 110 and STAs 120 to 140, where access point AP 110 accesses the Internet 150 via a wired or wireless connection. Access point AP 110 can associate stations STAs 120 and 130 to form a WLAN 102. Therefore, stations STAs 120 and 130 can connect to the Internet 150 through access point AP 110. In the context of this disclosure, AP 110 and STAs 120 to 140 can be collectively referred to as stations 110 to 140.

[0061] In the context of this disclosure, access point AP 110 and associated sites STA 120 and 130 can communicate uplink and downlink via a predetermined protocol (e.g., IEEE 802.11), including point-to-multipoint and point-to-point transmissions. Furthermore, packet data based on various frame structures, such as Physical Layer Protocol Data Units (PPDUs), can be transmitted between access point AP 110 and sites STA 120 and 130.

[0062] Sites STA can communicate in a peer-to-peer (P2P) manner via a point-to-point (P2P) link. For example, sites 120 and 130 can communicate in a P2P manner due to their proximity. As another example, sites 120 and 140 can communicate directly in a P2P manner within a transmission range 104. The P2P link can be established based on TDLS (Tunneled Direct Link Setup) or other P2P wireless protocols. The embodiments described herein regarding P2P are also applicable to device-to-device (D2D) communication or other communication protocols such as TDLS. Therefore, the P2P protocol is used for illustrative purposes only and is not intended to limit the scope of this disclosure.

[0063] In some embodiments, access point AP 100 may be, for example, a wireless router. Sites STA 120 to 140 may include wireless mobile devices, examples of which include, but are not limited to, smartphones, laptops, tablets, smart wearable devices, or in-vehicle mobile devices.

[0064] It should be understood that the communication environment 100 is for illustrative purposes only and does not imply any limitation on the scope of this application. Embodiments of this application may also be embodied in other network environments or architectures. Furthermore, it should be understood that the communication environment 200 may also include other elements or entities for purposes such as achieving communication connectivity, data transmission, network security, etc. For the sake of simplicity, in Figure 1 These elements or entities are not shown in the text, but this does not mean that the embodiments of this application do not include these elements or entities.

[0065] The network environment 100 according to embodiments of this application may be a wireless network that follows any currently known or future-developed protocol, including but not limited to WLANs based on standards such as 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a; Narrow Band-Internet of Things (NB-IoT); Global System for Mobile Communications (GSM); Enhanced Data Rate for GSM Evolution (EDGE); Wideband Code Division Multiple Access (WCDMA); Code Division Multiple Access 2000 (CDMA2000); Time Division-Synchronization Code Division Multiple Access (TD-SCDMA); Long Term Evolution (LTE); and 5G NR networks.

[0066] In WLAN 102, wireless channel resources are shared by multiple sites 110 to 130. Access point AP 110 and non-AP sites 120 and 130 compete for channel resources. Sites 110 to 130 need to listen to the channel before accessing it. Generally, listening is divided into physical carrier listening and virtual carrier listening. Physical carrier listening is implemented by listening to the energy on the channel and the WLAN wireless frame signal. When the received energy or the strength of the received WLAN wireless frame is less than a certain threshold, physical carrier listening determines that the channel is idle; otherwise, physical carrier listening determines that the channel is busy.

[0067] Virtual carrier sensing is implemented by setting the Network Allocation Vector (NAV). The NAV acts as a timer mechanism; when the NAV value is not zero, virtual carrier sensing determines the channel is busy; when the NAV value is zero, virtual carrier sensing determines the channel is idle. For example, after a station correctly receives a radio frame, it can update its maintained NAV based on the Duration field in the radio frame. If the Receiver Address (RA) of the received frame is its own MAC address, the station does not update the NAV. For other radio frames, when the Duration field value is greater than the station's current NAV value, the station updates the NAV based on the Duration field value. Typically, a station is only allowed to access the channel and transmit radio frames when both physical carrier sensing and virtual carrier sensing determine the channel is idle.

[0068] After successfully contending for a channel, the station can utilize the channel resources for data transmission. For example, AP 110 can send data to STA 120, which is within its signal coverage area. STA 140 is outside the signal coverage area of ​​AP 110; that is, AP 110 is unaware of the interference STA 140 is causing to STA 120, which is the receiver. STA 140 can detect STA 120 within its transmission range 104 by listening and intends to send data to it. As mentioned earlier, STA 140 is unaware of the ongoing data transmission between AP 110 and STA 120. If STA 140 also sends data to STA 120, STA 120 will simultaneously receive data from both AP 110 and STA 140, resulting in a conflict and preventing the receiver STA 120 from correctly receiving radio frames. In this situation, STA 140 is also referred to as a hidden node. The presence of a hidden node interferes with the receiver, preventing it from detecting other senders and thus causing data transmission failure.

[0069] The NAV mechanism effectively avoids collisions caused by hidden nodes. By using Virtual Carrier Sense, after a sending station wins the channel, it can exchange short frames with a receiving station before officially transmitting data. Both short frames use their Duration field to enable NAV on non-target stations around both communicating parties. This ensures that hidden nodes will not compete for the channel or transmit radio frames during the NAV protection period. This NAV protection period is typically called TXOP.

[0070] In early WLAN systems, each station had only one NAV. The IEEE 802.11ax standard introduced Dual NAVs technology for more granular management. One NAV is called the Intra-BSS NAV, and the other is called the Basic NAV. The Intra-BSS NAV is updated via Intra-BSS PPDUs, while the Basic NAV is updated via Inter-BSS PPDUs or PPDUs that cannot be distinguished as Intra-BSS or Inter-BSS. In short, Inter-BSS PPDUs can be PPDUs sent from STAs outside the local BSS, while Intra-BSS PPDUs can be PPDUs sent from stations within the local BSS. The specific methods for distinguishing between Intra-BSS and Intra-BSS PPDUs can be found in the IEEE 802.11ax standard and will not be elaborated upon here.

[0071] For a site that is not a TXOP holder, the intra-BSS NAV is updated if and only if the received frame meets all of the following conditions:

[0072] 1) The received frame is an Intra-BSS frame;

[0073] 2) The value of the Duration field in the received frame is greater than the current Intra-BSS NAV value of the site; and

[0074] 3) The RA of the received frame is not the MAC address of the station, or the received frame will not trigger the station to respond immediately, or the received frame is a trigger frame.

[0075] For a station, the basic NAV is updated if and only if the received frame satisfies all of the following conditions:

[0076] 1) The received frame is an inter-BSS frame, or it is impossible to distinguish whether it is an intra-BSS frame or an inter-BSS frame;

[0077] 2) The value of the Duration field in the received frame is greater than the current basic NAV value of the site; and

[0078] 3) The RA of the received frame is not the MAC address of the station.

[0079] If either the Intra-BSS NAV or the basic NAV is set to a non-zero value, the Virtual Carrier Sensing (VCS) considers the current channel busy and occupied by another site. If both the Intra-BSS NAV and the basic NAV are 0, the VCS considers the channel idle, and only then can a site compete for channel space. When a site is triggered to respond immediately by its associated AP, it can respond if its Physical Carrier Sensing (PCS) is idle and its basic NAV is 0. If the basic NAV is not 0, it cannot respond even if the PCS result is idle.

[0080] In addition to NAV or dual NAV, a timer TXNAV can also be maintained within the site acting as the TXOP holder. This timer is initialized by the Duration or ID field of the most recently successfully sent frame by the TXOP holder; that is, the duration of TXNAV is equal to the remaining duration of the current TXOP. TXNAV counts down from the end of the PPDU carrying the frame.

[0081] The IEEE 802.11be standard extends the TXOP mechanism. Specifically, a site holding a TXOP can allocate a portion of its time resources within the TXOP to a first site associated with it. This first site can then use the allocated time period to engage in peer-to-peer (P2P) communication with another site, such as a second site, or to send uplink data to the TXOP holder. This mechanism is called Triggered TXOP Sharing. This mechanism improves system efficiency by reducing collisions caused by sites competing for channel space with the AP (Access Point).

[0082] Figure 2 A schematic diagram of a trigger-based transmission opportunity sharing mechanism 200 according to an embodiment of the present disclosure is shown. The mechanism 200 may involve, for example... Figure 1 The diagram shows access point AP 110 and sites STA 120 and 130. For ease of description, references will be made below. Figure 1 To describe the trigger-based transmission opportunity sharing mechanism 200.

[0083] like Figure 2As shown, Access Point 110, having obtained a TXOP in the wireless LAN, can enter the TXOP period after sending a short frame CTS 201. Then, Access Point 110 can allocate the first period of the TXOP to STA 120 for data transmission by sending a Multi-User Request Transmission Opportunity Sharing Trigger Frame (MU-RTS TXS TF) 202 to STA 120. STA 120 can then occupy the channel by sending CTS 203 and utilize the resources of the first period to send SU PPDU 204 to STA 130. After receiving SU PPDU 204, STA 130 can send a Block Acknowledgement (BA) 205 to STA 120. After the first period ends, Access Point 110 can continue data transmission in the current TXOP, for example, by sending PPDU 206.

[0084] If STA 120 sends a message to AP 110 before the end of the first time period to return the remaining first time period to AP 110, that is, if STA 120 terminates data transmission in the first time period in advance, AP 110 can obtain the opportunity to send data in the first time period.

[0085] On the other hand, after STA 120 issues SU PPDU 204, AP 110 will set the NAV according to the Duration field in SU PPDU 204. Since the RA in SU PPDU 204 is the MAC address of STA 130, not the MAC address of AP 110, according to the regular NAV setting rules, AP 110's NAV update will affect its data transmission in subsequent TXOPs.

[0086] To address the aforementioned problems or other potential issues, exemplary embodiments of this disclosure provide an enhanced NAV setting mechanism. According to this enhanced mechanism, the AP acquiring the TXOP can conditionally either not update the NAV or conditionally ignore the NAV. This avoids the problem of the AP being unable to transmit data normally for the remaining time of the TXOP due to setting the NAV after receiving a PPDU sent by a STA sharing the TXOP or an Overlapped Basic Service Set (OBSS) STA.

[0087] According to some example embodiments of this disclosure, an AP may not update its maintained NAV based on predetermined rules or conditions, and this implementation is applicable to APs that support dual NAVs as well as APs that do not support dual NAVs. Reference will be made below. Figure 3 A flowchart is provided to describe a communication method 300 according to embodiments of the present disclosure. Method 300 can be... Figure 1The implementation is shown at access point AP110. For ease of discussion, the following will be combined with... Figure 1 This describes method 300. It should be understood that method 300 is also applicable to other communication scenarios and devices.

[0088] like Figure 3 As shown in 310, in WLAN 102, the access point AP 110, which obtains the TXOP, allocates the first time slot in the TXOP to a non-access point device (i.e., STA 120) for data transmission. Figure 2 In the example, access point AP 110 can allocate the first time slot in TXOP to STA 120 for data transmission by sending MU-RTS TXS TF 202 to STA 120.

[0089] In some example embodiments, the resources of the first time period can be used for P2P communication between STA 120 and STA 130, or for uplink transmission between STA 120 and AP 110.

[0090] At 320, access point AP 110 receives the first frame in the first time period. The RA or Transmitter Address (TA) of the first frame can be associated with STA 120. Figure 2 In the example, the first frame could be SU PPDU204, whose TA is associated with STA 120.

[0091] At 330, access point AP 110 keeps the NAV unchanged based on the first frame.

[0092] In some example embodiments, AP 110 may conditionally choose to update or not update NAV. For example, AP may not update NAV during a first time period only based on the RA or TA associated with STA 120 in the first frame.

[0093] In some embodiments where the access point AP 110 supports dual NAVs, the AP 110 can maintain two NAVs, and the AP 110 can update the Intra-BSS NAV in the two NAVs based on the satisfaction of conditions, including:

[0094] The first frame is an Intra-BSS frame;

[0095] • The first frame includes a first duration (i.e., the Duration field) for data transmission that is greater than the second duration indicated by the Intra-BSS NAV currently maintained by the access point AP110;

[0096] • The RA in the first frame is not the MAC address of access point AP 110; and

[0097] Neither the RA nor the TA in the first frame is the MAC address of STA 120.

[0098] exist Figure 2 In the example shown, AP 110 may not update the Intra-BSS NAV because some of the conditions above are not met, for example, the TA of SU PPDU 204 is associated with STA 120.

[0099] In some other embodiments where the access point AP 110 supports dual NAVs, the AP 110 can update the base NAV of the two NAVs based on the satisfaction of conditions, including:

[0100] • The first frame is an Inter-BSS frame, or the first frame is not identified by either Inter-BSS or Intra-BSS, meaning that the first frame cannot be distinguished as either Intra-BSS or Inter-BSS;

[0101] • The first frame includes a first duration (i.e., the Duration field) for data transmission that is greater than the second duration indicated by the basic NAV currently maintained by the access point device AP 110;

[0102] • The RA in the first frame is not the MAC address of access point AP 110; and

[0103] Neither the RA nor the TA in the first frame is the MAC address of STA 120.

[0104] exist Figure 2 In the example shown, AP 110 may not update the basic NAV because some of the conditions above are not met, for example, the TA of SU PPDU 204 is associated with STA 120.

[0105] In an embodiment where the access point AP 110 maintains a single NAV, regardless of whether the first frame is an Intra-BSS PPDU, Inter-BSS PPDU, or an indistinguishable Intra-BSS or Inter-BSS PPDU, as long as the RA or TA included in the first frame is the MAC address of STA120, AP 110 may not update the NAV.

[0106] In the existing standard, if the RA received by AP 110 during the first time period to carry the PPDU of the first frame is not the MAC address of AP 110, and the received power of the PPDU is greater than -82dBm, then AP 110 will update NAV. Here, -82dBm is for a PPDU with a bandwidth of 20MHz. For PPDUs with larger bandwidths, the threshold needs to be increased accordingly. For example, the thresholds corresponding to 40MHz, 80MHz, 160MHz, and 320MHz PPDUs are -79dBm, -76dBm, -73dBm, and -70dBm, respectively.

[0107] According to some example embodiments of this disclosure, increasing the received energy threshold to a certain extent (e.g., to -72dBm) can prevent AP 110 from updating the NAV for PPDUs with received energy greater than -82dBm, thereby reducing the probability that AP 110 will set the NAV in the first time period. In such an embodiment, AP 110 determines the received energy used to carry the PPDU of the first frame. If the received energy of AP 110 does not exceed a predetermined energy threshold (e.g., an increased energy threshold), AP 110 will keep the NAV unchanged.

[0108] When AP 110 supports dual NAV, if the RA of a PPDU received in the first time period is not the MAC address of AP 110, and the received power is less than a certain threshold, AP 110 does not need to update the Intra-BSS NAV if the PPDU is an Intra-BSS PPDU. If the frame is an Inter-BSS PPDU, or if it is impossible to distinguish between intra-BSS and inter-BSS PPDUs, AP 110 does not need to update the basic NAV. For PPDUs with a 20MHz bandwidth, this threshold can be set to greater than -82dBm. The threshold can be adjusted proportionally as the PPDU bandwidth increases, which will not be elaborated here.

[0109] If the AP 110 does not support dual NAV, and the RA of the PPDU received in the first time period is not the MAC address of the AP 110, and the received energy is less than a certain threshold, then the AP 110 does not need to update the NAV. Similarly, for a PPDU with a bandwidth of 20MHz, this threshold can be set to greater than -82dBm, and the threshold can be increased accordingly as the PPDU bandwidth increases.

[0110] In an alternative implementation of the above embodiments, AP 110 may not update the NAV if it receives a PPDU with received energy less than a certain threshold before the TXNAV expires. This further avoids the situation where, after the first time period ends, AP 110 is unable to send data within the remaining TXOP because it sets a basic NAV or NAV based on the OBSS PPDU.

[0111] In some example embodiments, after step 330, AP 110 may use RTS / CTS or MU-RTS / CTS before transmitting data within the TXOP. For example, before AP 110 transmits data within the TXOP, AP 110 may send an RTS frame to at least one receiving device and receive a CTS frame from at least one receiving device. Then, based on the reception of the CTS frame, AP 110 may transmit data to at least one receiving device.

[0112] As a simplified implementation of the above embodiments, after allocating a portion of TXOP (i.e., the first time period) to STA120, AP 110 may not update NAV during the first time period, regardless of whether the conditions discussed above are met.

[0113] In some example embodiments, AP 110 can be an extremely high throughput EHT access point, including but not limited to 802.11be-based communication servers, routers, switches, bridges, and other APs, as well as mobile phones, tablets, laptops, smartwatches, smart TVs, etc.

[0114] According to an example embodiment of this disclosure, an enhanced NAV setting mechanism is provided. Based on this enhanced mechanism, a site that obtains a TXOP can conditionally choose to update or not update the NAV, avoiding or reducing the need for the site to set the NAV in the first time period or within the TXOP, thereby allowing the site to continue data transmission within the remaining TXOP.

[0115] According to some example embodiments of this disclosure, an AP can update its maintained NAV based on predetermined rules or conditions, and this implementation is applicable to APs that support dual NAVs as well as APs that do not support dual NAVs. Reference will be made below. Figure 4 A flowchart is provided to describe a communication method 400 according to embodiments of the present disclosure. Method 400 can be... Figure 1 The implementation is shown at access point AP110. For ease of discussion, the following will be combined with... Figure 1 This describes method 400. It should be understood that method 400 is also applicable to other communication scenarios and devices.

[0116] In such Figure 4As shown in 410, the AP 110, which obtains a TXOP in the wireless LAN, allocates the first time segment of the TXOP to a non-access point device, such as STA 120, for data transmission. As previously described, the access point AP 110 can allocate the first time segment of the TXOP to STA 120 for data transmission by sending MU-RTS TXS TF 202 to STA 120.

[0117] In some example embodiments, the resources of the first time period can be used for P2P communication between STA 120 and STA 130, or for uplink transmission between STA 120 and AP 110.

[0118] In 420, AP 110 receives the first frame in the first time slot. Figure 2 In the example, the first frame could be SU PPDU204, whose TA is associated with STA 120.

[0119] In step 430, AP 110 determines whether all predetermined conditions have been met. In some example embodiments, the predetermined conditions may include:

[0120] • The first duration indicated by the first frame (i.e., the value of the Duration field) is greater than the current NAV value of AP 110.

[0121] • The RA in the first frame is not the MAC address of AP 110, or AP 110 is not the TXOP holder and the PPDU carrying the first frame does not include a frame requesting an immediate response from AP 110, or AP 110 is not the TXOP holder and the first frame is a trigger frame; and

[0122] Neither the RA nor the TA in the first frame is the MAC address of STA 120.

[0123] In 440, if the predefined conditions are met, AP 110 updates the NAV.

[0124] In an embodiment where access point AP 110 maintains a single NAV, the NAV can be updated as long as the above conditions are met, regardless of whether the first frame is an Intra-BSS PPDU, an Inter-BSS PPDU, or a PPDU that cannot be distinguished as Intra-BSS or Inter-BSS. Otherwise, if at least one of the above conditions is not met, AP 110 will not update the NAV. For example, Figure 2 In the example, the RA field in the first frame indicates the MAC address of STA 120, so AP 110 will not update NAV.

[0125] In some embodiments where the access point AP 110 supports dual NAVs, the AP 110 updates the Intra-BSS NAV in both NAVs only if the following condition is met:

[0126] • The first frame is an Intra-BSS frame. For the classification and definition of Intra-BSS and Inter-BSS PPDU, please refer to Section 26.2.2 of the IEEE 802.11ax standard.

[0127] • The first duration included in the first frame (i.e., the value of the Duration field) is greater than the current Intra-BSSNAV value of AP 110.

[0128] • The RA in the first frame is not the MAC address of AP 110, or AP 110 is not the TXOP holder and the PPDU carrying the first frame does not include a frame requesting an immediate response from AP 110, or AP 110 is not the TXOP holder and the first frame is a trigger frame; and

[0129] Neither the RA nor the TA in the first frame is the MAC address of STA 120.

[0130] If at least one of the above conditions is not met, AP 110 will not update the Intra-BSS NAV.

[0131] Additionally, in some embodiments where the access point AP 110 supports dual NAVs, the AP 110 will update the base NAV of the two NAVs if and only if the following conditions are met:

[0132] • The first frame is an Inter-BSS frame, or the first frame cannot be identified as Intra-BSS or Inter-BSS.

[0133] • The first duration included in the first frame (i.e., the value of the Duration field) is greater than the current basic NAV value of AP 110.

[0134] • The RA in the first frame is not the MAC address of AP 110, and

[0135] Neither the RA nor the TA in the first frame is the MAC address of STA 120.

[0136] If at least one of the above conditions is not met, AP 110 will not update the basic NAV.

[0137] In some example embodiments, after step 430, AP 110 may use RTS / CTS or MU-RTS / CTS before transmitting data within the TXOP. For example, before AP 110 transmits data within the TXOP, AP 110 may send an RTS frame to at least one receiving device and receive a CTS frame from at least one receiving device. Then, AP 110 may transmit data to at least one receiving device based on the reception of the CTS frame.

[0138] The exemplary embodiments of this disclosure provide a trigger-based transmission opportunity sharing mechanism. Based on this mechanism, an AP acquiring a TXOP (Transmission Opportunity Buffer) can allocate at least a portion of the TXOP to other non-AP sites. When the AP receives a frame containing a RA (Range Access Frame) or TA (Transmission Access Frame) corresponding to the MAC address of the non-AP, the AP may not update its NAV (Network Address Frame). Through this mechanism, the AP can avoid or reduce situations where it cannot transmit data for the remaining time of the TXOP due to updating the NAV. This improves the resource efficiency of the communication network and ensures system performance and communication quality.

[0139] According to some example embodiments of this disclosure, an AP can ignore the NAV it maintains based on predetermined rules or conditions, and this implementation is applicable to APs that support dual NAVs as well as APs that do not support dual NAVs. Reference will be made below. Figure 5 A flowchart is provided to describe a communication method 500 according to embodiments of the present disclosure. Method 500 can be... Figure 1 The implementation is shown at access point AP110. For ease of discussion, the following will be combined with... Figure 1 This describes method 500. It should be understood that method 500 is also applicable to other communication scenarios and devices.

[0140] like Figure 5 As shown, in 510, AP 110, which obtains the TXOP in the wireless LAN, allocates the first time slot in the TXOP to a non-access point device, such as STA 120, for data transmission. Figure 2 In the example, access point AP 110 can allocate the first time slot in TXOP to STA 120 for data transmission by sending MU-RTS TXS TF 202 to STA 120.

[0141] In 520, AP 110 receives the first frame in the first time slot. Figure 2 In the example, the first frame could be SU PPDU204, whose TA is associated with STA 120.

[0142] In 530, AP 110 updates the NAV maintained by AP 110 based on the first frame.

[0143] In 540, AP 110 determines whether the TA or RA of the first frame is associated with STA 120 and whether TXNAV is not equal to 0. In some example embodiments, "the TA or RA of the first frame is associated with STA 120 and TXNAV is not equal to 0" may be referred to as a predetermined condition.

[0144] If the TA or RA of the first frame is associated with STA 120 and TXNAV is not equal to 0, then in 550, AP 110 determines that the channel is idle based on virtual carrier sensing.

[0145] In embodiments where access point AP 110 does not support dual NAVs, AP 110 can ignore the NAV (not equal to 0) during the remaining TXOP period, or in other words, treat the NAV value as 0. This way, AP 110 can still send data during the remaining TXOP period even if the NAV value is not equal to 0.

[0146] In some embodiments where the access point AP 110 supports dual NAVs, the NAV can be either the Intra-BSS NAV within the basic service set or the basic NAV. For example, if the updated NAV is the Intra-BSS NAV, and the value of the basic NAV is 0, the AP 110 determines the channel is idle based on virtual carrier sensing. Conversely, if the value of the basic NAV is not 0, the AP 110 determines the channel is busy based on virtual carrier sensing.

[0147] In some other embodiments where the access point AP 110 supports dual NAVs, if the value of the Intra-BSS NAV is equal to 0 when the updated NAV is the basic NAV, the AP 110 determines the channel is idle based on virtual carrier sensing. Conversely, if the value of the Intra-BSS NAV is not equal to 0, the AP 110 determines the channel is busy based on virtual carrier sensing.

[0148] In some other embodiments where the access point AP 110 supports dual NAVs, if both the Intra-BSS NAV and the basic NAV are updated, that is, if neither of their values ​​is equal to 0, the AP 110 determines that the channel is idle based on virtual carrier sensing.

[0149] In an embodiment where access point AP 110 supports dual NAVs, if both NAVs are 0, AP 110 determines the channel is idle based on virtual carrier sensing. If at least one of the two NAVs is not 0, and the predetermined condition "the TA or RA of the first frame is associated with STA 120, and TXNAV is not equal to 0" is not met, AP 110 determines the channel is busy based on virtual carrier sensing.

[0150] In embodiments where the channel is determined to be idle, AP 110 can use RTS / CTS or MU-RTS / CTS after 550 before transmitting data within the TXOP. For example, before AP 110 transmits data within the TXOP, AP 110 can send an RTS frame to at least one receiving device and receive a CTS frame from at least one receiving device. Then, AP 110 can transmit data to at least one receiving device based on the reception of the CTS frame. This reduces collisions between PPDUs transmitted by AP 110 and PPDUs being transmitted in the P2P link or OBSS. Since RTS is a short frame, if RTS collides with PPDUs being transmitted in the P2P link or OBSS, the RTS frame will only interfere with a portion of the PPDU being transmitted. When the PPDU uses A-MPDU, only a portion of the MPDU will be affected. Furthermore, the affected portion can be corrected using FEC.

[0151] According to an example embodiment of this disclosure, a trigger-based transmission opportunity sharing mechanism is provided. An AP that acquires a TXOP and maintains dual NAVs can share a portion of the TXOP, for example, an allocated time period, with a non-AP site in this mechanism:

[0152] • If, during the allocated time period, only the Intra-BSS NAV is updated based on a radio frame, and the frame has a TA or RA equal to the MAC address of the non-AP site, and the TXNAV value is not equal to 0, the Virtual Carrier Sense Indicator (VCI) channel is idle when the Basic NAV timer is 0; otherwise, the VCI channel is busy when the Basic NAV timer is not 0.

[0153] • If, during the allocation period, only the basic NAV is updated based on a radio frame, and the frame has a TA or RA equal to the MAC address of the non-AP site, and the value of TXNAV is not equal to 0, the Virtual Carrier Sense Indicator (VCI) channel is idle when the Intra-BSS NAV timer is 0; conversely, the VCI channel is busy when the Intra-BSS NAV timer is not 0.

[0154] • If, during the allocated period, both the Intra-BSS NAV and the basic NAV are updated based on radio frames, and these frames have a TA or RA equal to the MAC address of the non-AP site, and the value of TXNAV is not equal to 0, then the Virtual Carrier Sense indicates that the channel is idle.

[0155] Otherwise, if both NAV timers are 0, the virtual carrier sense indicator channel is idle; if at least one of the two NAV timers is not 0, the virtual carrier sense indicator channel is busy.

[0156] Through the above mechanism, APs that obtain TXOPs can avoid or reduce situations where they are unable to send data within the remaining TXOPs due to setting the NAV of P2P links or OBSS PPDUs when TXNAV is not equal to 0. This improves the resource efficiency of the communication network and ensures system performance and communication quality.

[0157] In other embodiments of this disclosure, information about Figure 5 The simplified form of the described method 500. As discussed above, in method 500, AP 110 ignores the NAV value or treats the NAV value as 0 based on the predetermined condition "the TA or RA of the first frame is associated with STA 120 and TXNAV is not equal to 0" being met. In other example embodiments, AP 110 may ignore the NAV value or treat the NAV value as 0 solely based on the predetermined condition "TXNAV is not equal to 0".

[0158] In some embodiments where the access point AP 110 supports dual NAVs, AP 110 will ignore both the Intra-BSS NAV and the basic NAV when TXNAV is not equal to 0. In other words, AP 110 can treat the values ​​of Intra-BSS NAV and basic NAV as 0.

[0159] In some embodiments where the access point AP 110 does not support dual NAV, AP 110 can ignore the NAV if TXNAV is not equal to 0. In other words, AP 110 can treat the value of NAV as 0.

[0160] As an alternative embodiment, AP 110 may ignore the NAV value or treat the NAV value as 0 based on the predetermined condition "TXNAV is not equal to 0 and NAV is less than or equal to TXNAV" being met. When the predetermined condition is met, that is, when TXNAV is not equal to 0 and NAV is greater than TXNAV, AP 110 may ignore NAV or treat NAV as 0.

[0161] In this alternative embodiment, for AP 110 supporting dual NAVs, if Intra-BSS NAV is less than or equal to TXNAV, AP 110 may ignore Intra-BSS NAV or treat Intra-BSS NAV as 0. If Intra-BSS NAV is greater than TXNAV and TXNAV is not equal to 0, AP 110 may ignore the portion of Intra-BSS NAV less than or equal to TXNAV, or treat Intra-BSS NAV as 0 if TXNAV is not equal to 0. Similarly, if Basic NAV is less than or equal to TXNAV, AP 110 may ignore Basic NAV or treat Basic NAV as 0. If Basic NAV is greater than TXNAV and TXNAV is not equal to 0, AP 110 may ignore the portion of Basic NAV less than or equal to TXNAV, or treat Basic NAV as 0 if TXNAV is not equal to 0.

[0162] In this alternative implementation, for AP 110 that does not support dual NAV, if NAV is less than or equal to TXNAV, AP 110 may ignore NAV or treat NAV as 0. If NAV is greater than TXNAV and TXNAV is not equal to 0, AP 110 may ignore the portion of NAV less than or equal to TXNAV, or treat NAV as 0 if TXNAV is not equal to 0.

[0163] In some example implementations, AP 110 can use RTS / CTS or MU-RTS / CTS before transmitting data within the TXOP. This reduces collisions between PPDUs transmitted by AP 110 and PPDUs being transmitted in the P2P link or OBSS. Since RTS is a short frame, if RTS collides with a PPDU being transmitted in the P2P link or OBSS, the RTS frame will only interfere with a portion of the PPDU being transmitted. When the PPDU uses A-MPDU, only a portion of the MPDU will be affected. Furthermore, FEC can be used to correct the affected portion.

[0164] Figure 6 A schematic block diagram of a communication device 600 according to an example embodiment of the present disclosure is shown. Figure 6The communication device 600 shown can be implemented at the transmitting or receiving end of a communication, including but not limited to AP, STA, etc. Of course, other suitable devices can also be used. It should be understood that the communication device 600 is for illustrative purposes only and does not imply any limitation on the scope of this disclosure. Embodiments of this disclosure can also be embodied in communication devices with different architectures and functions. It should also be understood that the communication device 600 may include other elements or entities that are not shown for ease of description, but this does not mean that embodiments of this disclosure do not include these elements or entities.

[0165] like Figure 6 As shown, the communication device 600 includes an allocation unit 612, a receiving unit 614, and an update unit 616.

[0166] Allocation unit 612 is used to allocate the first time period in TXOP to a non-access point device for data transmission.

[0167] The receiving unit 614 is used to receive the first frame in the first time period. The access address or transmission address of the first frame is associated with the non-access point device.

[0168] Update unit 616 is used to keep the maintained network allocation vector NAV unchanged based on the first frame.

[0169] It should be understood that the allocation unit 612, receiving unit 614, and updating unit 616 in the communication device 600 can be used to implement, as per the above... Figure 3 For details of the other steps in the communication process discussed, please refer to the relevant descriptions above, which will not be elaborated here.

[0170] It should be understood that the communication device 600 can be implemented using application-specific integrated circuits, one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various processes of this disclosure, chips, boards, or communication devices.

[0171] Figure 7 A schematic block diagram of a communication device 700 according to an example embodiment of the present disclosure is shown. Figure 7 The communication device 700 shown can be implemented using any suitable device. It should be understood that the communication device 700 is for illustrative purposes only and does not imply any limitation on the scope of this disclosure. Embodiments of this disclosure can also be embodied in communication devices of different architectures and functions. It should also be understood that the communication device 700 may include other elements or entities that are not shown for ease of description, but this does not mean that embodiments of this disclosure do not include these elements or entities.

[0172] like Figure 7 As shown, the communication device 700 includes an allocation unit 712, a receiving unit 714, a determining unit 716, and an updating unit 718.

[0173] Allocation unit 712 is used to allocate the first time period in TXOP to a non-access point device for data transmission.

[0174] The receiving unit 714 is used to receive the first frame in the first time period.

[0175] Determining unit 716 is used to determine whether the following conditions are all met:

[0176] • The first frame is an Inter-BSS frame, or the first frame is not identified by either Inter-BSS or Intra-BSS;

[0177] • The first frame includes a first duration for data transmission that is greater than the second duration indicated by the basic NAV currently maintained by the access point device;

[0178] • The receive address of the first frame is not the Media Access Control (MAC) address of the access point device; and

[0179] • The access address or transmission address of the first frame is not associated with a non-access point device.

[0180] Update unit 718 is used to update NAV based on the satisfaction of predetermined conditions.

[0181] It should be understood that the communication device 700 can be implemented using application-specific integrated circuits, one or more FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various processes of this disclosure, chips, boards, or communication devices, etc.

[0182] Figure 8 This is a simplified block diagram of an example device 800 suitable for implementing embodiments of the present disclosure. Device 800 can be used to implement the communication device or communication apparatus of the present disclosure. As shown, device 800 includes one or more processors 810, and a transceiver 840 coupled to the processors 810;

[0183] In some example implementations, the transceiver 840 is used to implement the above. Figure 6 Middle receiving unit 614 or Figure 7 The function of the receiving unit 714 is detailed above and will not be repeated here.

[0184] The processor 810 can be used to implement the above. Figure 6The functions of the allocation unit 612 and the update unit 616 in the middle, or Figure 7 The functions of the allocation unit 712, the determination unit 716, and the update unit 718 are described above. Specific details can be found in the above text, based on the information provided. Figure 6 and Figure 7 The description will not be repeated here.

[0185] Optionally, the device 800 further includes a memory 820 coupled to the processor 810, the memory 820 for storing instructions executed by the processor, which, when executed by the processor, enable the processor to implement the above-mentioned... Figure 6 The functions of the allocation unit 612 and the update unit 616 in the middle, or Figure 7 The functions of the allocation unit 712, determination unit 716 and update unit 718 are detailed in the above description and will not be repeated here.

[0186] Transceiver 840 can be used for bidirectional communication. Transceiver 840 may have at least one communication interface for communication. The communication interface may include any interface necessary for communicating with other devices.

[0187] Processor 810 can be any type suitable for a local technology network and can include, but is not limited to, one or more of a general-purpose computer, a special-purpose computer, a microcontroller, a digital signal controller (DSP), and a controller-based multi-core controller architecture. Device 800 can have multiple processors, such as application-specific integrated circuit chips, which are time-subordinate to a clock synchronized with the main processor.

[0188] Memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 824, erasable programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that do not persist during power-off periods.

[0189] Computer program 830 includes computer-executable instructions that are executed by associated processor 810. Program 830 may be stored in ROM 820. Processor 810 can perform any suitable actions and processes by loading program 830 into RAM 820.

[0190] The embodiments of this disclosure can be implemented by means of program 830, enabling device 800 to perform as described in the reference. Figures 2 to 5 Any of the processes discussed herein. Embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0191] In some embodiments, program 830 may be tangibly contained in a computer-readable medium, which may include in device 800 (such as in memory 820) or other storage device accessible by device 800. Program 830 may be loaded from the computer-readable medium into RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0192] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or represented using some other illustration, it should be understood that the blocks, devices, systems, techniques, or methods described herein can be implemented as, as in the non-limiting examples, hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0193] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which execute in a device on a target's real or virtual processor to perform the above-referenced... Figures 3 to 5 The process / method described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided among program modules as needed. The machine-executable instructions for a program module can execute on a local or distributed device. In a distributed device, program modules can reside on both local and remote storage media.

[0194] Computer program code used to implement the methods of this disclosure may be written in one or more programming languages. This computer program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that when executed by the computer or other programmable data processing apparatus, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code may be executed entirely on a computer, partially on a computer, as a stand-alone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0195] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and so on. Examples of signals may include electrical, optical, radio, sound, or other forms of propagation signals, such as carrier waves, infrared signals, etc.

[0196] A computer-readable medium can be any tangible medium that contains or stores a program for or relating to an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More detailed examples of computer-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0197] Furthermore, although the operation of the methods of this disclosure is described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Rather, the steps depicted in the flowcharts may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps. It should also be noted that the features and functions of two or more devices according to this disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided and embodied by multiple devices.

[0198] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to well explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for communication, comprising: allocating, by an access point device, a first time period in a transmission opportunity (TXOP) to a non-access point device for data transmission, wherein the TXOP is obtained by the access point device in a wireless local area network (WLAN); receiving, by the access point device, a first frame in the first time period, wherein an access address or a transmit address of the first frame is associated with the non-access point device; and maintaining, by the access point device, a network allocation vector (NAV) based on the first frame.

2. The method of claim 1, wherein the access point device maintains a single NAV including the NAV.

3. The method of claim 1, wherein the access address or the transmit address of the first frame is a media access control (MAC) address of the non-access point device.

4. The method of claim 1, wherein the access point device allocates the first time period to the non-access point device through a multi-user request to send transmission opportunity sharing trigger frame (MU-RTS TXS) frame.

5. The method of claim 1, further comprising: sending, by the access point device, a request to send (RTS) frame to at least one receiving device before sending data; receiving, by the access point device, a clear to send (CTS) frame from the at least one receiving device; and sending, by the access point device, the data to the at least one receiving device.

6. The method of claim 1, wherein the access point device maintains two NAVs including the NAV, the NAV is an Intra-BSS network allocation vector (Intra-BSS NAV), and the method further comprises: updating, by the access point device, the Intra-BSS NAV based on a condition being satisfied, wherein the condition comprises: the first frame is an Intra-BSS frame; a first duration for data transmission included in the first frame is greater than a second duration indicated by an Intra-BSS NAV currently maintained by the access point device; a receive address of the first frame is not a media access control (MAC) address of the access point device; and an access address or a transmit address of the first frame is not associated with the non-access point device.

7. The method of claim 1, wherein the access point device maintains two NAVs including the NAV, the NAV is a basic NAV, and the method further comprises: updating, by the access point device, the basic NAV based on a condition being satisfied, wherein the condition comprises: the first frame is an Inter-BSS frame, or the first frame is not identified by either of an Inter-BSS or an Intra-BSS; a first duration for data transmission included in the first frame is greater than a second duration indicated by a basic NAV currently maintained by the access point device; a receive address of the first frame is not a media access control (MAC) address of the access point device; and an access address or a transmit address of the first frame is not associated with the non-access point device.

8. The method of claim 1, wherein maintaining the NAV further comprises: ​ The access point device determines a received energy for a physical layer protocol data unit, PPDU, carrying the first frame; and The access point device leaves the NAV unchanged based on the received energy not exceeding a predetermined energy threshold.

9. The method of claim 1, wherein the access point device is an extremely high throughput, EHT, access point.

10. A method for communication, comprising: an access point device obtaining a transmission opportunity, TXOP, in a wireless local area network, allocating a first time period in the TXOP to a non-access point device for data transmission; the access point device receiving a first frame in the first time period; and the access point device updating a network allocation vector, NAV, if a condition is met, the condition comprising: a first duration for data transmission included in the first frame being greater than a second duration indicated by a NAV currently maintained by the access point device, a receiving address of the first frame not being a media access control, MAC, address of the access point device, and an access address or a transmitting address of the first frame not being a MAC address of the non-access point device.

11. The method of claim 10, wherein the NAV is at least one of an Intra- basic service set, BSS, NAV and a basic NAV.

12. The method of claim 10, wherein the condition further comprises the first frame being an Intra-BSS frame, and the access point device updating the NAV comprises: the access point device updating an Intra-BSS NAV.

13. The method of claim 10, wherein the condition further comprises the first frame being an Inter-BSS frame, or the first frame not being identified by either of the Inter-BSS or Intra-BSS, and the access point device updating the NAV comprises: the access point device updating a basic NAV.

14. The method of claim 10, wherein the access point device maintains a single NAV including the NAV.

15. The method of claim 10, further comprising: prior to transmitting data, the access point device transmitting a request to send, RTS, frame to at least one receiving device; the access point device receiving a clear to send, CTS, frame from the at least one receiving device; and the access point device transmitting the data to the at least one receiving device.

16. A method for communication, comprising: an access point device obtaining a transmission opportunity, TXOP, in a wireless local area network, allocating a first time period in the TXOP to a non-access point device for data transmission; the access point device receiving a first frame in the first time period; the access point device updating a maintained network allocation vector, NAV, based on the first frame; and the access point device determining a channel to be idle based on virtual carrier sensing if an access address or a transmitting address of the first frame is associated with the non-access point device and a value of a TXNAV timer is not equal to 0. ​ ​ 17. The method of claim 16, wherein the access point device maintains a single NAV that includes the NAV.

18. The method of claim 16, wherein the access point device maintains two NAVs including the NAV, and the NAV is an Intra-BSS NAV, and the access point device determining the channel is idle based on virtual carrier sensing includes: if a value of a basic NAV of the two NAVs is equal to 0, then the access point device determines the channel is idle based on virtual carrier sensing.

19. The method of claim 16, wherein the access point device maintains two NAVs including the NAV, and the NAV is a basic NAV, and the access point device determining the channel is idle based on virtual carrier sensing includes: if a value of an Intra-BSS NAV of the two NAVs is equal to 0, then the access point device determines the channel is idle based on virtual carrier sensing.

20. The method of claim 16, wherein the access point device allocates the first period to the non-access point device through a Multi-User Request to Send Transmission Opportunity Sharing Trigger Frame, MU-RTS TXS TF.

21. The method of claim 16, further comprising: prior to transmitting data, the access point device transmitting a Request to Send, RTS, frame to at least one receiving device; the access point device receiving a Clear to Send, CTS, frame from the at least one receiving device; and the access point device transmitting the data to the at least one receiving device. the access point device is an Extremely High Throughput, EHT, access point.

22. The method of claim 16, wherein, 23. A communication device, comprising: at least one processor; at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the communication device to perform a method according to any of claims 1-9 or 10-15 or 16-22.

24. A computer readable storage medium having computer executable instructions stored thereon, which, when executed by a processor, cause the processor to perform a method according to any of claims 1-9 or 10-15 or 16-22.

25. A computer program product comprising computer executable instructions, wherein the computer executable instructions implement a method according to any of claims 1-9 or 10-15 or 16-22 when executed by a processor. ​

Images