Wireless communication method and communication device

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

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

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

[0003] Summary of the Invention

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

[0005] In a first aspect, a wireless communication method is provided, including: a first device sending a first PPDU to a second device, the first PPDU including a first user field of a first user, the first user field carrying UHR feature information.

[0006] According to a second aspect, a wireless communication method is provided, including: a second device 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.

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

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

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

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

[0011] In a seventh aspect, a device is provided, comprising a processor for calling a program from a memory so that the device executes the method as described in the first aspect or the second aspect.

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

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

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

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

[0016] In the present application, the first device may indicate UHR feature information to the second device through 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

[0017] FIG1 is a schematic structural diagram of a wireless communication system to which an embodiment of the present application is applicable.

[0018] FIG2 is a schematic diagram of the structure of an EHT MU PPDU.

[0019] FIG3 is a schematic diagram of the structure of the EHT-SIG content channel used in OFDMA transmission.

[0020] FIG4 is a schematic diagram of the structure of a 2D A-PPDU.

[0021] FIG5 is a schematic diagram of the structure of a DL OFDMA MU PPDU.

[0022] FIG6 is an example diagram of Inter-PPDU LPL.

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

[0024] FIG8 is a schematic structural diagram of the first PPDU provided in an embodiment of the present application.

[0025] FIG9 is a schematic diagram of the structure of a UHR-SIG provided in an embodiment of the present application.

[0026] FIG10 is a schematic structural diagram of a UHR-SIG provided in another embodiment of the present application.

[0027] FIG11 is a schematic structural diagram of a UHR-SIG provided in another embodiment of the present application.

[0028] FIG12 is a schematic structural diagram of a UHR-SIG provided in another embodiment of the present application.

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

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

[0031] FIG15 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0033] Communication System

[0034] The technical solutions provided in 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. For example, 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.

[0035] FIG1 is a schematic diagram of a communication system applicable to embodiments of the present application. Referring to FIG1 , the communication devices in the communication system 100 may include access points (APs) 111 and 112, and stations (STAs) 121 and 122. STA 121 may access the network through AP 111, and STA 122 may access the network through AP 112.

[0036] In some implementations, a STA may establish an association with one or more APs, after which the associated STAs and APs may communicate. For example, as shown in FIG1 , AP 111 and STA 121 may communicate after establishing an association, and AP 112 and STA 122 may communicate after establishing an association.

[0037] 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, where a peer STA may refer to a device that communicates with the STA peer, for example, the peer STA may be an AP or a non-AP STA.

[0038] It should be understood that FIG1 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 in the embodiments of the present application.

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

[0040] In the embodiments of this 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 type of STA. In other scenarios, STA can also be called non-AP STA.

[0041] In some scenarios, the aforementioned communication device may also be a "multi-link device (MLD)," i.e., a device that can communicate via multiple communication links, where the multiple communication links may include communication links in different frequency bands, such as millimeter wave bands and / or low-frequency bands. Generally, if the multi-link device is an AP, the AP may also be referred to as a "multi-link AP." If the multi-link device is a STA, the STA may also be referred to as a "multi-link STA."

[0042] In the embodiments of the present application, an AP may be a device in a wireless network. An AP may be a communication entity such as a communication server, a router, a switch, or a bridge, or the AP device may include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP may also be a chip, circuit, or processing system in these various forms of devices, thereby realizing the methods and functions of the embodiments of the present application. The AP device can be applied to a variety of scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as AR and VR), smart devices in smart offices (e.g., printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (e.g., vending machines, self-service navigation counters in supermarkets, self-service checkout devices, self-service ordering machines), etc.

[0043] In some implementations, the role of a STA in a communication system is not absolute; in some scenarios, a STA can function as an AP. For example, when a mobile phone is connected to a router, it can be a non-AP STA, while when it is acting as a hotspot for other phones, it functions as an AP.

[0044] In the embodiments of the present application, a STA in the embodiments of the present application may be a device with wireless transceiver capabilities, such as a device that supports the 802.11 series of protocols and can communicate with an AP or other STAs. For example, a STA is any user communication device that allows a user to communicate with an AP and, in turn, with a WLAN. Examples of STAs include user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0045] 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. Examples include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-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 capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future-evolved public land mobile communication networks. The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0046] By way of example and not limitation, in the embodiments of this application, the STA may also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices that utilize wearable technology to intelligently design and develop wearable devices for everyday wear, such as glasses, gloves, watches, clothing, and shoes. Examples include smart watches or smart glasses, as well as devices that focus on a specific application function and require integration with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0047] In addition, in the embodiments of the present application, a STA can also be a terminal device in the Internet of Things (IoT) system. The IoT is an important component 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 that interconnects people and machines and things. In the embodiments of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.

