Wireless communication method, and communication device

Abstract

Provided are a wireless communication method, and a communication device. The method comprises: a first station sending a first frame to a second station, wherein the first frame comprises first information, the first information being used for instructing the second station to performing transmission by means of using transmission resources which are held by the first station and are shared to the second station, and the first station is a non-access-point station.

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] During the communication process, how stations (STAs) and access points (APs) should flexibly schedule transmission resources to cope with sudden low-latency traffic is a problem that needs to be solved.

[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, including: a first station sends a first frame to a second station, the first frame includes first information, and the first information is used to indicate that the second station shares the transmission resources held by the first station for transmission.

[0006] In a second aspect, a wireless communication method is provided, including: a second station receives a first frame sent by a first station, the first frame includes first information, and the first information is used to indicate that the second station shares the transmission resources held by the first station for transmission.

[0007] According to a third aspect, a communication device is provided, which is a first site, and includes: a communication module for sending a first frame to a second site, wherein the first frame includes first information, and the first information is used to indicate that the second site shares the transmission resources held by the first site for transmission.

[0008] In a fourth aspect, a communication device is provided, which is a second site, and includes: a communication module for receiving a first frame sent by a first site, the first frame containing first information, and the first information is used to indicate that the second site shares the transmission resources held by the first site for transmission.

[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] In the embodiment of the present application, when a non-AP STA holds transmission resources, it can authorize the AP to use the transmission resources, thereby achieving flexible scheduling of transmission resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a wireless communication system to which an embodiment of the present application may be applied.

[0016] FIG2 is an example diagram of the transmission resource preemption process.

[0017] FIG. 3 is a diagram illustrating an example of a transmission opportunity (TXOP) sharing method.

[0018] FIG4 is a diagram illustrating an example of a reverse direction (RD) transmission process.

[0019] FIG5 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0020] FIG6 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0021] FIG7 is an example diagram of a control field provided in an embodiment of the present application.

[0022] FIG8 is an example diagram of an Extended TXOP Sharing (ETS) field provided in an embodiment of the present application.

[0023] FIG. 9 is an example diagram of the Extended TXOP Sharing Info subfield in FIG. 8 .

[0024] FIG. 10 is an example diagram of the target user information (Target User Info) subfield in FIG. 8 .

[0025] FIG11 is a diagram showing an example structure of a control frame provided in an embodiment of the present application.

[0026] FIG12 is an example diagram of the Frame Control field in FIG11 .

[0027] FIG13 is a schematic diagram of an extremely high throughput media access control (EHT MAC) capability information field provided by an embodiment of the present application.

[0028] FIG14 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0029] FIG15 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0030] FIG16 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0031] FIG17 is a flow chart of a wireless communication method according to an embodiment of the present application.

[0032] FIG18 is an operation flow chart of a restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0033] FIG19 is an operation flow chart of a restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0034] FIG20 is an operation flow chart of the restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0035] FIG21 is an operation flow chart of the restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0036] Figure 22 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0037] Figure 23 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0038] Figure 24 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0039] Figure 25 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0040] Figure 26 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0041] Figure 27 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0042] Figure 28 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0043] Figure 29 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0044] FIG30 is an operation flow chart of the non-restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0045] FIG31 is an operation flow chart of the non-restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0046] FIG32 is an operation flow chart of the non-restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0047] FIG33 is an operation flow chart of the non-restricted extended TXOP sharing mode provided in an embodiment of the present application.

[0048] Figure 34 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0049] Figure 35 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0050] Figure 36 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0051] Figure 37 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0052] Figure 38 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0053] Figure 39 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0054] Figure 40 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0055] Figure 41 is a flow chart of the wireless communication method provided in an embodiment of the present application.

[0056] Figure 42 is an example diagram of the command and status (CAS) control field provided in an embodiment of the present application.

[0057] FIG43 is an example diagram of the high throughput extended capabilities (HT Extended Capabilities) field provided in an embodiment of the present application.

[0058] Figure 44 is an example diagram of the High Efficiency 6GHz Capabilities field provided in an embodiment of the present application.

[0059] Figure 45 is a flow chart of the wireless communication method provided in an embodiment of the present application.

[0060] Figure 46 is a flow chart of the wireless communication method provided in an embodiment of the present application.

[0061] Figure 47 is an operational flow chart of extended RD transmission provided in an embodiment of the present application.

[0062] Figure 48 is an operational flow chart of extended RD transmission provided in an embodiment of the present application.

[0063] Figure 49 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0064] Figure 50 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0065] Figure 51 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0066] Figure 52 is an example diagram of a communication scenario provided in an embodiment of the present application.

[0067] Figure 53 is a structural diagram of the communication device provided in an embodiment of the present application.

[0068] Figure 54 is a structural diagram of the communication device provided in an embodiment of the present application.

[0069] Figure 55 is a structural schematic diagram of a device to which an embodiment of the present application can be applied. DETAILED DESCRIPTION

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

[0071] Communication System

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

[0073] 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 (STA) 120 accessing a network through the access point (AP) 110.

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

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

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

[0077] 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).

[0078] It should be understood that the roles of various communication devices in the communication system 100 are not absolute. Taking a mobile phone as an example, when the 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 plays the role of an AP.

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

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

[0081] There are one or more links between the STA and the AP. In some embodiments, the STA and the AP support multi-band communication. For example, the STA and the AP can communicate simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz frequency bands, or communicate simultaneously on different channels in the same frequency band (or different frequency bands) to improve 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. The multi-link device can be an access point device or a site device. If the multi-link device is an access point device, the multi-link device can include one or more APs; if the multi-link device is a site device, the multi-link device can include one or more non-AP STAs.

[0082] 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).

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

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

[0085] 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).

[0086] FIG1 exemplarily illustrates an AP and two STAs. Optionally, the communication system 100 may include multiple APs and any other number of STAs, which is not limited in this embodiment of the present application. In FIG1 , the AP, STA 120a, and STA 120b may be located in the same basic service set (BSS). The AP may be associated with STA 120a. The AP may be associated with STA 120b.

[0087] It should be understood that in the embodiments of the present application, a device with 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 AP 110 and a STA 120 with communication functionality. In addition, the communication device mentioned in the embodiments of the present application may also include other devices in the communication system 100, such as a network controller, a gateway, and other network entities (not shown in FIG1 ), which is not limited in the embodiments of the present application.

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

[0089] 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).

[0090] With the rise of extended reality (XR) devices, the demand for bursty low-latency traffic is increasing. For bursty low-latency traffic in the uplink (UL) or downlink (DL), related services need to obtain transmission resources as quickly as possible to complete data transmission. Assuming that the current transmission resource holder is a non-AP STA, if the AP or other non-AP STAs in the same BSS generate bursty low-latency traffic, these devices may not be able to obtain transmission resources in a timely manner, resulting in a significant latency impact on the bursty low-latency traffic service. To address this issue, the following describes some solutions provided by related technologies.

[0091] TXOP preemption

[0092] The proposal "11 23 1229 01 0uhr preemption for low latency application follow-up" proposes a solution for transmitting bursty low-latency traffic based on TXOP preemption. This solution limits the maximum length of large physical layer protocol data units (PPDUs) and sets the transmission interval to an indeterminate interframe space (xIFS), where xIFS is greater than the short interframe space (SIFS). This provides preemption opportunities for senders of low-latency traffic. This solution uses the first control frame of the TXOP or the function field of the current PPDU to indicate whether the next time slot can be preempted. The sender of low-latency traffic can send a common preemption request (PR) within the preemption-allowed interval. After receiving the PR, the AP can initiate low-latency traffic data packet transmission. The specific communication process is shown in Figure 2.

[0093] The proposal has the following limitations:

[0094] First: Changing the data transmission time slot to xIFS will bring additional time overhead for transmission;

[0095] Second, the PR sent by STAs is essentially an interference signal, which may be suspected of malicious competition.

[0096] Third: STA's preemptive behavior encroaches on the transmission opportunity of the original TXOP holder, which is not conducive to the fairness of transmission.

[0097] UL TXOP Sharing

[0098] Traditional TXOP sharing mainly involves sharing the TXOP held by the AP with STAs, that is, performing DL TXOP sharing.

[0099] The proposal, "11 23 1620 00 0uhr reverse txop sharing for uhr," discusses the benefits of UL TXOP sharing for non-AP STAs. The proposal states that, based on UL TXOP sharing, non-AP STAs can assist APs with network management, provide a more comprehensive uplink and downlink transmission switching mechanism, and offer more preemptive methods for low-latency traffic. However, the proposal does not provide specific operational methods.

[0100] The proposal "11 23 1387 01 0uhr txop sharing extensions for xr use cases" provides an application scenario for sharing the TXOP of a non-AP STA. In an AR scenario, the AP can be connected to a head-mounted device and a sensor device at the same time. In addition to transmitting data with the AP, the head-mounted device also needs to be concerned with data interaction between the sensor device and the AP. This proposal proposes a new type of TXOP control signal to complete the conversion operation between transmission resources. The specific communication process is shown in Figure 3. This proposal designs a solution for XR devices to share TXOP with the AP in a specific scenario. However, this proposal is only applicable to scenarios that include head-mounted devices and sensor devices and is not applicable to other application scenarios.

[0101] RD transmission

[0102] In the current 802.11 standard, based on the RD transmission protocol, a STA that holds a TXOP (RD initiator) can grant the remaining time within the TXOP to other STAs (RD responders) for RD transmission. The transmission resources used for subsequent RD transmissions can be used as a continuation of the current TXOP, reducing channel contention during transmission. Figure 4 shows an example of the RD transmission process.

[0103] The current RD transmission protocol has significant application limitations. For example, the RD transmission process must include an RD initiator. Another example is that the AP does not obtain full TXOP transmission rights within the RD transmission sequence. These issues mean that in practical applications, the current RD protocol is not flexible enough and does not effectively utilize transmission resources.

[0104] In response to one or more of the above problems, the embodiments of the present application are described in detail below. It should be understood that the application scenarios of the embodiments of the present application include but are not limited to single BSS scenarios, overlapping basic service sets (OBSS) scenarios, and virtual basic service sets (VBSS) scenarios.

[0105] In an embodiment of the present application, a STA (such as a non-AP STA) may authorize the AP to use part or all of the transmission resources it holds. The transmission resources mentioned here may refer to a TXOP, such as the TXOP held by the STA. It should be noted that in each embodiment of the present application, transmission resources and TXOP can be used interchangeably. After obtaining the TXOP held by the STA, the AP can better perform network management and service scheduling. For example, based on the TXOP, the AP can perform one or more operations including uplink data transmission, downlink data transmission, rapid conversion of uplink data and downlink data transmission, multi-user data transmission, BSS internal device management (such as collaborative transmission of multiple non-AP STAs under the BSS), and emergency scheduling of bursty low-latency traffic.

[0106] For ease of description, the STA holding the TXOP (such as a non-AP STA) will be referred to as the first STA hereinafter. Referring to Figure 5 , the first STA may send a first frame to the first AP (step S510). The first frame may include first information. The first information is used to instruct (or authorize) the second STA (the second STA may be, for example, an AP, and the following text will mainly use the second station as the first AP as an example for explanation. In the absence of conflict, the first AP in the following text may be replaced by the second station) to use or share the TXOP held by the first station for transmission. The first STA and the first AP may be located in the same BSS and associated with the first AP. The first STA may authorize the TXOP it holds to the first AP for use. The first STA may instruct the first AP to use the duration of the TXOP. The duration may be indicated, for example, by the Duration / ID field of the first frame.

