Wireless communication method and communication device

Abstract

The present application provides a wireless communication method and a communication device. The method comprises: a first device acquires a first data unit sent by a second device to a third device, the first data unit comprising a first field; and the first device sends a second field, the second field being time aligned with and having the same bandwidth as the first field. On the basis of the present application, the first device can send the second field that is time aligned with and has the same bandwidth as the first field. Therefore, the second field can be sent without a TXOP. That is, even if the first device does not obtain a TXOP, the second field can be actively sent on the basis of the first field. Thus, on the basis of the present application, the first device can actively send a signal by means of the second field, avoiding the problem of time delay caused by passive waiting.

Description

Wireless communication method and communication device Technical Field

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

[0002] In some communication systems (such as wireless local area network (WLAN) systems), if the first device does not obtain a transmission opportunity (TXOP), the first device cannot send data and can only receive data. For the first device that does not obtain a TXOP, the owner of the TXOP can provide transmission services to the first device through technologies such as TXOP preemption, coordinated-time division multiple address (C-TDMA), and null data physical layer protocol data unit (NDP) feedback report, thereby meeting the transmission needs of the first device. However, based on the above-mentioned related technologies, the first device can only passively wait for the TXOP owner to provide transmission services in most cases. If the waiting time is long, the transmission delay of the first device will be large or delay jitter may occur.

[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 method for wireless communication is provided, the method comprising: a first device obtains a first data unit sent by a second device to a third device, the first data unit comprising a first field; the first device sends a second field, the second field is time-aligned with the first field and has the same bandwidth.

[0006] In a second aspect, a method for wireless communication is provided, the method comprising: a second device sending a first data unit to a third device, the first data unit comprising a first field; wherein the second field sent by the first device is time-aligned with the first field and has the same bandwidth.

[0007] According to a third aspect, a method for wireless communication is provided, comprising: a third device receiving a first data unit sent by a second device, the first data unit including a first field; the third device receiving a second field sent by the first device; wherein the second field is time-aligned with the first field and has the same bandwidth.

[0008] In a fourth aspect, a communication device is provided, which is a first device and includes: an acquisition unit for acquiring a first data unit sent by a second device to a third device, the first data unit including a first field; a first sending unit for sending a second field, the second field being time-aligned with the first field and having the same bandwidth.

[0009] In a fifth aspect, a communication device is provided, which is a second device and includes: a second sending unit for sending a first data unit to a third device, the first data unit including a first field; wherein the second field sent by the first device is time-aligned with the first field and has the same bandwidth.

[0010] In the sixth aspect, a communication device is provided, which is a third communication device, and includes: a first receiving unit for receiving a first data unit sent by a second device, the first data unit including a first field; a second receiving unit for receiving a second field sent by the first device; wherein the second field is time-aligned with the first field and has the same bandwidth.

[0011] In the seventh 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 methods of the first aspect, the second aspect and the third aspect.

[0012] In an eighth 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.

[0013] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium 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.

[0014] In a tenth 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.

[0015] In the eleventh aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. 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.

[0016] Based on this application, the first device can transmit a second field with the same time-aligned bandwidth as the first field. Therefore, the transmission of the second field is not subject to TXOP restrictions. In other words, even if the first device does not obtain a TXOP, it can still proactively transmit the second field based on the first field. Therefore, based on this application, the first device can proactively transmit a signal using the second field, thereby avoiding the latency issue caused by passive waiting. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0018] FIG2 is an example diagram of the TXOP preemption process.

[0019] FIG3 is a diagram illustrating an example of a C-TDMA process.

[0020] FIG4 is a schematic diagram of the frame format of an NFRP trigger frame.

[0021] FIG5 is a schematic diagram of the format of the common information field in the NFRP trigger frame.

[0022] FIG6 is a schematic diagram of the format of the user information field in the NFRP trigger frame.

[0023] FIG7 is a diagram showing an example of the HE TB feedback NDP frame format.

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

[0025] FIG9 is an example diagram of a method for wireless communication provided in an embodiment of the present application.

[0026] FIG10 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0027] FIG11 is an example diagram of another wireless communication method provided in an embodiment of the present application.

[0028] Figure 12 is a schematic diagram of a PPDU format provided in an embodiment of the present application.

[0029] FIG13 is a schematic diagram of a U-SIG field format provided in an embodiment of the present application.

[0030] FIG14 is a schematic diagram of a UHR-SIG field format provided in an embodiment of the present application.

[0031] FIG15 is a schematic diagram of a setting element format provided in an embodiment of the present application.

[0032] Figure 16 is a format diagram of a second field update request frame provided in an embodiment of the present application.

[0033] Figure 17 is a format diagram of a second field update response frame provided in an embodiment of the present application.

[0034] FIG18 is a schematic diagram of the format of a reporting element provided in an embodiment of the present application.

[0035] FIG19 is a schematic diagram of the format of a UIE reporting frame provided in an embodiment of the present application.

[0036] Figure 20 is a schematic flow chart of the method provided in Example 1 of the present application.

[0037] Figure 21 is a schematic flow chart of the method provided in Example 2 of the present application.

[0038] Figure 22 is a schematic flow chart of the method provided in Example 3 of the present application.

[0039] Figure 23 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0040] Figure 24 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

[0041] Figure 25 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

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

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

[0044] Communication System

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059] Transmission opportunity (TXOP)

[0060] TXOP is a mechanism for allocating radio resources. In some communication systems, such as WLAN, multiple devices need to share limited radio resources. When a device obtains a TXOP, it can continue to send data within the TXOP. Other devices must compete for the channel and obtain a TXOP before they can send data.

[0061] TXOP preemption allows a STA that hasn't yet obtained a TXOP to preempt the remaining TXOP of the current TXOP holder. Specifically, the current TXOP holder can send a trigger frame to other devices to inform them that they can preempt the TXOP. Upon receiving the trigger message, the other device can preempt the TXOP to send data.

[0062] For ease of understanding, the TXOP preemption process is described below using the example shown in FIG2 .

[0063] As shown in Figure 2, the AP obtains a longer TXOP through channel competition. Within the AP's TXOP, after the AP and STA1 shake hands through request to send (RTS) and clear to send (CTS), the AP sends the first data to STA1. After receiving the first data, STA1 sends the first block acknowledgement (BA) frame to the AP. The AP sends a trigger message to devices including STA2. If STA2 has data to send, it can preempt the AP's TXOP. As shown in Figure 2, STA2 has second data to send to the AP at time t1. The second data can be, for example, uplink (UL) low latency (LL) data. Therefore, STA2 preempts the TXOP and obtains a preempted TXOP. Within the preempted TXOP, STA2 can send the second data to the AP. After receiving the second data, the AP can send a second BA corresponding to the second data.

[0064] It can be seen that when the AP does not send a trigger frame, STA2 cannot seize the TXOP and thus cannot transmit data.

[0065] For information about TXOP preemption technology, see the standard document "11-23-0018-01-0 Ultra-High Reliability Technology for Low Latency Support (11-23-0018-01-0uhr-low-latency-support-in-uhr)".

[0066] C-TDMA

[0067] C-TDMA technology allows a primary AP to share a portion of its TXOP duration with a secondary AP, enabling the secondary AP to quickly provide low-latency uplink or downlink transmission services to STAs within its basic service set (BSS). During the shared TXOP, the primary AP cannot use the corresponding medium, meaning it cannot transmit data. After the shared TXOP expires, the primary AP resumes normal uplink and downlink transmissions with STAs within its BSS.

[0068] For ease of understanding, C-TDMA is described below using the example shown in Figure 3. In Figure 3, AP1 is a primary AP and AP2 is a secondary AP.

[0069] Within the TXOP allocated to AP1, AP1 sends a control frame (such as the Collaborative TXOP Indicator (CAP TXOP Request, CTR) frame shown in the figure) to AP2, sharing a portion of the TXOP duration with AP2. Within the time allocated to AP2 (time allocated to AP-2), AP2 sends data twice to the STAs associated with AP2 (STAs associated with AP2) and receives the corresponding BA frames. After the time allocated to AP2, AP2 stops sending data, and AP1 begins sending data to one or more STAs associated with AP1.

[0070] For information about C-TDMA technology, please refer to the standard document "11-23-0261-00-0Ultra-Reliable TDMA for WiFi8 (11-23-0261-00-0UHR-TDMA-for-WiFi-8)".

[0071] Null data packet (NDP) feedback report

[0072] Related technologies (such as the IEEE 802.11ax standard) define NDP feedback reporting. NDP feedback reporting is a multi-user (MU) UL detection mechanism. This mechanism enables the AP to detect the cache status of STAs' uplink data and allocate appropriate transmission resources to STAs that need to send uplink data.

