Multi-access point transmission opportunity sharing processing method, storage medium, electronic apparatus, and computer program product

Abstract

Provided in the embodiments of the present application are a multi-access point transmission opportunity sharing processing method, a storage medium, an electronic apparatus, and a computer program product. The method comprises: after acquiring a transmission opportunity (TXOP), a primary access point performing PPDU transmission within a first BSS on the basis of the TXOP, wherein the duration of the PPDU is set to be less than a preset time; and when there is remaining TXOP, handing over the remaining TXOP to a secondary access point by means of a control frame.

Description

Multi-access point transmission opportunity sharing processing methods, storage media, electronic devices and computer program products

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411496790.7, filed on October 23, 2024, entitled “Multi-access point transmission opportunity sharing processing method, storage medium, electronic device and computer program product”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and more specifically, to a multi-access point transmission opportunity sharing processing method, storage medium, electronic device, and computer program product. Background Technology

[0004] Data needs to be transmitted wirelessly between network devices (such as access points, APs) and terminal devices (such as sites). During multi-access point collaboration, basic-NAV (Network Allocation Vector) protection prevents PPDU transmission.

[0005] No solution has yet been proposed to address the issue of PPDU transmission failure caused by basic-NAV protection during multi-access point collaboration in related technologies. Summary of the Invention

[0006] This application provides a multi-access point transmission opportunity sharing processing method, storage medium, electronic device, and computer program product to at least solve the problem in the related art where basic-NAV protection prevents PPDU transmission during multi-access point cooperation.

[0007] According to one embodiment of this application, a multi-access point transmission opportunity sharing processing method is provided, applied to a primary access point. The method includes: after acquiring a transmission opportunity (TXOP), transmitting a Physical Layer Protocol Data Unit (PPDU) within a First Basic Service Set (BSS) based on the TXOP, wherein the duration of the PPDU is set to be less than a preset time; and, if there are remaining TXOPs, transferring the remaining TXOPs between a control frame and a secondary access point.

[0008] According to another embodiment of this application, a multi-access point transmission opportunity processing method is provided, applied to a secondary access point. The method includes: after the primary access point transmits a Physical Layer Protocol Data Unit (PPDU) within a First Basic Service Set (BSS) based on an acquired transmission opportunity (TXOP), the remaining TXOPs are handed over between the primary access point and the secondary access point via a control frame, wherein the duration of the PPDU is less than a preset time.

[0009] According to yet another embodiment of this application, a computer program product is also provided, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0010] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.

[0011] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments. Attached Figure Description

[0012] Figure 1 is a schematic diagram of the multi-access point collaboration process in related technologies;

[0013] Figure 2 is a block diagram of the components of a wireless communication device in the related technology;

[0014] Figure 3 is a flowchart of a multi-access point transmission opportunity sharing processing method according to an embodiment of this application;

[0015] Figure 4 is a flowchart of a multi-access point transmission opportunity processing method according to an embodiment of this application;

[0016] Figure 5 is a schematic diagram of multi-access point cooperative transmission according to an embodiment of this application;

[0017] Figure 6 is a flowchart of the handover and reclamation of a multi-access point shared transmission opportunity according to an embodiment of this application;

[0018] Figure 7 is a schematic diagram of the handover and recycling of multiple access point transmission opportunities according to an embodiment of this application;

[0019] Figure 8 is a schematic diagram of the frame structure in the MAP negotiation phase of the transmission opportunity handover and reclamation method according to an embodiment of this application;

[0020] Figure 9 is a schematic diagram of the RTS and MU-RTS frame structures defined in the standard protocol according to an embodiment of this application;

[0021] Figure 10 is a schematic diagram of the handover and recycling of multiple access point transmission opportunities according to an embodiment of this application;

[0022] Figure 11 is a schematic diagram of the MAP-RTS TXS frame field in a multi-access point transport opportunity sharing according to an embodiment of this application;

[0023] Figure 12 is a block diagram of a multi-access point transmission opportunity sharing processing apparatus according to an embodiment of this application. Detailed Implementation

[0024] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0025] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0026] Figure 1 is a schematic diagram of the multi-access point (MAB) cooperation process in related technologies. As shown in Figure 1, basic-NAV (Network Allocation Vector) protection exists during MAB cooperation. In this scenario, the wireless network consists of AP1 (sharing access point) and associated STA1 (Station), AP2 (shared AP) and associated STA2. Frames sent by AP1 or STA1 during transmission are identified by STA2 as inter-BSS (Basic Service Set) frames. STA2 sets basic-NAV based on the duration field value in the inter-BSS frame until the current transmission opportunity (TXOP) ends. Due to the existence of basic-NAV, AP2 cannot trigger legacy STA2 to transmit uplink PPDU (Physical Layer Protocol Data Unit).

[0027] Figure 2 is a block diagram of a wireless communication device in the related art. As shown in Figure 2, this structure is applicable to various technologies or methods for implementing the embodiments of this application. In some embodiments, device 200 can operate independently or establish a connection with other devices to form a network system. When device 200 is deployed in a network, it can operate as a server or client in a server-client mode, or as a node in a P2P network mode. Device 200 may represent AP102, STA104, STA108, or any other device capable of executing relevant instructions, including methods for implementing or supporting the features described herein.