[0107] There are various ways for a first STA to share or authorize its TXOP with the first AP. For example, the first STA can share or authorize its TXOP with the first AP through a first sharing operation. Another example is that the first STA can share or authorize its TXOP with the first AP through a first reverse transmission operation. The following describes these two TXOP authorization methods in detail, using examples 1 and 2.

[0108] Example 1: First sharing operation

[0109] A TXOP sharing operation exists in the related art. This sharing operation only supports an AP sharing its TXOP with a STA. Unlike this sharing operation, the first sharing operation provided in Example 1 supports a first STA sharing its TXOP with a first AP. This first sharing operation can be considered an extension of the sharing operation provided in the related art and, therefore, can also be referred to as an "extended TXOP sharing operation." It should be noted that in Example 1, "first sharing operation," "extended transmission resource sharing operation," and "extended TXOP sharing operation" are used interchangeably.

[0110] Based on the extended TXOP sharing operation, the first AP can obtain the transmission resources held by the first STA, and thus can perform data transmission based on the transmission resources. Taking the scenario shown in Figure 1 as an example, assuming that the first STA is STA 120a in Figure 1, the first AP is AP 110 in Figure 1, and STA 120a holds a TXOP, then after AP 110 obtains the TXOP held by STA 120a, it can perform DL data transmission, UL data transmission, downlink multi-user (DL MU) data transmission, and uplink multi-user (UL MU) data transmission with STA 120a and / or STA 120b based on the TXOP. The introduction of the extended TXOP sharing operation helps the first AP complete the scheduling operation of bursty low-latency traffic more promptly and strengthens resource management in the BSS network.

[0111] The extended TXOP sharing operation can be initiated by the first STA or requested by the first AP. If the extended TXOP sharing operation is requested by the first AP, the first AP can first send a first request to the first STA to request the extended TXOP sharing operation (or request the TXOP held by the first STA). After receiving the first request, the first STA can initiate the extended TXOP sharing operation, thereby providing the first AP with a transmission resource, so that the first AP can transmit data based on the transmission resource.

[0112] In some implementations, the extended TXOP sharing operation may include a first sharing mode. In the first sharing mode, the first STA does not restrict the first AP's use of the transmission resources held by the first STA. Therefore, the first sharing mode may also be referred to as an unrestricted transmission resource sharing mode. For example, when the first STA holding the TXOP provides a period of transmission resources to the first AP, if the first STA does not have any data transmission requirements for the first AP within the shared TXOP time, the unrestricted transmission resource sharing mode may be used; when the first STA uses the unrestricted transmission resource sharing mode, the first STA does not set any requirements for the first AP's subsequent data transmission.

[0113] In some implementations, the extended TXOP sharing operation may include a second sharing mode. In the second sharing mode, the first STA restricts the way the first AP uses the transmission resources held by the first STA. Therefore, the second sharing mode may also be referred to as a restricted transmission resource sharing mode. For example, when the first STA holding a TXOP shares transmission resources with the first AP, if the first STA wishes to make transmission requirements for the data transmission of the first AP within the shared TXOP, the restricted transmission resource sharing mode may be used to constrain and control the data interaction method of the first AP in the shared TXOP. In the restricted transmission resource sharing mode, the first AP needs to comply with the transmission requirements proposed by the first STA to ensure that the first AP can complete the data transmission as expected by the first STA.

[0114] For example, in a restricted transmission resource sharing mode, the first STA can restrict the communication devices that participate in the target transmission (target transmission refers to the transmission performed by the first AP based on the transmission resources held by the first STA). Exemplarily, the first STA can indicate the target communication devices that participate in the target transmission through an association identity (AID). In other words, the first STA can indicate the AID of the target transmission device to the first AP, and accordingly, when the first AP performs the target transmission, the target transmission needs to include the communication devices corresponding to the AID.

[0115] For another example, in a restricted transmission resource sharing mode, the first STA may limit the communication bandwidth corresponding to the target transmission. The communication bandwidth corresponding to the target transmission may include: the average bandwidth used by the target transmission, the minimum bandwidth used by the target transmission, and / or the maximum bandwidth used by the target transmission.

[0116] For example, in a restricted transmission resource sharing mode, the first STA can simultaneously limit the target communication devices participating in the target transmission and the corresponding communication bandwidth of the target transmission. For example, the first STA can specify that the target transmission needs to cover the communication device corresponding to a certain AID and specify the minimum communication bandwidth used by the communication device corresponding to the AID.

[0117] For another example, in a restricted transmission resource sharing mode, the first STA may restrict the data category corresponding to the target transmission. For example, the first STA may indicate the data category that the target transmission needs to transmit through an access category (AC).

[0118] For example, in a restricted transmission resource sharing mode, the first STA can restrict both the target communication devices participating in the target transmission and the corresponding data categories. For example, the first STA can specify that the target transmission needs to cover the communication device corresponding to a certain AID and specify the data categories that need to be transmitted when communicating with the communication device corresponding to the AID.

[0119] The following provides a more specific example of the implementation of the first embodiment from the perspective of communication frame design and information interaction.

[0120] 6 , a first STA sends a first frame to a first AP (step S610 ). The first frame includes first information. The first information includes information related to the extended TXOP sharing operation.

[0121] The first information may be carried in a first field in the first frame. Hereinafter, this first field is referred to as the Extend TXOP Sharing field. When performing an extended TXOP sharing operation, the first STA may use the Extend TXOP Sharing field to manage the extended TXOP sharing operation. The Extend TXOP Sharing field may be a control field (such as the Control subfield in the HT Control field) or another type of field.

[0122] As an example, a new type of Control subfield can be added to the high efficiency variant high throughput control (HE variant HT Control) field. The Control ID of the Control subfield can be set to 10, for example. Figure 7 shows an example of the format of the Control subfield. As shown in Figure 7, in addition to the Control ID, the Control subfield can also include control information (Control Information). Table 1 below shows the control information represented by each Control ID of the Control subfield and the length of the control information. As shown in Table 1, the field corresponding to when the Control ID is 10 is the Extend TXOP Sharing field newly added in the embodiment of the present application.

[0123] Table 1 Control subfields provided in the embodiment of the present application

[0124] In some implementations, the first information mentioned above may include second information. The second information may be used to indicate a sharing mode of transmission resources. The sharing mode of transmission resources may include the unrestricted transmission resource sharing mode (referred to as the unrestricted sharing mode) and / or the restricted transmission resource sharing mode (referred to as the restricted sharing mode) mentioned above. For example, the value of the second information may include a first value (such as 1) and a second value (such as 0). If the value of the second information is the first value, it indicates that the sharing mode of the transmission resource that is about to be or is in progress is an unrestricted sharing mode. If the value of the second information is the second value, it indicates that the sharing mode of the transmission resource that is about to be or is in progress is a restricted sharing mode.

[0125] In some implementations, the first information mentioned above may include third information. The third information is used to limit the way the first AP uses the transmission resources. It should be understood that the first information may include the second information and the third information at the same time. If the second information indicates that the sharing mode of the transmission resources is a restricted sharing mode, the first information may include the third information. Of course, the embodiments of the present application are not limited to this. For example, the first information may also include the third information but not the second information. In this case, it can be determined based on the value of the third information whether the first STA has restricted the way the transmission resources are used, thereby determining whether the current sharing mode is an unrestricted sharing mode or a restricted sharing mode.

[0126] Furthermore, in some implementations, the third information is used to limit one or more of the following: communication devices participating in the target transmission (target transmission refers to transmission performed by the first AP based on the transmission resource), the communication bandwidth corresponding to the target transmission, and the data category corresponding to the target transmission. The meaning of the third information is described above and is not further elaborated here.

[0127] In some implementations, the first information includes fourth information. The fourth information is used to indicate that the first STA accepts (or agrees to) the first request initiated by the first AP. The first request is used to request an extended TXOP sharing operation. That is, in this implementation, the initialization behavior of the extended TXOP sharing operation is: the first AP initiates the request. For example, when the first AP has a transmission resource requirement, it can proactively initiate the first request to the first STA, and the first STA will agree or reject the sharing request based on its own circumstances.

[0128] In some implementations, the first information includes fifth information. The fifth information is used to instruct the first STA to share transmission resources with (or proactively share transmission resources with) the first AP. In other words, in this implementation, the initialization of the extended TXOP sharing operation is: the first STA proactively initiates sharing. For example, when the first STA wishes to transmit data between the first AP and a second STA, it can proactively share its own transmission resources with the first AP, allowing the first AP to complete the data transmission as expected.

[0129] 8 to 10 , the specific format and content of the extended TXOP sharing field will be described below by taking the case where the first information is carried in the extended TXOP sharing field as an example.

[0130] Figure 8 shows the specific format of the Extended TXOP Sharing field (used to carry the first information). As can be seen from Figure 8, the Extended TXOP Sharing field can include an Extended TXOP Sharing Information (Extend TXOP Sharing Info) subfield and a Target User Info (Target User Info) subfield. Figure 9 shows the specific format of the Extended TXOP Sharing Info subfield. As can be seen from Figure 9, the Extended TXOP Sharing Info subfield can further include one or more of the following subfields: Extended TXOP Sharing Mode, Extended TXOP Sharing Grant / Receive. The bits other than these are reserved bits of the Extended TXOP Sharing Info subfield. Extended TXOP Sharing Mode can be used to carry the second information mentioned above. The Target User Info subfield can be used to carry the third information mentioned above. Figure 10 shows the specific format of the Target User Info subfield. As shown in Figure 10, the Target User Info subfield can further include one or more of the following subfields: AID12, RU Allocation, and AC Constraint. AID12, RU Allocation, and AC Constraint can be used to restrict the target communication device participating in the target transmission, the communication bandwidth corresponding to the target transmission, and the data category corresponding to the target transmission, respectively.

[0131] Table 2 provides an example of the specific content of the Extend TXOP Sharing Info subfield.

[0132] Table 2 Specific contents of the Extend TXOP Sharing Info subfield

[0133] Table 3 gives an example of the specific content of the Target User Info subfield.

[0134] Table 3 Target User Info subfield details

[0135] The encoding format of AID12 may be consistent with the encoding format of AID12 in the User Info field in the 802.11 standard, as shown in Table 4 below.

[0136] Table 4 AID12 encoding format

[0137] The encoding format of RU Allocation may be consistent with the encoding format of RU Allocation in the User Info field in the 802.11 standard, as shown in Table 5 below.

[0138] Table 5 RU Allocation encoding format

[0139] The encoding format of AC Constraint can adopt the encoding method shown in Table 6 below.

[0140] Table 6 AC Constraint encoding format

[0141] It should be noted that the embodiments of the present application do not specifically limit the type of the first frame shown in Figure 6. In some implementations, the first frame can be a data frame. In other implementations, to enable the first STA to better implement the extended TXOP sharing operation, the first frame can be designed as a new type of control frame. This control frame can be called an extended TXOP sharing control frame, or ETS control frame for short.

