Wireless communication method and communication device

Abstract

The invention provides a wireless communication method and communication equipment. The method comprises the following steps: a first device receives a first field; wherein the first field is used for indicating the first equipment to adjust the length of the sent data unit. According to the invention, parameters can be provided for length adjustment of the sent data unit, so that the probability of interference occurrence is reduced, the packet loss rate is further reduced, and the reliability of a link is improved.

Description

Wireless communication method and communication device Technical Field

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

[0002] Communication devices may encounter interference. For example, interference can be internal or external. Interference can affect ongoing transmission or reception on the communication device. Related art methods for reducing interference all have problems.

[0003] Summary of the Invention

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

[0005] In a first aspect, a wireless communication method is provided, the method comprising: a first device receiving a first field; wherein the first field is used to instruct the first device to adjust the length of a sent data unit.

[0006] In a second aspect, a wireless communication method is provided, the method comprising: a second device sending a first field to a first device; wherein the first field is used to instruct the first device to adjust the length of a sent data unit.

[0007] According to a third aspect, a communication device is provided. The communication device is a first device, and includes: a receiving unit, configured to receive a first field; wherein the first field is configured to instruct the first device to adjust the length of a data unit to be sent.

[0008] In a fourth aspect, a communication device is provided, which is a second device and includes: a sending unit, configured to send a first field to a first device; wherein the first field is configured to instruct the first device to adjust the length of a data unit to be sent.

[0009] In a fifth aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory to enable the communication device to perform some or all of the steps in the above-mentioned various aspects of the method.

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

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

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

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

[0014] The first device can adaptively adjust the length of the data unit to be sent according to the first field. For example, the first field can indicate that the first device needs to adjust the length of the physical layer service data unit (PSDU), thereby avoiding problems such as retransmission caused by the first device choosing to increase the modulation and coding scheme (MCS) to reduce interference. For another example, the first field can indicate how to adjust the length of the data unit, thereby reducing the time for the first device to determine the length of the data unit to be sent to reduce interference, thereby increasing the speed at which the link is adjusted to the optimal (or better) parameters. It can be seen from this that the present application can provide parameters for adjusting the length of the data unit to be sent, thereby reducing the probability of interference, thereby reducing the packet loss rate, and improving the reliability of the link. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] FIG2 is an example diagram of an acknowledgment and retransmission mechanism.

[0017] FIG3 is a diagram illustrating an example of a block acknowledgement (BA) frame format.

[0018] FIG4 is an example diagram of a medium access control (MAC) frame.

[0019] FIG. 5A is a diagram showing an example format of an A-control field.

[0020] FIG5B is a diagram showing an example of the format of a control subfield.

[0021] FIG. 5C is a diagram showing an example of the format of a control information subfield in a control subfield.

[0022] FIG6 is a schematic diagram of a scenario in which overlapping basic service sets (OBSS) interference exists, to which an embodiment of the present application is applicable.

[0023] FIG7 is a timing diagram showing an example of an OBSS interference condition.

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

[0025] FIG9 is a schematic diagram of a BA frame format including a BA control field provided in an embodiment of the present application.

[0026] FIG10 is a schematic diagram of a compressed BA frame format provided in an embodiment of the present application.

[0027] FIG. 11 is a diagram illustrating an example of a multi-TID BA variant frame format provided in an embodiment of the present application.

[0028] FIG12 is an example diagram of a multi-STA BA variant frame format provided in an embodiment of the present application.

[0029] FIG13 is a schematic diagram of a ULA control field format provided in an embodiment of the present application.

[0030] Figure 14 is a schematic diagram of the format of the universal signaling field (U-SIG) field in a physical layer protocol data unit (PPDU) provided in an embodiment of the present application.

[0031] FIG15 is a timing diagram illustrating an example of reducing interference using the method provided in an embodiment of the present application.

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

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

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

[0035] The technical solutions in this application will be described below in conjunction with the accompanying drawings. To facilitate understanding, the terms involved in this application will first be explained.

[0036] Communication System

[0037] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), 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.

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

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

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

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

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

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

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

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

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

[0047] In the embodiments of the present application, a STA device 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 STA devices 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.

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

[0049] By way of example and not limitation, in the embodiments of this application, the STA device 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, 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.

[0050] In addition, in embodiments of the present application, the STA device 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 embodiments of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

[0051] Furthermore, in the embodiments of the present application, the STA device 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.

[0052] In addition, in an embodiment of the present application, the STA device 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.

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

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

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

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

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

[0058] Confirmation and retransmission mechanism

[0059] The following describes the acknowledgment procedure using frames that require immediate acknowledgment.

[0060] Related technologies (such as the 802.11 standard) define one or more of the following frames as requiring immediate acknowledgment: unicast non-Action No Ack management frames (Individually addressed Management frames other than Action No Ack frames); unicast non-QoS data frames (Individually addressed non-QoS Data frames); unicast QoS data frames using Normal Ack or Implicit BAR ack policy (Individually addressed QoS Data frames with Normal Ack or Implicit BAR ack policy); BlockAck frames not sent in immediate response to A-MPDU; BlockAckReq frames; PS-Poll frames, which can be acknowledged by generating a Data frame.

[0061] For frames with an immediate acknowledgment requirement set to 1 in the To distribution system (To DS) subfield, the receiving STA must send an acknowledgment (Ack) frame or a block acknowledgment (BA) frame after the short interframe space (SIFS) interval, regardless of the media's busy or idle state. As shown in Figure 2, the source sends a data frame. This data frame requires immediate acknowledgment. After receiving the data frame, the destination must send an ACK frame or a block acknowledgment (BA) frame after the SIFS interval.

[0062] After sending a MAC protocol data unit (MPDU) that requires a response Ack or BA frame (e.g., the MPDU including a data frame in Figure 2), the STA (e.g., the source in Figure 2) should wait for the confirmation timeout (AckTimeout) interval starting from the PHYTXEND.confirm primitive. The value of the AckTimeout interval is aSIFSTime + aSlotTime + aRxPHYStartDelay. Among them, aSIFSTime can indicate the SIFS time; aSlotTime can indicate the time slot time; and aRxPHYStartDelay can indicate the delay time for the start of receiving the physical layer.

[0063] If the PHY-RXSTART.indication primitive does not occur during the AckTimeout interval, the STA may conclude that the MPDU transmission has failed, and the STA will invoke its backoff procedure when the AckTimeout interval expires.

[0064] If the PHY-RXSTART.indication primitive does appear during the AckTimeout interval, the STA will wait for the corresponding PHY-RXEND.indication primitive to determine whether the MPDU transmission is successful. If the STA recognizes a valid Ack frame addressed to the STA and corresponds to the PHY-RXEND.indication primitive, the recognition is interpreted as a successful confirmation.

[0065] If a STA does not recognize a valid Ack frame addressed to it, it shall interpret this as a failure in its MPDU transmission. In this case, the STA shall invoke its backoff procedure at the PHY-RXEND.indication primitive.

[0066] For the distributed coordination function (DCF), in the specific case of receiving a corrupted Ack or BA frame, the backoff procedure results in the use of an extended inter-frame space (EIFS) instead of the distributed inter-frame spacing (DIFS) or arbitration inter-frame space (AIFS) after the AckTimeout interval and the subsequent reception of the corrupted Ack or BA frame.

[0067] For the enhanced distributed channel access function (EDCAF), if the transmission of an MPDU in a non-initial PPDU of a transmission opportunity (TXOP) holder fails, the STA can perform point coordination function inter-frame space (PIFS) recovery or wait for the transmit network allocation vector (TXNAV) timer to expire and invoke the backoff procedure. How the STA chooses between these options may be implementation-dependent.

[0068] It should be noted that PIFS recovery may mean that after a valid response is received to the initial frame of a TXOP, if the duration / ID field is set to the duration of multiple frame exchange sequences and a subsequent transmission failure occurs, the corresponding channel access function may start transmission after the CS mechanism indicates that the medium is idle at the TxPIFS timeslot boundary, provided that the duration of the transmission plus the total duration of any expected confirmation frames and the applicable IFS is less than the value of the remaining TXNAV timer.

[0069] dynamic fragmentation

[0070] Related art defines a process for generating unevenly segmented MAC service data units (MSDUs), A-MSDUs, or MMPDUs, where each segment is not necessarily the same length. The following example illustrates the segmentation process.