[0073] The MU UL detection mechanism also defines two related frame structures: the NDP feedback report poll (NFRP) trigger frame and the high-efficiency trigger-based null data packet (HE TB) feedback NDP frame. The AP sends the NFRP trigger frame to multiple STAs to trigger them to send back HE TB feedback NDP frames. The AP can determine which STAs need to participate in subsequent MU UL transmissions by parsing the high-efficiency long training field (HE-LTF) in the HE TB feedback NDP frame.

[0074] The following introduces the NFRP trigger frame and HE TB feedback NDP frame.

[0075] Figure 4 is a schematic diagram of the frame format of an NFRP trigger frame. An NFRP trigger frame may include: a frame control field, a duration field, a receive address (RA) field, a transfer address (TA) field, a common info field, a user info list field, a padding field, and a frame check sequence (FCS) field. Figure 4 shows the byte count of each field.

[0076] The format of the common information field in the NFRP trigger frame may be as shown in FIG5 . As shown in Figure 5, the common information field may include: trigger frame type field, uplink length (UL length) field, more trigger frames (more TF) field, carrier sense required (CS required) field, uplink bandwidth (UL BW) field, guard interval and HE-LTF type (GI and HE-LTF type) field, MU-MIMO HE-LTF mode field, number of HE-LTF symbols and midamble periodicity field, uplink space-time block coding (UL STBC) field, LDPC extra symbol segment field, AP transmit power (AP TX power) field, forward error correction code pre-filling factor (pre-FEC padding factor) field, packet extension disambiguation (PE disambiguation) field, uplink spatial reuse (UL spatial reuse) field, Doppler field, uplink HE-SIG-A2 reserved (UL HE-SIG-A2 reserved) field, reserved field, and trigger dependent common info field based on the trigger frame type.

[0077] The Uplink Bandwidth field is used to indicate the bandwidth of the NDP Feedback Report Response. The Uplink Space-Time Block Coding, LDPC Extra Symbol Part, Padding Factor Before Forward Error Correction Code, Packet Extension Disambiguation, Uplink Spatial Multiplexing, and Doppler subfields are reserved. The Number of HE-LTF Symbols and Midamble Period subfields indicate the number of HE-LTF symbols present in the NDP Feedback Report Response and are set to 1. The Guard Interval and HE-LTF Type subfields are set to 2. The Common Information Based on Trigger Frame Type subfield is not present.

[0078] The format of the user information list field in the NFRP trigger frame is shown in Figure 6. The user information list field includes: starting association identifier (starting AID) field, reserved field, feedback type field, uplink target receive power field, number of spatially multiplexed users field

[0079] The Starting Association Identifier field defines the first AID in the range of association identifiers (AIDs) that are intended to respond to the NFRP trigger frame.

[0080] The Feedback Type field is used to indicate the type of feedback information carried by the HE TB Feedback NDP.

[0081] The Uplink Target Received Power field indicates the expected received signal power measured at the AP's antenna connector and averaged over the antenna.

[0082] Spatial multiplexing user number field: indicates the number of STAs multiplexed on the same set of subcarriers in the same resource unit (RU), coded as the number of STAs - 1.

[0083] HE TB Feedback NDP is used to carry NDP feedback report information. Figure 7 shows an example of the HE TB Feedback NDP frame format.

[0084] The HE TB feedback NDP frame may include: legacy short training field (L-STF), legacy long training field (L-LTF), legacy signaling (L-SIG) field, repeated legacy signaling (repeated L-SIG) field, high-efficiency signaling field A (HE-SIG-A), high-efficiency short training field (HE-STF) and HE-LTF field, packet extension (PE).

[0085] The different RU subcarrier set indexes (RU_TONE_SET_INDEX) in the HE-LTF field are used to identify the AIDs and feedback information (FEEDBACK_STATUS) of different STAs. The HE-LTF subcarrier mapping relationship in the HE TB feedback NDP can be referred to in Table 1.

[0086] Table 1

[0087] In Table 1, the information in each grid can indicate the corresponding relationship between the corresponding RU subcarrier set index and the subcarrier that can have energy. Each RU subcarrier set index can correspond to one STA (indicated by AID). When the bandwidth (BW) is 20MHz, the feedback information FEEDBACK_STATUS=1 corresponds to the –113th, –77th, –41st, 6th, 42nd, and 78th subcarriers in the HE-LTF having energy, and the other subcarriers have no energy; the feedback information FEEDBACK_STATUS=0 corresponds to the –112th, –76th, –40th, 7th, 43rd, and 79th subcarriers in the HE-LTF having energy, and the other subcarriers have no energy. When the BW is 40MHz or 80MHz, the 20MHz subcarrier mapping relationship is expanded by 1 times and 3 times respectively, so that more STAs can be mapped (indicated by AID).

[0088] If a first device does not obtain a TXOP, it cannot send data and can only receive data. A first device that has not obtained a TXOP can obtain the TXOP of another device to transmit data through techniques such as TXOP preemption, C-TDMA, and HETB feedback NDP. With TXOP preemption or C-TDMA, the first device can only passively transmit data. Taking TXOP preemption as an example, the first device must receive a trigger frame sent by the TXOP owner before it can preempt the TXOP to send data. However, before the TXOP owner sends a trigger frame, the first device can only passively wait and cannot actively preempt the TXOP. Taking C-TDMA as an example, the first device can only send data after the TXOP owner shares the TXOP with it. Therefore, if the TXOP owner has not yet shared the TXOP, the first device can only passively wait and cannot actively request to share the TXOP. Regarding HETB feedback NDP, this mechanism is only applicable to AP-led MU UL transmission processes. This technique is not applicable to first devices in other transmission processes (such as MU DL, SU UL, or SU DL). Based on this, it is understandable that in many transmission processes, the first device can only passively wait for instructions from the TXOP owner or AP before starting data transmission. This may result in the first device's data transmission request not being discovered in a timely manner, resulting in long data transmission delays and delay jitter.

[0089] Figure 8 is a schematic flowchart of a wireless communication method provided by an embodiment of the present application to address the above-mentioned issues. The method shown in Figure 8 can be performed by a first device, a second device, and a third device. The first device, the second device, and the third device can be associated. The method shown in Figure 8 can include steps S810 to S830.

[0090] Step S810: The second device sends a first data unit to the third device.

[0091] In some embodiments, the second device may be the device that obtains a TXOP. Using the scenario shown in Figure 9 as an example, the second device may obtain a TXOP for a period of time. During the second device's TXOP, the second device and the third device exchange frames. During the TXOP, the second device may send a first data unit to the third device. The third device may reply with a second data unit in response to the first data unit. The second data unit may, for example, include a BA frame.

[0092] In some embodiments, the third device may be the device that obtains a TXOP. That is, the first data unit may be a response data unit. The response data unit may include a BA frame. Taking the scenario shown in Figure 10 as an example, the third device obtains a TXOP for a period of time. Within the third device's TXOP, the third device may send a third data unit to the second device. The second device may reply with the first data unit in response to the third data unit.

[0093] It should be noted that the first data unit may be a physical layer protocol data unit (PPDU). For example, the first data unit may be an ultra high reliability (UHR) PPDU. The UHR PPDU may include a UHR MU PPDU or a UHR ER PPDU.

[0094] The first data unit may include a first field.

[0095] The first data unit may include the first field or may not include the first field.

[0096] In some embodiments, if the owner of a TXOP can provide transmission services to other devices, the first data unit may include a first field. Providing transmission services may include allowing other devices to preempt the TXOP, sharing the TXOP with other devices, and other actions that allow other devices that have not obtained the TXOP to transmit data. For example, if the data exchanged between the second device and the third device is non-low-latency data (e.g., the first data unit carries non-low-latency data), the first data unit may include the first field.

[0097] In some embodiments, if the owner of the TXOP cannot or does not wish to provide transmission services to other devices, the first data unit may not include the first field. For example, if low-latency data is exchanged between the second device and the third device (e.g., the first data unit carries low-latency data), the first data unit may not include the first field.

[0098] Step S820: The first device obtains a first data unit.

[0099] In response to the first device acquiring the first data unit, the first device may determine whether the first data unit includes the first field. If the first data unit includes the first field, step S830 may be performed.

[0100] Step S830: The first device sends the second field to the third device.

[0101] In some embodiments, the timing of the first field can overlap the timing of the second field. That is, the second field can be transmitted within the transmission time of the first field. For example, the timing of the first field and the second field can be aligned. That is, the first field and the second field can be transmitted at the same time. As shown in Figure 9 or Figure 10, the first field and the second field are aligned in time.

[0102] In some embodiments, the bandwidth of the first field and the second field may be the same. That is, the first field and the second field may occupy the same bandwidth. This bandwidth may be the bandwidth corresponding to the TXOP. Within the same bandwidth, the first field and the second field may occupy different subcarriers so that a third device can detect the first field and the second field.

