Communication methods, apparatuses, and devices

Abstract

The application provides a communication method, device and equipment. The method comprises: a first access point generates a first frame, the first frame comprising a duration field, wherein the first frame is used to instruct a second access point to start using a transmission opportunity (TXOP) time resource, a first time indicated by the duration field is used to indicate a network allocation vector (NAV) of at least one station, and the NAV covers a transmission period of the second access point; and the first access point sends the first frame to the second access point and the at least one station. The application can reduce the influence of a hidden node on TXOP sharing, thereby improving the success rate of a TXOP return sharing type access point, and further improving communication efficiency.

Description

Technical Field

[0001] This application relates to the field of wireless communication, and more specifically, to a communication method, apparatus, and device. Background Technology

[0002] In wireless local area network (WLAN) systems, dense deployment of access points (APs) can cause mutual interference, leading to degraded latency and throughput. Multi-AP collaboration technology can alleviate these problems.

[0003] Multi-AP collaboration technology refers to the sharing of air interface resources through cooperation among multiple access points, thereby improving network performance, coverage, and user experience. For example, AP collaboration technology includes Coordinated Time Domain Multiple Access (Co-TDMA).

[0004] Co-TDMA mechanism refers to a mechanism in which multiple access points use channel resources in a time-sharing manner based on shared transmission opportunity (TXOP) to reduce service latency and increase transmission efficiency.

[0005] However, the success rate of TXOP returning to the shared node in the Co-TDMA mechanism provided by the relevant technologies needs to be further improved. Summary of the Invention

[0006] This application provides a communication method, apparatus, and device that can reduce the impact of hidden nodes on TXOP sharing, thereby improving the success rate of TXOP returning to the shared access point and thus helping to ensure the communication efficiency of Co-TDMA.

[0007] In a first aspect, a communication method is provided, the method comprising: a first access point generating a first frame, the first frame including a duration field, wherein the first frame is used to indicate that a second access point begins to use TXOP time resources, the duration field indicating a first time is used to indicate a network allocation vector (NAV) for at least one site, and the NAV covers the transmission period of the second access point; and the first access point transmitting the first frame.

[0008] Based on the first aspect mentioned above, in its first implementation, the first time is greater than or equal to the allocation time of the second access point.

[0009] Based on the first aspect or its first implementation, in its second implementation, the method further includes: during the protection time of the site under NAV, the first access point receives a third frame sent by the second access point, and regains control of the TXOP time resource; wherein the third frame is used by the second access point to return unused time in the TXOP time resource.

[0010] Based on the first aspect and any one of the first and second implementations described above, in its third implementation, the first frame includes a receive address RA field, wherein the RA field indicates the address of the second access point, which is used to indicate the same basic service set network allocation vector Intra-BSS NAV of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

[0011] In a second aspect, a communication method is provided, the method comprising: a second access point receiving a first frame sent by a first access point, the first frame including a duration field, wherein the first frame is used to indicate that the second access point begins to use TXOP time resources, the first time indicated by the duration field is used to indicate a network allocation vector (NAV) for at least one site, and the NAV covers the transmission period of the second access point; and, in response to the first frame, the second access point sending a second frame to the first access point and the at least one site.

[0012] Based on the second aspect mentioned above, in its first implementation, the value of the duration field in the second frame is 0.

[0013] Thirdly, a communication method is provided, the method comprising: a station receiving a first frame sent by a first access point, the first frame including a duration field, wherein the first frame is used to indicate that a second access point begins to use TXOP time resources, and the first time indicated by the duration field is used to indicate a network allocation vector (NAV) of at least one station; the station parsing the first frame; and the station setting the first time to NAV according to the parsing result, wherein the NAV covers the transmission period of the second access point.

[0014] Based on the third aspect mentioned above, in its first implementation, the first frame includes a receive address RA field, wherein the address of the second access point indicated by the RA field is used to indicate the same basic service set network allocation vector Intra-BSS NAV of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

[0015] Based on the first implementation of the third aspect described above, in its second implementation, the station sets the first time to NAV according to the parsing result, including: determining, according to the parsing result, that the value of the RA field in the first frame is the same as the address of the associated access point, and setting the first time to Intra-BSSNAV.

[0016] Based on the second implementation of the third aspect described above, in its third implementation, the method further includes: the station receiving a second frame sent by the second access point; the station parsing the second frame and determining that the value of the duration field in the second frame is 0; and the station maintaining the current Intra-BSS NAV.

[0017] Based on the third aspect mentioned above, in its fourth implementation, the station sets the first time to NAV according to the parsing result, including: determining, according to the parsing result, that the value of the received address RA field in the first frame is different from the address of the associated access point, and setting the first time to Basic Network Allocation Vector (Basic NAV).

[0018] Fourthly, a communication device is provided, configured at a first access point, the device comprising: a processing module for generating a first frame, the first frame including a duration field, wherein the first frame is used to indicate that a second access point begins to use TXOP time resources, the first time indicated by the duration field is used to indicate a network allocation vector (NAV) for at least one site, and the NAV covers the transmission period of the second access point; and a transceiver module for transmitting the first frame to the second access point and the at least one site.

[0019] Fifthly, a communication device is provided, configured at a second access point, the device comprising: a transceiver module, configured to receive a first frame transmitted by a first access point, the first frame including a duration field, wherein the first frame is used to indicate that the second access point begins to use TXOP time resources, the duration field indicating a first time is used to indicate a network allocation vector (NAV) for at least one site, and the NAV covers the transmission period of the second access point; and the transceiver module is further configured to, in response to the first frame, transmit a second frame to the first access point and the at least one site.

[0020] In a sixth aspect, a communication apparatus is provided, configured at a site, the apparatus comprising: a transceiver module, configured to receive a first frame transmitted by a first access point, the first frame including a duration field, wherein the first frame is used to indicate that a second access point begins to use TXOP time resources, and the first time indicated by the duration field is used to indicate a network allocation vector (NAV) for at least one site; a processing module, configured to parse the first frame; and the processing module is further configured to set the first time as the network allocation vector (NAV) based on the parsing result, wherein the NAV covers the transmission period of the second access point.

[0021] In a seventh aspect, an access point device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods of the first aspect or its implementations described above, or the methods of the second aspect or its implementations described above.

[0022] Eighthly, a site device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods in the third aspect or its implementations described above.

[0023] A ninth aspect provides a chip for implementing the methods of any one of the first to second aspects or their respective implementations. Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the methods of any one of the first to third aspects or their implementations.

[0024] In a tenth aspect, a readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to third aspects or their implementations described above.

[0025] Eleventhly, a communication device is provided, comprising: a processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the methods of any one of the first to third aspects or their implementations.

[0026] In a twelfth aspect, a communication system is provided, including an access point device and a terminal device, wherein the access point device is configured to perform the methods of the first aspect or the second aspect or their respective implementations described above, and the terminal device is configured to perform the methods of the third aspect or their respective implementations described above.

