Wireless communication methods and communication devices

Abstract

Provided are wireless communication methods and communication devices. A method comprises: a first device sends a first frame to a second device, the first frame comprising one or more of the following: first information, used for indicating whether to allow out-of-order transmission of data units in a first service flow; second information, used for indicating QoS features of the first service flow allowing out-of-order transmission and / or out-of-order transmission parameters allowed by the first service flow; third information, used for indicating a first TID and / or first user priority corresponding to the data units in the first service flow; and fourth information, used for indicating a transmission direction of the first service flow.

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] To solve the head-of-line blocking problem caused by in-order transmission, related technologies have introduced out-of-order transmission solutions. However, there is currently no suitable solution for how the communicating parties should perform out-of-order transmission.

[0003] Summary of the Invention

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

[0005] In a first aspect, a wireless communication method is provided, including: a first device sends a first frame to a second device, the first frame including one or more of the following: first information for indicating whether out-of-order transmission of data units in a first service flow is allowed; second information for indicating the quality of service (QoS) characteristics of the first service flow for which out-of-order transmission is allowed and / or out-of-order transmission parameters allowed by the first service flow; third information for indicating a first traffic identifier (TID) and / or a first user priority corresponding to the data unit in the first service flow; and fourth information for indicating the transmission direction of the first service flow.

[0006] In a second aspect, a wireless communication method is provided, including: a second device receives a first frame sent by a first device, where the first frame includes one or more of the following: first information for indicating whether out-of-order transmission of data units in a first service flow is allowed; second information for indicating the QoS characteristics of the first service flow for which out-of-order transmission is allowed and / or out-of-order transmission parameters allowed by the first service flow; third information for indicating a first TID and / or a first user priority corresponding to the data unit in the first service flow; and fourth information for indicating a transmission direction of the first service flow.

[0007] According to a third aspect, a communication device is provided, wherein the communication device is a first device, and the communication device includes: a first communication module, used to send a first frame to a second device, the first frame including one or more of the following: first information, used to indicate whether data units in a first service flow are allowed to be transmitted out of order; second information, used to indicate the QoS characteristics of the first service flow for which out of order transmission is allowed and / or the out of order transmission parameters allowed by the first service flow; third information, used to indicate a first TID and / or a first user priority corresponding to the data unit in the first service flow; and fourth information, used to indicate the transmission direction of the first service flow.

[0008] In a fourth aspect, a communication device is provided, which is a second device, and the communication device includes: a first communication module, used to receive a first frame sent by the first device, the first frame including one or more of the following: first information, used to indicate whether data units in a first service flow are allowed to be transmitted out of order; second information, used to indicate the QoS characteristics of the first service flow that allows out of order transmission and / or the out of order transmission parameters allowed by the first service flow; third information, used to indicate the first TID and / or first user priority corresponding to the data unit in the first service flow; fourth information, used to indicate the transmission direction of the first service flow.

[0009] In a fifth aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the method of the first aspect and / or the second aspect.

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

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

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

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

[0014] The embodiments of the present application define out-of-order transmission related information, which can indicate whether out-of-order transmission is allowed and / or out-of-order transmission parameters. The introduction of out-of-order transmission related information helps both communicating parties to clarify the out-of-order transmission mode, thereby ensuring the effective application of out-of-order transmission in practice. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] FIG2 is an example diagram of an out-of-order transmission mode.

[0017] FIG3 is another example diagram of an out-of-order transmission mode.

[0018] FIG4 is a schematic diagram of the format of the extended QoS feature element field provided in an embodiment of the present application.

[0019] FIG5 is a schematic diagram showing the format of the control information field in FIG4 .

[0020] FIG6 is a schematic diagram of the format of the stream classification service (SCS) descriptor element field provided in an embodiment of the present application.

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

[0022] FIG8 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application.

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

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

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

[0026] Communication System

[0027] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi) or other communication systems.

[0028] 1 is a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include an access point 110 and a station (STA) 120 accessing a network through the access point (AP) 110.

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

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

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

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

[0033] It should be understood that the roles of various communication devices in the communication system 100 are not absolute. Taking a mobile phone as an example, when the mobile phone is connected to a router, the mobile phone is a STA; when the mobile phone serves as a hotspot for other mobile phones, the mobile phone plays the role of an AP.

[0034] APs and STAs can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0035] In some embodiments, both the STA and the AP may support the 802.11be standard. The STA or AP may also support various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0036] There are one or more links between the STA and the AP. In some embodiments, the STA and the AP support multi-band communication. For example, the STA and the AP can communicate simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz frequency bands, or communicate simultaneously on different channels in the same frequency band (or different frequency bands) to improve the communication throughput and / or reliability between devices. Such a device is generally referred to as a multi-band device, or a multi-link device (MLD), sometimes also referred to as a multi-link entity or a multi-band entity. The multi-link device can be an access point device or a site device. If the multi-link device is an access point device, the multi-link device can include one or more APs; if the multi-link device is a site device, the multi-link device can include one or more non-AP STAs.

[0037] A multi-link device including one or more APs may be referred to as an access point multi-link device (AP MLD), and a multi-link device including one or more non-AP STAs may be referred to as a non-AP multi-link device (non-AP MLD).

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

[0039] In an embodiment of the present application, a STA may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. that supports WLAN / WiFi technology.

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

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

[0042] It should be understood that in the embodiments of the present application, a device with communication functionality in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include an AP 110 and a STA 120 with communication functionality. In addition, the communication device mentioned in the embodiments of the present application may also include other devices in the communication system 100, such as a network controller, a gateway, and other network entities (not shown in FIG1 ), which is not limited in the embodiments of the present application.

[0043] APs and STAs can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which APs and STAs are located.

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

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

[0046] SCS Process

[0047] In the SCS process, the non-AP MLD can send an SCS request frame to the AP MLD, requesting the AP MLD to classify the incoming individually addressed medium access control (MAC) service data unit (MSDU) according to the parameters provided by the non-AP MLD and / or describe its flow characteristics to the AP MLD.

[0048] If the Request Type field in the SCS Request frame is set to "Add" or "Change", the SCS Request frame may include an SCS Descriptor element, and the SCS Descriptor element may include a QoS Characteristics element. The QoS Characteristics element may be used to describe the traffic characteristics of the SCS flow requested by the SCS Request frame.

[0049] MLD maintains an SCS identifier (SCSID) for each non-AP MLD at the MLD level. That is, the SCSID used by a non-AP STA affiliated with a non-AP MLD in an SCS request frame sent to an AP affiliated with an AP MLD is unique among all STAs affiliated with the non-AP MLD. The SCSID is used by the non-AP MLD to request the creation, modification, or deletion of an SCS stream. The SCSID is used by the AP MLD to identify the SCS stream.

[0050] If the SCS descriptor element contains a QoS Features element and the Direction field in the QoS Features element indicates downlink, the CS descriptor element shall contain a Traffic Classification (TCLAS) Element field and may contain a TCLAS Processing Element field. If the SCS descriptor element field contains the TCLAS Element field and the TCLAS Processing Element field, the above fields describe the traffic classification that the non-AP STA requests the AP to apply to the corresponding flow.

[0051] In-order transmission mechanism provided by Wi-Fi MAC

[0052] Wi-Fi's MAC data service provides peer logical link control (LLC) sublayer entities or Institute of Electrical and Electronics Engineers (IEEE) 802.1Q bridge ports with the ability to exchange MSDUs. To support this service, the local MAC uses the underlying physical layer services to transmit MSDUs to the peer MAC entity, and the peer MAC entity transmits the MSDUs to the peer LLC sublayer or IEEE 802.1Q bridge port. This asynchronous MSDU transmission is performed on a connectionless basis. By default, the transmission of MSDUs is on a best-effort basis. However, QoS facilities use traffic identifiers (TIDs) to specify different services on a per-MSDU basis.

[0053] A STA can maintain one or more sequence number (SN) spaces to determine the sequence number of a frame when transmitting it. When multiple sequence number spaces are supported, the appropriate sequence number space is determined by the information in the MAC Control field of the frame to be transmitted. For each MSDU, aggregate MSDU (A-MSDU), or MAC management PDU (MMPDU) transmitted based on the SN space, the SN space can be represented by an SN counter, and the value of the counter starts at 0 and increments by 1.

[0054] The MLD can maintain one or more SN spaces. The SN space can contain one or more counters. MPDUs belonging to the same MSDU or A-MSDU should have the same SN. Different MSDUs, A-MSDUs, or MMPDUs (most likely) have different SNs.

[0055] Robust Security Network Association (RSNA) confidentiality and integrity protocol

[0056] The Wi-Fi standard defines the following RSNA confidentiality and integrity protocols: Counter Mode (CTR) with cipher-block chaining message authentication code (CBC-MAC) protocol (CTR with CBC-MAC protocol, CCMP) and Galois / counter mode protocol (GCMP).

[0057] CCMP provides data confidentiality, authentication, integrity, and replay protection. CCMP is a CCM based on the Advanced Encryption Standard (AES) encryption algorithm. CCM combines CTR for data confidentiality and CBC-MAC for authentication and integrity. CCM protects the integrity of the MPDU data field and selected parts of the IEEE 802.11 MPDU header. CCM is a generic mode that can be used with any block-oriented encryption algorithm. CCM requires a new temporary key for each session. CCM also requires that each frame protected by a given temporary key have a unique nonce value. Reusing a nonce value with the same temporary key invalidates all security guarantees.

[0058] For secure protocol version 0 (PV0) MPDUs, CCMP encrypts the body of the plaintext MPDU and encapsulates it into ciphertext. Each MPDU is assigned a new non-zero packet number (PN) by incrementing it, ensuring that PNs are not repeated for the same temporary key.

[0059] Number each MPDU in sequence to obtain the PN value corresponding to each MPDU. Each sender STA not affiliated with the MLD should maintain a single PN (48-bit counter) for each pairwise transient key security association (PTKSA) and group temporal key security association (GTKSA). Each sender STA affiliated with the MLD should use the PN (48-bit counter) maintained by the MLD for the PTKSA, or the PN maintained by the STA for the GTKSA. The PN should be implemented as a 48-bit strictly increasing integer, initialized to 0 when the corresponding transient key is initialized or refreshed (through key update).

[0060] The PN value of each MPDU increases by a positive number. For MPDUs consisting of fragmented MSDUs, A-MSDUs, and MMPDUs, the PN shall be incremented by 1. For P-V0 MPDUs, the PN of a series of encrypted MPDUs using the same temporary key will not repeat. For protocol version 1 (PV1) MPDUs, the PN of a series of encrypted MPDUs using the same temporary key and partial stream identifier (PTID) will not repeat.

[0061] When the PN space is exhausted (i.e., the PN exceeds the PN exhaustion minimum threshold or the PN exhaustion maximum threshold), the corresponding key can be replaced or the communication can be terminated. If individually addressed MPDUs are sent by the MLD to the receiving MLD through the attached STAs, a single PN space should be reserved for the PTKSA for transmission through all attached STAs.