[0071] The length of the first fragment shall be greater than or equal to the minimum fragment size indicated in the minimum fragment size subfield in the capability information field (e.g., the HE capability information field) in the capability element (e.g., the high efficiency (HE) capability element) sent by the receiving STA. If the length of the MSDU, A-MSDU, or MMPDU is less than the minimum fragment size, the MSDU, A-MSDU, or MMPDU shall not be fragmented. Fragments generated by dynamic fragmentation may be referred to as dynamic fragments.

[0072] STAs (e.g., HE STAs) can negotiate to use different levels of dynamic fragmentation, such as level 1, level 2, or level 3.

[0073] Level 1 supports one dynamic fragment in a non-A-MPDU; it does not support dynamic fragments in an A-MPDU that does not contain an S-MPDU.

[0074] Level 2 supports dynamic fragments in A-MPDUs that do not contain S-MPDUs, but the following conditions must be met: there is no more than one dynamic fragment for any given MSDU or A-MSDU in the A-MPDU, and the dynamic fragment is sent according to the block ACK protocol; there is no more than one dynamic fragment for any given MMPDU in the A-MPDU.

[0075] Level 3 supports dynamic fragments in an A-MPDU that does not contain an S-MPDU, provided that the following conditions are met: there are no more than four dynamic fragments in an A-MPDU for any given MSDU or A-MSDU, and these dynamic fragments are sent according to the Block ACK protocol; there are no more than one dynamic fragment in an A-MPDU.

[0076] BA frame

[0077] FIG3 is a diagram showing an example of a BA frame format.

[0078] As shown in Figure 3, a BA frame may include one or more of the following fields: frame control, duration, receiver address (RA), transmission address (TA), BA control, BA information, and frame check sequence (FCS). The BA control field may include one or more of the following fields: reserved, BA type, no memory kept, memory configuration tag, management acknowledgment (MANAGEMENT ACK), and TID information (TID_INFO). These fields are described below.

[0079] The frame control field is used to carry basic information such as the frame type.

[0080] The duration field is used to indicate the remaining duration of the TXOP.

[0081] The RA field is used to indicate the MAC address of the receiving station of the frame.

[0082] The TA field is used to indicate the MAC address of the sending station of the frame.

[0083] The BA type field indicates the BA frame variant type. For the values ​​and meanings of the BA type field, refer to Table 1.

[0084] Table 1

[0085] The "no memory kept", "memory configuration tag", and "management Ack" fields are used only by EDMG STA and are not described here.

[0086] The TID_INFO field has different meanings in different BA frame variants.

[0087] The BA information field has different formats and meanings in different BA frame variants.

[0088] A-control field

[0089] The A-control field may be a high throughput (HT) control field. To facilitate understanding of the A-control field, the HT control field is first introduced.

[0090] The QoS data frame, QoS null frame, and management frame can all contain the HT Control field. The presence of the HT Control field is controlled by the +HTC subfield in the Frame Control field.

[0091] Figure 4 is an example diagram of a MAC frame. Figure 4 illustrates the possible location of the HT Control field in a MAC frame. As shown in Figure 4, the HT Control field is located within the MAC header. A MAC frame may also include one or more of the following fields: Frame Control, Duration / ID, Address 1, Address 2, Address 3, Sequence Control, Address 4, QoS Control, Frame Body, and FCS.

[0092] Table 2 shows an example of the format of the HT control field. As shown in Table 2, the A-control field may be an HT control field when both B0 and B1 are 1.

[0093] Table 2

[0094] Figure 5A is a diagram showing an example format of an A-control field. As shown in Figure 5 , the A-control field may include one or more of the following fields: a control list and padding.

[0095] The control list field may include one or more control subfields. Figure 5B illustrates an example format of a control subfield. As shown in Figure 5B, the control subfield may include one or more of the following subfields: control ID and control information. The control ID subfield may indicate the type of the specific A-control subfield. Table 3 illustrates exemplary values ​​and meanings of the control ID subfield.

[0096] Table 3

[0097] It should be noted that the ELA control subfield (control flag value is 2) involved in Table 3 can contain parameters related to multiple link modulation and transmission modes for fast adaptive control of the EHT link. The specific format of the control information subfield in the ELA control subfield can be shown in Figure 5C.

[0098] As shown in Figure 5C, the control information subfield in the ELA control subfield may include one or more of the following fields: unsolicited MCS feedback (unsolicited MCS feedback, unsolicited MFB), MCS request (MCS request, MRQ) / uplink EHT triggered PPDU MFB (UL EHT TB PPDU MFB), number of spatial streams (NSS), UHR-MCS, resource unit (RU) allocation (RU allocation), PS160, bandwidth (BW), MCS request sequence indication (MRQ sequence identifier, MSI) or partial PPDU parameters (MSI / partial PPDU parameters), transmit beamforming (TX beamforming), high-efficiency link adaptation / very high throughput link adaptation (HE link adaptation or EHT link adaptation, HLA / ELA). They are explained below.

[0099] The unsolicited MFB field value of 1 indicates that the ELA control field is an unsolicited MFB, and the value of 0 indicates that the ELA control field is an MRQ or a solicited MFB.

[0100] For the MRQ field, when the unsolicited MFB field is set to 1, the MRQ field can indicate whether the ELA control is a request or a response. For example, a MRQ field value of 1 can indicate a request for ELA feedback. For another example, a MRQ field value of 0 can indicate a response to an ELA request.

[0101] For the MRQ field, when the unsolicited MFB field is set to 0, the MRQ field indicates the MFBs for different transmission modes. For example, a MRQ field value of 1 may indicate that the NSS, EHR-MCS, BW, PS160, and RU Allocation fields represent the recommended MFBs for the EHT TB PPDU sent by the station. For another example, a MRQ field value of 0 may indicate that the NSS, UHR-MCS, BW, PS160, and RU Allocation fields represent the recommended MFBs for the PPDU sent to the station.

[0102] The NSS field may indicate the recommended number of spatial streams.

[0103] The EHT-MCS field may indicate the recommended MCS used by the PPDU.

[0104] The PS160 field may indicate: when the size of an RU or multiple resource unit (MRU) is less than or equal to 2×996 subcarriers, the primary 160 MHz channel or secondary 160 MHz channel allocated by the RU or MRU; otherwise, the PS160 subfield together with the RU allocation subfield indicates the RU or MRU index.

[0105] The RU Allocation field may be used to indicate the recommended RU or MRU.

[0106] The BW field may be used to indicate the recommended bandwidth.

[0107] For the MSI / partial PPDU parameter field, when the unsolicited MFB field value is 0, this field can indicate the sequence number of the MFB request; when the unsolicited MFB field value is 1, this field can indicate the type and coding type of the PPDU.

[0108] The Transmit Beamforming field may indicate whether the fed-back MFB is estimated based on a beamformed PPDU. For example, a value of 1 in the Transmit Beamforming field may indicate that the fed-back MFB is estimated for a beamformed PPDU. For another example, a value of 0 in the Transmit Beamforming field may indicate that the fed-back MFB is not estimated for a beamformed PPDU.

[0109] The HLA / ELA field can indicate whether the A-control subfield is HLA or ELA. For example, a value of 1 in the HLA / ELA field can indicate ELA. For another example, a value of 0 in the HLA / ELA field can indicate HLA.

[0110] interference

[0111] Communication devices may encounter interference. Interference can be internal or external. For example, Wi-Fi devices can encounter interference from internal sources, such as Bluetooth and Wi-Fi, or external sources, such as Wi-Fi multi-link operations or other communication technologies.

[0112] Interference can affect ongoing transmission or reception by a communication device. For example, interference can reduce the signal to interference plus noise ratio (SINR), resulting in a failure to receive data packets. Alternatively, interference can force the STA to stop sending signals. When a received PPDU is interfered with and results in data packet loss, not only does the receiver lose some data packets, but the transmitter may also perform some unnecessary or abnormal operations. The operations of the transmitter include, for example, triggering a rate selection mechanism to reduce the rate of subsequent transmissions. The reason why the transmitter performs these unnecessary or abnormal operations is that the transmitter is unaware that the data packet loss is not due to channel conditions, but rather to unexpected and infrequent interference.