[0027] The above technical solution can ensure the NAV coverage of the cooperative access point transmission cycle, so that there is no interference (such as the hidden node of the second node occupying the channel) during the process of the cooperative access point returning control of the TXOP time resource to the shared access point. This ensures that the control of the TXOP time resource is successfully returned to the shared access point, which is conducive to improving the transmission efficiency of Co-TDMA. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 A schematic structural diagram of a communication system applicable to embodiments of this application is shown.

[0030] Figure 2 This diagram illustrates the interaction between an AP and a site sharing a TXOP under a TXS operation mechanism provided by related technologies.

[0031] Figure 3 This diagram illustrates the interaction of APs sharing TXOPs under a Co-TDMA mechanism provided by related technologies.

[0032] Figure 4 It shows Figure 3 The diagram illustrates a technical problem that exists in the Co-TDMA mechanism.

[0033] Figure 5 This is one of the interactive schematic diagrams of a communication method provided in the embodiments of this application.

[0034] Figure 6 This is one of the schematic diagrams of a Co-TDMA process framework provided in the embodiments of this application.

[0035] Figure 7 This is the second interactive schematic diagram of a communication method provided in the embodiments of this application.

[0036] Figure 8 This is the second schematic diagram of a Co-TDMA process framework provided in the embodiments of this application.

[0037] Figure 9 This is one of the schematic block diagrams of a communication device provided according to an embodiment of this application.

[0038] Figure 10 This is a second schematic block diagram of a communication device provided according to an embodiment of this application.

[0039] Figure 11 This is a third schematic block diagram of a communication device provided according to an embodiment of this application.

[0040] Figure 12 This is a schematic block diagram of a communication device provided according to an embodiment of this application.

[0041] Figure 13 This is a schematic block diagram of a chip provided according to an embodiment of this application.

[0042] Figure 14 This is a schematic block diagram of a communication system provided according to an embodiment of this application. Detailed Implementation

[0043] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0044] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Furthermore, the terms "first" and "second," etc., used herein are used only to distinguish different objects and not to describe a particular order.

[0045] It should be noted that, in the embodiments of this application, "at least one item" refers to one item or more items, "more items" refers to two items or more, and "at least two items" refers to two items or more. "At least one of the following items" or similar expressions can refer to any combination of these items. For example, at least one item of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c".

[0046] It should be noted that in the embodiments of this application, "and / or" indicates that the connected objects can have three relationships. For example, "A and / or B" can represent three scenarios: only A exists, only B exists, and both A and B exist simultaneously. The character " / " generally indicates that the preceding and following objects have an "or" relationship.

[0047] It should be understood that the "instruction" mentioned in the embodiments of this application can be a direct instruction or an indirect instruction. For example, A instructing B can mean that A directly instructs B, such as B being obtainable through A; or it can mean that A indirectly instructs B, such as A instructing C, where B is obtainable through C, for example, B and C are related.

[0048] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems, such as the Wireless Fidelity (WiFi) protocol. This WiFi protocol may include, but is not limited to, the 802.11 series protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0049] Figure 1 A schematic structural diagram of a communication system 100 applicable to embodiments of this application is shown. The communication system 100 may include an access point device 110 and a site device 120. The site device 120 can access the network through the access point device 110.

[0050] Access points can support communication or sensing based on WiFi protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0051] The site can support communication or sensing based on WiFi protocols, such as 802.11a, 802.11ax, 802.11ac, 802.11b, 802.11be, 802.11g, 802.11n, 802.11bn, or next-generation protocols.

[0052] The communication in the communication system 100 can be communication between access points and stations, or communication between stations, or communication between access points.

[0053] An access point acts as a bridge connecting wired and wireless networks. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0054] A station (STA) includes access point stations (AP STA) and non-access point stations (non-AP stations). For simplicity, access point stations are usually referred to as access points (AP), and non-access point stations as stations (STA). Station equipment is also called a station, a non-access point station (Non-AP STA), or a non-access point node.

[0055] In some scenarios, access points and sites can be devices used in vehicle networking, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0056] In some scenarios, the access point can be a terminal device (such as a mobile phone) with a WiFi chip or a network device (such as a router).

[0057] In this application embodiment, the site can be a mobile phone, tablet computer, computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, set-top box, wireless device in self-driving, vehicle communication device, wireless device in remote medical care, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city or smart home, wireless device, wireless communication chip, etc. that support WLAN or WiFi technology.

[0058] It should be understood that Figure 1 Only one access point and two sites are shown in the example. Optionally, the communication system 100 may include multiple access points or other numbers of sites. This application embodiment does not limit this.

[0059] Optionally, the communication system 100 may also include other devices, such as network controllers, gateways, and other network entities, which are not limited in this application.

[0060] To facilitate understanding of the embodiments of this application, the related technologies are described.

[0061] 802.11be introduced the TXOP sharing (TXS) mechanism. Through this mechanism, the access point (AP) can share part or all of its TXOPs with non-AP STAs within the Basic Service Set (BSS) during the acquired TXOP time, thereby optimizing service latency or throughput.

[0062] Figure 2 This diagram illustrates the interaction between an AP and a site sharing a TXOP under a TXS operation mechanism provided by related technologies. (Reference) Figure 2 The access point (AP) sends a Clear To Send to Self (CTS-to-self) frame to notify other devices that it is about to begin transmission. Understandably, CTS-to-self is part of the Request to Send / Clear to Send (RTS / CTS) mechanism. Compared to the complete handshake mechanisms of RTS-to-AP and CTS-from-AP, CTS-to-self is a simplified form because the access point device can directly reserve a channel by sending a CTS frame with its own destination address.

[0063] The AP sends a Multi-User Request To Send (MU-RTS) TXS trigger frame, which contains information about the sharing mode (TXOP Sharing Mode = 1) and specifies the non-AP STA (e.g., STA1) with which it will share the TXOP.

[0064] Upon receiving the aforementioned MU-RTS TXS trigger frame, Non-AP STA1 sends a Clear Transmit Response (CTS) to AP. The CTS response to AP indicates that Non-AP STA1 acknowledges its readiness to receive data.

[0065] Non-AP STA1 transmits data to the AP within the allocated time in a non-triggered block (non-TB) PPDU. For example, Non-AP STA1 can also transmit data to other non-AP STAs within the allocated time in a non-TB PPDU. For example, the reliability of data transmission can be ensured through block acknowledgments (BA), such as... Figure 2 The AP sends a BA to the non-AP STA1.

[0066] The above process occurs within the TXOP time obtained by the AP.

[0067] As can be seen, the TXS operation mechanism allows the AP to share part or all of its acquired TXOP time with non-AP STAs, enabling these STAs to communicate directly with other STAs without having to relay through the AP each time. This reduces the AP's workload, increases network throughput, and lowers service latency, especially in high-density and high-traffic wireless network environments.

[0068] Co-TDMA borrows from the TXS operating mechanism and extends it accordingly for multi-AP scenarios, such as... Figure 3 The diagram illustrates the interaction of AP-to-AP (AP) sharing of TXOPs under the Co-TDMA mechanism of draft protocol version 0.3. It should be noted that this application is based on the Co-TDMA process of draft standard version 0.3. This process framework is only a basic architecture for the inventive points of this application; therefore, if the subsequent standard definitions change, this application will change accordingly, and this application is not limited thereto.