[0062] The receiver shall discard any received data frame with a PN less than or equal to the target value (the value of the replay counter associated with the transmitter address (TA), receiver address (RA), and priority value of the received MPDU). If the MPDU is an individually addressed data frame transmitted between an AP MLD and a non-AP MLD associated with the AP MLD through an affiliated STA, the receiver shall discard any received data frame with a PN less than or equal to the target value (the value of the replay counter associated with the transmitter MLD MAC address, the receiver MLD MAC address (individual or group address), and the priority value of the received MPDU).

[0063] For individually addressed MPDUs received by dependent STAs from the transmitting MLD, the receiving MLD shall maintain a set of replay counters for the PTKSA for all dependent STAs.

[0064] Out-of-order delivery scheme

[0065] Intel's UHR proposal, IEEE 802.11-23 / 697r0, addresses the Wi-Fi head-of-line blocking issue and proposes allowing the MAC-service access point (SAP) to optionally transmit packets out of order for specific TIDs. The number of specific TIDs may be limited to one or two, and these specific TIDs may be used only during flow establishment that can benefit from out-of-order delivery (e.g., following appropriate SCS negotiation). Furthermore, the PN space used for frames requiring out-of-order delivery is differentiated from that for frames requiring in-order delivery. Figure 2 illustrates an example of the out-of-order delivery process. As shown in Figure 2, although the receiver initially fails to successfully receive an MPDU with an SN of 11 and a PN of 51, it still passes the received MPDU (e.g., an MPDU with a PN of 50 or 113) to the next MAC process for replay detection. Then, after receiving an MPDU with a PN of 51, it passes it along with the subsequently received MPDUs to the next MAC process.

[0066] In its UHR proposal, IEEE 802.11-23 / 0799r0, MediaTek proposed a separate PN sequence and replay counter for low-latency packets. This allows for earlier processing of low-latency packets while still supporting replay detection for other packets within the same TID. As shown in Figure 3, flows A and B use different PN sequences and replay counters. Although MPDU0 is not successfully received, the STA can still transmit MPDU2 and MPDU3 to the upper layer.

[0067] The WiFi MAC's restriction on in-order transmission of data units can lead to head-of-line blocking. This means that if there are holes in the reordering buffer (i.e., packets with earlier sequence numbers that have not been received), the packets stored in the reordering buffer will not be forwarded. The sender must first send packets with lower sequence numbers before sending packets with higher sequence numbers. Consequently, packets requiring low latency cannot be transmitted quickly due to head-of-line blocking, resulting in packet transmission failing to meet QoS requirements.

[0068] Therefore, the head-of-line blocking problem can be solved by introducing an out-of-order transmission mechanism in specific scenarios (such as scenarios where multiple business flows are mapped to one TID, or scenarios where Layer 2 and Layer 3 protocols coordinate to handle low-latency flow transmission). However, there is currently no suitable solution for how to perform out-of-order transmission. For example, to ensure that the out-of-order transmission mechanism is effectively applied to the transmission of low-latency flows, the data sender and receiver corresponding to the business flow need to determine in advance whether to adopt the out-of-order transmission mechanism and / or related out-of-order transmission parameters. The solutions proposed by IEEE 802.11-23 / 697r0 and IEEE802.11-23 / 0799r0 do not involve how the data sender and receiver negotiate to determine whether to adopt the out-of-order transmission mechanism and / or related out-of-order transmission parameters.

[0069] To address the above issues, embodiments of the present application define information related to out-of-order transmission. This information can be used to negotiate (or request) whether to adopt out-of-order transmission and / or related out-of-order transmission parameters. The introduction of information related to out-of-order transmission helps both communicating parties clarify the out-of-order transmission method, thereby ensuring the effective application of out-of-order transmission in practice.

[0070] The following is a detailed description of the related information about out-of-order transmission.

[0071] First information: used to indicate whether out-of-order transmission of data units in the first service flow is allowed

[0072] It should be noted that, unless there is a conflict, the service flows, data flows, and QoS flows mentioned in the embodiments of this application can be used interchangeably. In some implementations, the service flows mentioned in the embodiments of this application can refer to SCS flows. The service flows mentioned in the embodiments of this application can refer to service flows in a specific transmission direction. For example, the service flows mentioned in the embodiments of this application can refer to service flows in the uplink direction, service flows in the downlink direction, or service flows on a direct link.

[0073] It should also be noted that the data unit mentioned in the embodiments of the present application may refer to a combination of one or more of a data frame, MSDU, A-MSDU or MPDU, etc.

[0074] The first information is used to indicate whether out-of-order transmission of data units in the first service flow is permitted. The out-of-order transmission mentioned here may refer to a possible difference between the time sequence in which the transmitting end sends data units in the MAC SAP and the time sequence in which the receiving end receives data units in the MAC SAP. For example, if the transmitting end sends data unit 0 and data unit 1 sequentially in the MAC SAP, and the receiving end receives data unit 1 and data unit 0 sequentially in the MAC SAP, the transmission of data unit 0 and data unit 1 can be considered out-of-order transmission because the receiving end first receives data unit 1, which has a later transmission order.

[0075] The first information may have one or more values. For example, if the value of the first information is a first value (e.g., 0), it indicates that out-of-order transmission of data units in the first service flow is not permitted. For another example, if the value of the first information is a second value (e.g., 1), it indicates that out-of-order transmission of data units in the first service flow is permitted.

[0076] Second information: used to indicate the QoS characteristics of the first service flow that allows out-of-order transmission and / or the out-of-order transmission parameters allowed by the first service flow

[0077] In some implementations, the second information indicates a flow characteristic, a QoS characteristic, or a QoS expectation of the first service flow that allows out-of-order transmission.

[0078] In some implementations, the second information indicates an out-of-order transmission parameter and / or an out-of-order degree allowed for the first service flow.

[0079] The second information may be related to a "hole" generated when the first business flow is transmitted out of order. In the case where the receiving end has received a data unit with a later sending order, the data unit with an earlier sending order that the receiving end has not received forms a hole. The hole is caused by the existence of out-of-order transmission. Therefore, the hole mentioned in the embodiment of the present application can also be called an out-of-order hole. The hole in the first business flow may correspond to the "target data unit" in the first business flow. The target data unit mentioned here is a data unit or multiple consecutive data units that the receiving end of the first business flow expects to receive but has not received (the continuous mentioned here refers to continuous in sending order or sending time), and the sending order of the target data unit (at the sending end of the first business flow) is before the received data unit in the first business flow. In other words, when the receiving end receives one or more data units, a data unit (such as an MSDU or A-MSDU) that the receiving end expected to receive but did not receive and that was sent before the received data unit is called a hole. Alternatively, multiple consecutive data units that the receiving end expected to receive but did not receive and that were sent before the received data unit are called a hole (the consecutive mentioned here refers to the consecutive sending order or sending time).

[0080] In some implementations, the second information may be related to the size (or size) of a hole in the first service flow. As mentioned above, a hole corresponds to a target data unit in the first service flow. The size of a hole may refer to the number of data units contained in the target data unit. For example, if the target data unit corresponding to a hole includes only one data unit, the size of the hole may be 1. For another example, if the target data unit corresponding to a hole includes N consecutive data units, the size of the hole may be N. Exemplarily, for a hole, assuming that the earliest data unit among the data units currently expected to be received but not received is MSDU-n, and assuming that the data unit among the currently received data units whose transmission time is not earlier than MSDU-n and is closest to MSDU-n in terms of transmission order is MSDU-m, the size of a hole may be determined based on the number of unreceived data units between MSDU-n and MSDU-m (MSDU-n needs to be included in the calculation of the number of unreceived data units between MSDU-n and MSDU-m). Among them, when the SN corresponding to the data unit is continuously increased by 1 in the sending order, if the SN of MSDU-n is SN(n) and the SN of MSDU-m is SN(m), the size of the hole is SN(m)-SN(n).

[0081] For example, the second information may be used to indicate the maximum size of a hole allowed. That is, the second information indicates the maximum size of a hole allowed to appear in the first service flow. The maximum size of a hole may be represented by an unsigned integer.

[0082] In some implementations, the second information may be related to the number of holes allowed within the first time period. The first time period mentioned here can be set according to actual needs. For example, the first time period can be a given service period (SP), a given time window, or a duration.

[0083] For example, the second information indicates the maximum number of holes allowed in the first time period. That is, the second information indicates the maximum number of holes allowed in the first service flow in the first time period. The maximum number of holes allowed in the first time period can be represented by an unsigned integer.

[0084] In some implementations, the second information may be related to the interval between two adjacent holes (or two consecutive holes) (i.e., the number of data units included between the two adjacent holes). Assuming that the two adjacent holes include a first hole and a second hole, the interval between the two adjacent holes may be determined based on the number of data units between the earliest corresponding data unit in the first hole (i.e., the data unit with the highest transmission order among the data units expected to be received but not received in the first hole) and the earliest corresponding data unit in the second hole (i.e., the data unit with the highest transmission order among the data units expected to be received but not received in the second hole). Of course, the interval between two adjacent holes may also be determined based on the number of data units between the latest corresponding data unit in the first hole (i.e., the data unit with the highest transmission order among the data units expected to be received but not received in the first hole) and the earliest corresponding data unit in the second hole (i.e., the data unit with the highest transmission order among the data units expected to be received but not received in the second hole). Alternatively, the interval between two adjacent holes can also be determined based on the number of data units between the corresponding latest data unit in the first hole (i.e., the data unit with the latest sending order among the data units expected to be received but not received in the first hole) and the corresponding latest data unit in the second hole (i.e., the data unit with the latest sending order among the data units expected to be received but not received in the second hole).

[0085] For example, the second information may indicate the minimum interval allowed between two adjacent holes. That is, the second information indicates the minimum number of data units allowed between two adjacent holes. The minimum interval may be the minimum interval within a given service cycle (or a given time window or duration). The minimum interval may be represented by an unsigned integer.

[0086] For another example, the second information may indicate the maximum allowed interval between two adjacent holes. That is, the second information indicates the maximum number of data units allowed between two adjacent holes. The maximum interval may be the maximum interval within a given service cycle (or a given time window or duration). The maximum interval may be represented by an unsigned integer.

[0087] In some implementations, the second information may be related to a target time interval. The target time interval refers to the time interval between the time when the hole is generated and the time when the target data unit is expected to be received. The target time interval may also be referred to as the expected hole filling time. For example, suppose that a received data unit is passed to the upper layer, but at this time there are one or more consecutive data units that are located before the data unit in the sending order and have not been received. The one or more consecutive data units are the target data units mentioned above, and the existence of the target data units creates a hole. In this case, the target time interval refers to the duration between the time when the hole is generated by the one or more data units and the time when the upper layer expects to receive the one or more consecutive data units.

[0088] For example, the second information is used to indicate the maximum allowed target time interval. The maximum time interval can be represented by an unsigned integer. The maximum time interval can be in microseconds, for example.

[0089] Third information: used to indicate the first TID and / or first user priority corresponding to the data unit in the first service flow

[0090] The data units in the first service flow correspond to the first TID and / or the first user priority, which may mean that when the data units in the first service flow are transmitted, the data units in the first service flow (individually addressed data units) can be mapped to the first TID and / or the first user priority.