[0113] Related art suggests adding a signaling indicator to the BA frame sent as an immediate response to a PPDU transmission, indicating that abnormal interference with PPDU reception is the primary cause of packet loss. This allows the sender to clearly identify the cause of packet loss and take appropriate measures to address it. For example, the indication of whether PPDU reception was interfered with can be a simple 1-bit field. Alternatively, more advanced methods can be used to more accurately locate the impact of interference when needed.

[0114] Figure 6 illustrates a scenario involving two BSSs with OBSS interference. As shown in Figure 6, BSS1 includes AP1, STA1, and STA3; BSS2 includes AP2 and STA2. Because STA1 is in the overlapping coverage area of ​​BSS1 and BSS2, the signal transmitted by AP2 acts as OBSS interference to STA1.

[0115] Since OBSS interference signals generally conform to the WiFi protocol, OBSS interference is generally discontinuous. Figure 7 shows a timing diagram illustrating STA1 experiencing OBSS interference from AP2. It can be seen that the intermittent BA frames sent by AP2 overlap with the data frames sent by AP1, resulting in OBSS interference. As shown in Figure 7, the data frames with SN=1 and SN=3 sent by AP1 to STA1 experience transmission errors and retransmissions. This means that the frames sent by AP1 to STA1 intermittently experience errors and are retransmitted. This shows that OBSS interference can reduce transmission success rates, increase packet loss rates, and increase average transmission latency.

[0116] Interference can be categorized as narrowband interference or wideband interference based on the relative bandwidth of the interfering signal and the normal signal. Narrowband interference occurs when the bandwidth of the interfering signal is significantly smaller than that of the normal signal. Wideband interference occurs when the bandwidth of the interfering signal is equal to or greater than that of the normal signal. Narrowband interference is typically addressed by static puncturing or allocating interference-free RUs. Wideband interference is typically addressed by shortening the PPDU length or suspending transmission.

[0117] To address wideband interference, as mentioned above, a single bit is added to the BA frame to indicate whether a received PPDU is subject to interference. However, this approach has drawbacks. First, after a device detects interference, it must attempt to adjust the PPDU length to the appropriate value, slowing the link's adjustment to optimal parameters. Second, this indication method is not suitable for stations located at the edge of the BSS. For example, if the transmitting station increases the MCS rather than shortening the PSDU to shorten the PPDU length, while this reduces the probability of interference collisions, it will also result in PPDU reception failures due to the lower SNR, resulting in no significant improvement in the overall packet error rate. For example, in Figure 6, STA1, located at the edge of the BSS, is not only subject to OBSS interference but also experiences a lower SNR for the signal received from AP1 than STA3, located at the center of the BSS. Therefore, increasing the MCS of the PPDU sent by AP1 to STA1 may result in reception failure.

[0118] In addition, related technologies have proposed that BA frames can be used to indicate more precise interference location information, such as the period, duty cycle, and frequency of the interfering signal. However, this would incur significant signaling overhead, as each QoS data frame would likely correspond to a BA frame. Furthermore, this high signaling overhead would affect communication efficiency.

[0119] Therefore, it can be seen that the methods for reducing interference in the related art all have problems. In response to this, the present application proposes a wireless communication method shown in FIG8 to solve the above problems.

[0120] The method shown in FIG8 can be performed by a first device and a second device. The first device can be the AP or non-AP STA described above. The second device can be the AP or non-AP STA described above. The first device can send a data unit to the second device to implement communication between the first device and the second device.

[0121] The method shown in FIG. 8 may include step S810 .

[0122] Step S810: The second device sends a first field to the first device.

[0123] The first field may be used to instruct the first device to adjust the length of the data unit to be sent. The data unit may include one or more of the following: PSDU, PPDU.

[0124] The first device adjusting the length of the sent data unit may include: the first device shortening the length of the sent data unit. As mentioned above, shortening the length of the sent data unit can cope with broadband interference.

[0125] In some embodiments, the first field may have other names, which are not limited in this application. For example, the first field may also be called: PSDU length reduction field, PPDU length reduction field, PSDU length field, PPDU length field, etc.

[0126] In some embodiments, the first field may include one or more fields. In the case where the first field includes multiple fields, the multiple fields may jointly instruct the first device to adjust the length of the transmitted data unit.

[0127] The first device can adaptively adjust the length of the data unit to be sent according to the first field. That is, the first field can provide suggestions or instructions for adjusting the length of the data unit. For example, the first field can indicate that the first device needs to adjust the length of the PSDU, thereby avoiding problems such as retransmission caused by the first device choosing to increase the MCS. For another example, the first field can indicate how to adjust the length of the data unit, thereby reducing the time it takes for the first device to determine the length of the data unit, thereby increasing the speed at which the link adjusts to the optimal (or better) parameters. It can be seen from this that the present application can effectively adjust the length of the data unit to be sent, thereby reducing the probability of interference, thereby reducing the packet loss rate, and improving the reliability of the link.

[0128] In some embodiments, the first field may be used to indicate one or more of the following information: whether to adjust the length of the data unit, and how to adjust the length of the data unit.

[0129] When the first field indicates whether to adjust the length of the data unit, the first field may indicate or suggest whether to adjust the data unit according to a first adjustment scheme. The first adjustment scheme may, for example, include adjusting the length of the data unit to N% of a specific length, where N may be a number greater than 0 and less than 100. The specific length may be the length of the original data unit (i.e., the historical data unit). For example, the specific length may be the length of the data unit last sent.

[0130] In the case where the first field indicates whether to adjust the length of the data unit, the first field may include a first bit (i.e., the first field is one bit), and the first bit may be used to indicate whether the first device needs to adjust the length of the data unit to be sent. For example, a value of 0 for the first bit may indicate that the first device does not need to adjust the length of the data unit to be sent; a value of 1 for the first bit may indicate that the first device needs to adjust the length of the data unit to be sent. For another example, a value of 1 for the first bit may indicate that the first device does not need to adjust the length of the data unit to be sent; a value of 0 for the first bit may indicate that the first device needs to adjust the length of the data unit to be sent.

[0131] It can be seen from this that the present application can adjust the length of the data unit with a smaller number of bits, thereby reducing communication overhead.

[0132] The first field may indicate how to adjust the length of the data unit. In other words, the first field may indicate an adjustment scheme for the length of the data unit. For example, when the first field indicates how to adjust the length of the data unit, the first field may indicate: a first length of the adjusted data unit.

[0133] For example, the first length may be a maximum length of the data unit. That is, the first field may indicate the maximum length of the adjusted data unit. The first device may adjust the length of the data unit so that the length of the data unit is less than or equal to the maximum length.

[0134] It should be noted that the first length may also be other lengths related to the data unit, for example, the first length may be the average length or minimum length of the data unit.

[0135] It should be noted that this application does not limit the manner in which the first length is indicated. For example, the first length may be indicated by a data length or a time length. Correspondingly, the unit of the first length may be a data size or a time unit. For example, the unit of the first length may be bytes. For another example, the unit of the first length may be microseconds.

[0136] When the first field indicates the first length, the first field may also simultaneously indicate whether the first device adjusts the length of the data unit being sent. For example, when the value of the first field is a specific value, the first field may indicate that the first device does not need to adjust the length of the data unit being sent. When the value of the first field is not a specific value, the first field may indicate that the first device needs to adjust the length of the data unit being sent, and the first field may indicate the first length. Exemplarily, the specific value may be 0, for example. When the value of the first field is 0, the first field indicates that the first device does not need to adjust the length of the data unit being sent. When the value of the first field is not 0, the value of the first field may indicate the first length.

[0137] In some embodiments, the first field can independently indicate the first length. That is, the first device can determine the first length based solely on the first field. For example, the value of the first field (hereinafter referred to as the first value for ease of description) can be the first length. In another example, the first value can be calculated to be the first length. In another example, a mapping relationship can exist between the value of the first field and the first length, and the first length can be determined based on the mapping relationship and the first value.

[0138] For example, the value of the first field can be represented by A, and the first length C can satisfy: C=A, or C=2 (13+A) -1. For example, the first field can be 2 to 12 bits. The first field value A (A≠0) can indicate the maximum duration (in microseconds) of the PPDU sent by the first device. The first field value 0 can indicate that there is no need to adjust the PPDU length. For another example, the first field can be 2 to 8 bits. The first field value A (A≠0) can indicate that the maximum length of the PSDU sent by the first device does not exceed 2 (13+A) -1 byte. The first field value 0 may indicate that the PSDU length does not need to be adjusted.