[0069] refer to Figure 3 In multi-AP collaborative TXOP transmission, the roles include: Sharing AP and Coordinated AP. The AP that initiates the sharing process is called the Sharing AP, such as... Figure 3 AP1; AP(s) that are coordinated to participate in the process are called Coordinated AP(s), such as Figure 3 AP2 and AP3 are examples of APs in the sharing architecture. The sharing APs acquire a TXOP (Turn-Off Point) through air interface contention. The participating Coordinated APs (s) then share a TXOP segment in a time-sharing manner. The duration of each TXOP segment can be announced via an initial control frame. Thus, in the multi-AP cooperation process based on TXOPs, the APs (s) share the time and frequency resources during the TXOP period.

[0070] During the polling phase, the Sharing AP polls the Coordinated APs to determine which APs will participate in this TXOP sharing. The Coordinated APs determined to participate in this TXOP sharing must respond to the Sharing AP's polling, indicating whether they are willing to participate in the sharing process. For example, refer to... Figure 3The Sharing AP (AP1) initiates the Co-TDMA process by sending an initial control frame (ICF frame) and triggers subsequent signaling interactions. In response, the Coordinated APs (such as AP2 and AP3) acknowledge receipt of the ICF, confirming that the sharing request has been received. The ICF frame can be implemented using a Buffer Status Report Poll (BSRP frame).

[0071] During the TXOP allocation phase, the sharing AP instructs the coordinated AP to begin using the shared TXOP by sending a TXOP allocation frame, specifying the sharing parameters. This TXOP allocation frame can be implemented using a MU-RTS TXS trigger frame. The MU-RTS TXS trigger frame is a control frame used to coordinate the transmission activities of multiple STAs or APs within the same TXOP.

[0072] After receiving the TXOP Allocation Frame, the Coordinated AP will send a ClearToSend (CTS) response to the Sharing AP. This frame indicates that the Coordinated AP has acknowledged receiving the allocation information and is ready to begin transmission.

[0073] During the Frame Exchange Phase, the Coordinated AP and its associated STA exchange data frames, using allocated TXOPs for communication. Each Coordinated AP uses TXOPs in a predetermined time slot order to ensure no conflicts occur.

[0074] During the TXOP Return Phase, if a Coordinated AP has not used up its allocated time, it can return the remaining TXOPs to the Sharing AP in advance via a TXOP return frame. By returning unused TXOPs early, overall resource utilization can be improved and waste can be avoided.

[0075] As can be seen, the Co-TDMA scheme, by introducing the concepts of Sharing AP and Coordinated AP, enables efficient collaboration and resource sharing among multiple APs. The entire process begins with the transmission of ICF frames, proceeds through multiple stages including polling, TXOP allocation, frame switching, and TXOP return, ultimately completing a full multi-AP collaborative transmission process. This mechanism not only improves the performance and efficiency of wireless networks but also provides a technological foundation for future multi-AP collaborative operations.

[0076] However, the security of the TXOP return mechanism in the aforementioned Co-TDMA operation needs to be improved.

[0077] Figure 4 It shows Figure 3 This illustrates a security issue with the TXOP return mechanism in the Co-TDMA mechanism shown. (Reference) Figure 4 The Sharing AP (AP1) sends a MU-RTS TXS trigger frame to allocate multiple access point transmission opportunities. However, the Network Allocation Vector (NAV) protection set based on this frame only covers until the end of the CTS (Concurrent Transmission Time). Therefore, during the Allocation Time, a STA hidden from the Coordinated AP (AP2) may occupy the channel, causing the Coordinated AP to fail to successfully return the TXOP to the Sharing AP, or affecting its retransmission opportunity after the TXOP is returned to the Sharing AP. An exemplary process is as follows: AP1 allocates time resources via the MU-RTS TXS trigger frame, and AP2 responds with a CTS confirmation of reception. The NAV set by the site based on the MU-RTS TXS trigger frame only covers until the end of the CTS; however, during subsequent frame transmissions, due to the lack of NAV coverage, a hidden STA may suddenly occupy the channel, causing AP2 to encounter a busy channel when attempting to return the TXOP, ultimately leading to the failure of the TXOP return mechanism. This problem highlights the inadequacy of the existing mechanism in dealing with hidden node interference, and urgently needs improvement to enhance overall security and reliability.

[0078] The technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, all of which fall within the protection scope of the embodiments of this application.

[0079] Figure 5 This illustration shows one of the information interaction diagrams of a communication method P500 applicable to embodiments of this application. (Reference) Figure 5 The embodiment described in the figure includes at least the following:

[0080] In S510, the first access point generates a first frame, which includes a duration field. The first frame is used to indicate that the second access point starts using the TXOP time resource. The duration field indicates a first time used to indicate the NAV of at least one site, and the NAV covers the transmission period of the second access point.

[0081] In this application, the first frame is used to indicate that the second access point begins using the TXOP time resource. (See reference...) Figure 3 The primary function of the TXOP allocation frame is to trigger the coordinated AP to begin using the shared TXOP and to indicate the sharing parameters. Therefore, in an exemplary embodiment, the first frame mentioned above may be a TXOP allocation frame.

[0082] For example, refer to Figure 5 As a Sharing AP, the first access point 510 generates a TXOP allocation frame, which is used to instruct the second access point 520 (Coordinated AP) to start using the TXOP time resource.

[0083] In an exemplary embodiment, the TXOP allocation frame may contain the following fields.

[0084] The Frame Control Field is used to define the frame type and subtype, indicating that this is a MU-RTS frame.

[0085] The Duration / ID Field is used to set the NAV, thereby informing other devices not to attempt to access the channel for a future period. In related technologies, the value of this field is generally set to SIFS+CTS frame time.

[0086] The Receiver Address (RA) field indicates the address of the receiving device for this frame. In related technologies, the value of this field is the broadcast address.

[0087] The Transmitter Address (TA) field is the address of the device that initiated the frame.

[0088] Understandably, this frame also contains other fields for indicating sharing parameters, which will not be elaborated here.

[0089] As mentioned above, such as Figure 3In the related technologies shown, the Duration field value in the TXOP allocation frame is SIFS+CTS frame time. However, the NAV set accordingly can only cover up to the end of CTS and cannot fully cover the Allocation time. This presents a technical problem that the Sharing AP may not be able to successfully regain control of the TXOP.

[0090] In the solution provided in this application, the Duration field value in the TXOP allocation frame is set to: First Time. This First Time is a calculated time value, specifically ensuring that the NAV set by the site can cover the 520 transmission cycle of the second access point, thereby ensuring coverage of all activities of the Coordinated AP throughout the entire transmission cycle.

[0091] In an exemplary embodiment, the first time value is greater than or equal to the Allocation Time value to ensure that the NAV covers at least all activities of the Coordinated AP throughout the entire transmission cycle.

