Wireless communication method and communication device

Abstract

The invention provides a wireless communication method and communication equipment. The method comprises: a first STA receiving a first field sent by a first AP; wherein the first field is used for bearing first information, the first information is used for instructing the first AP to share a part of TXOP acquired by the first AP to the first STA, the first STA is associated with the second AP, and the first STA is in a coverage range of a signal sent by the first AP. According to the embodiment of the invention, the first STA can send data in the TXOP shared by the first AP, thereby improving the throughput of the first STA, and reducing the sending time delay of the first STA.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method and a communication device. Background Art

[0002] In related technologies, transmission opportunities (TXOPs) can be shared between devices. For example, an access point (AP) can allocate its TXOP to a single station (STA) associated with the AP based on TXOP sharing. For another example, when two APs are within each other's coverage area, one AP can share its acquired TXOP with the other AP through coordinated-AP time division multiple access (CAP TDMA).

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a wireless communication method is provided, the method comprising: a first STA receives a first field sent by a first AP; wherein the first field is used to carry first information, the first information is used to instruct the first AP to share part of the TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

[0006] In a second aspect, a wireless communication method is provided, which includes: a first AP sends a first field to a first STA; wherein the first field is used to carry first information, and the first information is used to instruct the first AP to share part of the TXOP obtained by the first AP with the first STA, and the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

[0007] According to a third aspect, a communication device is provided. The communication device is a first STA, and includes: a receiving unit configured to receive a first field sent by a first AP; wherein the first field is configured to carry first information, and the first information is configured to instruct the first AP to share a portion of a TXOP acquired by the first AP with the first STA; the first STA is associated with a second AP, and the first STA is within coverage of a signal transmitted by the first AP.

[0008] In a fourth aspect, a communication device is provided. The communication device is a first AP. The communication device includes: a transmitting unit, configured to transmit a first field to a first STA; wherein the first field is configured to carry first information, the first information being configured to instruct the first AP to share a portion of a TXOP acquired by the first AP with the first STA, the first STA being associated with a second AP, and the first STA being within coverage of a signal transmitted by the first AP.

[0009] In a fifth aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the first aspect and / or the second aspect.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0011] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device to execute part or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a ninth aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] Since the first STA is within the coverage range of the first AP's transmission signal (hereinafter referred to as the first coverage range), the first STA's data transmission will be affected by the devices within the first coverage range. For example, the first STA cannot access the channel within the TXOP obtained by the first AP. This application proposes that, through the first field, the first AP can share part of the TXOP it has obtained with the first STA. Based on this, the first STA can send data within the TXOP shared by the first AP, thereby improving the first STA's throughput and reducing the first STA's transmission latency. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a wireless communication system used in an embodiment of the present application.

[0016] FIG2 is an example diagram of sharing TXOPs between APs in the CAP TDMA process.

[0017] FIG3 is a diagram illustrating an example of a CAP TDMA process.

[0018] FIG4 is an example diagram of a scenario to which the embodiments of the present application are applicable.

[0019] FIG5 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

[0020] FIG6 is an example diagram of a virtual basic service set (VBSS).

[0021] FIG7 is an example diagram of a VBSS-based technical solution provided in an embodiment of the present application.

[0022] FIG8 is an example diagram of another VBSS-based technical solution provided in an embodiment of the present application.

[0023] FIG9 is an example diagram of a technical solution based on virtual association provided in an embodiment of the present application.

[0024] FIG10 is an example diagram of another technical solution based on virtual association provided in an embodiment of the present application.

[0025] FIG11A is a schematic diagram of the capability information field format provided in an embodiment of the present application.

[0026] FIG. 11B is an example diagram of a format of a field of extremely high throughput (EHT) medium access control (MAC) capabilities information provided by an embodiment of the present application.

[0027] Figure 12 is a schematic diagram of the method provided in Example 1 of the present application.

[0028] Figure 13 is a schematic diagram of the method provided in Example 2 of the present application.

[0029] Figure 14 is a schematic diagram of the method provided in Example 3 of the present application.

[0030] FIG15 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0031] FIG16 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

[0032] FIG17 is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The technical solution in this application will be described below with reference to the accompanying drawings.

[0034] Communication System

[0035] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi) or other communication systems.

[0036] 1 is a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include an access point 110 and a station 120 that accesses a network through the access point 110.

[0037] In some scenarios, an AP is also called an AP STA. In a sense, an AP is also a STA.

[0038] In some scenarios, a STA is also called a non-AP STA.

[0039] The communication in the communication system 100 can be communication between an AP and a STA, communication between STAs, or communication between a STA and a peer STA, where a peer STA may refer to a device that communicates with the STA peer, for example, a peer STA may be an AP or a STA.

[0040] An AP acts as a bridge between wired and wireless networks, connecting wireless network clients together and then connecting the wireless network to the Ethernet. An AP can be a terminal device with a WiFi chip (such as a mobile phone) or a network device (such as a router).

[0041] It should be understood that the role of STA in the communication system is not absolute. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a STA. When the mobile phone serves as a hotspot for other mobile phones, the mobile phone acts as an AP.

[0042] APs and STAs can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0043] In some embodiments, both the STA and the AP may support the 802.11be standard. The STA or AP may also support various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0044] There are one or more links between the station and the access point. In some embodiments, the station and the access point support multi-band communication. For example, communication is performed simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands, or communication is performed simultaneously on different channels in the same band (or different bands), thereby improving the communication throughput and / or reliability between devices. Such a device is generally referred to as a multi-band device, or a multi-link device (MLD), sometimes also referred to as a multi-link entity or a multi-band entity. A multi-link device can be an access point device or a station device. If the multi-link device is an access point device, the multi-link device includes one or more APs; if the multi-link device is a station device, the multi-link device includes one or more non-AP STAs.

[0045] A multi-link device including one or more APs may be referred to as an access point multi-link device (AP MLD), and a multi-link device including one or more non-AP STAs may be referred to as a non-AP multi-link device (non-AP MLD).

[0046] In an embodiment of the present application, the AP may include multiple APs, the non-AP may include multiple STAs, multiple links may be formed between the APs in the AP and the STAs in the non-AP, and data communication may be performed between the APs in the AP and the corresponding STAs in the non-AP through the corresponding links.

[0047] In an embodiment of the present application, a STA may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. that supports WLAN / WiFi technology.

[0048] The frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (such as 2.4 GHz, 5 GHz, and 6 GHz) and high frequency bands (such as 45 GHz and 60 GHz).

[0049] FIG1 exemplarily shows an AP and two STAs. Optionally, the communication system 100 may include multiple APs and other numbers of STAs, which is not limited in the embodiments of the present application.

[0050] It should be understood that in the embodiments of the present application, a device having communication functionality in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include an access point 110 and a station 120 having communication functionality. Access point 110 and station 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a gateway, or other network entities, which is not limited in the embodiments of the present application.

[0051] APs and STAs can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which APs and STAs are located.

[0052] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0053] TXOP sharing

[0054] In some communication systems, an AP can allocate its TXOP to a single non-AP STA associated with the AP based on TXOP sharing. The non-AP STA can implement uplink (UL) physical layer protocol data unit (PPDU) and / or peer-to-peer (P2P) frame exchanges based on the shared TXOP.

[0055] The AP can use a multi-user request to send TXOP sharing (MU-RTS TXS) trigger frame to share the TXOP with a non-AP STA. For example, the Triggered TXOP Sharing Mode subfield of the Common Info field of the multi-user request to send (MU-RTS) trigger frame can give the TXOP sharing mode. If the Triggered TXOP Sharing Mode subfield is 0, it may indicate that the AP does not use TXOP sharing, that is, the trigger frame is an ordinary MU-RTS trigger frame rather than a MU-RTS TXS trigger frame. If the Triggered TXOP Sharing Mode subfield is 1 or 2, it may indicate that the AP uses TXOP sharing, that is, the trigger frame is a MU-RTS TXS trigger frame.

[0056] Multi-AP TXOP sharing

[0057] In some communication systems, TXOP sharing can be achieved between multiple APs. For example, TXOP sharing between multiple APs can be achieved based on coordinated-AP time division multiple access (CAP TDMA).

[0058] Figure 2 illustrates an example of TXOP sharing between APs during the CAP TDMA process. Compared to enhanced distributed channel access (EDCA), in the CAP TDMA process, the AP that gains medium access divides the TXOP duration and shares all frequency resources within a smaller TXOP duration block with its neighboring APs. As shown in Figure 2, if AP1 gains medium access, it can share frequency resources within the TXOP duration block with its neighboring APs (AP2, AP3, and AP4). If AP2 gains medium access, it can share frequency resources within the TXOP duration block with its neighboring APs (AP1, AP3, and AP4).

[0059] It should be noted that the use of CAP TDMA requires the following prerequisites: all APs participating in CAP transmission belong to the same extended service set (ESS); APs cannot manage overlapping basic service sets (OBSS) STAs; APs participating in CAP transmission must be within each other's coverage and able to communicate directly; all APs participating in CAP transmission do not have to have the same primary 20MHz channel; there is no pre-allocated master AP or pre-allocated AP group; the time resources within the TXOP are coordinated by the TXOP holder; and APs coordinate using the air interface.