[0028] Device 200 may include processor 204 (e.g., central processing unit (CPU), graphics processing unit (GPU) or any combination thereof), memory 202, display device 212, input device 214, sensor device 216 and antenna 218.

[0029] Memory 202 stores the control program and various data used. AP102 and STA104, STA108 can be configured to implement or support the implementation of part or all of the methods described herein, for example, by executing program instructions stored in the memory. The memory can be implemented as RAM, flash memory, ROM, EPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this respect, the memory can be coupled to the processor, allowing the processor to read information from and write information to the memory. In some embodiments, the memory may each include a cache for storing temporary variables or other intermediate information during the execution of instructions executed by the processor. The memory may also include non-volatile memory for storing instructions to be executed by the processor. Upon device power-up, one or more programs stored on a hard disk or read-only memory are transferred to random access memory and registers for storing variables and parameters required by the present invention.

[0030] Device 200 may also include display device 212 and input device 214 (e.g., keyboard and mouse). In some embodiments, display device 212 and input device 214 may be touch screen displays. Sensor 216 may be, for example, a Global Positioning System (GPS) sensor or other sensors.

[0031] Processor 204 is responsible for executing various instruction sets or software programs and managing data transmission and reception tasks. Processor 204 may include a Media Access Control Unit 206 (MAC unit), a Physical Layer Unit 208 (PHY unit), and a storage unit 210. These units, including PHY unit 208, MAC unit 206, and storage unit 210, can be interconnected and may be partially or entirely integrated on a single chip. Processor 204 can implement or assist in implementing one or more of the functions, operations, or methods described herein by running program code stored in storage units 202 or 210. Furthermore, processor 204 can be configured to use one or more antennas to transmit and receive signals with other wireless devices (e.g., AP 102, STA 104, or legacy device 108). In a particular embodiment, PHY unit 208 is responsible for performing functions such as signal encoding and decoding, power amplification, and filtering, including generating baseband signals for transmission and decoding received signals. PHY unit 208 can also transmit signals according to one of the 802.11 standards discussed herein, such as 802.11ax / 802.11be. MAC unit 206 is responsible for managing access rights to the wireless communication medium. In some embodiments, MAC unit 206 can compete for access to the wireless medium based on Network Allocation Vector (NAV) and Channel Clearance Assessment (CCA). Certain functions of signal transmission and reception may be performed collaboratively by PHY unit 208, MAC unit 206, and other components. In some embodiments, processor 204 may integrate one or more general-purpose or purpose-specific processors. Processor 204 may also be configured as a Field Programmable Gate Array (FPGA) or implemented using dedicated hardware components such as Application-Specific Integrated Circuits (ASICs) to implement the required hardware and logic circuitry. In some cases, the implementation of processor 204 may rely on the combination of software-configured elements with other hardware elements.

[0032] Antenna 218 may include one or more directional or omnidirectional antennas, including, for example, linearly polarized antennas, circularly polarized antennas, narrowband antennas, wideband antennas, ultra-wideband antennas, or other types of antennas suitable for transmitting RF signals. In some embodiments, antenna 218 may be configured to perform wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some embodiments, multi-user MIMO technology may be used for wireless communication.

[0033] In several embodiments, the methods described herein may be implemented entirely in software, or in part through a combination of software and firmware. These software components and / or firmware may be encoded on a persistent computer-readable storage medium for the processor to read. The processor parses and executes these encoded instructions to perform the series of operations described herein. These instructions may exist in various forms, including but not limited to raw source code, compiled code, scripts requiring interpretation, directly executable programs, statically compiled programs, or dynamically generated programs.

[0034] This embodiment provides a multi-access point transmission opportunity sharing processing method operating on the above-mentioned wireless communication device. Figure 3 is a flowchart of the multi-access point transmission opportunity sharing processing method according to an embodiment of this application, applied to the main access point. As shown in Figure 3, the process includes the following steps.

[0035] Step S302: After obtaining the transmission opportunity TXOP, the physical layer protocol data unit (PPDU) within the first basic service set (BSS) is transmitted based on the TXOP, wherein the duration of the PPDU is set to be less than a preset time.

[0036] Step S304: If there are remaining TXOPs, the remaining TXOPs are handed over between the control frame and the secondary access point.

[0037] Through the above steps S302 to S304, the problem that basic-NAV protection prevents PPDU transmission during multi-access point collaboration in related technologies can be solved. After the primary access point obtains TXOP, it performs PPDU transmission within the BSS. The duration of the PPDU is set to be sufficiently short (i.e., less than the preset time), thereby avoiding setting basic-NAV protection for the associated STA of the secondary access point and allowing the STA to perform PPDU transmission.

[0038] In this embodiment, step S204 may include: transferring the remaining first TXOP to the secondary access point via a first control frame. The first control frame carries the MAC addresses (Medium Access Control) of the primary and secondary access points. The MAC address of the secondary access point is used to instruct its associated sites not to update the basic network allocation vector (basic-NAV). This mechanism ensures that the associated sites of the secondary access point can continue to monitor the network, avoiding unnecessary NAV updates and thus improving transmission efficiency. It is particularly suitable for real-time application environments requiring rapid response.