[0048] Furthermore, in the embodiments of the present application, a STA may be a device in a connected vehicle system. The communication methods in a connected vehicle system are collectively referred to as V2X (where X represents everything). For example, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0049] In addition, in an embodiment of the present application, STA may also include sensors such as smart printers, train detectors, and gas stations. 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.

[0050] In addition, the AP device in the embodiment of the present application may be a device for communicating with a STA. 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.

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

[0052] From the perspective of STA-supported communication standards, in some implementations, non-AP STAs can support the 802.11be standard. Non-AP STAs can also support various current and future 802.11 family wireless local area network (WLAN) standards, including 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0053] In the embodiments of the present application, there is no limitation on the frequency bands supported by WLAN technology. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to, low frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (e.g., 45 GHz, 60 GHz).

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

[0055] Extremely high throughput (EHT)-signal (SIG) field

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

[0057] The EHT-SIG field can provide additional signaling to the U-SIG field for STAs decoding the EHT MU PPDU. In an EHT MU PPDU, the EHT-SIG field can include the U-SIG overflow bits, which are common to all users. The EHT-SIG field can also include resource unit (RU) allocation information, allowing STAs to locate corresponding resources used in the EHT modulation field of the PPDU.

[0058] The EHT-SIG field of a 20 MHz EHT MU PPDU may contain 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 contain two EHT-SIG content channels. For OFDMA transmission and multi-user non-OFDMA transmission, the EHT-SIG field of an EHT MU PPDU of 160 MHz or wider may contain 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 Figure 3.

[0059] 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-MIMO (multiple input multiple output), and the number of users allocated for MU-MIMO. The format of the common field can be as shown in Table 1.

[0060] Table 1 Common field format for OFDMA transmission

[0061] 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 the user field of the OFDMA transmission.

[0062] 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 the user encoding blocks can be as shown in Table 2.

[0063] Table 2 Format of user encoding blocks

[0064] The content of the user field depends on whether the address of this field is a non-MU-MIMO assigned user in the RU or a MU-MIMO assigned user in the RU. When the address of this 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 this field is a MU-MIMO assigned user in the RU, the format of the user field can be as shown in Table 4.

[0065] Table 3 User field format for non-MU-MIMO allocation

[0066] Table 4 MU-MIMO allocated user field format

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

[0068] For latency-sensitive services, related technologies have proposed 2D A-PPDU. In 2D A-PPDU, downlink RUs can be allocated not only in the frequency domain but also in the time domain, so as to transmit as many latency-sensitive media access control service data units (MSDUs) as possible on the ongoing PPDU to reduce delay.

[0069] Requirements for inserting delay-sensitive MSDUs into PPDUs may include: (1) being transparent to legacy STAs, including 11be release 1; (2) transmitting as many delay-sensitive MSDUs as possible on an ongoing PPDU (including an FDA-PPDU) to reduce latency; and (3) using only necessary subchannels, as delay-sensitive traffic is usually small and using the entire 320 MHz PPDU is quite wasteful.

[0070] Considering these requirements, the structure of a 2D FD A-PPDU can be as shown in Figure 4. To reduce the complexity of the delay-sensitive MSDU receiver, delay-sensitive MSDUs can be transmitted based on the slot start time. For example, a fixed number of OFDM symbols can be defined for the potential start of a 2D FD A-PPDU for transmitting delay-sensitive MSDUs. For example, as shown in Figure 5, a fixed number of OFDM symbols can also be defined within a downlink (DL) OFDMA MU PPDU for transmitting delay-sensitive MSDUs.

[0071] Low power listening (LPL) for inter-basic service set (BSS) PPDUs (also known as inter-PPDUs)