[0060] As shown in FIG3 , the CAP TDMA process may include: transmission indication and request (TX Ind&Req), scheduling allocation (schedule Alloc) and data transmission (data TX).

[0061] For example, AP1, having received a TXOP, can send an indication to other APs, inquiring about their willingness to participate in CAP TDMA. If other APs wish to participate in CAP TDMA initiated by AP1, they can respond to AP1's indication. AP1 informs other APs of the start time and duration of its allocated TXOP. During the allocated TXOP time, other APs that have received the TXOP can perform data transmission with associated non-AP STAs.

[0062] The expected benefits of CAP TDMA may include one or more of the following: improved worst-case latency; improved throughput fairness. CAP TDMA's primary advantage is low latency, meaning it can improve worst-case latency in multi-BSS scenarios. When APs frequently share TXOPs, the AP can provide each node with greater access to the medium. CAP TDMA can also help devices experiencing interference transmit more frequently, thereby providing more equitable throughput.

[0063] The most significant limitation of CAP TDMA is that the two APs sharing a TXOP must be within each other's coverage area. This requirement enables the two APs (for example, AP1 and AP2) to communicate directly over the air interface. In this scenario, low-latency traffic for all non-AP STAs associated with AP1 and all non-AP STAs associated with AP2 can be transmitted much faster than without CAP TDMA. This is because without CAP TDMA, non-AP STAs associated with AP1 can only transmit data by competing for channel access or by being scheduled by AP1. If AP1 is within the coverage area of ​​AP2 and AP2 accesses the channel, neither AP1 nor its associated non-AP STAs can transmit data while AP2 obtains the TXOP. Similarly, for AP2, neither AP2 nor its associated non-AP STAs can transmit data while AP1 accesses the channel. Therefore, if either the AP or non-AP STA has low-latency data, it cannot be transmitted immediately, resulting in longer delays. CAP TDMA alleviates this problem. If AP1 accesses the channel, AP1 can share part of its TXOP with AP2 to complete data transmission with its associated non-AP STA. Similarly, if AP2 accesses the channel, it can share part of its TXOP with AP1 to complete data transmission with its associated non-AP STA.

[0064] As can be seen from the above, related technologies can enable TXOP sharing between devices. For example, based on TXOP sharing technology, an AP can share its TXOP with associated non-AP STAs. In another example, if two APs are within each other's coverage area, the two APs can share the TXOP obtained by one of the APs through CAP TDMA.

[0065] However, it is difficult for the AP to share TXOPs with STAs that are not associated with the AP. As discussed above, if the STA is within the AP's coverage area, this may result in longer transmission delays and lower throughput. This is further analyzed with reference to Figure 4.

[0066] As shown in Figure 4, the coverage areas of AP1 and AP2 are outlined by circular dashed lines. AP1 is associated with STA1 and STA3 (indicated by the double-arrow dashed lines), while AP2 is associated with STA2. STA1 is within the coverage area of ​​AP2, and STA2 is within the coverage area of ​​AP2. Therefore, compared to STA3, STA1 is subject to interference from devices within AP2's coverage area. For example, whether AP2 or STA2 accesses the channel, STA1's basic network allocation vector (NAV) is set, preventing STA1 from accessing the channel during this period. In other words, STA1 cannot access the channel during the TXOP acquired by AP2. If STA1 cannot access the channel, if it has data to transmit (such as low-latency data (also known as delay-sensitive data)), it will not be able to send this data in a timely manner, resulting in longer latency. Furthermore, if STA1 and STA3 have the same amount of data to transmit, STA1 will take longer to transmit this data because it is subject to greater interference. Therefore, STA1's throughput will be lower than STA3's.

[0067] To address the above issues, the present application proposes a method as shown in Figure 5. Figure 5 is a schematic flow chart of a wireless communication method provided by an embodiment of the present application. The method as shown in Figure 5 can be performed by a first STA and a first AP.

[0068] The first AP may be a device that acquires a TXOP. In other words, the first AP may be a TXOP holder.

[0069] The first STA may be associated with the second AP. For example, the first STA may be a non-AP STA associated with the second AP. The second AP may be an AP different from the first AP. In other words, the first STA is not associated with the first AP.

[0070] The first STA may be within the coverage of the signal transmitted by the first AP. For example, the first STA may be within the basic service set (BSS) corresponding to the first AP (hereinafter referred to as the first BSS). As described above, the first STA may be associated with the second AP. Therefore, the first STA may be within the BSS corresponding to the second AP (hereinafter referred to as the second BSS). In this case, the first STA is within both the first BSS and the second BSS. That is, the first STA is within the OBSS. Therefore, the first STA may also be referred to as an OBSS non-AP STA.

[0071] Taking the scenario shown in Figure 4 as an example, the first AP can be AP2, the first STA can be STA1, and the second AP can be AP1. As shown in Figure 4, STA1 is located in AP2's BSS, but STA1 is associated with AP1. In other words, STA1 is within AP2's signal coverage area but is not associated with AP2.

[0072] The method shown in FIG. 5 may include step S510 .

[0073] Step S510: A first STA receives a first field sent by a first AP.

[0074] The first field may carry first information. The first information may be used to instruct the first AP to share a portion of the TXOP acquired by the first AP with the first STA.

[0075] In some embodiments, the first field may include a newly added field. The newly added field may occupy one or more bits in a reserved field in the related art. In other embodiments, the first field may include an existing field in the related art. For example, when an existing field has a specific value, it may indicate that the existing field and / or a field related to the existing field carries the first information.

[0076] The first field may include one or more fields. That is, the first information may be indicated by one field or by a combination of multiple fields.

[0077] In some embodiments, the first field may be carried in a first trigger frame. The first trigger frame may be, for example, a MU-RTS TXS trigger frame. For example, the first field may include a triggered TXOP sharing mode (Triggered TXOP Sharing Mode) subfield in the MU-RTS TXS trigger frame. Exemplarily, if the triggered TXOP sharing mode subfield is a first value, it may indicate that the MU-RTS TXS trigger frame is used to share part of the TXOP with non-associated STAs. The first value may be greater than or equal to 3. For another example, the first field may include a newly added field in the MU-RTS TXS trigger frame. If the newly added field is a second value, it may indicate that the MU-RTS TXS trigger frame is used to share part of the TXOP with non-associated STAs. The second value may be a number greater than or equal to 0.

[0078] The first information may also be used to indicate information about a TXOP shared by the first AP for the first STA. The information about the TXOP shared by the first AP for the first STA may include one or more of the following: a start time of the shared TXOP, an end time of the shared TXOP, and a duration of the shared TXOP. The shared TXOP may also be referred to as an allocated TXOP.

[0079] Although the first STA is not associated with the first AP, the first AP can share part of its acquired TXOP with the first STA through the first field. The first STA can send data within the TXOP shared with the first AP, thereby improving the first STA's throughput and reducing the first STA's transmission latency.

[0080] For example, when the first AP obtains the TXOP, if there is a remaining part of the TXOP, or the device in the first BSS does not have low-latency data waiting to be sent, if the first STA has low-latency data waiting to be sent, the first AP can share part of the TXOP with the first STA, thereby improving the throughput of the first STA.

[0081] For example, if the first AP releases the remaining TXOP, the device accessing the channel may not be the first STA, meaning the first STA may not be able to access the channel immediately. However, through step S510, the first AP can accurately share the TXOP with the first STA, thereby increasing the first STA's chance of successfully competing for the channel and ensuring fairness in device access to the channel. By increasing the first STA's chance of successfully competing for the channel, the first STA's throughput can be improved.

[0082] Furthermore, as noted above, implementing TXOP sharing among multiple APs through CAP TDMA requires both APs to be within each other's coverage. This means that, in related art, if a first STA is not within the coverage of the second AP, the first AP cannot share its TXOP with the second AP for communication with the first STA. However, this application is not subject to these limitations. A first STA within the overlapping coverage of two APs can obtain the shared TXOP using the first information, thereby addressing issues such as the urgent need for low-latency services and throughput fairness.

[0083] It should be noted that the first STA and the first AP can have the same or different primary channels. The first AP's primary channel must be within the first STA's operating channel range. The first STA's primary channel should be within the first AP's operating channel range. If the first AP shares a TXOP with the first STA, the channel assigned by the first AP to the first STA must include the first STA's primary channel, and the channel assigned by the first AP to the first STA must also include the first AP's primary channel.

[0084] The following describes in detail how the first AP sends the first field to the first STA.

[0085] In some embodiments, the first AP and the second AP may belong to the same VBSS. A VBSS may refer to an infrastructure BSS with a set of cooperating APs. A set of cooperating APs within a VBSS may be referred to as a cooperating AP group. A cooperating AP group may include multiple APs, which may implement multi-AP collaboration. The cooperating AP group may include a multi-AP coordinator and at least one member AP. The multi-AP coordinator may be used to control the member APs of the VBSS.