[0039] In one embodiment, the first control frame includes at least a TA field, an RA field, and a duration field. The TA field is set to the MAC address of the primary access point, the RA field is set to the MAC address of the secondary access point, and the duration field is set to the available time allocated to the secondary access point. This detailed information transmission ensures that the secondary access point accurately understands the transferred TXOP resources, thereby enabling efficient data transmission. It is suitable for scenarios requiring precise resource management, such as video conferencing and online education.

[0040] In one embodiment, after handing over the remaining first TXOP to the secondary access point via a first control frame, the method further includes: receiving a response from the secondary access point via a second control frame, wherein the second control frame is sent by the secondary access point after determining that the first control frame is a TXOP handover frame, and the second control frame carries the MAC address of the secondary access point; and determining that the first TXOP handover was successful based on the second control frame. This response mechanism ensures the confirmation of TXOP handover, avoids resource allocation problems caused by transmission errors, enhances system stability, and is suitable for scenarios with complex network environments and high transmission quality requirements.

[0041] In one embodiment, the second control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to the Duration of the first control frame minus the Short Interframe Spacing (SIFS) and then minus the duration of the second control frame. This method of calculating the duration ensures accurate allocation of network resources and avoids wasted time, making it particularly suitable for time-sensitive applications such as industrial automation and telemedicine.

[0042] In one embodiment, the method further includes: receiving the remaining second TXOP of the first TXOP returned by the secondary access point via a third control frame, wherein the second TXOP is returned by the secondary access point after performing PPDU transmission within the second BSS based on the first TXOP. This mechanism for returning remaining TXOPs can further improve resource utilization, ensure dynamic allocation of network resources, and is suitable for scenarios with frequent changes in network load, such as large shopping malls and stadiums.

[0043] In one embodiment, the aforementioned third control frame includes at least: a TA field, an RA field, and a Duration field, wherein the TA field is set to the MAC address of the secondary access point, the RA field is set to the broadcast address, and the Duration field is set to 0. This design ensures that all listening stations can receive the TXOP returned information, avoiding resource allocation conflicts, enhancing system robustness, and is suitable for scenarios with multiple users and multiple devices online simultaneously, such as office environments and home networks.

[0044] In one embodiment, after determining that the first TXOP handover was successful based on the second control frame, the method further includes: sending a fourth control frame to the secondary access point, wherein the fourth control frame is used to instruct the hidden access point of the secondary access point not to reset the NAV. This mechanism ensures that the hidden access point can continue to monitor the network, avoiding resource waste caused by frequent NAV resets, and is particularly suitable for network environments with hidden nodes, such as dense urban areas and multi-story buildings.

[0045] In one embodiment, the aforementioned fourth control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to 0. This design ensures that the hidden access point accurately receives the instruction not to reset the NAV, avoiding data transmission delays caused by NAV reset, enhancing the real-time performance of the system, and is suitable for scenarios requiring low-latency transmission, such as online games and virtual reality.

[0046] In one embodiment, before handing over the remaining TXOPs between the control frame and the secondary access point, the method further includes: instructing the secondary access point to recognize the first control frame as a TXOP handover frame during transmission via a trigger frame. This pre-instruction mechanism ensures that the secondary access point accurately identifies the TXOP handover frame, avoiding resource allocation problems caused by frame identification errors, enhancing system collaboration, and is suitable for scenarios requiring multi-access point collaboration, such as intelligent transportation systems and large-scale IoT deployments.

[0047] In one embodiment, the reserved field of the trigger type in the trigger frame represents the MAP coordination trigger type, which is used to indicate the handover of the first TXOP via the first control frame. The use of this reserved field ensures correct parsing of the trigger frame, avoids system failures due to frame type identification errors, and enhances system reliability and stability. It is suitable for scenarios with complex network architectures and diverse equipment types, such as smart cities and smart factories.

[0048] This application embodiment also provides a multi-access point transmission opportunity processing method. Figure 4 is a flowchart of the multi-access point transmission opportunity processing method according to the embodiment of this application. As shown in Figure 4, the method is applied to the secondary access point. The method includes: step S402, after the primary access point performs PPDU transmission in the first BSS based on the acquired transmission opportunity TXOP, the remaining TXOP is handed over between the primary access point and the control frame, wherein the duration of the PPDU is less than a preset time.

[0049] This method can effectively improve the data transmission efficiency of secondary access points, especially in high-density network environments, significantly improving network resource utilization and enhancing user experience. It is suitable for scenarios requiring multiple access points to work together, such as large public places and corporate parks.

[0050] In this embodiment, the handover of the remaining TXOPs between the control frame and the primary access point can include: receiving the remaining first TXOPs handed over by the primary access point via a first control frame, wherein the first control frame carries the MAC addresses of the primary access point and the secondary access point, and the MAC address of the secondary access point is used to instruct the associated site of the secondary access point not to update the basic-network allocation vector (basic-NAV); and identifying the first control frame as a TXOP handover frame. This mechanism ensures that the secondary access point can immediately start data transmission, avoiding unnecessary waiting time, and is particularly suitable for real-time application environments that require rapid response, such as online live streaming and remote teaching.

