WO2025148012A1 - Wireless communication method and communication device - Google Patents

Abstract

Provided are a wireless communication method and a communication device. The method comprises: a first device sending a first PPDU to a second device, wherein the first PPDU comprises a first user field of a first user, and the first user field carries UHR feature information. On the basis of the present application, a first device can indicate UHR feature information to a second device by means of a first user field in a first PPDU, thereby facilitating communication between the first device and the second device to achieve UHR features.

Description

Wireless communication method and communication device Technical Field

The present application relates to the field of communication technology, and more specifically to a wireless communication method and a communication device.

Background Art

With the development of wireless fidelity (Wi-Fi) technology, the communication process between access points (AP) and stations (STA) may involve ultra-high reliability (UHR) features. Therefore, AP and STA may need to indicate relevant information of UHR features to each other. However, how AP and STA indicate relevant information of UHR features is not yet clear.

Summary of the invention

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

In a first aspect, a wireless communication method is provided, including: a first device sends a first PPDU to a second device, the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information.

According to a second aspect, a wireless communication method is provided, including: a second device receives a first PPDU sent by a first device, wherein the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information.

According to a third aspect, a communication device is provided, which is a first device and includes: a sending module for sending a first PPDU to a second device, wherein the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information.

In a fourth aspect, a communication device is provided, which is a second device and includes: a receiving module for receiving a first PPDU sent by a first device, wherein the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information.

In a fifth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method described in the first aspect.

In a sixth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method described in the second aspect.

In a seventh aspect, a device is provided, comprising a processor, configured to call a program from a memory so that the device executes the method described in the first aspect or the second aspect.

In an eighth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect or the second aspect.

In a ninth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

In a tenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

In an eleventh aspect, a computer program is provided, wherein the computer program enables a computer to execute the method as described in the first aspect or the second aspect.

In the present application, the first device may indicate UHR feature information to the second device via the first user field in the first PPDU, thereby facilitating communication between the first device and the second device to implement the UHR feature.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of a wireless communication system to which an embodiment of the present application is applicable.

Figure 2 is a schematic diagram of the structure of EHT MU PPDU.

Figure 3 is a schematic diagram of the structure of the EHT-SIG content channel used in OFDMA transmission.

Figure 4 is a schematic diagram of the structure of 2D A-PPDU.

Figure 5 is a schematic diagram of the structure of DL OFDMA MU PPDU.

Figure 6 is an example diagram of Inter-PPDU LPL.

FIG. 7 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application.

FIG8 is a schematic diagram of the structure of the first PPDU provided in an embodiment of the present application.

FIG. 9 is a schematic diagram of the structure of a UHR-SIG provided in an embodiment of the present application.

FIG10 is a schematic diagram of the structure of a UHR-SIG provided in another embodiment of the present application.

FIG. 11 is a schematic diagram of the structure of a UHR-SIG provided in another embodiment of the present application.

FIG12 is a schematic diagram of the structure of a UHR-SIG provided in another embodiment of the present application.

FIG. 13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.

FIG14 is a schematic diagram of the structure of a communication device provided in another embodiment of the present application.

FIG. 15 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in this application will be described below in conjunction with the accompanying drawings.

Communication System

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), Wi-Fi, high performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks or other communication systems. For another example, the technical solutions provided in the embodiments of the present application can be applied to communication systems that adopt the 802.11 standard. Exemplarily, the 802.11 standard includes, but is not limited to, the 802.11ax standard, the 802.11be standard, and the next generation 802.11 standard.

FIG1 is a schematic diagram of a communication system to which an embodiment of the present application is applicable. Referring to FIG1 , the communication devices in the communication system 100 may include access points (AP) 111 and AP 112, and stations (STA) 121 and STA 122, wherein STA 121 may access the network through AP 111, and STA 122 may access the network through AP 112.

In some implementations, a STA may establish an association with one or more APs, and then the associated STAs and APs may communicate with each other. As shown in FIG. 1 , AP 111 and STA 121 may communicate with each other after establishing an association, and AP 112 and STA 122 may communicate with each other after establishing an association.

In some implementations, the communication in the communication system 100 may be communication between an AP and a non-AP STA, communication between a non-AP STA and a non-AP STA, or communication between a STA and a peer STA, wherein 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 non-AP STA.

It should be understood that Figure 1 exemplarily shows two AP STAs and two non-AP STAs, and the communication system 100 may also include a larger number of AP STAs, or the communication system 100 may include other numbers of non-AP STAs, which is not limited to the embodiments of the present application.

In addition, the above communication system can be applied to scenarios of multi-device collaboration, such as multi-AP (multiple access points, Multi-AP) collaboration, or multi-site collaboration.

In the embodiments of the present application, the names of AP and/or STA are not limited. In some scenarios, AP can also be called AP STA, that is, in a sense, AP is also a STA. In other scenarios, STA can also be called non-AP STA.

In some scenarios, the above-mentioned communication device may also be a "multi-link device (MLD)", that is, a device that can communicate through multiple communication links, wherein the multiple communication links may include communication links of different frequency bands, for example, millimeter wave bands and/or low frequency bands. Generally, if the multi-link device is an AP, the AP may also be called a "multi-link AP". If the multi-link device is a STA, the STA may also be called a "multi-link STA".