[0072] Low power (LP) mode typically uses one RF link, low-order MCS, and small bandwidth; while 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 subsequent PPDUs (i.e., data PPDUs) for delivering the target STA's data. The interval between the notification PPDU and the first data PPDU provides sufficient duration for changing the PHY parameters / functions.

[0073] During the LPL process, the target STA initially listens in a dedicated LP mode. 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 include a wake-up indication or an indication of upcoming data. 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 data for the target STA.

[0074] According to the above description, the communication process between AP and STA may involve UHR features such as 2D FD A-PPDU and inter-PPDU LPL. Therefore, the 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, the AP needs to further indicate the time domain resource unit to each STA. For example, in the LPL of inter-PPDU, the AP needs to indicate the PHY parameters of the target STA to enter high power in the notification PPDU. However, how the AP and STA indicate relevant information of the UHR features is not yet clear.

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

[0076] As shown in Figure 7, an embodiment of the present application provides a wireless communication method. The method shown in Figure 7 is applicable to any of the APs and / or STAs described above. For ease of understanding, the following uses "first device" and "second device" to represent devices applicable to this method. In the embodiment of the present application, the first device may be an AP, and the second device may be a STA. Alternatively, the first device in the embodiment of the present application may be a STA, and the second device may be an AP.

[0077] The method shown in Figure 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 the 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. Or 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.

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

[0079] 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, the number of reserved bits available in the user field is relatively small, with 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.

[0080] The first user field may not include subfields, and the UHR feature information may be carried in the first user field itself. For example, the first user field may be an expanded field based on 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. In this case, the number of bits in the first user field is greater than 22 bits, for example, the number of bits in the first user field may be 30 bits. Carrying the UHR feature information in the first user field itself helps reduce the decoding overhead of the second device.

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

[0082] The third user field is described in detail below. Within the first user field, the third user field can be located after the second user field, and the third user field can be adjacent to the second user field, helping the first user quickly locate the third user field. Furthermore, the third user field can 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. In this case, the number of bits of the first user field is also greater than 22 bits.

[0083] The first n bits of the third user field can be used to indicate a first identifier, and the first identifier can be used to indicate a first user. The first n bits of the second user field can also be used to indicate a 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-IDs. 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.

[0084] Furthermore, the first PPDU may also include a first field. The first field may be used to indicate whether the first user field carries a third user field, helping the first user determine whether to search for the corresponding third user field. For example, 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 the 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 the 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.

[0085] In some implementations, the first field may be located within the second user field. For example, when the second user field is the user field described above, the first field may occupy a bit within the user field described above. For example, the first field may occupy a reserved bit within the user field described above.

[0086] 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. For example, 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.

[0087] The first field can be recognized by the second device based on the resource preemption function of the second device. That is, the second device with resource preemption function can recognize the first field and then attempt to find one or more corresponding third user fields. A second device without resource preemption function may not recognize the first field and then not attempt to find one or more corresponding third user fields, which helps reduce the decoding overhead of such second devices. The resource preemption function of the second device can be determined based on 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 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 indicate that the second device supports the resource preemption function. When the value of the first information is the second value, it can indicate 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.

[0088] The following is a detailed introduction to the UHR feature information in the first user field.

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

[0090] Furthermore, the first time domain resource number may be determined based on the second field. That is, the first user field may carry the second field to indicate the first time domain resource number. The second field may occupy L bits in the first user field, where L may be a positive integer less than the total number of bits in the first user field.

[0091] In some implementations, the second field can be used to indicate a first value n, and the first value n can be used to indicate a multiple of the first time domain resource number relative to the second value M. The first time domain resource number can then be determined based on the product n×M of the first value n and the second value M, and the product n×M can be used to indicate the number of the first n×M OFDM symbols occupied by the first service in the first time domain resource. Alternatively, the product n×M can also be used to indicate the number of the last n×M 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 can be 5, 10, or 20. The second value M can be predefined or preconfigured by the protocol, or the second value M can also 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.

[0092] 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 resource 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 via 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. For example, 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, the second device is facilitated to quickly determine the number of first time domain resources.