[0051] In one embodiment, the first control frame includes at least a TA field, an RA field, a Duration field, and an Allocation Start Time subfield. The TA field is set to the MAC address of the primary access point, the RA field is set to the MAC address of the secondary access point, the Duration field is set to the available time allocated to the secondary access point, and the Allocation Start Time subfield is set to indicate the start time at which the primary access point allocates data transmission to the secondary access point. This detailed information transmission ensures that the secondary access point accurately understands the transferred TXOP resources and transmission time, thereby enabling efficient data transmission. It is suitable for scenarios requiring precise resource management, such as video conferencing and online education.

[0052] In one embodiment, after identifying the first control frame as a TXOP handover frame, the method further includes: returning a response to the primary access point via a second control frame, wherein the second control frame carries the MAC address of the secondary access point and is used to instruct the primary access point to confirm that the first TXOP handover was successful. This response mechanism ensures the confirmation of TXOP handover, avoids resource allocation problems caused by transmission errors, enhances system stability, and is suitable for scenarios with complex network environments and high transmission quality requirements, such as financial transactions and data backup.

[0053] In one embodiment, the second control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to the Duration of the first control frame minus the Short Interframe Spacing (SIFS) and then minus the duration of the second control frame. This method of calculating the duration ensures accurate allocation of network resources and avoids wasted time, making it particularly suitable for time-sensitive applications such as industrial automation and telemedicine.

[0054] In one embodiment, the method further includes: transmitting PPDUs within a second BSS based on a first TXOP; and, if there are remaining TXOPs, returning the remaining second TXOPs to the primary access point via a third control frame. This mechanism for returning remaining TXOPs can further improve resource utilization, ensure dynamic allocation of network resources, and is suitable for scenarios with frequent changes in network load, such as large shopping malls and stadiums. It can flexibly adjust resource allocation according to real-time network load conditions, thereby improving network efficiency.

[0055] In one embodiment, the third control frame includes at least: a TA field, an RA field, and a Duration field, wherein the TA field is set to the MAC address of the secondary access point, the RA field is set to the broadcast address, and the Duration field is set to 0. This design ensures that all listening stations can receive the TXOP returned information, avoiding resource allocation conflicts, enhancing system robustness, and is suitable for scenarios with multiple users and multiple devices online simultaneously, such as office environments and home networks. It can ensure fair allocation of network resources and improve user satisfaction.

[0056] In one embodiment, before handing over the remaining TXOPs to the primary access point via a control frame, the method further includes: determining via a trigger frame or negotiation frame that the primary access point will hand over the remaining TXOPs via a first control frame during transmission. This pre-determination mechanism ensures that the secondary access point is accurately prepared to receive TXOPs, avoiding data transmission delays due to insufficient preparation, enhancing the real-time performance and responsiveness of the system. It is suitable for scenarios requiring low-latency transmission, such as online games and virtual reality, and can provide a smooth, latency-free user experience.

[0057] In one embodiment, the reserved field of the trigger type in the trigger frame represents the MAP coordination trigger type, which is used to indicate the handover of the first TXOP via the first control frame. The use of this reserved field ensures correct parsing of the trigger frame, avoids system failures due to frame type identification errors, and enhances system reliability and stability. It is suitable for scenarios with complex network architectures and diverse device types, such as smart cities and smart factories, ensuring accurate and efficient data transmission between different types of devices and systems.

[0058] The multi-access point transmission opportunity sharing processing provided in this application improves the utilization rate of transmission opportunities in a wireless network by sharing and handing over TXOPs between the primary and secondary access points. This effectively avoids resource waste and enhances the flexibility and efficiency of multi-access point collaboration, making it particularly suitable for high-density wireless network environments. It significantly improves network throughput and user experience. This innovative TXOP sharing and handover mechanism not only significantly improves network resource utilization but also flexibly adjusts resource allocation according to real-time changes in the network environment, effectively avoiding resource idleness and waste. In high-density wireless network environments, this method can significantly improve network throughput, reduce data transmission latency, and enhance user experience. Simultaneously, the clever design of control frames ensures the smooth progress of the TXOP handover process, avoiding unnecessary waiting for other stations in the network and further improving overall network performance. Furthermore, the pre-setting of trigger frames or negotiation frames enhances inter-system cooperation, ensuring the accuracy and timeliness of TXOP handover, which has significant practical application value for building an efficient and stable wireless network environment. In practical applications, this method can be widely used in various high-density network environments, such as large public places, corporate parks, and intelligent transportation systems, providing users with more stable, efficient, and low-latency network services. It also provides network operators with more flexible and intelligent network resource management solutions, and has broad market prospects and application potential.

[0059] Figure 5 is a schematic diagram of multi-access point cooperative transmission according to an embodiment of this application. As shown in Figure 5, multiple access points can be divided into two main categories: sharing APs and shared APs, or master APs, slave APs, etc. A sharing AP or master AP refers to the AP responsible for coordinating other APs in multi-AP cooperative transmission. It plays the role of coordinator, responsible for coordinating the transmission of other APs and ensuring their cooperation and interoperability. A shared AP or slave AP refers to the AP whose shared resource allocation and resource status are managed and notified by the sharing AP in multi-AP cooperative transmission. These APs receive notifications from the sharing AP and perform transmission operations on shared resources. The sharing AP coordinates shared resources to avoid collisions and improve transmission efficiency. When transmitting data, the shared AP may perform operations such as time slot allocation, power control, and transmission time adjustment according to the coordination of the sharing AP to ensure smooth cooperative transmission.