[0086] Figure 6 is an example diagram of a VBSS. As shown in Figure 6, the collaborative AP group in the VBSS includes a multi-AP coordinator, member AP1, and member AP2. Link quality metrics can be performed between AP1 and STA1. For example, link quality metrics can be implemented using a received signal strength indicator (RSSI). Similarly, link quality metrics can be performed between AP2 and STA2. Multiple APs can communicate via backhaul links.

[0087] A non-AP STA can be served by one or more selected anchor APs. For a specific non-AP STA, some or all member APs within the VBSS can serve as anchor APs for that non-AP STA. For example, the anchor AP for a non-AP STA can be an associated AP.

[0088] A VBSS can meet one or more of the following requirements: all member APs can share the same service set identifier (SSID), that is, all member APs can belong to the same ESS; all member APs share association / authentication; when non-AP STAs roam within the VBSS, they do not need to re-associate / authenticate; non-AP STAs use the same starting association identifier (AID) within the VBSS, that is, non-AP STAs have globally unique AIDs within the VBSS; non-AP STAs will locally retain the capability information of the anchor AP and neighbor APs; all member APs operate on the same channel; and non-AP STAs can receive data from any member AP in the VBSS.

[0089] Based on VBSS, related technologies implement multi-AP collaborative communication. Based on VBSS, this application can implement information exchange between a first STA and a first AP. The information exchange between the first STA and the first AP can be implemented based on one or more of the following VBSS features: Based on the VBSS architecture, an AP can obtain information about all non-AP STAs within its coverage area, even if the AP is not associated with the non-AP STA; Based on the VBSS architecture, a non-AP STA can obtain information about all APs (including anchor APs and neighbor APs) within its coverage area; and a non-AP STA has a globally unique AID within the VBSS.

[0090] Taking the example of a first AP sending a first field to a first STA, the first AP may send the first field through a second AP associated with the first STA. The first AP and the second AP may communicate via a backhaul link. Alternatively, the first AP and the second AP may communicate via a backhaul link via a multi-AP coordinator.

[0091] The following uses Figures 7 and 8 as examples to illustrate the technical solution based on VBSS. The first AP can be AP2 as shown in Figure 7 or 8, the first STA can be STA1 as shown in Figure 7 or 8, and the second AP can be AP1 as shown in Figure 7 or 8. AP1, AP2, and the multi-AP coordinator can form a VBSS. AP1 and AP2 have the same SSID and belong to the same ESS. AP1 and AP2 can be controlled by the multi-AP coordinator, and both AP1 and AP2 have established backhaul links with the multi-AP coordinator (indicated by the black solid line). The anchor AP for STA1 and STA3 can be AP1. The anchor AP for STA2 can be AP2. STA1, STA2, and STA3 all have globally unique AIDs within the VBSS. AP2 can first send the first field to the multi-AP coordinator. The multi-AP coordinator then sends the first field to AP1. AP1 sends the received first field to STA1.

[0092] It should be noted that the first AP and the second AP in a VBSS may not be within each other's coverage. As shown in Figure 7, AP1 and AP2 are not within each other's coverage. In this case, the first AP and the second AP cannot directly communicate over the air interface. Therefore, the first AP and the second AP cannot share the TXOP obtained by the first AP with the second AP through the CAP TDMA technical solution to achieve communication between the first STA and the second AP. However, based on the present application, even if the first AP and the second AP are not within each other's coverage, the first AP can share the TXOP obtained by the first AP with the first STA.

[0093] It should be noted that the first and second APs in a VBSS can be within each other's coverage area. As shown in Figure 8, AP1 and AP2 are within each other's coverage area. In this case, at any given time, only one of the first and second APs can access the channel.

[0094] The above describes the technical solution based on VBSS. The following describes the technical solution of virtual association.

[0095] In some embodiments, a first STA can be virtually associated with a first AP. Virtually associated devices can transmit control information and / or management information, but cannot transmit data. A first STA can be virtually associated with one or more APs. That is, although a first STA can only establish an association with a second AP, it can establish a virtual association with one or more APs.