[0139] In some embodiments, the first field may be combined with other information to indicate the first length. For example, the first length may be determined by a first value and a second value.

[0140] Exemplarily, the first length C may satisfy: The value of the first field is A, and the value of the second field is B.

[0141] Based on the present application, the first device can not only adjust the length of the sent data unit with reference to the indication of the first field, but also adjust the length of the sent data unit to an appropriate value as quickly as possible in combination with other information.

[0142] It should be noted that the length of the first field can be any value between 2 bits and 12 bits. It is understandable that if the value of the first field is equal to the first length, the first field requires more bits to satisfy the indication of the first length. In this case, the length of the first field can be, for example, any value between 2 bits and 12 bits. If the value of the first field is not equal to the first length (for example, the value of the first field is calculated to obtain the first length), the length of the first field can be smaller. In this case, the length of the first field can be, for example, any value between 2 bits and 8 bits.

[0143] It should be noted that the length of the first field can also be other values, and this application does not impose any restrictions on this.

[0144] The second value may satisfy one or more of the following: the second value is determined based on the value of the second field; the second value is determined based on the value of a static physical layer (PHY) characteristic parameter; the second value is determined based on the length of a data unit historically sent by the first device. Each of these is described below.

[0145] The second value is determined based on the value of the second field

[0146] It is understood that the first field may be combined with one or more fields to indicate the first length, wherein the one or more fields may include the second field, and the one or more fields may be fields different from the first field.

[0147] It should be noted that the second value can be determined based on the value of the second field, which can mean that the second field can directly or indirectly indicate the second value. For example, the second value can be the value of the second field. Alternatively, the second value can be calculated from the value of the second field.

[0148] For example, the second field may be located in a capabilities element. The capabilities element may be sent by the second device. That is, the first device may determine the first length based on the first field and the capabilities information of the second device.

[0149] For example, the second field may include a maximum A-MPDU length exponent extension field. Based on the second field, the maximum A-MPDU length may be determined. The second value may be the maximum A-MPDU length.

[0150] In an optional implementation, when the second field is located in a first-type capability element, the first length may be the length of the first-type data unit. The first type may, for example, include one or more of the following: ultra-high reliability (UHR), extremely high throughput (EHT), high-efficiency (HE), very high-throughput (VHT), and high-throughput (HT). The first device may determine how to adjust the length of the first-type data unit by referring to the second field and the first field in the first-type capability element.

[0151] For example, the second field may be located in one or more of the following element information sent by the second device: a UHR capability element, an EHT capability element, a HE capability element, a VHT capability element, or an HT capability element. If the first device is to send a UHR data unit to the second device, the second field in the UHR capability element may be referenced. If the first device is to send an EHT data unit to the second device, the second field in the EHT capability element may be referenced. If the first device is to send an HE data unit to the second device, the second field in the HE capability element may be referenced. If the first device is to send a VHT data unit to the second device, the second field in the VHT capability element may be referenced. If the first device is to send an HT data unit to the second device, the second field in the HT capability element may be referenced.

[0152] It is understood that the value of the second field in the capability element is related to the capabilities of the second device. The value of the second field in the capability element of different devices may be different. Therefore, based on the second field in the capability element, the first device can adjust the length of the transmitted data unit according to the specific conditions of each device, thereby making the adjustment of the data unit length more real-time or more flexible.

[0153] The second field is described in detail below through Example 1.

[0154] Example 1

[0155] In embodiment 1, the first field is 2 to 8 bits. The second field may be the Maximum A-MPDU Length Exponent Extension field. The value of the first field is A (A≠0) indicating that the station receiving the field needs to adjust the maximum length of the sent PSDU to no more than Byte; a value of 0 indicates that no PSDU length adjustment is required.

[0156] The maximum A-MPDU length may be determined by the Maximum A-MPDU Length Exponent Extension field. The Maximum A-MPDU Length Exponent Extension field may be located in one or more of the following capability elements sent by the second device sending the first field: UHR capability element, EHT capability element, HE capability element, VHT capability element, or HT capability element.

[0157] The Maximum A-MPDU Length Exponent Extension field in the UHR capability element, EHT capability element, HE capability element, VHT capability element, and HT capability element may indicate the maximum length (in bytes) of an A-MPDU that the second device may receive through a UHR PPDU, EHT PPDU, HE PPDU, VHT PPDU, or HT PPDU, respectively.

[0158] If the first device is to send a UHR PPDU to the second device, the Maximum A-MPDU Length Exponent Extension field in the UHR capability element may be referred to; if an EHT PPDU is to be sent, the Maximum A-MPDU Length Exponent Extension field in the EHT capability element may be referred to; if an HE PPDU is to be sent, the Maximum A-MPDU Length Exponent Extension field in the HE capability element may be referred to; if a VHT PPDU is to be sent, the Maximum A-MPDU Length Exponent Extension field in the VHT capability element may be referred to; if an HT PPDU is to be sent, the Maximum A-MPDU Length Exponent Extension field in the HT capability element may be referred to.

[0159] The second value is determined based on the value of the static physical layer characteristic parameter

[0160] Static PHY characteristic parameters may be used to indicate the maximum receive and / or transmit data unit length supported by the PHY. For example, static PHY characteristic parameters may include one or more of the following: the maximum receive and / or transmit PSDU length supported by the physical layer, and the maximum receive and / or transmit PPDU length supported by the physical layer.

[0161] In some embodiments, static PHY feature parameters may include aPSDU maximum length (aPSDUMaxLength) and / or aPPDU maximum duration (aPPDUMaxTime). aPSDUMaxLength may be used to indicate the maximum receive and transmit PSDU length supported by the PHY. aPPDUMaxTime may be used to indicate the maximum receive and transmit PPDU length supported by the PHY. For example, the first device may determine the length of the transmitted PSDU with reference to aPSDUMaxLength and the first field. For another example, the first device may determine the length of the transmitted PPDU with reference to aPPDUMaxTime and the first field.

[0162] It should be noted that the static PHY characteristic parameters may include static PHY characteristic parameters of the first type. Correspondingly, the first length may be the length of the first type of data unit. That is, when the first device needs to send a first type of data unit, the first device may determine the length of the first type of data unit with reference to the first type of static PHY characteristic parameters.

[0163] For example, aPSDUMaxLength may be a static PHY feature parameter of UHR PHY, EHT PHY, HE PHY, VHT PHT, or HT PHY. The first device may determine the length of the UHR PSDU by referring to the UHR PHY feature parameter aPSDUMaxLength. The first device may determine the length of the EHT PSDU by referring to the EHT PHY feature parameter aPSDUMaxLength. The first device may determine the length of the VHT PSDU by referring to the VHT PHY feature parameter aPSDUMaxLength. The first device may determine the length of the HT PSDU by referring to the HT PHY feature parameter PaSDUMaxLength.

[0164] For another example, aPPDUMaxTime may be a static PHY feature parameter of UHR PHY, EHT PHY, HE PHY, VHT PHT, or HT PHY. The first device may determine the length of the UHR PPDU with reference to the UHR PHY feature parameter aPPDUMaxTime. The first device may determine the length of the EHT PPDU with reference to the EHT PHY feature parameter aPPDUMaxTime. The first device may determine the length of the VHT PPDU with reference to the VHT PHY feature parameter aPPDUMaxTime. The first device may determine the length of the HT PPDU with reference to the HT PHY feature parameter aPPDUMaxTime.

[0165] The following is detailed description through Example 2 and Example 3.

[0166] Example 2

[0167] In embodiment 2, the first field is 2 to 8 bits. The first field value A (A≠0) indicates that the first device needs to adjust the maximum length of the sent PSDU to no more than Bytes; the first field value of 0 indicates that the PSDU length does not need to be adjusted. The aPSDUMaxLength is a static PHY feature parameter of UHR PHY, EHT PHY, HE PHY, VHT PHT or HT PHY. aPSDUMaxLength is used to indicate the maximum receive and transmit PSDU length supported by the PHY.

[0168] Example 3