[0091] In some implementations, the first TID may be a TID that allows out-of-order transmission.

[0092] In some implementations, the first TID may be a TID that does not allow out-of-order transmissions.

[0093] In some implementations, the first user priority level may be a user priority level that allows out-of-order transmission.

[0094] In some implementations, the first user priority may be a user priority that does not allow out-of-order transmission.

[0095] In some implementations, if the first service flow is a service flow that allows out-of-order transmission, the first TID may be a TID that allows out-of-order transmission or a TID that does not allow out-of-order transmission. Furthermore, if the first TID is a TID that allows out-of-order transmission and the SCS request is successfully accepted, the transmission of the first service flow needs to meet one or more requirements indicated by the out-of-order transmission parameter (or the transmission of the first service flow matches the one or more requirements indicated by the out-of-order transmission parameter). The out-of-order transmission parameter may be defined or indicated by the second information described above. For example, the out-of-order transmission parameter may include one or more of the following parameters: a maximum size of a hole allowed, a maximum number of holes allowed in a first time period, a minimum interval between two adjacent holes allowed, a maximum interval between two adjacent holes allowed, and a maximum target time interval allowed.

[0096] In some implementations, if the first service flow is a service flow that allows out-of-order transmission, the first user priority may be a user priority that allows out-of-order transmission, or may be a user priority that does not allow out-of-order transmission. Furthermore, if the first user priority is a user priority that allows out-of-order transmission, the transmission of the first service flow needs to meet the requirements of the out-of-order transmission parameters (or the transmission of the first service flow matches the out-of-order transmission parameters). The out-of-order transmission parameters may be defined or indicated by the second information in the foregoing text. For example, the out-of-order transmission parameters may include one or more of the following parameters: the maximum size of a hole allowed, the maximum number of holes allowed in the first time period, the minimum interval between two adjacent holes allowed, the maximum interval between two adjacent holes allowed, and the maximum target time interval allowed.

[0097] In some implementations, if the first service flow is a service flow that does not allow out-of-order transmission, the first TID is a TID that does not allow out-of-order transmission.

[0098] In some implementations, if the first service flow is a service flow that does not allow out-of-order transmission, the first user priority is a user priority that does not allow out-of-order transmission.

[0099] Fourth information: used to indicate the transmission direction of the first service flow

[0100] In some implementations, the fourth information may indicate that the transmission direction of the first service flow is one of an uplink, a downlink, and a direct link. An uplink refers to sending a data unit (such as an MSDU or A-MSDU) from a non-AP STA (or a non-AP MLD) to an AP (or an AP MLD). A downlink refers to sending a data unit (such as an MSDU or A-MSDU) from an AP (or an AP MLD) to a non-AP STA (or a non-AP MLD). A direct link refers to sending a data unit (such as an MSDU or A-MSDU) via a peer-to-peer link.

[0101] Fifth information: used to indicate the in-order or out-of-order processing mode of the data units in the first service flow (or the data units corresponding to the first TID and / or the first user priority mentioned above)

[0102] In some implementations, the fifth information is used to indicate whether to differentiate the data units in the first service flow, that is, whether to divide the data units in the first service flow into different types of data units.

[0103] In some implementations, the fifth information is used to indicate whether the data units in the first service flow are processed as or whether they are processed as data units of the same type.

[0104] In some implementations, the fifth information is used to indicate whether the data units in the first service flow correspond to or correspond to the same SN sequence, the same SN space, or the same SN counter. An SN sequence can correspond to an SN space and / or an SN counter.

[0105] In some implementations, the fifth information is used to indicate whether the data units in the first service flow correspond to or correspond to the same PN sequence, the same PN space, or the same PN counter. A PN sequence may correspond to a PN space and / or a PN counter.

[0106] In some implementations, the fifth information is used to indicate whether the data units in the first business flow are processed according to or whether they are processed according to multiple types of data units. For example, the data units in the first business flow can be divided into multiple types of data units, and the multiple types of data units correspond to different latency requirements (such as low latency requirements and non-low latency requirements). For another example, the data units in the first business flow can be divided into multiple types of data units, and the multiple types of data units correspond to different data unit tags (for example, multiple types of data units correspond to a first tag and a second tag, and the data units corresponding to the first tag and the second tag may have different latency requirements or other requirements). For another example, the data units in the first business flow can be divided into multiple types of data units, and the multiple types of data units correspond to different TCLAS elements.

[0107] In some implementations, the fifth information is used to indicate whether the data units in the first service flow correspond to or correspond to multiple SN sequences, multiple SN spaces, or multiple SN counters. For example, the data units in the first service flow can be divided into two types of data units (such as data units with low-latency transmission requirements and data units without low-latency transmission requirements). Different SN sequences, SN spaces, or SN counters can be allocated for the two types of data units. For another example, the data units in the first service flow can be divided into two types of data units, where one type of data unit corresponds to one TCLAS element in the associated TCLAS element, and the other type of data unit corresponds to other TCLAS elements in the associated TCLAS element. For the two types of data units, different SN sequences, SN spaces, or SN counters can be allocated. For another example, the data units in the first service flow can be divided into multiple types of data units, where each type of data unit corresponds to one TCLAS element in the associated TCLAS element. For multiple types of data units, different SN sequences, SN spaces, or SN counters can be allocated for different types of data units.

[0108] In some implementations, the fifth information is used to indicate whether the data units in the first service flow correspond to or correspond to multiple PN sequences, multiple PN spaces, or multiple PN counters. For example, the data units in the first service flow can be divided into two types of data units (such as data units with low-latency transmission requirements and data units without low-latency transmission requirements), and different PN sequences, PN spaces, or PN counters can be allocated to the two types of data units. For another example, the data units in the first service flow can be divided into two types of data units, one type of data unit corresponding to one TCLAS element in the associated TCLAS elements, and the other type of data unit corresponding to other TCLAS elements in the associated TCLAS elements. For the two types of data units, different PN sequences, PN spaces, or PN counters can be allocated. For another example, the data units in the first service flow can be divided into multiple types of data units, each type of data unit corresponding to one TCLAS element in the associated TCLAS elements. For multiple types of data units, different PN sequences, PN spaces, or PN counters can be allocated to different types of data units.

[0109] Sixth information: used to indicate whether to allow the same type of data units in the first service flow to be transmitted out of order

[0110] The sixth information is used to indicate whether to allow the data units of the same type in the first service flow to be transmitted out of order. The type distinction method of the data units in the first service flow can refer to the relevant description of the fifth information.

[0111] The sixth information may include one or more values. For example, the sixth information may include a first value (e.g., 0) and a second value (e.g., 1). If the value of the sixth information is the first value, it indicates that data units of the same type in the first service flow are allowed to be transmitted out of order. If the value of the sixth information is the second value, it indicates that data units of the same type in the first service flow are not allowed to be transmitted out of order.

[0112] The above text describes in detail the out-of-order transmission related information defined in the embodiments of the present application. The following describes in detail the carrying method of the out-of-order transmission related information with examples.

[0113] In some implementations, a first QoS feature element field may be defined. The first QoS feature element field may include one or more of the first to sixth information mentioned above. The first QoS feature element field can be considered an extension of the QoS feature element field in related technologies. Therefore, the first QoS feature element field is hereinafter referred to as the extended QoS feature element field.

[0114] The extended QoS feature element field may include a control information field and other fields. The first information, third information, fifth information, and sixth information mentioned above may be carried in the control information field. The out-of-order transmission parameter indicated by the second information may be carried in other fields.

[0115] Figure 4 illustrates an example of the format of the Extended QoS Feature Element field. As shown in Figure 4, the Extended QoS Feature Element includes one or more of the following fields: Element ID, Length, Element ID Extension, Control Information, Minimum Serving Interval, Maximum Serving Interval, Minimum Data Rate, Latency Limit, Maximum Out-of-Sequence Hole, Maximum Number of Out-of-Sequence Holes, Minimum Out-of-Sequence Hole Interval, Maximum Out-of-Sequence Hole Interval, and Maximum Expected Out-of-Sequence Hole Fill Time. The meanings of these fields are described below.

[0116] The element identifier, length, and element identifier extension fields may conform to the definitions in the IEEE 802.11 specification. Figure 5 illustrates an example of the control information field format. In the control information field, the direction field specifies the transmission direction of the data unit described by the element, as defined in Table 1.

[0117] Table 1 Direction field encoding

[0118] The TID field contains the TID value corresponding to the data unit described by the element. The first TID mentioned above can be carried in the TID field. The TID field can be set to the same value as the User Priority field, for example.

[0119] The User Priority field contains the user priority value (0-7) corresponding to the data unit described by this element. The first user priority mentioned above can be carried in this TID field. If the Intra-Access Category Priority element is present in the SCS Descriptor element, the User Priority field is set to the value of the User Priority field in the Intra-Access Category Priority element.

[0120] The "Is out-of-order transmission allowed" field can be used to carry the first information mentioned above. The "Is out-of-order transmission allowed" field is used to indicate whether the data unit described by this element (such as MSDU or A-MSDU) is allowed to be transmitted out of order (Note: out-of-order transmission here means that the time sequence in which the sending end sends the data units in the MAC SAP and the time sequence in which the receiving end receives the data units in the MAC SAP may be different). For example, a value of 0 in the "Is out-of-order transmission allowed" field indicates that the data unit described by this element is not allowed to be transmitted out of order; a value of 1 in the "Is out-of-order transmission allowed" field indicates that the data unit described by this element is allowed to be transmitted out of order in the MAC SAP.

[0121] The Data Unit Handling field is used to carry the fifth information mentioned above. The Data Unit Handling field can be used to specify the processing method for in-order or out-of-order transmission of the data unit described by this element. Table 2 gives an example of the encoding method of this field.

[0122] Table 2: Data unit processing field encoding

[0123] The "Whether out-of-order transmission of the same type is allowed" field can be used to carry the sixth information mentioned above. The "Whether out-of-order transmission of the same type is allowed" field is used to indicate whether data units of the same type are allowed to be transmitted out-of-order in the MAC SAP (Note: the type distinction method refers to the indication of the data unit processing field. The same type of data units can use the same SN sequence and / or PN sequence). For example, a value of 0 in the "Whether out-of-order transmission of the same type is allowed" field indicates that data units of the same type are not allowed to be transmitted out-of-order in the MAC SAP; a value of 1 in the "Whether out-of-order transmission of the same type is allowed" field indicates that data units of the same type are allowed to be transmitted out-of-order in the MAC SAP.

[0124] The "Additional Parameters Presence Bitmap" field contains a bitmap. The i-th entry of the bitmap is set to 1 if the i-th field starting from the "Maximum Out-of-Sequence Hole Size" field is present in the element, and is set to 0 otherwise.

[0125] The Link ID field contains the link identifier. This identifier corresponds to the link on which the direct link transmission will occur. This field is reserved if the Direction field is not equal to 2 (indicating a direct link).

[0126] The content of the "Minimum Service Interval" field is related to the value of the "Direction" field.