[0096] It should be noted that APs can also establish virtual associations. For example, if a second AP is within the coverage area of ​​a first AP's signal transmission, and the first AP is also within the coverage area of ​​the second AP's signal transmission (i.e., the first AP and the second AP are within each other's coverage area), the second AP can be virtually associated with the first AP. When a second AP can be virtually associated with a first AP, control information and / or management information can be transmitted between the first and second APs, but data cannot be transmitted.

[0097] It should be noted that the AP that establishes a virtual association with the first STA (ie, the first AP) and the AP that establishes an association (ie, the second AP) both belong to the same ESS. Multiple APs that are virtually associated need to belong to the same ESS.

[0098] The first AP can assign a unique AID to a device virtually associated with the first AP. Therefore, even if the first STA is not associated with the first AP, the first AP can assign an AID to the first STA if the first STA is virtually associated with the first AP. Based on the AID assigned by the first AP to the first STA, the first AP can communicate with the first STA. For example, based on the AID assigned by the first AP to the first STA, the first AP can send a first field to the first STA.

[0099] It should be noted that virtual association does not affect the use of the original NAV. For example, the STA can regard the NAV set in the BSS where the virtual associated AP is located as the basic NAV, and the NAV set in the BSS where the associated AP is located as the internal NAV.

[0100] The following describes the technical solution for virtual association in conjunction with Figures 9 and 10. The first AP may be AP2 as shown in Figure 9 or 10, the first STA may be STA1 as shown in Figure 9 or 10, and the second AP may be AP1 as shown in Figure 9 or 10. AP1 is associated with STA1 and STA3 (indicated by double-arrow dashed lines); AP2 is associated with STA2. AP1 and AP2 have the same SSID and belong to the same ESS. STA1 can be virtually associated with AP2 (indicated by double-arrow solid lines in the figure). After STA1 establishes a virtual association with AP2, control information and / or management information can be transmitted between STA1 and AP2.

[0101] It should be noted that the first AP and the second AP may not be within each other's coverage. As shown in Figure 9, AP1 and AP2 are not within each other's coverage. In this case, the first AP and the second AP cannot directly communicate over the air interface. Therefore, the first AP and the second AP cannot share the TXOP obtained by the first AP with the second AP through multi-AP TXOP sharing, thereby enabling communication between the first STA and the second AP. However, based on the present application, even if the first AP and the second AP are not within each other's coverage, the first AP can share the TXOP obtained by the first AP with the virtually associated first STA.

[0102] It should be noted that the first AP and the second AP can be within each other's coverage. As shown in Figure 10, AP1 and AP2 are within each other's coverage. In this case, at any given time, only one of the first and second APs can access the channel. When the first AP accesses the channel, the first AP can share the TXOP obtained by the first AP with the virtually associated first STA. Alternatively, the first AP can share the TXOP obtained by the first AP with the virtually associated second AP.

[0103] It should be noted that the process for establishing a virtual association is similar to the process for establishing an association between an AP and a non-AP STA in related technologies. The main differences include: the device needs to indicate that it supports virtual association; and the device needs to declare that it is establishing a virtual association. This is explained in detail below.

[0104] In some embodiments, the first AP may send virtual association capability information. The virtual association capability information may indicate whether the first AP supports other devices to establish a virtual association with the first AP.

[0105] The virtual association capability information can be carried in the virtual association capability subfield in the capability information field. The capability information field can be carried in a beacon frame or a probe response frame. Figure 11A is an example diagram of the capability information field. The capability information field may include one or more of the following fields: ESS, independent basic service set (IBSS), reserved field, privacy, short preamble, spectrum management, quality of service (QoS), short slot time, automatic power save delivery (APSD), radio measurement, and end process delay (EPD).

[0106] For example, if the virtual association capability information is 0, it may indicate that the first AP does not support a communication device establishing a virtual association with the first AP; if the virtual association capability information is 1, it may indicate that the first AP supports a communication device establishing a virtual association with the first AP. Alternatively, if the virtual association capability information is 1, it may indicate that the first AP does not support a communication device establishing a virtual association with the first AP; if the virtual association capability information is 0, it may indicate that the first AP supports a communication device establishing a virtual association with the first AP.

[0107] The first STA or the second AP may send virtual association request information. The virtual association request information may be used to indicate that the first STA or the second AP requests to establish a virtual association.

[0108] The virtual association request information may be carried in the virtual association capability subfield of the capability information field. The capability information field may be carried in an association request frame. FIG11A is an example diagram of the capability information field.

[0109] For example, if the virtual association request information is 0, it may indicate that the first STA or the second AP is requesting to establish a virtual association; if the virtual association request information is 1, it may indicate that the first STA or the second AP is not requesting to establish a virtual association. Alternatively, if the virtual association request information is 1, it may indicate that the first STA or the second AP is requesting to establish a virtual association; if the virtual association request information is 0, it may indicate that the first STA or the second AP is not requesting to establish a virtual association.

[0110] The first AP may send virtual association response information. The virtual association response information may be used to indicate that the first AP is to establish a virtual association.

[0111] The virtual association response information may be carried in the virtual association capability subfield of the capability information field. The capability information field may be carried in an association response frame. FIG11A is an example diagram of the capability information field.

[0112] For example, if the virtual association response information is 0, it may indicate that the first AP is to establish a virtual association; if the virtual association response information is 1, it may indicate that the first AP is not to establish a virtual association. Alternatively, if the virtual association response information is 1, it may indicate that the first AP is to establish a virtual association; if the virtual association response information is 0, it may indicate that the first AP is not to establish a virtual association.

[0113] As mentioned above, a virtual association can also be established between two APs. One of the two APs can be the master AP, and the other can be the slave AP. For example, the AP that sends the virtual association request message can be the slave AP, and the AP that sends the virtual association response message can be the master AP.

[0114] Based on the VBSS solution and / or virtual association solution described above, a TXOP sharing solution can be implemented between an AP and unassociated STAs. This TXOP sharing solution can include one or more of the following: capability indication, buffer status reporting, scheduling allocation, and data transmission. Each of these is described below.

[0115] Ability Indicator

[0116] In some embodiments, a first AP or a first STA may declare whether it supports OBSS TXOP sharing. For the first AP, OBSS TXOP sharing may include: the first AP is able to share a TXOP with the first STA. Alternatively, OBSS TXOP sharing may include: the first AP supports sharing a TXOP with devices within the OBSS. For the first STA or a second AP, OBSS TXOP sharing may include: the first STA or the second AP is able to use a TXOP shared by the first AP. Alternatively, OBSS TXOP sharing may include: the first STA or the second AP supports the use of a TXOP shared by unassociated APs within the OBSS. Alternatively, OBSS TXOP sharing may include: the first STA or the second AP is willing to participate in a TXOP shared by unassociated APs within the OBSS.

[0117] OBBS TXOP sharing can be represented by a new TXOP sharing mode. For example, OBBS TXOP sharing capability can be represented by TXOP Sharing Mode 3.

[0118] It should be noted that there may be two modes of TXOP sharing in the related art. These two modes may be TXOP Sharing Mode 1 and TXOP Sharing Mode 2. For example, the Triggered TXOP Sharing Mode 1 Support and Triggered TXOP Sharing Mode 2 Support subfields in the EHT MAC Capability Information field in the EHT Capability Element respectively indicate whether the current STA supports TXOP Sharing Mode 1 and TXOP Sharing Mode 2. The OBBS TXOP sharing capability mentioned above can be represented by TXOP Sharing Mode 3 in order to distinguish it from the TXOP sharing mode in the related art. Therefore, the OBBS TXOP sharing capability can also be represented by TXOP sharing modes with other serial numbers, as long as it is distinguished from the TXOP mode in the related art.

[0119] In some embodiments, the first AP may send first capability information. The first capability information may be used to indicate whether the first AP supports OBSS TXOP sharing.

[0120] In some embodiments, the first STA may send second capability information, where the second capability information may be used to indicate whether the first STA supports OBSS TXOP sharing.

[0121] The first capability information or the second capability information can be carried in a field within a capabilities element. In other words, whether a device supports OBSS TXOP sharing can be indicated by a field within the capabilities element. For example, the first capability information and the second capability information can be carried in the same field within the capabilities element. When the first AP sends this field, it can indicate the first capability information; when the first STA sends this field, it can indicate the second capability information.

[0122] The capability element may include, for example, an EHT capability element. For example, information indicating whether a device supports OBSS TXOP sharing may be carried in a subfield within the EHT MAC capability information field within the EHT capability element. This subfield may be a newly added "Triggered TXOP Sharing Mode 3 Support" subfield.

[0123] For example, for an AP, if the "Triggered TXOP Sharing Mode 3 Support" subfield is set to N, it indicates that the AP can transmit a MU-RTS TXS trigger frame and allocate a TXOP segment to the first STA or slave AP. Alternatively, if the "Triggered TXOP Sharing Mode 3 Support" subfield is set to N, it indicates that the AP can respond to MU-RTS TXS trigger frames as a slave AP and send information to associated or virtually associated devices via a TXOP shared by other APs. If the "Triggered TXOP Sharing Mode 3 Support" subfield is set to M, it indicates that the AP cannot transmit a MU-RTS TXS trigger frame or cannot allocate a TXOP segment to the first STA or slave AP. Alternatively, if the "Triggered TXOP Sharing Mode 3 Support" subfield is set to M, it indicates that the AP cannot respond to MU-RTS TXS trigger frames as a slave AP or cannot send information to associated or virtually associated devices via a TXOP shared by other APs. N can be 1 and M can be 0, or N can be 0 and M can be 1.

[0124] For another example, for the first STA, if the "Triggered TXOP Sharing Mode 3 Support" subfield is set to N, it indicates that the first STA can respond to the MU-RTS TXS trigger frame, and the MU-RTS TXS trigger frame allocates a TXOP to the first STA or the slave AP. If the "Triggered TXOP Sharing Mode 3 Support" subfield is set to M, it indicates that the first STA cannot respond to the MU-RTS TXS trigger frame, and the MU-RTS TXS trigger frame cannot allocate a TXOP to the first STA. N can be 1 and M can be 0; or N can be 0 and M can be 1.

[0125] In some implementations, the "Triggered TXOP Sharing Mode 3 Support" subfield may be a subfield added to BIT14 of the EHT MAC Capability Information field of the EHT Capability element. FIG11B is an example diagram of the EHT MAC Capability Information field format. As shown in FIG11B , the EHT Capability element may include the following fields: Element ID, Length, Element ID Extension, EHT MAC Capability Information, EHT PHY Capabilities Information, Supported EHT-MCS And NSS Set, and EHT PPE Thresholds (Optional). The EHT MAC Capability Information field includes a Triggered TXOP Sharing Mode 3 Support subfield (indicated by a gray background box). The EHT MAC capability information field may also include the following subfields: EPCS Priority Access Support, EHT OM Control Support, Triggered TXOP Sharing Mode1 Support, Triggered TXOP Sharing Mode2 Support, Restricted TWT Support, SCS Traffic Description Support, Maximum MPDU Length, Maximum A-MPDU Length Exponent Extension, EHT TRS Support, TXOP Return Support In TXOP Sharing Mode2, TWO BQRs Support, EHT Link Adaptation Support, and reserved fields.

[0126] Cache Status Report

[0127] In some embodiments, the first STA may send second information to the first AP. The second information may be used to indicate buffer information of the first STA. The buffer information may include, for example, a buffer status. The buffer status may include, for example, one or more of the following information: the amount of data to be sent, whether there is delay-sensitive data to be sent, and the amount of delay-sensitive data to be sent.

[0128] Based on the second information, the first AP can obtain the cache status of the first STA and allocate resources to the first STA. For example, the first AP can allocate a TXOP to the first STA based on the second information, so that the first STA completes the transmission of data to be sent and / or delay-sensitive data to be sent.

[0129] As described above, the interaction between the first STA and the first AP may be implemented based on VBSS and / or virtual association, which will be described below respectively.

[0130] For example, the first AP and the second AP may belong to the same VBSS. Optionally, the first STA may send the second information to the first AP through the second AP. For example, the first STA may send the second information to the second AP, and the second AP may indirectly send the second information to the neighboring AP of the first STA (e.g., the first AP) through the multi-AP coordinator.

[0131] For another example, the first STA can be virtually associated with the first AP. Based on the virtual association between the first STA and the first AP, the first STA can send the second information to the first AP. Alternatively, the second AP can be virtually associated with the first AP, and based on the virtual association between the second AP and the first AP, the first STA can send the second information to the first AP through the second AP. As can be seen from the above, after establishing the virtual association, the first AP can know the information of all non-AP STA / APs that have established virtual associations within its coverage area. Both the associated non-AP STA and the virtually associated non-AP STA / AP have a unique AID. Similarly, the non-AP STA / AP can know the information of the AP with which it has established a virtual association. Therefore, based on the virtual association between the first STA / second AP and the first AP, the first STA can send the second information to the first AP.

[0132] Similarly, when a first AP and a second AP are virtually associated, the second AP can transmit its cache information so that the first AP can allocate a shared TXOP to the second AP. For example, in the scenario shown in Figure 10, the first AP is AP2 and the second AP is AP1. AP2 is the master AP and AP1 is the slave AP. To allocate a TXOP to AP1, AP2 needs to know AP1's cache information. AP1 needs to report its cache status using the second information to inform AP2 of its cache status and facilitate resource allocation.

[0133] In some embodiments, in response to a first STA receiving a first trigger message sent by a first AP, the first STA sends the second message to the first AP. In other words, the first STA will send the second message to the first AP only if the first AP sends the first trigger message or the first STA receives the first trigger message. In other words, the first trigger message can be used to request the first STA's cached information.

[0134] Optionally, the first AP may send the first trigger information directly to the first STA. Alternatively, the first AP may send the first trigger information to the first STA via a second AP. In other words, the first AP may trigger the second AP associated with the first STA, and the first AP may obtain the cached information of the first STA through the second AP.

[0135] The first trigger information may be carried in a first trigger frame, and the second information may be carried in a response frame corresponding to the first trigger frame.

[0136] In some implementations, the first trigger frame may be a buffer status report poll (BSRP) frame. That is, by multiplexing the BSRP frame, the first AP may initiate an explicit buffer status report request to the first STA. The first STA may respond with the first STA's buffer information to the first AP.

[0137] In some implementations, the first trigger may be a new type of trigger frame. The new type may be a first type. The first type may be, for example, an OBSS BSRP. Correspondingly, the first type of trigger frame may be an OBSS BSRP frame.

[0138] For the first type of trigger frame, there may be a User Info field containing the AID information of the first STA. The RA field of the first type of trigger frame may point to the first STA.

[0139] The first type of trigger frame may be added by adding the first type to the Trigger Type subfield of the Common Info field of the trigger frame. For example, the Trigger Type subfield value corresponding to the first type may be a value greater than 7 and less than 16.

[0140] Table 1 is an example diagram of the coding of the trigger type subfield. As shown in Table 1, the first type is OBSS BSRP, and the value of the trigger type subfield corresponding to the first type is 8.

[0141] Table 1

[0142] In some embodiments, if a first condition is met, the first STA sends the second information to the first AP. For the first trigger information, the first condition may be a response condition for the first trigger information. That is, the first STA may respond to the first trigger information and send the second information only if the first condition is met.

[0143] In some embodiments, if a first condition is met, the second AP virtually associated with the first AP may send second information to the first AP.

[0144] Optionally, the first condition may include: the value of the first STA's internal NAV is 0, and the basic NAV of the first STA set by devices other than the first AP is 0. It is understandable that the first condition ignores the basic NAV of the first STA set by the first AP. If the internal NAV of the first STA is not 0, then a device in the BSS where the second AP associated with the first STA is located is occupying the channel. Therefore, the first STA cannot send the second information to the first AP. The basic NAV of the first STA can be set by a device not associated with the first STA. If the basic NAV set by a device other than the first AP is not 0, then there are other devices other than the first AP and the second AP occupying the channel. Therefore, the first STA cannot send the second information to the first AP.

[0145] Optionally, the first condition may include: the first STA's physical carrier sensing does not detect that the channel is busy. In the case that the first STA's physical carrier sensing detects that the channel is busy, the first STA cannot transmit the second information on the busy channel.

[0146] Scheduling Allocation

[0147] In some embodiments, the first STA receives third information sent by the first AP. The third information may be used to instruct the first AP to initiate a TXOP sharing process for the first STA. Alternatively, the third information may be used to indicate information about the TXOP allocated by the first AP to the first STA.

[0148] It can be understood that, based on the third information, the OBSS TXOP sharing capability described above can be implemented.

[0149] The third information may be carried in the second field. The second field may be, for example, a triggered TXOP sharing mode (Triggered TXOP Sharing Mode) subfield in the MU-RTS TXS trigger frame.

[0150] The second field being the first value may indicate that the first AP initiates a TXOP sharing process for the first STA. Table 2 is described using an example in which the second field is the triggered TXOP sharing mode subfield and the first value is 3.

[0151] As can be seen from Table 3, if the first AP supports OBSS TXOP sharing, it indicates support for the use of TXOP sharing mode 3 newly added in this application. The behavior of the first AP may include: the MU-RTS TXS frame sent contains only one user information (User Info) field, and the AID subfield therein is the AID of the non-associated STA supporting OBSS TXOP sharing within the coverage area of ​​the AP.

[0152] In combination with the OBSS TXOP sharing capability described above, if the device's capability supports OBSS TXOP sharing, it may indicate that the corresponding device supports transmitting or responding to MU-RTS TXS trigger frames, and the triggered TXOP sharing mode field is equal to 3.

[0153] It should be noted that the second field and the first field may include the same field. For example, the second field may be the same as the first field. That is, the same field may be used to carry both the first information and the third information. For example, both the first field and the second field may include a triggered TXOP sharing mode subfield in the MU-RTS TXS trigger frame. When the triggered TXOP sharing mode subfield is a first value, the triggered TXOP sharing mode subfield may indicate that the first AP initiates a TXOP sharing process for the first STA, and may also indicate that the MU-RTS TXS trigger frame is used by the first AP to share part of the TXOP obtained by the first AP with the first STA.

[0154] In some embodiments, if the second condition is met, the first STA may send a response message to the first AP for the third information. Alternatively, if the second condition is met, the first STA may send a response message to the first AP. For example, if the first AP receives a response message from the first STA, it may indicate that the TXOP allocation is successful; if the first AP does not receive a response message from the first STA, it may indicate that the TXOP allocation has failed.

[0155] When the third information is carried in a trigger frame, the response information can be carried in a clear to send (CTS) frame. If the first AP receives a CTS frame from the first STA, it can indicate that the TXOP allocation is successful; if the first AP does not receive a CTS frame from the first STA, it indicates that the TXOP allocation failed.

[0156] Optionally, the second condition may include: the value of the first STA's internal NAV is 0, and the basic NAV of the first STA set by devices other than the first AP is 0. It is understandable that the second condition ignores the basic NAV of the first STA set by the first AP. If the internal NAV of the first STA is not 0, the device in the BSS where the second AP associated with the first STA is located is occupying the channel. Therefore, the first STA cannot send a response message to the first AP. The basic NAV of the first STA can be set by a device not associated with the first STA. If the basic NAV set by a device other than the first AP is not 0, there are other devices other than the first AP and the second AP occupying the channel. Therefore, the first STA cannot send a response message to the first AP.

[0157] Optionally, the second condition may include: the first STA's physical carrier sensing does not detect that the channel is busy. In the case that the first STA's physical carrier sensing detects that the channel is busy, the first STA cannot transmit response information on the busy channel.

[0158] The following takes the scenario shown in FIG7 as an example to illustrate Case 1 and Case 2 respectively.

[0159] Case 1: STA1 and STA3 are not within each other's coverage.

[0160] As shown in Figure 7, STA1 and STA3 are associated with AP1, and STA2 is associated with AP2. STA1 and STA3 are not within each other's coverage area and cannot communicate directly over the air interface. Assume that AP2 wants to share its TXOP with STA1 and uses a MU-RTS TXS trigger frame to share the TXOP. If STA1 can use the TXOP, it can send a CTS frame to AP2; otherwise, it cannot. Possible scenarios include Case 1.1 and Case 1.2.

[0161] In case 1.1, STA3 is performing uplink transmission. STA1 can normally receive MU-RTS TXS frames from AP 2. STA1's internal NAV may not be 0 (for example, set by an RTS or CTS frame sent by AP1), or it may be 0 (for example, STA1 is in the OBSS area, and a conflict may occur when STA1 receives the RTS or CTS frame sent by AP1, causing the internal NAV to be incorrectly set to 0). If STA1's internal NAV is not 0, STA1 will not reply with a CTS frame to AP2, and AP2's TXOP sharing fails. If STA1's internal NAV is 0 and all other NAVs except the basic NAV set by AP2 are 0, and physical carrier sensing detects that the channel is idle, STA1 can reply with a CTS frame to AP2.

[0162] In case 1.2, STA3 does not transmit data. STA 1 receives the MU-RTS TXS frame from AP 2 normally. On STA 1, the internal NAV is 0. Only if all other NAVs except the basic NAV set by AP 2 are 0 and physical carrier sensing detects an idle channel can non-AP STA 1 reply with a CTS frame to AP 2.

[0163] Case 2: STA1 and STA3 are within each other's coverage.

[0164] As shown in Figure 8, STA1 and STA3 are associated with AP1, and STA2 is associated with AP2. STA1 and STA3 are within each other's coverage area and can communicate directly over the air interface. Assume that AP2 wants to share its TXOP with STA1, using the MU-RTS TXS trigger frame. If STA1 can use this TXOP, it can send a CTS frame to AP1. If STA1 cannot use this TXOP, it cannot send a CTS frame. Possible scenarios include Case 2.1 and Case 2.2.

[0165] In scenario 2.1, STA3 is performing an uplink transmission. To avoid a conflict with STA3's uplink transmission, STA1 cannot properly receive MU-RTS TXS frames from AP2. Alternatively, STA1 can successfully receive MU-RTS TXS frames from AP2, but physical carrier sensing detects a busy channel. In this case, STA1 does not send a CTS frame to AP2, and TXOP sharing initiated by AP2 fails.

[0166] In case 2.2, STA 3 does not transmit. STA 1 receives a MU-RTS TXS frame from AP 2. If STA 1's internal NAV is 0, and all other NAVs except the basic NAV set by AP 2 are 0, and physical carrier sensing detects that the channel is idle, STA 1 can reply with a CTS frame to AP 2.

[0167] As described above, if the second condition is not met, the first AP may fail to share the TXOP with the first STA. To improve the success rate of TXOP sharing, the present application provides the following technical solutions.

[0168] In some embodiments, a first AP may receive TXOP information of the second AP sent by a second AP. The TXOP information may include, for example, one or more of the following: the second AP's channel access status, the end time of the TXOP obtained by the second AP, the duration of the TXOP obtained by the second AP, etc. Based on the TXOP information of the second AP, the first AP may obtain the channel occupancy status within the BSS where the first STA is located, thereby sharing the first AP's TXOP with the first STA at an appropriate time.

[0169] For example, because the second AP is associated with the first STA, the first STA's internal NAV is not zero during the second AP's TXOP duration. Therefore, the first AP may not share the TXOP with the first STA during the second AP's TXOP duration. In other words, the portion of the TXOP shared by the first AP with the first STA is outside the second AP's TXOP duration. This implementation avoids TXOP sharing failures caused by the first STA's internal NAV not being zero.

[0170] Optionally, based on the VBSS and / or virtual association method described above, the second AP may send TXOP information of the second AP to the first AP.

[0171] For example, if an AP within a VBSS obtains a channel access opportunity (e.g., a second AP), it can send its channel access status and TXOP end time to the multi-AP coordinator, which then shares this information with other APs (e.g., the first AP). Taking the scenario shown in Figure 7 as an example, if AP 2 learns the TXOP end time of AP1 through the multi-AP coordinator, then within the TXOP end time of AP1, AP2 may not consider sharing the TXOP obtained by AP2 with STA1 associated with AP1.

[0172] Data transmission

[0173] After the first AP successfully shares a TXOP with the first STA, the first STA can transmit data within the TXOP shared with the first AP. For example, the first STA can send data to the second AP and / or other STAs. Alternatively, after the first AP successfully shares a TXOP with the second AP, the second AP can transmit signals to associated STAs and / or virtually associated STAs within the TXOP shared with the first AP.

[0174] It should be noted that the first STA or the second AP can only transmit data during the time corresponding to the portion of the TXOP shared by the first AP. The first STA or the second AP can only complete data transmission on the channel and bandwidth specified by the first AP.

[0175] The data transmission process is described in detail below through three embodiments in conjunction with FIG. 12 to FIG. 14 .

[0176] Example 1

[0177] Figure 12 is a schematic diagram of the method provided in Example 1. The method shown in Figure 12 can be performed by AP1, AP2, and STA1. AP1, AP2, and STA1 can be corresponding communication devices in the scenarios shown in any of Figures 7-10. The first AP is AP2, the second AP is AP1, and the first STA is STA1.

[0178] The method shown in Example 1 may include steps S1211 to S1230.

[0179] In step S1211, AP2 sends a MU-RTS TXS trigger frame to STA1. In the MU-RTS TXS trigger frame, a value of a triggered TXOP sharing mode subfield is equal to 3.

[0180] The MU-RTS TXS trigger frame can allocate time for STA1. The time allocated by the MU-RTS TXS trigger frame is the portion of the TXOP shared by AP2 with STA1.

[0181] In step S1212, STA1 sends a CTS response to AP2.

[0182] During the time when the MU-RTS TXS triggers frame allocation, STA1 and AP1 may perform steps S1221 to S1224 .

[0183] In step S1221 , STA1 sends an uplink non-trigger based (non-TB) PPDU to AP1 associated with STA1 .

[0184] In step S1222 , in response to step S1221 , AP1 sends a block acknowledgement (BA) frame to STA1 .

[0185] In step S1223 , STA1 sends an uplink non-TB PPDU to AP1 .

[0186] In step S1224 , in response to step S1222 , AP1 sends a BA frame to STA1 .

[0187] Step S1230: After PIFS, within the TXOP acquired by AP2, AP2 can send data to other STAs.

[0188] Optionally, step S1202 may be included before step S1211.

[0189] In step S1202 , AP2 performs CTS (CTS-to-self) transmission directed to itself.

[0190] Example 2

[0191] Figure 13 is a schematic diagram of the method provided in Example 2. Example 2 can be performed by AP1, AP2, STA1, and STA3. AP1, AP2, STA1, and STA3 can be corresponding communication devices in the scenarios shown in any of Figures 7-10. The first AP is AP2, the second AP is AP1, and the first STA is STA1.

[0192] The method shown in Example 2 may include steps S1311-S1340.

[0193] In step S1311, AP2 sends a MU-RTS TXS trigger frame to STA1. In the MU-RTS TXS trigger frame, a value of a triggered TXOP sharing mode subfield is equal to 3.

[0194] The MU-RTS TXS trigger frame can allocate time for STA1. The time allocated by the MU-RTS TXS trigger frame is the portion of the TXOP shared by AP2 with STA1.

[0195] Step S1312: STA1 sends a CTS response to AP2.

[0196] During the time when the MU-RTS TXS triggers frame allocation, STA1 and AP1 may perform steps S1321 to S1332 .

[0197] Step S1321 , STA1 sends a UL non-TB PPDU to AP1 associated with STA1 .

[0198] Step S1322: With respect to step S1321, AP1 sends a BA frame to STA1.

[0199] In step S1331, STA1 sends data to STA3.

[0200] In step S1332 , in response to step S1331 , STA3 sends a BA frame to STA1 .

[0201] Step S1340: After PIFS, within the TXOP acquired by AP2, AP2 can send data to other STAs.

[0202] Optionally, step S1302 may be included before step S1311.

[0203] In step S1302, AP2 performs CTS-to-self transmission.

[0204] Example 3

[0205] FIG14 is a schematic diagram of the method provided in Example 3. Example 3 can be performed by AP1, AP2, and STA1. AP1, AP2, and STA1 can be corresponding communication devices in the scenario shown in FIG8 or FIG10. The first AP is AP2, the second AP is AP1, and the first STA is STA1.

[0206] The method shown in Example 3 may include steps S1411-S1430.

[0207] In step S1411, AP2 sends a MU-RTS TXS trigger frame to AP1. A value of a triggered TXOP sharing mode subfield in the MU-RTS TXS trigger frame is equal to 3.

[0208] The MU-RTS TXS trigger frame can allocate time for AP1. The time allocated by the MU-RTS TXS trigger frame is the portion of the TXOP shared by AP2 with AP1.

[0209] Step S1412: AP1 sends a CTS response to AP2.

[0210] During the time when the MU-RTS TXS triggers frame allocation, STA1 and AP1 may perform steps S1421 to S1432 .

[0211] In step S1421 , AP1 sends a downlink (DL) non-TB PPDU to STA1 associated with AP1 .

[0212] In step S1422 , in response to step S1421 , STA1 sends a BA frame to AP1 .

[0213] In step S1423 , AP1 sends a non-TB PPDU to STA1 .

[0214] Step S1424: For step S1424, STA1 sends a BA frame to AP1.

[0215] Step S1430: After PIFS, within the TXOP acquired by AP2, AP2 can send data to other STAs.

[0216] Optionally, step S1402 may be included before step S1411.

[0217] In step S1402, AP2 performs CTS-to-self transmission.

[0218] It should be noted that, in this application, the first AP and the second AP may belong to the same ESS and have the same SSID.

[0219] It should be noted that most of the above embodiments are described by taking the case where the first AP shares the TXOP with the first STA as an example. It is understandable that these embodiments can also be applied to the case where the first AP shares the TXOP with the second AP.

[0220] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, so for parts not described in detail, reference can be made to the above method embodiments.

[0221] FIG15 is a schematic structural diagram of a communication device 1500 provided in an embodiment of the present application. The communication device 1500 may be a first STA and may include a receiving unit 1510.

[0222] The receiving unit 1510 is used to receive the first field sent by the first AP; wherein the first field is used to carry the first information, and the first information is used to indicate that the first AP shares part of the TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

[0223] In some embodiments, the first AP and the second AP belong to the same VBSS.

[0224] In some embodiments, the receiving unit 1510 is specifically configured to: receive the first field sent by the first AP through the second AP.

[0225] In some embodiments, the first STA is virtually associated with the first AP; wherein, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

[0226] In some embodiments, the receiving unit is specifically configured to: receive the first field sent by the first AP through the AID allocated by the first AP to the first STA.

[0227] In some embodiments, when the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

[0228] In some embodiments, the communication device 1500 is further used to: receive first capability information sent by the first AP; wherein the first capability information is used to indicate whether the first AP can share the TXOP with the first STA.

[0229] In some embodiments, the first capability information is carried in a field in a capability element.

[0230] In some embodiments, the communication device 1500 is further configured to: send second capability information to the first AP; wherein the second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

[0231] In some embodiments, the second capability information is carried in a field in a capability element.

[0232] In some embodiments, the communication device 1500 is further used to: send second information to the first AP; wherein the second information is used to indicate the cache information of the first STA.

[0233] In some embodiments, the first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

[0234] In some embodiments, sending the second information to the first AP includes: sending the second information to the first AP in response to the first STA receiving the first trigger information.

[0235] In some embodiments, the first trigger information is carried in a BSRP frame.

[0236] In some embodiments, the first trigger information is carried in a newly added first type of trigger frame.

[0237] In some embodiments, sending the second information to the first AP includes: sending the second information to the first AP when the first condition is met; wherein the first condition includes one or more of the following: the physical carrier sensing of the first STA does not detect that the channel is busy; the value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

[0238] In some embodiments, the communication device 1500 is further used to: receive third information sent by the first AP; wherein the third information is used to instruct the first AP to start a TXOP sharing process for the first STA.

[0239] In some embodiments, the third information is carried in the second field, and the second field having a first value indicates that the first AP initiates a TXOP sharing process for the first STA.

[0240] In some embodiments, the third information is carried in the MU-RTS TXS trigger frame, and the second field is the triggered TXOP sharing mode subfield.

[0241] In some embodiments, the communication device 1510 is also used to: send response information of the third information to the first AP when the second condition is met; wherein the second condition includes one or more of the following: the physical carrier sensing of the first STA does not detect that the channel is busy; the value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

[0242] In some embodiments, the first AP and the second AP belong to the same ESS.

[0243] In some embodiments, the communication device 1500 is further configured to: send data to the second AP and / or other STAs within a TXOP shared by the first AP.

[0244] In an optional embodiment, the receiving unit 1510 may be a transceiver 1730. The communication device 1500 may further include a processor 1710 and a memory 1720, as specifically shown in FIG17 .

[0245] FIG16 is a schematic structural diagram of a communication device 1600 provided in an embodiment of the present application. The communication device 1600 is a first AP and includes a sending unit 1610.

[0246] The sending unit 1610 is used to send a first field to the first STA; wherein the first field is used to carry the first information, the first information is used to indicate that the first AP shares part of the TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

[0247] In some embodiments, the first AP and the second AP belong to the same VBSS.

[0248] In some embodiments, the sending unit 1610 is specifically configured to send the first field to the first STA through the second AP.

[0249] In some embodiments, the first STA is virtually associated with the first AP; wherein, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

[0250] In some embodiments, the sending unit 1610 is specifically configured to send the first field to the first STA through the AID allocated by the first AP to the first STA.

[0251] In some embodiments, when the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

[0252] In some embodiments, the communication device 1600 is further configured to: send first capability information to the first STA; wherein the first capability information is used to indicate whether the first AP can share a TXOP with the first STA.

[0253] In some embodiments, the first capability information is carried in a field in a capability element.

[0254] In some embodiments, the communication device 1600 is further used to: receive second capability information sent by the first STA; wherein the second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

[0255] In some embodiments, the second capability information is carried in a field in a capability element.

[0256] In some embodiments, the communication device 1600 is further used to: receive second information sent by the first STA; wherein the second information is used to indicate the cache information of the first STA.

[0257] In some embodiments, the first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

[0258] In some embodiments, receiving the second information includes: receiving the second information in response to the first AP sending the first trigger information.

[0259] In some embodiments, the first trigger information is carried in a BSRP frame.

[0260] In some embodiments, the first trigger information is carried in a newly added first type of trigger frame.

[0261] In some embodiments, receiving the second information sent by the first STA includes: receiving the second information sent by the first STA when a first condition is met; wherein the first condition includes one or more of the following: the physical carrier sensing of the first STA does not detect that the channel is busy; the value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

[0262] In some embodiments, the communication device 1600 is further configured to: send third information to the first STA; wherein the third information is used to instruct the first AP to initiate a TXOP sharing process for the first STA.

[0263] In some embodiments, the third information is carried in the second field, and the second field having a first value indicates that the first AP initiates a TXOP sharing process for the first STA.

[0264] In some embodiments, the third information is carried in the MU-RTS TXS trigger frame, and the second field is the triggered TXOP sharing mode subfield.

[0265] In some embodiments, the communication device 1600 is also used to: receive response information of the third information when the second condition is met; wherein the second condition includes one or more of the following: the physical carrier sensing of the first STA does not detect that the channel is busy; the value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

[0266] In some embodiments, the communication device 1600 is further configured to: receive TXOP information of a second AP sent by the second AP.

[0267] In some embodiments, the first AP and the second AP belong to the same VBSS, and the TXOP information of the second AP is transmitted through a multi-AP coordinator in the VBSS.

[0268] In some embodiments, the TXOP shared by the first AP to the first STA is outside the duration of the TXOP of the second AP.

[0269] In some embodiments, the first AP and the second AP belong to the same ESS.

[0270] In an optional embodiment, the sending unit 1610 may be a transceiver 1730. The communication device 1600 may further include a processor 1710 and a memory 1720, as specifically shown in FIG17 .

[0271] Figure 17 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 17 indicate that the unit or module is optional. Device 1700 can be used to implement the method described in the above method embodiment. Device 1700 can be a chip or a communication device.

[0272] The device 1700 may include one or more processors 1710. The processor 1710 may support the device 1700 to implement the method described in the method embodiment above. The processor 1710 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0273] The apparatus 1700 may further include one or more memories 1720. The memories 1720 store programs that can be executed by the processor 1710, causing the processor 1710 to perform the methods described in the above method embodiments. The memories 1720 may be independent of the processor 1710 or integrated into the processor 1710.