[0169] In embodiment 3, the first field is 2 to 8 bits. The value of the first field is A (A≠0) indicating that the first device needs to adjust the maximum length of the PPDU to be sent. A value of 0 indicates that the PPDU length does not need to be adjusted. aPPDUMaxTime is a static PHY feature parameter of UHR PHY, EHT PHY, HE PHY, VHT PHT or HT PHY. aPPDUMaxTime is used to indicate the maximum receive and send PPDU length supported by the PHY.

[0170] The second value is determined based on the length of the data unit sent historically by the first device.

[0171] The historically sent data unit may be a data unit sent before the current moment. For example, the historically sent data unit may include the last sent data unit.

[0172] The following is explained in detail through Examples 4 and 5.

[0173] Example 4

[0174] In another embodiment, the field is 2 to 8 bits, and its value A (A≠0) indicates that the station receiving the field needs to adjust the maximum length of the sent PSDU to no more than Byte; a value of 0 indicates that no PSDU length adjustment is required.

[0175] Example 5

[0176] In another embodiment, the field is 2 to 8 bits, and its value A (A≠0) indicates that the station receiving the field needs to adjust the length of the PPDU to be sent to a maximum of Byte; a value of 0 indicates that the PPDU length does not need to be adjusted.

[0177] The first field may belong to the first frame or the first PPDU. That is, the first field may be transmitted in the form of a MAC frame or a PHY layer PPDU. The first frame will be described below.

[0178] In some embodiments, the first frame may include one or more of the following: a BA frame, a data frame, a null frame, and a management frame. The data frame may be a QoS data frame. The null frame may be a QoS null frame. The first frame may be a newly added frame or may reuse an existing frame. The first field may be a newly added field in the first frame. Alternatively, the first field may be carried in an existing field in the first frame, i.e., the first field may reuse an existing field. For example, the first field may be carried in a reserved field in the first frame.

[0179] The following description is made by taking the example that the first frame includes a BA frame.

[0180] In some implementations, the first field may belong to a BA control field of a BA frame.

[0181] Optionally, the reserved bits in the BA control field can be used to carry the first field. For example, the B0 reserved field in the BA control field shown in FIG3 can be used to carry the first field. For another example, the B5-B8 reserved fields in the BA control field shown in FIG3 can be used to carry the first field.

[0182] Figure 9 is a schematic diagram of a BA frame format including a BA control field provided in an embodiment of the present application. As shown in Figure 9, the first field (represented by a gray filled rectangle) can occupy 1 bit in the BA control field and be located at B5. As shown in Figure 9, the BA control field may also include one or more of the following fields: frame control, duration, RA, TA, BA control, BA information, and FCS. Among them, the BA control field may include one or more of the following fields: reserved, BA type, no memory kept, memory configuration tag, and management Ack. For the description of these fields, please refer to the description related to Figure 3 above and will not be repeated here.

[0183] It should be noted that the position of the first field in Figure 9 is only an example and the position of the first field is variable.

[0184] In some implementations, the first field may belong to a BA information field of a BA frame.

[0185] Optionally, the BA frame may include a third field that indicates whether the first field is present in the BA information field. For example, a value of 1 in the third field indicates that the first field is present in the BA information field; a value of 0 in the third field indicates that the first field is not present in the BA information field. A value of 0 in the third field indicates that the first field is present in the BA information field; a value of 1 in the third field indicates that the first field is not present in the BA information field.

[0186] Exemplarily, the third field may be located in the BA control field. For example, the third field may be carried by a reserved field.

[0187] In some embodiments, the BA information field may include a fourth field. The first field may be a subfield of the fourth field. In this case, the third field may be used to indicate whether the fourth field is present in the BA information field.

[0188] For example, the fourth field may carry one or more types of feedback information. The information carried by the first field may belong to the one or more types of feedback information. Exemplarily, the fourth field may carry one or more types of feedback information for a UHR link. Therefore, the fourth field may be referred to as a UHR link feedback (ULF) field. Correspondingly, the third field may be referred to as a ULF present field.

[0189] In some embodiments, the BA frame may be a compressed BA variant frame, a multi-communication identifier BA variant frame, or a multi-site BA variant frame.

[0190] Figure 10 is a schematic diagram of a compressed BA frame format provided by an embodiment of the present application. As shown in Figure 10, the BA control field includes a third field. The BA information field includes a fourth field. The fourth field includes the first field. The fourth field may include one or more of the following fields: interference, signal to noise ratio (SNR), MCS, RU allocation (RU allocation), BW, NSS, PPDU type (PPDU type), reserved. The BA information field may also include one or more of the following fields: block ACK starting sequence control (block Ack starting sequence control), block ACK bitmap (block Ack bitmap). The block ACK starting sequence control field may include one or more of the following fields: fragment number (fragment number), starting sequence number (starting sequence number).

[0191] It should be noted that the positions of the first, third, and fourth fields in FIG10 are merely examples. The positions of the first, third, and fourth fields are all variable. In addition, the presence and position of the fields within the fourth field in FIG10 are also variable.

[0192] Figure 11 is an example diagram of a multi-TID BA variant frame format provided by an embodiment of the present application. As shown in Figure 11, the BA information field includes the fourth field. The fourth field includes the first field. The BA control field includes the third field. The fourth field may include one or more of the following fields: interference, signal-to-noise ratio (SNR), multi-channel sequence count (MCS), rule allocation, bandwidth, non-stable sequence count (NSS), PPDU type, and reserved. The BA information field may also include one or more of the following fields: per-TID information (per TID info), block acknowledgement start sequence control, and block acknowledgement bitmap. The block acknowledgement start sequence control field may include one or more of the following fields: number of fragments and starting sequence number.

[0193] It should be noted that the positions of the first, third, and fourth fields in FIG11 are merely examples. The positions of the first, third, and fourth fields are all variable. In addition, the presence and position of the fields within the fourth field in FIG11 are also variable.

[0194] Figure 12 is an example diagram of a multi-STA BA variant frame format provided by an embodiment of the present application. As shown in Figure 12, the BA information field includes a fourth field. The fourth field includes the first field. The BA control field includes the third field. The fourth field may include one or more of the following fields: interference, SNR, MCS, RU allocation, BW, NSS, PPDU type, and reserved. The BA information field may also include one or more of the following fields: AID TID information (AID TID info), block acknowledgment start sequence control, and block acknowledgment bitmap. The block acknowledgment start sequence control field may include one or more of the following fields: number of fragments and starting sequence number.

[0195] It should be noted that the positions of the first, third, and fourth fields in FIG12 are merely examples. The positions of the first, third, and fourth fields are all variable. In addition, the presence and position of the fields within the fourth field in FIG12 are also variable.

[0196] In some embodiments, the first field may belong to the A-control field. It is understood that the number of bits available for A-control is relatively large. Therefore, having the first field belong to the A-control field can make the configuration of the first field more flexible.

[0197] For example, a new variant type of the A-control field may be newly defined to carry the first field. For example, the new variant type of the A-control field may be a ULA control field. The ULA control field exists in the MAC header of a data frame, a null frame, or a management frame.

[0198] Figure 13 is a schematic diagram of a ULA control field format provided by an embodiment of the present application. As shown in Figure 13, the ULA control field may include one or more of the following fields: control ID, control information.

[0199] The Control ID field can indicate the variant type of the A-control. The value of the Control ID field can be a positive integer. For example, the value of the Control ID field can be any integer between 10 and 14. For example, a value of 10 in the Control ID field can indicate the ULA control variant type.

[0200] The control information field may carry a series of parameters related to link adaptation. The control information field may include a first field.

[0201] The control information field may also include one or more of the following fields: unsolicited MCS feedback (unsolicited MCS feedback, unsolicited MFB), MRQ / uplink EHT triggered PPDU MFB (UL EHT TB PPDU MFB), NSS, UHR-MCS, RU allocation, PS160, BW, MCS request sequence indicator (MRQ sequence identifier, MSI) or partial PPDU parameters (MSI / partial PPDU parameters), and transmit beamforming. These are described below.

[0202] The unsolicited MFB field value of 1 indicates that the ELA control field is an unsolicited MFB, and the value of 0 indicates that the ELA control field is an MRQ or a solicited MFB.

[0203] For the MRQ field, when the unsolicited MFB field is set to 1, the MRQ field can indicate whether the ELA control is a request or a response. For example, a MRQ field value of 1 can indicate a request for ELA feedback. For another example, a MRQ field value of 0 can indicate a response to an ELA request.