[0127] For example, if the Direction field is set to 0 (uplink), the Minimum Service Interval field contains an unsigned integer that specifies the minimum time interval between the start times of two consecutive service periods allocated to STAs for uplink frame exchanges. The minimum time interval is in microseconds.

[0128] For example, if the Direction field is set to 1 (downlink), the Minimum Service Interval field contains an unsigned integer that specifies the minimum time interval between the start times of two consecutive service periods allocated to STAs for downlink frame exchanges. This minimum time interval is in microseconds.

[0129] For example, if the Direction field is set to 2 (direct link), the Minimum Service Interval field contains an unsigned integer that specifies the minimum time interval between the start times of two consecutive service periods allocated to a STA for direct link frame exchanges. This minimum time interval is in microseconds.

[0130] The content of the "Maximum Service Interval" field is related to the value of the "Direction" field.

[0131] For example, if the Direction field is set to 0 (uplink), the Maximum Service Interval field contains an unsigned integer that specifies the maximum time interval between the start times of two consecutive service periods allocated to STAs for uplink frame exchanges. The maximum time interval is in microseconds.

[0132] For example, if the Direction field is set to 1 (downlink), the Maximum Service Interval field contains an unsigned integer that specifies the maximum time interval between the start times of two consecutive service periods allocated to a STA for a downlink frame exchange sequence. This maximum time interval is in microseconds.

[0133] For example, if the Direction field is set to 2 (direct link), the Maximum Service Interval field contains an unsigned integer that specifies the maximum time interval between the start times of two consecutive service periods allocated to STAs for direct link frame exchanges. This maximum time interval is in microseconds.

[0134] It should be understood that the value of the "Maximum Service Interval" field is greater than or equal to the value of the "Minimum Service Interval" field.

[0135] The Minimum Data Rate field contains an unsigned integer that indicates the minimum data rate in the MAC SAP for transmitting data units (such as MSDUs or A-MSDUs) belonging to the service flow described by this element. The unit of this field is kilobits per second.

[0136] The Delay Bound field contains an unsigned integer (in microseconds) that indicates the maximum time to transmit a data unit (such as an MSDU or A-MSDU) belonging to the service flow described by this element. Taking an MSDU or A-MSDU as an example, the transmission time is measured from the time the MSDU or the first of the MSDUs that constitute an A-MSDU reaches the local MAC sublayer through the local MAC SAP until the MPDU containing the MSDU is successfully transmitted to the destination.

[0137] The Maximum Out-of-Sequence Hole field can be used to carry the maximum size of a hole allowed mentioned above. For an introduction to the "maximum size of a hole allowed", please refer to the previous article and will not be repeated here.

[0138] The Maximum Out-of-Sequence Hole Number field may be used to carry the maximum number of holes allowed in the first period mentioned above. For an introduction to the "maximum number of holes allowed in the first period," reference may be made to the previous text and will not be repeated here.

[0139] The Minimum Out-of-Sequence Hole Interval field can be used to carry the minimum interval between two adjacent holes mentioned above. For an introduction to the "minimum interval between two adjacent holes", please refer to the previous article and will not be repeated here.

[0140] The Maximum Out-of-Sequence Hole Interval field can be used to carry the maximum interval allowed between two adjacent holes mentioned above. For an introduction to the "maximum interval allowed between two adjacent holes," please refer to the previous article and will not be repeated here.

[0141] The Maximum Expected Out-of-Sequence Hole Filling Time field can be used to carry the maximum target time interval mentioned above. For an introduction to the "maximum target time interval", please refer to the previous article and will not be repeated here.

[0142] The Extended QoS Features element field is described in detail above. This Extended QoS Features element field can be carried in the SCS Descriptor element field. The SCS Descriptor element defines information about the flow being classified using the SCS process. Figure 6 shows an example of the SCS Descriptor element field.

[0143] 6 , the element identification field and length field may comply with the definition of the IEEE 802.11 specification. The SCSID field is set to a non-zero value selected by the non-AP STA, which uses this field to identify the SCS stream specified in this SCS descriptor element.

[0144] The Request Type field is used to identify the type of SCS request, including Add, Remove, and Change.

[0145] When the Request Type field is equal to "Add" or "Change," the frame includes the Intra-Access Category Priority Element field, which complies with the definition of the "Intra-Access Category Priority Element" in the IEEE 802.11 specification. The Intra-Access Category Priority Element provides the non-AP STA with the relative priority information of flows defined by the access category (AC) to the AP.

[0146] The TCLAS Element field contains zero or more TCLAS elements, which specify how the incoming MSDU is classified as part of this SCS flow. The TCLAS Element field conforms to the "TCLAS Element" definition in the IEEE 802.11 specification. When the Request Type field is equal to "Add" or "Change," one or more TCLAS elements are present; when the Request Type field is equal to "Remove," no TCLAS elements are present.

[0147] The TCLAS element contains a set of necessary parameters for identifying various PDUs or incoming MSDUs (from higher layers in all STAs or from the distribution system (DS) corresponding to the AP) belonging to a specific traffic stream (TS).

[0148] When there are multiple TCLAS elements in the TCLAS element field and the TCLAS processing element field contains a TCLAS processing element, the TCLAS processing element defines how to process the multiple TCLAS elements. The specific processing method complies with the definition of "TCLAS processing element" in the IEEE 802.11 specification. Among them, the TCLAS processing element, when included in the SCS description element, can indicate one of the following:

[0149] The PDU content or MSDU parameters must match the parameters in all related TCLAS elements;

[0150] The PDU content or MSDU parameters must match at least one associated TCLAS element;

[0151] A PDU or MSDU that does not belong to any other TS is classified to that TS using a TCLAS processing element, in which case there is no associated TCLAS element.

[0152] The QoS Characteristics Element field contains zero or one QoS Characteristics element to describe the traffic characteristics and QoS expectations of the SCS flow. When the Request Type field is equal to "Add" or "Change", there are zero or one QoS Characteristics elements; when the Request Type field is equal to "Remove", there are no QoS Characteristics elements.

[0153] The Extended QoS Characteristics Element field contains zero or one Extended QoS Characteristics element to describe the traffic characteristics and QoS expectations of the SCS flow (allowing out-of-order transmission of data units). When the Request Type field is equal to "Add" or "Change", zero or one Extended QoS Characteristics element is present. When the Request Type field is equal to "Remove", no QoS Characteristics element is present.

[0154] The following is a detailed explanation of the embodiments of the present application from the perspective of frame interaction.

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

[0156] In some implementations, the first frame may be used to negotiate whether out-of-order transmission is permitted and / or parameters related to out-of-order transmission. For example, the first frame may include one or more of the first to sixth information items mentioned above. Details of the first to sixth information items are described above and are not further elaborated here.

[0157] In some implementations, the first device may be a non-AP STA or a non-AP MLD, and the second device may be an access point or an AP MLD.

[0158] In some implementations, the first frame may be a request frame, such as an SCS request frame.

[0159] In some implementations, the first frame may be a response frame, such as an SCS response frame.

[0160] In some implementations, the first frame may be a frame defined in a negotiation process for in-sequence / out-of-sequence transmission of other data units.

[0161] Taking the first frame as a first request frame (such as an SCS request frame) as an example, the second device can accept the request corresponding to the first request frame or reject the request corresponding to the first request frame.

[0162] In some implementations, if the second device rejects the SCS request corresponding to the first request frame, the second device may send a first response frame to the first device. The first response frame includes seventh information. The seventh information may be used to indicate that the second device does not support out-of-order transmission.

[0163] In some implementations, if the second device rejects the request corresponding to the first request frame, the second device may send a first response frame to the first device. The first response frame includes seventh information. The seventh information may be used to indicate that the second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

[0164] In some implementations, after receiving the first response frame, the first device may send a second request frame to the second device. The second request frame may include the out-of-order transmission parameter modified based on the modification suggestion.

[0165] In some implementations, the first device negotiates in-order or out-of-order transmission with the second device; after the negotiation is successfully completed, the first device sends a second request frame (such as an SCS request frame) to the second device, and the second request frame includes the negotiated out-of-order transmission parameters.

[0166] In some implementations, the first frame is a first request frame. After the first device sends the first request frame to the second device, the first device receives a first response frame sent by the second device. The first response frame includes eighth information indicating that the request corresponding to the first request frame was successfully accepted. After receiving the first response frame, the first device and / or the second device transmits the first service flow based on whether out-of-order transmission is allowed and / or the out-of-order transmission parameter.

[0167] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, then the transmission of the first service flow meets one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on the one or more requirements indicated by the out-of-order transmission parameter (or, the transmission of the first service flow needs to be guided by the one or more requirements indicated by the out-of-order transmission parameter); wherein the first request frame indicates that out-of-order transmission of data units of the first service flow is allowed.

[0168] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space, or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

[0169] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first business flow correspond to different SN spaces, different SN sequences, different PN spaces, or different PN sequences, the data units in the first business flow use replay detection based on the PN window; or, the data units in the first business flow use replay detection not based on the PN window; wherein the first request frame indicates that the data units of the first business flow are allowed to be transmitted out of order.

[0170] The interactive process shown in Figure 7 can occur in the SCS process. That is to say, the embodiment of the present application can be applied to the SCS process and extend the SCS process. In this case, the interactive process provided by the embodiment of the present application can be called an extended SCS process. The following describes the embodiment of the present application in more detail by taking the updating or extension of the SCS process as an example. It should be noted that the examples below are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0171] This example proposes a method for describing a business flow that allows out-of-order transmission, as well as an extended SCS mechanism and method for classifying data units and describing business flows that allow out-of-order transmission.

[0172] Defines extended QoS feature elements for describing service flows that allow out-of-order transmission

[0173] The extended QoS feature element contains a set of out-of-order transmission parameters that define the characteristics and QoS expectations of service flows that allow out-of-order transmission of data units in the context of a specific station or multi-link device. These parameters are used by non-AP STAs (or non-AP MLDs) and APs (or AP MLDs) to support the transmission of QoS service flows using the SCS process and the processes defined in the in-order / out-of-order data unit transmission negotiation. Out-of-order transmission refers to the possibility that the time sequence in which the data units are sent by the transmitter in the MAC SAP may differ from the time sequence in which the data units are received by the receiver in the MAC SAP (Note: This refers to the difference between the order in which data units are received and the order in which they are sent, occurring outside the case of data unit loss, that is, the difference between the order in which data units are received and the order in which they are sent, occurring when data unit loss is not determined). For a detailed description of out-of-order transmission, please refer to the previous article and will not be elaborated here.

[0174] Expanding the definition of the SCS process

[0175] First: Expand SCS process functions and behaviors

[0176] The SCS process allows for the use of Layer 2 and / or Layer 3 signaling to establish a classification to match incoming individually addressed data units (such as MSDUs or A-MSDUs). Once the data units are classified, individually addressed data units matching the classification are assigned to an AC and marked with Drop Eligibility. When intra-access category prioritization is enabled, the SCS process allows data units matching the classification to be assigned to the primary or backup enhanced distributed channel access (EDCA) transmit queues for more granular prioritization.