[0092] As can be seen, by setting an appropriate Duration field value in this embodiment, it can be ensured that all stations receiving the frame (including the hidden nodes of the Coordinated AP) can correctly set their NAV, thereby avoiding channel interference during subsequent transmission and ensuring that the Sharing AP may not be able to successfully regain control of the TXOP.

[0093] For example, the first frame described above can be implemented using a MU-RTS TXS trigger frame. The MU-RTS TXS trigger frame allows the AP to trigger multiple non-AP sites to simultaneously perform uplink transmissions, which helps reduce channel contention and improve spectrum utilization. Through the MU-RTS TXS trigger frame, the AP can allocate specific Resource Units (RUs) to each participating STA. These RUs can be different sets of subcarriers to achieve spatial multiplexing. The frame also contains the necessary information to synchronize the transmission time of all participating STAs, ensuring they start transmitting data at the same time, thereby avoiding collisions.

[0094] In S520, the first access point sends a first frame to the second access point and at least one station.

[0095] The Sharing AP will send out the first frame it generates (such as the MU-RTS TXS trigger frame). This first frame will be captured by all devices capable of receiving it, including the Coordinated AP (second access point 321) and any potentially hidden nodes (such as...). Figure 3 (STA shown in the image).

[0096] It should be noted that the reference Figure 5 S530 and S540 are the processing steps of the second access point 520 and the site 530 after receiving the first frame, respectively. In this embodiment of the application, the execution order of S530 and S540 is not distinguished.

[0097] In S530, station 530 parses the first frame and sets the NAV, and the NAV covers the transmission cycle of the second access point.

[0098] NAV is a counter stored in the device's MAC layer, representing the remaining time (in microseconds) that the channel will be occupied by other devices. During this period, the device postpones its own transmission to avoid collisions. NAV is updated by setting the NAV value in the Duration field of received frames (such as RTS, CTS, ACK, or data frames). NAV decrements over time, and once it reaches zero, the device can attempt to compete for the channel.

[0099] For example, the specific implementation of setting the NAV based on the first frame may include the following steps.

[0100] Step 11: The station receives the first frame.

[0101] The site determines whether the first frame belongs to a frame type that can be updated to NAV. For example, any control frame (e.g., CTS, RTS, TXOP Allocation Frame) that contains a Duration field may trigger an NAV update.

[0102] Step 12: The site extracts the Duration field from the first frame and compares the site's current NAV with the Duration field value in the first frame.

[0103] When the Duration field value in the first frame is greater than the remaining NAV of the site, the NAV will be updated to the Duration field value.

[0104] By following the steps above, it can be ensured that the NAV set by the site is greater than or equal to the Duration field value in the first frame, thereby preventing the second access point from hiding the site's occupation of the channel during the shared TXOP period.

[0105] In this embodiment of the application, any station that receives the first frame mentioned above (including...) Figure 3The hidden node (STA) of the CoordinatedAP shown in the image parses the Duration field value in the frame and can set its own NAV based on steps 11 and 12 above. Once the station sets its NAV, it will avoid contention or occupancy of the channel until the NAV timeout expires. This effectively prevents other stations (especially hidden nodes) from occupying the channel during the CoordinatedAP's transmission cycle.

[0106] In this embodiment of the application, since the Duration field value in the first frame is set to the aforementioned first time, the NAV of the site can completely cover all activities of the Coordinated AP throughout the entire transmission cycle, thereby ensuring that the TXOP return frame returned by the Coordinated AP to the Sharing AP is not interfered with.

[0107] In an exemplary embodiment, after receiving the first frame and setting its NAV, the Coordinated AP begins using the TXOP time resources allocated to it to transmit data with its associated site. During data transmission between the Coordinated AP and its associated site, since the NAVs of other sites (including hidden nodes) are active, they will not compete for or occupy the channel, thus ensuring the smooth operation of the Coordinated AP's transmission.

[0108] refer to Figure 5 In S540, the second access point 520 generates a third frame, which is used to return unused time in the TXOP time resource. In S550, the first access point 510 receives the aforementioned third frame.

[0109] The third frame mentioned above is used to return any unused allocated time in the TXOP to the Sharing AP in advance. Therefore, in this embodiment, the third frame mentioned above is a TXOP return frame.

[0110] After the Coordinated AP completes its data transmission task within the TXOP time resource, if there are still unused time resources, it generates a third frame (TXOP return frame) to return these unused time resources. This third frame is used to return the TXOP time resource controller to the first access point 510, specifically informing the Sharing AP of the current remaining TXOP time resources so that the Sharing AP can reallocate or utilize these time resources.

[0111] After receiving the third frame, the Sharing AP can understand the Coordinated AP's usage of TXOP time resources and perform further time resource management and allocation accordingly. Since the NAVs of other sites (including hidden nodes) are active, they will not compete for or occupy the channel, thus ensuring that the controller of TXOP time resources safely returns to the Sharing AP.

[0112] It should be noted that the reference Figure 6 By delaying the access channel duration through NAV, the multi-access point transport opportunity allocates the frame (first frame), extending the time until AP1 (Sharing AP) regains the remaining unused time in the TXOP. This covers the following processes: frame exchange in BBS2, TXOP return frame transmission, and the Sharing AP sending an acknowledgment frame (ACK) after receiving the TXOP return frame and regaining the remaining unused time in the TXOP. Compared to Figure 3 This application obviously solves the above-mentioned technical problems existing in the related technologies and effectively ensures the security of the TXOP return mechanism.

[0113] Through such Figure 5 In the illustrated embodiment, TXOP reclamation is completed within the protected time window, effectively preventing interference (including hidden node channel occupancy) during the process of the Coordinated AP returning control of TXOP time resources to the Sharing AP. This not only ensures the successful return of control of TXOP time resources to the Sharing AP but also improves the overall network transmission efficiency and resource utilization. Furthermore, the solution provided in this application fully utilizes existing frame formats without requiring additional fields, exhibiting high compatibility.

[0114] Figure 7 This is a second schematic diagram illustrating information interaction in a communication method P700 applicable to embodiments of this application. Method P700 is implemented based on method P500, and the specific implementations of the features included in method P500 are applicable to method P700. (Reference) Figure 7 The embodiment described in the figure includes at least the following:

[0115] In S710, the first access point 510 generates a first frame, which includes a duration field and an RA field. The first frame is used to indicate that the second access point starts using the TXOP time resource. The duration field indicates a first time, and the RA field indicates the address of the second access point.

[0116] As described in the embodiment corresponding to S510 above, as a Sharing AP, the first access point 510 generates a TXOP allocation frame, which is used to trigger the second access point 520 (Coordinated AP) to start using the TXOP time resource.

[0117] The value settings of the Duration field in the TXOP Allocation Frame provided in this application embodiment are as in the embodiment corresponding to S510, and will not be described in detail here.

