Multi-ap sharing return method, apparatus, and access point device

Abstract

The application discloses a multi-AP shared return method, device and access point equipment, and belongs to the technical field of communication. The multi-AP shared return method comprises the following steps: receiving a first frame from a second AP; obtaining a transmission opportunity TXOP sharing duration of the second AP according to the first frame; updating a network allocation vector NAV of a first AP according to the TXOP sharing duration of the second AP; and performing TXOP return in the case that a first condition is met, wherein the first condition comprises that an end time of the NAV of the first AP is earlier than an end time of TXOP sharing time allocated to the second AP.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and in particular relates to a method, apparatus and access point device for multi-AP shared return. Background Technology

[0002] Multiple access points (APs) negotiate and share transmission opportunities (TXOPs) to time-sharingly utilize air interface resources, thereby reducing service latency and increasing transmission efficiency. The roles in multi-AP collaborative TXOP transmission include sharing APs and shared APs. The AP that initiates the sharing process is called the sharing AP, and the APs(s) coordinated to participate in the sharing are called shared APs(s). The sharing AP obtains a TXOP through air interface contention, and the shared APs(s) participating in the sharing use a segment of the TXOP(s) in a time-sharing manner. The duration of each TXOP segment can be announced through control frames. Related technologies use TXOP return frames to return TXOPs to the sharing AP before the allocated time is fully used; this explicit return method incurs additional air interface overhead. Summary of the Invention

[0003] This application provides a method, apparatus, and access point device for sharing multiple access points (APs).

[0004] Firstly, a multi-AP shared return method is provided, executed by the first AP, the method comprising:

[0005] Receive the first frame from the second AP;

[0006] The duration of the TXOP (Transmission Opportunity Shared) of the second AP is obtained based on the first frame;

[0007] Update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP;

[0008] If the first condition is met, execute TXOP and return;

[0009] The first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP;

[0010] The TXOP sharing time is indicated by the first AP sending a Transmission Opportunity Sharing MU-RTSTXS frame via a multi-user request.

[0011] Secondly, a multi-AP shared return device is provided, comprising:

[0012] The receiving module is used to receive the first frame from the second AP;

[0013] The processing module is used to obtain the transmission opportunity (TXOP) sharing duration of the second AP based on the first frame;

[0014] The processing module is also configured to update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP;

[0015] The processing module is also configured to execute TXOP return if the first condition is met;

[0016] The first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP;

[0017] The TXOP sharing time is indicated by the first AP sending a Transmission Opportunity Sharing MU-RTSTXS frame via a multi-user request.

[0018] Thirdly, a multi-AP shared return device is provided, the device being configured to perform the steps of the method described in the first aspect.

[0019] Fourthly, an access point device is provided, the access point device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0020] Fifthly, an access point device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a first frame from a second AP; the processor is configured to obtain the transmission opportunity sharing (TXOP) duration of the second AP based on the first frame; update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP; and perform a TXOP return if a first condition is met; wherein the first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP; wherein the TXOP sharing time is indicated by the first AP sending a transmission opportunity sharing (MU-RTS) TXS frame through a multi-user request.

[0021] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0022] A seventh aspect provides a communication system comprising: a first AP and a second AP, wherein the first AP is configured to perform the steps of the method described in the first aspect.

[0023] Eighthly, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method as described in the first aspect.

[0024] In this embodiment, the first AP updates its NAV based on the TXOP sharing duration of the second AP, and uses this NAV information to perform a TXOP return if the first condition is met. This adopts an implicit TXOP return method, which does not require the APs participating in TXOP sharing to send TXOP return frames, thus reducing air interface overhead. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of a network architecture of a communication system provided in an embodiment of this application;

[0026] Figure 2 This is a schematic diagram of a transmission opportunity sharing operation provided in an embodiment of this application;

[0027] Figure 3 This is a schematic diagram of a multi-AP collaboration process provided in an embodiment of this application;

[0028] Figure 4 This is a flowchart illustrating a multi-AP shared return method provided in an embodiment of this application;

[0029] Figure 5 This is a schematic diagram of a TXOP return in a multi-AP sharing scenario provided in an embodiment of this application;

[0030] Figure 6 This is a schematic diagram of the structure of a multi-AP shared return device provided in an embodiment of this application;

[0031] Figure 7 This is a schematic diagram of the structure of an access point device provided in an embodiment of this application. Detailed Implementation