[0060] There are generally two methods for assigning the roles of sharing APs and shared APs. The first method determines these roles based on the initial negotiation of the cooperative transmission set or on factors such as network topology, AP processing capacity, AP location, and coverage. The second method assigns the role of the sharing AP to the first AP to complete the backoff process and attempt to access the channel in a Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) mechanism. In the first method, the roles of sharing APs and shared APs are usually permanent or semi-permanent (relative to the network lifetime). In the second method, the roles of sharing APs and shared APs change dynamically.

[0061] In Figure 5, the sharing AP accesses the channel and sends a trigger frame via the CSMA / CA mechanism. The trigger frame typically carries coordination information for shared AP2 and shared AP3. After a short interframe space (SIFS), the sharing AP, shared AP2, and shared AP3 simultaneously access the channel for cooperative transmission. Cooperative transmission modes can include Cooperative Beamforming (Co-BF), Cooperative Spatial Reuse (Co-SR), and Cooperative Orthogonal Frequency Division Multiple Access (Co-OFDMA).

[0062] This invention proposes a method for sharing transmission opportunities among multiple access points. This method can complete the handover and reclamation process of shared TXOPs among multiple access points. At the same time, this method can also handle the basic-NAV protection problem and the TXOP return failure caused by hidden nodes.

[0063] Figure 6 is a flowchart of the handover and reclamation of a multi-access point shared transmission opportunity according to an embodiment of this application. As shown in Figure 6, it includes the following steps.

[0064] Step S601: After the sharing AP obtains the TXOP, it performs data transmission within its own BSS.

[0065] In step S602, if there are remaining TXOPs, the sharing AP transfers the TXOPs to the shared AP via a control frame.

[0066] In step S603, the shared AP responds via a control frame, and then data transmission within the BSS begins.

[0067] In step S604, if there are remaining TXOPs, the shared AP returns the TXOPs via a control frame.

[0068] Figure 7 is a schematic diagram of the handover and recycling of multiple access point transmission opportunities according to an embodiment of this application. As shown in Figure 7, BSS1 in the wireless network consists of AP1 (sharing AP) and associated STA1, BSS2 consists of AP2 (shared AP) and associated STA2, and STA3 is associated with other BSS and is a hidden node of AP2.

[0069] First, a frame exchange process is carried out within BSS1. The sharing AP can send a DL PPDU to STA1 or trigger STA1 to send a UL Data PPDU via a trigger frame. During the frame exchange process, all PPDUs are set to a shorter duration, that is, the duration is set to not exceed the time of the RTS (request to send) frame transmission.

[0070] After the BSS1 intraframe exchange is completed, the TXOP handover process begins. The sharing AP sends an RTS frame to hand over the TXOP. The TA field of the RTS frame is set to AP1's MAC address, the RA field to AP2's MAC address, and the Duration field to the available time allocated by the sharing AP to the shared AP. Upon receiving the RTS frame, the shared AP recognizes it as a TXOP handover frame (the recognition process and conditions are shown in Figure 8) and replies with a CTS (clear to send) frame as an acknowledgment. In this CTS frame, the RA field is set to AP2's MAC address, and the Duration field is set to the Duration value in the RTS frame minus the Shortest Interframe Space (SIFS) minus the CTS frame's own duration. After receiving the CTS frame, the sharing AP confirms the TXOP handover is complete and immediately sends a CTS frame to prevent STA3 from resetting its NAV. The RA field of the CTS frame sent by the sharing AP is set to AP2's MAC address, and the Duration field is set to 0.

[0071] After the TXOP handover is completed, the shared AP can proceed with the frame exchange process within BSS2. The shared AP can send DL PPDU to STA2 or trigger STA2 to send UL Data PPDU via a trigger frame. During the frame exchange process, the Duration setting of all PPDUs shall not exceed the available time shared by the TXOP.

[0072] After the BSS2 intra-frame exchange is completed, the remaining TXOP return process can begin. The shared AP sends a CF-End frame, where the TA field is set to AP2's MAC address, the RA field is set to the broadcast address, and the Duration field is set to 0. Upon receiving this frame, the sharing AP can re-access the channel and become the owner of the TXOP.

[0073] The state control process of each node in the transmission opportunity handover and recovery in the embodiments of this application includes: during the frame switching process in BSS1, all PPDUs are set to a shorter duration. The purpose is to protect its own transmission from interference by neighboring nodes during the frame switching process, and also to avoid basic-NAV protection problems for STAs in BSS2.

[0074] The sharing AP sends an RTS frame to the shared AP. The TA field of the RTS frame contains the MAC address of AP1. Therefore, STAs (STA1) within BSS1 will recognize it as an intra-BSS PPDU and set their own intra-NAV. Subsequently, STA1 will not actively compete for the channel and thus interfere with BSS2. The RA field of the RTS frame contains the MAC address of AP2. Therefore, STAs (STA2) within BSS2 will recognize it as an intra-BSS PPDU and set their own intra-NAV according to the Duration value of the RTS frame. Subsequent uplink transmissions within BSS2 can be triggered by AP2 via a trigger frame.