[0204] For the MRQ field, when the unsolicited MFB field is set to 0, the MRQ field indicates the MFBs for different transmission modes. For example, a MRQ field value of 1 may indicate that the NSS, EHR-MCS, BW, PS160, and RU Allocation fields represent the recommended MFBs for the EHT TB PPDU sent by the station. For another example, a MRQ field value of 0 may indicate that the NSS, UHR-MCS, BW, PS160, and RU Allocation fields represent the recommended MFBs for the PPDU sent to the station.

[0205] The NSS field may indicate the recommended number of spatial streams.

[0206] The EHT-MCS field may indicate the recommended MCS used by the PPDU.

[0207] The PS160 field may indicate: when the size of the RU or multiple resource unit (MRU) is less than or equal to 2×996 subcarriers, the primary 160 MHz channel or secondary 160 MHz channel allocated by the RU or MRU; otherwise, the PS160 subfield together with the RU allocation subfield represents the RU or MRU index.

[0208] The RU Allocation field may be used to indicate the recommended RU or MRU.

[0209] The BW field may be used to indicate the recommended bandwidth.

[0210] For the MSI / partial PPDU parameter field, when the unsolicited MFB field value is 0, this field can indicate the sequence number of the MFB request; when the unsolicited MFB field value is 1, this field can indicate the type and coding type of the PPDU.

[0211] The Transmit Beamforming field may indicate whether the fed-back MFB is estimated based on a beamformed PPDU. For example, a value of 1 in the Transmit Beamforming field may indicate that the fed-back MFB is estimated for a beamformed PPDU. For another example, a value of 0 in the Transmit Beamforming field may indicate that the fed-back MFB is not estimated for a beamformed PPDU.

[0212] It should be noted that the existence and order of the fields contained in the control information field are variable.

[0213] The following describes the first PPDU carrying the first field.

[0214] In some embodiments, the first field may be present in a U-SIG field in the first PPDU.

[0215] Figure 14 is a format diagram of the U-SIG field in a UHR PPDU provided in an embodiment of the present application. As shown in Figure 14, the U-SIG field may include a first field. The U-SIG field may also include one or more of the following fields: PHY version identifier, bandwidth, uplink / downlink (UL / DL), BSS color, TXOP, disregard, validate, PPDU type and compression mode, punctured channel information, UHR-SIG MCS, number of UHR-SIG symbols, cyclic redundancy check (CRC), and tail.

[0216] It should be noted that the first field can be used to instruct, inform, or suggest that the first device adjust the length of the data unit to be sent. In other words, the first device can directly adjust the length of the data unit to be sent according to the instruction of the first field; or the first device can refer to the first field and determine whether and / or how to adjust the length of the data unit to be sent according to the suggestion of the first field.

[0217] It should be noted that, in response to the first device receiving the first field, when the first field indicates that the length of the data unit needs to be adjusted, the first device needs to start and / or complete the adjustment of the length of the data unit as soon as possible. In response to the first device receiving the first field, when the first field indicates that the length of the data unit does not need to be adjusted, the first device may ignore the first field.

[0218] When the first device needs to adjust the length of a data unit, the method for adjusting the length of the data unit may be implementation-dependent. For example, the first device may adjust the number of MPDUs aggregated in the A-MPDU. In another example, the first device may use the dynamic fragmentation technology described above to adjust the length of a single MPDU or MMPDU.

[0219] In some embodiments, the first device may generate non-uniformly segmented MSDUs, A-MSDUs, or MMPDUs. In the case where the first device is a HE STA, the HE STA may negotiate the use of different levels of dynamic fragmentation. For example, the levels may be Level 1, Level 2, or Level 3. Each of these levels is described below.

[0220] Level 1 supports one dynamic fragment in a non-A-MPDU; it does not support dynamic fragments in an A-MPDU that does not contain an S-MPDU.

[0221] Level 2 supports dynamic fragments in A-MPDUs that do not contain S-MPDUs, but the following conditions must be met: there is no more than one dynamic fragment for any given MSDU or A-MSDU in the A-MPDU, and the dynamic fragment is sent according to the block ACK protocol; there is no more than one dynamic fragment for any given MMPDU in the A-MPDU.

[0222] Level 3 supports dynamic fragments in an A-MPDU that does not contain an S-MPDU, provided that the following conditions are met: there are no more than four dynamic fragments in an A-MPDU for any given MSDU or A-MSDU, and these dynamic fragments are sent according to the Block ACK protocol; there are no more than one dynamic fragment in an A-MPDU.

[0223] For ease of understanding, the method provided in this application is illustrated below through Example 6.

[0224] Example 6

[0225] Example 6 proposes a corresponding technical solution for the scenario shown in FIG7 .

[0226] In Example 6, the first field is used to indicate how to adjust the PSDU length, and the first frame is a BA frame. The meaning of the first field is whether to adjust the PSDU length to 50% of the original length. The timing of using the method proposed in this application to reduce interference is shown in Figure 15.

[0227] First, AP1 sends a CTS to obtain a TXOP, thereby sending a series of data frames to STA1. STA1 immediately responds with a BA frame. Simultaneously, STA2 also sends a certain frame to STA2, which it then responds with a BA frame. Figure 15 shows that the BA frames sent by AP2 cause OBSS interference to STA1, causing transmission errors and retransmissions of the data frames with SN=1 sent by AP1. During the retransmissions, STA1 does not receive the correct data frames and therefore does not respond with BA frames. However, STA1 can detect that the continuous transmission failures are due to OBSS interference.

[0228] Subsequently, the second retransmission of the data frame with SN=1 sent by AP1 to STA1 does not receive OBSS interference and is therefore successfully transmitted. To reduce the probability of the same interference occurring during subsequent transmissions, STA1 sends the first frame (the BA* frame in Figure 15) carrying the first field to AP1. The value of the first field is 1, suggesting that AP1 shorten the PSDU length to 50% of the original length.

[0229] After receiving the first frame, AP1 adjusted the PSDU length based on the first field. As can be seen, the air interface duration of data frames with SNs 2, 3, 4, and 5 was reduced from 100us to 60us compared to data frames with SNs 0 and 1 (the length of the PPDU preamble was not adjusted), thereby reducing the probability of interference. As a result, AP1 successfully transmitted data frames with SNs 2, 3, and 4, until it transmitted a data frame with SN 5, which overlapped with the BA frame sent by AP2 and caused interference. This significantly reduced the probability of transmission failure compared to before the PSDU length adjustment.

[0230] In the scenario shown in Figure 15, the probability that the data frame sent by AP1 to STA1 is subject to OBSS interference depends on the air interface duration of the data frame sent by AP1 and the duration of the interval when AP2 does not send frames. In Figure 15, the OBSS interference probability can be:

[0231] Before the PSDU length is adjusted, the OBSS interference probability = 100 us / (150 us+2*16 us) = 55%.

[0232] After PSDU length adjustment, OBSS interference probability = 60 us / (150 us+2*16 us) us = 33%.

[0233] As can be seen, the OBSS interference probability after PSDU length adjustment is reduced from 55% to 33%. Therefore, the proposed first field can effectively adjust the PSDU length, thereby effectively reducing the probability of OBSS interference, thereby reducing the packet loss rate and improving link reliability.

[0234] Related technologies convey specific information about interference or interfering signals, which can be unclear or require significant bit overhead. This solution, however, conveys information related to adjusting the PSDU or PPDU length. This requires fewer bits and accurately indicates how to adjust the length, thereby reducing the probability of interference.

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

[0236] FIG16 is a schematic structural diagram of a communication device 1600 provided in an embodiment of the present application. The communication device 1600 may include a receiving unit 1610 .

[0237] The receiving unit 1610 is configured to receive a first field, wherein the first field is configured to instruct the first device to adjust the length of the data unit to be sent.

[0238] In some embodiments, the data unit includes one or more of the following: PSDU, PPDU.

[0239] In some embodiments, the first field is used to indicate one or more of the following information: whether to adjust the length of the data unit;

[0240] The first length of the data unit after adjustment.

[0241] In some embodiments, the first length is a maximum length of the data unit.