[0118] In related technologies, the RA field value in the TXOP allocation frame is the broadcast address. If the RA field value in the TXOP allocation frame follows this related technology, the station receiving the TXOP allocation frame, after parsing the frame, will determine that the RA field value is different from the address of the associated access point and will set a basic NAV. Since the basic NAV prevents the station from occupying the channel during the NAV protection period, the station associated with the second access point cannot transmit data during the period when the second access point obtains the TXOP. In this embodiment, to ensure data transmission between the Coordinated AP and its associated STA, the RA field value in the TXOP allocation frame is set to the address of the second access point 520. Since the RA field value in the first frame is the address of the second access point 520, the station associated with the second access point will set an Intra-BSS NAV according to the Duration field value in the first frame, thus not affecting the transmission from the station associated with the second access point to the second access point, ensuring data interaction between the second access point and its associated station. Through this setting, it can be ensured that the hidden nodes of the Coordinated AP near the Sharing AP cannot occupy the transmission opportunity, while not affecting the normal communication of the Coordinated AP and its associated STA.

[0119] In one exemplary embodiment, the relevant fields and field values ​​in the first frame described above are shown in Table 1.

[0120] Table 1

[0121] Fields Field value Duration Allocation time for the second access point RA Address of the second access point

[0122] In S720, the first access point 510 sends the aforementioned first frame to the second access point and at least one station.

[0123] If the Sharing AP sends the first frame, the first frame will be captured by all stations that can receive it, including the Coordinated AP (second access point 520), the second station 532 (the station associated with the second access point), and the first station 531 (the station not associated with the second access point).

[0124] It should be noted that the reference Figure 7 S730, S730' and S730" are the processing steps of the second access point 520, the second station 532 and the first station 531 after receiving the first frame, respectively. In this embodiment of the application, the execution order of S730, S730' and S730" is not distinguished.

[0125] After receiving the first frame, the second station 532 executes S730': the second station parses the first frame and sets the Intra-BSS NAV.

[0126] For example, the specific implementation of setting the NAV by the second station based on the first frame may include the following steps.

[0127] Step 21: The second station receives the first frame.

[0128] The second station determines whether the first frame belongs to a frame type eligible for NAV updates. For example, any control frame (e.g., CTS, RTS, TXOP Allocation Frame) containing a Duration field may trigger an NAV update. Since the first frame can be a TXOP Allocation Frame, it can trigger an NAV update.

[0129] Step 22: The second station checks whether the RA field value of the first frame belongs to this BSS.

[0130] A station sets the Duration of a frame to intra-BSS Duration only if the RA field value carried in the frame belongs to the local BSS. Since the RA field value in the first frame is the same as the address of the access point associated with the second station, the second station can set its intra-BSS Duration based on the duration field value in the first frame.

[0131] Step 23: The second station extracts the Duration field from the first frame and compares the current NAV of the station with the Duration field value in the first frame.

[0132] If the Duration field value in the first frame is greater than the remaining time of the site's current NAV, then its intra-BSS NAV is set through the Duration field value.

[0133] By following the steps above, it can be ensured that the intra-BSS NAV set by the second site is greater than or equal to the Duration field value in the first frame, thereby ensuring data transmission between the second access point and its associated site during the shared TXOP period.

[0134] As can be seen, the Intra-BSS NAV is the NAV of the same BSS (i.e., the device under the same AP). When the Intra-BSS NAV has not expired, it can still respond to the AP's trigger frame to carry out uplink data transmission, thereby improving channel multiplexing efficiency.

[0135] In this embodiment, after receiving the first frame, the second station 532 can set the Intra-BSS NAV to the Duration field value (i.e., the first time) in the first frame based on steps 21-23. Therefore, the Intra-BSS NAV set by the second station 532 covers the transmission period of the second access point 520, thereby ensuring data transmission between the second access point and its associated stations during the shared TXOP period.

[0136] As shown in Table 1, the first frame enables the associated STA (second site 532) of the second access point to set the Intra-BSS NAV (instead of the Basic NAV), thereby allowing the transmission of data (such as ACK / data frames) to the Coordinated AP within the authorized usage time of the second access point, effectively opening a channel for the associated STA of the Coordinated AP. Furthermore, this does not affect subsequent message interactions between the second site 532 and the Coordinated AP, ensuring the effective utilization of TXOP.

[0137] Continue to refer to Figure 7 After receiving the first frame, the first station 531 executes S730: parse the first frame and set the Basic NAV.

[0138] For example, the specific implementation of setting the NAV by the first site according to the first frame may include the following steps.

[0139] Step 31: The first station receives the first frame.

[0140] The first station determines whether the first frame belongs to a frame type that can be updated to NAV. For example, any control frame (e.g., CTS, RTS, TXOP Allocation Frame) that contains a Duration field may trigger an NAV update.

[0141] Step 32: The first station checks whether the RA field value of the first frame belongs to this BSS.

[0142] A station only sets the Duration of a frame to intra-BSS Duration if the RA field value carried in the frame belongs to the local BSS. Since the RA field value in the first frame is different from the address of the access point associated with the first station, the first station does not set intra-BSS NAV, but sets it to Basic NAV.

[0143] Step 33: The first station extracts the Duration field from the first frame and compares the station's current NAV with the Duration field value in the first frame.

[0144] When the Duration field value in the first frame is greater than the remaining time of the site's current NAV, its Basic NAV is set by the Duration field value.

[0145] By following the steps above, it can be ensured that the Basic NAV set by the first site is greater than or equal to the Duration field value in the first frame. Thus, during the TXOP sharing period of the second access point, the Basic NAV will prevent the first site from occupying the channel within the NAV protection period, thereby avoiding interference with the transmission of the Coordinated AP and ensuring that the TXOP is successfully returned to the Sharing AP.

[0146] As can be seen from Table 1, the first frame can suppress the hidden node of the second access point. For example, with Allocation Time = 400μs, device A (the hidden node of the second access point) sets Basic NAV = 400μs, meaning it is prohibited from occupying the main channel for 400μs. For example, it is prohibited from sending data to the Sharing AP for 400μs, thereby avoiding problems such as competing for the main channel with the TXOP return frame, and effectively ensuring that the TXOP resource controller returns to the Sharing AP.

[0147] Continue to refer to Figure 7 After receiving the first frame, the second access point 520 executes S730 and S740.

[0148] In S730, the second access point generates a second frame, in which the duration field has a value of 0.

[0149] For example, the second access point 520 generates a response frame (CTS frame) in response to a TXOP allocation frame (such as a MU-RTS TXS trigger frame) sent by the first access point.

[0150] It should be noted that in related technologies, the CTS frame inherits the Duration setting of the MU-RTS TXS trigger frame. However, in this embodiment, the value of the Duration field in the second frame is set to 0, as shown in Table 2.

[0151] Table 2

[0152] Fields Field value Purpose of setting Duration 0 To prevent the second node associated with the STA from being locked by the Basic NAV

[0153] If the related technology is adopted, and the second frame inherits the Duration setting of the first frame, then the Duration field value in the second frame will be, for example, Allocation Time—SIFS—CTS time. Furthermore, the device receiving the second frame, such as the second site, will set the Basic NAV based on the Duration field value in the second frame, thereby preventing it from sending data to the second access point during the Basic NAV protection time. Table 3 illustrates the differences between the CTS frame using the related technology and the second frame (CTS frame) provided in this application.