[0032] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0033] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0034] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc.; an indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0035] The technical solutions provided in this application can be applied to wireless local area network (WLAN) systems, and are applicable to any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols used in WLANs, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, and future 802.11 protocols. The methods provided in this application can be implemented by communication devices in a wireless communication system or by chips or processors within those devices. Accordingly, the communication device supports communication using the IEEE 802.11 series protocols. Although the embodiments of this application are mainly illustrated using a network deploying IEEE 802.11 as an example, those skilled in the art will readily understand that the various aspects involved in this application can be extended to other networks employing various standards or protocols, such as Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to IEEE 802.11, mainly used in Europe), wide area network (WAN), WLAN, personal area network (PAN), wireless personal area network systems based on ultra-wideband (UWB), sensing systems, or other networks now known or to be developed in the future. The methods provided in the embodiments of this application can be applied to the IEEE 802.15 series protocols, such as the 802.15.4a protocol, the 802.15.4z protocol, or the 802.15.4ab protocol, or a future generation of UWB WPAN protocol, etc., which will not be listed one by one.The technical solutions provided in this application can also be applied to the following communication systems, such as Internet of Things (IoT) systems, Vehicle-to-X (V2X) systems, narrowband Internet of Things (NB-IoT) systems, devices used in V2X systems, IoT nodes and sensors in IoT systems, smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities. Alternatively, they can also be applied to Long Term Evolution (LTE) systems, 5th-generation (5G) communication systems, and new communication systems that will emerge in future communication developments. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

[0036] In the WiFi protocol, a station (abbreviated as STA) includes access point stations (abbreviated as AP STA) and non-access point stations (abbreviated as non-AP station). For the sake of simplicity, access point stations are usually called access points (abbreviated as AP), and non-access point stations are called stations (abbreviated as STA).

[0037] For example, please refer to Figure 1 This diagram illustrates a network architecture of a communication system according to an embodiment of this application. The communication system 100 may include an access point AP110 and a station STA120 that accesses the network through the access point AP110.

[0038] The communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA. Here, a peer STA can refer to a device that communicates with a STA on an equal footing. For example, a peer STA may be an AP or a non-AP STA.

[0039] An access point (AP) 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. AP devices can be terminal devices with Wi-Fi chips (such as mobile phones) or network devices (such as wireless routers, wireless switches, or wireless repeaters).

[0040] It should be understood that the role of a STA in a communication system is not absolute. For example, in some scenarios, when a mobile phone connects to a router, it is a non-AP STA; when the mobile phone acts as a hotspot for other mobile phones, it plays the role of an AP.

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

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

[0043] WLAN systems can provide high-speed, low-latency transmission. As WLAN application scenarios continue to evolve, WLAN systems will be applied to more scenarios or industries, such as the Internet of Things industry, the Internet of Vehicles industry, the banking industry, enterprise offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital wards, classrooms, shopping malls, squares, streets, production workshops and warehouses, etc. Of course, devices that support WLAN communication or sensing (such as access points or sites) can be sensor nodes in smart cities (such as smart water meters, smart electricity meters, and smart air monitoring nodes), smart devices in smart homes (such as smart cameras, projectors, displays, televisions, speakers, refrigerators, and washing machines), nodes in the Internet of Things (IoT), entertainment terminals (such as wearable devices for augmented reality (AR) and virtual reality (VR), smart devices in smart offices (such as printers, projectors, loudspeakers, and speakers), vehicle-to-everything (V2X) devices, infrastructure in daily life scenarios (such as vending machines, self-service navigation kiosks in supermarkets, self-service checkout machines, and self-service ordering machines), and equipment in large sports and music venues.

[0044] In this embodiment, an access point is a device with wireless communication capabilities, supporting communication or sensing using the WLAN protocol. It has the function of communicating or sensing with other devices in the WLAN network (such as non-AP STAs or other access points), and can also have the function of communicating or sensing with other devices. Alternatively, an access point acts as a bridge connecting wired and wireless networks, primarily connecting various wireless network clients together and then connecting the wireless network to the Ethernet. This wireless communication device can be a complete device, or a chip, processing system, or functional module installed within a complete device. Devices with these chips, processing systems, or functional modules can implement the methods and functions of this embodiment under the control of the chips, processing systems, or functional modules. The AP in this embodiment is a device providing services to non-AP STAs and can support 802.11 series protocols or subsequent protocols. For example, an access point can be an access point for terminals (such as mobile phones) to enter a wired (or wireless) network, mainly deployed in homes, buildings, and parks, with a typical coverage radius of tens to hundreds of meters; it can also be deployed outdoors. For example, an AP can be a communication server, router, switch, bridge, or other communication entity; APs can include various forms of macro base stations, micro base stations, repeater stations, etc.

[0045] In the embodiments of this application, the site can be a mobile phone, tablet, 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 communication chip / application specific integrated circuit (ASIC) / system on chip (SOC), etc.

[0046] WLAN technology can support frequency bands including but not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 60GHz).

[0047] Figure 1 An exemplary embodiment shows one AP 110 and two non-AP STAs 120. Optionally, the communication system 100 may include multiple AP STAs and other numbers of non-AP STAs, which is not limited in this application embodiment.

[0048] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include an access point 110 and a station 120 with communication functions. The access point 110 and the station 120 may be the specific equipment described above, which will not be repeated here. The communication equipment may also include other equipment in the communication system 100, such as network controllers, gateways and other network entities. This application embodiment does not limit this.