[0177] The extended SCS procedure (an extension to the SCS procedure currently defined in IEEE 802.11) allows a non-AP STA (or non-AP MLD) to request the AP (or AP MLD) to classify incoming individually addressed data units (MSDUs or A-MSDUs) and / or describe their flow characteristics to the AP (or AP MLD) based on parameters provided by the non-AP STA (or non-AP MLD). The extended SCS procedure can be used to describe flow characteristics that allow for out-of-order transmission of data units (such as MSDUs or A-MSDUs). Out-of-order transmission refers to the possibility that the time order in which data units are sent by the sender in the MAC SAP differs from the time order in which they are received by the receiver in the MAC SAP. The degree of out-of-order transmission allowed by an SCS flow can be negotiated using relevant fields in the extended QoS characteristics element carried in relevant management frames (such as SCS request frames and / or SCS response frames) in the SCS procedure. (For a description of the extended QoS characteristics element, please refer to the previous section and will not be detailed here.) Furthermore, individually addressed data units in the corresponding direction that match the classification can be mapped to specific TIDs and / or user priorities. For example, based on whether out-of-order transmission is permitted for the individually addressed data unit of the matching class and / or the out-of-order transmission method and transmission parameters, the individually addressed data unit of the matching class is mapped to a specific TID and / or specific user priority that matches the corresponding "whether out-of-order transmission is permitted" parameter and / or the out-of-order transmission method and transmission parameters. For the individually addressed data unit of the matching class mapped to the specific TID and / or specific user priority, the sender of the data unit transmits the data according to the previously negotiated out-of-order transmission parameters.

[0178] In particular, when an SCS request is successfully accepted, the extended QoS feature element carried therein includes whether out-of-order transmission is allowed and / or the method and transmission parameters for out-of-order transmission, and the individually addressed data unit of the corresponding direction matching the classification is mapped to a specific TID and / or specific user priority that matches the corresponding "whether out-of-order transmission is allowed" parameter and / or the method and transmission parameters for out-of-order transmission.

[0179] For ease of understanding, the following describes the SCS extension process in more detail with reference to two specific embodiments.

[0180] Example 1

[0181] When an SCS request is successfully accepted, the values ​​of the various fields in the extended QoS feature element it carries are as follows.

[0182] The Direction field value is 1. This means that the Direction field indicates a downlink. The so-called downlink refers to the link for sending data units (such as MSDUs or A-MSDUs) from the AP (or AP MLD) to the non-AP STA (or non-AP MLD).

[0183] The TID field value and the user priority field value are both indicated as 6.

[0184] The value of the "Is Out-of-order Transmission Allowed" field is 1, indicating that the data unit described by this element is allowed to be transmitted out of order in the MAC SAP.

[0185] The value of the data unit processing field is 0, indicating that data units (referring to data units corresponding to the TID indicated by the TID field) are not distinguished, and a unified SN sequence (or SN counter) and / or PN sequence (or PN counter) is used for the data units, that is, the data units corresponding to the TID indicated by the TID field are treated as data units of the same type.

[0186] The value of the "Whether to allow out-of-order transmission of the same type" field is 1, indicating that data units of the same type are allowed to be transmitted out of order in the MAC SAP.

[0187] The value of the Maximum Out-of-Sequence Hole Size field is 20.

[0188] As the sender of the data unit, the AP (or AP MLD) processes the data unit with a TID value of 6 in the following manner.

[0189] 1) Data units with TID value 6 are not distinguished

[0190] For a TID value of 6, data units with different service flows or different markings are not distinguished; data units with a TID value of 6 corresponding to different service flows, different transmission delay requirements, different transmission urgency or other QoS requirements are not marked.

[0191] 2) SN allocation and processing

[0192] If the recipient is a non-MLD STA, the SN counter or SN sequence is allocated according to <the STA MAC address identified by Address 1, TID(6)>. If the recipient is an MLD, the SN counter or SN sequence is allocated according to <the MLD MAC address to which the STA identified by Address 1 belongs, TID(6)>. The above-mentioned Address 1 refers to the RA of the STA serving as the recipient.

[0193] 3) PN Allocation and Processing

[0194] The PN counter or PN sequence is allocated according to <TA, RA, TID i or the corresponding priority>.

[0195] For example, if the recipient is a non-MLD STA, the PN counter or PN sequence is allocated according to <the STA MAC address identified by TA, the STA MAC address identified by RA, TID(6) or user priority(6)>. Another example, if the recipient is an MLD, the PN counter or PN sequence is allocated according to <the MLD MAC address to which the STA identified by TA belongs, the MLD MAC address to which the STA identified by RA belongs, TID(6) or user priority(6)>.

[0196] The non-AP STA (or non-AP MLD) as the recipient of the data unit adopts the following processing method for the data unit with a TID value of 6.

[0197] 1) SN Processing and Reordering

[0198] For the received data unit corresponding to <TA, TID(6)>, even if there are data units that have not been received before and whose corresponding SN is lower than the SN of this data unit (that is, the data units that are in the front in the transmission order but have not been received), when the difference between the SN of the received and to-be-transmitted data unit and the SN of the un-received data unit (for example, the earliest un-received data unit) is less than or equal to the set threshold size (that is, the value of the SN deviation threshold field, which is 20 in this example), still pass the data unit of the specific TID or marked (such as MSDU or A-MSDU) to the next MAC process (or pass it to the upper layer).

[0199] 2) PN Processing and Replay Detection

[0200] The replay counter is allocated according to <TA, RA, TID(6) or user priority(6)> and replay detection is performed; replay detection of the data unit can be carried out using PN window-based replay detection (the PN window size is 20 in this example).

[0201] Embodiment 2

[0202] When an SCS request is successfully accepted, the values ​​of the various fields in the extended QoS feature element it carries are as follows.

[0203] The direction field value indicates 0, that is, the direction field indicates uplink. The so-called uplink refers to the link for sending data units (such as MSDUs or A-MSDUs) from a non-AP STA (or non-AP MLD) to an AP (or AP MLD).

[0204] The TID field value and the user priority field value are both indicated as 5.

[0205] The value of the "Is Out-of-order Transmission Allowed" field is 1, indicating that the data unit described by this element is allowed to be transmitted out of order in the MAC SAP.

[0206] The data unit processing field value is 1, indicating that two types of data units are distinguished (such as data units with low-latency transmission requirements and data units without low-latency transmission requirements), and different SN sequences and / or PN sequences are allocated to the two types of data units).

[0207] The value of the "Whether to allow out-of-order transmission of the same type" field is 0, indicating that data units of the same type are not allowed to be transmitted out of order in the MAC SAP.

[0208] A non-AP STA (or non-AP MLD), as the sender of a data unit, processes a data unit with a TID value of 5 in the following manner.

[0209] 1) Data unit marking

[0210] For uplink data units with TID 5, the system distinguishes between data units in delay-sensitive traffic flows and data units in non-delay-sensitive traffic flows, and marks the different types of data units. Specifically, data units in delay-sensitive traffic flows are assigned a delay-sensitive tag, while data units in non-delay-sensitive traffic flows are assigned a non-delay-sensitive tag.

[0211] 2) SN allocation and processing

[0212] The SN counter or SN sequence is allocated according to <MLD MAC address to which the STA identified by address 1 is attached, TID (5), data unit tag>.

[0213] For a given receiver, the data unit corresponding to TID (5) (i.e., a separately addressed data unit) uses one SN space and multiple counters. The counters are indexed by <MLD MAC address of the STA identified by address 1, TID (5), and data unit tag (delay-sensitive tag or non-delay-sensitive tag)>. Address 1 refers to the RA of the receiving STA.

[0214] 3) PN Allocation and Processing

[0215] Allocate a PN counter or PN sequence according to <the MLD MAC address to which the STA identified by TA belongs, the MLD MAC address to which the STA identified by RA belongs, TID(5) or user priority(5), data unit flag (delay-sensitive flag or non-delay-sensitive flag)>.

[0216] For a given receiver, the data unit corresponding to TID(5) (i.e., a separately addressed data unit) uses one PN space and multiple counters (or PN sequences). Among them, the counters are indexed according to <the MLD MAC address to which the STA identified by TA belongs, the MLD MAC address to which the STA identified by RA belongs, TID(5) or user priority, data unit flag>.

[0217] The AP (or AP MLD) as the receiver of the data unit adopts the following processing method for the data unit with TID value of 5.

[0218] 1) SN Processing and Reordering

[0219] When the transmitting party is a non-MLD STA, allocate and / or control the reordering buffer according to <the STA MAC address identified by TA, TID(5), data unit flag (i.e., delay-sensitive flag and non-delay-sensitive flag)>.

[0220] When the transmitting party is an MLD, allocate and / or control the reordering buffer according to <the MLD MAC address to which the STA identified by TA belongs, TID(5), data unit flag (i.e., delay-sensitive flag and non-delay-sensitive flag)>.

[0221] 2) PN Processing and Replay Detection

[0222] Allocate a replay counter and perform replay detection according to <TA, RA, TID(5) or user priority(5), data unit flag (i.e., delay-sensitive flag and non-delay-sensitive flag)>.

[0223] Second: Extended SCS Process Rules and Constraints

[0224] A non-AP STA (or non-AP MLD) can establish an SCS flow that allows out-of-order transmission of data units (such as MSDU or A-MSDU) with an AP (or AP MLD) according to the SCS process currently defined in IEEE 802.11 and the additional rules and constraints proposed in the embodiments of this application (see the following description).

[0225] If the Request Type field in the SCS request frame transmitted by a non-AP STA (or non-AP MLD) is set to "Add" or "Change," the SCS request frame includes an SCS descriptor element, and the SCS descriptor element includes an extended QoS characteristics element. The extended QoS characteristics element describes the service flow characteristics of the SCS flow requested to allow out-of-order transmission. In particular, if the non-AP STA (or non-AP MLD) is unsure whether the AP (or AP MLD) allows out-of-order transmission of the SCS flow, the non-AP STA (or non-AP MLD) shall not send an SCS request frame containing an SCS descriptor element with an extended QoS characteristics element to the AP (or AP MLD). For example, if a non-AP STA (or non-AP MLD) does not receive a capability element sent by an AP (or AP MLD) (the value of the capability element is 1, indicating that the AP (or AP MLD) allows out-of-order transmission of SCS streams), the non-AP STA (or non-AP MLD) shall not send an SCS request frame containing an SCS descriptor element of an extended QoS feature element to the AP (or AP MLD).

[0226] MLD maintains a SCSID for each non-AP MLD at the MLD level. This means that the SCSID used by a non-AP STA affiliated with a non-AP MLD in an SCS request frame sent to an AP affiliated with an AP MLD is unique among all STAs affiliated with the non-AP MLD. The SCSID is used by the non-AP MLD to request the creation, modification, or deletion of an SCS stream. The SCSID is used by the AP MLD to identify an SCS stream.

[0227] An SCS request frame containing an extended QoS feature element (where the direction field of the extended QoS feature element is set to uplink or downlink) sent by a non-AP STA affiliated with a non-AP MLD to an AP affiliated with an AP MLD, or an SCS request frame without a QoS feature element, is interpreted as a request to create or modify an SCS flow applied to the MLD level.