[0154] Table 3

[0155]

[0156] As can be seen, in this application, the second frame (CTS frame) does not use the Duration setting inherited from the first frame (MU-RTS TXS trigger frame) in related technologies, thereby avoiding the Basic NAV generated by this frame from preventing its associated STA from sending messages during the shared allocation time.

[0157] In S740, the second access point sends a second frame to the first access point and at least one other station. This frame is captured by the first access point. This frame is also captured by all stations capable of receiving it, including the second station 532 and the first station 531.

[0158] It should be noted that the reference Figure 7 S750, S750' and S750" are the processing steps of the second access point 520, the second station 532 and the first station 531 after receiving the second frame, respectively. In this embodiment of the application, the execution order of S750, S750' and S750" is not distinguished.

[0159] In this process, after receiving the second frame, the second station 532 executes S750': parse the second frame and keep Intra-BSSNAV.

[0160] For example, a specific implementation of the second station maintaining the current NAV without updating it after receiving the second frame may include the following steps.

[0161] Step 41: The second station receives the second frame.

[0162] The second station determines whether the second frame belongs to a frame type eligible for NAV updates. For example, any control frame (e.g., CTS, RTS, TXOP Allocation Frame) containing a Duration field may trigger an NAV update. The current second frame is a CTS and contains a Duration field, therefore the next step is executed.

[0163] Step 42: The second station checks whether the RA field value of the second frame belongs to this BSS.

[0164] A site only sets the duration of a frame to intra-BSS duration if the RA field value carried in the frame belongs to the local BSS. Since the RA field value in the second frame is different from that of the associated access point, the second site will not set intra-BSS duration accordingly.

[0165] Step 43: The second station extracts the Duration field from the second frame and compares the current NAV of the station with the Duration field value in the second frame.

[0166] Since the Duration field value (0) in the second frame is less than the current intra-BSS NAV, the current intra-BSS NAV is maintained without NAV update, thus continuing to protect the Coordinated AP transmission cycle without affecting its own message interaction.

[0167] Among them, after receiving the second frame, the first station 531 executes S750: parse the second frame and keep the Basic NAV.

[0168] Similar to the processing logic in steps 41-43, after receiving the second frame, the first station 531 parses the duration field value and finds it to be 0, thus maintaining the previous Basic NAV unchanged. This continues to protect the Coordinated AP transmission cycle and prevents it from occupying the channel.

[0169] Continue to refer to Figure 7 In the S750, the second access point transmits data with the associated second site.

[0170] Example reference Figure 8 During the “Frame Interaction in BBS2” process, the NAV status of each device is shown in Table 4.

[0171] Table 4

[0172] Equipment type NAV status Channel permissions First station (e.g.) Figure 8 STA1) Basic NAV effective Sending is prohibited Second station (e.g.) Figure 8 STA2) Intra-BSS NAV effective Running the second access point to send data / ACK Second access point (such as) Figure 8 (AP2) No NAV limit Free to send

[0173] Referring to Table 4, in this embodiment of the application, by setting the fields in the first frame (as shown in Table 1) and the fields in the second frame (as shown in Table 2), the hidden node is suppressed (i.e., Basic NAV prevents it from interfering with the shared transmission) and the associated site of the second access point is allowed to communicate unimpeded (i.e., Intra-BSS NAV allows communication within the local BSS). Therefore, the data transmission process between the second access point and the associated site can be executed smoothly.

[0174] Continue to refer to Figure 7 In S760, the second access point generates a third frame, which is used to return unused time from the TXOP time resource to the first access point.

[0175] After the Coordinated AP completes its data transmission task within the TXOP time resource, if there are still unused time resources, it will generate a third frame to return these unused time resources. Therefore, the purpose of the third frame is to inform the Sharing AP of the remaining TXOP time resources so that the Sharing AP can reallocate or utilize these time resources.

[0176] In S770, the first access point receives the third frame sent by the second access point. Thus, the sharing AP obtains the unused time from the TXOP time resource from the coordinated AP, and the sharing AP successfully regains control of the TXOP.

[0177] At this time, the Basic NAV initially set in the first frame has not expired (e.g., 50μs remaining). The first station (including the hidden node of the second access point) is still in a silent state, that is, the first station will not compete for or occupy the channel, thus ensuring the smooth transmission of the third frame, that is, the Coordinated AP safely returns the TXOP Return frame to the SharingAP.

[0178] Therefore, after receiving the third frame, the Sharing AP can understand the Coordinated AP's usage of TXOP time resources and perform further time resource management and allocation accordingly. Furthermore, after the Coordinated AP sends the TXOP return frame, if the STAs near the Sharing AP are still within the NAV protection period of the first frame, the Sharing AP can send an ACK and obtain a transmission opportunity, and surrounding hidden nodes cannot affect its subsequent transmission.

[0179] like Figure 7In the illustrated embodiment, firstly, the device type is distinguished by the RA field of the first frame (MU-RTS TXS trigger frame), enabling precise NAV control. Specifically, the second site (associated STA) is configured with Intra-BSS NAV (allowing local transmission), while the first site (non-associated STA) is configured with Basic NAV (forced silence), thus resolving the hidden terminal interference problem. Secondly, setting Duration=0 in the second frame (CTS) prevents NAV reset, ensuring uninterrupted network protection during the TXOP shared period. The third frame (TXOP Return) completes the return of the remaining time within the NAV protection window, preventing hidden nodes from preempting the channel, thereby ensuring the safe reclamation of TXOP time resources. Thirdly, the second access point (Coordinated AP) communicates freely with the associated site during the allocated time, while the first access point (Sharing AP) achieves conflict-free resource reclamation through network-wide NAV protection, significantly improving the throughput and reliability of multi-AP collaboration.

[0180] As can be seen, the embodiments of this application achieve precise NAV control through the collaborative design of existing related fields in the TXOP allocation frame and CTS frame. This ensures the security of TXOP return by eliminating hidden terminal threats through Basic NAV, and guarantees smooth local services of cooperating APs and efficient communication through Intra-BSS NAV. Furthermore, the solution provided in this application fully utilizes existing frame formats without adding any new fields, exhibiting high compatibility.

[0181] The following combination Figure 8 A specific implementation of the receiving method P700. (See reference) Figure 8 Suppose that at time X, AP1 (Sharing AP) sends a MU-RTS TXS trigger frame (first frame). In this frame, the Duration field is set to the Allocation Time of AP2 (Coordinated AP), and the RA field value is the address of AP2.

[0182] STA1 parses the first frame and sets Basic NAV to Allocation Time (covering the entire shared period). STA2 parses the first frame and sets Intra-BSS NAV to Allocation Time.

[0183] At time X+ΔT1, AP2 responds to CTS (second frame), in which Duration = 0. Therefore, after STA1 / STA2 parses the second frame, neither updates NAV (maintaining the original state).

[0184] At time point X+ΔT2, AP2 transmits data within BSS2. During this process, STA1's Basic NAV is active, meaning STA1 remains silent; STA2's Intra-BSS NAV is active, thus it can send data to AP2.