[0075] If the shared AP successfully receives the RTS frame and the sharing AP also successfully receives the corresponding CTS frame, it indicates that the TXOP handover is successful. STAs within BSS1 will recognize the CTS frame as an inter-BSS PPDU and set their own basic-NAV according to the Duration value. STAs within BSS2 will recognize the CTS frame as an intra-BSS PPDU and therefore will not update their own NAV. Otherwise, in other cases, the TXOP handover is considered to have failed, and the sharing AP can choose to continue its own BSS transmission or resend the RTS frame.

[0076] To prevent hidden nodes of the shared AP from interfering with the subsequent TXOP reclamation process, the sharing AP will send a CTS frame with the RA field set to AP2's MAC address and the Duration field set to 0.

[0077] If the shared AP has remaining TXOPs after transmission is complete, it will send a CF-End frame to return the remaining TXOPs. If the sharing AP successfully receives the CF-End frame, it means that the TXOPs have been successfully returned. STAs within BSS1 will recognize the CF-End frame as an inter-BSS PPDU and reset their own basic-NAV (external) to 0. STAs within BSS2 will recognize the CF-End frame as an intra-BSS PPDU and therefore reset their own internal intra-NAV to 0. If the sharing AP fails to receive the CF-End frame and the TXOPs return fails, the sharing AP will wait until the allocated sharing time expires before restarting transmission.

[0078] Figure 8 is a schematic diagram of the frame structure in the MAP negotiation phase of the transmission opportunity handover and recovery method according to an embodiment of this application. As shown in Figure 8, in the MAP negotiation phase, the sharing AP can indicate the MAP coordination trigger type by using the reserved field of Trigger Type in the trigger frame. This indicates that the sharing AP will subsequently hand over the TXOP via the RTS frame. During the subsequent transmission process, the shared AP will identify the RTS frame sent by the sharing AP (TA field is the MAC address of the sharing AP, and RA field is the MAC address of the shared AP) as the TXOP handover frame and perform the relevant steps according to the transmission opportunity sharing method proposed in this invention.

[0079] MAP coordination: Define the MAP coordination trigger type using a reserved value of the Trigger Type subfield in the Common Info field.

[0080] TXS by RTS: When this field is 1, it indicates that the sharing AP will subsequently hand over the TXOP via an RTS frame. This is represented by a reserved bit in the Common Info field.

[0081] Figure 9 is a schematic diagram of the RTS and MU-RTS frame structures defined in the standard protocol according to an embodiment of this application. As shown in Figure 9, the method of handing over TXOPs through RTS frames reduces the overhead of Common Info, User Info List, and Padding fields compared to MU-RTS frames. The Duration field in the RTS frame indicates the duration for which the sharing AP will share resources with the shared AP (the bandwidth is assumed to be the full bandwidth available to the shared AP by default). The RA field is filled with the MAC address of the shared AP, and the TA field is filled with the MAC address of the sharing AP.

[0082] Figure 10 is a schematic diagram of the handover and recycling of multiple access point transmission opportunities according to an embodiment of this application. As shown in Figure 10, BSS1 in the wireless network consists of AP1 (sharing AP) and associated STA1, and BSS2 consists of AP2 (shared AP) and associated STA2.

[0083] First, a frame exchange process is carried out within BSS1. The sharing AP can send a DL PPDU to STA1 or trigger STA1 to send a UL Data PPDU via a trigger frame. During the frame exchange process, all PPDUs are set to a short duration, that is, the duration is set to not exceed the transmission time of the MAP-RTS TXS frame (the frame structure is shown in Figure 11).

[0084] After the BSS1 intraframe exchange is completed, the TXOP handover process begins. The sharing AP sends a MAP-RTS TXS frame to hand over the TXOP. In this MAP-RTS TXS frame, the TA field is set to AP1's MAC address, the RA field to AP2's MAC address, the Duration field to the available duration allocated by the sharing AP to the shared AP, and the AP ID subfield to the unique ID of the shared AP negotiated between the APs. Upon receiving the MAP-RTS TXS frame, the shared AP parses the AP ID field to see if it matches its own ID. If a match is found, the shared AP recognizes the MAP-RTS TXS frame as a TXOP handover frame and replies with a CTS frame as an acknowledgment. In this CTS frame, the RA field is set to AP2's MAC address, and the Duration field is the Duration value from the MAP-RTS TXS frame minus the Shortest Interframe Spacing (SIFS) and the CTS frame's own duration. Upon receiving the CTS frame, the sharing AP confirms the TXOP handover is complete.

[0085] After the TXOP handover is completed, the shared AP can proceed with the frame exchange process within BSS2. The shared AP can send DL PPDU to STA2 or trigger STA2 to send UL Data PPDU via a trigger frame. During the frame exchange process, the Duration setting of all PPDUs shall not exceed the available time shared by the TXOP.

[0086] After the BSS2 intra-frame exchange is completed, the remaining TXOP return process can begin. The shared AP sends a CF-End frame, where the TA field is set to AP2's MAC address, the RA field is set to the broadcast address, and the Duration field is set to 0. Upon receiving this frame, the sharing AP can re-access the channel and become the owner of the TXOP to proceed with subsequent frame exchanges.