[0049] It should be understood that the terms “system” and “network” used in this application are often used interchangeably herein.

[0050] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0051] In this application embodiment, "predefined" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including access points and sites). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0052] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the WiFi protocol and related protocols applied to future WiFi communication systems, and this application does not limit it.

[0053] Access point 110 and site 120 can associate and communicate via wireless LAN technology. Association refers to the process of negotiating wireless link services between the STA and AP to establish a wireless link between them.

[0054] In wireless LANs, dense deployment of access points can cause mutual interference, leading to deterioration in latency and throughput. Coordinating the shared use of air interface resources among multiple access points is a typical optimization approach. Coordinated Time Division Multiple Access (Co-TDMA) is one of the hotly debated technologies in this area. A common practice is for multiple access points to negotiate and share transmission opportunity (TXOP) to use air interface resources in a time-sharing manner, thereby reducing service latency and increasing transmission efficiency.

[0055] IEEE 802.11be introduced Transport Opportunity Sharing (TXS) operation. Figure 2 This is a schematic diagram of a transmission opportunity sharing operation provided in an embodiment of this application. The AP sends a CTS-to-self, and then sends a Multi-User Request to Send with TXOP Sharing (MU-TRS TXS) trigger frame to STA1. The MU-TRS TXS trigger frame carries the TXOP sharing time allocated to STA1. STA1 sends a CTS response frame to the AP, and then exchanges frames with the AP. During the obtained TXOP time, the AP shares the TXOP with stations within the basic service set (BSS) to optimize service latency or throughput.

[0056] A common Co-TDMA scheme borrows from the TXS mechanism and extends it accordingly for multi-AP scenarios. In the multi-AP collaboration process based on TXOP, AP(s) share the time and frequency resources used during TXOP. Figure 3 This is a schematic diagram of a multi-AP collaboration process provided in an embodiment of this application. The roles in the multi-AP collaborative TXOP transmission include sharing AP and shared AP. The AP that initiates the sharing process is called the sharing AP, corresponding to... Figure 3 In the context of AP1, the AP(s) coordinated to participate in sharing are called shared AP(s), corresponding to... Figure 3 AP2 / AP3 in the example. Sharing APs obtain TXOPs through air interface contention. The shared APs(s) participating in the sharing use one segment of TXOP(s) in a time-sharing manner. The duration of each TXOP segment can be announced through control frames.

[0057] Figure 3The primary function of the initial control frame (ICF) is to initiate the current Co-TDMA process and trigger signaling interaction; during the TXOP allocation phase, it shares the AP (such as...). Figure 3 AP1 in the context of TXOP allocation uses the MU-TRS TXS trigger frame, also known as the TXOP allocation frame. The main function of the TXOP allocation frame is to trigger the shared AP to begin using the shared TXOP and indicate the sharing parameters. During the TXOP return phase, the shared AP (such as AP1) allocates the TXOP via the MU-TRS TXS trigger frame. Figure 3 AP3 in the middle returns the TXOP to the sharing AP through the TXOP return frame. The purpose of the TXOP return frame is to return the TXOP to the sharing AP in advance if the allocated time has not been used up.

[0058] There are different solutions for handling the TXOP return phase. Solution 1 involves segmenting the control frame to set the duration of the TXOP's network allocation vector (NAV). If the TXOP returns prematurely, the NAV must be reset to avoid affecting subsequent APs' use of the remaining TXOP time. Solution 2 involves adding a CAS Control field to the action frame header to complete the return notification. In both solutions, the TXOP return is completed by sending a control frame through the shared AP, and both solutions incur additional air interface overhead.

[0059] To reduce air interface overhead during the TXOP return phase and improve wireless resource utilization, this application proposes a multi-AP shared return method, apparatus, and access point device.

[0060] In the embodiments of this application, MU-RTS TXS trigger frames and MU-RTS TXS frames can be used interchangeably.

[0061] In the embodiments of this application, shared, TXOP shared, and shared TXOP can be used interchangeably.

[0062] In the embodiments of this application, response, reply, and feedback can be used interchangeably.

[0063] The multi-AP shared return method, apparatus, and access point device provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0064] Figure 4This is a flowchart illustrating a multi-AP shared return method provided in an embodiment of this application. The executing entity of this multi-AP shared return method is the first AP. Here, the first AP can be understood as the sharing AP, that is, the AP that initiates the TXOP sharing process.

[0065] like Figure 4 As shown, the multi-AP shared return method includes:

[0066] Step 400: Receive the first frame from the second AP;

[0067] Receiving the first frame from the second AP can be understood as listening to the first frame from the second AP.

[0068] On the other side of the communication, the second AP sends or broadcasts the first frame.

[0069] The second AP can be understood as a shared AP(s), that is, an AP(s) that is coordinated to participate in sharing.

[0070] The second AP announces its TXOP sharing duration via the first frame. The first AP receives the first frame sent by the second AP, which carries the second AP's TXOP sharing duration.