[0103] Based on this application, the first device can transmit a second field with the same time-aligned bandwidth as the first field. Therefore, the transmission of the second field is not subject to TXOP restrictions. In other words, even if the first device does not obtain a TXOP, it can still proactively transmit the second field based on the first field. Therefore, based on this application, the first device can proactively transmit a signal using the second field, thereby avoiding the latency issue caused by passive waiting.

[0104] In some embodiments, the second field may belong to a field set, which may include one or more fields that are time-aligned and have the same bandwidth as the first field. For example, the first device may belong to multiple devices. The multiple devices may each transmit multiple fields. The multiple fields may be time-aligned and have the same bandwidth as the first field. It is understood that a third device may detect multiple fields in the field set, thereby receiving signals transmitted by the multiple devices.

[0105] In some embodiments, the second field may include a data transmission request from the first device. That is, the first device may request data transmission via the second field. In response to the second field, the TXOP owner may provide transmission services to the first device, allowing the first device to transmit data. For example, if a third device is the TXOP owner, then, in response to receiving the second field, the third device may provide transmission services to the first device. Alternatively, if the second device is the TXOP owner, the third device may forward the second field or information obtained via the second field to the TXOP owner, allowing the second device to provide transmission services to the first device.

[0106] This application does not limit the manner in which the TXOP owner provides transmission services to the first device. For example, the TXOP owner may send a trigger frame to the first device so that the first device preempts the TXOP. Alternatively, the TXOP owner may allocate the TXOP to the first device via C-TDMA.

[0107] As can be seen, the first device can actively request to send data through the second field, allowing the TXOP owner to accurately provide transmission services to the first device. It can be understood that when the first device has data to send, the first device can send a data transmission request through the second field as quickly as possible to transmit the data, thereby avoiding the large delay and delay jitter caused by passively waiting for the TXOP owner to provide services to the first device. In addition, compared to related technologies that require the exchange of multiple signaling messages, the present application can detect the device's data transmission request by receiving the second field. Therefore, the present application can also reduce signaling overhead.

[0108] In some embodiments, when the first device generates data to be sent, the first device may obtain a first data unit. It is understood that if the first device does not generate data to be sent, the first device may not obtain the first data unit, thereby reducing energy consumed by obtaining the first data unit and further reducing energy consumption of the first device.

[0109] In some embodiments, the data transmission requirement of the first device indicated by the second field may include a low-latency data transmission requirement. Continuing with Figure 9 , the first device generates a low-latency data unit to be transmitted at time t2. After time t2, the first device may obtain the first data unit and transmit the second field. The second field may indicate a low-latency data transmission request at time t2.

[0110] Compared to low-latency service discovery methods in related technologies, this application can proactively notify a specific site of a low-latency service transmission request, allowing the specific site to accurately provide transmission services for that site. Therefore, this application can improve the efficiency of discovering low-latency services and reduce signaling overhead, thereby effectively reducing the latency and latency jitter during the transmission of low-latency services at the cost of lower signaling overhead.

[0111] In some embodiments, the second field may be used to indicate the identity information of the first device. The first field may be used to indicate the identity of the second device. The identity information may include, for example, an AID.

[0112] Based on this, both the first field and the second field can be carried in a user identification extension (UIE) field indicating identity information. The UIE field may indicate different information for the first and second fields. The first device may belong to multiple devices, and the multiple devices may each send their corresponding fields through the UIE field.

[0113] After receiving the second field, the third device can parse the second field to obtain the identity information of the first device. That is, the third device can determine that the device sending the second field is the first device based on the identity information indicated in the second field. If the second field indicates the transmission requirements of the device sending the second field, the identity information indicated in the second field can be used to determine that the second field indicates the transmission requirements of the first device, thereby facilitating the TXOP owner to provide targeted services to the first device. Similarly, the first field can be used to indicate the identity information of the first device.

[0114] 9 , when the third device detects the UIE field, it can determine that the senders of the two UIE fields are the first device and the second device respectively through the two detected UIE fields (represented by UIE(1+2) in FIG9 ).

[0115] Taking Figure 11 as an example, the second device can send the first field, the first device can send the second field, and the fourth device can send the fifth field. When the third device detects the UIE field, it can determine that the sending devices of the three received UIEs (represented by UIE (1+2+4) in Figure 9) are the first device, the second device, and the fourth device, respectively, based on the identity information contained in the UIE field.

[0116] It should be noted that the UIE field is only a name for the field, and the field carrying the first field and the second field may also have other names, and this application does not impose any restrictions on this.

[0117] It should be noted that, in some embodiments, the UIE field may have other functions. For example, the UIE field may increase receiver processing time (similar to the function of the PE field).

[0118] The identity information of the first device can be indicated by the subcarrier set occupied by the second field. The subcarrier set can include one or more subcarriers. The subcarrier can be an RU subcarrier. The AP can set different subcarrier sets for different devices. For example, the identity information of the second device can be indicated by the subcarrier set occupied by the first field. Exemplarily, the mapping relationship between identity information and subcarrier set can be shown in Table 1.

[0119] Taking the case where both the second field and the first field are carried in the UIE field as an example, the third device can determine the identity information of the device that sends the UIE field by detecting the energy of the subcarrier. As an implementation method, if the third device detects that the subcarriers in the first subcarrier set have energy, it can be determined that the device corresponding to the first subcarrier set has sent the UIE field. For example, if the third device detects energy in the subcarriers in the subcarrier set corresponding to the first device, the third device can determine that the first device has sent the UIE field. Alternatively, if the third device detects energy in the subcarriers in multiple subcarrier sets, the third device can determine that multiple devices corresponding to multiple subcarrier sets have all sent UIE fields.

[0120] In some embodiments, the third device may detect subcarrier energy within a first time window to determine the identity information of the device that sent the UIE field. If the third device detects subcarrier energy during part or all of the first time window, it may determine that the corresponding device sent the UIE field. The first time window may, for example, include the time period for receiving the first field.

[0121] There may be a transmission delay between different devices and the third device. Therefore, the UIE fields sent by different devices may not reach the third device at the same time. That is, when multiple UIE fields are sent at the same time, it is difficult for the third device to detect that the subcarriers corresponding to the multiple UIE fields have energy at the same time. Based on the present application, as long as the third device detects that the subcarriers corresponding to the UIE field have energy within the first time window, it can be considered that the corresponding device has sent the UIE field, thereby making the reception of the UIE field more flexible and accurate. In some embodiments, the first field can be located at the end of the first data unit. When the first field is located at the end of the first data unit, the first device can have more time to detect the first data unit, prepare for the transmission of the second field, etc., thereby simplifying the transmission of the second field.

[0122] The first data unit may also include a third field. The third field may precede the first field. The third field may be used to reserve time for the first device to switch to the transmitting state. For example, within the time specified in the third field, the first device may switch from the receiving state to the transmitting state. It is understood that the third field may reserve time for the first device to prepare for sending the second field. The third field may also be referred to as a reverse interval (RI) field.

[0123] In some embodiments, the third field can be connected to the first field, so that the first device can send the second field as soon as possible after switching to the sending state, thereby reducing the time it takes for the first device to switch to the sending state and reducing the energy consumption of the first device in the sending state.

[0124] As mentioned above, the third field is primarily used to reserve a period of time. Therefore, this application does not limit the signal carried in the third field. For example, the third field can carry a random signal. Alternatively, the third field does not carry a valid signal. In other words, the third field may not send any signal, or the third field may carry an invalid signal. Compared to other signals, the generation process of a random signal or an invalid signal is simpler, thereby reducing the complexity of generating the third field.

[0125] The following uses a UHR PPDU as an example, and in conjunction with Figure 12, illustrates the PPDU format including the UIE field and / or the RI field. As shown in Figure 12, the UIE field is located at the end of the PPDU. The length of the UIE field can be variable. The RI field can be located before the UIE field. The length of the RI field can be variable.

[0126] As shown in Figure 12, the UHR PPDU may also include one or more of the following fields: L-STF, L-LTF, L-SIG field, repeated L-SIG (RL-SIG) field, universal signaling (U-SIG) field, UHR signaling field, UHR short training field (UHR short training field, UHR-STF), and UHR long training sequence (UHR long training field, UHR-LTF). They are described below.

[0127] L-STF can be used for PPDU discovery and preliminary time and frequency synchronization.

[0128] L-LTF can be used for preliminary channel estimation and further time-frequency alignment.

[0129] L-SIG can be used to carry information required for parsing PPDU.

[0130] RL-SIG may be a repetition of L-SIG.

[0131] U-SIG can be used to carry information required to parse PPDU.

[0132] The UHR-SIG field may be used to carry information related to DL MU transmission. The UHR-SIG field is just one name for the field, and the field used to carry information related to DL MU transmission may also be called by other names.