[0087] As shown in Figure 10, the state control process includes: during frame switching in BSS1, all PPDUs are set to a shorter duration. The purpose is to protect their own transmission from interference by neighboring nodes during frame switching, and also to avoid basic-NAV protection issues for STAs in BSS2.

[0088] The sharing AP sends a MAP-RTS TXS frame to the shared AP to hand over the TXOP. The TA field of the MAP-RTS TXS frame contains the MAC address of AP1, and the RA field contains the MAC address of AP2. Therefore, both STA1 and STA2 will recognize it as an intra-BSS PPDU and set their own intra-NAV. Subsequently, STA1 will not actively compete for the channel and interfere with BSS2, and STA2 can also send UL TB Data PPDUs during the shared TXOP period.

[0089] If the shared AP successfully receives the MAP-RTS TXS frame and the sharing AP also successfully receives the corresponding CTS frame, it indicates that the TXOP handover is successful. STAs within BSS1 will recognize the CTS frame as an inter-BSS PPDU and set their own basic-NAV according to the Duration value. STAs within BSS2 will recognize the CTS frame as an intra-BSS PPDU but will not update their own NAV. Otherwise, in other cases, the TXOP handover is considered to have failed, and the sharing AP can choose to continue its own BSS transmission or resend the MAP-RTS TXS frame.

[0090] After a successful TXOP handover, the shared AP can begin data transmission within BSS2. If the shared AP has remaining TXOPs after the transmission is complete, it will send a CF-End frame with the TA field set to the MAC address of AP2 to return the remaining TXOPs. If the sharing AP successfully receives the CF-End frame, it indicates that the TXOP return was successful. STA1 will recognize the CF-End frame as an inter-BSS PPDU and reset its basic-NAV to 0. STAs within BSS2 will recognize the CF-End frame as an intra-BSS PPDU and reset their intra-NAV to 0. Otherwise, the TXOP return fails, and the sharing AP will wait until the allocated sharing time expires before restarting the transmission.

[0091] Figure 11 is a schematic diagram of the MAP-RTS TXS frame field in a multi-access point transmission opportunity sharing according to an embodiment of this application. As shown in Figure 11, the Sharing AP uses this frame to hand over the shared TXOP, and the shared AP responds with a CTS frame as an acknowledgment.

[0092] MAP RTS TXS field: The MAP RTS TXS type is defined using a reserved value of the Trigger Type subfield in the Common Info field. The Sharing AP uses this frame to hand over the shared TXOP.

[0093] The User Info List field consists of multiple shared AP information (i.e., AP Info). The AP Info field includes the AP ID, Allocation Start Time, Allocation Duration, Allocation RU, and reserved fields.

[0094] AP ID field: refers to a special ID negotiated between APs. If a shared AP recognizes that the AP ID value matches its own, then the shared AP can use the shared TXOP.

[0095] The Allocation Start Time field indicates the start time that the sharing AP allocates to the shared AP for data transmission. After responding to the CTS frame, the shared AP must wait for the duration specified in this field before it can transmit data.

[0096] The Allocation Duration field indicates the duration for which a sharing AP allocates shared resources to a shared AP.

[0097] The Allocation RU field indicates the available RU size and index of the sharing AP allocated to the shared AP.

[0098] According to one embodiment of this application, a multi-access point transmission opportunity sharing processing apparatus is provided. FIG12 is a block diagram of the multi-access point transmission opportunity sharing processing apparatus according to an embodiment of this application. As shown in FIG12, it is applied to a primary access point. The apparatus includes: an acquisition module 122, used to acquire a transmission opportunity TXOP and then transmit a Physical Layer Protocol Data Unit (PPDU) within a First Basic Service Set (BSS) based on the TXOP, wherein the duration of the PPDU is set to be less than a preset time; and a first handover module 124, used to hand over the remaining TXOPs to a secondary access point through a control frame when there are remaining TXOPs.

[0099] According to another embodiment of this application, a multi-access point transmission opportunity processing apparatus is provided, applied to a secondary access point. The apparatus includes: a second handover module, configured to hand over the remaining TXOPs between the primary access point and the primary access point via a control frame after the primary access point transmits Physical Layer Protocol Data Units (PPDUs) within a First Basic Service Set (BSS) based on the acquired transmission opportunity (TXOP). The duration of the PPDU is less than a preset time.

[0100] This application also provides a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to implement the steps in any of the above method embodiments.

[0101] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0102] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0103] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0104] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0105] The examples in this embodiment can be referred to the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0106] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0107] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for processing shared transmission opportunities across multiple access points, applied to a primary access point, the method comprising: After acquiring a transmission opportunity (TXOP), a physical layer protocol data unit (PPDU) is transmitted within the first basic service set (BSS) based on the TXOP, wherein the duration of the PPDU is set to be less than a preset time. If there are remaining TXOPs, the remaining TXOPs are handed over between the control frame and the secondary access point.

2. The method according to claim 1, wherein, The handover of the remaining TXOPs between the control frame and the secondary access point includes: The remaining first TXOP of the TXOP is transferred to the secondary access point via a first control frame. The first control frame carries the MAC addresses of the primary access point and the secondary access point. The MAC address of the secondary access point is used to instruct the associated site of the secondary access point not to update the basic-network allocation vector (basic-NAV).