[0071] The fact that the first frame carries the TXOP sharing duration of the second AP can be understood as the first frame containing a field or information indicating the TXOP sharing duration.

[0072] Figure 5 This is a schematic diagram of a TXOP return in a multi-AP sharing scenario provided in an embodiment of this application. For example... Figure 5 As shown, during the TXOP allocation phase, AP1 (i.e., the first AP) sends a MU-RTS TXS frame to AP2 (i.e., the second AP). This MU-RTS TXS frame carries the TXOP sharing time allocated by AP1 to AP2. During the shared transmission phase, AP1 receives the first frame from AP2. On the other side of the communication, AP2 sends or broadcasts the first frame, announcing the duration information of AP2's TXOP, i.e., the TXOP sharing duration of the second AP.

[0073] In this embodiment of the application, the TXOP sharing duration of the second AP can be understood as the duration during which the second AP uses the shared TXOP. By announcing its TXOP sharing duration, the second AP announces the time it still needs to occupy the channel.

[0074] Optionally, the first frame is a frame sent by the second AP after the feedback frame of the MU-RTS TXS frame. This can be understood as a frame sent by the second AP after the sharing allocation phase, or as a frame sent by the second AP during the sharing transmission phase. The first frame carries the TXOP sharing duration of the second AP.

[0075] In some embodiments, the first frame is the first frame sent by the second AP after the feedback frame of the MU-RTS TXS frame. It can be understood as the first frame sent by the second AP after the sharing allocation phase, or it can also be understood as the first frame sent by the second AP during the sharing transmission phase.

[0076] The aforementioned shared allocation phase can be understood as the phase of allocating TXOP sharing time, triggering the shared AP to use the shared TXOP, and indicating the sharing parameters.

[0077] The shared transmission phase described above occurs after the shared allocation phase, during which the shared AP uses the shared TXOP for data transmission.

[0078] The MU-RTS TXS frame is used to trigger the second AP to use the shared TXOP and indicate the sharing parameters, which include the TXOP sharing time (also known as allocation time) allocated to the second AP.

[0079] Typically, during the sharing allocation phase, the sharing AP (first AP) sends a MU-RTS TXS frame, and the shared AP (second AP) replies with a feedback frame of the MU-RTS TXS frame to confirm participation in TXOP sharing.

[0080] Optionally, the first frame can be a control frame, a data frame, or another type of frame. This application does not limit the type of the first frame. It should be understood that the first frame mentioned above can refer to the first control frame, the first data frame, or the first frame of other types. This application does not limit the type of the first frame in its embodiments.

[0081] In some example embodiments, the first frame is the first data frame, which is the first data frame sent by the second AP after the feedback frame of the MU-RTS TXS frame.

[0082] In some example embodiments, the first frame is the first control frame, and the feedback frame of the MU-RTS TXS frame is the clear-to-send (CTS) frame sent by the second AP during the sharing allocation phase. The first frame following this CTS frame provides feedback on the TXOP sharing duration of the second AP. (Continue to refer to...) Figure 5 , Figure 5 During the sharing allocation phase, AP2 sends a resp frame, which is the feedback frame to the MU-RTS TXS frame. This resp frame is a CTS frame, and the first frame sent by the second AP after this resp frame provides feedback on the TXOP sharing duration of the second AP. The first frame sent by the second AP after this resp frame... Figure 5 The frame in the middle could be an RTS frame sent by the second AP during the shared transmission phase.

[0083] Optionally, the first frame can also be a frame sent by the second AP after the first frame. The first frame must carry the TXOP sharing duration of the second AP. The lengths of the TXOP sharing duration carried by the second AP in different frames sent by the second AP after the first frame may differ, but the endpoints are the same. For example, if the second AP sends a second frame and a third frame after sending the first frame during the shared transmission phase, then the second or third frame can also serve as the first frame. It should be noted that the TXOP sharing duration of the second AP carried in the second frame is longer than that carried in the third frame; however, the end time of the TXOP sharing duration carried in the second frame is the same as the end time of the TXOP sharing duration carried in the third frame.

[0084] Step 401: Obtain the transmission opportunity TXOP sharing duration of the second AP based on the first frame;

[0085] It is understandable that after the first AP receives the first frame sent by the second AP, it obtains the TXOP sharing duration of the second AP based on the first frame.

[0086] Optionally, the TXOP sharing duration of the second AP is indicated by the duration field in the MAC header of the first frame and / or the TXOP field in the preamble. Correspondingly, the first AP determines the TXOP sharing duration of the second AP by obtaining the content of the duration field in the MAC header of the first frame, and / or by obtaining the content of the TXOP field in the preamble.

[0087] Step 402: Update the network allocation vector (NAV) of the first AP according to the TXOP sharing duration of the second AP;

[0088] It is understandable that the first AP updates its network allocation vector (NAV) based on the TXOP sharing duration of the second AP. Specifically, the update method is to set the TXOP sharing duration of the second AP to the NAV of the first AP.