[0093] In some other implementations, the second field may be used to indicate a first value n, which may be used to indicate that the first service is in the nth time domain resource. The number of first time domain resources may be determined based on the first value n and a second value M, which 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 resource 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 via the L-SIG field in the first PPDU. The first value n is a positive integer, for example, 1, 2, 3, or 4. The second value M is also a positive integer, for example, 5, 10, or 20. The second value M may be predefined or preconfigured by the protocol, or may be determined by negotiation between the first and second devices. The second field may simply indicate that the first service is in the nth time domain resource, helping to reduce the amount of information carried by the first user field.

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

[0095] It is worth noting that if the first service described above can be a low-latency service, the low-latency service can 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 can be occupied by non-low-latency services. Alternatively, if the first service can be a non-low-latency service, the non-low-latency service can 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 can be occupied by low-latency services.

[0096] The UHR feature information may also include parameters corresponding to the low-power listening mode to facilitate the second device to switch the listening mode. The parameters corresponding to the low-power listening mode may be parameters that indicate 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 high power consumption from the low-power listening mode. Exemplarily, the field carrying high power bandwidth (hereinafter referred to as the "high power bandwidth field") can occupy 2 bits in the first user field. 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. When the value of the high power bandwidth field is 3, it can represent 320MHz.

[0097] In addition to UHR feature information, the first user field may also carry basic information about the first user. This basic information may include STA-ID, MCS, spatial stream, coding mode, and enabled beamforming parameters. For example, the first user field may also include a fundamental information field, in which case the basic information may be carried.

[0098] The wireless communication method according to the embodiment of the present application is described below with reference to Figures 8 to 12. It should be noted that Figures 8 to 12 take the example of the first device being an AP and the second device being a STA.

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

[0100] 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 UHR MU PPDU bandwidth 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.

[0101] For example, the format of the UHR-SIG field may be the same as the format of the EHT-SIG shown in Figure 3. 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.

[0102] As described above, the first PPDU may include a first user field. The following describes an example of the first user field of the first PPDU in the wireless communication method according to an embodiment of the present application, with reference to Figures 9 and 10. For example, the first PPDU in Figures 9 and 10 may be the UHR MU PPDU shown in Figure 8, and the first user field may be located in the UHR-SIG field of the UHR MU PPDU.

[0103] As shown in Figure 9, 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 feature information can be carried in the first user field itself. In Figure 9, the UHR feature information takes the first time domain resource number as an example, and the first time domain resource number 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 (low latency preemption time resource) / non-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 first user's STA-ID, MCS, spatial stream, coding mode, and enabled beamforming parameters. 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 number of bits in 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 reserved. The values ​​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 sub-fields in Table 5 or Table 6. The arrangement and combination of the sub-fields 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.

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

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

[0106] It is worth noting that the UHR feature information carried by the first user field shown in Figure 9 may also include parameters corresponding to the low power monitoring mode. For example, taking the bit N of the first user field as 30, the first user field carrying the fundamental information 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) can be as shown in Table 7 or Table 8. Among them, the fundamental information can occupy the first 22 bits of the first user field, the low latency preemption time resource / non-low latency time resource field can occupy the 6 bits after the fundamental information, and the high power bandwidth field can occupy the remaining 2 bits. For example, 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 the subfields shown in Table 7 or Table 8 is one of multiple implementations of the first user field and does not constitute a limitation on the first user field.

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

[0108] Table 8 Format of the first user field for MU-MIMO allocation

[0109] As shown in Figure 10, 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 Figure 9, 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 22 bits. The user extension field may be located after the user field and 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 enabled 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. Exemplarily, 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 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 and the user field can be located in the same user encoding blocks. 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 is the second field, which 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. 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 subfields in Table 9. The subfield 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.

[0110] Table 9 User extension field format

[0111] It is worth noting that the UHR feature information carried by the first user field shown in Figure 10 may also include parameters corresponding to the low-power monitoring mode. Exemplarily, the user extension field that carries 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) can be as shown in Table 10. Among them, the STA-ID of the first user can occupy the first 11 bits of the user extension field, the low latency preemption time resource / non-low latency time resource field can occupy the 6 bits after the STA-ID, the high power bandwidth field can occupy the 2 bits after the low latency preemption time resource / non-low latency time resource field, and the remaining 3 bits 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 10. The permutation and combination of the 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.

[0112] Table 10 User extension field format