[0133] The UHR-STF field is used to assist the receiver in performing preliminary time and frequency synchronization, and to assist the receiver in detecting the reliability of the PE subfield.

[0134] The UHR-LTF field is used by the receiver for channel estimation.

[0135] As described above, the first data unit may include the first field or may not include the first field. If the first data unit includes the first field, the first device can send the second field. If the first data unit does not include the first field, the first device cannot send the second field.

[0136] In some embodiments, the second device may send first indication information. The first indication information may be used to indicate whether the first data unit includes the first field.

[0137] The first device may determine whether to send the second field based on the received first indication information.

[0138] The first indication information may be included in the indication data unit. For example, the first field may be included in a preamble of the indication data unit. The first device may obtain the first indication information by detecting the preamble of the indication data unit.

[0139] In some embodiments, the first data unit may be an indication data unit or a response data unit to an indication data unit. In other words, the first data unit may include the first indication information. Alternatively, if the first data unit is a response data unit, the PPDU to which the first data unit responds may include the first indication information.

[0140] Exemplarily, the indication data unit may include a fourth field. The fourth field may be used to indicate whether the first field exists in the current indication data unit and / or whether the first field exists in the response data unit. For example, the fourth field may be used to indicate one or more of the following information: the indication data unit includes the first field; the response data unit of the indication data unit includes the first field; both the indication data unit and the response data unit of the indication data unit include the first field; and neither the indication data unit nor the response data unit of the indication data unit includes the first field.

[0141] Taking the first field carried in the UIE field as an example, the value of the fourth field can be as shown in Table 2.

[0142] Table 2

[0143] In some embodiments, the first indication information may further indicate whether the first data unit includes a third field. Taking the third field carried in the RI field as an example, the value of the fourth field may be as shown in Table 3.

[0144] Table 3

[0145] In some embodiments, the first indication information may be carried in a U-SIG field. For example, the U-SIG field may include a UIE (presence of UIE) field. If the UIE field indicates the presence of the UIE field, the first data unit may include the first field. If the UIE field indicates the absence of the UIE field, the first data unit may not include the first field.

[0146] Figure 13 is a schematic diagram of a U-SIG field format provided in an embodiment of the present application. As shown in Figure 13, the U-SIG field may include whether a UIE field exists. The U-SIG field may also include one or more of the following fields: a physical (PHY) version identifier field, a bandwidth field, an uplink / downlink (UL / DL) field, a basic service set color (BSS color) field, a TXOP field, a disregard field, a validate field, a PPDU type and compression mode field, a punctured channel information field, a modulation and coding scheme (MCS) field of the UHR-SIG field, the number of UHR-SIG symbols in the UHR-SIG field, a cyclic redundancy check (CRC), and a tail field. Some of the fields are described below.

[0147] The PHY version identification field is used to indicate different PHY versions.

[0148] The Bandwidth field is used to indicate the bandwidth of the PPDU.

[0149] The UL / DL field is used to indicate whether the PPDU is transmitted in the uplink or downlink direction.

[0150] The TXOP field is used to indicate the duration of the TXOP and the value of the network allocation vector (NAV).

[0151] Ignore fields are reserved fields that are ignored.

[0152] Validation Fields Reserved fields for validation.

[0153] The PPDU Type and Compression Mode fields are used to indicate the type of PPDU.

[0154] The channel puncturing information field is used to indicate the location and mode of PPDU puncturing.

[0155] The CRC field is used to check the cyclic redundancy code of B0-B41 in the U-SIG field.

[0156] The tail field is a field for terminating the grid of the convolutional decoder.

[0157] In some embodiments, the first indication information may be carried in the UHR-SIG field. As described above, the UHR-SIG field may be used to carry information related to DL MU transmission. For example, the UHR-SIG field may include whether a UIE field is present. For an explanation of whether a UIE field is present, refer to the above.

[0158] Figure 14 is a schematic diagram of a UHR-SIG field format provided by an embodiment of the present application. As shown in Figure 14, the UHR-SIG field may include a common field and a user specific field. The common field may include whether a UIE field exists. The UHR-SIG field may also include one or more of the following fields: Spatial Reuse field, Guard Interval field and Additional Long Training Field Size (GI+LTF size) field, Number of UHR-LTF symbols field, LDPC additional symbol segmentation field, Forward Error Correction Code front filling factor, Packet extension disambiguation field, Number of non-OFDMA users field. Some of the fields are introduced below.

[0159] The Spatial Multiplexing field is used to indicate whether spatial multiplexing mode is allowed during the transmission of this PPDU.

[0160] The GI+LTF Size field is used to indicate the duration of the GI and the type of UHR-LTF.

[0161] The LDPC Extra Symbol Segment field is used to indicate whether the LDPC Extra Symbol Segment occurs.

[0162] The number of non-OFDMA users field is used to indicate the number of all non-OFDMA users.

[0163] As mentioned above, the identity information of the first device can be indicated by the subcarrier set occupied by the second field. The subcarrier set occupied by the second field can be configured by a setup element in the first frame. For example, the fourth device can indicate the subcarrier set used by the opposite device to send the UIE field through the setup field. The fourth device can be an AP. The fourth device can be the same as the second device or the third device. In the case where both the first field and the second field are carried in the UIE field, the setup element can also be called a UIE setup element.

[0164] The setting element may include a subcarrier set identification field. The identification may include, for example, individual subcarrier identifications and a subcarrier set index field. The subcarrier set index may represent one or more subcarriers in the subcarrier set through an index.

[0165] The setting element may configure the subcarrier set occupied by the corresponding UIE field for the first device through the identification field of the subcarrier set. For example, when the first device sends the second field, the subcarriers in the subcarrier set occupied by the UIE field configured for the first device may have energy, while other subcarriers may not have energy.

[0166] Figure 15 is a schematic diagram of a setup element format provided by an embodiment of the present application. As shown in Figure 15, the setup element may include a subcarrier set index. The setup element may also include one or more of the following fields: an element ID field, an element ID extension field, and a length field. These are described below.

[0167] The element identifier field is used to identify the element as a setting element. The value of the element identifier field can be 255, for example.

[0168] The element identifier extension and the element identifier field together identify the setting element. The value of the element identifier extension field can be any integer between 136 and 255.

[0169] The length field may be used to indicate the number of bytes in the element in addition to the element identifier field and the length field.

[0170] As an implementation, the first frame may include a frame sent by the AP when the STA initially accesses the network. For example, the first frame may include one or more of the following: a probe response frame, an association response frame, or a reassociation response frame.

[0171] The first frame including the setting element may be an action frame. The first frame may belong to a newly defined action frame. For ease of description, the newly defined action frame may be referred to as a UIE action frame. The UIE action frame may be used for the management of the UIE field. The UIE action frame may be distinguished from other action frames by the category field. For example, a value of 39 in the category field may indicate that the action frame is a UIE action frame. Different UIE action frames (i.e., subtypes of UIE action frames) may be indicated by the UIE action field. For example, a value of 1 in the UIE action field in the first frame may indicate that the UIE action is a UIE update request frame.

[0172] As an implementation manner, the first frame may be a newly added frame, which may be called, for example, a second field update request frame or a UIE update request (UIE update request) frame.

[0173] Figure 16 is a schematic diagram of the format of a second field update request frame provided by an embodiment of the present application. As shown in Figure 16, the second field update request frame may include a settings element. The settings element may be located within the action field. The action field may also include: a type field and / or a UIE action field.

[0174] The Type field is used to indicate the specific type of the action frame. The value of this field is any integer between 39 and 125. For example, a value of 39 in the Type field indicates that the action frame is a UIE action frame type.

[0175] The UIE Action field is used to indicate the subtype of the UIE Action frame. For example, a value of 1 in the UIE Action field may indicate that the action frame is a UIE Update Request frame.

[0176] The second field update request frame may include one or more of the following fields: a frame control field, a duration field, a receiving address (RA) field, a transport address (TA) field, a sequence control field, a high throughput (HT) control field, an action field, and an FCS field. These fields are described below.

[0177] The frame control field is used to indicate the version and specific type of MAC.

[0178] The duration field is used to indicate the length of the TXOP.

[0179] The sequence control field is used to indicate the sequence number of the frame.

[0180] The second field update response frame corresponding to the second field update request frame can be used to respond to the update request of the second field. For example, the second field update response frame can be used to feedback whether the subcarrier set of the second field is successfully configured.

[0181] In some embodiments, the second field update response frame may include a response status indication field. The response status indication field may be used to indicate whether the subcarrier set configuration was successful. For example, a value of 1 in the response status indication field may indicate that the subcarrier set configuration was successful, while a value of 0 in the response status indication field may indicate that the subcarrier set configuration failed. Alternatively, a value of 0 in the response status indication field may indicate that the subcarrier set configuration was successful, while a value of 1 in the response status indication field may indicate that the subcarrier set configuration failed.