[0089] Optionally, the updating the NAV of the first AP according to the TXOP sharing duration of the second AP further includes:

[0090] using the updated NAV of the first AP for enhanced distributed channel access (English: enhanced distributed channel access, abbreviation: EDCA) processing.

[0091] Step 403: If a first condition is met, perform TXOP return;

[0092] where the first condition includes:

[0093] The end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP.

[0094] The TXOP sharing time is indicated by the first AP through a MU-RTS TXS frame. That is, the first AP sends the MU-RTS TXS frame to the second AP in the sharing allocation phase, and the MU-RTS TXS frame carries the TXOP sharing time allocated to the second AP.

[0095] It should be noted that the TXOP sharing time allocated to the second AP and the TXOP sharing duration of the second AP satisfy that: the TXOP sharing duration of the second AP is less than the TXOP sharing time allocated to the second AP.

[0096] In the embodiments of this application, the end time refers to the end of a period of time or a time unit.

[0097] It can be understood that the first AP performs TXOP return processing by using its NAV information. That is, according to the NAV of the first AP, if it is determined that the first condition is met, the TXOP return is performed.

[0098] In an implementation, the first condition is that the end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP, that is, if the end time of the NAV of the Sharing AP < the end time of the allocation time of the shared AP is satisfied, the Sharing AP performs TXOP return.

[0099] In another embodiment, the first condition further includes: a first duration required for the first AP to perform frame exchange with a first STA is less than or equal to the remaining TXOP sharing time, where the first STA is one or more non-AP stations associated with the first AP. That is, the first condition is: the end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is less than or equal to the remaining TXOP sharing time. It can be understood that the Sharing AP performs TXOP return only when the end time of the NAV of the Sharing AP is less than the end time of the allocation time of the shared AP, and the first duration required for the Sharing AP to perform frame exchange with its associated STA (i.e., the first STA) is less than or equal to the remaining TXOP sharing time. The reason for setting the first condition in this way is that only when the first duration required for the Sharing AP to perform frame exchange with its associated STA (i.e., the first STA) is less than or equal to the remaining TXOP sharing time, can the Sharing AP use the remaining TXOP sharing time to perform frame exchange with the first STA. Otherwise, the Sharing AP cannot complete the frame exchange with the first STA using the remaining TXOP sharing time.

[0100] In the multi-AP sharing and returning method provided in the embodiments of the present application, the first AP updates the NAV according to the TXOP sharing duration of the second AP, and uses this NAV information to perform TXOP return when the first condition is satisfied. An implicit TXOP return manner is adopted, which does not require APs participating in TXOP sharing to send a TXOP return frame, so that air interface overhead can be reduced.

[0101] Optionally, the performing TXOP return includes:

[0102] When the end time of the NAV of the first AP arrives, it is determined that the channel is idle through a carrier sensing mechanism, and the remaining TXOP sharing time is used after a second duration following the arrival of the end time of the NAV of the first AP.

[0103] Optionally, performing TXOP return means that the TXOP is returned to the first AP, that is, the first AP can use the remaining TXOP sharing time.

[0104] It can be understood that when the end time of the NAV of the first AP arrives, the first AP determines that the channel is idle through a carrier sense (English: carrier sense, abbreviated as CS) mechanism, and after a second duration following the arrival of the end time of the NAV, the first AP uses the remaining TXOP sharing time.

[0105] It should be noted that the remaining TXOP sharing time is determined based on the TXOP sharing time allocated to the second AP and the TXOP sharing duration of the second AP.

[0106] Optionally, the second duration is greater than or equal to the Point Coordination Function Interframe Space (PIFS).

[0107] In some embodiments, the second duration is the Point Coordination Function Inter-Frame Spacing (PIFS), that is, when the end time of the first AP's NAV arrives, the first AP determines that the channel is idle through the carrier sensing mechanism, and after the PIFS following the end time of the NAV, the first AP uses the remaining TXOP to share the time.

[0108] refer to Figure 5 If the NAV of the first AP reaches its end time, after the PIFS interval, the TXOP returns to the first AP, and the first AP can use the remaining TXOP to share the time.

[0109] The multi-AP shared return method provided in this application embodiment involves the first AP updating the NAV based on the TXOP sharing duration of the second AP, and using the NAV information to determine that the channel is idle through a carrier sensing mechanism when a first condition is met. After a second duration following the end time of the NAV, the first AP can use the remaining TXOP sharing time. This method adopts an implicit TXOP return method, which does not require the shared AP to send a TXOP return frame, thus reducing air interface overhead.

[0110] In some embodiments, when the first condition is that the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, the use of the remaining TXOP shared time includes:

[0111] Determine whether the first duration required to perform frame exchange with the first STA is less than or equal to the remaining TXOP shared time;

[0112] If the first duration is less than or equal to the remaining TXOP sharing time, a frame exchange is performed with the first STA.