[0113] In addition, the UHR-SIG field shown in Figure 10 includes a UHR-SIG content channel. As mentioned above, for a UHR MU PPDU greater than 20MHz, when OFDMA transmission and multi-user non-OFDMA transmission are performed, its UHR-SIG field may include multiple UHR-SIG content channels. Therefore, the UHR-SIG field shown in Figure 10 may also include multiple UHR-SIG content channels. If the UHR-SIG field shown in Figure 10 includes multiple UHR-SIG content channels, the content in the user specific field of different UHR-SIG content channels may be different. For example, part of the UHR-SIG content channel may include a user extension field, while the remaining UHR-SIG content channel may not include a user extension field. For example, when a 40MHz UHR MU PPDU is transmitted using OFDMA, UHR-SIG content channel 1 may include a user extension field; and UHR-SIG content channel 2 may not include a user extension field.

[0114] As previously described, when the first user field includes the third user field, the first PPDU may also include a first field to indicate whether the first user field carries the third user field. The first field of the wireless communication method according to an embodiment of the present application is described below using the first user field shown in FIG. 10 as an example, in conjunction with FIG. 11 and FIG. 12 . For ease of understanding, the first field may be a user extension enable field.

[0115] As shown in Figure 11, the first field (taking the user extension enable field as an example) can 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 can be as shown in Table 11, and the user extension enable field can 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 can 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 own STA-ID. When the value of the user extension enable field is 1, it can indicate that there is no user extension field. It is worth noting that the user field in the embodiment of the present application can be composed of one or more sub-fields in Table 11. The combination of sub-fields shown in Table 11 is one of the multiple implementation methods of the user field and does not constitute a limitation on the user field.

[0116] Table 11: User field format for non-MU-MIMO

[0117] As shown in Figure 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 own 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 sub-fields in Table 12. The combination of sub-fields shown in Table 12 is one of the multiple implementation methods of the common field and does not constitute a limitation on the common field.

[0118] Table 12 Common field format

[0119] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 12. 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. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0120] Figure 13 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 Figure 13 is a first device and may include a sending module 1310. Sending module 1310 may be configured to send a first PPDU to a second device. The first PPDU may include a first user field for a first user, which may carry UHR feature information.

[0121] 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 conjunction with Figures 7 to 12 above. The communication device 1300 includes units or modules 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 should be known to those skilled in the art. The text descriptions corresponding to the aforementioned Figures 7 to 12 can be introduced into this example and correspond to the modules in the communication device 1300.

[0122] Figure 14 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 Figure 14 is a second device and may include a receiving module 1410. Receiving module 1410 may be configured to receive a first PPDU sent by a first device. The first PPDU may include a first user field for a first user, which may carry UHR feature information.

[0123] 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 introduced in conjunction with Figures 7 to 12 above. The communication device 1400 includes units or modules 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 again here. However, 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 and correspond to the modules in the communication device 1400.

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

[0125] 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 be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A wireless communication method, characterized in that, 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 UHR feature information is carried in the first user field.

2. The method according to claim 1, wherein 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.

3. The method according to claim 2, wherein 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.

4. The method according to claim 2 or 3, characterized in that, The third user field has the same number of bits as the second user field.

5. The method according to any one of claims 2 to 4, 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.

6. The method according to any one of claims 2 to 5, 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 the first user, and the second identifier is the same as the first identifier.

7. The method according to claim 5 or 6, characterized in that, The value of n is 11.

8. 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.

9. The method according to any one of claims 2 to 8, characterized in that, The first PPDU further includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field.

10. The method according to claim 9, wherein The first field is located in the second user field.

11. The method according to claim 9, wherein The first PPDU further includes a first general field, and the first field is located in the first general field.

12. The method according to any one of claims 9 to 11, characterized in that The first field is recognized by the second device based on the resource preemption function of the second device.

13. The method according to claim 12, characterized in that, The preemption function is determined based on the first information of the second device, and the first information is maintained by the management entity of the second device.

14. The method according to any one of claims 1 to 13, characterized in that, The UHR feature information includes a first time-domain resource number, 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 resource, the first time-domain resource is the time-domain resource divided in the first frequency-domain RU, and the first frequency-domain RU corresponds to the first user.

15. The method according to claim 14, wherein The first time-domain resource number is determined based on a second field.

16. The method according to claim 15, wherein The second field is used to indicate a first value n, and the first value n is used to indicate the multiple of the first time-domain resource number relative to a second value M, and the second value M is a positive integer.