[0142] Taking the first control frame as an example, Figure 11 shows a possible structure of this control frame. As can be seen from Figure 11, this control frame contains two fields for recording information related to the extended TXOP sharing operation: Extended TXOP Sharing Info and Target User Info. The meaning of these two fields can be found in the descriptions of Figures 8 to 10 above.

[0143] The content of the Frame Control field of the control frame shown in Figure 11 is shown in Figure 12. The encoding method of the Subtype and Control Frame Extension subfields in the Frame Control field may adopt the encoding method shown in Table 7 below.

[0144] Table 7 Coding method of Subtype and Control Frame Extension subfields of ETS control frame

[0145] Communications devices participating in the extended TXOP sharing operation must be capable of performing the sharing operation. Whether a communications device is capable of performing the extended TXOP sharing operation can be indicated by capability information. This capability information can, for example, be carried in the EHT MAC capability information field. Taking the first frame mentioned above as an example, the first frame can include capability information indicating that the first STA is capable of performing the first sharing operation, and this capability information can be carried in the EHT MAC capability information field.

[0146] For example, the B14 reserved bit in the EHT MAC capability information field can be modified to the Extend TXOP Sharing Support field to indicate whether the current device has the extended TXOP sharing capability. If an AP or STA has the extended TXOP sharing capability, the Extend TXOP Sharing Support field in the modified EHT MAC capability information field will be set to 1 to indicate support for the "extended TXOP sharing operation"; otherwise, the bit will be set to 0 to indicate support for the "extended TXOP sharing operation". Figure 13 shows the modified EHT MAC capability information field, where B0 to B13 are existing capability fields and B14 is the newly added extended TXOP sharing capability field (i.e., Extend TXOP Sharing Support). Table 8 shows an example of the attribute values ​​of the Extend TXOP Sharing Support field and its meaning.

[0147] Table 8 Extend TXOP Sharing Support field description

[0148] If the AP or STA has the extended TXOP sharing capability and sets the Extend TXOP Sharing Support field in the EHT MAC capability information field to 1, then when performing the extended TXOP sharing operation, the attributes of the Extend TXOP Sharing control field will be set according to its own needs.

[0149] As mentioned above, the extended TXOP sharing operation can be initiated based on the request of the first AP. Figure 14 shows an example of performing an extended TXOP sharing operation based on the request of the first AP. Referring to Figure 14, before the first STA sends the first frame to the first AP, the first STA first receives the second frame sent by the first AP (step S1420). The second frame contains the first request, and the first request is used to request the extended TXOP sharing operation. For example, the second frame may include the Extend TXOP Sharing field described above. The Extend TXOP Sharing field in the second frame and the Extend TXOP Sharing field in the first frame may use the same format, except that, for the first AP, the Extend TXOP Sharing Grant / Extend TXOP Sharing Receive field is Extend TXOP Sharing Receive, and the first AP may set the value of Extend TXOP Sharing Receive to 1 to indicate that the first AP requests the first STA to extend the TXOP sharing operation.

[0150] As shown in Figure 15, in some implementations, after the first STA sends the first frame to the first AP, the first AP may send a third frame to the first STA (step S1520). The third frame includes confirmation information of the first sharing operation. For example, the third frame may include the Extend TXOP Sharing field described above. The Extend TXOP Sharing field in the third frame may use the same format as the Extend TXOP Sharing field in the first frame, except that, for the first AP, the Extend TXOP Sharing Grant / Extend TXOP Sharing Receive field is Extend TXOP Sharing Receive, and the first AP may set the value of Extend TXOP Sharing Receive to 1 to indicate that the first AP confirms the execution of the extended TXOP sharing operation.

[0151] As shown in Figure 16, in some implementations, after the first STA sends the first frame to the first AP, the first AP may send a fourth frame to the first STA (step S1620). The fourth frame contains sixth information. The sixth information is used to indicate one or more of the following: ending the extended TXOP sharing operation and returning the transmission resources to the first STA. For example, the fourth frame may include the Extend TXOP Sharing field described above. The Extend TXOP Sharing field in the fourth frame and the Extend TXOP Sharing field in the first frame may use the same format, except that, for the first AP, the Extend TXOP Sharing Grant / Extend TXOP Sharing Receive field is Extend TXOP Sharing Receive, and the first AP may set the value of Extend TXOP Sharing Receive to 0 to indicate that the first AP ends the extended TXOP sharing operation and returns the transmission resources to the first STA.

[0152] As shown in FIG. 17 , in some implementations, after the first STA sends the first frame to the first AP, the first AP may send a Contention Free–End (CF-End) frame to the first STA (step S1720 ) to directly declare the end of the extended TXOP sharing operation.

[0153] The following examples are used to describe the embodiments of the present application in more detail. It should be noted that the examples below are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. It is apparent that those skilled in the art can make various equivalent modifications or changes based on the examples given below, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0154] Example 1: Limited Extended TXOP Sharing Mode

[0155] When an AP with extended TXOP sharing capability exchanges UL data with a STA with extended TXOP sharing capability, the AP can proactively request a limited extended TXOP sharing operation based on its own transmission requirements and request a transmission resource segment from the STA. The STA can also proactively initiate a limited extended TXOP sharing operation based on its own transmission requirements and allocate a transmission resource segment to the AP. During the limited extended TXOP sharing operation, the STA specifies subsequent transmission requirements for the AP.

[0156] 1.1 AP Behavior

[0157] When an AP with extended TXOP sharing capability exchanges UL data with a STA with extended TXOP sharing capability, if the AP expects the STA to perform limited extended TXOP sharing and request a transmission resource, it can send a frame carrying the Extend TXOP Sharing Control field (hereinafter referred to as the ETS Control field) to the STA; the AP will set the Extend TXOP Sharing Mode attribute value in the Extend TXOP Sharing Info subfield to 0 and the Extend TXOP Sharing Receive attribute value to 1, indicating that the AP is requesting the STA to perform limited extended TXOP sharing.

[0158] If the AP sends a frame carrying the ETS Control field or directly receives a frame containing the ETS Control field from a STA, and the Extend TXOP Sharing Mode attribute value in the Extend TXOP Sharing Info subfield is 0 and the Extend TXOP Sharing Grant attribute value is 1, indicating that the STA is preparing to initiate a restricted extended TXOP sharing operation, the AP will parse and save the contents of the Target User Info subfield. The AP will reply to the STA with a frame carrying the ETS Control field or an ETS Control frame, and set the Extend TXOP Sharing Mode attribute value in the Extend TXOP Sharing Info subfield to 0 and the Extend TXOP Sharing Receive attribute value to 1, indicating that the AP has successfully received the STA's original TXOP transmission resources.

[0159] After completing the transmission of the confirmation frame, the AP is deemed to have obtained the original TXOP transmission resources of the STA; in the subsequent transmission process, the AP needs to give priority to guaranteeing the transmission requirements proposed by the STA in the Target User Info subfield.

[0160] If the AP fails to transmit a frame carrying the ETS control field, or if the AP receives a data frame or ETS control frame containing the ETS control field from a STA, and the Extend TXOP Sharing Mode attribute value is 0 or the Extend TXOP Sharing Grant attribute value is 0, the AP's request fails.

[0161] After completing data transmission within the acquired TXOP, if the AP wishes to return the transmission resource to the original resource holder, it will send a frame carrying the ETS control field to the original resource holder, i.e., the STA. The AP will set the Extend TXOP Sharing Mode attribute value to 0 and the Extend TXOP Sharing Receive attribute value to 0 in the frame, indicating that the remaining transmission resource will be returned to the STA. Otherwise, the AP will send a CF-end frame to directly declare the end of the current TXOP.

[0162] Figure 18 is a flowchart of operations in the restricted extended TXOP sharing mode. Figure 18 is mainly described from the perspective of the AP, and in Figure 18, the extended TXOP sharing operation is initiated based on the AP's request.

[0163] 18 , in step S1802 , the AP prepares to start an extended TXOP sharing operation.

[0164] In step S1804, the AP sets Extend TXOP Sharing Mode to 0, sets Extend TXOP Sharing Receive to 1, and requests transmission resources from the STA.

[0165] In step S1806, it is determined whether the STA accepts the resource request. If not, step S1820 is executed; if accepted, step S1808 is executed.

[0166] In step S1808, the AP parses the Target User Info field of the STA.

[0167] In step S1810, the AP sets Extend TXOP Sharing Receive to 1 as confirmation information to the STA.

[0168] In step S1812, the AP obtains transmission resources and performs data transmission. During the data transmission process, the AP needs to ensure that the data transmission process meets the transmission requirements set forth in the Target User Info field.

[0169] In step S1814, the AP determines whether to return the transmission resources. If so, step S1816 is executed; if not, step S1818 is executed.

[0170] In step S1816, the AP sets Extend TXOP Sharing Receive to 0 and returns the transmission resources of this segment to the STA.

[0171] In step S1818, the AP sends a CF-end frame to end this TXOP.

[0172] In step S1820, the current extended TXOP sharing operation ends.

[0173] Figure 19 is another operation flow chart of the limited extended TXOP sharing mode. Figure 19 is mainly described from the perspective of the AP, and in Figure 19, the extended TXOP sharing operation is actively initiated by the STA.

[0174] In step S1902, the AP receives a request from the STA.

[0175] In step S1904, the AP parses the Target User Info field of the STA.

[0176] In step S1906 , the AP sets Extend TXOP Sharing Mode to 0 and sets Extend TXOP Sharing Receive to 1, indicating that an extended TXOP sharing operation is performed with the STA.

[0177] In step S1908, the AP obtains transmission resources and performs data transmission, and the data transmission needs to meet the transmission requirements of the Target User Info field.

[0178] In step S1910, the AP determines whether to return the transmission resources. If the transmission resources are returned, the process proceeds to step S1912; if not, the process proceeds to step S1914.

[0179] In step S1912, the AP sets Extend TXOP Sharing Receive to 0 and returns the transmission resources of this segment to the STA.

[0180] In step S1914, the AP sends a CF-end frame to end this TXOP.

[0181] In step S1916, the extended TXOP sharing operation ends.

[0182] 1.2 STA Behavior

[0183] When a STA with extended TXOP sharing capability exchanges UL data with an AP with extended TXOP sharing capability, if the STA expects the AP to perform limited extended TXOP sharing and grant a period of transmission resources; or if the STA receives a frame from the AP containing the ETS Control field with the Extend TXOP Sharing Mode attribute set to 0 and the Extend TXOP Sharing Receive attribute set to 1, the STA can respond with a data frame or ETS Control frame containing the ETS Control field, setting the Extend TXOP Sharing Mode attribute in the Extend TXOP Sharing Info subfield to 0 and the Extend TXOP Sharing Grant attribute to 1. The STA can also set the Target User Info subfield based on its own transmission requirements. These actions indicate that the STA will perform a period of limited extended TXOP sharing. Furthermore, the STA uses the Duration / ID field to specify the duration of the transmission resources allocated to the AP.

[0184] If the STA receives a frame from the AP containing the ETS control field within a later timeframe, with the Extend TXOP Sharing Mode attribute set to 0 and the Extend TXOP Sharing Receive attribute set to 0, the remaining transmission resources are reclaimed. After sharing its transmission resources with the AP, the STA adjusts its operating state, such as adjusting its power mode, as appropriate.