[0113] It is understood that, under the condition that the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, if the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, then the first AP performs a TXOP return. Specifically, the first AP performing a TXOP return includes: when the end time of the NAV of the first AP arrives, determining that the channel is idle through a carrier sensing mechanism, and using the remaining TXOP shared time after a second duration following the arrival of the end time of the NAV. The use of the remaining TXOP shared time includes: the first AP first determining whether the first duration required for frame exchange with the first STA is less than or equal to the remaining TXOP shared time. If the first duration is less than or equal to the remaining TXOP shared time, frame exchange is performed with the first STA within the remaining TXOP shared time. If the first duration is greater than the remaining TXOP shared time, frame exchange is not performed with the first STA.

[0114] The multi-AP shared return method provided in this application embodiment involves the first AP updating the NAV based on the TXOP sharing duration of the second AP, and using the NAV information to determine that the channel is idle through a carrier sensing mechanism. After a second duration following the end of the NAV, the first AP can use the remaining TXOP sharing time. When using the remaining TXOP sharing time, it is necessary to determine whether the first duration required for frame exchange with the first STA is less than or equal to the remaining TXOP sharing time. If the first duration is less than or equal to the remaining TXOP sharing time, frame exchange is performed with the first STA. This method adopts an implicit TXOP return method, which does not require the shared AP to send a TXOP return frame, thus reducing air interface overhead. Furthermore, by determining whether the duration required for frame exchange is less than or equal to the remaining TXOP sharing time before frame exchange with the site equipment, it avoids determining that frame exchange cannot be completed only after frame exchange has started, resulting in invalid frame exchange. This improves the efficiency of frame exchange and avoids invalid frame exchange.

[0115] In some embodiments, if the first condition is met, and the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is less than or equal to the remaining TXOP shared time, then TXOP return is performed.

[0116] The execution of TXOP return includes:

[0117] If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, frame exchange is performed with the first STA during the remaining TXOP shared time.

[0118] Specifically, the first AP's TXOP return includes: if the end time of the first AP's NAV arrives, determining that the channel is idle through a carrier sense mechanism, and using the remaining TXOP sharing time after a second duration following the arrival of the NAV end time. The use of the remaining TXOP sharing time includes: performing frame exchange with the first STA during the remaining TXOP sharing time.

[0119] It is understandable that if the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP and the first STA to exchange frames is less than or equal to the remaining TXOP shared time, it means that the remaining TXOP shared time is sufficient for the first AP and the first STA to exchange frames. Then, after the end time of the NAV of the first AP arrives, the channel is determined to be idle through the carrier sensing mechanism. Then, after the second duration after the end time of the NAV arrives, the first AP and the first STA will exchange frames.

[0120] For an understanding of the second duration in this embodiment, please refer to the description in the previous embodiments, which will not be repeated here.

[0121] The multi-AP shared return method provided in this application embodiment involves the first AP updating the NAV based on the TXOP sharing duration of the second AP. TXOP return processing is only performed when the end time of the first AP's NAV is earlier than the end time of the TXOP sharing time allocated to the second AP, and the first duration required for frame exchange between the first AP and the first STA is less than or equal to the remaining TXOP sharing time. This implicit TXOP return method eliminates the need for the shared AP to send TXOP return frames, reducing air interface overhead. Furthermore, the TXOP return is only performed when the first duration required for frame exchange with the site equipment is less than or equal to the remaining TXOP sharing time, saving air interface resources and improving frame exchange efficiency.

[0122] Optionally, the TXOP sharing duration of the second AP is indicated by the duration field in the MAC header of the first frame and / or the TXOP field in the preamble.

[0123] For example, the first frame is the first data frame sent by the second AP after the feedback frame of the MU-RTS TXS frame. The TXOP field in the preamble of this data frame is used to announce the TXOP sharing duration of the second AP. It should be noted that this method of using the TXOP field in the preamble of the data frame for announcement requires the PPDU protocol version ≥ HE.

[0124] For example, the first frame is the first control frame sent by the second AP after the feedback frame of the MU-RTS TXS frame, and the TXOP field in the preamble of the control frame is used to announce the TXOP sharing duration of the second AP.

[0125] For example, the first frame is the first control frame sent by the second AP after the feedback frame of the MU-RTS TXS frame, and the duration field of the MAC header of the control frame announces the TXOP sharing duration of the second AP.

[0126] For example, the first frame is the first data frame sent by the second AP after the feedback frame of the MU-RTS TXS frame, and the duration field of the MAC header of the data frame is used to announce the TXOP sharing duration of the second AP.

[0127] Optionally, obtaining the TXOP sharing duration of the second AP based on the first frame includes one of the following:

[0128] Obtain the content of the duration field in the MAC header of the first frame to get the TXOP shared duration of the second AP;

[0129] Obtain the content of the TXOP field in the preamble corresponding to the first frame to obtain the TXOP sharing duration of the second AP.

[0130] The multi-AP shared return method provided in this application can save signaling overhead by using the duration field of the MAC header of the first frame and / or the TXOP field in the preamble to indicate the TXOP sharing duration of the second AP.