17. The method according to claim 16, wherein The first time-domain resource number 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 OFDM symbols occupied by the first service in the first time-domain resource, or the product n×M is used to indicate the last n×M OFDM symbols occupied by the first service in the first time-domain resource.

18. The method according to claim 15, wherein, The second field is used to indicate a first value n and a second value M, the first value n is used to indicate the first service 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.

19. The method according to claim 15, characterized in that, The second field is used to indicate a first value n, and the first value n is used to indicate the first service in the nth time-domain resource.

20. The method according to claim 19, wherein, The first time-domain resource number is based on the first value n and the second value M, and the second value M is used to indicate the number of OFDM symbols in each time-domain resource.

21. The method according to claim 20, characterized in that, The second value M is predefined or preconfigured by the protocol, or the second value M is determined through negotiation between the first device and the second device.

22. The method according to claim 15, wherein, 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 in each time-domain resource.

23. The method according to claim 22, wherein The number of the first 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.

24. The method according to claim 23, wherein The second value M is predefined or preconfigured by the protocol, or the second value M is determined through negotiation between the first device and the second device.

25. The method according to any one of claims 14 to 24, characterized in that, The first service is a low-latency service, or the first service is a non-low-latency service.

26. The method according to any one of claims 1 to 25, characterized in that, The UHR feature information further includes parameters corresponding to the low-power listening mode.

27. The method according to any one of claims 1 to 26, characterized in that, The first user field further carries the basic information of the first user.

28. The method according to any one of claims 1 to 27, characterized in that The first device is an AP device and the second device is an STA device, or the first device is an STA device and the second device is an AP device.

29. 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.

30. 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.

31. A wireless communication method, characterized in that, Including: The second device receives a first PPDU sent by the first device, and the first PPDU includes a first user field of the first user, and the first user field carries UHR feature information.

32. The method according to claim 31, wherein 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.

33. The method according to claim 32, wherein 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.

34. The method according to claim 32 or 33, characterized in that, The number of bits of the third user field is the same as that of the second user field.

35. The method according to any one of claims 32 to 34, 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.

36. The method according to any one of claims 32 to 35, characterized in that, The first n bits of the second user field are used to indicate a second identifier, and the second identifier is used to indicate the first user, and the second identifier is the same as the first identifier.

37. The method according to claim 35 or 36, characterized in that, The value of n is 11.

38. The method according to any one of claims 32 to 37, characterized in that, The second user field and the third user field are located in the same user coding block.

39. The method according to any one of claims 32 to 38, characterized in that, The first PPDU further includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field.

40. The method according to claim 39, characterized in that, The first field is located in the second user field.

41. The method according to claim 39, wherein, The first PPDU further includes a first general field, and the first field is located in the first general field.

42. The method according to any one of claims 39 to 41, characterized in that, The first field is recognized by the second device based on the resource preemption function of the second device.

43. The method according to claim 42, wherein The preemption function is determined based on the first information of the second device, and the first information is maintained by the management entity of the second device.

44. The method according to any one of claims 31 to 43, characterized in that, The UHR feature information includes the number of the first time-domain resources. The number of the first time-domain resources 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.

45. The method according to claim 44, characterized in that, The number of the first time-domain resources is determined based on the second field.

46. The method according to claim 45, wherein The second field is used to indicate a first value n, and the first value n is used to indicate a multiple of the number of the first time-domain resources relative to a second value M, where the second value M is a positive integer.

47. The method according to claim 46, wherein The number of the first 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 number of the first n×M OFDM symbols occupied by the first service in the first time-domain resources, or the product n×M is used to indicate the number of the last n×M OFDM symbols occupied by the first service in the first time-domain resources.

48. The method according to claim 45, characterized in that, The second field is used to indicate a first value n and a second value M, where 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 of each time-domain resource.

49. The method according to claim 45, 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.

50. The method according to claim 49, characterized in that, The number of the first time-domain resources is based on the first value n and the second value M, and the second value M is used to indicate the number of OFDM symbols of each time-domain resource.

51. The method according to claim 50, wherein The second value M is predefined or preconfigured by a protocol, or the second value M is determined through negotiation between the first device and the second device.

52. The method according to claim 45, 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.