3. The method according to claim 2, wherein, The first control frame includes at least a TA field, an RA field, and a duration field, wherein the TA field is set to the MAC address of the primary access point, the RA field is set to the MAC address of the secondary access point, and the duration field is set to the available duration allocated to the secondary access point.

4. The method according to claim 3, wherein, After transferring the remaining first TXOP of the TXOP to the secondary access point via the first control frame, the method further includes: The response returned by the secondary access point is received through a second control frame, wherein the second control frame is sent by the secondary access point after determining that the first control frame is a TXOP handover frame, and the second control frame carries the MAC address of the secondary access point. The first TXOP handover was determined to be successful based on the second control frame.

5. The method according to claim 4, wherein, The second control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to the Duration of the first control frame minus the short inter-frame interval (SIFS) and then minus the duration of the second control frame.

6. The method according to claim 4, wherein, The method further includes: The second TXOP remaining after the first TXOP is returned by the secondary access point via the third control frame, wherein the second TXOP is returned by the secondary access point after performing PPDU transmission within the second BSS based on the first TXOP.

7. The method according to claim 6, wherein, The third control frame includes at least: a TA field, an RA field, and a Duration field, wherein the TA field is set to the MAC address of the secondary access point, the RA field is set to the broadcast address, and the Duration field is set to 0.

8. The method according to claim 4, wherein, After determining that the first TXOP handover was successful based on the second control frame, the method further includes: A fourth control frame is sent to the secondary access point, wherein the fourth control frame is used to instruct the hidden access point of the secondary access point not to reset the NAV.

9. The method according to claim 8, wherein, The fourth control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to 0.

10. The method according to any one of claims 2 to 9, wherein, Before handing over the remaining TXOPs between the control frame and the secondary access point, the method further includes: The trigger frame instructs the secondary access point to recognize the first control frame as a TXOP handover frame during transmission.

11. The method according to claim 10, wherein, The reserved field of the trigger type in the trigger frame represents the MAP coordination trigger type, wherein the MAP coordination trigger type is used to indicate the handover of the first TXOP through the first control frame.

12. A method for processing transmission opportunities across multiple access points, applied to a secondary access point, the method comprising: After the primary access point transmits Physical Layer Protocol Data Units (PPDUs) within the First Basic Service Set (BSS) based on the acquired Transmission Opportunity (TXOP), the remaining TXOPs are handed over between the primary access point and the control frame, wherein the duration of the PPDU is less than a preset time.

13. The method according to claim 12, wherein, The handover of the remaining TXOPs between the control frame and the primary access point includes: The first control frame receives the remaining first TXOP of the TXOP handed over by the primary access point, wherein the first control frame carries the MAC addresses of the primary access point and the secondary access point, and the MAC address of the secondary access point is used to indicate that the associated site of the secondary access point does not update the basic-network allocation vector (basic-NAV). The first control frame is identified as a TXOP handover frame.

14. The method according to claim 13, wherein, The first control frame includes at least a TA field, an RA field, a Duration field, and an Allocation Start Time subfield, wherein the TA field is set to the MAC address of the primary access point, the RA field is set to the MAC address of the secondary access point, the Duration field is set to the available duration allocated to the secondary access point, and the Allocation Start Time subfield is set to indicate the start time for the primary access point to allocate data transmission to the secondary access point.

15. The method according to claim 13, wherein, After identifying the first control frame as a TXOP handover frame, the method further includes: A response is returned to the primary access point via a second control frame, wherein the second control frame carries the MAC address of the secondary access point and is used to instruct the primary access point to confirm that the first TXOP handover was successful.

16. The method according to claim 15, wherein, The second control frame includes at least: an RA field and a Duration field, wherein the RA field is set to the MAC address of the secondary access point, and the Duration field is set to the Duration of the first control frame minus the short inter-frame interval (SIFS) and then minus the duration of the second control frame.

17. The method according to claim 13, wherein, The method further includes: PPDU transmission within the second BSS is performed based on the first TXOP; If there are remaining TXOPs in the first TXOP, the remaining second TXOPs are returned to the main access point via a third control frame.

18. The method according to claim 17, wherein, The third control frame includes at least: a TA field, an RA field, and a Duration field, wherein the TA field is set to the MAC address of the secondary access point, the RA field is set to the broadcast address, and the Duration field is set to 0.

19. The method according to any one of claims 13 to 18, wherein, Before handing over the remaining TXOPs to the primary access point via control frames, the method further includes: The primary access point is determined to hand over the remaining TXOPs during transmission via the first control frame by triggering or negotiating frames.

20. The method according to claim 19, wherein, The reserved field of the trigger type in the trigger frame represents the MAP coordination trigger type, wherein the MAP coordination trigger type is used to indicate the handover of the first TXOP through the first control frame.

21. A computer-readable storage medium storing a computer program, wherein, The computer program is configured to execute the method described in any one of claims 1 to 9 when it is run.

22. An electronic device comprising a memory and a processor, the memory storing a computer program, the processor being configured to run the computer program to perform the method of any one of claims 1 to 9.

23. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11, 12 to 20.

Images