[0185] At time X+ΔT3, AP2 sends a TXOP Return frame (the third frame). After receiving the third frame, AP1 can reclaim the remaining TXOP time. Afterwards, the entire network's NAV expires, and the channel is released.

[0186] pass Figure 8 The illustrated embodiment clearly demonstrates that the embodiments of this application achieve Basic / Intra-BSS NAV splitting through RA addressing of the MU-RTS TXS trigger frame, thereby enabling precise NAV control. Specifically, the NAV protection window covers the entire TXOPReturn process, ensuring the safe reclamation of time resources. Furthermore, different cooperative access points are assigned a first time (i.e., the Duration field value in the first frame), such as the first time being the Allocation Time of the current AP, which helps ensure compatibility of multi-AP collaboration.

[0187] The above text combined Figures 5 to 8 The method embodiments of this application are described in detail below, in conjunction with... Figures 9 to 11 The present application describes the device embodiments in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.

[0188] Figure 9 A schematic block diagram of a communication device 900 according to an embodiment of this application is shown. The communication device 900 can be a shared access point device (Sharing AP) in multi-access point cooperative communication, or a component of the access point device, such as a chip, circuit, or module. Figure 9 The communication device 900 includes:

[0189] Processing module 901 is configured to generate a first frame, the first frame including a duration field, wherein the first frame is used to indicate that the second access point begins to use TXOP time resources, the first time indicated by the duration field is used to indicate the network allocation vector (NAV) of at least one site, and the NAV covers the transmission period of the second access point; and transceiver module 902 is configured to send the first frame to the second access point and the at least one site.

[0190] Based on the above-mentioned communication device 900, in its first implementation, the first time is greater than or equal to the allocation time of the second access point.

[0191] Based on the above-mentioned communication device 900 or its first implementation, in its second implementation, the transceiver module 902 is further configured to receive a third frame sent by the second access point during the protection time of the site being in NAV, and the processing module 901 is further configured to regain control of the TXOP time resource; wherein, the third frame is used by the second access point to return the unused time in the TXOP time resource.

[0192] Based on the above-mentioned communication device 900 and any one of its first and second implementations, in its third implementation, the first frame includes a receive address RA field, wherein the RA field indicates the address of the second access point, which is used to indicate the same basic service set network allocation vector Intra-BSS NAV of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

[0193] It should be understood that the communication device 900 described in the embodiments of this application may correspond to the first access point in the method embodiments of this application, and the various units in the device 900 and the other operations and / or functions described above are respectively for implementing Figure 5 or Figure 7 The corresponding processes applied to the first access point device in the above embodiments will not be described in detail here for the sake of brevity.

[0194] Figure 10 A schematic block diagram of a communication device 1000 according to an embodiment of this application is shown. The communication device 1000 can be a coordinated access point device (AP) in multi-access point cooperative communication, or a component of the access point device, such as a chip, circuit, or module. Figure 10 The communication device 1000 includes:

[0195] The transceiver module 1001 receives a first frame sent by a first access point. The first frame includes a duration field, wherein the first frame is used to indicate that a second access point starts using TXOP time resources, and the first time indicated by the duration field is used to indicate the network allocation vector (NAV) of at least one site, and the NAV covers the transmission period of the second access point; the transceiver module 1001 is also used to respond to the first frame by sending a second frame to the first access point and the at least one site.

[0196] Based on the above-mentioned communication device 1000, in its first implementation, the device further includes: a processing module 1002; the processing module 1002 is used to generate a second frame, wherein the field value of the duration field in the second frame is 0.

[0197] Based on the above-mentioned communication device 1000 or its first implementation, in its second implementation, the processing module 1002 is used to parse the first frame and start using TXOP time resources according to the parsing result.

[0198] It should be understood that the communication device 1000 described in the embodiments of this application may correspond to the second access point in the method embodiments of this application, and the various units in the device 1000 and the other operations and / or functions described above are respectively for implementing Figure 5 or Figure 7 The corresponding processes applied to the second access point device in the embodiments described herein will not be repeated here for the sake of brevity.

[0199] Figure 11 A schematic block diagram of a communication device 1100 according to an embodiment of this application is shown. The communication device 1100 can be a station device associated with an access point device in multi-access point cooperative communication, or a component of the station device, such as a chip, circuit, or module. Figure 11 The communication device 1100 includes:

[0200] The transceiver module 1101 is configured to receive a first frame sent by a first access point, the first frame including a duration field, wherein the first frame is used to indicate that a second access point begins to use TXOP time resources, and the first time indicated by the duration field is used to indicate the network allocation vector (NAV) of at least one station; the processing module 1102 is configured to parse the first frame; and the processing module 1102 is further configured to set the first time as the network allocation vector (NAV) according to the parsing result, and the NAV covers the transmission period of the second access point.

[0201] Based on the above-mentioned communication device 1100, in its first implementation, the first frame includes a receive address RA field, wherein the address of the second access point indicated by the RA field is used to indicate the same basic service set network allocation vector Intra-BSS NAV of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

[0202] Based on the first implementation of the communication device 1100 described above, in its second implementation, the processing module 1102 is specifically used to: determine, based on the parsing result, that the value of the receiving address RA field in the first frame is the same as the address of the associated access point, and set the first time to the same basic service set Intra-BSS NAV.

[0203] In a third implementation of the communication device 1100, based on the second implementation of the above-mentioned communication device 1100, the transceiver module 1101 is further configured to: receive a second frame sent by the second access point; the processing module 1102 is further configured to parse the second frame and determine that the field value of the duration field in the second frame is 0; and the processing module 1102 is further configured to maintain the current Intra-BSS NAV.

[0204] Based on the above-mentioned communication device 1100, in its fourth implementation, the processing module 1102 is specifically used to: determine, according to the parsing result, that the value of the received address RA field in the first frame is different from the address of the associated access point, and set the first time to Basic Network Allocation Vector (Basic NAV).

[0205] The communication device provided in this embodiment can ensure the NAV coverage of the cooperative access point transmission cycle, so that there is no interference (such as the hidden node of the second node occupying the channel) during the process of the cooperative access point returning control of the TXOP time resource to the shared access point. This ensures that the control of the TXOP time resource is successfully returned to the shared access point, which is beneficial to improving transmission efficiency.

[0206] It should be understood that the communication device 1100 described in the embodiments of this application may correspond to the station in the method embodiments of this application, and the various units in the device 1100 and the other operations and / or functions described above are respectively for implementing Figure 5 or Figure 7 The corresponding processes applied to the site equipment in the embodiments described herein will not be repeated here for the sake of brevity.

[0207] This application provides an access point device, characterized in that it includes: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to implement the method applied to the access point device in this application embodiment.

[0208] This application provides a site device, characterized in that it includes: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to implement the method applied to the site device in this application embodiment.