53. The method according to claim 52, characterized in that, The number of the first time-domain resources is determined based on the first value n and the second value M, and the second value M is used to indicate that the first service is in the Mth time-domain resource.

54. The method according to claim 53, wherein The second value M is predefined or preconfigured by a protocol, or the second value M is determined through negotiation between the first device and the second device.

55. The method according to any one of claims 44 to 54, characterized in that, The first service is a low-latency service, or the first service is a non-low-latency service.

56. The method according to any one of claims 31 to 55, characterized in that The UHR feature information further includes parameters corresponding to the low-power listening mode.

57. The method according to any one of claims 31 to 56, characterized in that The first user field further carries the basic information of the first user.

58. The method according to any one of claims 31 to 57, 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.

59. The method according to any one of claims 34 to 58, characterized in that, The number of bits of the second user field and the third user field is 22 bits.

60. The method according to any one of claims 31 to 59, characterized in that The number of bits of the first user field is greater than 22 bits.

61. A communication device, which is a first device and includes: A sending module, configured 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.

62. The communication device according to claim 61, wherein, The first user field includes a second user field and a third user field, where 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.

63. The communication device according to claim 62, 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.

64. The communication device according to claim 62 or 63, characterized in that, The third user field has the same number of bits as the second user field.

65. The communication device according to any one of claims 62 to 64, 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.

66. The communication device according to any one of claims 62 to 65, 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.

67. The communication device according to claim 65 or 66, characterized in that, The value of n is 11.

68. The communication device according to any one of claims 62 to 67, characterized in that, The second user field and the third user field are located in the same user coding block.

69. The communication device according to any one of claims 62 to 68, characterized in that, The first PPDU further includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field.

70. The communication device according to claim 69, characterized in that, The first field is located in the second user field.

71. The communication device according to claim 69, characterized in that, The first PPDU further includes a first general field, and the first field is located in the first general field.

72. The communication device according to any one of claims 69 to 71, characterized in that, The first field is recognized by the second device based on the resource preemption function of the second device.

73. The communication device according to claim 72, 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.

74. The communication device according to any one of claims 61 to 73, characterized in that, The UHR feature information includes a first time-domain resource number, the first time-domain resource number is the number of OFDM symbols occupied by a first service of the first user in a first time-domain resource, the first time-domain resource is a time-domain resource divided in a first frequency-domain RU, and the first frequency-domain RU corresponds to the first user.

75. The communication device according to claim 74, characterized in that, The first time-domain resource number is determined based on a second field.

76. The communication device according to claim 75, characterized in that, The second field is used to indicate a first value n, and 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.

77. The communication device according to claim 76, characterized in that, The first time-domain resource number 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 OFDM symbols occupied by the first service in the first time-domain resource, or the product n×M is used to indicate the last n×M OFDM symbols occupied by the first service in the first time-domain resource.

78. The communication device according to claim 75, 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 the first service 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.

79. The communication device according to claim 75, characterized in that, The second field is used to indicate a first value n, and the first value n is used to indicate the first service in the nth time-domain resource.

80. The communication device according to claim 79, wherein The first time-domain resource number is based on the first value n and the second value M, and the second value M is used to indicate the number of OFDM symbols in each time-domain resource.

81. The communication device according to claim 80, characterized in that, The second value M is predefined or preconfigured by a protocol, or the second value M is determined through negotiation between the first device and the second device.

82. The communication device according to claim 75, 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 in each time-domain resource.

83. The communication device according to claim 82, characterized in that, The first time-domain resource number is determined based on the first value n and the second value M, and the second value M is used to indicate the first service in the Mth time-domain resource.

84. The communication device according to claim 83, wherein, The second value M is predefined or preconfigured by a protocol, or the second value M is determined through negotiation between the first device and the second device.

85. The communication device according to any one of claims 74 to 84, characterized in that, The first service is a low-latency service, or the first service is a non-low-latency service.

86. The communication device according to any one of claims 61 to 85, characterized in that, The UHR feature information further includes parameters corresponding to a low-power listening mode.

87. The communication device according to any one of claims 61 to 86, characterized in that, The first user field further carries basic information of the first user.

88. The communication device according to any one of claims 61 to 87, 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.

89. The communication device according to any one of claims 64 to 88, characterized in that, The number of bits of the second user field and the third user field is 22 bits.