[0185] Figure 20 is another operation flow chart in the restricted extended TXOP sharing mode. Figure 20 is mainly described from the perspective of the STA, and in Figure 20, the extended TXOP sharing operation is initiated based on the request of the AP.

[0186] Referring to FIG. 20 , in step S2002 , the STA receives a request from the AP.

[0187] In step S2004, the STA determines whether to approve the secondary resource request. If the STA approves the secondary resource request, the process proceeds to step S2006; if the STA disapproves the secondary resource request, the process proceeds to step S2016.

[0188] In step S2006, the STA sets the Extend TXOP Sharing Mode to 0 and the Extend TXOP Sharing Grant to 1, indicating that the STA accepts the request. In addition, the STA sets the Target User Info field according to its own needs.

[0189] In step S2008, it is determined whether the AP has replied with a confirmation message. If the AP has replied with a confirmation message, the process proceeds to step S2010; if the AP has not replied with a confirmation message, the process proceeds to step S2014.

[0190] In step S2010, the AP obtains transmission resources and performs data transmission.

[0191] In step S2012, it is determined whether the AP returns the transmission resources. If the AP returns the transmission resources, the process proceeds to step S2014; if the AP does not return the transmission resources, the process proceeds to step S2016.

[0192] In step S2014, the STA reclaims transmission resources.

[0193] In step S2016, the extended TXOP sharing operation ends.

[0194] Figure 21 is another operation flow chart in the restricted extended TXOP sharing mode. Figure 21 is mainly described from the perspective of a STA, and in Figure 21, the extended TXOP sharing operation is actively initiated by the STA.

[0195] 21 , in step S2102 , the STA prepares to start an extended TXOP sharing operation.

[0196] In step S2104, the STA sets Extend TXOP Sharing Mode to 0, sets Extend TXOP Sharing Grant to 1, and sets the Target User Info field according to its own needs, preparing to perform an extended TXOP sharing operation with the AP.

[0197] In step S2106, it is determined whether the AP replies with a confirmation message. If not, the process proceeds to step S2112; if the AP replies with a confirmation message, the process proceeds to step S2108.

[0198] In step S2108, the AP obtains transmission resources and performs data transmission.

[0199] In step S2110, it is determined whether the AP returns the transmission resources. If the AP returns the transmission resources, the process proceeds to step S2112; if the AP does not return the transmission resources, the process proceeds to step S2114.

[0200] In step S2112, the STA reclaims transmission resources.

[0201] In step S2114, the current extended TXOP sharing operation ends.

[0202] 1.3 Scenario Example