[0182] The second field update response frame may also be a UIE action frame.

[0183] Figure 17 is a schematic diagram of the format of a second field update response frame provided by an embodiment of the present application. As shown in Figure 17, the second field update response frame may include a response status indication field. The response status indication field may be located within the action field. The action field may also include: a type field and / or a UIE action field.

[0184] The Type field is used to indicate the specific type of the action frame. The value of this field is any integer between 39 and 125. For example, a value of 39 in the Type field indicates that the action frame is a UIE action frame type.

[0185] The UIE Action field is used to indicate the subtype of the UIE Action frame. For example, a value of 2 in the UIE Action field may indicate that the action frame is an update response frame.

[0186] As shown in Figure 17, the Update Response frame may include one or more of the following fields: Frame Control Field, Duration Field, RA Field, TA Field, Sequence Control Field, HT Control Field, Action Field, and FCS Field. For descriptions of each field, refer to the corresponding field in the second field of the Update Request frame.

[0187] The second field update response frame may also include one or more of the following fields: frame control field, duration field, RA field, TA field, sequence control field, high throughput control field, action field, and FCS field. For the meanings of these fields, refer to the meanings of the corresponding fields in Figure 16.

[0188] As described above, other devices may also transmit fields that are time-aligned with the first field and have the same bandwidth. Therefore, a third device receiving the first data unit may detect a field set. The field set may include one or more detected fields that are time-aligned with the first field and have the same bandwidth. If only the first device transmits the second field, the field set includes the first field and the second field. If multiple devices transmit fields that are time-aligned with the first device and have the same bandwidth, the field set includes multiple fields and the first field. The multiple fields may correspond one-to-one to the multiple devices.

[0189] In some embodiments, the third device may send a second indication message. The second indication message may be used to indicate that the first device sent the second field. Alternatively, the second indication message may be used to indicate whether the third device detected the second field. Alternatively, the second indication message may be used to indicate whether the third device detected a field set. Alternatively, the second indication message may be used to indicate a detection result of a UIE field. The detection result may include the number of fields in the detected field set and / or identity information corresponding to the detected field.

[0190] In some embodiments, the second indication information may be carried in a response data unit.

[0191] In some embodiments, the subcarrier set occupied by the detected second field is indicated by a report element in the second frame. In other words, the report element can be used to indicate the detected field set. Alternatively, the report element can be used to indicate the subcarrier set occupied by the detected field set. When the second field is carried in the UIE field, the report element can also be called a UIE report element.

[0192] Exemplarily, the reporting element includes one or more of the following fields: a number of subcarrier set indexes field and a subcarrier set index list field. The number of subcarrier set indexes field may be used to indicate the number of subcarrier sets occupied by a field set. The subcarrier set index list may be used to indicate the subcarrier sets occupied by a field set. The number of subcarrier sets included in the subcarrier set index list is consistent with the number indicated by the number of subcarrier set indexes field.

[0193] Figure 26 is a schematic diagram of the format of a reporting element provided in an embodiment of the present application. As shown in Figure 26, the reporting element may include a number of subcarrier set index fields and a subcarrier set index list field. The reporting element may also include one or more of the following fields: an element identifier field, an element identifier extension field, and a length field.

[0194] The element identifier field is used to identify the element as a setting element. The value of the element identifier field can be 255, for example.

[0195] The element identifier extension and the element identifier field together identify the setting element. The value of the element identifier extension field can be any integer between 136 and 255.

[0196] The length field may be used to indicate the number of bytes in the element in addition to the element identifier field and the length field.

[0197] As an implementation method, the second frame may include a report frame. The report frame may also be referred to as a UIE report frame. The report frame may be a UIE action frame described above. Figure 19 is a schematic diagram of the format of a UIE report frame provided in an embodiment of the present application. As shown in Figure 19, the UIE report frame may include a report element. The report element may be located within an action field. The action field may further include: a type field and / or a UIE action field.

[0198] The Type field is used to indicate the specific type of the action frame. The value of this field is any integer between 39 and 125. For example, a value of 39 in the Type field indicates that the action frame is a UIE action frame type.

[0199] The UIE action field is used to indicate the subtype of the UIE action frame. For example, a value of 3 in the UIE action field may indicate that the action frame is a UIE reporting frame.

[0200] As shown in Figure 19, the UIE reporting frame may include one or more of the following fields: frame control field, duration field, RA field, TA field, sequence control field, HT control field, action field, and FCS field. For descriptions of each field, refer to the corresponding field in the second field update request frame.

[0201] For ease of understanding, the present application is described below with reference to Examples 1 to 3.

[0202] Example 1

[0203] FIG20 is a schematic flow chart of the method provided in Example 1. The method shown in FIG20 can be performed by the AP, STA1, and STA2. The AP has already associated with both STA1 and STA2. The method shown in FIG20 includes steps S2010 to S2070.

[0204] Step S2010: Within the AP's TXOP, the AP transmits downlink non-low-latency data to STA1.

[0205] In step S2020, STA1 replies with a BA frame to the AP to confirm the success or failure of the transmission in step S2010.

[0206] Because the data being transmitted between the AP and STA1 is not a low-latency service, the AP can indicate in the U-SIG field or UHR-SIG field of the PPDU in step S2010 that the PPDU sent by STA1 to the AP may include the RI field and the UIE field. For example, the PPDU carrying the BA frame in step S2020 may include the RI field and the UIE field.

[0207] It can be understood that, based on step S2020, other STAs may be allowed to send the UIE field so that the AP can identify UIEs from multiple STAs that may exist in the UIE field and perform corresponding operations.

[0208] In the PPDU in step S2020, the UIE(1) field identifies the AID of STA1.

[0209] In step S2030, STA2 sends a UIE(2) field that is aligned with the UIE(1) field and identifies its own AID.

[0210] At the time shown in the figure, STA2 has received data for a low-latency service that needs to be transmitted to the AP. However, at this time, STA2 has not yet obtained a TXOP, so it can only receive PPDUs and cannot send PPDUs. When STA2 receives the PPDU (i.e., the PPDU in step S2020) that carries the BA frame and contains the RI and UIE fields sent by STA1, it can find that the end of the PPDU contains the RI field and the UIE field through a specific identification field. In order to send uplink low-latency data as quickly as possible, STA2 completes the switch from the receiving state to the transmitting state within the time of the RI field, and sends a UIE (2) field that is aligned with the UIE (1) field and identifies its own AID to inform the AP that STA2 needs to preempt the next TXOP.

[0211] In step S2040, the AP parses the UIE field to obtain UIE(1) and UIE(2), and then learns that STA2 needs to send uplink low-latency data.

[0212] Step S2050: The AP sends a trigger frame to STA2.

[0213] Step S2060: Based on the triggering of the trigger frame, STA2 sends uplink low-latency data to the AP.

[0214] Step S2070: In response to step S2060, the AP replies with a BA frame.

[0215] Based on steps S2050 to S2070, STA2 completes the transmission of uplink low-latency data.

[0216] Example 2

[0217] FIG21 is a schematic flow chart of the method provided in Example 2. The method shown in FIG21 can be performed by the AP, STA1, and STA2. The AP has already associated with both STA1 and STA2. The method shown in FIG21 includes steps S2110 to S2170.

[0218] Step S2110: Within the AP's TXOP, the AP transmits non-low-latency data to STA1.

[0219] Because the data transmission being performed by the AP is not a low-latency service, the PPDU sent by the AP to STA1 can contain the RI and UIE(0) fields. This allows other STAs to send the UIE field, and allows STA1 to identify the UIEs that may exist in the UIE field from multiple STAs and perform corresponding operations. The UIE(0) field identifies the AP's AID.

[0220] In step S2120, STA2 sends a UIE(2) field that is aligned with the UIE(0) field and identifies its own AID.

[0221] At the time shown in the figure, STA2 has received data for an uplink low-latency service that needs to be transmitted to the AP. However, at this moment, STA2 has not yet obtained a TXOP, so it can only receive PPDUs and cannot send PPDUs. When STA2 receives the PPDU containing the RI and UIE fields sent by the AP, it finds that the end of the PPDU contains the RI and UIE fields through a specific identification field. Therefore, in order to send uplink low-latency data as quickly as possible, STA2 completes the switch from the receiving state to the transmitting state within the time of the RI field, and then sends a UIE(2) field that is aligned with the UIE(0) field and identifies its own AID to inform STA1 that STA2 needs to preempt the next TXOP.

[0222] In step S2130, STA1 parses the UIE field and obtains UIE(0) and UIE(2).

[0223] From step S2130 , STA1 learns that STA2 needs to send uplink low-latency data.

[0224] In step S2140, STA1 sends a PPDU. This PPDU can be used to inform the AP of STA2's low-latency data transmission requirements.

[0225] Step S2150: The AP sends a trigger frame to STA2.