90. The communication device according to any one of claims 61 to 89, characterized in that, The number of bits of the first user field is greater than 22 bits.

91. A communication device, which is the second device, includes: A receiving module, configured 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.

92. The communication device according to claim 91, characterized in that, The first user field includes a second user field and a third user field, where 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.

93. The communication device according to claim 92, characterized in that, In the first user field, the third user field is located after the second user field and is adjacent to the second user field.

94. The communication device according to claim 92 or 93, 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, 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.

96. The communication device according to any one of claims 92 to 95, characterized in that, The first n bits of the second user field are used to indicate a second identifier, and the second identifier is used to indicate the first user, and the second identifier is the same as the first identifier.

97. The communication device according to claim 95 or 96, characterized in that, The value of n is 11.

98. The communication device according to any one of claims 92 to 97, characterized in that The second user field and the third user field are located in the same user coding block.

99. The communication device according to any one of claims 92 to 98, characterized in that, The first PPDU further includes a first field, and the first field is used to indicate whether the third user field is carried in the first user field.

100. The communication device according to claim 99, characterized in that, The first field is located in the second user field.

101. The communication device according to claim 99, characterized in that, The first PPDU further includes a first general field, and the first field is located in the first general field.

102. The communication device according to any one of claims 99 to 101, characterized in that, The first field is recognized by the second device based on the resource preemption function of the second device.

103. The communication device according to claim 102, 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.

104. The communication device according to any one of claims 91 to 103, characterized in that, The UHR feature information includes a first time-domain resource number, where the first time-domain resource number is the number of OFDM symbols occupied by a first service of the first user in a first time-domain resource, the first time-domain resource is a time-domain resource divided in a first frequency-domain RU, and the first frequency-domain RU corresponds to the first user.

105. The communication device according to claim 104, characterized in that, The first time-domain resource number is determined based on a second field.

106. The communication device according to claim 105, wherein The second field is used to indicate a first value n, and 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.

107. The communication device according to claim 106, wherein The first time-domain resource number 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 OFDM symbols occupied by the first service in the first time-domain resource, or the product n×M is used to indicate the last n×M OFDM symbols occupied by the first service in the first time-domain resource.

108. The communication device according to claim 105, characterized in that, The second field is used to indicate a first value n and a second value M, where 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.

109. The communication device according to claim 105, characterized in that, The second field is used to indicate a first value n, where 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, wherein The number of the first time-domain resources is based on the first value n and the second value M, where the second value M is used to indicate the number of OFDM symbols in each time-domain resource.

111. The communication device according to claim 110, characterized in that, The second value M is predefined or preconfigured by the protocol, or the second value M is determined through negotiation between the first device and the second device. The communication device according to claim 105, wherein, The second field is used to indicate a first value n, where the first value n is used to indicate the number of OFDM symbols in each time-domain resource.

113. The communication device according to claim 112, characterized in that, The number of the first time-domain resources is determined based on the first value n and the second value M, where the second value M is used to indicate that the first service is in the Mth time-domain resource.

114. The communication device according to claim 113, characterized in that, The second value M is predefined or preconfigured by the protocol, or the second value M is determined through negotiation between the first device and the second device.

115. The communication device according to any one of claims 104 to 114, characterized in that, The first service is a low-latency service, or the first service is a non-low-latency service.

116. The communication device according to any one of claims 91 to 115, characterized in that, The UHR feature information further includes parameters corresponding to the low-power listening mode.

117. The communication device according to any one of claims 91 to 116, characterized in that, The first user field further carries the basic information of the first user.

118. The communication device according to any one of claims 91 to 117, 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.

119. The communication device according to any one of claims 94 to 118, 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, characterized in that The number of bits of the first user field is greater than 22 bits.

121. A communication device, characterized in that, It includes a memory and a processor. The memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method according to any one of claims 1-30.

122. A communication device, characterized in that, It includes a memory and a processor. The memory is used to store a program, and the processor is used to call the program in the memory so that the communication device executes the method according to any one of claims 31-60.

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

124. A chip, characterized in that, It includes a processor, which is used to call a program from a memory so that the device installed with the chip executes the method according to any one of claims 1-30 or 31-60.

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

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

127. 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.

Images