[0209] Figure 12 This is a schematic structural diagram of a communication device 1200 provided in an embodiment of this application. Figure 12 The communication device 1200 shown includes a processor 1210, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0210] Optionally, such as Figure 12 As shown, the communication device 1200 may further include a memory 1220. The processor 1210 can call and run computer programs from the memory 1220 to implement the methods in the embodiments of this application. For example, when the communication device 1200 is an access point device, the processor 1210 can call and run computer programs from the memory 1220 to implement the various steps of the method embodiments executed by the access point device, achieving the same technical effect. When the communication device 1200 is a terminal device, the processor 1210 can call and run computer programs from the memory 1220 to implement the various steps of the method embodiments executed by the site device, achieving the same technical effect.

[0211] Alternatively, the memory 1220 may be a separate device independent of the processor 1210, or it may be integrated into the processor 1210.

[0212] Optionally, such as Figure 12 As shown, the communication device 1200 may also include a transceiver 1230. The processor 1210 can control the transceiver 1230 to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0213] Optionally, transceiver 1230 may include a transmitter and a receiver. Transceiver 1230 may further include antennas, and the number of antennas may be one or more.

[0214] Figure 13 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 13 The chip 1300 shown includes a processor 1310, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0215] Optionally, such as Figure 13 As shown, chip 1300 may further include memory 1320. Processor 1310 can retrieve and run computer programs from memory 1320 to implement the methods described in this embodiment.

[0216] Alternatively, the memory 1320 may be a separate device independent of the processor 1310, or it may be integrated into the processor 1310.

[0217] Optionally, the chip 1300 may also include an input interface 1330. The processor 1310 can control the input interface 1330 to communicate with other devices or chips, for example, to acquire information or data sent by other devices or chips.

[0218] Optionally, the chip 1300 may also include an output interface 1340. The processor 1310 can control the output interface 1340 to communicate with other devices or chips, for example, to output information or data to other devices or chips.

[0219] Optionally, the chip can be applied to the access point device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the access point device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0220] Optionally, the chip can be applied to the site device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the site device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0221] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0222] Figure 14 This is a schematic block diagram of a communication system 1400 provided in an embodiment of this application. Figure 14 As shown, the communication system 1400 includes an access point device 1410 and a site device 1420.

[0223] The access point device 1410 can be used to implement the corresponding functions implemented by the access point device in the above method, and the site device 1420 can be used to implement the corresponding functions implemented by the site device in the above method. For the sake of brevity, they will not be described in detail here.

[0224] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0225] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0226] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0227] This application also provides a readable storage medium storing a computer program that, when executed by a processor, implements the various processes of the above-described method embodiments.

[0228] Optionally, the readable storage medium can be applied to the access point device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0229] Optionally, the readable storage medium can be applied to the site device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0230] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the various processes of the above-described method embodiments.

[0231] Optionally, the computer program product can be applied to the access point device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0232] Optionally, the computer program product can be applied to the site device in the embodiments of this application, and the computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0233] This application also provides a computer program. When executed by a processor, this computer program implements the various processes of the above-described method embodiments.

[0234] Optionally, the computer program can be applied to the access point device in the embodiments of this application. The computer program causes the processor to execute the corresponding process implemented by the access point device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0235] Optionally, the computer program can be applied to the site device in the embodiments of this application. The computer program causes the processor to execute the corresponding process implemented by the third site device in the method embodiments of this application. To avoid repetition, it will not be described again here.

[0236] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0237] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0238] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0239] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0240] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0241] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0242] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first access point generates a first frame, which includes a duration field. The first frame is used to indicate that the second access point begins to use the Transmission Opportunity (TXOP) time resource. The duration field indicates a first time used to indicate the Network Allocation Vector (NAV) of at least one site, and the NAV covers the transmission period of the second access point. The first access point sends the first frame to the second access point and the at least one site.

2. The method according to claim 1, characterized in that, The first time is greater than or equal to the allocation time of the second access point.

3. The method according to claim 1 or 2, characterized in that, The method further includes: During the NAV protection period of the site, the first access point receives the third frame sent by the second access point and regains control of the TXOP time resource. The third frame is used by the second access point to return unused time from the TXOP time resource.

4. The method according to any one of claims 1-3, characterized in that, The first frame includes a Receive Address (RA) field, wherein the RA field indicates the address of the second access point, which is used to indicate the Intra-BSS NAV of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

5. A communication method, characterized in that, include: The second access point receives a first frame sent by the first access point. The first frame includes a duration field, wherein the first frame is used to indicate that the second access point begins to use the transmission opportunity (TXOP) time resource, and the first time indicated by the duration field is used to indicate the network allocation vector (NAV) of at least one site, and the NAV covers the transmission period of the second access point. In response to the first frame, the second access point sends a second frame to the first access point and the at least one site.

6. The method according to claim 5, characterized in that, The duration field value in the second frame is 0.

7. A communication method, characterized in that, include: A station receives a first frame sent by a first access point. The first frame includes a duration field, wherein the first frame is used to indicate that a second access point begins to use the transmission opportunity (TXOP) time resource, and the first time indicated by the duration field is used to indicate the network allocation vector (NAV) of at least one station. The site parses the first frame; Based on the parsing results, the site sets the first time as NAV, and the NAV covers the transmission period of the second access point.

8. The method according to claim 7, characterized in that, The first frame includes a receive address (RA) field, wherein the address of the second access point indicated by the RA field is used to indicate the same basic service set network allocation vector (Intra-BSS NAV) of the site associated with the second access point, and the Intra-BSS NAV covers the transmission period of the second access point.

9. The method according to claim 8, characterized in that, The site sets the first time as NAV based on the parsing results, including: Based on the parsing results, it is determined that the value of the RA field in the first frame is the same as the address of the associated access point, and the first time is set to the same basic service set Intra-BSS NAV.

10. The method according to claim 9, characterized in that, The method further includes: The station receives the second frame sent by the second access point; The site parses the second frame and determines that the value of the duration field in the second frame is 0; The site maintains its current Intra-BSS NAV.

11. The method according to claim 8, characterized in that, The site sets the first time as NAV based on the parsing results, including: Based on the parsing results, it is determined that the value of the RA field in the first frame is different from the address of the associated access point, and the first time is set as the Basic Network Allocation Vector (Basic NAV).

12. A communication device, characterized in that, Configured at the first access point, the device includes: A processing module is used to generate a first frame, the first frame including a duration field, wherein the first frame is used to indicate that the second access point begins to use the transmission opportunity TXOP time resource, the first time indicated by the duration field is used to indicate the network allocation vector NAV of at least one site, and the NAV covers the transmission period of the second access point. A transceiver module is used to send the first frame to the second access point and the at least one site.

13. An access point device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1-4, or to perform the method as described in claim 5 or 6.

14. A site device, characterized in that, include: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 7-11.

15. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as described in any one of claims 1-4, or the method as described in claim 5 or 6, or the method as described in any one of claims 7-11.

16. A readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1-4, or to perform the method as described in claim 5 or 6, or to perform the method as described in any one of claims 7-11.

17. A communication system, characterized in that, It includes an access point device and a site device, the access point device being configured to perform the method as described in any one of claims 1-4, or to perform the method as described in claim 5 or 6, and the site device being configured to perform the method as described in any one of claims 7-11.

Images