In the embodiment of the present application, AP can be a device in a wireless network. AP can be a communication entity such as a communication server, a router, a switch, a bridge, or the AP device can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, AP can also be a chip or circuit or processing system in these various forms of devices, so as to realize the method and function of the embodiment of the present application. AP devices can be applied to a variety of scenarios, such as sensor nodes in smart cities (such as smart water meters, smart electric meters, smart air detection nodes), smart devices in smart homes (such as smart cameras, projectors, display screens, televisions, stereos, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (such as wearable devices such as AR and VR), smart devices in smart offices (such as printers, projectors, etc.), Internet of Vehicles devices in Internet of Vehicles, some infrastructure in daily life scenarios (such as vending machines, self-service navigation desks in supermarkets, self-service cash registers, self-service ordering machines), etc.

In some implementations, the role of STA in the communication system is not absolute, and in some scenarios, STA can act as AP. For example, in the scenario where a mobile phone is connected to a router, the mobile phone can be a non-AP STA, while in the scenario where the mobile phone acts as a hotspot for other mobile phones, the mobile phone plays the role of AP.

In the embodiment of the present application, the STA in the embodiment of the present application may be a device with wireless transceiver functions, such as supporting the 802.11 series of protocols, and may communicate with the AP or other STAs. For example, the STA is any user communication device that allows the user to communicate with the AP and then communicate with the WLAN. STA is, for example: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The STA in the embodiment of the present application may also be a device that provides voice/data connectivity to users, such as a handheld device or vehicle-mounted device with wireless connection function. For example, a mobile phone, a tablet computer, 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 self-driving car, etc. The present invention also includes wireless terminals in the following aspects: wireless terminals in remote driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved public land mobile communication networks (PLMNs), etc. The embodiments of the present application are not limited to this.

As an example but not a limitation, in the embodiments of the present application, the STA may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. For example: smart watches or smart glasses, and devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smart phones, such as various smart bracelets and smart jewelry for vital sign monitoring.

In addition, in the embodiment of the present application, STA can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. In the embodiment of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.

In addition, in the embodiment of the present application, STA can be a device in the vehicle networking system. The communication methods in the vehicle networking system are collectively referred to as V2X (X represents anything). For example, the V2X communication includes: vehicle to vehicle (V2V) communication, vehicle to roadside infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

In addition, in an embodiment of the present application, STA may also include sensors such as smart printers, train detectors, gas stations, etc. Its main functions include collecting data (partial terminal devices), receiving control information and downlink data from AP devices, and sending electromagnetic waves to transmit data to AP devices.

In addition, the AP device in the embodiment of the present application may be a device for communicating with a STA, and the AP device may be a network device in a wireless local area network. The AP device may be used to communicate with the STA through the wireless local area network.

From the perspective of the communication standards supported by the AP, in some implementations, the AP may be a device supporting the 802.11be standard. The AP may also be a device supporting various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.

From the perspective of the communication standards supported by STA, in some implementations, non-AP STA can support 802.11be. Non-AP STA can also support 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a, and other current and future 802.11 family wireless local area networks (WLAN) standards.

In the embodiment of the present application, the frequency band supported by WLAN technology is not limited. In some implementations, the frequency band supported by WLAN technology may include but is not limited to: low frequency band (such as 2.4 GHz, 5 GHz, 6 GHz), high frequency band (such as 45 GHz, 60 GHz).

It should be understood that the specific forms of STA and AP devices in the embodiments of the present application are not particularly limited and are merely illustrative.

Extremely high throughput (EHT) - signal (SIG) field

In the communication between AP and STA, EHT multi-user (MU) physical layer protocol data unit (PPDU) can be used for data transmission of one or more users, and the format of EHT MU PPDU can be shown in FIG2. Among them, non-high-throughput (non-HT)-short training field (STF), non-HT long-training field (L-LTF), non-HT-signal field (L-SIG), repeated non-high-throughput signal field (RL-SIG), universal-signal field (U-SIG) and EHT-SIG field can be referred to as pre-EHT modulation fields; EHT-STF, EHT-LTF, data and packet extension (PE) fields can be referred to as EHT modulation fields.

Among them, the EHT-SIG field can provide additional signaling to the U-SIG field for STAs to decode the EHT MU PPDU. In the EHT MU PPDU, the EHT-SIG field can contain the U-SIG overflow bit common to all users. The EHT-SIG field can further contain resource unit (RU) allocation information, allowing the STA to find the corresponding resources used in the EHT modulation field of the PPDU.

The EHT-SIG field of a 20 megahertz (MHz) EHT MU PPDU may include one EHT-SIG content channel. For orthogonal frequency division multiple access (OFDMA) transmission and multi-user non-OFDMA transmission, the EHT-SIG field of a 40 MHz or 80 MHz EHT MU PPDU may include two EHT-SIG content channels. For OFDMA transmission and multi-user non-OFDMA transmission, the EHT-SIG field of a 160 MHz or wider EHT MU PPDU may include two EHT-SIG content channels per 80 MHz frequency sub-block. When the bandwidth of the EHT MU PPDU for OFDMA transmission is greater than 80 MHz, the EHT-SIG content channel for each 80 MHz frequency sub-block is allowed to carry different information. When the bandwidth is equal to 20/40/80 MHz, the EHT-SIG content channel format used for OFDMA transmission may be as shown in FIG. 3.

For OFDMA transmission, the common field of the EHT-SIG content channel contains information about RU allocation, such as the RU allocation used in the EHT modulation field of the PPDU, the RU allocated for MU-multiple input multiple output (MIMO), and the number of users allocated for MU-MIMO. The format of the common field can be shown in Table 1.

Table 1 Common field format of OFDMA transmission

The union of user specific fields in the EHT-SIG content channel contains information for all users in the PPDU on how to decode its payload. As shown in Figure 3, the user specific field consists of user encoding blocks, which in turn consist of user fields for OFDMA transmissions.

The user specific field in the EHT-SIG content channel can consist of zero or more user encoding blocks, followed by padding (if present). The format of user encoding blocks can be shown in Table 2.

Table 2 Format of user encoding blocks

The content of the user field depends on whether the address of the field is a non-MU-MIMO assigned user in the RU or a MU-MIMO assigned user in the RU. When the address of the field is a non-MU-MIMO assigned user in the RU, the content of the user field can be as shown in Table 3. When the address of the field is a MU-MIMO assigned user in the RU, the format of the user field can be as shown in Table 4.

Table 3 User field format for non-MU-MIMO allocation

Table 4 Format of user field allocated by MU-MIMO

Two-dimensional (2D) frequency domain (FD) aggregated (A)-PPDU

For latency-sensitive services, the related technology proposes 2D A-PPDU. In 2D A-PPDU, the RU of downlink transmission can be allocated not only in the frequency domain but also in the time domain, so as to transmit as many latency-sensitive medium access control service data units (MSDU) as possible on the on-going PPDU to reduce delay.

Requirements for inserting delay-sensitive MSDUs into PPDUs may include: (1) being transparent to legacy STAs, including 11be release 1; (2) transmitting delay-sensitive MSDUs as much as possible on the ongoing PPDU (including FD A-PPDU) to reduce latency; (3) using only necessary subchannels, considering that delay-sensitive traffic is usually small, using the entire 320MHz PPDU It's quite wasteful.

Considering these requirements, the structure of the 2D FD A-PPDU can be as shown in FIG4. In order to reduce the complexity of the delay-sensitive MSDU receiver, the delay-sensitive MSDU can be transmitted based on the start time of the slot. For example, a fixed number of OFDM symbols can be defined for the potential start 2D FD A-PPDU for transmitting the delay-sensitive MSDU. Exemplarily, as shown in FIG5, a fixed number of OFDM symbols can also be defined in the downlink (DL) OFDMA MU PPDU for transmitting the delay-sensitive MSDU.

Low power listening ( LPL) for inter-basic service set (BSS) PPDU (also known as inter-PPDU)

The low power (LP) mode usually uses one RF link, low-order MCS and small bandwidth; while the high power (HP) mode uses multiple RF links, high-order MCS and bandwidth up to 320MHz, and the duration of changing different physical (PHY) parameters varies greatly. The related art proposes an inter-PPDU LPL scheme to reduce power consumption and signaling overhead at the same time. The inter-PPDU LPL scheme can be shown in Figure 6, including an initial PPDU (i.e., notification PPDU) for waking up the target STA, and the subsequent PPDU (i.e., data PPDU) delivers the data of the target STA. The interval between the notification PPDU and the first data PPDU provides sufficient duration for changing PHY parameters/functions.

During the LPL process, the target STA initially listens in a dedicated LP mode, and once a wake-up indication is detected, the target STA begins to switch to HP mode. In the inter-PPDU LPL scheme, the AP can send an initial PPDU (i.e., notification PPDU) to wake up the target STA. The notification PPDU can indicate the PHY parameters received in HP mode, which may also contain a wake-up indication or an upcoming data indication. For example, the detection of different PHY parameters can be regarded as a wake-up indication. The notification PPDU is mainly used to transmit data to other STAs, and the subsequent PPDU (i.e., data PPDU) is used to transmit the data of the target STA.

According to the above description, the communication process between AP and STA may involve UHR features such as LPL of 2D FD A-PPDU and inter-PPDU. Therefore, AP and STA may need to indicate relevant information of UHR features to each other. For example, when allocating time domain resources for different delay-sensitive MSDUs in 2D FD A-PPDU, AP needs to further indicate the time domain resource unit to each STA. For another example, in the LPL of inter-PPDU, AP needs to indicate the PHY parameters of the target STA entering high power in the notification PPDU. However, it is not yet clear how AP and STA indicate relevant information of UHR features.

Based on this, the method of the embodiment of the present application is introduced in detail below.

As shown in FIG. 7 , an embodiment of the present application provides a wireless communication method. The method shown in FIG. 7 is applicable to any AP and/or STA described above. For ease of understanding, the first device and the second device are used below to represent devices applicable to the present method. The first device in the embodiment of the present application may be an AP, and the second device may be a STA. Alternatively, the first device in the embodiment of the present application may also be a STA, and the second device may be an AP.

The method shown in FIG. 7 may include step S710. In step S710, the first device sends a first PPDU to the second device. The first PPDU may include a first user field for a first user, and the first user field may carry UHR feature information. The UHR feature information may be related information between the first device and the second device for implementing the UHR feature. When the first device is a STA and the second device is an AP, the first PPDU may be a PPDU in an uplink transmission process, such as a single user (SU) transmission mode of an uplink MU PPDU. Alternatively, when the first device is an AP and the second device is a STA, the first PPDU may also be a PPDU in a downlink transmission process, such as a MU PPDU of downlink OFDMA.

Based on the present application, the first device can indicate UHR feature information to the second device through the first user field in the first PPDU, which helps to implement the UHR feature in the communication between the first device and the second device.

The first user field is introduced in detail below. As mentioned above, the user field of the EHT-SIG field in the PPDU shown in Figure 3 can be used to indicate relevant information of each user. However, as shown in Table 3 or Table 4, there are fewer reserved bits available in the user field, only 1 or even no reserved bits. However, the UHR feature information may occupy more than 1 bit, so it is difficult to use the user field of the EHT-SIG field to carry the UHR feature information. Based on this, in the present application, the UHR feature information can be carried in the first user field.

The first user field may not include a subfield, and the UHR feature information may be carried in the first user field itself. For example, the first user field may be a field expanded on the basis of the user field of the EHT-SIG field, that is, a certain number of bits may be added to the user field of the EHT-SIG field to carry the UHR feature information. At this time, the number of bits of the first user field is greater than 22 bits, for example, the number of bits of the first user field may be 30 bits. The UHR feature information is carried in the first user field itself, which helps to reduce the decoding overhead of the second device.

Alternatively, the first user field may include a subfield, and the UHR feature information may be carried in the subfield. Exemplarily, the first user field may include a second user field and a third user field. Among them, the second user field may be used to carry the basic information of the first user. For example, the second user field may be the user field described above. The third user field may be used to carry the UHR feature information, and the third user field may have one or more. For example, the third user field may be a subfield added in addition to the user field described above. The UHR feature information is carried in the subfield of the first user field, which helps the second device to quickly locate the UHR feature information.

The third user field is described in detail below. In the first user field, the third user field may be located after the second user field, and the third user field may be adjacent to the second user field, which helps the first user to quickly locate the third user field. Furthermore, the third user field may have the same number of bits as the second user field. For example, when the second user field is the user field described above, the number of bits of the second user field and the third user field is 22 bits. At this time, the number of bits of the first user field is also greater than 22 bits.

The first n bits of the third user field can be used to indicate the first identifier, and the first identifier can be used to indicate the first user. The first n bits of the second user field can also be used to indicate the second identifier, and the second identifier can also be used to indicate the first user, and the second identifier is the same as the first identifier. That is, the first n bits of the third user field and the second user field can be used to indicate the identifier of the same user, that is, the third user field and the second user field can be fields for the same user. Exemplarily, the value of n can be 11, and the first identifier and the second identifier can be STA-ID. Based on this, it helps the first user to quickly locate its corresponding third user field. The second user field can be located in the same user encoding blocks as the third user field, which helps the first user to quickly locate the third user field.

Furthermore, the first PPDU may also include a first field, and the first field may be used to indicate whether the first user field carries a third user field, which helps the first user determine whether it is necessary to find a third user field corresponding to it. Exemplarily, the first field may occupy one bit in the first PPDU. When the value of the first field is a first value, it may indicate that the first user field carries a third user field. When the value of the first field is a second value, it may indicate that the first user field does not carry a third user field. For example, the first value may be 1, and the second value may be 0. For another example, the first value may be 0, and the second value may be 1.

In some implementations, the first field may be located in the second user field. Exemplarily, when the second user field is the user field described above, the first field may occupy a bit in the user field described above. For example, the first field may occupy a reserved bit in the user field described above.

In some other implementations, the first PPDU may further include a first common field, and the first field may be located in the first common field. Exemplarily, the first common field may be the common field shown in Table 1, and the first field may occupy one bit in the common field shown in Table 1. For example, the first field may occupy the 13th bit of the common field described above.

The first field can be identified by the second device based on the resource preemption function of the second device. That is, the second device with the resource preemption function can identify the first field, and then try to find one or more third user fields corresponding to it. The second device without the resource preemption function may not identify the first field, and then not try to find one or more third user fields corresponding to it, which helps to reduce the decoding overhead of such second devices. The resource preemption function of the second device can be determined based on the first information of the second device, and the first information can be maintained by the management entity of the second device. Exemplarily, the first information can be the management information base (MIB) information or management information set information of the second device, such as dot11 Preemption Option Implemented information. When the value of the first information is the first value, it can be indicated that the second device supports the resource preemption function. When the value of the first information is the second value, it can be indicated that the second device does not support the resource preemption function. For example, the first value can be true, and the second value can be false. Exemplarily, the first information can be maintained by the station management entity (SME) of the second device.

The UHR feature information in the first user field is introduced in detail below.

The UHR characteristic information may include the number of first time domain resources, which may refer to the number of OFDM symbols occupied by the first service of the first user in the first time domain resources, and the first time domain resources may be the time domain resources divided in the first frequency domain RU. The first frequency domain RU may be the frequency domain RU in the first PPDU, and the first frequency domain RU may correspond to the first user. That is, the number of first time domain resources is the number of time domain resources allocated to the first service in the first frequency domain RU. Based on the first number of time domain resources, the first device or the second device may preferentially occupy a corresponding number of OFDM symbols in the first time domain resources to transmit the first service, which helps to reduce the transmission delay of the first service.

Further, the first time domain resource number can be determined based on the second field. That is, the first user field can carry the second field to indicate the first time domain resource number. The second field can occupy L bits in the first user field, and L can be a positive integer less than the total number of bits in the first user field.

In some implementations, the second field may be used to indicate a first value n, and the first value n may be used to indicate a multiple of the first time domain resource number relative to the second value M. Then the first time domain resource number may be determined based on the product n×M of the first value n and the second value M, and the product n×M may be used to indicate the first n×M number of OFDM symbols occupied by the first service in the first time domain resource. Alternatively, the product n×M may also be used to indicate the last n×M number of OFDM symbols occupied by the first service in the first time domain resource. The second value M is a positive integer. For example, the second value M may be 5, 10 or 20. The second value M may be predefined or preconfigured by the protocol, or the second value M may be determined by negotiation between the first device and the second device. The second field is used to indicate a multiple of the first time domain resource number relative to the second value M, which helps to reduce the amount of information in the second field.

In some other implementations, the second field may be used to indicate a first value n and a second value M. The first value n may be used to indicate that the first service is in the nth time domain resource, and the second value M may be used to indicate the number of OFDM symbols in each time domain resource. The second device may then determine the number of time domain resources based on the total number of OFDM symbols in the time domain resources and the second value M, and then locate the time domain resources where the first service is located based on the first value n. The total number of OFDM symbols in the time domain resources may be obtained through the L-SIG field in the first PPDU. The first value n is a positive integer, for example, the first value n may be 1, 2, 3, or 4. The second value M is also a positive integer, for example, the second value M may be 5, 10, or 20. Exemplarily, the first value n may occupy 2 bits in the second field, and the second value M may occupy L-2 bits in the second field. For example, when the value of the bit of the first value n is 0, it can represent that the first value n is 1, when the value of the bit is 1, it can represent that the first value n is 2, when the value of the bit is 2, it can represent that the first value n is 3, and when the value of the bit is 3, it can represent that the first value n is 4. Based on the first value n and the second value M, it is helpful for the second device to quickly determine the number of first time domain resources.

In some other implementations, the second field may be used to indicate a first value n, and the first value n may be used to indicate that the first service is in the nth time domain resource. The number of the first time domain resources may be determined based on the first value n and the second value M, and the second value M may be used to indicate the number of OFDM symbols of each time domain resource. The second device may then determine the number of time domain resources based on the total number of OFDM symbols of the time domain resources and the second value M, and then locate the time domain resources where the first service is located based on the first value n. The total number of OFDM symbols of the time domain resources may be obtained through the L-SIG field in the first PPDU. The first value n is a positive integer, for example, the first value n may be 1, 2, 3 or 4. The second value M is also a positive integer, for example, the second value M may be 5, 10 or 20. The second value M may be predefined or preconfigured by the protocol, or the second value M may also be determined by negotiation between the first device and the second device. The second field may only indicate that the first service is in the nth time domain resource, which helps to reduce the amount of information carried by the first user field.

In some other implementations, the second field may be used to indicate a first value n, and the first value is used to indicate the number of OFDM symbols of each time domain resource. The number of the first time domain resources may be determined based on the first value n and the second value M, and the second value M may be used to indicate that the first service is in the Mth time domain resource. The second device may then determine the number of time domain resources based on the total number of OFDM symbols of the time domain resources and the first value n, and then locate the time domain resources where the first service is located based on the second value M. Among them, the total number of OFDM symbols of the time domain resources can be obtained through the L-SIG field in the first PPDU. The second value M may be predefined or preconfigured by the protocol, or the second value M may be determined by negotiation between the first device and the second device. The second field may only indicate the number of OFDM symbols of each time domain resource, which helps to reduce the amount of information carried by the first user field.

It is worth noting that the above-mentioned first service may be a low-latency service, in which case the low-latency service may preferentially occupy the number of OFDM symbols corresponding to the first number of time domain resources in the first time domain resources, and the remaining number of OFDM symbols may be occupied by non-low-latency services. Alternatively, the first service may be a non-low-latency service, in which case the non-low-latency service may preferentially occupy the number of OFDM symbols corresponding to the first number of time domain resources in the first time domain resources, and the remaining number of OFDM symbols may be occupied by low-latency services.

The UHR feature information may also include parameters corresponding to the low power listening mode, so that the second device switches the listening mode. The parameters corresponding to the low power listening mode may be parameters indicating that the second device enters the high power mode from the low power listening mode, such as high power bandwidth, MCS, number of spatial streams, etc. Among them, high power bandwidth can be used to indicate the bandwidth of the second device entering the high power mode from the low power listening mode. Exemplarily, the field carrying high power bandwidth (hereinafter referred to as "high power bandwidth field") may occupy 2 bits in the first user field. When the value of the high power bandwidth field is 0, it may represent 40MHz. When the value of the high power bandwidth field is 1, it may represent 80MHz. When the value of the high power bandwidth field is 2, it may represent 160MHz. When the value of the high power bandwidth field is 3, it may represent 320MHz.

In addition to the UHR feature information, the first user field may also carry the basic information of the first user. The basic information of the first user may include STA-ID, MCS, spatial stream, coding mode, and enabled beamforming parameters. Exemplarily, the first user field may also include a fundamental information field, and the basic information of the first user may be carried in the fundamental information field.

The wireless communication method of the embodiment of the present application is described below by way of example in conjunction with Figures 8 to 12. It should be noted that in Figures 8 to 12, the first device is an AP and the second device is a STA.

The following is an example of the first PPDU in the wireless communication method of the embodiment of the present application, with reference to FIG8. Exemplarily, the first PPDU shown in FIG8 may be a UHR MU PPDU. In the communication between the AP and the STA, the UHR MU PPDU may be used for transmission of one or more users. In the UHR MU PPDU, L-STF, L-LTF, L-SIG, RL-SIG, U-SIG and UHR-SIG may be referred to as pre-UHR modulation fields, and UHR-STF, UHR-LTF, data field and PE field may be referred to as UHR modulation fields.

The UHR-SIG field of a 20 MHz UHR MU PPDU may contain one UHR-SIG content channel. For OFDMA transmission and multi-user non-OFDMA transmission, the UHR-SIG field of a 40 MHz or 80 MHz UHR MU PPDU may contain two UHR-SIG content channels. For OFDMA transmission and multi-user non-OFDMA transmission, the UHR-SIG field of a 160 MHz or wider UHR MU PPDU may contain two UHR-SIG content channels per 80 MHz frequency sub-block. When the bandwidth of the UHR MU PPDU for OFDMA transmission is greater than 80 MHz, the UHR-SIG content channel for each 80 MHz frequency sub-block may be allowed to carry different information.

Exemplarily, the format of the UHR-SIG field may be the same as the format of the EHT-SIG shown in FIG3 . The UHR-SIG content channel of the UHR-SIG field may include a common field and a user specific field. The user specific field may include one or more user encoding blocks and padding (if present), and the user encoding block may include one or more user fields.

As described above, the first PPDU may include a first user field. The first user field of the first PPDU in the wireless communication method of an embodiment of the present application is introduced by way of example in conjunction with FIG. 9 and FIG. 10. For example, the first PPDU in FIG. 9 and FIG. 10 may be the UHR MU PPDU shown in FIG. 8, and the first user field may be located in the UHR-SIG field of the UHR MU PPDU.

As shown in FIG9 , the first user field is a user field field expanded on the basis of the user field of the UHR-SIG field, and the UHR characteristic information can be carried in the first user field itself. In FIG9 , the UHR characteristic information takes the first time domain resource number as an example, then the first time domain resource number is The number of domain resources can be determined based on the second field in the first user field. Referring to Figure 9, the first user field can be composed of a fundamental information field, a low latency preemption time resource/non-low latency time resource field, and a reserved bit. The fundamental information field can be used to carry basic information of the first user, such as the STA-ID, MCS, spatial stream, coding method, and beamforming parameters of the first user. The low latency preemption time resource/non-low latency time resource field, i.e., the second field, can be used to carry the number of OFDM symbols occupied by low latency services/non-low latency services in the first time domain resources. Exemplarily, the structure of the first user field in Figure 9 can be as shown in Table 5 or Table 6, and the bit position of the first user field can be N. The fundamental information field can occupy the first 22 bits, the low latency preemption time resource/non-low latency time resource field can occupy the L fields after the fundamental information field, and the remaining bits can be used as reserved bits. The value of the low latency preemption time resource/non-low latency time resource field can be as described above and will not be repeated here. It is worth noting that the first user field in the embodiment of the present application can be composed of one or more subfields in Table 5 or Table 6. The combination of subfields shown in Table 5 or Table 6 is one of the multiple implementation methods of the first user field and does not constitute a limitation on the first user field.

Table 5 First User Field Format for Non-MU-MIMO Allocation

Table 6 Format of the first user field for MU-MIMO allocation

It is worth noting that the UHR feature information carried by the first user field shown in FIG9 may also include parameters corresponding to the low power monitoring mode. Exemplarily, taking the bit position N of the first user field as 30 as an example, the first user field carrying the fundamental information of the first user, the number of first time domain resources (taking low latency preemption time resource/non-low latency time resource as an example) and the parameters corresponding to the low power monitoring mode (taking high power bandwidth as an example) may be as shown in Table 7 or Table 8. Among them, fundamental information may occupy the first 22 bits of the first user field, low latency preemption time resource/non-low latency time resource field may occupy 6 bits after fundamental information, and high power bandwidth field may occupy the remaining 2 bits. Exemplarily, when the value of the high power bandwidth field is 0, it can represent 40MHz, when the value of the high power bandwidth field is 1, it can represent 80MHz, when the value of the high power bandwidth field is 2, it can represent 160MHz, and when the value of the high power bandwidth field is 3, it can represent 320MHz. It is worth noting that the first user field in the embodiment of the present application can be composed of one or more sub-fields in Table 7 or Table 8. The arrangement and combination of sub-fields shown in Table 7 or Table 8 is one of the multiple implementation methods of the first user field and does not constitute a limitation on the first user field.

Table 7 First User Field Format for Non-MU-MIMO Allocation

Table 8 Format of the first user field assigned by MU-MIMO

As shown in FIG10 , the first user field may also be a field with an additional subfield added on the basis of the user field of the UHR-SIG field, and the UHR feature information may be carried in the newly added subfield. In FIG9 , the UHR feature information takes the first time domain resource number as an example, and the first time domain resource number may be determined based on the second field in the first user field. Exemplarily, the first user field may be composed of the user field (i.e., the second user field) and the user extension field (i.e., the third user field) of the UHR-SIG field. The bits of the user field and the user extension field may be the same, both of which are 22 bits. The user extension field may be located after the user field and is adjacent to the user field. The user field may be used to carry basic information of the first user, such as the STA-ID, MCS, spatial stream, coding mode, and beamforming parameters of the first user. The structure of the user field may be as shown in Table 3 or Table 4. The user extension field may be used to carry UHR feature information, and exemplary, the structure of the user extension field may be as shown in Table 9. The first 11 bits of the user extension field can be used to carry the STA-ID, and the STA-ID is the same as the STA-ID carried by the first 11 bits of the user field. Moreover, the user extension field can be located in the same user encoding blocks as the user field. In the user extension field, the L bits after the STA-ID can be used to carry the low latency preemption time resource/non-low latency time resource field. The low latency preemption time resource/non-low latency time resource field, i.e., the second field, can be used to carry the number of OFDM symbols occupied by the low latency preemption time resource/non-low latency time resource field in the first time domain resource. The value of the low latency preemption time resource/non-low latency time resource field can be as described above, and will not be repeated here. The remaining bits of the user extension field can be used as reserved bits. It is worth noting that the user extension field in the embodiment of the present application can be composed of one or more sub-fields in Table 9. The sub-field arrangement and combination shown in Table 9 is one of the multiple implementation methods of the user extension field and does not constitute a limitation on the user extension field.

Table 9 user extension field format

It is worth noting that the UHR feature information carried by the first user field shown in FIG10 may also include parameters corresponding to the low power monitoring mode. Exemplarily, the user extension field carrying the STA-ID of the first user, the first time domain resource number (taking low latency preemption time resource/non-low latency time resource as an example) and the parameters corresponding to the low power monitoring mode (taking high power bandwidth as an example) may be as shown in Table 10. Among them, the STA-ID of the first user may occupy the first 11 bits of the user extension field, the low latency preemption time resource/non-low latency time resource field may occupy the 6 bits after the STA-ID, the high power bandwidth field may occupy the 2 bits after the low latency preemption time resource/non-low latency time resource field, and the remaining 3 bits may be used as reserved bits. It is worth noting that the user extension field in the embodiment of the present application may be composed of one or more sub-fields in Table 10. The arrangement and combination of subfields shown in Table 10 is one of the multiple implementation methods of the user extension field and does not constitute a limitation on the user extension field.

Table 10 user extension field format

In addition, the UHR-SIG field shown in FIG10 includes a UHR-SIG content channel. As described above, when the UHR MU PPDU greater than 20 MHz performs OFDMA transmission and multi-user non-OFDMA transmission, its UHR-SIG field may include multiple UHR-SIG content channels. Therefore, the UHR-SIG field shown in FIG10 may also include multiple UHR-SIG content channels. If the UHR-SIG field shown in FIG10 includes multiple UHR-SIG content channels, the contents of the user specific fields of different UHR-SIG content channels may be different. For example, some UHR-SIG content channels may include a user extension field, while the remaining UHR-SIG content channels may not include a user extension field. For example, when the 40 MHz UHR MU PPDU performs OFDMA transmission, UHR-SIG content channel 1 may include a user extension field; and UHR-SIG content channel 2 may not include a user extension field.

As described above, when the first user field includes the third user field, the first PPDU may also include a first field to indicate whether the third user field is carried in the first user field. The first field of the wireless communication method of the embodiment of the present application is illustrated below by taking the first user field shown in FIG. 10 as an example in combination with FIG. 11 and FIG. 12. For ease of understanding, the first field may be a user extension enable field.

As shown in FIG. 11, the first field (taking the user extension enable field as an example) may be located in the second user field (taking the user field as an example) of the first user field, indicating whether the user field is followed by one or more third user fields (taking the user extension field as an example) for the same STA. Exemplarily, the format of the user field may be as shown in Table 11, and the user extension enable field may occupy the 15th bit of the user field. When the value of the user extension enable field is different, its meaning is different. For example, when the value of the user extension enable field is 0, it may indicate that there is a user extension field, that is, the STA will try to continue to find one or more additional user extension fields that match its STA-ID. When the value of the user extension enable field is 1, it may indicate that there is no user extension field. It is worth noting that the user field in the embodiment of the present application may be composed of one or more sub-fields in Table 11. The sub-field arrangement and combination shown in Table 11 is one of the multiple implementations of the user field and does not constitute a limitation on the user field.

Table 11 Non-MU-MIMO user field format

As shown in FIG. 12, the first field may also be located in the common field of the first PPDU, indicating whether the user specific field corresponding to the common field contains a user field and one or more additional user extension fields for the same STA. Exemplarily, the format of the common field may be as shown in Table 12, and the user extension enable field may occupy the 13th bit of the common field. When the value of the user extension enable field is different, its meaning is different. For example, when the value of the user extension enable field is 0, it may indicate that there is a user extension field, that is, the STA will try to continue to find one or more additional user extension fields that match its STA-ID. When the value of the user extension enable field is 1, it may indicate that there is no user extension field. It is worth noting that the common field in the embodiment of the present application may be composed of one or more subfields in Table 12. The subfield arrangement and combination shown in Table 12 is one of the multiple implementations of the common field and does not constitute a limitation on the common field.

Table 12 common field format

The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 12, and the device embodiment of the present application is described in detail below in conjunction with Figures 13 to 15. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the part not described in detail can refer to the previous method embodiment.

FIG13 is a schematic diagram of the structure of a communication device provided by an embodiment of the present application. The communication device 1300 shown in FIG13 is a first device, which may include a sending module 1310. The sending module 1310 may be used to send a first PPDU to a second device, and the first PPDU may include a first user field of a first user, and the first user field carries UHR feature information.

In an embodiment of the present application, the above-mentioned communication device 1300 can be used to execute some or all of the method steps executed by the first device in the above-mentioned method embodiment. For example, the communication device 1300 can be used to execute some or all of the method steps executed by the first device in the method introduced in the above text in conjunction with Figures 7 to 12. The communication device 1300 includes a unit or module for executing the method steps corresponding to the aforementioned Figures 7 to 12. The method flow has been described in detail in the aforementioned implementation mode. The modules in this embodiment have the same functions or perform the same steps, which will not be described here, but should be known to those skilled in the art. The text description corresponding to the aforementioned Figures 7 to 12 can be introduced into this example, corresponding to the modules in the communication device 1300.

FIG14 is a schematic diagram of the structure of a communication device provided by another embodiment of the present application. The communication device 1400 shown in FIG14 is a second device, which may include a receiving module 1410. The receiving module 1410 may be used to receive a first PPDU sent by a first device, and the first PPDU may include a first user field of a first user, and the first user field carries UHR feature information.

In an embodiment of the present application, the above-mentioned communication device 1400 can be used to execute some or all of the method steps executed by the second device in the above-mentioned method embodiment. For example, the communication device 1400 can be used to execute some or all of the method steps executed by the second device in the method described in the above text in conjunction with Figures 7 to 12. The communication device 1400 includes a unit or module for executing the method steps corresponding to the aforementioned Figures 7 to 12. The method flow has been described in detail in the aforementioned embodiment. The modules in this embodiment have the same functions or perform the same steps, which will not be described here, but as those skilled in the art should know, the text descriptions corresponding to the aforementioned Figures 7 to 12 can be introduced into this example, corresponding to the modules in the communication device 1400.

FIG15 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The dotted lines in FIG15 indicate that the unit or module is optional. The device 1500 may be used to implement the method described in the above method embodiment. The device 1500 may be a chip, a terminal device or a network device.

The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 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 also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

The apparatus 1500 may further include one or more memories 1520. The memory 1520 stores a program, which can be executed by the processor 1510, so that the processor 1510 executes the method described in the above method embodiment. The memory 1520 may be independent of the processor 1510 or integrated in the processor 1510.

The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips through the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips through the transceiver 1530.

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

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

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

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 the present application, and are not intended to limit the present 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 of their variations are intended to cover non-exclusive inclusions.

In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication 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.

In the embodiments of the present application, the term "and/or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. 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 article generally indicates that the associated objects before and after are in an "or" relationship.

In the embodiments of the present application, the term "include" may refer to direct inclusion or indirect inclusion. Optionally, the term "include" mentioned in the embodiments of the present application may be replaced with "indicate" or "used to determine". For example, "A includes B" may be replaced with "A indicates B" or "A is used to determine B".

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.

In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by 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 may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may 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. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital versatile disk (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (127)

A wireless communication method, comprising: The first device sends a first PPDU to the second device, where the first PPDU includes a first user field for a first user, and the first user field carries UHR feature information. The method according to claim 1 is characterized in that the first user field includes a second user field and a third user field, the second user field is used to carry basic information of the first user, and the third user field is used to carry the UHR feature information. The method according to claim 2 is characterized in that, in the first user field, the third user field is located after the second user field, and the third user field is adjacent to the second user field. The method according to claim 2 or 3 is characterized in that the number of bits of the third user field is the same as that of the second user field. The method according to any one of claims 2 to 4 is characterized in that the first n bits of the third user field are used to indicate a first identifier, and the first identifier is used to indicate the first user. The method according to any one of claims 2 to 5 is characterized in that the first n bits of the second user field are used to indicate a second identifier, the second identifier is used to indicate a first user, and the second identifier is the same as the first identifier. The method according to claim 5 or 6 is characterized in that the value of n is 11. The method according to any one of claims 2 to 7, characterized in that the second user field and the third user field are located in the same user coding block. The method according to any one of claims 2 to 8 is characterized in that the first PPDU also includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field. The method according to claim 9, characterized in that the first field is located in the second user field. The method according to claim 9 is characterized in that the first PPDU also includes a first general field, and the first field is located in the first general field. The method according to any one of claims 9 to 11 is characterized in that the first field is recognized by the second device based on a resource preemption function of the second device. The method according to claim 12 is characterized in that the preemption function is determined based on first information of the second device, and the first information is maintained by a management entity of the second device. The method according to any one of claims 1 to 13 is characterized in that the UHR characteristic information includes the number of first time domain resources, the first time domain resource number is the number of OFDM symbols occupied by the first service of the first user in the first time domain resources, the first time domain resources are the time domain resources divided in the first frequency domain RU, and the first frequency domain RU corresponds to the first user. The method according to claim 14 is characterized in that the first number of time domain resources is determined based on the second field. The method according to claim 15 is characterized in that the second field is used to indicate a first value n, the first value n is used to indicate a multiple of the first time domain resource number relative to a second value M, and the second value M is a positive integer. The method based on claim 16 is characterized in that the first number of time domain resources is determined based on the product n×M of the first value n and the second value M, and the product n×M is used to indicate the first n×M number of OFDM symbols occupied by the first service in the first time domain resources, or the product n×M is used to indicate the last n×M number of OFDM symbols occupied by the first service in the first time domain resources. The method according to claim 15 is characterized in that the second field is used to indicate a first value n and a second value M, the first value n is used to indicate that the first service is in the nth time domain resource, and the second value M is used to indicate the number of OFDM symbols in each time domain resource. The method according to claim 15 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate that the first service is in the nth time domain resource. The method according to claim 19 is characterized in that the first number of time domain resources is based on the first value n and a second value M, and the second value M is used to indicate the number of OFDM symbols of each time domain resource. The method according to claim 20 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The method according to claim 15 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate the number of OFDM symbols of each time domain resource. The method according to claim 22 is characterized in that the first number of time domain resources is determined based on the first value n and a second value M, and the second value M is used to indicate that the first service is in the Mth time domain resource. The method according to claim 23 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The method according to any one of claims 14 to 24 is characterized in that the first service is a low-latency service, or the first service is a non-low-latency service. The method according to any one of claims 1 to 25 is characterized in that the UHR feature information also includes parameters corresponding to the low power monitoring mode. The method according to any one of claims 1 to 26 is characterized in that the first user field also carries basic information of the first user. The method according to any one of claims 1 to 27 is characterized in that the first device is an AP device and the second device is a STA device, or the first device is a STA device and the second device is an AP device. The method according to any one of claims 4 to 28, characterized in that the number of bits of the second user field and the third user field is 22 bits. The method according to any one of claims 1 to 29, characterized in that the number of bits of the first user field is greater than 22 bits. A wireless communication method, comprising: The second device receives a first PPDU sent by the first device, where the first PPDU includes a first user field for a first user, and the first user field carries UHR feature information. The method according to claim 31 is characterized in that the first user field includes a second user field and a third user field, the second user field is used to carry the basic information of the first user, and the third user field is used to carry the UHR feature information. The method according to claim 32 is characterized in that, in the first user field, the third user field is located after the second user field, and the third user field is adjacent to the second user field. The method according to claim 32 or 33 is characterized in that the number of bits of the third user field is the same as that of the second user field. The method according to any one of claims 32 to 34 is characterized in that the first n bits of the third user field are used to indicate a first identifier, and the first identifier is used to indicate the first user. The method according to any one of claims 32 to 35 is characterized in that the first n bits of the second user field are used to indicate a second identifier, the second identifier is used to indicate a first user, and the second identifier is the same as the first identifier. The method according to claim 35 or 36 is characterized in that the value of n is 11. The method according to any one of claims 32 to 37 is characterized in that the second user field and the third user field are located in the same user coding block. The method according to any one of claims 32 to 38 is characterized in that the first PPDU also includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field. The method according to claim 39, characterized in that the first field is located in the second user field. The method according to claim 39 is characterized in that the first PPDU also includes a first general field, and the first field is located in the first general field. The method according to any one of claims 39 to 41 is characterized in that the first field is recognized by the second device based on a resource preemption function of the second device. The method according to claim 42 is characterized in that the preemption function is determined based on first information of the second device, and the first information is maintained by a management entity of the second device. The method according to any one of claims 31 to 43 is characterized in that the UHR characteristic information includes the number of first time domain resources, the first time domain resource number is the number of OFDM symbols occupied by the first service of the first user in the first time domain resources, the first time domain resources are the time domain resources divided in the first frequency domain RU, and the first frequency domain RU corresponds to the first user. The method according to claim 44 is characterized in that the first number of time domain resources is determined based on the second field. The method according to claim 45 is characterized in that the second field is used to indicate a first value n, the first value n is used to indicate a multiple of the first time domain resource number relative to a second value M, and the second value M is a positive integer. The method based on claim 46 is characterized in that the first number of time domain resources is determined based on the product n×M of the first value n and the second value M, and the product n×M is used to indicate the first n×M number of OFDM symbols occupied by the first service in the first time domain resources, or the product n×M is used to indicate the last n×M number of OFDM symbols occupied by the first service in the first time domain resources. The method according to claim 45 is characterized in that the second field is used to indicate a first value n and a second value M, the first value n is used to indicate that the first service is in the nth time domain resource, and the second value M is used to indicate the number of OFDM symbols in each time domain resource. The method according to claim 45 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate that the first service is in the nth time domain resource. The method according to claim 49 is characterized in that the first number of time domain resources is based on the first value n and a second value M, and the second value M is used to indicate the number of OFDM symbols of each time domain resource. The method according to claim 50 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The method according to claim 45 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate the number of OFDM symbols for each time domain resource. The method according to claim 52 is characterized in that the first time domain resource number is determined based on the first value n and a second value M, and the second value M is used to indicate that the first service is in the Mth time domain resource. The method according to claim 53 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The method according to any one of claims 44 to 54 is characterized in that the first service is a low-latency service, or the first service is a non-low-latency service. The method according to any one of claims 31 to 55 is characterized in that the UHR feature information also includes parameters corresponding to the low power consumption monitoring mode. The method according to any one of claims 31 to 56 is characterized in that the first user field also carries basic information of the first user. The method according to any one of claims 31 to 57 is characterized in that the first device is an AP device and the second device is a STA device, or the first device is a STA device and the second device is an AP device. The method according to any one of claims 34 to 58 is characterized in that the number of bits of the second user field and the third user field is 22 bits. The method according to any one of claims 31 to 59 is characterized in that the number of bits of the first user field is greater than 22 bits. A communication device, the communication device being a first device, comprising: The sending module is used to send a first PPDU to a second device, where the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information. The communication device according to claim 61 is characterized in that the first user field includes a second user field and a third user field, the second user field is used to carry basic information of the first user, and the third user field is used to carry the UHR feature information. The communication device according to claim 62 is characterized in that, in the first user field, the third user field is located after the second user field, and the third user field is adjacent to the second user field. The communication device according to claim 62 or 63 is characterized in that the number of bits of the third user field is the same as that of the second user field. The communication device according to any one of claims 62 to 64 is characterized in that the first n bits of the third user field are used to indicate a first identifier, and the first identifier is used to indicate the first user. The communication device according to any one of claims 62 to 65 is characterized in that the first n bits of the second user field are used to indicate a second identifier, the second identifier is used to indicate a first user, and the second identifier is the same as the first identifier. The communication device according to claim 65 or 66 is characterized in that the value of n is 11. The communication device according to any one of claims 62 to 67 is characterized in that the second user field and the third user field are located in the same user coding block. The communication device according to any one of claims 62 to 68 is characterized in that the first PPDU also includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field. The communication device according to claim 69 is characterized in that the first field is located in the second user field. The communication device according to claim 69 is characterized in that the first PPDU also includes a first general field, and the first field is located in the first general field. The communication device according to any one of claims 69 to 71 is characterized in that the first field is recognized by the second device based on a resource preemption function of the second device. The communication device according to claim 72 is characterized in that the preemption function is determined based on first information of the second device, and the first information is maintained by a management entity of the second device. The communication device according to any one of claims 61 to 73 is characterized in that the UHR characteristic information includes the number of first time domain resources, the first time domain resource number is the number of OFDM symbols occupied by the first service of the first user in the first time domain resources, the first time domain resources are the time domain resources divided in the first frequency domain RU, and the first frequency domain RU corresponds to the first user. The communication device according to claim 74 is characterized in that the first number of time domain resources is determined based on the second field. The communication device according to claim 75 is characterized in that the second field is used to indicate a first value n, the first value n is used to indicate a multiple of the first time domain resource number relative to a second value M, and the second value M is a positive integer. The communication device according to claim 76 is characterized in that the first number of time domain resources is determined based on the product n×M of the first value n and the second value M, and the product n×M is used to indicate the first n×M number of OFDM symbols occupied by the first service in the first time domain resources, or the product n×M is used to indicate the last n×M number of OFDM symbols occupied by the first service in the first time domain resources. The communication device according to claim 75 is characterized in that the second field is used to indicate a first value n and a second value M, the first value n is used to indicate that the first service is in the nth time domain resource, and the second value M is used to indicate the number of OFDM symbols in each time domain resource. The communication device according to claim 75 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate that the first service is in the nth time domain resource. The communication device according to claim 79 is characterized in that the first number of time domain resources is based on the first value n and a second value M, and the second value M is used to indicate the number of OFDM symbols of each time domain resource. The communication device according to claim 80 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The communication device according to claim 75 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate the number of OFDM symbols for each time domain resource. The communication device according to claim 82 is characterized in that the first time domain resource number is determined based on the first value n and a second value M, and the second value M is used to indicate that the first service is in the Mth time domain resource. The communication device according to claim 83 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The communication device according to any one of claims 74 to 84 is characterized in that the first service is a low-latency service, or the first service is a non-low-latency service. The communication device according to any one of claims 61 to 85 is characterized in that the UHR feature information also includes parameters corresponding to the low power listening mode. The communication device according to any one of claims 61 to 86 is characterized in that the first user field also carries basic information of the first user. The communication device according to any one of claims 61 to 87 is characterized in that the first device is an AP device and the second device is a STA device, or the first device is a STA device and the second device is an AP device. The communication device according to any one of claims 64 to 88 is characterized in that the number of bits of the second user field and the third user field is 22 bits. The communication device according to any one of claims 61 to 89 is characterized in that the number of bits of the first user field is greater than 22 bits. A communication device, wherein the communication device is a second device, comprising: The receiving module is used to receive a first PPDU sent by a first device, where the first PPDU includes a first user field of a first user, and the first user field carries UHR feature information. The communication device according to claim 91 is characterized in that the first user field includes a second user field and a third user field, the second user field is used to carry the basic information of the first user, and the third user field is used to carry the UHR feature information. The communication device according to claim 92 is characterized in that, in the first user field, the third user field is located after the second user field, and the third user field is adjacent to the second user field. The communication device according to claim 92 or 93 is characterized in that the number of bits of the third user field is the same as that of the second user field. The communication device according to any one of claims 92 to 94 is characterized in that the first n bits of the third user field are used to indicate a first identifier, and the first identifier is used to indicate the first user. The communication device according to any one of claims 92 to 95 is characterized in that the first n bits of the second user field are used to indicate a second identifier, the second identifier is used to indicate a first user, and the second identifier is the same as the first identifier. The communication device according to claim 95 or 96 is characterized in that the value of n is 11. The communication device according to any one of claims 92 to 97 is characterized in that the second user field and the third user field are located in the same user coding block. The communication device according to any one of claims 92 to 98 is characterized in that the first PPDU also includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field. The communication device according to claim 99 is characterized in that the first field is located in the second user field. The communication device according to claim 99 is characterized in that the first PPDU also includes a first general field, and the first field is located in the first general field. The communication device according to any one of claims 99 to 101 is characterized in that the first field is recognized by the second device based on a resource preemption function of the second device. The communication device according to claim 102 is characterized in that the preemption function is determined based on first information of the second device, and the first information is maintained by a management entity of the second device. The communication device according to any one of claims 91 to 103 is characterized in that the UHR characteristic information includes the number of first time domain resources, the first time domain resource number is the number of OFDM symbols occupied by the first service of the first user in the first time domain resources, the first time domain resources are the time domain resources divided in the first frequency domain RU, and the first frequency domain RU corresponds to the first user. The communication device according to claim 104 is characterized in that the first number of time domain resources is determined based on the second field. The communication device according to claim 105 is characterized in that the second field is used to indicate a first value n, the first value n is used to indicate a multiple of the first time domain resource number relative to a second value M, and the second value M is a positive integer. The communication device according to claim 106 is characterized in that the first number of time domain resources is determined based on the product n×M of the first value n and the second value M, and the product n×M is used to indicate the first n×M number of OFDM symbols occupied by the first service in the first time domain resources, or the product n×M is used to indicate the last n×M number of OFDM symbols occupied by the first service in the first time domain resources. The communication device according to claim 105 is characterized in that the second field is used to indicate a first value n and a second value M, the first value n is used to indicate that the first service is in the nth time domain resource, and the second value M is used to indicate the number of OFDM symbols in each time domain resource. The communication device according to claim 105 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate that the first service is in the nth time domain resource. The communication device according to claim 109 is characterized in that the first number of time domain resources is based on the first value n and a second value M, and the second value M is used to indicate the number of OFDM symbols of each time domain resource. The communication device according to claim 110 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The communication device according to claim 105 is characterized in that the second field is used to indicate a first value n, and the first value n is used to indicate the number of OFDM symbols of each time domain resource. The communication device according to claim 112 is characterized in that the first time domain resource number is determined based on the first value n and a second value M, and the second value M is used to indicate that the first service is in the Mth time domain resource. The communication device according to claim 113 is characterized in that the second value M is predefined or preconfigured by a protocol, or the second value M is determined by negotiation between the first device and the second device. The communication device according to any one of claims 104 to 114 is characterized in that the first service is a low-latency service, or the first service is a non-low-latency service. The communication device according to any one of claims 91 to 115 is characterized in that the UHR feature information also includes parameters corresponding to the low power consumption monitoring mode. The communication device according to any one of claims 91 to 116 is characterized in that the first user field also carries basic information of the first user. The communication device according to any one of claims 91 to 117 is characterized in that the first device is an AP device and the second device is a STA device, or the first device is a STA device and the second device is an AP device. The communication device according to any one of claims 94 to 118 is characterized in that the number of bits of the second user field and the third user field is 22 bits. The communication device according to any one of claims 91 to 119 is characterized in that the number of bits of the first user field is greater than 22 bits. A communication device, characterized in that it comprises a memory and a processor, wherein the memory is used to store a program, and the processor Used to call the program in the memory to enable the communication device to execute the method according to any one of claims 1-30. 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 31-60. A device, characterized in that it comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-30 or 31-60. A chip, characterized in that it comprises 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-30 or 31-60. A computer-readable storage medium, characterized in that a program is stored thereon, wherein the program enables a computer to execute the method as described in any one of claims 1-30 or 31-60. A computer program product, characterized in that it comprises a program, wherein the program enables a computer to execute the method according to any one of claims 1-30 or 31-60. A computer program, characterized in that the computer program enables a computer to execute the method according to any one of claims 1-30 or 31-60.