[0228] When the AP (or AP MLD) rejects the SCS request, the value of the SCS status field of the SCS response frame can be set to one of the following corresponding values: request rejected (REQUEST_DECLINED); the requested TCLAS is not supported by the AP (REQUESTED_TCLAS_NOT_SUPPORTED_BY_AP); rejected with suggested changes (REJECTED_WITH_SUGGESTED_CHANGES); insufficient TCLAS processing resources (INSUFFICIENT_TCLAS_PROCESSING_RESOURCES); and the AP does not support the requested out-of-order delivery (REQUESTED_OUT_OF_ORDER_DELIVERY_NOT_SUPPORTED_BY_AP).

[0229] If the AP (or AP MLD) sets the Status field value to Reject with a proposed modification, the AP may include an SCS Descriptor element with an Extended QoS Features element in the SCS Response frame to indicate the recommended extended QoS feature parameters for the SCS flow. Specifically, the SCS Response frame may include the Allowed Out-of-Sequence Delivery parameter.

[0230] The AP (or AP MLD) may schedule and transmit data units according to the parameters defined by the extended QoS feature element. Specifically, when an SCS request is successfully accepted and the extended QoS feature element it carries includes out-of-order transmission parameters, the AP (or AP MLD) and / or non-AP STA (or non-AP MLD) shall transmit data units corresponding to the specified TID and / or user priority in the specified direction of the service flow defined by the extended QoS feature element in accordance with the allowed out-of-order delivery requirements (including whether out-of-order is allowed, data unit processing, whether out-of-order is allowed for the same type, maximum out-of-order hole size, maximum number of out-of-order holes, minimum out-of-order hole interval, maximum out-of-order hole interval, maximum expected out-of-order hole fill time, and other related parameters).

[0231] In particular, when an SCS request is successfully accepted and the extended QoS feature element it carries includes an out-of-order transmission parameter, it is necessary to ensure that the data units corresponding to the specified TID and / or user priority in the specified direction of the service flow defined by the extended QoS feature element meet the requirements of the out-of-order transmission parameter.

[0232] Example 3

[0233] If the SCS request frame sent by a non-AP STA (or non-AP MLD) carries an extended QoS feature element, and the transmission of the service flow defined by the extended QoS feature element (the service flow corresponding to the TID and / or user priority in the specified direction) does not comply with the out-of-order transmission parameter requirements defined by the extended QoS feature element, that is, it does not comply with the requirements corresponding to one or more field values ​​of the relevant parameters specified by the extended QoS feature element, such as whether out-of-order transmission is allowed, data unit processing, whether out-of-order transmission of the same type is allowed, maximum out-of-order hole size, maximum number of out-of-order holes, minimum out-of-order hole interval, maximum out-of-order hole interval, and maximum expected out-of-order hole fill time, the AP (or AP MLD) may send an SCS response frame to the non-AP STA (or non-AP MLD) to reject the SCS request. The AP (or AP MLD) can set the status value corresponding to "AP does not support the requested out-of-order delivery (REQUESTED_OUT_OF_ORDER_DELIVERY_NOT_SUPPORTED_BY_AP)" or "rejected with suggested changes (REJECTED_WITH_SUGGESTED_CHANGES)" in the SCS status field of the SCS response frame. After receiving the SCS response frame, the non-AP STA (or non-AP MLD) can adopt one of the following methods:

[0234] (1) Modify the relevant parameters in the extended QoS feature element in the SCS request according to the out-of-order transmission parameters in the recommended extended QoS feature element carried in the SCS response frame and re-initiate the SCS request;

[0235] (2) Initiate negotiation on in-order / out-of-order transmission of data units to the AP (or AP MLD) so that the transmission of the service flow defined by the extended QoS feature element carried in the SCS request complies with the out-of-order transmission parameter requirements defined by the extended QoS feature element, that is, it complies with the requirements corresponding to one or more field values ​​in the relevant parameters such as whether out-of-order transmission is allowed, data unit processing, whether out-of-order transmission of the same type is allowed, maximum out-of-order hole size, maximum number of out-of-order holes, minimum out-of-order hole interval, maximum out-of-order hole interval, and maximum expected out-of-order hole filling time specified by the extended QoS feature element; after the negotiation on in-order / out-of-order transmission of data units is successfully completed, the non-AP STA (or non-AP MLD) re-initiates the SCS request to the AP (or AP MLD).

[0236] Example 4

[0237] If data unit transmission in the target service flow of a non-AP STA (or non-AP MLD) (i.e., the service flow in the specified direction and corresponding to the specified TID and / or user priority defined by the extended QoS feature element) does not comply with the out-of-order delivery parameter requirements of the extended QoS feature element, that is, does not comply with the requirements corresponding to one or more field values ​​of the relevant parameters specified by the extended QoS feature element, such as whether out-of-order delivery is allowed, data unit processing, whether out-of-order delivery of the same type is allowed, maximum out-of-order hole size, maximum number of out-of-order holes, minimum out-of-order hole interval, maximum out-of-order hole interval, and maximum expected out-of-order hole fill time, the non-AP STA (or non-AP MLD) does not first initiate an SCS request to the AP (or AP MLD), but instead initiates in-order / out-of-order data unit transmission negotiation with the AP (or AP MLD) to ensure that data unit transmission in the service flow defined by the extended QoS feature element complies with the out-of-order delivery parameter requirements of the extended QoS feature element. After the negotiation of in-order / out-of-order transmission of data units is successfully completed, the non-AP STA (or non-AP MLD) initiates an SCS request to the AP (or AP MLD).

[0238] The head-of-line blocking problem can be solved by introducing a mechanism for handling data units sent out of order in specific scenarios (such as scenarios where multiple service flows are mapped to a single flow identifier (TID), or scenarios where Layer 2 and Layer 3 protocols coordinate to handle low-latency flow transmission). To ensure that the out-of-order transmission mechanism is effectively applied to the transmission of low-latency flows, the non-AP STA (or non-AP MLD) and the AP (or AP MLD) need to negotiate to determine whether the SCS flow adopts the out-of-order transmission mechanism and the related out-of-order transmission parameters and their associated TID and / or user priority parameters. This example proposes a method for describing service flows that allow out-of-order transmission, as well as an extended SCS mechanism and method for classifying data units and describing service flows that allow out-of-order transmission. This example defines extended QoS feature elements for describing service flows that allow out-of-order transmission, and defines an extended SCS process for classifying data units and describing service flows that allow out-of-order transmission. The above improvements help both communicating parties clarify the out-of-order transmission method, thereby ensuring the effective application of out-of-order transmission in practice.

[0239] The out-of-order transmission method described in the above embodiments can be applied to the SCS flow establishment and negotiation mechanism in a single BSS scenario and a multi-link operation scenario, and can also be applied to the SCS flow establishment and negotiation scenario in a multi-AP collaboration scenario.

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

[0241] Figure 8 is a structural diagram of a communication device provided by an embodiment of the present application. The communication device 800 shown in Figure 8 may be the first device mentioned above. The communication device 800 includes a first communication module 810. The first communication module 810 is used to send a first frame to the second device, and the first frame includes one or more of the following: first information for indicating whether the data units in the first service flow are allowed to be transmitted out of order; second information for indicating the quality of service QoS characteristics of the first service flow that allows out of order transmission and / or the out of order transmission parameters allowed by the first service flow; third information for indicating the first traffic identifier TID and / or the first user priority corresponding to the data units in the first service flow; fourth information for indicating the transmission direction of the first service flow.

[0242] In some implementations, the second information is related to a hole generated in the first business flow during the out-of-order transmission, and the hole corresponds to a target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

[0243] In some implementations, the second information is used to indicate one or more of the following out-of-order transmission parameters:

[0244] The maximum size of a cavity allowed;

[0245] The maximum number of holes allowed in the first period;

[0246] The minimum distance allowed between two adjacent cavities;

[0247] The maximum distance allowed between two adjacent holes;

[0248] The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

[0249] In some implementations, the first frame further includes fifth information, where the fifth information is used to indicate whether the data units in the first service flow are to be processed in sequence or out of sequence.

[0250] In some implementations, the fifth information is used to indicate one of the following:

[0251] The data units in the first service flow are processed as data units of the same type;

[0252] The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter;

[0253] The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter;

[0254] The data units in the first service flow are processed according to multiple types of data units;

[0255] The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters;

[0256] The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

[0257] In some implementations, the multiple types of data units satisfy one or more of the following:

[0258] Corresponding to different latency requirements;

[0259] Corresponding to different flow classification TCLAS elements;

[0260] Corresponding to different data unit tags.

[0261] In some implementations, the first frame further includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

[0262] In some implementations, the first frame includes a first QoS characteristics element field, and the first QoS characteristics element field includes one or more of the first information, the second information, and the third information.

[0263] In some implementations, the first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

[0264] In some implementations, the first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

[0265] In some implementations, if the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied:

[0266] The first TID is a TID that allows or does not allow out-of-order transmission;

[0267] The first user priority is a user priority for allowing or not allowing out-of-order transmission.

[0268] In some implementations, if the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied:

[0269] The first TID is a TID that does not allow out-of-order transmission;

[0270] The first user priority is a user priority that does not allow out-of-order transmission.

[0271] In some implementations, the first frame is a first request frame, and the communication device further includes:

[0272] The first device receives a first response frame sent by the second device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following:

[0273] The second device does not support the out-of-order transmission;

[0274] The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

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

[0276] The second communication module is configured to send a second request frame to the second device, where the second request frame includes the out-of-order transmission parameters modified based on the modification suggestion.

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

[0278] The third communication module is configured to negotiate in-order or out-of-order transmission with the second device; after the negotiation is successfully completed, send a second request frame to the second device, where the second request frame includes the negotiated out-of-order transmission parameters.

[0279] In some implementations, the first frame is a first request frame, and the communication device further includes:

[0280] A fourth communication module is used to receive a first response frame sent by the second device, where the first response frame contains eighth information, and the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; and transmit the first service flow based on whether out-of-order transmission is allowed and / or the out-of-order transmission parameters.

[0281] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, then the transmission of the first service flow meets one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

[0282] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space, or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

[0283] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces, or different PN sequences, the data units in the first service flow adopt replay detection based on the PN window; or, the data units in the first service flow adopt replay detection not based on the PN window; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

[0284] In some implementations, the first request frame is an SCS request frame, and the first response frame is an SCS response frame.

[0285] In some implementations, the first device is a non-access point station and the second device is an access point; or, the first device is a non-access point multi-link device and the second device is an access point multi-link device.

[0286] Figure 9 is a structural diagram of a communication device provided in another embodiment of the present application. The communication device 900 shown in Figure 9 may be the second device mentioned above. The communication device 900 includes a first communication module 910. The first communication module 910 is used to receive a first frame sent by a first device, and the first frame includes one or more of the following: first information for indicating whether data units in a first service flow are allowed to be transmitted out of order; second information for indicating the quality of service QoS characteristics of the first service flow that allows out of order transmission and / or the out of order transmission parameters allowed by the first service flow; third information for indicating the first traffic identifier TID and / or the first user priority corresponding to the data unit in the first service flow; fourth information for indicating the transmission direction of the first service flow.