[0242] In some embodiments, the first length is determined by a first value and a second value of the first field, and the second value satisfies one or more of the following: the second value is determined based on the value of the second field; the second value is determined based on the value of a static physical layer characteristic parameter; the second value is determined based on the length of a data unit historically sent by the first device.

[0243] In some embodiments, the value of the first field is A, the second value is B, and the first length C satisfies:

[0244] In some embodiments, the second field is located in a capability element.

[0245] In some embodiments, the second field comprises a maximum aggregate medium access control protocol data unit length index field.

[0246] In some embodiments, the capability element comprises a capability element of a first type, and the first length is a length of a data unit of the first type.

[0247] In some embodiments, the first type includes one or more of the following: UHR, EHT, HE, VHT, HT.

[0248] In some embodiments, the static physical layer characteristic parameter is used to indicate the length of the maximum receiving and / or sending data unit that the physical layer can support.

[0249] In some embodiments, the static physical layer characteristic parameters include: aPSDUMaxLength and / or aPPDUMaxTime.

[0250] In some embodiments, the value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

[0251] In some embodiments, the first field belongs to a first frame, and the first frame includes one or more of the following: a BA frame, a data frame, a null frame, and a management frame.

[0252] In some embodiments, the first field belongs to a BA control field.

[0253] In some embodiments, the first field belongs to a BA information field.

[0254] In some embodiments, the BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field is present in the BA information field.

[0255] In some embodiments, the BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame, or a multi-site BA variant frame.

[0256] In some embodiments, the first field belongs to an A-control field.

[0257] In some embodiments, the first field belongs to a first PPDU.

[0258] In some embodiments, the first field is used to instruct the first device to adjust the length of the data unit to be sent, including: the first field is used to suggest the first device to adjust the length of the data unit to be sent.

[0259] In an optional embodiment, the receiving unit 1610 may be a transceiver 1830. The communication device 1600 may further include a processor 1810 and a memory 1820, as specifically shown in FIG18 .

[0260] FIG17 is a schematic structural diagram of a communication device 1700 provided in an embodiment of the present application. The communication device 1700 may include a sending unit 1710 .

[0261] The sending unit 1710 is used to send a first field to a first device; wherein the first field is used to instruct the first device to adjust the length of the data unit to be sent.

[0262] In some embodiments, the data unit includes one or more of the following: PSDU, PPDU.

[0263] In some embodiments, the first field is used to indicate one or more of the following information: whether to adjust the length of the data unit; and the first length of the data unit after adjustment.

[0264] In some embodiments, the first length is a maximum length of the data unit.

[0265] In some embodiments, the first length is determined by a first value and a second value of the first field, and the second value satisfies one or more of the following: the second value is determined based on the value of the second field; the second value is determined based on the value of a static physical layer characteristic parameter; the second value is determined based on the length of a data unit historically sent by the first device.

[0266] In some embodiments, the value of the first field is A, the second value is B, and the first length C satisfies:

[0267] In some embodiments, the second field is located in a capability element.

[0268] In some embodiments, the second field comprises a maximum aggregate medium access control protocol data unit length index field.

[0269] In some embodiments, the capability element comprises a capability element of a first type, and the first length is a length of a data unit of the first type.

[0270] In some embodiments, the first type includes one or more of the following: UHR, EHT, HE, VHT, HT.

[0271] In some embodiments, the static physical layer characteristic parameter is used to indicate the length of the maximum receiving and / or sending data unit that the physical layer can support.

[0272] In some embodiments, the static physical layer characteristic parameters include: aPSDUMaxLength and / or aPPDUMaxTime.

[0273] In some embodiments, the value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

[0274] In some embodiments, the first field belongs to a first frame, and the first frame includes one or more of the following: a block acknowledgement BA frame, a data frame, a null frame, and a management frame.

[0275] In some embodiments, the first field belongs to a BA control field.

[0276] In some embodiments, the first field belongs to a BA information field.

[0277] In some embodiments, the BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field is present in the BA information field.

[0278] In some embodiments, the BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame, or a multi-site BA variant frame.

[0279] In some embodiments, the first field belongs to an A-control field.

[0280] In some embodiments, the first field belongs to a first PPDU.

[0281] In some embodiments, the first field is used to instruct the first device to adjust the length of the data unit to be sent, including: the first field is used to suggest the first device to adjust the length of the data unit to be sent.

[0282] In an optional embodiment, the sending unit 1710 may be a transceiver 1830. The communication device 1700 may further include a processor 1810 and a memory 1820, as specifically shown in FIG18 .

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

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

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

[0286] The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips via the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips via the transceiver 1830.

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

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

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

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

[0291] In the embodiments of the present application, a "field" may also be referred to as a "field," a "subfield," or a "subfield." A field may occupy one or more bytes (byte / octet), or a field may occupy one or more bits (bit).

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A wireless communication method, characterized in that: include: The first device receives the first field; The first field is used to instruct the first device to adjust the length of the sent data unit.

2. The method according to claim 1, characterized in that The data unit includes one or more of the following: a physical layer service data unit PSDU and a physical layer protocol data unit PPDU.

3. The method according to claim 1 or 2, characterized in that: The first field is used to indicate one or more of the following information: whether to adjust the length of the data unit; The first length of the data unit is adjusted.

4. The method according to claim 3, characterized in that: The first length is the maximum length of the data unit.

5. The method according to any one of claims 3 or 4, characterized in that The first length is determined by a first value and a second value of the first field, where the second value satisfies one or more of the following: The second value is determined based on the value of the second field; The second value is determined based on the value of the static physical layer characteristic parameter; The second value is determined based on the length of a data unit historically sent by the first device.

6. The method according to claim 5, characterized in that The value of the first field is A, the second value is B, and the first length C satisfies:

7. The method according to claim 5 or 6, characterized in that: The second field is located in the capability element.

8. The method according to claim 7, characterized in that The second field includes a maximum aggregate medium access control protocol data unit length index field.

9. The method according to claim 7 or 8, characterized in that: The capability element includes a first type of capability element, and the first length is a length of a data unit of the first type.

10. The method according to claim 9, characterized in that The first type includes one or more of the following: ultra-high reliability UHR, extremely high throughput EHT, high efficiency HE, very high throughput VHT, and high throughput HT.

11. The method according to claim 5 or 6, characterized in that: The static physical layer characteristic parameter is used to indicate the maximum length of the receiving and / or sending data unit that the physical layer can support.

12. The method according to claim 11, characterized in that The static physical layer characteristic parameters include: aPSDU maximum length aPSDUMaxLength and / or aPPDU maximum duration aPPDUMaxTime.

13. The method according to claim 3 or 4, characterized in that: The value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

14. The method according to any one of claims 1 to 13, characterized in that The first field belongs to a first frame, and the first frame includes one or more of the following: a block confirmation BA frame, a data frame, an empty frame, and a management frame.

15. The method according to claim 14, characterized in that The first field belongs to the BA control field.

16. The method according to claim 14 or 15, characterized in that The first field belongs to the BA information field.

17. The method according to claim 16, characterized in that The BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field exists in the BA information field.

18. The method according to any one of claims 14 to 17, characterized in that: The BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame or a multi-site BA variant frame.

19. The method according to claim 14, characterized in that The first field belongs to the A-control field.

20. The method according to any one of claims 1 to 13, characterized in that The first field belongs to a first PPDU.

21. The method according to any one of claims 1 to 20, characterized in that The first field is used to instruct the first device to adjust the length of the sent data unit, including: The first field is used to suggest that the first device adjust the length of the sent data unit.

22. A wireless communication method, characterized in that: include: The second device sends a first field to the first device; The first field is used to instruct the first device to adjust the length of the sent data unit.

23. The method according to claim 22, characterized in that The data unit includes one or more of the following: a physical layer service data unit PSDU and a physical layer protocol data unit PPDU.

24. The method according to claim 22 or 23, characterized in that The first field is used to indicate one or more of the following information: whether to adjust the length of the data unit; The first length of the data unit is adjusted.

25. The method according to claim 24, characterized in that The first length is the maximum length of the data unit.

26. The method according to any one of claims 24 or 25, characterized in that The first length is determined by a first value and a second value of the first field, where the second value satisfies one or more of the following: The second value is determined based on the value of the second field; The second value is determined based on the value of the static physical layer characteristic parameter; The second value is determined based on the length of a data unit historically sent by the first device.