[0226] Step S2160: Triggered by the trigger frame of step S2150, STA2 sends uplink low-latency data.

[0227] In step S2170 , the AP replies to STA2 with the BA frame corresponding to step S2160 to confirm whether the transmission in step S2160 is successful or failed.

[0228] Based on steps S2150 to S2170 , STA2 completes the transmission of uplink low-latency data to the AP.

[0229] Example 3

[0230] FIG22 is a schematic flow chart of the method provided in Example 3. The method shown in FIG22 can be performed by the AP, STA1, STA2, and STA3. The AP has already associated with STA1, STA2, and STA3. The method shown in FIG22 includes steps S2210 to S2290.

[0231] Step S2210: In the AP's TXOP, the AP transmits downlink non-low-latency data to STA1.

[0232] In step S2220 , STA1 replies with a BA frame to the AP to confirm the success or failure of the transmission in step S2210 .

[0233] Since the data transmission between the AP and STA1 is a non-low-latency service, the AP can indicate in the U-SIG field or UHR-SIG field of the PPDU it sends that the PPDU sent by STA1 to the AP may contain the RI and UIE fields. For example, the PPDU carrying the BA frame in step S2220 may contain the RI and UIE fields. In other words, the AP allows other STAs to send the UIE field so that the AP can identify the UIEs from multiple STAs that may exist in the UIE field and perform corresponding operations. The UIE(1) field in Figure 22 identifies the AID of STA1.

[0234] In step S2230, STA2 sends a UIE(2) field that is aligned with the UIE(1) field and identifies its own AID.

[0235] In step S2240, STA3 sends a UIE(3) field that is aligned with the UIE(1) field and identifies its own AID.

[0236] As shown in Figure 22, STA2 and STA3 each received a low-latency service data that needed to be transmitted to the AP at the time shown. However, STA2 and STA3 have not yet obtained a TXOP, so they can only receive PPDUs. After STA2 and STA3 receive the PPDU containing the BA frame sent by STA1 and containing the RI and UIE fields, they find that the end of the PPDU contains the RI and UIE fields through a specific identification field. Based on this, in order to send uplink low-latency data as quickly as possible, STA2 and STA3 complete the switch from the receiving state to the transmitting state within the time of the RI field, and respectively send a UIE(2) field and UIE(3) field that are aligned with the UIE(1) field and identify their own AID to inform the AP: STA2 and STA3 both need to seize the next TXOP.

[0237] In step S2250, the AP parses the UIE field and obtains UIE(1), UIE(2), and UIE(3).

[0238] According to step S2250, the AP may know that STA2 and STA3 need to send uplink low-latency data.

[0239] In step S2260 , the AP sends a trigger frame to STA2 and STA3.

[0240] Step S2270: Triggered by the trigger frame, STA2 sends low-latency data.

[0241] Step S2280: Triggered by the trigger frame, STA3 sends low-latency data.

[0242] In step S2290 , the AP sends a BA frame to STA2 and STA3.

[0243] Based on steps S2260 to S2290, STA2 and STA3 complete the transmission of their respective uplink low-latency data.

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

[0245] FIG23 is a schematic structural diagram of a communication device 2300 provided in an embodiment of the present application. The communication device 2300 is a first device and includes an acquiring unit 2310 and a first sending unit 2320.

[0246] The acquiring unit 2310 is configured to acquire a first data unit sent by the second device to the third device, where the first data unit includes a first field.

[0247] The first sending unit 2320 is configured to send a second field, where the second field is time-aligned with the first field and has the same bandwidth.

[0248] In some embodiments, the second field is used to indicate identity information of the first device.

[0249] In some embodiments, the identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

[0250] In some embodiments, the second device or the third device is a device that obtains a TXOP.

[0251] In some embodiments, the first data unit further includes a third field, and the third field is used to reserve time for the first device to switch to the sending state.

[0252] In some embodiments, the third field carries a random signal, or the third field does not carry a valid signal.

[0253] In some embodiments, the communication device is further used to: obtain first indication information; wherein the first indication information is used to indicate whether the first data unit includes the first field.

[0254] In some embodiments, the first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit to the indication data unit.

[0255] In some embodiments, the indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: the indication data unit includes the first field; the response data unit of the indication data unit includes the first field; the indication data unit and the response data unit of the indication data unit both include the first field; the indication data unit and the response data unit of the indication data unit do not include the first field.

[0256] In some embodiments, the first indication information is carried in a U-SIG field or a UHR-SIG field, where the UHR-SIG field is used to carry information related to DL MU transmission.

[0257] In some embodiments, the subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

[0258] In some embodiments, the setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

[0259] In some embodiments, the first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

[0260] In some embodiments, the first frame is an action frame.

[0261] In some embodiments, the second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

[0262] In some embodiments, the detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

[0263] In some embodiments, the second field belongs to a field set, and the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: a number of subcarrier set index fields, used to indicate the number of subcarrier sets occupied by the field set; a subcarrier set index list field, used to indicate the subcarrier set occupied by the field set.

[0264] In some embodiments, the second frame is an action frame.

[0265] In some embodiments, the second field is used to indicate data transmission requirements of the first device.

[0266] In some embodiments, the data transmission requirements include: low-latency data transmission requirements.

[0267] In some embodiments, the data associated with the first data unit is non-low-latency data.

[0268] In some embodiments, the first field is located at the end of the first data unit.

[0269] In some embodiments, the first data unit is a PPDU.

[0270] In an optional embodiment, the first sending unit 2320 may be a transceiver 2630. The acquiring unit 2310 may be a processor 2610. The communication device 2300 may further include a memory 2620, as specifically shown in FIG26 .

[0271] Figure 24 is a schematic structural diagram of a communication device 2400 provided in an embodiment of the present application. Communication device 2300 is a second device. Communication device 2400 includes a first transmitting unit 2410.

[0272] The first sending unit 2410 is used to send a first data unit to a third device, where the first data unit includes a first field; wherein a second field sent by the first device is time-aligned with the first field and has the same bandwidth.

[0273] In some embodiments, the second field is used to indicate identity information of the first device.

[0274] In some embodiments, the identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

[0275] In some embodiments, the second device or the third device is a device that obtains a TXOP.

[0276] In some embodiments, the communication device is further used to: receive second indication information; wherein the second indication information is used to indicate that the first device has sent the second field.

[0277] In some embodiments, the first data unit further includes a third field, and the third field is used to reserve time for the first device to switch to the sending state.

[0278] In some embodiments, the third field carries a random signal, or the third field does not carry a valid signal.

[0279] In some embodiments, the communication device is further used to: send first indication information; wherein the first indication information is used to indicate whether the first data unit includes the first field.

[0280] In some embodiments, the first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit to the indication data unit.

[0281] In some embodiments, the indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: the indication data unit includes the first field; the response data unit of the indication data unit includes the first field; the indication data unit and the response data unit of the indication data unit both include the first field; the indication data unit and the response data unit of the indication data unit do not include the first field.

[0282] In some embodiments, the first indication information is carried in a U-SIG field or a UHR-SIG field, where the UHR-SIG field is used to carry information related to DL MU transmission.

[0283] In some embodiments, the subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

[0284] In some embodiments, the setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

[0285] In some embodiments, the first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

[0286] In some embodiments, the first frame is an action frame.

[0287] In some embodiments, the second field update response frame corresponding to the second field update request frame includes: a response status indication field, wherein the response status indication field is used to indicate whether the subcarrier set is configured successfully.

[0288] In some embodiments, the detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

[0289] In some embodiments, the second field belongs to a field set, and the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: a number of subcarrier set index fields, used to indicate the number of subcarrier sets occupied by the field set; a subcarrier set index list field, used to indicate the subcarrier set occupied by the field set.

[0290] In some embodiments, the second frame is an action frame.

[0291] In some embodiments, the second field is used to indicate data transmission requirements of the first device.

[0292] In some embodiments, the data transmission requirements include: low-latency data transmission requirements.

[0293] In some embodiments, the data associated with the first data unit is non-low-latency data.

[0294] In some embodiments, the first field is located at the end of the first data unit.

[0295] In some embodiments, the first data unit is a PPDU.

[0296] In an optional embodiment, the second sending unit 2410 may be a transceiver 2630. The communication device 2400 may further include a processor 2610 and a memory 2620, as specifically shown in FIG26 .

[0297] FIG25 is a schematic structural diagram of a communication device 2500 provided in an embodiment of the present application. The communication device 2500 is a third device and includes a first receiving unit 25120 and a second receiving unit 2520.

[0298] The first receiving unit 2510 is used to receive a first data unit sent by a second device, where the first data unit includes a first field.

[0299] The second receiving unit 2520 is configured to receive a second field sent by the first device.

[0300] The second field is time-aligned and has the same bandwidth as the first field.