[0203] Figure 22 shows a scenario where the AP successfully applies for transmission resources from STA1 and performs DL data transmission. In the scenario shown in Figure 22, STA1 uses ETS control frames to exchange information. The AP and STA1 are performing UL data transmission, both of which have the ability to share extended TXOPs. At this time, a burst of low-latency traffic that needs to be transmitted to STA2 appears at the AP (this low-latency traffic is related to STA1's business). The AP proactively initiates a restricted extended TXOP sharing operation request to STA1. STA1 responds with an ETS control frame and requests the AP to exchange data with STA2 in the Target User Info field. The AP exchanges DL data with STA2 within the obtained transmission time. After completing the data exchange, the AP returns the transmission resources to STA1.

[0204] Figure 23 illustrates a scenario where the AP successfully requests transmission resources from STA1 and performs DL data transmission. The AP and STA1 are performing UL data transmission. Both have the extended TXOP sharing capability, and the AP experiences bursts of low-latency traffic that needs to be transmitted to STA2 (this low-latency traffic is related to STA1's service). The AP proactively initiates a restricted extended TXOP sharing operation request to STA1. STA1 requests data exchange with STA2 in the Target User Info field. The AP performs DL data exchange with STA2 within the specified transmission time. After completing the data exchange, the AP returns the transmission resources to STA1.

[0205] Figure 24 shows a scenario where the AP successfully requests transmission resources from STA1 and performs MU DL data transmission. The AP and STA1 are performing UL data transmission. Both have the extended TXOP sharing capability, and at this time, a burst of low-latency traffic (this low-latency traffic is related to STA1's service) is transmitted from the AP to STA2. The AP proactively initiates a restricted extended TXOP sharing operation request to STA1. STA1 requests data exchange with STA2 in the Target User Info field. The AP prioritizes DL data exchange with STA2 within the obtained transmission time and uses the remaining transmission resources for DL ​​data exchange with STA1. After completing the data exchange, the AP returns the transmission resources to STA1.

[0206] Figure 25 illustrates a scenario where the AP successfully requests transmission resources from STA1 and performs UL data transmission. The AP and STA1 are performing UL data transmission. Both have the Extended TXOP Sharing capability, and the AP needs to query STA2 for bursty low-latency traffic. The AP proactively initiates a restricted Extended TXOP Sharing operation request to STA1. STA1 uses the Target User Info field to request data exchange between the AP and STA2. The AP exchanges UL data with STA2 within the specified transmission time. After completing the data exchange, the AP returns the transmission resources to STA1.

[0207] Figure 26 shows a scenario where the AP successfully requests transmission resources from STA1 and performs DL data transmission. The AP and STA1 are performing UL data transmission. Both have the ability to share extended TXOPs, and at this time, a burst of low-latency traffic (this low-latency traffic is related to STA1's service) appears at the AP and is transmitted to STA2. The AP proactively initiates a limited extended TXOP sharing operation request to STA1. STA1 requests the AP to exchange data with STA2 in the Target User Info field. The AP exchanges DL data with STA2 within the obtained transmission time. After completing the data exchange, the AP sends a CF-end frame to end the current TXOP. STA1 does not reclaim the transmission resources.

[0208] Figures 27, 28, and 29 illustrate scenarios where STA1 allocates transmission resources to the AP and the AP performs downlink (DL) data transmission. The AP and STA1 are performing UL data transmission, both of which have the extended TXOP sharing capability. STA1 now wishes for the AP to assist STA2 in managing low-latency traffic (this low-latency traffic is related to STA1's services). STA1 proactively initiates a limited extended TXOP sharing operation with the AP. STA1 requests data exchange between the AP and STA2 in the Target User Info field. The AP performs downlink data exchange with STA2 within the specified transmission time. Figure 27 illustrates a scenario where the STA proactively initiates an extended TXOP sharing operation using an ETS control frame. Figure 28 illustrates a scenario where the AP returns transmission resources to STA1 after completing data exchange. Figure 29 illustrates a scenario where the AP sends a CF-end frame to end the current TXOP, and STA1 does not reclaim the transmission resources.

[0209] Example 2: Unrestricted Extended TXOP Sharing Mode

[0210] When an AP with extended TXOP sharing capability exchanges UL data with a STA with extended TXOP sharing capability, the AP can proactively request unrestricted extended TXOP sharing based on its own transmission requirements and request a transmission resource segment from the STA. The STA can also proactively initiate unrestricted extended TXOP sharing based on its own transmission requirements and allocate a transmission resource segment to the AP. During unrestricted extended TXOP sharing, the STA does not specify subsequent transmission requirements for the AP.

[0211] 2.1 AP Behavior

[0212] When an AP with extended TXOP sharing capability exchanges UL data with a STA with extended TXOP sharing capability, if the AP requests the STA to perform unrestricted extended TXOP sharing and request a transmission resource, the AP may send a frame carrying the Extend TXOP Sharing control field to the STA. The AP will set the Extend TXOP Sharing Mode attribute value to 1 and the Extend TXOP Sharing Receive attribute value to 1, indicating that the AP is requesting the STA to perform restricted extended TXOP sharing.

[0213] If the AP sends a frame carrying the ETS Control field (or directly receives) a data frame or ETS Control frame containing the ETS Control field from the STA, and the Extend TXOP Sharing Mode attribute value is 1 and the Extend TXOP Sharing Grant attribute value is 1 in the frame, it means that the STA is ready to initiate an unrestricted extended TXOP sharing operation. The AP will reply to the STA with a frame carrying the ETS Control field, and the AP will set the Extend TXOP Sharing Mode attribute value to 1 and the Extend TXOP Sharing Receive attribute value to 1 in the frame, indicating that the AP has successfully received the transmission resources held by the STA.

[0214] After completing the sending of the confirmation frame, the AP is deemed to have obtained the TXOP transmission resources held by the STA.

[0215] If the AP fails to transmit a frame carrying the ETS Control field, or if the AP receives a data frame or ETS Control frame containing the ETS Control field from a STA, and the Extend TXOP Sharing Mode attribute value of the frame is 1 and the Extend TXOP Sharing Grant attribute value is 0, it means that the AP's request has failed.

[0216] After completing data transmission within the specified transmission time, if the AP wishes to return the transmission resource to the original resource holder, it sends a frame containing the ETS control field to the original resource holder (the STA). The AP sets the Extend TXOP Sharing Mode attribute in this frame to 1 and the Extend TXOP Sharing Receive attribute to 0, indicating that the remaining transmission resource will be returned to the STA. Otherwise, the AP sends a CF-end frame to directly end the current TXOP.

[0217] Figure 30 is a flowchart of the operation in the unrestricted extended TXOP sharing mode. Figure 30 is mainly described from the perspective of the AP, and in Figure 30, the extended TXOP sharing operation is initiated based on the AP's request.

[0218] 30 , in step S3002 , the AP prepares to start an extended TXOP sharing operation.

[0219] In step S3004, the AP sets Extend TXOP Sharing Mode to 1 and sets Extend TXOP Sharing Receive to 1 to request transmission resources from the STA.

[0220] In step S3006, it is determined whether the STA agrees to the secondary resource request. If the STA agrees to the secondary resource request, the process proceeds to step S3008; if the STA disagrees to the secondary resource request, the process proceeds to step S3018.

[0221] In step S3008, the AP sets Extend TXOP Sharing Receive to 1 as confirmation information to the STA.

[0222] In step S3010, the AP obtains transmission resources and performs data transmission.

[0223] In step S3012, the AP determines whether to return the transmission resources. If so, the process proceeds to step S3014; if not, the process proceeds to step S3016.

[0224] In step S3014, the AP sets Extend TXOP Sharing Receive to 0, thereby returning the transmission resources of this segment to the STA.

[0225] In step S3016, the AP sends a CF-end frame to end this TXOP.

[0226] In step S3018, the extended TXOP sharing operation ends.

[0227] Figure 31 is another operation flow chart of the unrestricted extended TXOP sharing mode. Figure 31 is mainly described from the perspective of the AP, and in Figure 31, the extended TXOP sharing operation is actively initiated by the STA.

[0228] Referring to FIG. 31 , in step S3102 , the AP receives a request from the STA.

[0229] In step S3104, the AP sets Extend TXOP Sharing Mode to 1 and Extend TXOP Sharing Receive to 1, indicating that an extended TXOP sharing operation is performed with the STA.

[0230] In step S3106, the AP obtains transmission resources and performs data transmission.

[0231] In step S3108, the AP determines whether to return the transmission resources. If so, the process proceeds to step S3110; if not, the process proceeds to step S3112.

[0232] In step S3110, the AP sets Extend TXOP Sharing Receive to 0, thereby returning the transmission resources of this segment to the STA.

[0233] In step S3112, the AP sends a CF-end frame to end this TXOP.

[0234] In step S3114, the extended TXOP sharing operation ends.

[0235] 2.2 STA Behavior

[0236] When a STA with extended TXOP sharing capability exchanges UL data with an AP with extended TXOP sharing capability, if the STA expects the AP to perform unrestricted extended TXOP sharing and grant a period of transmission resources, or if the STA receives a frame from the AP containing the ETS Control field with the Extend TXOP Sharing Mode attribute set to 1 and the Extend TXOP Sharing Receive attribute set to 1, the STA can reply with a data frame or ETS Control frame containing the ETS Control field and setting the Extend TXOP Sharing Mode attribute to 1 and the Extend TXOP Sharing Grant attribute to 1, indicating that the STA will perform unrestricted extended TXOP sharing. The STA uses the Duration / ID field to specify the duration of the transmission resources allocated to the AP.

[0237] If the STA subsequently receives a frame from the AP containing the ETS control field, and the Extend TXOP Sharing Mode attribute value of the frame is 1 and the Extend TXOP Sharing Receive attribute value is 0, the STA reclaims the remaining transmission resources. After sharing its transmission resources with the AP, the STA adjusts its operating state accordingly.

[0238] Figure 32 is another operation flow chart of the unrestricted extended TXOP sharing mode. Figure 32 is mainly described from the perspective of the STA, and in Figure 32, the extended TXOP sharing operation is initiated based on the request of the AP.

[0239] Referring to FIG. 32 , in step S3202 , the STA receives a request from the AP.

[0240] In step S3204, the STA determines whether to approve the secondary resource request. If so, the process proceeds to step S3206; if not, the process proceeds to step S3216.

[0241] In step S3206, the STA sets Extend TXOP Sharing Mode to 1 and Extend TXOP Sharing Grant to 1, indicating that the request is approved.

[0242] In step S3208, it is determined whether the AP has replied with a confirmation message. If so, the process proceeds to step S3210; if not, the process proceeds to step S3214.

[0243] In step S3210, the AP obtains transmission resources and performs data transmission.

[0244] In step S3212, it is determined whether the AP has returned the transmission resources. If the transmission resources have been returned, the process proceeds to step S3214; if the transmission resources have not been returned, the process proceeds to step S3216.

[0245] In step S3214, the STA reclaims the transmission resources.

[0246] In step S3216, the extended TXOP sharing operation ends.

[0247] Figure 33 is another operation flow chart of the unrestricted extended TXOP sharing mode. Figure 33 is mainly described from the perspective of a STA, and in Figure 33, the extended TXOP sharing operation is actively initiated by the STA.

[0248] 33 , in step S3302 , the STA prepares to start an extended TXOP sharing operation.

[0249] In step S3304, the STA sets Extend TXOP Sharing Mode to 1 and Extend TXOP Sharing Grant to 1, and prepares to perform an extended TXOP sharing operation with the AP.

[0250] In step S3306, it is determined whether the AP has replied with a confirmation message. If so, the process proceeds to step S3308; if not, the process proceeds to step S3312.

[0251] In step S3308, the AP obtains transmission resources and performs data transmission.

[0252] In step S3310, it is determined whether the AP has returned the transmission resources. If the transmission resources have been returned, the process proceeds to step S3312; if the transmission resources have not been returned, the process proceeds to step S3314.

[0253] In step S3312, the STA reclaims transmission resources.

[0254] In step S3314, the extended TXOP sharing operation ends.

[0255] 2.3 Scenario Example

[0256] Figure 34 shows a scenario where the AP successfully requests transmission resources from STA1 and performs DL data transmission. In the scenario shown in Figure 34, STA1 uses ETS control frames to exchange information. The AP and STA1 are performing UL data transmission, both of which have extended TXOP sharing capabilities, and at this time, bursts of low-latency traffic transmitted to STA2 appear at the AP. The AP proactively initiates an unrestricted extended TXOP sharing operation request to STA1. Within the obtained transmission time, the AP can perform DL data transmission according to its own needs (such as exchanging DL data with STA2 in this scenario). After completing the data exchange, the AP returns the transmission resources to STA1.

[0257] Figure 35 illustrates a scenario where the AP successfully requests transmission resources from STA1 and performs DL data transmission. The AP and STA1 are performing UL data transmission, both of which have extended TXOP sharing capabilities. At this time, bursts of low-latency traffic are occurring at the AP, destined for STA2. The AP proactively initiates an unrestricted extended TXOP sharing operation request to STA1. Within the requested transmission time, the AP can perform DL data transmission based on its needs (for example, exchanging DL data with STA2 in this scenario). After completing the data exchange, the AP returns the transmission resources to STA1.

[0258] Figure 36 illustrates a scenario where the AP successfully requests transmission resources from STA1 and performs UL data transmission. The AP and STA1 are performing UL data transmission. Both have the Extended TXOP Sharing capability, and the AP needs to query STA2 for bursty low-latency traffic. The AP proactively initiates an unrestricted Extended TXOP Sharing request to STA1. Within the requested transmission time, the AP can perform UL data transmission based on its needs. After completing the data exchange, the AP returns the transmission resources to STA1.

[0259] Figure 37 illustrates a scenario where the AP successfully requests transmission resources from STA1 and performs DL data transmission. The AP and STA1 are performing UL data transmission. Both have the extended TXOP sharing capability, and bursts of low-latency traffic are occurring at the AP, destined for STA2. The AP proactively initiates an unrestricted extended TXOP sharing request to STA1. Within the allocated transmission time, the AP can perform DL data transmission based on its needs. After completing the data exchange, the AP sends a CF-end frame to end the current TXOP. STA1 does not reclaim the transmission resources.

[0260] Figures 38, 39, and 40 all illustrate scenarios where STA1 allocates transmission resources to the AP and the AP performs DL data transmission. The AP and STA1 are performing UL data transmission, and both have the ability to share extended TXOPs. At this point, STA1 wishes for the AP to assist STA2 in managing low-latency traffic (this low-latency traffic is related to STA1's services). STA1 proactively initiates an unrestricted extended TXOP sharing operation with the AP. Within the obtained transmission time, the AP can perform DL data transmission according to its needs (in this scenario, it exchanges DL data with STA2). Figure 38 shows a scenario where the STA proactively initiates an unrestricted TXOP sharing operation using an ETS control frame. Figure 39 shows a scenario where the AP returns transmission resources to STA1 after completing data exchange. Figure 40 shows a scenario where the AP sends a CF-end frame to end the current TXOP, and STA1 does not reclaim the transmission resources.

[0261] Example 2: First RD transmission

[0262] In the RD transmission protocol provided by related technologies, when a STA (such as a non-AP STA) holding transmission resources transmits RD to an AP, the AP's data transmission must meet the following rules:

[0263] a) The AP's subsequent communication objects must include the STA that holds the transmission resources;

[0264] b) When the AP is transmitting RD, if the AP completes the data interaction with the original transmission resource holder or sends a confirmation message, the original transmission resource holder, that is, the STA, will end the RD transmission process.

[0265] As can be seen, in the existing RD transmission protocol, the transmission rights that an AP obtains from a STA are very limited. This limited transmission right is reflected both in the communication target (the AP must communicate data with the STA holding the transmission resources) and in the duration of the RD transmission (the RD transmission is terminated when an acknowledgment message is received). To meet the application requirements of various scenarios (such as network management and low-latency service processing), the AP needs to have more transmission rights and / or transmission resources in RD transmission to achieve the desired transmission goals.

[0266] Based on the above considerations, Example 2 extends or enhances the RD transmission protocol to support the first RD transmission. The first RD transmission may also be referred to as extended RD transmission or enhanced RD transmission. In Example 2, the terms first RD transmission, extended RD transmission, and enhanced RD transmission may be used interchangeably. The following description primarily uses extended RD transmission as an example.

[0267] In some implementations, extended RD transmission may enhance RD transmission based on one or more of the following:

[0268] a) Extended RD transmission supports the first AP initiating target transmission based on the transmission resources held by the first STA, wherein the target communication device participating in the target transmission may include the first STA or may not include the first STA; that is, the first AP can transmit data according to its own needs and is not required to communicate with the original transmission resource holder.

[0269] b) Extended RD transmission does not have any additional termination rule; that is, during the extended RD transmission process, even if the first AP sends a confirmation message, it does not necessarily mean that the extended RD transmission is terminated.

[0270] c) If the first AP completes data interaction before the end of the extended RD transmission specified time, it can return the current transmission resource to the first STA in an explicit notification manner.

[0271] Extending RD transmission can enable APs to have more flexible data transmission methods to meet the needs of low-latency service transmission and network management in multiple scenarios.

[0272] The following provides a more detailed example of the implementation of the second embodiment from the perspective of communication frame design and information interaction.

[0273] Referring to Figure 41 , a first STA sends a first frame to a first AP (step S4110). The first frame includes first information. The first information indicates that the first STA has initiated an extended RD transmission. Alternatively, the first information includes information related to the extended RD transmission. Alternatively, the first information carries management information for the extended RD transmission.

[0274] The first information is carried in the CAS Control field. For example, bit B3 of the Control Information subfield of the CAS Control field is set to "Extend Reserve Direction Grant (Extend RDG)." Figure 42 shows an example of the specific format of the modified CAS Control field. Table 9 shows the values ​​and meanings of "Extend RDG."

[0275] Table 9 "Extend RDG" values ​​and their meanings

[0276] The first STA and / or the first AP may be a communication device with extended RD transmission capability. The first STA and / or the first AP may indicate whether it has extended RD transmission capability through capability information. For example, the first frame in Figure 41 may include ninth information, which is used to indicate that the first STA has the capability to perform the first reverse transmission. The ninth information may be carried in the HT Extended Capabilities field and / or the HE 6GHz Capabilities field. For example, bit B12 of the HT Extended Capabilities field and bit B14 of the Capabilities Information field of the HE 6GHz Capabilities field may be set to "Extend RD Responder" to indicate whether the communication device has extended RD transmission capability. If the communication device has extended RD transmission capability, Extend RD Responder may be set to 1; otherwise, Extend RD Responder may be set to 0. Figures 43 and 44 respectively provide examples of the revised HT Extended Capabilities field and HE 6GHz Capabilities field.

[0277] Referring to FIG. 45 , in some implementations, after sending the first frame, the first AP sends a fifth frame to the first STA (step S4520). The fifth frame includes confirmation information for the first reverse transmission (i.e., acceptance of the extended RD transmission process initiated by the peer end). For example, the fifth frame may include the aforementioned Extended RDG field, with the value of the Extended RDG field set to 1.

[0278] Referring to FIG. 46 , in some implementations, after sending the first frame, the first AP sends a sixth frame to the first STA (step S4620). The sixth frame includes eighth information. The eighth information indicates one or more of the following: terminating the first reverse transmission and returning the transmission resources to the first STA. For example, the sixth frame may include the aforementioned Extend RDG field, with the value of the Extend RDG field set to 0.

[0279] In some implementations, during the extended RD transmission process, the first AP only obtains partial transmission rights of the transmission resources, and therefore the first AP cannot use the CF-end frame to end the TXOP.

[0280] In some implementations, if a legacy STA does not support extended RD transmission, it may still use the RD transmission method provided by related technologies to perform data transmission.

[0281] The following examples are used to describe the embodiments of the present application in more detail. It should be noted that the examples below are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. It is apparent that those skilled in the art can make various equivalent modifications or changes based on the examples given below, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0282] Example 3:

[0283] This example proposes extended RD transmission. With extended RD transmission, a STA can temporarily transfer its transmission resources to the AP. The AP can then use these resources for downlink or uplink data transmission. Devices that support this solution are called "extended RD transmission-capable." Devices with extended RD transmission capabilities are identified in their capabilities information.

[0284] When a STA with extended RD transmission capability conducts UL data transmission with an AP with extended RD transmission capability, this example provides a solution to temporarily transfer transmission resources to the AP. After acquiring these transmission resources, the AP will perform data transmission based on its needs. After completing the data transmission, the AP must return the transmission rights to the original STA.

[0285] When a STA with extended RD transmission capability exchanges UL data with an AP with the same capability, if the STA expects the AP to perform extended RD transmission and allocate a transmission resource, the STA can send a frame with the CAS control field and set the Extend RDG attribute value in the CAS control field to 1, indicating that the STA will perform an extended RD transmission. The STA can use the Duration / ID field to specify the transmission duration allocated to the AP.

[0286] If an AP with extended RD transmission capability receives a frame from a STA containing the CAS Control field and the Extend RDG attribute in the CAS Control field set to 1, it indicates that the STA is preparing to perform an extended RD transmission. The AP responds to the STA with a frame containing the CAS Control field and the Extend RDG attribute set to 1, indicating that the AP has successfully received the transmission resources indicated by the STA. After sending this confirmation frame, the AP is considered to have obtained the transmission resources from the STA.

[0287] If the AP completes data transmission before the end of the assigned transmission time, it should return the transmission resource to the original resource holder. The AP sends a frame with the CAS control field and sets the Extend RDG attribute value in the CAS control field to 1 to the original resource holder. Otherwise, the AP continues to send data until the assigned transmission time ends, at which time the STA reclaims the transmission resource. The AP cannot send CF-end to end the current transmission resource.

[0288] STA operation process

[0289] Figure 47 is a flowchart of the operation of extended RD transmission. Figure 47 is mainly described from the perspective of STA.

[0290] 47 , in step S4702 , the STA prepares to start an extended RD transmission.

[0291] In step S4704, the STA sets the Extend RDG bit to 1 and authorizes the AP.

[0292] In step S4706, it is determined whether the AP has replied with a confirmation message. If so, the process proceeds to step S4708; if not, the process proceeds to step S4712.

[0293] In step S4708, the AP obtains transmission resources and performs data transmission.

[0294] In step S4710, it is determined whether the AP returns the transmission resources in advance. If the transmission resources are returned in advance, the process proceeds to step S4712; if the transmission resources are not returned in advance, the process proceeds to step S4714.

[0295] In step S4712, the STA reclaims transmission resources in advance.

[0296] In step S4714, the STA reclaims the transmission resources at the expected time.

[0297] In step S4716, the extended RD transmission ends.

[0298] AP operation process

[0299] Figure 48 is a flowchart of the operation of extended RD transmission. Figure 48 is mainly described from the perspective of the AP.

[0300] 48 , in step S4802 , the AP receives an extended RD transmission request from the STA.

[0301] In step S4804, the AP sets the Extend RDG bit to 1 and sends a confirmation message to the STA.

[0302] In step S4806, the AP obtains transmission resources and performs data transmission.

[0303] In step S4808, the AP determines whether to return the transmission resources in advance. If so, the AP proceeds to step S4810; if not, the AP proceeds to step S4812.

[0304] In step S4810, the AP sets Extend RDG to 0 and returns the transmission resources to the STA.

[0305] In step S4812, the AP ends the transmission at the expected time.

[0306] In step S4814, the extended RD transmission ends.

[0307] Scenario Example

[0308] Figure 49 illustrates a scenario where STA1 is performing extended RD transmission with the AP, while the AP is performing DL data transmission. The AP and STA1 are performing UL data transmission, both of which have the extended RD transmission capability. STA1 also requests the AP's assistance in managing low-latency traffic for STA2 (this low-latency traffic is related to STA1's services). STA1 proactively initiates an extended RD transmission with the AP. First, STA1 allocates extended RD transmission time to the AP, and then the AP performs DL data transmission with STA2. After completing the data transmission, the AP proactively returns the transmission resources to STA1. STA1 will reclaim the transmission resources in advance.

[0309] Figure 50 illustrates a scenario where STA1 is performing extended RD transmission with the AP, while the AP is performing DL data transmission. The AP and STA1 are performing UL data transmission, both of which have the extended RD transmission capability. STA1 also requests the AP to assist STA2 in managing low-latency traffic related to STA1's services. STA1 proactively initiates an extended RD transmission with the AP. First, STA1 allocates extended RD transmission time to the AP, after which the AP performs DL data transmission with STA2. The AP continues exchanging data until the allocated time expires. STA1 reclaims transmission resources at the expected time.

[0310] Figure 51 illustrates a scenario where STA1 is performing extended RD transmission with the AP, while the AP is performing UL data transmission. The AP and STA1 are performing UL data transmission. Both AP and STA1 have the extended RD transmission capability, and STA1 requests the AP's assistance in managing low-latency traffic for STA2 (this low-latency traffic is related to STA1's services). STA1 proactively initiates an extended RD transmission with the AP. First, STA1 allocates extended RD transmission time to the AP, and then the AP performs UL data transmission with STA2. After completing the data transmission, the AP proactively returns the transmission resources to STA1. STA1 will reclaim the transmission resources in advance.

[0311] Figure 52 illustrates a scenario where STA1 is performing extended RD transmission with the AP, while the AP is also performing UL data transmission. The AP and STA1 are performing UL data transmission. Both have the extended RD transmission capability, and STA1 requests the AP's assistance in managing low-latency traffic for STA2 (this low-latency traffic is related to STA1's service). STA1 proactively initiates an extended RD transmission sequence with the AP. First, STA1 allocates extended RD transmission time to the AP, after which the AP performs UL data transmission with STA2. The AP continues to exchange data until the allocated time expires. STA1 reclaims transmission resources at the expected time.

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

[0313] FIG53 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. The communication device 5300 shown in FIG53 may be the first station mentioned above. The communication device 5300 includes:

[0314] The communication module 5310 is configured to send a first frame to a second station, where the first frame includes first information, and the first information is configured to indicate that the second station shares the transmission resources held by the first station for transmission.

[0315] In some implementations, the first information includes relevant information of a first sharing operation, where the first sharing operation is used to share the transmission resource with the second site.

[0316] In some implementations, the first information includes second information, where the second information is used to indicate a sharing mode of the transmission resource.

[0317] In some implementations, the transmission resource sharing mode includes one or more of the following:

[0318] a first sharing mode, in which the first site does not restrict the second site from using the transmission resource;

[0319] A second sharing mode, in which the first site restricts the second site from using the transmission resource.

[0320] In some implementations, the first information includes third information, and the third information is used to limit the way the second station uses the transmission resource.

[0321] In some implementations, the third information is used to limit one or more of the following:

[0322] target communication devices participating in target transmission;

[0323] The communication bandwidth corresponding to the target transmission;

[0324] The data category corresponding to the target transmission;

[0325] The target transmission is the transmission performed by the second station based on the transmission resource.

[0326] In some implementations, the first information includes fourth information, where the fourth information is used to instruct the first site to accept the first request initiated by the second site, where the first request is used to request the first sharing operation.

[0327] In some implementations, the communication module 5310 is further configured to: before the first site sends the first frame to the second site, receive a second frame sent by the second site, where the second frame includes the first request.

[0328] In some implementations, the first information includes fifth information, where the fifth information is used to instruct the first site to actively share the transmission resources with the second site.

[0329] In some implementations, the communication module 5310 is further configured to:

[0330] After sending the first frame, a third frame sent by the second station is received, where the third frame includes confirmation information of the first sharing operation.

[0331] In some implementations, the communication module 5310 is further configured to:

[0332] Receive a fourth frame sent by the second station, where the fourth frame includes sixth information, where the sixth information is used to indicate one or more of the following:

[0333] End the first sharing operation;

[0334] Returning the transmission resource to the first site.

[0335] In some implementations, the communication module 5310 is further configured to:

[0336] Receive the CF-end frame sent by the second station.

[0337] In some implementations, the first information is carried in a control field.

[0338] In some implementations, the control field is a control subfield in the HT control field.

[0339] In some implementations, the first frame is a control frame or a data frame.

[0340] In some implementations, the first frame includes seventh information, where the seventh information is used to indicate that the first site has the capability to perform the first sharing operation.

[0341] In some implementations, the seventh information is carried in an EHT MAC capability information field.

[0342] In some implementations, the first information is used to indicate that the first station initiated a first reverse transmission.

[0343] In some implementations, the first reverse transmission supports the second station initiating a target transmission based on the transmission resource, wherein target communication devices participating in the target transmission do not include the first station.

[0344] In some implementations, the communication module 5310 is further configured to:

[0345] After sending the first frame, a fifth frame sent by the second station is received, where the fifth frame includes confirmation information of the first reverse transmission.

[0346] In some implementations, the communication module 5310 is further configured to:

[0347] Receive a sixth frame sent by the second station, where the sixth frame includes eighth information, where the eighth information is used to indicate one or more of the following:

[0348] Ending the first reverse transmission;

[0349] Returning the transmission resource to the first site.

[0350] In some implementations, the first information is carried in a CAS control field.

[0351] In some implementations, the first frame includes ninth information, where the ninth information is used to indicate that the first station has the capability to perform the first reverse transmission.

[0352] In some implementations, the ninth information is carried in the HT extended capability field and / or the HE 6 GHz capability field.

[0353] In some implementations, the first frame includes tenth information, where the tenth information is used to indicate a duration for which the second station uses the transmission resource.

[0354] In some implementations, the tenth information is carried in a duration / identification field.

[0355] In some implementations, the transmission resource is a partial or full transmission opportunity.

[0356] In some implementations, the second station is an access point.

[0357] In some implementations, the first site is associated with the second site.

[0358] In some implementations, the first station is a non-access point station.

[0359] FIG54 is a schematic diagram of the structure of a communication device provided in another embodiment of the present application. The communication device 5400 shown in FIG54 may be the second site mentioned above. The communication device 5400 includes:

[0360] The communication module 5410 is configured to receive a first frame sent by a first station, where the first frame includes first information, and the first information is configured to indicate that the second station shares the transmission resources held by the first station for transmission.

[0361] In some implementations, the first information includes relevant information of a first sharing operation, where the first sharing operation is used to share the transmission resource with the second site.

[0362] In some implementations, the first information includes second information, where the second information is used to indicate a sharing mode of the transmission resource.

[0363] In some implementations, the transmission resource sharing mode includes one or more of the following:

[0364] a first sharing mode, in which the first site does not restrict the second site from using the transmission resource;

[0365] A second sharing mode, in which the first site restricts the second site from using the transmission resource.

[0366] In some implementations, the first information includes third information, and the third information is used to limit the way the second station uses the transmission resource.