27. The method according to claim 26, characterized in that The value of the first field is A, the second value is B, and the first length C satisfies:

28. The method according to claim 26 or 27, characterized in that The second field is located in the capability element.

29. The method according to claim 28, characterized in that The second field includes a maximum aggregate medium access control protocol data unit length index field.

30. The method according to claim 28 or 29, characterized in that The capability element includes a first type of capability element, and the first length is a length of a data unit of the first type.

31. The method according to claim 30, characterized in that The first type includes one or more of the following: ultra-high reliability UHR, extremely high throughput EHT, high efficiency HE, very high throughput VHT, and high throughput HT.

32. The method according to claim 26 or 27, characterized in that The static physical layer characteristic parameter is used to indicate the maximum length of the receiving and / or sending data unit that the physical layer can support.

33. The method according to claim 32, characterized in that The static physical layer characteristic parameters include: aPSDU maximum length aPSDUMaxLength and / or aPPDU maximum duration aPPDUMaxTime.

34. The method according to claim 24 or 25, characterized in that The value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

35. The method according to any one of claims 22 to 34, characterized in that The first field belongs to a first frame, and the first frame includes one or more of the following: a block confirmation BA frame, a data frame, an empty frame, and a management frame.

36. The method according to claim 35, characterized in that The first field belongs to the BA control field.

37. The method according to claim 35 or 36, characterized in that The first field belongs to the BA information field.

38. The method according to claim 37, characterized in that The BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field exists in the BA information field.

39. The method according to any one of claims 35 to 38, characterized in that The BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame or a multi-site BA variant frame.

40. The method according to claim 35, characterized in that The first field belongs to the A-control field.

41. The method according to any one of claims 22 to 34, characterized in that The first field belongs to a first PPDU.

42. The method according to any one of claims 22 to 41, characterized in that The first field is used to instruct the first device to adjust the length of the sent data unit, including: The first field is used to suggest that the first device adjust the length of the sent data unit.

43. A communication device, characterized in that: The communication device is a first device, and the communication device includes: A receiving unit, configured to receive a first field; The first field is used to instruct the first device to adjust the length of the sent data unit.

44. The device according to claim 43, characterized in that The data unit includes one or more of the following: a physical layer service data unit PSDU and a physical layer protocol data unit PPDU.

45. Apparatus according to claim 43 or 44, characterised in that The first field is used to indicate one or more of the following information: whether to adjust the length of the data unit; The first length of the data unit is adjusted.

46. ​​The device according to claim 45, characterized in that The first length is the maximum length of the data unit.

47. Apparatus according to any one of claims 45 or 46, characterised in that The first length is determined by a first value and a second value of the first field, where the second value satisfies one or more of the following: The second value is determined based on the value of the second field; The second value is determined based on the value of the static physical layer characteristic parameter; The second value is determined based on the length of a data unit historically sent by the first device.

48. The device according to claim 47, characterized in that The value of the first field is A, the second value is B, and the first length C satisfies:

49. Apparatus according to claim 47 or 48, characterised in that The second field is located in the capability element.

50. The apparatus according to claim 48, characterized in that The second field includes a maximum aggregate medium access control protocol data unit length index field.

51. The apparatus according to claim 48 or 50, characterized in that The capability element includes a first type of capability element, and the first length is a length of a data unit of the first type.

52. The device according to claim 51, characterized in that The first type includes one or more of the following: ultra-high reliability UHR, extremely high throughput EHT, high efficiency HE, very high throughput VHT, and high throughput HT.

53. The apparatus according to claim 47 or 48, characterized in that The static physical layer characteristic parameter is used to indicate the maximum length of the receiving and / or sending data unit that the physical layer can support.

54. The device according to claim 53, characterized in that The static physical layer characteristic parameters include: aPSDU maximum length aPSDUMaxLength and / or aPPDU maximum duration aPPDUMaxTime.

55. The apparatus according to claim 45 or 46, characterized in that The value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

56. The apparatus according to any one of claims 43 to 55, characterized in that The first field belongs to a first frame, and the first frame includes one or more of the following: a block confirmation BA frame, a data frame, an empty frame, and a management frame.

57. The device according to claim 56, characterized in that The first field belongs to the BA control field.

58. The apparatus according to claim 56 or 57, characterized in that The first field belongs to the BA information field.

59. The device according to claim 58, characterized in that The BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field exists in the BA information field.

60. The apparatus according to any one of claims 56 to 59, characterized in that The BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame or a multi-site BA variant frame.

61. The apparatus according to claim 56, characterized in that The first field belongs to the A-control field.

62. The apparatus according to any one of claims 43 to 55, characterized in that The first field belongs to a first PPDU.

63. The apparatus according to any one of claims 43 to 62, characterized in that The first field is used to instruct the first device to adjust the length of the sent data unit, including: The first field is used to suggest that the first device adjust the length of the sent data unit.

64. A communication device, characterized in that: The communication device is a second device, and the communication device includes: A sending unit, configured to send a first field to a first device; The first field is used to instruct the first device to adjust the length of the sent data unit.

65. The device according to claim 64, characterized in that The data unit includes one or more of the following: a physical layer service data unit PSDU and a physical layer protocol data unit PPDU.

66. Apparatus according to claim 64 or 65, characterised in that The first field is used to indicate one or more of the following information: whether to adjust the length of the data unit; The first length of the data unit is adjusted.

67. The device according to claim 66, characterized in that The first length is the maximum length of the data unit.

68. Apparatus according to any one of claims 66 or 67, characterised in that The first length is determined by a first value and a second value of the first field, where the second value satisfies one or more of the following: The second value is determined based on the value of the second field; The second value is determined based on the value of the static physical layer characteristic parameter; The second value is determined based on the length of a data unit historically sent by the first device.

69. The device according to claim 68, characterized in that The value of the first field is A, the second value is B, and the first length C satisfies:

70. The apparatus according to claim 68 or 69, characterized in that The second field is located in the capability element.

71. The device according to claim 70, characterized in that The second field includes a maximum aggregate medium access control protocol data unit length index field.

72. The device according to claim 70 or 71, characterized in that The capability element includes a first type of capability element, and the first length is a length of a data unit of the first type.

73. The device according to claim 72, characterized in that The first type includes one or more of the following: ultra-high reliability UHR, extremely high throughput EHT, high efficiency HE, very high throughput VHT, and high throughput HT.

74. The apparatus according to claim 68 or 69, characterized in that The static physical layer characteristic parameter is used to indicate the maximum length of the receiving and / or sending data unit that the physical layer can support.

75. The device according to claim 74, characterized in that The static physical layer characteristic parameters include: aPSDU maximum length aPSDUMaxLength and / or aPPDU maximum duration aPPDUMaxTime.

76. The apparatus of claim 66 or 67, wherein: The value of the first field is A, and the first length C satisfies: C=A; or, C=2 (13+A) -1.

77. The apparatus according to any one of claims 64 to 76, characterized in that The first field belongs to a first frame, and the first frame includes one or more of the following: a block confirmation BA frame, a data frame, an empty frame, and a management frame.

78. The device according to claim 77, characterized in that The first field belongs to the BA control field.

79. The apparatus according to claim 77 or 78, characterized in that The first field belongs to the BA information field.

80. The apparatus according to claim 79, characterized in that The BA control field in the BA frame includes a third field, and the third field is used to indicate whether the first field exists in the BA information field.

81. The apparatus according to any one of claims 77 to 80, characterized in that The BA frame is a compressed BA variant frame, a multi-communication identifier BA variant frame or a multi-site BA variant frame.

82. The apparatus of claim 77, wherein: The first field belongs to the A-control field.

83. The apparatus according to any one of claims 64 to 76, characterized in that The first field belongs to a first PPDU.

84. The apparatus according to any one of claims 64 to 83, characterized in that The first field is used to instruct the first device to adjust the length of the sent data unit, including: The first field is used to suggest that the first device adjust the length of the sent data unit.

85. A communication device, characterized in that: The device comprises 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 as claimed in any one of claims 1 to 42.

86. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to cause the device to execute a method as claimed in any one of claims 1 to 42.

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

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

89. A computer program product, characterized in that A program is included, which causes a computer to execute the method according to any one of claims 1 to 42.

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

Images