[0301] In some embodiments, the second field is used to indicate identity information of the first device.

[0302] In some embodiments, the identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

[0303] In some embodiments, the second device or the third device is a device that obtains a TXOP.

[0304] In some embodiments, the communication device is further used to: send second indication information to the second device; wherein the second indication information is used to indicate that the first device has sent the second field.

[0305] In some embodiments, the first data unit further includes a third field, and the third field is used to reserve time for the first device to switch to the sending state.

[0306] In some embodiments, the third field carries a random signal, or the third field does not carry a valid signal.

[0307] In some embodiments, the communication device is further used to: send first indication information; wherein the first indication information is used to indicate whether the first data unit includes the first field.

[0308] In some embodiments, the first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit to the indication data unit.

[0309] In some embodiments, the indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: the indication data unit includes the first field; the response data unit of the indication data unit includes the first field; the indication data unit and the response data unit of the indication data unit both include the first field; the indication data unit and the response data unit of the indication data unit do not include the first field.

[0310] In some embodiments, the first indication information is carried in a U-SIG field or a UHR-SIG field, where the UHR-SIG field is used to carry information related to DL MU transmission.

[0311] In some embodiments, the subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

[0312] In some embodiments, the setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

[0313] In some embodiments, the first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

[0314] In some embodiments, the first frame is an action frame.

[0315] In some embodiments, the second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

[0316] In some embodiments, the detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

[0317] In some embodiments, the second field belongs to a field set, and the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: a number of subcarrier set index fields, used to indicate the number of subcarrier sets occupied by the field set; a subcarrier set index list field, used to indicate the subcarrier set occupied by the field set.

[0318] In some embodiments, the second frame is an action frame.

[0319] In some embodiments, the second field is used to indicate data transmission requirements of the first device.

[0320] In some embodiments, the data transmission requirements include: low-latency data transmission requirements.

[0321] In some embodiments, the data associated with the first data unit is non-low-latency data.

[0322] In some embodiments, the first field is located at the end of the first data unit.

[0323] In some embodiments, the first data unit is a PPDU.

[0324] In an optional embodiment, the first receiving unit 2510 or the second receiving unit 2520 may be a transceiver 2630. The communication device 2500 may further include a processor 2610 and a memory 2620, as specifically shown in FIG26 .

[0325] Figure 26 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 26 indicate that the unit or module is optional. Device 2600 may be used to implement the method described in the above method embodiment. Device 2600 may be a chip, a terminal device, or a network device.

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

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

[0328] The apparatus 2600 may further include a transceiver 2630. The processor 2610 may communicate with other devices or chips via the transceiver 2630. For example, the processor 2610 may transmit and receive data with other devices or chips via the transceiver 2630.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A wireless communication method, characterized in that: include: The first device acquires a first data unit sent by the second device to the third device, where the first data unit includes a first field; The first device transmits a second field, the second field being time-aligned and having the same bandwidth as the first field.

2. The method according to claim 1, characterized in that The second field is used to indicate identity information of the first device.

3. The method according to claim 2, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

4. The method according to any one of claims 1 to 3, characterized in that The second device or the third device is a device that obtains a transmission opportunity TXOP.

5. The method according to any one of claims 1 to 4, characterized in that The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

6. The method according to claim 5, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

7. The method according to any one of claims 1 to 6, characterized in that Also includes: The first device obtains first indication information; The first indication information is used to indicate whether the first data unit includes the first field.

8. The method according to claim 7, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

9. The method according to claim 8, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

10. The method according to any one of claims 7 to 9, characterized in that: The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

11. The method according to any one of claims 1 to 10, characterized in that The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

12. The method according to claim 11, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

13. The method according to claim 11 or 12, characterized in that: The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

14. The method according to any one of claims 11 to 13, characterized in that The first frame is an action frame.

15. The method according to any one of claims 13 or 14, characterized in that The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

16. The method according to any one of claims 1 to 15, characterized in that The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

17. The method according to claim 16, characterized in that The second field belongs to a set of fields, the set of fields including one or more detected fields that are time-aligned and have the same bandwidth as the first field, The reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

18. The method according to claim 16 or 17, characterized in that The second frame is an action frame.

19. The method according to any one of claims 1 to 18, characterized in that The second field is used to indicate a data transmission requirement of the first device.

20. The method according to claim 19, characterized in that The data transmission requirements include: low-latency data transmission requirements.

21. The method according to any one of claims 1 to 20, characterized in that The data associated with the first data unit is non-low-latency data.

22. The method according to any one of claims 1 to 21, characterized in that The first field is located at the end of the first data unit.

23. The method according to any one of claims 1 to 22, characterized in that The first data unit is a physical layer protocol data unit PPDU.

24. A wireless communication method, characterized in that: include: The second device sends a first data unit to the third device, where the first data unit includes a first field; The second field sent by the first device is time-aligned with the first field and has the same bandwidth.

25. The method according to claim 24, characterized in that The second field is used to indicate identity information of the first device.

26. The method according to claim 25, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

27. The method according to any one of claims 24 to 26, characterized in that The second device or the third device is a device that obtains a transmission opportunity TXOP.

28. The method according to claim 27, characterized in that Also includes: The second device receives second indication information; The second indication information is used to indicate that the first device has sent the second field.

29. The method according to any one of claims 24 to 28, characterized in that The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

30. The method according to claim 29, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

31. The method according to any one of claims 24 to 30, characterized in that Also includes: The second device sends first indication information; The first indication information is used to indicate whether the first data unit includes the first field.

32. The method according to claim 31, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

33. The method according to claim 32, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

34. The method according to any one of claims 31 to 33, characterized in that The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

35. The method according to any one of claims 24 to 34, characterized in that The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

36. The method according to claim 35, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

37. The method according to claim 35 or 36, characterized in that The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

38. The method according to any one of claims 35 to 37, characterized in that The first frame is an action frame.

39. The method according to any one of claims 37 or 38, characterized in that The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

40. The method according to any one of claims 24 to 39, characterized in that The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

41. The method according to claim 40, characterized in that The second field belongs to a field set, the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

42. The method according to claim 40 or 41, characterized in that The second frame is an action frame.

43. The method according to any one of claims 24 to 42, characterized in that The second field is used to indicate a data transmission requirement of the first device.

44. The method according to claim 43, characterized in that The data transmission requirements include: low-latency data transmission requirements.

45. The method according to any one of claims 24 to 44, characterized in that The data associated with the first data unit is non-low-latency data.

46. ​​The method according to any one of claims 24 to 45, characterized in that The first field is located at the end of the first data unit.

47. The method according to any one of claims 24 to 46, characterized in that The first data unit is a physical layer protocol data unit PPDU.

48. A method of wireless communication, characterized in that: include: The third device receives a first data unit sent by the second device, where the first data unit includes a first field; The third device receives the second field sent by the first device; The second field is time-aligned and has the same bandwidth as the first field.

49. The method according to claim 48, characterized in that The second field is used to indicate identity information of the first device.

50. The method according to claim 49, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

51. The method according to any one of claims 48 to 50, characterized in that The second device or the third device is a device that obtains a transmission opportunity TXOP.

52. The method according to claim 51, characterized in that Also includes: The third device sends second indication information to the second device; The second indication information is used to indicate that the first device has sent the second field.

53. The method according to any one of claims 48 to 52, characterized in that The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

54. The method according to claim 53, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

55. The method according to any one of claims 48 to 54, characterized in that Also includes: The third device sends first indication information; The first indication information is used to indicate whether the first data unit includes the first field.

56. The method according to claim 55, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

57. The method according to claim 56, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

58. The method according to any one of claims 55 to 57, characterized in that The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

59. The method according to any one of claims 48 to 58, characterized in that The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

60. The method according to claim 59, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

61. The method according to claim 59 or 60, characterized in that The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

62. The method according to any one of claims 59 to 61, characterized in that The first frame is an action frame.

63. The method according to any one of claims 61 or 62, characterized in that The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

64. The method according to any one of claims 48 to 63, characterized in that The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

65. The method according to claim 64, characterized in that The second field belongs to a field set, the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

66. The method according to claim 64 or 65, characterized in that The second frame is an action frame.

67. The method according to any one of claims 48 to 66, characterized in that The second field is used to indicate a data transmission requirement of the first device.

68. The method according to claim 67, characterized in that The data transmission requirements include: low-latency data transmission requirements.

69. The method according to any one of claims 48 to 68, characterized in that The data associated with the first data unit is non-low-latency data.

70. The method according to any one of claims 48 to 69, characterized in that The first field is located at the end of the first data unit.

71. The method according to any one of claims 48 to 70, characterized in that The first data unit is a physical layer protocol data unit PPDU.