[0274] The apparatus 1700 may further include a transceiver 1730. The processor 1710 may communicate with other devices or chips via the transceiver 1730. For example, the processor 1710 may transmit and receive data with other devices or chips via the transceiver 1730.

[0275] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0276] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0277] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0278] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0279] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0280] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0281] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0282] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0283] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0284] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0285] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0286] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include a WiFi protocol and related protocols used in future WiFi communication systems, and the present application does not limit this.

[0287] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0289] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0290] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0291] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The first station STA receives the first field sent by the first access point AP; The first field is used to carry first information, and the first information is used to instruct the first AP to share part of the transmission opportunities TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

2. The method according to claim 1, characterized in that The first AP and the second AP belong to the same virtual basic service set VBSS.

3. The method according to claim 2, characterized in that The first STA receiving a first field sent by the first AP includes: The first STA receives the first field sent by the first AP through the second AP.

4. The method according to any one of claims 1 to 3, characterized in that The first STA is virtually associated with the first AP; In which, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

5. The method according to claim 4, characterized in that The first STA receiving a first field sent by the first AP includes: The first STA receives the first field sent by the first AP through the AID allocated by the first AP to the first STA.

6. The method according to any one of claims 1 to 5, characterized in that When the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first STA receives first capability information sent by the first AP; The first capability information is used to indicate whether the first AP can share the TXOP with the first STA.