[0367] In some implementations, the third information is used to limit one or more of the following:

[0368] target communication devices participating in target transmission;

[0369] The communication bandwidth corresponding to the target transmission;

[0370] The data category corresponding to the target transmission;

[0371] The target transmission is the transmission performed by the second station based on the transmission resource.

[0372] In some implementations, the first information includes fourth information, where the fourth information is used to instruct the first site to accept the first request initiated by the second site, where the first request is used to request the first sharing operation.

[0373] In some implementations, the communication module 5410 is further configured to: send a second frame to the first station before the second station receives the first frame sent by the first station, where the second frame includes the first request.

[0374] In some implementations, the first information includes fifth information, where the fifth information is used to instruct the first site to actively share the transmission resources with the second site.

[0375] In some implementations, the communication device 5410 further includes:

[0376] After receiving the first frame, a third frame is sent to the first site, where the third frame includes confirmation information of the first sharing operation.

[0377] In some implementations, the communication module 5410 is further configured to:

[0378] Send a fourth frame to the first station, where the fourth frame includes sixth information, where the sixth information is used to indicate one or more of the following:

[0379] End the first sharing operation;

[0380] Returning the transmission resource to the first site.

[0381] In some implementations, the communication module 5410 is further configured to:

[0382] Send a CF-end frame to the first station.

[0383] In some implementations, the first information is carried in a control field.

[0384] In some implementations, the control field is a control subfield in the HT control field.

[0385] In some implementations, the first frame is a control frame or a data frame.

[0386] In some implementations, the first frame includes seventh information, where the seventh information is used to indicate that the first site has the capability to perform the first sharing operation.

[0387] In some implementations, the seventh information is carried in an EHT MAC capability information field.

[0388] In some implementations, the first information is used to indicate that the first station initiated a first reverse transmission.

[0389] In some implementations, the first reverse transmission supports the second station initiating a target transmission based on the transmission resource, wherein target communications devices participating in the target transmission do not include the first station.

[0390] In some implementations, the communication module 5410 is further configured to:

[0391] After receiving the first frame, a fifth frame is sent to the first station, where the fifth frame includes confirmation information of the first reverse transmission.

[0392] In some implementations, the communication module 5410 is further configured to:

[0393] Send a sixth frame to the first station, where the sixth frame includes eighth information, where the eighth information is used to indicate one or more of the following:

[0394] Ending the first reverse transmission;

[0395] Returning the transmission resource to the first site.

[0396] In some implementations, the first information is carried in a CAS control field.

[0397] In some implementations, the first frame includes ninth information, where the ninth information is used to indicate that the first station has the capability to perform the first reverse transmission.

[0398] In some implementations, the ninth information is carried in the HT extended capability field and / or the HE 6 GHz capability field.

[0399] In some implementations, the first frame includes tenth information, where the tenth information is used to indicate a duration for which the second station uses the transmission resource.

[0400] In some implementations, the tenth information is carried in a duration / identification field.

[0401] In some implementations, the transmission resource is a partial or full transmission opportunity.

[0402] In some implementations, the second station is an access point.

[0403] In some implementations, the first site is associated with the second site.

[0404] In some implementations, the first station is a non-access point station.

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

[0406] The device 5500 may include one or more processors 5510. The processor 5510 may support the device 5500 to implement the method described in the method embodiment above. The processor 5510 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.

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

[0408] The apparatus 5500 may further include a transceiver 5530. The processor 5510 may communicate with other devices or chips via the transceiver 5530. For example, the processor 5510 may transmit and receive data with other devices or chips via the transceiver 5530.

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

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

[0411] 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 communication device in each embodiment of the present application.

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

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

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

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

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

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

[0418] 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."

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

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

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

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

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

[0424] 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)).

[0425] 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, it includes: A first station sends a first frame to a second station, the first frame contains first information, and the first information is used to indicate that the second station is shared with the transmission resources held by the first station for transmission.

2. The method according to claim 1, characterized in that, the first information contains information related to a first sharing operation, and the first sharing operation is used to share the transmission resources with the second station.

3. The method according to claim 2, characterized in that, the first information contains second information, and the second information is used to indicate the sharing mode of the transmission resources.

4. The method according to claim 3, characterized in that, the sharing mode of the transmission resources includes one or more of the following: A first sharing mode, in which the first station does not restrict the usage mode of the second station for the transmission resources; A second sharing mode, in which the first station restricts the usage mode of the second station for the transmission resources.

5. The method according to any one of claims 2 to 4, characterized in that, the first information contains third information, and the third information is used to restrict the usage mode of the second station for the transmission resources.

6. The method according to claim 5, characterized in that, the third information is used to restrict one or more of the following: Target communication devices participating in the target transmission; The communication bandwidth corresponding to the target transmission; The data category corresponding to the target transmission; wherein the target transmission is the transmission performed by the second station based on the transmission resources.

7. The method according to any one of claims 2 to 6, characterized in that, the first information contains fourth information, and the fourth information is used to indicate that the first station accepts a first request initiated by the second station, and the first request is used to request the first sharing operation.

8. The method according to claim 7, characterized in that, before the first station sends the first frame to the second station, the method further includes: The first station receives a second frame sent by the second station, and the second frame contains the first request.

9. The method according to any one of claims 2 to 6, characterized in that, the first information contains fifth information, and the fifth information is used to indicate that the first station actively shares the transmission resources with the second station.

10. The method according to any one of claims 2 to 9, characterized in that, the method further includes: After sending the first frame, the first station receives a third frame sent by the second station, and the third frame contains confirmation information of the first sharing operation.

11. The method according to any one of claims 2 to 10, characterized in that, the method further includes: The first station receives a fourth frame sent by the second station, and the fourth frame contains sixth information, and the sixth information is used to indicate one or more of the following: End the first sharing operation; Return the transmission resources to the first station.

12. The method according to any one of claims 2 to 10, wherein, the method further includes: the first station receives a contention-free end (CF-end) frame sent by the second station.

13. The method according to any one of claims 2 to 12, wherein, the first information is carried in a control field.

14. The method according to claim 13, wherein, the control field is a control sub-field in a high throughput (HT) control field.

15. The method according to any one of claims 2 to 14, wherein, the first frame is a control frame or a data frame.

16. The method according to any one of claims 2 to 15, wherein, the first frame includes seventh information, and the seventh information is used to indicate that the first station has the ability to perform the first sharing operation.

17. The method according to claim 16, wherein, the seventh information is carried in an extremely high throughput media access control (EHT MAC) capability information field.

18. The method according to claim 1, wherein, the first information is used to indicate that the first station has initiated a first reverse transmission.

19. The method according to claim 18, wherein, the first reverse transmission supports the second station to initiate a target transmission based on the transmission resource, and the target communication device participating in the target transmission does not include the first station.

20. The method according to claim 18 or 19, wherein, the method further includes: after sending the first frame, the first station receives a fifth frame sent by the second station, and the fifth frame includes confirmation information of the first reverse transmission.

21. The method according to any one of claims 18 to 20, wherein, the method further includes: the first station receives a sixth frame sent by the second station, and the sixth frame includes eighth information, and the eighth information is used to indicate one or more of the following: ending the first reverse transmission; returning the transmission resource to the first station.

22. The method according to any one of claims 18 to 21, wherein, the first information is carried in a command and status (CAS) control field.

23. The method according to any one of claims 18 to 22, wherein, the first frame includes ninth information, and the ninth information is used to indicate that the first station has the ability to perform the first reverse transmission.

24. The method according to claim 23, wherein, the ninth information is carried in an HT extension capability field and / or a high efficiency (HE) 6 GHz capability field.

25. The method according to any one of claims 1 to 24, wherein, the first frame includes tenth information, and the tenth information is used to indicate the duration for which the second station uses the transmission resource.

26. The method according to claim 25, wherein, the tenth information is carried in a duration / identifier field.

27. The method according to any one of claims 1 to 26, wherein, The transmission resource is part or all of the transmission opportunities.

28. The method according to any one of claims 1 to 27, wherein, the second site is an access point.

29. The method according to any one of claims 1 to 28, wherein, the first site is associated with the second site.

30. The method according to any one of claims 1 to 29, wherein, the first site is a non-access point site.

31. A wireless communication method, wherein, comprising: A second site receives a first frame sent by a first site, the first frame includes first information, and the first information is used to indicate that the second site is shared with the transmission resource held by the first site for transmission.

32. The method according to claim 31, wherein, the first information includes information related to a first sharing operation, and the first sharing operation is used to share the transmission resource with the second site.

33. The method according to claim 32, wherein, the first information includes second information, and the second information is used to indicate the sharing mode of the transmission resource.

34. The method according to claim 33, wherein, the sharing mode of the transmission resource includes one or more of the following: A first sharing mode, in the first sharing mode, the first site does not restrict the usage mode of the transmission resource by the second site; A second sharing mode, in the second sharing mode, the first site restricts the usage mode of the transmission resource by the second site.

35. The method according to any one of claims 32 to 34, wherein, the first information includes third information, and the third information is used to restrict the usage mode of the transmission resource by the second site.

36. The method according to claim 35, wherein, the third information is used to restrict one or more of the following: Target communication devices participating in the target transmission; The communication bandwidth corresponding to the target transmission; The data category corresponding to the target transmission; wherein, the target transmission is the transmission performed by the second site based on the transmission resource.

37. The method according to any one of claims 32 to 36, wherein, the first information includes fourth information, and the fourth information is used to indicate that the first site accepts a first request initiated by the second site, and the first request is used to request the first sharing operation.

38. The method according to claim 37, wherein, before the second site receives the first frame sent by the first site, the method further includes: The second site sends a second frame to the first site, and the second frame includes the first request.

39. The method according to any one of claims 32 to 36, wherein, the first information includes fifth information, and the fifth information is used to indicate that the first site actively shares the transmission resource with the second site.

40. The method according to any one of claims 32 to 39, wherein, the method further includes: After receiving the first frame, the second station sends a third frame to the first station, and the third frame contains confirmation information of the first sharing operation.

41. The method according to any one of claims 32 to 40, wherein, the method further includes: the second station sends a fourth frame to the first station, and the fourth frame contains sixth information for indicating one or more of the following: ending the first sharing operation; returning the transmission resource to the first station.

42. The method according to any one of claims 32 to 40, wherein, the method further includes: the second station sends a contention-free end CF-end frame to the first station.

43. The method according to any one of claims 32 to 42, wherein, the first information is carried in a control field.

44. The method according to claim 13, wherein, the control field is a control sub-field in a high throughput HT control field.

45. The method according to any one of claims 32 to 44, wherein, the first frame is a control frame or a data frame.

46. The method according to any one of claims 32 to 45, wherein, the first frame contains seventh information for indicating that the first station has the ability to perform the first sharing operation.

47. The method according to claim 46, wherein, the seventh information is carried in an extremely high throughput media access control EHT MAC capability information field.

48. The method according to claim 31, wherein, the first information is used to indicate that the first station has initiated a first reverse transmission.

49. The method according to claim 48, wherein, the first reverse transmission supports the second station to initiate a target transmission based on the transmission resource, and the target communication device participating in the target transmission does not include the first station.