[0131] Optionally, the method further includes:

[0132] If the end time of the NAV of the first AP is equal to or later than the end time of the TXOP shared time allocated to the second AP, then no TXOP return is performed; or,

[0133] If the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is greater than the remaining TXOP shared time, then TXOP return is not performed.

[0134] Understandably, if the first condition is not met, TXOP will not be executed and will not return.

[0135] The multi-AP shared return method provided in this application embodiment updates the NAV based on the TXOP sharing duration of the second AP, and uses the NAV information to perform a TXOP return if a first condition is met; otherwise, it does not perform a TXOP return. This implicit TXOP return method eliminates the need for the second AP to send a TXOP return frame, thus reducing air interface overhead. This application embodiment uses existing NAV information as input and combines it with a carrier sensing mechanism, resulting in a simple processing method.

[0136] The multi-AP shared return method provided in this application can be executed by a multi-AP shared return device. This application uses the execution of the multi-AP shared return method by a multi-AP shared return device as an example to illustrate the multi-AP shared return device provided in this application.

[0137] This application provides a multi-AP shared return device. As an example, the multi-AP shared return device can be a communication device or a component within a communication device, such as a chip. The communication device can be an access point device.

[0138] The multi-AP shared return device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0139] Specifically, Figure 6 This is a schematic diagram of a multi-AP shared return device provided in an embodiment of this application. See also... Figure 6 When the multi-AP shared return device is an access point device or a component within an access point device, the multi-AP shared return device 600 includes a receiving module 601 for receiving a first frame from the second AP; a processing module 602 for obtaining the transmission opportunity sharing (TXOP) duration of the second AP based on the first frame; the processing module 602 is further configured to update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP; the processing module 602 is further configured to perform a TXOP return if a first condition is met; wherein the first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP; wherein the TXOP sharing time is indicated by the first AP sending a transmission opportunity sharing (MU-RTS) TXS frame through a multi-user request.

[0140] Optionally, the processing module 602 is used for:

[0141] If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, the remaining TXOP time is used to share the time.

[0142] Optionally, the processing module 602 is used for:

[0143] Determine whether the first duration required to perform frame exchange with the first STA is less than or equal to the remaining TXOP shared time;

[0144] If the first duration is less than or equal to the remaining TXOP sharing time, a frame exchange is performed with the first STA;

[0145] The first STA is one or more non-AP sites associated with the first AP.

[0146] Optionally, the first condition further includes: the first duration required for the first AP to exchange frames with the first STA is less than or equal to the remaining TXOP sharing time, wherein the first STA is one or more non-AP sites associated with the first AP.

[0147] Optionally, the processing module 602 is used for:

[0148] If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, frame exchange is performed with the first STA during the remaining TXOP shared time.

[0149] Optionally, the second duration is greater than or equal to the Point Coordination Function Inter-Frame Spacing (PIFS).

[0150] Optionally, the first frame is the first frame sent by the second AP after the feedback frame of the MU-RTS TXS frame.

[0151] Optionally, the TXOP sharing duration of the second AP is indicated by the duration field in the MAC header of the first frame and / or the TXOP field in the preamble corresponding to the first frame.

[0152] Optionally, the processing module 602 is further configured to:

[0153] If the end time of the NAV of the first AP is equal to or later than the end time of the TXOP shared time allocated to the second AP, then no TXOP return is performed; or,

[0154] If the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is greater than the remaining TXOP shared time, then TXOP return is not performed.

[0155] The multi-AP shared return device provided in this application embodiment can achieve... Figures 4 to 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0156] Figure 7 This is a structural schematic diagram of an access point device provided in an embodiment of this application. For example... Figure 7 As shown in the figure, this application embodiment also provides an access point device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instructions that can run on the processor 701. When the program or instructions are executed by the processor 701, they implement the various steps of the above-described multi-AP shared return method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0157] In some embodiments, the access point device 700 may further include a transceiver, which the processor 701 may control to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0158] The transceiver may include a transmitter and a receiver. The transceiver may further include antennas, which may be one or more.

[0159] In some embodiments, the access point device 700 may specifically be the first AP or the second AP in the embodiments of this application. When the access point device 700 is the first AP, it can implement the corresponding process implemented by the first AP in the method of the embodiments of this application, which will not be described in detail here.

[0160] In some embodiments, this application also provides an access point device, including a processor and a communication interface, wherein the communication interface is configured to receive a first frame from a second AP; the processor is configured to obtain the transmission opportunity sharing (TXOP) duration of the second AP based on the first frame; update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP; and perform a TXOP return if a first condition is met; wherein the first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP sharing time allocated to the second AP; wherein the TXOP sharing time is indicated by the first AP sending a transmission opportunity sharing (MU-RTS) TXS frame through a multi-user request.

[0161] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described multi-AP shared return method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0162] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0163] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described multi-AP shared return method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0164] 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.