8. The method according to claim 7, characterized in that The first capability information is carried in a field in a capability element.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The first STA sends second capability information to the first AP; The second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

10. The method according to claim 9, characterized in that The second capability information is carried in a field in a capability element.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: The first STA sends second information to the first AP; The second information is used to indicate the cache information of the first STA.

12. The method according to claim 11, characterized in that The first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

13. The method according to claim 11 or 12, characterized in that: The first STA sends second information to the first AP, including: In response to the first STA receiving the first trigger information, the first STA sends second information to the first AP.

14. The method according to claim 13, characterized in that The first trigger information is carried in a buffer status report polling BSRP frame.

15. The method according to claim 13, characterized in that The first trigger information is carried in a newly added first type of trigger frame.

16. The method according to any one of claims 11 to 15, characterized in that The first STA sends second information to the first AP, including: When the first condition is met, the first STA sends second information to the first AP; The first condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

17. The method according to any one of claims 1 to 16, characterized in that The method further comprises: The first STA receives third information sent by the first AP; The third information is used to instruct the first AP to start a TXOP sharing process for the first STA.

18. The method according to claim 17, characterized in that The third information is carried in the second field, and the second field is a first value indicating that the first AP starts a TXOP sharing process for the first STA.

19. The method according to claim 18, characterized in that The third information is carried in a multi-user request to send transmission opportunity sharing MU-RTS TXS trigger frame, and the second field is a triggered TXOP sharing mode subfield.