50. The method according to claim 48 or 49, wherein, the method further includes: after receiving the first frame, the second station sends a fifth frame to the first station, and the fifth frame contains confirmation information of the first reverse transmission.

51. The method according to any one of claims 48 to 50, wherein, the method further includes: the second station sends a sixth frame to the first station, and the sixth frame contains eighth information for indicating one or more of the following: ending the first reverse transmission; returning the transmission resource to the first station.

52. The method according to any one of claims 48 to 51, wherein, the first information is carried in a command and status CAS control field.

53. The method according to any one of claims 48 to 52, wherein, the first frame contains ninth information for indicating that the first station has the ability to perform the first reverse transmission.

54. The method according to claim 53, wherein, The ninth information is carried in the HT extension capability field and / or the high-efficiency HE 6 GHz capability field.

55. The method according to any one of claims 31 to 54, wherein, the first frame includes a tenth information, and the tenth information is used to indicate the duration for which the second station uses the transmission resource.

56. The method according to claim 55, wherein, the tenth information is carried in the duration / identification field.

57. The method according to any one of claims 31 to 56, wherein, the transmission resource is part or all of the transmission opportunity.

58. The method according to any one of claims 31 to 57, wherein, the second station is an access point.

59. The method according to any one of claims 31 to 58, wherein, the first station is associated with the second station.

60. The method according to any one of claims 31 to 59, wherein, the first station is a non-access point station.

61. A communication device, wherein, the communication device is a first station, and the communication device includes: a communication module, configured to send a first frame to a second station, where the first frame includes a first information, and the first information is used to indicate that the second station is shared the transmission resource held by the first station for transmission.

62. The communication device according to claim 61, wherein, the first information includes information related to a first sharing operation, and the first sharing operation is used to share the transmission resource to the second station.

63. The communication device according to claim 62, wherein, the first information includes a second information, and the second information is used to indicate the sharing mode of the transmission resource.

64. The communication device according to claim 63, wherein, the sharing mode of the transmission resource includes one or more of the following: a first sharing mode, in which the first station does not restrict the second station's use of the transmission resource way; a second sharing mode, in which the first station restricts the second station's use of the transmission resource.

65. The communication device according to any one of claims 62 to 64, wherein, the first information includes a third information, and the third information is used to restrict the second station's use of the transmission resource.

66. The communication device according to claim 65, wherein, the third information is used to restrict one or more of the following: the target communication device participating in the target transmission; the communication bandwidth corresponding to the target transmission; the data category corresponding to the target transmission; wherein, the target transmission is the transmission performed by the second station based on the transmission resource.

67. The communication device according to any one of claims 62 to 66, wherein, the first information includes a fourth information, and the fourth information is used to indicate that the first station accepts a first request initiated by the second station, and the first request is used to request the first sharing operation.

68. The communication device according to claim 67, wherein, the communication module is further configured to: before the first site sends a first frame to a second site, receive a second frame sent by the second site, where the second frame includes the first request.

69. The communication device according to any one of claims 62 to 66, wherein, the first information includes fifth information, and the fifth information is used to indicate that the first site actively shares the transmission resource with the second site.

70. The communication device according to any one of claims 62 to 69, wherein, the communication module is further configured to: after sending the first frame, receive a third frame sent by the second site, where the third frame includes confirmation information of the first sharing operation.

71. The communication device according to any one of claims 62 to 70, wherein, the communication module is further configured to: receive a fourth frame sent by the second site, where the fourth frame includes sixth information, and the sixth information is used to indicate one or more of the following: ending the first sharing operation; returning the transmission resource to the first site.

72. The communication device according to any one of claims 62 to 70, wherein, the communication module is further configured to: receive a contention-free end (CF-end) frame sent by the second site.

73. The communication device according to any one of claims 62 to 72, wherein, the first information is carried in a control field.

74. The communication device according to claim 73, wherein, the control field is a control sub-field in a high throughput (HT) control field.

75. The communication device according to any one of claims 62 to 74, wherein, the first frame is a control frame or a data frame.

76. The communication device according to any one of claims 62 to 75, wherein, the first frame includes seventh information, and the seventh information is used to indicate that the first site has the ability to perform the first sharing operation.

77. The communication device according to claim 76, wherein, the seventh information is carried in an extremely high throughput media access control (EHT MAC) capability information field.

78. The communication device according to claim 61, wherein, the first information is used to indicate that the first site has initiated a first reverse transmission.

79. The communication device according to claim 78, wherein, the first reverse transmission supports the second site to initiate a target transmission based on the transmission resource, and the target communication device participating in the target transmission does not include the first site.

80. The communication device according to claim 78 or 79, wherein, the communication module is further configured to: after sending the first frame, receive a fifth frame sent by the second site, where the fifth frame includes confirmation information of the first reverse transmission.

81. The communication device according to any one of claims 78 to 80, wherein, the communication module is further configured to: Receive the sixth frame sent by the second station, where the sixth frame contains eighth information, and the eighth information is used to indicate one or more of the following: End the first reverse transmission; Return the transmission resource to the first station.

82. The communication device according to any one of claims 78 to 81, wherein, The first information is carried in the Command and Status CAS control field.

83. The communication device according to any one of claims 78 to 82, wherein, The first frame contains ninth information, and the ninth information is used to indicate that the first station has the ability to perform the first reverse transmission.

84. The communication device according to claim 83, wherein, The ninth information is carried in the HT extension capability field and / or the High Efficiency HE 6GHz capability field.

85. The communication device according to any one of claims 61 to 84, wherein, The first frame contains tenth information, and the tenth information is used to indicate the duration for which the second station uses the transmission resource.

86. The communication device according to claim 85, wherein, The tenth information is carried in the Duration / ID field.

87. The communication device according to any one of claims 61 to 86, wherein, The transmission resource is part or all of the transmission opportunity.

88. The communication device according to any one of claims 61 to 87, wherein, The second station is an access point.

89. The communication device according to any one of claims 61 to 88, wherein, The first station is associated with the second station.

90. The communication device according to any one of claims 61 to 89, wherein, The first station is a non-access point station.

91. A communication device, wherein, The communication device is a second station, and the communication device includes: A communication module, configured to receive a first frame sent by a first station, where the first frame contains first information, and the first information is used to indicate that the second station is shared the transmission resource held by the first station for transmission.

92. The communication device according to claim 91, wherein, The first information includes information related to a first sharing operation, and the first sharing operation is used to share the transmission resource with the second station.

93. The communication device according to claim 92, wherein, The first information includes second information, and the second information is used to indicate the sharing mode of the transmission resource.

94. The communication device according to claim 93, wherein, The sharing mode of the transmission resource includes one or more of the following: A first sharing mode, in which the first station does not restrict the usage mode of the transmission resource by the second station; A second sharing mode, in which the first station restricts the usage mode of the transmission resource by the second station.

95. The communication device according to any one of claims 92 to 94, wherein, The first information includes third information, and the third information is used to restrict the way the second station uses the transmission resource.

96. The communication device according to claim 95, wherein, the third information is used to restrict one or more of the following: the target communication device participating in the target transmission; the communication bandwidth corresponding to the target transmission; the data category corresponding to the target transmission; wherein the target transmission is the transmission performed by the second station based on the transmission resource.

97. The communication device according to any one of claims 92 to 96, wherein, the first information includes fourth information, and the fourth information is used to instruct the first station to accept the first request initiated by the second station, and the first request is used to request the first sharing operation.

98. The communication device according to claim 97, wherein, the communication module is further configured to: before the second station receives the first frame sent by the first station, send a second frame to the first station, and the second frame includes the first request.

99. The communication device according to any one of claims 92 to 96, wherein, the first information includes fifth information, and the fifth information is used to instruct the first station to actively share the transmission resource with the second station.

100. The communication device according to any one of claims 92 to 99, wherein, the communication device further includes: after receiving the first frame, send a third frame to the first station, and the third frame includes the confirmation information of the first sharing operation.

101. The communication device according to any one of claims 92 to 100, wherein, the communication module is further configured to: send a fourth frame to the first station, and the fourth frame includes sixth information, and the sixth information is used to instruct one or more of the following: end the first sharing operation; return the transmission resource to the first station.

102. The communication device according to any one of claims 92 to 100, wherein, the communication module is further configured to: send a contention-free end CF-end frame to the first station.

103. The communication device according to any one of claims 92 to 102, wherein, the first information is carried in a control field.

104. The communication device according to claim 103, wherein, the control field is a control subfield in a high throughput HT control field.

105. The communication device according to any one of claims 92 to 104, wherein, the first frame is a control frame or a data frame.

106. The communication device according to any one of claims 92 to 105, wherein, the first frame includes seventh information, and the seventh information is used to indicate that the first station has the ability to perform the first sharing operation.

107. The communication device according to claim 106, wherein, the seventh information is carried in an extremely high throughput media access control EHT MAC capability information field.

108. The communication device according to claim 91, wherein, The first information is used to indicate that the first station has initiated a first reverse transmission.

109. The communication device according to claim 108, wherein, the first reverse transmission supports the second station to initiate a target transmission based on the transmission resource, and the target communication devices participating in the target transmission do not include the first station.

110. The communication device according to claim 108 or 109, wherein, the communication module is further configured to: after receiving the first frame, send a fifth frame to the first station, and the fifth frame includes confirmation information of the first reverse transmission.

111. The communication device according to any one of claims 108 to 110, wherein, the communication module is further configured to: send a sixth frame to the first station, and the sixth frame includes eighth information, and the eighth information is used to indicate one or more of the following: ending the first reverse transmission; returning the transmission resource to the first station.

112. The communication device according to any one of claims 108 to 111, wherein, the first information is carried in a Command and Status (CAS) control field.

113. The communication device according to any one of claims 108 to 112, wherein, the first frame includes ninth information, and the ninth information is used to indicate that the first station has the ability to perform the first reverse transmission.

114. The communication device according to claim 113, wherein, the ninth information is carried in an HT extension capability field and / or a High Efficiency (HE) 6 GHz capability field.

115. The communication device according to any one of claims 91 to 114, wherein, the first frame includes tenth information, and the tenth information is used to indicate the duration for which the second station uses the transmission resource.

116. The communication device according to claim 115, wherein, the tenth information is carried in a Duration / ID field.

117. The communication device according to any one of claims 91 to 116, wherein, the transmission resource is part or all of the transmission opportunity.

118. The communication device according to any one of claims 91 to 117, wherein, the second station is an access point.

119. The communication device according to any one of claims 91 to 118, wherein, the first station is associated with the second station.

120. The communication device according to any one of claims 91 to 119, wherein, the first station is a non-access point station.

121. A communication device, wherein, it includes 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 according to any one of claims 1-30 or 31-60.

122. A device, wherein, it includes a processor, which is used to call a program from a memory so that the device executes the method according to any one of claims 1-30 or 31-60.

123. A chip, Characterized in that, It includes a processor for calling a program from a memory, such that a device installed with the chip executes the method according to any one of claims 1-30 or 31-60.

124. A computer-readable storage medium, Characterized in that, A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1-30 or 31-60.

125. A computer program product, Characterized in that, It includes a program, and the program causes a computer to execute the method according to any one of claims 1-30 or 31-60.

126. A computer program, Characterized in that, The computer program causes a computer to execute the method according to any one of claims 1-30 or 31-60.

Images