[0287] In some implementations, the second information is related to a hole generated in the first business flow during the out-of-order transmission, and the hole corresponds to a target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

[0288] In some implementations, the second information is used to indicate one or more of the following out-of-order transmission parameters:

[0289] The maximum size of a cavity allowed;

[0290] The maximum number of holes allowed in the first period;

[0291] The minimum distance allowed between two adjacent cavities;

[0292] The maximum distance allowed between two adjacent holes;

[0293] The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

[0294] In some implementations, the first frame further includes fifth information, where the fifth information is used to indicate whether the data units in the first service flow are to be processed in sequence or out of sequence.

[0295] In some implementations, the fifth information is used to indicate one of the following:

[0296] The data units in the first service flow are processed as data units of the same type;

[0297] The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter;

[0298] The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter;

[0299] The data units in the first service flow are processed according to multiple types of data units;

[0300] The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters;

[0301] The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

[0302] In some implementations, the multiple types of data units satisfy one or more of the following:

[0303] Corresponding to different latency requirements;

[0304] Corresponding to different flow classification TCLAS elements;

[0305] Corresponding to different data unit tags.

[0306] In some implementations, the first frame further includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

[0307] In some implementations, the first frame includes a first QoS characteristics element field, and the first QoS characteristics element field includes one or more of the first information, the second information, and the third information.

[0308] In some implementations, the first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

[0309] In some implementations, the first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

[0310] In some implementations, if the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied:

[0311] The first TID is a TID that allows or does not allow out-of-order transmission;

[0312] The first user priority is a user priority for allowing or not allowing out-of-order transmission.

[0313] In some implementations, if the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied:

[0314] The first TID is a TID that does not allow out-of-order transmission;

[0315] The first user priority is a user priority that does not allow out-of-order transmission.

[0316] In some implementations, the first frame is a first request frame, and the communication device further includes:

[0317] The second communication module is configured to send a first response frame to the first device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following:

[0318] The second device does not support the out-of-order transmission;

[0319] The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

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

[0321] The third communication module is configured to receive a second request frame sent by the first device, where the second request frame includes out-of-order transmission parameters modified based on the modification suggestion.

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

[0323] The fourth communication module is configured to negotiate in-order or out-of-order transmission with the first device; after the negotiation is successfully completed, receive a second request frame sent by the first device, where the second request frame includes the negotiated out-of-order transmission parameters.

[0324] In some implementations, the first frame is a first request frame, and the communication device further includes:

[0325] A fifth communication module is used to send a first response frame to the first device, where the first response frame contains eighth information, and the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; and the first service flow is transmitted according to whether out-of-order transmission is allowed and / or the out-of-order transmission parameters.

[0326] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, then the transmission of the first service flow meets one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

[0327] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space, or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

[0328] In some implementations, when the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces, or different PN sequences, the data units in the first service flow adopt replay detection based on the PN window; or, the data units in the first service flow adopt replay detection not based on the PN window; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

[0329] In some implementations, the first request frame is an SCS request frame, and the first response frame is an SCS response frame.

[0330] In some implementations, the first device is a non-access point station and the second device is an access point; or, the first device is a non-access point multi-link device and the second device is an access point multi-link device.

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

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

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

[0334] The apparatus 1000 may further include a transceiver 1030. The processor 1010 may communicate with other devices or chips via the transceiver 1030. For example, the processor 1010 may transmit and receive data with other devices or chips via the transceiver 1030.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0351] 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, It is characterized in that include: The first device sends a first frame to the second device, where the first frame includes one or more of the following: The first information is used to indicate whether out-of-order transmission of data units in the first service flow is allowed; second information, used to indicate the quality of service QoS characteristics of the first service flow that allows out-of-order transmission and / or the out-of-order transmission parameters allowed by the first service flow; The third information is used to indicate a first traffic identifier TID and / or a first user priority corresponding to the data unit in the first service flow; The fourth information is used to indicate the transmission direction of the first service flow.

2. The method according to claim 1, It is characterized in that The second information is related to the hole generated by the first business flow during the out-of-order transmission, and the hole corresponds to the target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

3. The method according to claim 2, It is characterized in that The second information is used to indicate one or more of the following out-of-order transmission parameters: the maximum size of a hole allowed; The maximum number of holes allowed in the first period; The minimum distance allowed between two adjacent holes; The maximum distance allowed between two adjacent holes; The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

4. The method according to any one of claims 1 to 3, It is characterized in that The first frame also includes fifth information, and the fifth information is used to indicate the in-order or out-of-order processing mode of the data units in the first service flow.

5. The method according to claim 4, It is characterized in that The fifth information is used to indicate one of the following: The data units in the first service flow are processed as data units of the same type; The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter; The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter; The data units in the first service flow are processed according to multiple types of data units; The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters; The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

6. The method according to claim 5, It is characterized in that The multiple types of data units satisfy one or more of the following: Corresponding to different latency requirements; Corresponding to different flow classification TCLAS elements; Corresponding to different data unit tags.

7. The method according to any one of claims 1 to 6, It is characterized in that The first frame also includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

8. The method according to any one of claims 1 to 7, It is characterized in that The first frame includes a first QoS feature element field, and the first QoS feature element field contains one or more of the first information, the second information, and the third information.

9. The method according to claim 8, It is characterized in that The first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

10. The method according to claim 8 or 9, It is characterized in that The first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

11. The method according to any one of claims 1 to 10, It is characterized in that If the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that allows or does not allow out-of-order transmission; The first user priority is a user priority for allowing or not allowing out-of-order transmission.

12. The method according to any one of claims 1 to 10, It is characterized in that If the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that does not allow out-of-order transmission; The first user priority is a user priority that does not allow out-of-order transmission.

13. The method according to any one of claims 1 to 12, It is characterized in that The first frame is a first request frame, and the method further includes: The first device receives a first response frame sent by the second device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following: The second device does not support the out-of-order transmission; The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

14. The method according to claim 13, It is characterized in that The method further comprises: The first device sends a second request frame to the second device, where the second request frame includes the out-of-order transmission parameters modified based on the modification suggestion.

15. The method according to claim 13, It is characterized in that The method further comprises: The first device negotiates with the second device whether to transmit in sequence or out of sequence; After the negotiation is successfully completed, the first device sends a second request frame to the second device, where the second request frame includes the negotiated out-of-order transmission parameters.

16. The method according to any one of claims 1 to 15, It is characterized in that The first frame is a first request frame, and the method further includes: The first device receives a first response frame sent by the second device, where the first response frame includes eighth information, where the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; The first device and / or the second device transmits the first service flow according to whether out-of-order transmission is allowed and / or the out-of-order transmission parameter.

17. The method according to claim 16, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, the transmission of the first service flow satisfies one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

18. The method according to claim 16 or 17, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

19. The method according to claim 16 or 17, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces or different PN sequences, the data units in the first service flow adopt replay detection based on PN windows; or, the data units in the first service flow adopt replay detection not based on PN windows; wherein the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

20. The method according to any one of claims 13 to 19, It is characterized in that The first request frame is an SCS request frame, and the first response frame is an SCS response frame.

21. The method according to any one of claims 1 to 20, Features: The first device is a non-access point station, and the second device is an access point; or, The first device is a non-access point multi-link device, and the second device is an access point multi-link device.

22. A wireless communication method, It is characterized in that include: The second device receives a first frame sent by the first device, where the first frame includes one or more of the following: First information, used to indicate whether out-of-order transmission of data units in the first service flow is allowed; second information, used to indicate the quality of service QoS characteristics of the first service flow that allows out-of-order transmission and / or the out-of-order transmission parameters allowed by the first service flow; The third information is used to indicate a first traffic identifier TID and / or a first user priority corresponding to the data unit in the first service flow; The fourth information is used to indicate the transmission direction of the first service flow.

23. The method according to claim 22, It is characterized in that The second information is related to the hole generated by the first business flow during the out-of-order transmission, and the hole corresponds to the target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

24. The method according to claim 23, It is characterized in that The second information is used to indicate one or more of the following out-of-order transmission parameters: the maximum size of a hole allowed; The maximum number of holes allowed in the first period; The minimum distance allowed between two adjacent holes; The maximum distance allowed between two adjacent holes; The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

25. The method according to any one of claims 22 to 24, It is characterized in that The first frame also includes fifth information, and the fifth information is used to indicate the in-order or out-of-order processing mode of the data units in the first service flow.

26. The method according to claim 25, It is characterized in that The fifth information is used to indicate one of the following: The data units in the first service flow are processed as data units of the same type; The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter; The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter; The data units in the first service flow are processed according to multiple types of data units; The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters; The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

27. The method according to claim 26, It is characterized in that The multiple types of data units satisfy one or more of the following: Corresponding to different latency requirements; Corresponding to different flow classification TCLAS elements; Corresponding to different data unit tags.

28. The method according to any one of claims 22 to 27, It is characterized in that The first frame also includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

29. The method according to any one of claims 22 to 28, It is characterized in that The first frame includes a first QoS feature element field, and the first QoS feature element field contains one or more of the first information, the second information, and the third information.

30. The method according to claim 29, It is characterized in that The first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

31. The method according to claim 29 or 30, It is characterized in that The first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

32. The method according to any one of claims 22 to 31, It is characterized in that If the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that allows or does not allow out-of-order transmission; The first user priority is a user priority for allowing or not allowing out-of-order transmission.

33. The method according to any one of claims 22 to 31, It is characterized in that If the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that does not allow out-of-order transmission; The first user priority is a user priority that does not allow out-of-order transmission.

34. The method according to any one of claims 22 to 33, It is characterized in that The first frame is a first request frame, and the method further includes: The second device sends a first response frame to the first device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following: The second device does not support the out-of-order transmission; The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

35. The method according to claim 34, It is characterized in that The method further comprises: The second device receives a second request frame sent by the first device, where the second request frame includes the out-of-order transmission parameters modified based on the modification suggestion.

36. The method according to claim 34, It is characterized in that The method further comprises: The second device negotiates with the first device for in-order or out-of-order transmission; After the negotiation is successfully completed, the second device receives a second request frame sent by the first device, wherein the second request frame includes a negotiation request frame. The out-of-order transmission parameters after the quotient.

37. The method according to any one of claims 22 to 36, It is characterized in that The first frame is a first request frame, and the method further includes: The second device sends a first response frame to the first device, where the first response frame includes eighth information, where the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; The second device and / or the first device transmits the first service flow according to whether out-of-order transmission is allowed and / or the out-of-order transmission parameter.

38. The method according to claim 37, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, the transmission of the first service flow satisfies one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

39. The method according to claim 37 or 38, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

40. The method according to claim 37 or 38, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces or different PN sequences, the data units in the first service flow adopt replay detection based on PN windows; or, the data units in the first service flow adopt replay detection not based on PN windows; wherein the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