20. The method according to any one of claims 17 to 19, characterized in that The method further comprises: When the second condition is met, the first STA sends response information of the third information to the first AP; The second condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

21. The method according to any one of claims 1 to 20, characterized in that The first AP and the second AP belong to the same extended service set ESS.

22. The method according to any one of claims 1 to 21, characterized in that The method further comprises: In a TXOP shared by the first AP, the first STA sends data to the second AP and / or other STAs.

23. A wireless communication method, characterized in that: include: The first access point AP sends a first field to the first station STA; The first field is used to carry first information, and the first information is used to instruct the first AP to share part of the transmission opportunities TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

24. The method according to claim 23, characterized in that The first AP and the second AP belong to the same virtual basic service set VBSS.

25. The method according to claim 24, characterized in that The first AP sends first information to the first STA, including: The first AP sends the first field to the first STA through the second AP.

26. The method according to any one of claims 23 to 25, characterized in that The first STA is virtually associated with the first AP; In which, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

27. The method according to claim 26, characterized in that The first AP sends first information to the first STA, including: The first AP sends the first field to the first STA through the AID allocated by the first AP to the first STA.

28. The method according to any one of claims 23 to 27, characterized in that When the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

29. The method according to any one of claims 23 to 28, characterized in that The method further comprises: The first AP sends first capability information to the first STA; The first capability information is used to indicate whether the first AP can share the TXOP with the first STA.

30. The method according to claim 29, characterized in that The first capability information is carried in a field in a capability element.

31. The method according to any one of claims 23 to 30, characterized in that The method further comprises: The first AP receives second capability information sent by the first STA; The second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

32. The method according to claim 31, characterized in that The second capability information is carried in a field in a capability element.

33. The method according to any one of claims 23 to 32, characterized in that The method further comprises: The first AP receives second information sent by the first STA; The second information is used to indicate the cache information of the first STA.

34. The method according to claim 33, characterized in that The first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

35. The method according to claim 33 or 34, characterized in that The first AP receiving the second information includes: In response to the first AP sending the first trigger information, the first AP receives the second information.

36. The method according to claim 35, characterized in that The first trigger information is carried in a buffer status report polling BSRP frame.