72. A communication device, characterized in that: The communication device is a first device, and the communication device includes: An acquiring unit, configured to acquire a first data unit sent by the second device to the third device, wherein the first data unit includes a first field; The first sending unit is used to send a second field, where the second field is time-aligned and has the same bandwidth as the first field.

73. The communication device according to claim 72, characterized in that The second field is used to indicate identity information of the first device.

74. The communication device according to claim 73, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

75. The communication device according to any one of claims 72 to 74, characterized in that: The second device or the third device is a device that obtains a transmission opportunity TXOP.

76. The communication device according to any one of claims 72-75, characterized in that The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

77. The communication device according to claim 76, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

78. The communication device according to any one of claims 72 to 77, characterized in that: The communication device is also used for: Obtaining first indication information; The first indication information is used to indicate whether the first data unit includes the first field.

79. The communication device according to claim 78, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

80. The communication device according to claim 79, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

81. The communication device according to any one of claims 78 to 80, characterized in that: The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

82. The communication device according to any one of claims 72 to 81, characterized in that: The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

83. The communication device according to claim 82, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

84. The communication device according to claim 82 or 83, characterized in that The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

85. The communication device according to any one of claims 82-84, characterized in that The first frame is an action frame.

86. The communication device according to any one of claims 84 or 85, characterized in that The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

87. The communication device according to any one of claims 72 to 86, characterized in that: The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

88. The communication device according to claim 87, characterized in that The second field belongs to a set of fields, the set of fields including one or more detected fields that are time-aligned and have the same bandwidth as the first field, The reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

89. The communication device according to claim 87 or 88, characterized in that The second frame is an action frame.

90. The communication device according to any one of claims 72 to 89, characterized in that: The second field is used to indicate a data transmission requirement of the first device.

91. The communication device according to claim 90, characterized in that The data transmission requirements include: low-latency data transmission requirements.

92. The communication device according to any one of claims 72 to 91, characterized in that: The data associated with the first data unit is non-low-latency data.

93. The communication device according to any one of claims 72 to 92, characterized in that: The first field is located at the end of the first data unit.

94. The communication device according to any one of claims 72 to 93, characterized in that: The first data unit is a physical layer protocol data unit PPDU.

95. A communication device, characterized in that: The communication device is a second device, and the communication device includes: A first sending unit, configured to send a first data unit to a third device, where the first data unit includes a first field; The second field sent by the first device is time-aligned with the first field and has the same bandwidth.

96. The communication device according to claim 95, characterized in that The second field is used to indicate identity information of the first device.

97. The communication device according to claim 96, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

98. The communication device according to any one of claims 95-97, characterized in that: The second device or the third device is a device that obtains a transmission opportunity TXOP.

99. The communication device according to claim 98, characterized in that The communication device is also used for: receiving second indication information; The second indication information is used to indicate that the first device has sent the second field.

100. The communication device according to any one of claims 95-99, characterized in that: The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

101. The communication device according to claim 100, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

102. The communication device according to any one of claims 95-101, characterized in that: The communication device is also used for: Sending first instruction information; The first indication information is used to indicate whether the first data unit includes the first field.

103. The communication device according to claim 102, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

104. The communication device according to claim 103, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

105. The communication device according to any one of claims 102-104, characterized in that: The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

106. The communication device according to any one of claims 95-105, characterized in that: The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

107. The communication device according to claim 106, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

108. The communication device according to claim 106 or 107, characterized in that: The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

109. The communication device according to any one of claims 106-108, characterized in that: The first frame is an action frame.

110. The communication device according to any one of claims 108 or 109, characterized in that: The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

111. The communication device according to any one of claims 95-110, characterized in that: The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

112. The communication device according to claim 111, characterized in that The second field belongs to a field set, the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

113. The communication device according to claim 111 or 112, characterized in that: The second frame is an action frame.

114. The communication device according to any one of claims 95-113, characterized in that: The second field is used to indicate a data transmission requirement of the first device.

115. The communication device according to claim 114, characterized in that The data transmission requirements include: low-latency data transmission requirements.

116. The communication device according to any one of claims 95-115, characterized in that: The data associated with the first data unit is non-low-latency data.

117. The communication device according to any one of claims 95-116, characterized in that: The first field is located at the end of the first data unit.

118. The communication device according to any one of claims 95-117, characterized in that: The first data unit is a physical layer protocol data unit PPDU.

119. A communication device, characterized in that: The communication device is a third device, and the communication device includes: A first receiving unit, configured to receive a first data unit sent by a second device, wherein the first data unit includes a first field; A second receiving unit, configured to receive a second field sent by the first device; The second field is time-aligned and has the same bandwidth as the first field.

120. The communication device according to claim 119, characterized in that The second field is used to indicate identity information of the first device.

121. The communication device according to claim 120, characterized in that The identity information of the first device is indicated by a subcarrier set occupied by the second field, where the subcarrier set includes one or more subcarriers.

122. The communication device according to any one of claims 119 to 121, characterized in that: The second device or the third device is a device that obtains a transmission opportunity TXOP.

123. The communication device according to claim 122, characterized in that The communication device is also used for: Sending second indication information to the second device; The second indication information is used to indicate that the first device has sent the second field.

124. The communication device according to any one of claims 119-123, characterized in that The first data unit also includes a third field, and the third field is used to reserve time for the first device to switch to a sending state.

125. The communication device according to claim 124, characterized in that The third field carries a random signal, or the third field does not carry a valid signal.

126. The communication device according to any one of claims 119-125, characterized in that: The communication device is also used for: Sending first instruction information; The first indication information is used to indicate whether the first data unit includes the first field.

127. The communication device according to claim 126, characterized in that The first indication information is included in an indication data unit, and the first data unit is the indication data unit or a response data unit of the indication data unit.

128. The communication device according to claim 127, characterized in that The indication data unit includes a fourth field, and the fourth field is used to indicate one or more of the following information: The indication data unit includes the first field; The response data unit of the indication data unit includes the first field; The indication data unit and the response data unit of the indication data unit both include the first field; Neither the indication data unit nor the response data unit of the indication data unit includes the first field.

129. The communication device according to any one of claims 126-128, characterized in that: The first indication information is carried in a unified signaling U-SIG field or an ultra-high reliability signaling UHR-SIG field, and the UHR-SIG field is used to carry information related to downlink multi-user transmission.

130. The communication device according to any one of claims 119-129, characterized in that: The subcarrier set occupied by the second field is configured by a setting element in the first frame, and the subcarrier set includes one or more subcarriers.

131. The communication device according to claim 130, characterized in that The setting element includes a subcarrier set index field, and the subcarrier set index field is used to configure the subcarrier set.

132. The communication device according to claim 130 or 131, characterized in that The first frame includes one or more of the following: a probe response frame, an association response frame, a reassociation response frame, and a second field update request frame.

133. The communication device according to any one of claims 130-132, characterized in that: The first frame is an action frame.

134. The communication device according to any one of claims 132 or 133, characterized in that The second field update response frame corresponding to the second field update request frame includes: a response status indication field, and the response status indication field is used to indicate whether the subcarrier set is configured successfully.

135. The communication device according to any one of claims 119-134, characterized in that: The detected subcarrier set occupied by the second field is indicated by a reporting element in the second frame, and the subcarrier set includes one or more subcarriers.

136. The communication device according to claim 135, characterized in that The second field belongs to a field set, the field set includes one or more detected fields that are time-aligned and have the same bandwidth as the first field, and the reporting element includes one or more of the following fields: The number field of the subcarrier set index is used to indicate the number of subcarrier sets occupied by the field set; The subcarrier set index list field is used to indicate the subcarrier set occupied by the field set.

137. The communication device according to claim 135 or 136, characterized in that The second frame is an action frame.

138. The communication device according to any one of claims 119 to 137, characterized in that: The second field is used to indicate a data transmission requirement of the first device.

139. The communication device according to claim 138, characterized in that The data transmission requirements include: low-latency data transmission requirements.

140. The communication device according to any one of claims 119-139, characterized in that: The data associated with the first data unit is non-low-latency data.

141. The communication device according to any one of claims 119-140, characterized in that The first field is located at the end of the first data unit.

142. The communication device according to any one of claims 119 to 141, characterized in that: The first data unit is a physical layer protocol data unit PPDU.

143. A communication device, characterized in that: It includes a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory so that the communication device executes the method as described in any one of claims 1-71.

144. A device, characterized in that: It includes a processor for calling a program from a memory so that the device executes a method as described in any one of claims 1-71.

145. A chip, characterized in that: It includes a processor for calling a program from a memory so that a device equipped with the chip executes a method as described in any one of claims 1 to 71.

146. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method as described in any one of claims 1-71.

147. A computer program product, characterized in that Comprising a program which causes a computer to execute the method as claimed in any one of claims 1 to 71.

148. A computer program, characterized in that The computer program causes a computer to execute the method as claimed in any one of claims 1 to 71.

Images