[0165] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described multi-AP shared return method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0166] This application embodiment also provides a communication system, including: a first AP and a second AP, wherein the first AP can be used to perform the steps of the above-described multi-AP shared return method.

[0167] 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. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0168] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0169] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for sharing return among multiple access points (APs), characterized in that, Applied to the first access point (AP), including: Receive the first frame from the second AP; The transmission opportunity TXOP sharing duration of the second AP is obtained based on the first frame; Update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP; If the first condition is met, execute TXOP and return; The first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP; The TXOP sharing time is indicated by the first AP sending a Transmission Opportunity Sharing MU-RTS TXS frame via a multi-user request.

2. The method according to claim 1, characterized in that, The execution of TXOP return includes: If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, the remaining TXOP time is used to share the time.

3. The method according to claim 2, characterized in that, The use of the remaining TXOP shared time includes: Determine whether the first duration required to perform frame exchange with the first STA is less than or equal to the remaining TXOP shared time; If the first duration is less than or equal to the remaining TXOP sharing time, a frame exchange is performed with the first STA; The first STA is one or more non-AP sites associated with the first AP.

4. The method according to claim 1, characterized in that, The first condition further includes: the first duration required for the first AP to exchange frames with the first STA is less than or equal to the remaining TXOP sharing time, wherein the first STA is one or more non-AP sites associated with the first AP.

5. The method according to claim 4, characterized in that, The execution of TXOP return includes: If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, frame exchange is performed with the first STA during the remaining TXOP shared time.

6. The method according to claim 2 or 5, characterized in that, The second duration is greater than or equal to the Point Coordination Function Inter-Frame Spacing (PIFS).

7. The method according to any one of claims 1-6, characterized in that, The first frame is the first frame sent by the second AP after the feedback frame of the MU-RTS TXS frame.

8. The method according to any one of claims 1-7, characterized in that, The TXOP sharing duration of the second AP is indicated by the duration field in the MAC header of the first frame and / or the TXOP field in the preamble corresponding to the first frame.

9. The method according to claim 1 or 4, characterized in that, The method further includes: If the end time of the NAV of the first AP is equal to or later than the end time of the TXOP shared time allocated to the second AP, then no TXOP return is performed; or, If the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is greater than the remaining TXOP shared time, then TXOP return is not performed.

10. A multi-AP shared return device, characterized in that, include: The receiving module is used to receive the first frame from the second AP; The processing module is used to obtain the transmission opportunity (TXOP) sharing duration of the second AP based on the first frame; The processing module is also configured to update the network allocation vector (NAV) of the first AP based on the TXOP sharing duration of the second AP; The processing module is also configured to execute TXOP return if the first condition is met; The first condition includes: the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP; The TXOP sharing time is indicated by the first AP sending a Transmission Opportunity Sharing MU-RTS TXS frame via a multi-user request.

11. The apparatus according to claim 10, characterized in that, The execution of TXOP return includes: If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, the remaining TXOP time is used to share the time.

12. The apparatus according to claim 11, characterized in that, The use of the remaining TXOP shared time includes: Determine whether the first duration required to perform frame exchange with the first STA is less than or equal to the remaining TXOP shared time; If the first duration is less than or equal to the remaining TXOP sharing time, a frame exchange is performed with the first STA; The first STA is one or more non-AP sites associated with the first AP.

13. The apparatus according to claim 10, characterized in that, The first condition further includes: the first duration required for the first AP to exchange frames with the first STA is less than or equal to the remaining TXOP sharing time, wherein the first STA is one or more non-AP sites associated with the first AP.

14. The apparatus according to claim 13, characterized in that, The execution of TXOP return includes: If the NAV of the first AP ends, the channel is determined to be idle through the carrier sensing mechanism. After a second duration following the end of the NAV of the first AP, frame exchange is performed with the first STA during the remaining TXOP shared time.

15. The apparatus according to claim 11 or 14, characterized in that, The second duration is greater than or equal to the Point Coordination Function Inter-Frame Spacing (PIFS).

16. The apparatus according to any one of claims 10-15, characterized in that, The first frame is the first frame sent by the second AP after the feedback frame of the MU-RTS TXS frame.

17. The apparatus according to any one of claims 10-16, characterized in that, The TXOP sharing duration of the second AP is indicated by the duration field in the MAC header of the first frame and / or the TXOP field in the preamble corresponding to the first frame.

18. The apparatus according to claim 10 or 13, characterized in that, The processing module is also used for: If the end time of the NAV of the first AP is equal to or later than the end time of the TXOP shared time allocated to the second AP, then no TXOP return is performed; or, If the end time of the NAV of the first AP is earlier than the end time of the TXOP shared time allocated to the second AP, and the first duration required for the first AP to perform frame exchange with the first STA is greater than the remaining TXOP shared time, then TXOP return is not performed.

19. An access point device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the multi-AP shared return method as described in any one of claims 1 to 9.

20. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the multi-AP shared return method as described in any one of claims 1 to 9.

Images