37. The method according to claim 35, characterized in that The first trigger information is carried in a newly added first type of trigger frame.

38. The method according to any one of claims 33 to 37, characterized in that The first AP receiving the second information sent by the first STA includes: When the first condition is met, the first AP receives the second information sent by the first STA; The first condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

39. The method according to any one of claims 23 to 38, characterized in that The method further comprises: The first AP sends third information to the first STA; The third information is used to instruct the first AP to start a TXOP sharing process for the first STA.

40. The method according to claim 39, characterized in that The third information is carried in the second field, and the second field is a first value indicating that the first AP starts a TXOP sharing process for the first STA.

41. The method according to claim 40, characterized in that The third information is carried in a multi-user request to send transmission opportunity sharing MU-RTS TXS trigger frame, and the second field is a triggered TXOP sharing mode subfield.

42. The method according to any one of claims 39 to 41, characterized in that The method further comprises: When the second condition is met, the first AP receives response information of the third information; The second condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

43. The method according to any one of claims 39 to 42, characterized in that The method further comprises: The first AP receives TXOP information of the second AP sent by the second AP.

44. The method according to claim 43, characterized in that The first AP and the second AP belong to the same VBSS, and the TXOP information of the second AP is transmitted through a multi-AP coordinator in the VBSS.

45. The method according to claim 43 or 44, characterized in that The TXOP shared by the first AP with the first STA is outside the duration of the TXOP of the second AP.

46. ​​The method according to any one of claims 23 to 45, characterized in that The first AP and the second AP belong to the same extended service set ESS.

47. A communication device, characterized in that: The communication device is a first station STA, and the communication device includes: A receiving unit, configured to receive a first field sent by a first access point AP; The first field is used to carry first information, and the first information is used to instruct the first AP to share part of the transmission opportunities TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

48. The communication device according to claim 47, characterized in that The first AP and the second AP belong to the same virtual basic service set VBSS.

49. The communication device according to claim 48, characterized in that The receiving unit is specifically used for: The first field sent by the first AP is received through the second AP.

50. The communication device according to any one of claims 47 to 49, characterized in that: The first STA is virtually associated with the first AP; In which, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

51. The communication device according to claim 50, characterized in that The receiving unit is specifically used for: The first field sent by the first AP is received through the AID allocated by the first AP to the first STA.

52. The communication device according to any one of claims 47 to 51, characterized in that: When the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

53. The communication device according to any one of claims 47 to 52, characterized in that: The communication device is also used for: Receiving first capability information sent by the first AP; The first capability information is used to indicate whether the first AP can share the TXOP with the first STA.

54. The communication device according to claim 53, characterized in that The first capability information is carried in a field in a capability element.

55. The communication device according to any one of claims 47 to 54, characterized in that: The communication device is also used for: Sending second capability information to the first AP; The second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

56. The communication device according to claim 55, characterized in that The second capability information is carried in a field in a capability element.

57. The communication device according to any one of claims 47 to 56, characterized in that: The communication device is also used for: Sending second information to the first AP; The second information is used to indicate the cache information of the first STA.

58. The communication device according to claim 57, characterized in that The first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

59. The communication device according to claim 57 or 58, characterized in that The sending the second information to the first AP includes: In response to the first STA receiving the first trigger information, second information is sent to the first AP.

60. The communication device according to claim 59, characterized in that The first trigger information is carried in a buffer status report polling BSRP frame.

61. The communication device according to claim 59, characterized in that The first trigger information is carried in a newly added first type of trigger frame.

62. The communication device according to any one of claims 57 to 61, characterized in that: The sending the second information to the first AP includes: When the first condition is met, sending second information to the first AP; The first condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

63. The communication device according to any one of claims 47 to 62, characterized in that: The communication device is also used for: receiving third information sent by the first AP; The third information is used to instruct the first AP to start a TXOP sharing process for the first STA.

64. The communication device according to claim 63, characterized in that The third information is carried in the second field, and the second field is a first value indicating that the first AP starts a TXOP sharing process for the first STA.

65. The communication device according to claim 64, characterized in that The third information is carried in a multi-user request to send transmission opportunity sharing MU-RTS TXS trigger frame, and the second field is a triggered TXOP sharing mode subfield.

66. The communication device according to any one of claims 63 to 65, characterized in that: The communication device is also used for: When the second condition is met, sending response information of the third information to the first AP; The second condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

67. The communication device according to any one of claims 47 to 66, characterized in that: The first AP and the second AP belong to the same extended service set ESS.

68. The communication device according to any one of claims 47 to 67, characterized in that: The communication device is also used for: In a TXOP shared by the first AP, data is sent to the second AP and / or other STAs.

69. A communication device, characterized in that: The communication device is a first access point AP, and the communication device includes: A sending unit, configured to send a first field to a first station STA; The first field is used to carry first information, and the first information is used to instruct the first AP to share part of the transmission opportunities TXOP obtained by the first AP with the first STA, the first STA is associated with the second AP, and the first STA is within the coverage range of the signal sent by the first AP.

70. The communication device according to claim 69, characterized in that The first AP and the second AP belong to the same virtual basic service set VBSS.

71. The communication device according to claim 70, characterized in that The sending unit is specifically used for: The first field is sent to the first STA through the second AP.

72. The communication device according to any one of claims 69 to 71, characterized in that: The first STA is virtually associated with the first AP; In which, when the first STA is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the first STA, but data cannot be transmitted between the first AP and the first STA.

73. The communication device according to claim 72, characterized in that The sending unit is specifically used for: The first field is sent to the first STA through the AID allocated by the first AP to the first STA.

74. The communication device according to any one of claims 69 to 73, characterized in that: When the second AP is within the coverage range of the signal sent by the first AP and the first AP is within the coverage range of the signal sent by the second AP, the second AP is virtually associated with the first AP. When the second AP is virtually associated with the first AP, control information and / or management information can be transmitted between the first AP and the second AP, but data cannot be transmitted between the first AP and the second AP.

75. The communication device according to any one of claims 69 to 74, characterized in that: The communication device is also used for: Sending first capability information to the first STA; wherein the first capability information is used to indicate whether the first AP can share a TXOP with the first STA.

76. The communication device according to claim 75, characterized in that The first capability information is carried in a field in a capability element.

77. The communication device according to any one of claims 69 to 76, characterized in that: The communication device is also used for: receiving second capability information sent by the first STA; The second capability information is used to indicate whether the first STA can use the TXOP shared by the first AP.

78. The communication device according to claim 77, characterized in that The second capability information is carried in a field in a capability element.

79. The communication device according to any one of claims 69 to 78, characterized in that: The communication device is also used for: receiving second information sent by the first STA; The second information is used to indicate the cache information of the first STA.

80. The communication device according to claim 79, characterized in that The first AP and the second AP belong to the same VBSS; the first STA sends the second information to the first AP through the second AP.

81. The communication device according to claim 79 or 80, characterized in that: The receiving the second information comprises: In response to the first AP sending the first trigger information, the second information is received.

82. The communication device according to claim 81, characterized in that The first trigger information is carried in a buffer status report polling BSRP frame.

83. The communication device according to claim 81, characterized in that The first trigger information is carried in a newly added first type of trigger frame.

84. The communication device according to any one of claims 79 to 83, characterized in that: The receiving the second information sent by the first STA includes: When the first condition is met, receiving the second information sent by the first STA; The first condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

85. The communication device according to any one of claims 69 to 84, characterized in that: The communication device is also used for: Sending third information to the first STA; The third information is used to instruct the first AP to start a TXOP sharing process for the first STA.

86. The communication device according to claim 85, characterized in that The third information is carried in the second field, and the second field is a first value indicating that the first AP starts a TXOP sharing process for the first STA.

87. The communication device according to claim 86, characterized in that The third information is carried in a multi-user request to send transmission opportunity sharing MU-RTS TXS trigger frame, and the second field is a triggered TXOP sharing mode subfield.

88. The communication device according to any one of claims 85-87, characterized in that: The communication device is also used for: When the second condition is met, receiving response information of the third information; The second condition includes one or more of the following: The physical carrier sensing of the first STA does not detect that the channel is busy; The value of the internal network allocation vector of the first STA is 0, and the basic network allocation vectors of the first STA set by devices other than the first AP are all 0.

89. The communication device according to any one of claims 85-88, characterized in that The communication device is also used for: Receive TXOP information of the second AP sent by the second AP.

90. The communication device according to claim 89, characterized in that The first AP and the second AP belong to the same VBSS, and the TXOP information of the second AP is transmitted through a multi-AP coordinator in the VBSS.

91. The communication device according to claim 89 or 90, characterized in that: The TXOP shared by the first AP with the first STA is outside the duration of the TXOP of the second AP.

92. The communication device according to any one of claims 69 to 91, characterized in that: The first AP and the second AP belong to the same extended service set ESS.

93. A communication device, characterized in that: It comprises a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1-46.

94. A device, characterized in that It comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-46.

95. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 46.

96. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 46.

97. A computer program product, characterized in that A program is included, which causes a computer to execute the method as claimed in any one of claims 1 to 46.

98. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 46.

Images