41. The method according to any one of claims 34 to 40, It is characterized in that The first request frame is an SCS request frame, and the first response frame is an SCS response frame.

42. The method according to any one of claims 22 to 41, Features: The first device is a non-access point station, and the second device is an access point; or, The first device is a non-access point multi-link device, and the second device is an access point multi-link device.

43. A communication device, It is characterized in that The communication device is a first device, and the communication device includes: The first communication module is configured to send a first frame to the second device, where the first frame includes one or more of the following: The first information is used to indicate whether out-of-order transmission of data units in the first service flow is allowed; second information, used to indicate the quality of service QoS characteristics of the first service flow that allows out-of-order transmission and / or the out-of-order transmission parameters allowed by the first service flow; The third information is used to indicate a first traffic identifier TID and / or a first user priority corresponding to the data unit in the first service flow; The fourth information is used to indicate the transmission direction of the first service flow.

44. The communication device according to claim 43, It is characterized in that The second information is related to the hole generated by the first business flow during the out-of-order transmission, and the hole corresponds to the target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

45. The communication device according to claim 44, It is characterized in that The second information is used to indicate one or more of the following out-of-order transmission parameters: the maximum size of a hole allowed; The maximum number of holes allowed in the first period; The minimum distance allowed between two adjacent holes; The maximum distance allowed between two adjacent holes; The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

46. ​​A communication device according to any one of claims 43 to 45, It is characterized in that The first frame also includes fifth information, and the fifth information is used to indicate the in-order or out-of-order processing mode of the data units in the first service flow.

47. The communication device according to claim 46, It is characterized in that The fifth information is used to indicate one of the following: The data units in the first service flow are processed as data units of the same type; The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter; The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter; The data units in the first service flow are processed according to multiple types of data units; The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters; The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

48. The communication device according to claim 47, It is characterized in that The multiple types of data units satisfy one or more of the following: Corresponding to different latency requirements; Corresponding to different flow classification TCLAS elements; Corresponding to different data unit tags.

49. A communication device according to any one of claims 43 to 48, It is characterized in that The first frame also includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

50. The communication device according to any one of claims 43 to 49, It is characterized in that The first frame includes a first QoS feature element field, and the first QoS feature element field contains one or more of the first information, the second information, and the third information.

51. The communication device according to claim 50, It is characterized in that The first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

52. The communication device according to claim 50 or 51, It is characterized in that The first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

53. A communication device according to any one of claims 43 to 52, It is characterized in that If the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that allows or does not allow out-of-order transmission; The first user priority is a user priority for allowing or not allowing out-of-order transmission.

54. A communication device according to any one of claims 43 to 52, It is characterized in that If the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that does not allow out-of-order transmission; The first user priority is a user priority that does not allow out-of-order transmission.

55. A communication device according to any one of claims 43 to 54, It is characterized in that The first frame is a first request frame, and the communication device further includes: The first device receives a first response frame sent by the second device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following: The second device does not support the out-of-order transmission; The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

56. The communication device according to claim 55, It is characterized in that The communication device further comprises: The second communication module is used to send a second request frame to the second device, where the second request frame includes the out-of-order transmission parameters modified based on the modification suggestion.

57. The communication device according to claim 55, It is characterized in that The communication device further comprises: The third communication module is used to negotiate in-order or out-of-order transmission with the second device; after the negotiation is successfully completed, send a second request frame to the second device, where the second request frame includes the negotiated out-of-order transmission parameters.

58. A communication device according to any one of claims 43 to 57, It is characterized in that The first frame is a first request frame, and the communication device further includes: A fourth communication module is used to receive a first response frame sent by the second device, the first response frame includes eighth information, and the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; and transmit the first service flow according to whether out-of-order transmission is allowed and / or the out-of-order transmission parameters.

59. The communication device according to claim 58, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, the transmission of the first service flow satisfies one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

60. The communication device according to claim 58 or 59, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

61. The communication device according to claim 58 or 59, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces or different PN sequences, the data units in the first service flow adopt replay detection based on PN windows; or, the data units in the first service flow adopt replay detection not based on PN windows; wherein the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

62. A communication device according to any one of claims 55 to 61, It is characterized in that The first request frame is an SCS request frame, and the first response frame is an SCS response frame.

63. A communication device according to any one of claims 43 to 62, Features: The first device is a non-access point station, and the second device is an access point; or, The first device is a non-access point multi-link device, and the second device is an access point multi-link device.

64. A communication device, It is characterized in that The communication device is a second device, and the communication device includes: The first communication module is configured to receive a first frame sent by a first device, where the first frame includes one or more of the following: The first information is used to indicate whether out-of-order transmission of data units in the first service flow is allowed; second information, used to indicate the quality of service QoS characteristics of the first service flow that allows out-of-order transmission and / or the out-of-order transmission parameters allowed by the first service flow; The third information is used to indicate a first traffic identifier TID and / or a first user priority corresponding to the data unit in the first service flow; The fourth information is used to indicate the transmission direction of the first service flow.

65. The communication device according to claim 64, It is characterized in that The second information is related to the hole generated by the first business flow during the out-of-order transmission, and the hole corresponds to the target data unit in the first business flow. The target data unit is a data unit or multiple consecutive data units that are expected to be received but not received, and the sending order of the target data unit is before the received data unit in the first business flow.

66. The communication device according to claim 65, It is characterized in that The second information is used to indicate one or more of the following out-of-order transmission parameters: the maximum size of a hole allowed; The maximum number of holes allowed in the first period; The minimum distance allowed between two adjacent holes; The maximum distance allowed between two adjacent holes; The maximum target time interval allowed is the time interval between the time when the hole is generated and the time when the target data unit is expected to be received.

67. A communication device according to any one of claims 64 to 66, It is characterized in that The first frame also includes fifth information, and the fifth information is used to indicate the in-order or out-of-order processing mode of the data units in the first service flow.

68. The communication device according to claim 67, It is characterized in that The fifth information is used to indicate one of the following: The data units in the first service flow are processed as data units of the same type; The data units in the first service flow correspond to the same sequence number SN sequence, the same SN space or the same SN counter; The data units in the first service flow correspond to the same packet number PN sequence, the same PN space or the same PN counter; The data units in the first service flow are processed according to multiple types of data units; The data units in the first service flow correspond to multiple SN sequences, multiple SN spaces or multiple SN counters; The data units in the first service flow correspond to multiple PN sequences, multiple PN spaces or multiple PN counters.

69. The communication device according to claim 68, It is characterized in that The multiple types of data units satisfy one or more of the following: Corresponding to different latency requirements; Corresponding to different flow classification TCLAS elements; Corresponding to different data unit tags.

70. The communication device according to any one of claims 64 to 69, It is characterized in that The first frame also includes sixth information, where the sixth information is used to indicate whether data units of the same type in the first service flow are allowed to be transmitted out of order.

71. A communication device according to any one of claims 64 to 70, It is characterized in that The first frame includes a first QoS feature element field, and the first QoS feature element field contains one or more of the first information, the second information, and the third information.

72. The communication device according to claim 71, It is characterized in that The first frame includes a flow classification service SCS descriptor element field, and the first QoS feature element field is located in the SCS descriptor element field.

73. The communication device according to claim 71 or 72, It is characterized in that The first QoS feature element field includes a control information field, the first information and / or the third information is carried in the control information field, and the second information is carried in other fields of the first QoS feature element field except the control information field.

74. A communication device according to any one of claims 64 to 73, It is characterized in that If the first service flow is a service flow that allows out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that allows or does not allow out-of-order transmission; The first user priority is a user priority for allowing or not allowing out-of-order transmission.

75. A communication device according to any one of claims 64 to 74, It is characterized in that If the first service flow is a service flow that does not allow out-of-order transmission, one or more of the following is satisfied: The first TID is a TID that does not allow out-of-order transmission; The first user priority is a user priority that does not allow out-of-order transmission.

76. A communication device according to any one of claims 64 to 75, It is characterized in that The first frame is a first request frame, and the communication device further includes: The second communication module is configured to send a first response frame to the first device, where the first response frame includes seventh information, where the seventh information is used to indicate one or more of the following: The second device does not support the out-of-order transmission; The second device rejects the request corresponding to the first request frame, and the seventh information indicates a modification suggestion for the out-of-order transmission parameter.

77. The communication device according to claim 76, It is characterized in that The communication device further comprises: The third communication module is used to receive a second request frame sent by the first device, where the second request frame includes the out-of-order transmission parameters modified based on the modification suggestion.

78. The communication device according to claim 76, It is characterized in that The communication device further comprises: The fourth communication module is used to negotiate in-order or out-of-order transmission with the first device; after the negotiation is successfully completed, receive a second request frame sent by the first device, wherein the second request frame includes the negotiated out-of-order transmission parameters.

79. A communication device according to any one of claims 64 to 78, It is characterized in that The first frame is a first request frame, and the communication device further includes: A fifth communication module is used to send a first response frame to the first device, wherein the first response frame includes eighth information, and the eighth information is used to indicate that the request corresponding to the first request frame is successfully accepted; and the first service flow is transmitted according to whether out-of-order transmission is allowed and / or the out-of-order transmission parameters.

80. The communication device according to claim 79, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the first TID is a TID that allows out-of-order transmission or the first user priority is a user priority that allows out-of-order transmission, the transmission of the first service flow satisfies one or more requirements indicated by the out-of-order transmission parameter, or the first service flow needs to be transmitted based on one or more requirements indicated by the out-of-order transmission parameter; wherein the first request frame indicates that data units of the first service flow are allowed to be transmitted out of order.

81. The communication device according to claim 79 or 80, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to the same SN space, the same SN sequence, the same PN space or the same PN sequence, the data units in the first service flow adopt PN window-based replay detection; wherein, the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

82. The communication device according to claim 79 or 80, It is characterized in that When the request corresponding to the first request frame is successfully accepted, if the data units in the first service flow correspond to different SN spaces, different SN sequences, different PN spaces or different PN sequences, the data units in the first service flow adopt replay detection based on PN windows; or, the data units in the first service flow adopt replay detection not based on PN windows; wherein the first request frame indicates that the data units of the first service flow are allowed to be transmitted out of order.

83. A communication device according to any one of claims 79 to 82, It is characterized in that The first request frame is an SCS request frame, and the first response frame is an SCS response frame.

84. A communication device according to any one of claims 64 to 83, Features: The first device is a non-access point station, and the second device is an access point; or, The first device is a non-access point multi-link device, and the second device is an access point multi-link device.

85. A communication device, It is 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 described in any one of claims 1-21 or 22-42.

86. A device, It is characterized in that It comprises a processor, which is used to call a program from a memory so that the device executes the method as described in any one of claims 1-21 or 22-42.

87. A chip, It is 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 the method as described in any one of claims 1-21 or 22-42.

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

89. A computer program product, It is characterized in that A program is included, which causes a computer to execute the method as described in any one of claims 1-21 or 22-42.

90. A computer program, It is characterized in that The computer program causes a computer to execute the method according to any one of claims 1-21 or 22-42.

Images