Buffer status report sending method and apparatus, buffer status report receiving method and apparatus, and medium

Abstract

The present application relates to the technical field of communications, and discloses a buffer status report sending method and apparatus, a buffer status report receiving method and apparatus, and a medium. The buffer status report sending method comprises: sending a first frame, the first frame being used for indicating the size and delay requirements of at least one service data unit within a buffer. A first frame indicates the size and delay requirements of at least one service data unit within a buffer, so that when reporting a buffer status, a station can also simultaneously report the delay requirements corresponding to data within the buffer.

Description

Method, device and medium for sending buffer status report TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology, in particular to a method for sending a buffer status report, a method for receiving a buffer status report, an apparatus and a medium. BACKGROUND

[0002] In related technologies, it is proposed that, in the process of data transmission, a station needs to complete data transmission within a certain time delay.

[0003] SUMMARY

[0004] Embodiments of the present application provide a method for sending a buffer status report, a method for receiving a buffer status report, an apparatus and a medium. The technical solutions are as follows:

[0005] According to an aspect of an embodiment of the present application, a method for sending a buffer status report is provided, and the method comprises:

[0006] sending a first frame, wherein the first frame is used to indicate the size of at least one service data unit in a buffer and a time delay requirement.

[0007] According to another aspect of an embodiment of the present application, a method for receiving a buffer status report is provided, and the method comprises:

[0008] receiving a first frame, wherein the first frame is used to indicate the size of at least one service data unit in a buffer and a time delay requirement.

[0009] According to another aspect of an embodiment of the present application, a sending apparatus for a buffer status report is provided, and the apparatus comprises:

[0010] a sending module, configured to send a first frame, wherein the first frame is used to indicate the size of at least one service data unit in a buffer and a time delay requirement.

[0011] According to another aspect of an embodiment of the present application, a receiving apparatus for a buffer status report is provided, and the apparatus comprises:

[0012] a receiving module, configured to receive a first frame, wherein the first frame is used to indicate the size of at least one service data unit in a buffer and a time delay requirement.

[0013] According to another aspect of an embodiment of the present application, a communication device is provided, and the communication device comprises:

[0014] a processor;

[0015] a transceiver connected to the processor;

[0016] a memory for storing executable instructions of the processor;

[0017] The processor is configured to load and execute executable instructions to implement the sending method and / or receiving method of the buffer status report according to the various aspects described above.

[0018] According to another aspect of the embodiments of the present application, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program loaded and executed by a communication device to implement the sending method and / or receiving method of the buffer status report according to the various aspects described above.

[0019] According to another aspect of the embodiments of the present application, a computer program product or computer program is provided, and the computer program product or computer program includes computer instructions stored in a computer readable storage medium; the communication device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to implement the sending method and / or receiving method of the buffer status report according to the various aspects described above.

[0020] The technical solutions provided by the embodiments of the present application can include the following beneficial effects:

[0021] By sending the first frame carrying the buffer status report to the access point, and indicating the size and delay requirement of at least one service data unit in the buffer through the first frame, the station can report the delay requirement corresponding to the data in the buffer when reporting the buffer status, so that the access point can reasonably allocate channel resources according to the received delay requirement, so that the data transmission can meet the corresponding delay requirement. BRIEF DESCRIPTION OF DRAWINGS

[0022] FIG. 1 shows a schematic diagram of a communication system according to an embodiment of the present application;

[0023] FIG. 2 shows a flowchart of a sending method of a buffer status report according to an embodiment of the present application;

[0024] FIG. 3 shows a flowchart of a receiving method of a buffer status report according to an embodiment of the present application;

[0025] FIG. 4 shows an effect comparison diagram according to an embodiment of the present application;

[0026] FIG. 5 shows a diagram of receiving reordering according to an embodiment of the present application;

[0027] FIG. 6 shows a diagram of receiving reordering according to an embodiment of the present application;

[0028] FIG. 7 shows a diagram of receiving reordering according to an embodiment of the present application;

[0029] FIG. 8 shows a flow chart of a method for transmitting and receiving a buffer status report according to an embodiment of the present application;

[0030] FIG. 9 shows a block diagram of a device for transmitting a buffer status report according to an embodiment of the present application;

[0031] FIG. 10 shows a block diagram of a device for receiving a buffer status report according to an embodiment of the present application;

[0032] FIG. 11 shows a block diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0033] To make the objects, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings. The exemplary embodiments will be described in detail herein with reference to the drawings. The following description relates to the drawings, in which like numerals refer to like elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims. All other embodiments obtained by those of ordinary skill in the art without departing from the spirit of the present application are within the scope of the present application.

[0034] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in this disclosure and the appended claims, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that, although the terms first, second, third, etc. can be used herein to describe various information, but those terms are not intended to denote a temporal or chronological order. Rather, those terms are used merely as labels to distinguish different specific embodiments from each other. For example, a first item could be termed a second item, and, similarly, a second item could be termed a first item without departing from the scope of the present disclosure. As used herein, the term "if' can be construed to mean "when" or "in response to determining" depending on the context.

[0035] First, the related art involved in the embodiments of the present application is introduced:

[0036] QoS NULL Frame format:

[0037] Table 1

[0038] wherein RA denotes Reciver Address (RA) and TA denotes Transmitter Address (TA).

[0039] Quality of Service Data Frame (QoS DATA Frame) format:

[0040] Table 2

[0041] Sequence Control Field (Sequence Control Field):

[0042] Table 3

[0043] Quality of Service Control Field (QoS Control Field):

[0044] Table 4

[0045] wherein TID denotes Traffic Identifier (TID), A-MSDU Present denotes Aggregate MAC Service Data Unit (A-MSDU) present, and TXOP denotes Transmission Opportunity (TXOP).

[0046] High Throughput (HT) Control Field (HT Control Field) format:

[0047] Table 5

[0048] wherein VHT denotes Very High Throughput (VHT), HE denotes High Effiency (HE), AC denotes Access Category (AC), RDG denotes Reverse Direction Grant (RDG), and PPDU denotes PHY Protocol Data Unit (PPDU).

[0049] FIG. 1 is a schematic diagram of a communication system 10 according to an example embodiment of the present application. The communication system 10 can include terminal-to-terminal, terminal-to-network device, or access point (AP) to station (STA) communication, which is not limited in the present application. The communication system 10 includes an AP 110 and a STA 120 as an example in the present application.

[0050] In some scenarios, the AP can also be referred to as an AP STA, that is, in a certain sense, the AP is also a kind of STA. In some scenarios, the STA can also be referred to as a non-AP STA.

[0051] In some embodiments, the STA can include an AP STA and a non-AP STA. The communication in the communication system can be between the AP and the non-AP STA, between the non-AP STAs, or between the STA and a peer STA, where the peer STA can refer to a device that communicates with the STA, for example, the peer STA can be an AP or a non-AP STA. As an example, there are two communication scenarios between the STA and the AP: uplink communication scenario and downlink communication scenario. The uplink communication refers to the STA sending a signal to the AP, and the downlink communication refers to the AP sending a signal to the STA. The AP acts as a bridge connecting the wired network and the wireless network, and mainly functions to connect various wireless network clients together and then access the wireless network to the Ethernet. The AP device can be a terminal device (such as a mobile phone) or a network device (such as a router) with a wireless fidelity (WiFi) chip.

[0052] In some embodiments, different communication devices can use different DRUs when transmitting wireless signals.

[0053] It should be understood that the role of the STA in the communication system is not absolute, for example, in some scenarios, when a mobile phone connects to a router, the mobile phone is a non-AP STA, and when the mobile phone acts as a hotspot for other mobile phones, the mobile phone plays the role of an AP. The AP and the non-AP STA can be devices applied in the Internet of Vehicles, Internet of Things (IoT) nodes, sensors, smart cameras, smart remote controllers, smart water meters, smart electricity meters, and sensors in smart cities.

[0054] In some embodiments, the non-AP STA can support, but is not limited to, the 802.11bf standard. The non-AP STA can also support various current and future 802.11 family of Wireless Local Area Network (WLAN) standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. In some embodiments, the AP can be a device that supports the 802.11bf standard. The AP can also be a device that supports various current and future 802.11 family of WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0055] In embodiments of the present application, the STA can be a mobile phone, a tablet computer, a computer, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a communication device in industrial control, a set-top box, a communication device in self-driving, a vehicle-mounted communication device, a communication device in telemedicine, a communication device in smart grid, a communication device in transportation safety, a communication device in smart city, or a communication device in smart home, a wireless communication chip, etc. that supports WLAN / Wi-Fi technology. The WLAN technology can support frequency bands including but not limited to: low frequency bands (2.4 GHz, 5 GHz, 6 GHz), high frequency bands (60 GHz).

[0056] There is one or more links between a station and an access point. In some embodiments, the station and the access point support multi-band communication, for example, simultaneously communicating on 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz frequency bands, or simultaneously communicating on different channels of the same frequency band (or different frequency bands), to improve the communication throughput and / or reliability between devices. Such devices are commonly referred to as multi-band devices, and can also be referred to as Multi-Link Devices (MLDs), and sometimes as multi-link entities or multi-band entities. A multi-link device can be an access point device or a station device. If the multi-link device is an access point device, the multi-link device contains one or more APs; if the multi-link device is a station device, the multi-link device contains one or more non-AP STAs. A multi-link device containing one or more APs can also be referred to as an AP, and a multi-link device containing one or more non-AP STAs can also be referred to as a Non-AP, which can be referred to as a STA in embodiments of the present application.

[0057] In the embodiments of the present application, the APs can include a plurality of APs, the Non-APs include a plurality of STAs, a plurality of links can be formed between the plurality of APs in the APs and the plurality of STAs in the Non-APs, and data communication can be performed between the APs in the APs and the corresponding STAs in the Non-APs through the corresponding links.

[0058] The AP is a device deployed in a wireless local area network to provide wireless communication functions for the STAs. The STA can include a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent or a user device. Alternatively, the STA can also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and the embodiments of the present application are not limited thereto.

[0059] In the embodiments of the present application, the STA and the AP both support the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, but are not limited to the IEEE 802.11 standard.

[0060] In the related art, in the process of data communication between the AP and the STA, the data sender device sends a buffer status report (BSR) to the data receiver device to inform the data receiver device how much data is waiting to be sent in the buffer. In the embodiments of the present application, the data sender device is taken as an example to illustrate the data receiver device as an AP.

[0061] In order to meet the low-latency data transmission requirement, the related art proposes that in the process of data transmission, the station needs to complete the transmission of data within a certain time delay. However, different data has different time delay requirements. Therefore, how to make the access point know the time delay requirement corresponding to the data to be transmitted by the station in time, so that the access point can more reasonably allocate channel resources, is a problem to be solved at present.

[0062] Based on the above defects, the embodiment of the present application proposes a sending method of buffer status report, which sends the delay requirement to the data receiving side device, so that the data receiving side device can arrange the channel resources reasonably based on the received delay requirement. FIG. 2 shows a flowchart of the sending method of buffer status report provided by an exemplary embodiment of the present application. The method is executed by a data sending side device, which can be an AP or a STA. The present application takes the data sending side device as an STA for example. The method comprises the following steps.

[0063] Step 220: sending a first frame, the first frame being used to indicate the size of at least one service data unit in the buffer and the delay requirement.

[0064] The first frame is sent by the data sending side device to the data receiving side device.

[0065] In some embodiments, the data sending side device sends the first frame to the data receiving side device, which is used to report the low latency buffer status report (LL BSR) to the data receiving side device through the first frame. The LL BSR includes the size of at least one service data unit in the buffer and the delay requirement. In different embodiments, the LL BSR can also be referred to as BSR, or be referred to as other names.

[0066] In some embodiments, the first frame comprises:

[0067] a first field used to indicate the size of at least one service data unit in the buffer;

[0068] a second field used to indicate the delay requirement.

[0069] The first field can also be understood as a first type field or a first type field, which refers to a type field used to indicate the size of at least one service data unit in the buffer.

[0070] In some embodiments, the service data unit is MSDU or A-MSDU.

[0071] In some embodiments, the size of at least one service data unit in the buffer is represented by at least one of the following:

[0072] the number of bits occupied by at least one service data unit;

[0073] the channel resources required by at least one service data unit;

[0074] the number of at least one service data unit.

[0075] Specifically, the first field comprises at least one of the following fields:

[0076] a field for indicating the average number of bits of the at least one service data unit;

[0077] a field for indicating the number of the at least one service data unit;

[0078] a field for indicating the size proportion of the sum of the number of bits of the at least one service data unit to the total number of bits of the buffer;

[0079] a field for indicating the queue size of the at least one service data unit;

[0080] a field for indicating the scaling factor of the at least one service data unit;

[0081] a field for indicating the TXOP duration required by the at least one service data unit;

[0082] a field for indicating the bandwidth required by the at least one service data unit;

[0083] a field for indicating the modulation and coding scheme required by the at least one service data unit.

[0084] For example, the size of the at least one service data unit in the buffer can be calculated by the average number of bits of the at least one service data unit and the number of the at least one service data unit indicated in the first field. For example, if the average number of bits of the at least one service data unit is 5 bits and the number of the at least one service data unit is 3, then the size of the service data unit occupying 15 bits in the buffer can be calculated.

[0085] For example, the size of the at least one service data unit in the buffer can be calculated by the size proportion of the sum of the number of bits of the at least one service data unit to the total number of bits of the buffer indicated in the first field. For example, if the sum of the number of bits of the at least one service data unit is 15 bits and the total number of bits of the buffer is 60 bits, then the size of the buffer occupied by the at least one service data unit is 15 / 60 = 1 / 4.

[0086] Optionally, the first field further comprises a field for indicating the sum of the number of bits of the at least one service data unit. Or, the sum of the number of bits of the at least one service data unit is calculated in the case that the average number of bits of the at least one service data unit and the number of the at least one service data unit are indicated in the first field.

[0087] Optionally, the first field further comprises a field for indicating the total number of bits of the buffer.

[0088] For example, the size of the at least one service data unit in the buffer can be calculated by the sequence size of the at least one service data unit and the scaling factor of the at least one service data unit indicated in the first field. The scaling factor is used to indicate the data unit of the data to be transmitted, such as MB; the sequence size is used to indicate the number of data units of the data to be transmitted, such as 8. In the case that the sequence size of the at least one service data unit is 8 and the scaling factor of the at least one service data unit is MB, the size of the at least one service data unit in the buffer can be calculated as 8 MB.

[0089] For example, the size of the at least one service data unit in the buffer can be calculated by the TXOP duration required by the at least one service data unit, the bandwidth required by the at least one service data unit, and the MCS required by the at least one service data unit indicated in the first field. For example, the size of the at least one service data unit in the buffer can be calculated by the product of the TXOP duration required by the at least one service data unit, the bandwidth required by the at least one service data unit, and the MCS required by the at least one service data unit indicated in the first field.

[0090] Optionally, any of the subfields in the first field can be used independently or in any combination. For example, the TXOP duration required by the at least one service data unit and the bandwidth required by the at least one service data unit can be indicated by one subfield. For example, the first field is used to indicate the TXOP duration required by the at least one service data unit under a 20 MHz bandwidth.

[0091] The second field can also be understood as a second type of field or a second type of field, which refers to a type of field for indicating a delay requirement.

[0092] In some embodiments, the second field is used to explicitly indicate the delay requirement corresponding to each service data unit. For example, the second field directly indicates the expiration time corresponding to each service data unit.

[0093] In some embodiments, the second field is used to implicitly indicate the delay requirement corresponding to each service data unit. For example, the second field is used to indicate the earliest expiration time and / or the latest expiration time corresponding to the at least one service data unit.

[0094] In some embodiments, the second field comprises at least one of the following fields:

[0095] a field for indicating the expiration time corresponding to each service data unit in the at least one service data unit;

[0096] a field for indicating an earliest expiration time corresponding to the at least one service data unit;

[0097] a field for indicating a latest expiration time corresponding to the at least one service data unit;

[0098] a field for indicating an offset value of the latest expiration time relative to the earliest expiration time;

[0099] a field for indicating an offset value of the earliest expiration time relative to the latest expiration time;

[0100] a field for indicating a latest time of channel resource required by the at least one service data unit.

[0101] In some embodiments, the field for indicating a latest time of channel resource required by the at least one service data unit comprises a field for indicating a latest time for the at least one service data unit to start channel resource allocation, and / or a field for indicating a latest time for the at least one service data unit to complete channel resource allocation.

[0102] In some embodiments, the delay requirement is characterized by an absolute time, or the delay requirement is characterized by an offset value relative to a transmission time or a reception time.

[0103] In some embodiments, the first frame is a new frame type defined in the embodiments of the present application.

[0104] In some embodiments, the first frame is a Quality of Service NULL frame (QoS NULL Frame) or a Quality of Service DATA frame (QoS DATA Frame) or a Block Ack (BA) frame.

[0105] Optionally, the first field and the second field are carried by at least one of a Sequence Control Field, a QoS Control Field and an HT Control Field in the QoS NULL Frame.

[0106] Optionally, the first field and the second field are carried by at least one of a Sequence Control Field, a QoS Control Field and an HT Control Field in the QoS DATA Frame.

[0107] Optionally, the BA frame is regarded as the first frame when the value of the target reserved bit in the BA frame is the first value, and the BA frame is regarded as a normal frame when the value of the target reserved bit in the BA frame is the second value. For example, the value of the target reserved bit in the BA frame is set to 0 to indicate that the BA frame is regarded as the first frame, and the value of the target reserved bit in the BA frame is set to 1 to indicate that the BA frame is regarded as a normal frame. Alternatively, the value of the target reserved bit in the BA frame is set to 1 to indicate that the BA frame is regarded as the first frame, and the value of the target reserved bit in the BA frame is set to 0 to indicate that the BA frame is regarded as a normal frame.

[0108] In some embodiments, the first frame is a Quality of Service Null Frame (QoS NULL Frame), and the first field and the second field are carried in at least one of a High Throughput (HT) Control field, an Ultra High Reliability (UHR) Control field, and an Extended HT Control field of the Quality of Service Null Frame (QoS NULL Frame).

[0109] In some embodiments, the first frame is a Quality of Service Data Frame (QoS DATA Frame), and the first field and the second field are carried in at least one of a High Throughput (HT) Control field, an Ultra High Reliability (UHR) Control field, and an Extended HT Control field of the Quality of Service Data Frame (QoS DATA Frame).

[0110] In some embodiments, the High Throughput (HT) Control field includes an A-Control field, and the A-Control field is used to carry the first field and the second field. For example, a new A-Control field is defined in the High Throughput (HT) Control field. The first field and the second field are carried using the A-Control field. Specifically, the first field and the second field are carried using control information in the A-Control field.

[0111] In some embodiments, all bits of the High Throughput (HT) Control field are used to carry the first field and the second field. For example, the High Throughput (HT) Control field is redefined. The first field and the second field are carried using all bits in the High Throughput (HT) Control field.

[0112] In some embodiments, a UHR Control Field is used to carry the first field and the second field. For example, a new UHR Control Field is defined. The UHR Control Field is used to replace the HT Control Field. In this case, the length of the UHR Control Field can be redefined.

[0113] In some embodiments, the HT Control Field and the Extended HT Control Field are used to carry the first field and the second field. That is, the HT Control Field and the Extended HT Control Field are jointly used to carry the first field and the second field. For example, the HT Control Field is kept unchanged, and a new Extended HT Control Field is defined. The HT Control Field and the Extended HT Control Field are jointly used to carry the first field and the second field.

[0114] In summary, the method provided by the embodiments allows the station to report the delay requirement corresponding to the data in the buffer when reporting the buffer status, so that the AP can allocate the channel resources according to the received delay requirement, and the data transmission can meet the corresponding delay requirement.

[0115] FIG. 3 shows a flowchart of a method for receiving a buffer status report according to an example embodiment of the present application. The method is performed by a data receiver device, which can be an AP or a STA. The method is described below by taking the data receiver device as an AP.

[0116] Step 420: receiving a first frame, the first frame being used to indicate the size and delay requirement of at least one service data unit in the buffer.

[0117] The first frame is sent by a data sender device to the data receiver device.

[0118] In some embodiments, the data sender device sends the first frame to the data receiver device, so as to report the low-delay buffer status report to the data receiver device through the first frame.

[0119] In some embodiments, the first frame comprises:

[0120] a first field for indicating a size of the at least one service data unit in the buffer;

[0121] a second field for indicating a latency requirement.

[0122] The first field, which can also be understood as a first type of field or a first type field, refers to a type of field for indicating a size of the at least one service data unit in the buffer.

[0123] In some embodiments, the service data unit is an MSDU or an A-MSDU.

[0124] In some embodiments, the size of the at least one service data unit in the buffer is represented by at least one of:

[0125] a number of bits occupied by the at least one service data unit;

[0126] a channel resource required by the at least one service data unit;

[0127] a number of the at least one service data unit.

[0128] In particular, the first field comprises at least one of the following fields:

[0129] a field for indicating an average number of bits of the at least one service data unit;

[0130] a field for indicating a number of the at least one service data unit;

[0131] a field for indicating a size ratio of a sum of a number of bits of the at least one service data unit to a total number of bits of the buffer;

[0132] a field for indicating a queue size of the at least one service data unit;

[0133] a field for indicating a scaling factor of the at least one service data unit;

[0134] a field for indicating a TXOP duration required by the at least one service data unit;

[0135] a field for indicating a bandwidth required by the at least one service data unit;

[0136] a field for indicating a MCS required by the at least one service data unit.

[0137] For example, the size of the at least one service data unit in the buffer can be calculated by the average bit number of the at least one service data unit and the number of the at least one service data unit indicated in the first field. For example, if the average bit number of the at least one service data unit is 5 bits and the number of the at least one service data unit is 3, then the size of the service data unit occupying 15 bits in the buffer can be calculated.

[0138] For example, the size of the at least one service data unit in the buffer can be calculated by the size ratio of the sum of the bit number of the at least one service data unit to the total bit number of the buffer indicated in the first field. For example, if the sum of the bit number of the at least one service data unit is 15 bits and the total bit number of the buffer is 60 bits, then the size of the buffer occupied by the at least one service data unit is 15 / 60 = 1 / 4.

[0139] Optionally, the first field further comprises a field for indicating the sum of the bit number of the at least one service data unit. Or, in the case that the average bit number of the at least one service data unit and the number of the at least one service data unit are indicated in the first field, the sum of the bit number of the at least one service data unit can be calculated.

[0140] Optionally, the first field further comprises a field for indicating the total bit number of the buffer.

[0141] For example, the size of the at least one service data unit in the buffer can be calculated by the sequence size of the at least one service data unit and the scaling factor of the at least one service data unit indicated in the first field. The scaling factor is used to indicate the data unit of the data to be sent, such as MB; and the sequence size is used to indicate the number of the data to be sent according to the data unit, such as 8. If the sequence size of the at least one service data unit is 8 and the scaling factor of the at least one service data unit is MB, then the size of the at least one service data unit in the buffer is 8 MB.

[0142] For example, the size of the at least one service data unit in the buffer can be calculated by the TXOP duration required by the at least one service data unit, the bandwidth required by the at least one service data unit, and the MCS required by the at least one service data unit indicated in the first field. For example, the size of the at least one service data unit in the buffer can be calculated by the product of the bit rate indicated by the TXOP duration required by the at least one service data unit, the bandwidth required by the at least one service data unit, and the MCS required by the at least one service data unit.

[0143] Optionally, any of the subfields in the first field can be used independently or in any combination. For example, a subfield can be used to indicate both the TXOP duration required for the at least one service data unit and the bandwidth required for the at least one service data unit. For example, the first field includes a subfield for indicating the TXOP duration required for the at least one service data unit at 20MHz bandwidth.

[0144] The second field, which can also be understood as a second type of field or a second type of field, refers to a type of field used to indicate a latency requirement.

[0145] In some embodiments, the second field is used to explicitly indicate the latency requirement corresponding to each service data unit. For example, the second field directly indicates the expiration time corresponding to each service data unit.

[0146] In some embodiments, the second field is used to implicitly indicate the latency requirement corresponding to each service data unit. For example, the second field is used to indicate the earliest expiration time and / or the latest expiration time corresponding to the at least one service data unit.

[0147] In some embodiments, the second field includes at least one of the following fields:

[0148] a field for indicating the expiration time corresponding to each service data unit in the at least one service data unit;

[0149] a field for indicating the earliest expiration time corresponding to the at least one service data unit;

[0150] a field for indicating the latest expiration time corresponding to the at least one service data unit;

[0151] a field for indicating the offset value of the latest expiration time relative to the earliest expiration time;

[0152] a field for indicating the offset value of the earliest expiration time relative to the latest expiration time;

[0153] a field for indicating the latest time of the channel resource required for the at least one service data unit.

[0154] In some embodiments, the field for indicating the latest time of the channel resource required for the at least one service data unit includes a field for indicating the latest time for the at least one service data unit to start channel resource allocation and / or a field for indicating the latest time for the at least one service data unit to complete channel resource allocation.

[0155] In some embodiments, the latency requirement is characterized by an absolute time, or the latency requirement is characterized by an offset value relative to the transmission time or the reception time.

[0156] In some embodiments, the first frame is a newly defined frame type in the embodiments of the present application.

[0157] In some embodiments, the first frame is a QoS NULL Frame or a QoS DATA Frame or a BA frame.

[0158] Optionally, the first field and the second field are carried in at least one of a Sequence Control Field, a QoS Control Field and an HT Control Field in the QoS NULL Frame.

[0159] Optionally, the first field and the second field are carried in at least one of a Sequence Control Field, a QoS Control Field and an HT Control Field in the QoS DATA Frame.

[0160] Optionally, the BA frame is taken as the first frame when a value of a target reserved bit in the BA frame is a first value, and the BA frame is taken as a normal frame when the value of the target reserved bit in the BA frame is a second value. For example, the BA frame is taken as the first frame by setting the value of the target reserved bit in the BA frame to 0, and the BA frame is taken as the normal frame by setting the value of the target reserved bit in the BA frame to 1. Alternatively, the BA frame is taken as the first frame by setting the value of the target reserved bit in the BA frame to 1, and the BA frame is taken as the normal frame by setting the value of the target reserved bit in the BA frame to 0.

[0161] In some embodiments, the first frame is a QoS NULL Frame, and the first field and the second field are carried in at least one of an HT Control Field, a UHR Control Field and an Extended HT Control Field in the QoS NULL Frame.

[0162] In some embodiments, the first frame is a Quality of Service (QoS) DATA frame, and the first field and the second field are carried in at least one of a HT Control field, a UHR Control field, and an Extended HT Control field of the QoS DATA frame.

[0163] In some embodiments, the HT Control field includes an A-Control field for carrying the first field and the second field. For example, a new A-Control field is defined in the HT Control field. The first field and the second field are carried using the A-Control field. In particular, the first field and the second field are carried using control information in the A-Control field.

[0164] In some embodiments, all bits of the HT Control field are used to carry the first field and the second field. For example, the HT Control field is redefined. The first field and the second field are carried using all bits in the HT Control field.

[0165] In some embodiments, the UHR Control field is used to carry the first field and the second field. For example, a new UHR Control field is defined. The UHR Control field is used instead of the HT Control field. In some embodiments, the length of the UHR Control field can be redefined.

[0166] In some embodiments, the HT Control Field and the Extended HT Control Field are used to carry the first field and the second field. That is, the HT Control Field and the Extended HT Control Field are jointly used to carry the first field and the second field. For example, the HT Control Field is kept unchanged, and a new Extended HT Control Field is defined. The first field and the second field are jointly carried by using the HT Control Field and the Extended HT Control Field.

[0167] In summary, the method provided by the embodiments enables the access point to allocate channel resources according to the received delay requirement, so that the data transmission can meet the corresponding delay requirement.

[0168] For example, as shown in FIG. 4, the embodiments of the present application give an effect comparison between the station sending a conventional BSR and the station sending the LL BSR provided by the embodiments of the present application.

[0169] For example, as shown in FIG. 4(a), when the station sends a conventional BSR, the access point cannot learn the delay information of the data to be sent by the station in time. After receiving the Trigger Frame, the access point cannot refer to the related data delay information when allocating channel resources, which may result in that part of the data cannot be transmitted before the expiration time. For example, the PPDU1 and the PPDU4 with delay requirement cannot be transmitted before the expiration time.

[0170] For example, as shown in FIG. 4(b), when the station sends the LL BSR provided by the embodiments of the present application, the access point can preferentially allocate more channel resources to the station with delay requirement after receiving the TF, so that the station with delay requirement can complete the data transmission before the expiration time. For example, the channel resources are preferentially allocated to the PPDU1 and the PPDU4 with delay requirement. After the transmission of the PPDU1 and the PPDU4 is completed, the channel resources are allocated to the PPDU2 and the PPDU3 without delay requirement.

[0171] Based on this, the sending method / receiving method of the buffer status report provided by the embodiments of the present application can effectively ensure that the data is transmitted before the expiration time.

[0172] In the optional embodiment based on FIG. 2 or FIG. 3, when the field for indicating the sequence size in the first field is carried in the QoS Control Field in the QoS NULL Frame or the QoS DATA Frame, the number of bits corresponding to the field for indicating the sequence size in the QoS Control Field can be insufficient. That is, the requirement of accurately indicating the sequence size of the at least one service data unit cannot be met by using only the field for indicating the sequence size in the QoS Control Field.

[0173] Based on this, the embodiment of the present application further proposes that the first frame further comprises: a sixth field for extending the indication of the sequence size of the buffer.

[0174] The sixth field can also be understood as a sixth type field or a sixth type field, which refers to a type field for extending the indication of the sequence size of the buffer.

[0175] In some embodiments, the sixth field and the field for indicating the sequence size in the first field jointly indicate the sequence size of the buffer.

[0176] By supplementing the sixth field in the first frame, when the field for indicating the sequence size in the first field is carried in the first frame, the problem that the sequence size of the at least one service data unit cannot be accurately indicated due to the insufficient number of bits corresponding to the field for indicating the sequence size in the first field can be avoided.

[0177] In the optional embodiment based on FIG. 2 or FIG. 3, when the field for indicating the TXOP duration required by the at least one service data unit in the first field is carried in the QoS Control Field in the QoS NULL Frame or the QoS DATA Frame, the number of bits corresponding to the field for indicating the TXOP duration required by the at least one service data unit in the QoS Control Field can be insufficient. That is, the requirement of accurately indicating the TXOP duration required by the at least one service data unit cannot be met by using only the field for indicating the TXOP duration required by the at least one service data unit in the QoS Control Field.

[0178] Based on this, the embodiment of the present application further proposes that the first frame further comprises: a seventh field for extending the indication of the TXOP duration required by the at least one service data unit.

[0179] The seventh field can also be understood as a seventh type field or a seventh type of field, which refers to a type field used to extend the TXOP duration required by at least one service data unit.

[0180] In some embodiments, the seventh field is jointly indicated with the field in the first field described above for indicating the TXOP duration required by at least one service data unit.

[0181] By supplementing the seventh field in the first frame, when the field in the first field for indicating the TXOP duration required by at least one service data unit is carried in the first frame, the problem of being unable to accurately indicate the TXOP duration required by at least one service data unit due to insufficient number of bits corresponding to the field in the first field for indicating the TXOP duration required by at least one service data unit can be avoided.

[0182] In the optional embodiments based on FIG. 2 or FIG. 3, when the data sender device reports the size of the buffer and the delay requirement of at least one service data unit in the buffer to the data receiver device, the identification corresponding to the at least one service data unit in the buffer can also be sent at the same time.

[0183] Specifically, the first frame further includes a third field for indicating the identification corresponding to the at least one service data unit.

[0184] The third field can also be understood as a third type field or a third type of field, which refers to a type field used to indicate the identification corresponding to the at least one service data unit.

[0185] In some embodiments, the identification corresponding to the at least one service data unit includes at least one of an AC, a TID, and a Stream Classification Service Identifier (SCSID).

[0186] In some embodiments, the identification corresponding to the at least one service data unit is also used to indicate the AC or TID or SCSID to which the buffer belongs.

[0187] In some embodiments, the identification corresponding to the at least one service data unit is also used to indicate the AC or TID or SCSID to which the at least one service data unit in the buffer belongs.

[0188] In some embodiments, the third field includes at least one of the following: an AC field; a TID field; an SCSID field; a field for indicating the number of identifications; a partial SCSID field; and a concatenation of the TID field and the partial SCSID field is a complete SCSID.

[0189] In some embodiments, the first frame is a QoS NULL Frame, and the third field is carried in at least one of a QoS Control Field, an HT Control Field, an UHR Control Field, and an Extended HT Control Field of the QoS NULL Frame.

[0190] In some embodiments, the first frame is a QoS DATA Frame, and the third field is carried in at least one of a QoS Control Field, an HT Control Field, an UHR Control Field, and an Extended HT Control Field of the QoS DATA Frame.

[0191] In some embodiments, when the TID field and the partial SCSID field are included in the third field at the same time, the TID field and the partial SCSID field are carried in different fields respectively. For example, the TID field is carried in a QoS Control Field, and the partial SCSID field is carried in at least one of an HT Control Field, an UHR Control Field, and an Extended HT Control Field. This is only an example, and other possible carrying manners are not excluded.

[0192] Optionally, the first frame is a QoS NULL Frame, the TID field is carried in a QoS Control Field of the QoS NULL Frame, and the partial SCSID field is carried in at least one of an HT Control Field, an UHR Control Field, and an Extended HT Control Field of the QoS NULL Frame.

[0193] Optionally, the first frame is a quality of service data frame (QoS DATA Frame), the TID field is carried in a quality of service control field (QoS Control Field) of the quality of service data frame (QoS DATA Frame), and part of the SCSID field is carried in at least one of an HT control field (HT Control Field), a UHR control field (UHR Control Field), and an extended HT control field (Extended HT Control Field) of a quality of service null frame (QoS NULL Frame).

[0194] In conclusion, the method provided in the embodiment can make the access point know the AC, TID, or SCSID to which the at least one service data unit in the buffer belongs in time by simultaneously sending the identifier corresponding to the at least one service data unit in the buffer when the size of the buffer and the delay requirement of the at least one service data unit are reported, and thus the stability of data transmission is ensured.

[0195] In some embodiments, after receiving the low-delay buffer status report sent by the data sender, the data receiver will continue to perform subsequent steps related to data transmission based on the received low-delay buffer status report. Specifically, the data receiver will transmit each service data unit according to the delay requirement indicated in the low-delay buffer status report.

[0196] In the related art, when the low-delay buffer status report does not carry the delay requirement corresponding to the service data unit, the data receiver mainly performs in-sequence transmission of the service data unit according to the size of the sequence number (SN) corresponding to the service data unit received by the data receiver. For example, assuming that SN1 corresponding to service data unit 1 is X1 and SN2 corresponding to service data unit 2 is X1+1, since SN1 is smaller than SN2, service data unit 1 is transmitted first, and then service data unit 2 is transmitted. That is, the data sender needs to indicate the SN corresponding to the service data unit when sending the low-delay buffer status report to the data sender.

[0197] In some embodiments, the SN is used to sequentially number each service data unit and to help reorder the service data units in the case of out-of-order, packet loss, timeout, etc. during transmission.

[0198] In the optional embodiments based on FIG. 2 or FIG. 3, the first frame further includes a fourth field for indicating a sequence number corresponding to the at least one service data unit.

[0199] The fourth field can also be understood as a fourth type of field, which refers to a type field used to indicate a sequence number corresponding to the at least one service data unit.

[0200] In some embodiments, the fourth field includes at least one of the following:

[0201] a field used to indicate a minimum sequence number corresponding to the at least one service data unit;

[0202] a field used to indicate a maximum sequence number corresponding to the at least one service data unit;

[0203] a field used to indicate an offset value between the minimum sequence number and a sequence number of a current service data unit;

[0204] a field used to indicate an offset value between the maximum sequence number and the sequence number of the current service data unit;

[0205] The current service data unit is a service data unit carried in the first frame.

[0206] In some embodiments, the minimum sequence number corresponding to the at least one service data unit can also be understood as a minimum value of the sequence numbers corresponding to the at least one service data unit in the buffer, or as a value of a sequence number corresponding to a first service data unit in the buffer.

[0207] In some embodiments, the maximum sequence number corresponding to the at least one service data unit can also be understood as a maximum value of the sequence numbers corresponding to the at least one service data unit in the buffer, or as a value of a sequence number corresponding to a last service data unit in the buffer.

[0208] In some embodiments, based on the offset value between the minimum sequence number and the sequence number of the current service data unit, and the minimum sequence number, the sequence number of the current service data unit can be determined. For example, assuming that the minimum sequence number is X1 and the offset value between the minimum sequence number and the sequence number of the current service data unit is N, then the sequence number of the current service data unit is X1+N.

[0209] In some embodiments, based on the offset value between the maximum sequence number and the sequence number of the current service data unit, and the maximum sequence number, the sequence number of the current service data unit can be determined. For example, assuming that the maximum sequence number is X2 and the offset value between the maximum sequence number and the sequence number of the current service data unit is M, then the sequence number of the current service data unit is X2-M.

[0210] In some embodiments, the first frame is a Quality of Service Null Frame (QoS NULL Frame), and the fourth field is carried in at least one of a Sequence Control Field, an HT Control Field, a UHR Control Field, and an Extended HT Control Field of the Quality of Service Null Frame (QoS NULL Frame).

[0211] In some embodiments, the data receiving device transmits each service data unit according to the delay requirement of the service data unit corresponding to the SN of the service data unit, and the delay requirement of the service data unit.

[0212] In some embodiments, when the first service data unit is received and the second service data unit before the first service data unit in the receiving reordering buffer is not successfully received, the expiration time corresponding to the first service data unit delivers the first service data unit to the next MAC process.

[0213] For example, as shown in FIG. 5, when the AP receives the MSDUs with SN=X+1 and SN=X+2 but does not receive the MSDU with SN=X, since the MSDUs with SN=X+1 and SN=X+2 have indicated the expiration time as T1, the MSDUs with SN=X+1 and SN=X+2 will be delivered to the next MAC process within T1 even if the MSDU with SN=X is not received and transmitted.

[0214] In summary, the method provided in the embodiments can enable the AP to timely transmit the received service data units according to the delay requirement of each service data unit by simultaneously sending the SN corresponding to the at least one service data unit in the buffer when reporting the size of the buffer and the delay requirement of the at least one service data unit.

[0215] In some embodiments, after the data receiving device delivers the at least one service data unit in the buffer to the next MAC process, the data receiving device also needs to perform replay detection on the at least one service data unit to ensure that the same service data unit is not repeatedly delivered.

[0216] In some embodiments, replay detection is implemented by counting the Packet Number (PN) for at least one service data unit. The rules for replay detection include at least one of the following:

[0217] • The PN value is continuously counted for each MAC Protcol Data Unit (MPDU). MPDUs belonging to the same MSDU or A-MSDU shall have the same PN. Different MSDUs or A-MSDUs or M-MPDUs have different PNs.

[0218] • Each data sender device shall maintain a PN value for each Pairwise Transient Key Security Association (PTKSA), Group Temporal Key Security Association (GTKSA), and Station Key Security Association (STAkeySA).

[0219] • The PN sequence is a 48-bit monotonically increasing positive integer, which is also initialized to 1 when the corresponding transient key is initialized or refreshed.

[0220] • The data receiver device shall maintain a separate set of PN replay counters for each PTKSA, GTKSA, and STAkeySA. The data receiver device resets the replay counter to 0 when the transient key is reset. The replay counter is set to the PN value of the next receivable Cipher-Block Chaining Message Authentication Code (CBC-MAC) Protocol (CCMP) MPDU.

[0221] • The data receiver device maintains a separate replay counter for IEEE 802.11 MSDU priority for each PTKSA, GTKSA, and STAkeySA, and obtains the PN value from the received data frame to check the replayed data frame. At this time, the IEEE 802.11 MSDU priority is not used. The data sender does not reorder the frames within the replay counter, but can reorder the data frames outside the replay counter.

[0222] • If the PN values of multiple fragmented MSDUs corresponding to one complete MSDU are not consecutive, the complete MSDU will be discarded by the data sink device as a whole. The data sink device will also discard any MPDUs with a PN value less than or equal to the replay counter value.

[0223] In some embodiments, as mentioned in the above embodiments, the data sink device will not pass the service data units one by one to the next MAC process in the order of ascending SN based on the size of the buffer and the latency requirement of the received at least one service data unit. Therefore, the replay detection mechanism in the related art can not be able to meet the accurate replay detection.

[0224] Based on this, the embodiments of the present application further propose that the first frame further comprises a fifth field for indicating a replay counter used by the at least one service data unit in replay detection.

[0225] The fifth field can also be understood as a fifth type field or a fifth type of field, which refers to a type field for indicating a replay counter used by the at least one service data unit in replay detection.

[0226] In some embodiments, the fifth field complies with at least one of the following principles:

[0227] • Service data units of the same TA and SCSID use the same replay counter, and service data units of different TA and SCSID use different replay counters;

[0228] • Service data units of the same latency requirement use the same replay counter, and service data units of different latency requirements use different replay counters;

[0229] • The replay counters corresponding to at least two service data units are different.

[0230] In some embodiments, in the case of receiving a third service data unit, replay detection is performed on the third service data unit based on the replay counter indicated by the fifth field for the third service data unit.

[0231] As shown in FIG. 6, for example, when an MSDU or A-MSDU enters the Replay Detection stage from the receive reordering buffer, the received Replay Counter ID can be compared with the corresponding replay counter. Optionally, the Replay Counter ID is used to indicate the replay counter used by at least one service data unit during the replay detection.

[0232] For example, in the case that the AP receives the MSDUs with SN=X+1 and SN=X+2 but does not receive the MSDU with SN=X, since the MSDUs with SN=X+1 and SN=X+2 have indicated an expiration time of T1, the MSDUs with SN=X+1 and SN=X+2 will be passed to the next MAC process within T1 even if the MSDU with SN=X is not received and transmitted. At this time, the Replay Counter ID corresponding to the MSDUs with SN=X+1 and SN=X+2 is R2, so the MSDUs with SN=X+1 and SN=X+2 will be subjected to replay detection based on the replay counter R2 when entering the Replay Detection stage from the receive reordering buffer.

[0233] In the case that the MSDU with SN=X is subsequently received, since the MSDU with SN=X has indicated an expiration time of T2, the AP will pass the MSDU with SN=X to the next MAC process within T2. However, since the MSDU with SN=X is an MSDU before the MSDUs with SN=X+1 and SN=X+2, if the MSDU with SN=X is subjected to replay detection based on the replay counter R2, a situation in which the detection fails can occur. Based on this, in the embodiments of the present application, the Replay Counter ID corresponding to the MSDU with SN=X is set to R1. When the MSDU with SN=X enters the Replay Detection stage from the receive reordering buffer, the MSDU with SN=X will be subjected to replay detection based on the replay counter R1, so as to ensure that the MSDU with SN=X can pass the replay detection.

[0234] In some embodiments, the AP can set a replay counter for each SCS under the same TA and TID respectively according to the SCSID of each received MSDU or A-MSDU. For example, as shown in FIG. 7, the MSDUs with SN=X+1 and SN=X+2 correspond to the same replay counter Z1 respectively.

[0235] In summary, the method provided by the embodiments enables the AP to timely perform replay counting on the service data units according to the correct replay counter by reporting the replay counter used by the at least one service data unit in the buffer during replay detection, so that the service data units can be accurately subjected to replay detection when being delivered to the next MAC process.

[0236] In some embodiments, after the data receiving side device receives the size of the buffer and the delay requirement of the at least one service data unit, the data receiving side device needs to reasonably allocate the channel resources based on the size of the buffer and the delay requirement of the at least one service data unit received, so that the data transmission can meet the corresponding delay requirement.

[0237] Optionally, the data receiving side device triggers the allocation of the channel resources by sending a basic trigger frame or a Multi User Request to Send Transmission (MU RTS TXS) frame.

[0238] In some embodiments, the first frame further includes an eighth field for indicating that the AP needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

[0239] The eighth field can also be understood as an eighth type field or an eighth type field, which refers to a type field for indicating that the AP needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

[0240] In some embodiments, when the eighth field has a first value, it is used to indicate that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission.

[0241] In some embodiments, when the eighth field has a second value, it is used to indicate that the AP needs to send a MU RTS TXS frame for channel resource allocation or sharing.

[0242] For example, when the value of the eighth field is 0, it indicates that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; when the value of the eighth field is 1, it indicates that the AP needs to send an MU RTS TXS frame for channel resource allocation or sharing. Alternatively, when the value of the eighth field is 1, it indicates that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; when the value of the eighth field is 0, it indicates that the AP needs to send an MU RTS TXS frame for channel resource allocation or sharing.

[0243] In summary, the method provided by the embodiment reports the eighth field to indicate that the data receiver device sends a basic trigger frame or an MU RTS TXS frame for channel resource allocation or sharing, so that the data receiver device can reasonably allocate channel resources based on the size of the buffer and the delay requirement of the received at least one service data unit.

[0244] In some embodiments, the first field, the second field and the third field can be combined to implement a new embodiment. The first field, the second field and the fourth field can be combined to implement a new embodiment. The first field, the second field and the fifth field can be combined to implement a new embodiment. The first field, the second field and the sixth field can be combined to implement a new embodiment. The first field, the second field and the seventh field can be combined to implement a new embodiment. The first field, the second field and the eighth field can be combined to implement a new embodiment.

[0245] In some embodiments, the first field, the second field, the third field, and the fourth field described above can be combined to implement a new embodiment. The first field, the second field, the third field, and the fifth field described above can be combined to implement a new embodiment. The first field, the second field, the third field, and the sixth field described above can be combined to implement a new embodiment. The first field, the second field, the third field, and the seventh field described above can be combined to implement a new embodiment. The first field, the second field, the third field, and the eighth field described above can be combined to implement a new embodiment. The first field, the second field, the fourth field, and the fifth field described above can be combined to implement a new embodiment. The first field, the second field, the fourth field, and the sixth field described above can be combined to implement a new embodiment. The first field, the second field, the fourth field, and the seventh field described above can be combined to implement a new embodiment. The first field, the second field, the fourth field, and the eighth field described above can be combined to implement a new embodiment. The first field, the second field, the fifth field, and the sixth field described above can be combined to implement a new embodiment. The first field, the second field, the fifth field, and the seventh field described above can be combined to implement a new embodiment. The first field, the second field, the fifth field, and the eighth field described above can be combined to implement a new embodiment. The first field, the second field, the sixth field, and the seventh field described above can be combined to implement a new embodiment. The first field, the second field, the sixth field, and the eighth field described above can be combined to implement a new embodiment. The first field, the second field, the seventh field, and the eighth field described above can be combined to implement a new embodiment.

[0246] In some embodiments, the first field, the second field, the third field, the fourth field, the fifth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the sixth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field and the sixth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field and the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the sixth field and the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the sixth field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the seventh field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field and the sixth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field and the seventh field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the sixth field and the seventh field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the sixth field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the seventh field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the fifth field, the sixth field and the seventh field can be combined to implement a new embodiment. The first field, the second field, the fifth field, the sixth field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the fifth field, the seventh field and the eighth field can be combined to implement a new embodiment. The first field, the second field, the sixth field, the seventh field and the eighth field can be combined to implement a new embodiment.

[0247] In some embodiments, the first field, the second field, the third field, the fourth field, the fifth field, the sixth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the fifth field, the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the fifth field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the sixth field, the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the sixth field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fourth field, the seventh field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field, the sixth field, the seventh field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field, the sixth field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the fifth field, the seventh field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the third field, the sixth field, the seventh field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field, the sixth field, the seventh field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field, the sixth field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the fifth field, the seventh field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the fourth field, the sixth field, the seventh field, the eighth field can be combined to implement a new embodiment. The first field, the second field, the fifth field, the sixth field, the seventh field, the eighth field can be combined to implement a new embodiment.

[0248] In some embodiments, the first field, the second field, the third field, the fourth field, the fifth field, the sixth field, the seventh field and the eighth field can be combined to form a new embodiment. The first field, the second field, the third field, the fourth field, the fifth field, the sixth field, the eighth field can be combined to form a new embodiment. The first field, the second field, the third field, the fourth field, the fifth field, the seventh field, the eighth field can be combined to form a new embodiment. The first field, the second field, the third field, the fourth field, the sixth field, the seventh field, the eighth field can be combined to form a new embodiment. The first field, the second field, the third field, the fifth field, the sixth field, the seventh field, the eighth field can be combined to form a new embodiment. The first field, the second field, the fourth field, the fifth field, the sixth field, the seventh field, the eighth field can be combined to form a new embodiment.

[0249] In some embodiments, the first field, the second field, the third field, the fourth field, the fifth field, the sixth field, the seventh field and the eighth field can be combined to form a new embodiment.

[0250] Next, at least one field carried in the first frame is exemplified in the embodiments of the present application. Specifically, the first frame is taken as a quality of service null frame (QoS NULL Frame) in the embodiments of the present application. The at least one field carried in the first frame is carried in at least one of a sequence control field (Sequence Control Field), a quality of service control field (QoS Control Field) and an HT control field (HT Control Field) in the quality of service null frame (QoS NULL Frame).

[0251] For the sequence control field (Sequence Control Field):

[0252] In the related art, the sequence control field (Sequence Control Field) in the quality of service null frame (QoS NULL Frame) can be set to any value, thus the sequence control field (Sequence Control Field) has not been used. As shown in Table 3.

[0253] In some embodiments, when the first frame is a QoS NULL frame, the SN of the first MSDU or A-MSDU in the buffer is indicated by the Sequence Control Field. That is, the MSDU or A-MSDU with the smallest SN is indicated by the Sequence Control Field. Alternatively, the SN of the last MSDU or A-MSDU in the buffer is indicated by the Sequence Control Field. That is, the MSDU or A-MSDU with the largest SN is indicated by the Sequence Control Field.

[0254] That is, the fourth field for indicating the sequence number corresponding to the at least one service data unit is carried by the Sequence Control Field. Wherein, the SN of the first MSDU is the smallest sequence number, the SN of the last MSDU is the largest sequence number, and the SN is the sequence number of the service data unit.

[0255] For the QoS Control Field:

[0256] In some embodiments, when the first frame is a QoS NULL frame, the setting of the QoS Control Field includes the following three possible schemes:

[0257] Scheme 1.1: The QoS Control Field is unchanged, that is, the QoS Control Field format in the related art is used, as shown in Table 4 above.

[0258] Scheme 1.2: Bit 7 in the QoS Control Field is used to indicate whether a QoS NULL Frame is used as the first frame. As shown in Table 4 above, Bit 7 in the QoS Control Field is a reserved bit when a QoS NULL Frame is used. Alternatively, when the value of Bit 7 is set to 1, it indicates that a QoS NULL Frame is used as the first frame; when the value of Bit 7 is set to 0, it indicates that a QoS NULL Frame is not used as the first frame. Alternatively, when the value of Bit 7 is set to 0, it indicates that a QoS NULL Frame is used as the first frame; when the value of Bit 7 is set to 1, it indicates that a QoS NULL Frame is not used as the first frame.

[0259] Scheme 1.3: A new QoS Control Field is defined.

[0260] For the HT Control Field:

[0261] When the HT Control Field is used to carry the above-mentioned fields, the position of the above-mentioned fields in the HT Control Field includes the following four schemes:

[0262] Scheme 2.1: A new A-Control Field is defined in the HT Control Field. The above-mentioned fields are carried by using the A-Control Field. Specifically, the above-mentioned fields are carried by using the Control Information in the A-Control Field. When this scheme is used, the first number of bits in the A-Control Field is used to carry the above-mentioned fields, and the first number is less than or equal to 26.

[0263] Scheme 2.2: The HT Control Field is redefined. All bits in the HT Control Field are used to carry the above-mentioned fields.

[0264] Scheme 2.3: Define a new UHR Control Field. Use the UHR Control Field instead of the HT Control Field. When this scheme is used, the length of the UHR Control Field can be redefined. Or use the unused Control ID in the A-Control Field to represent the UHR Control Field.

[0265] Scheme 2.4: Keep the HT Control Field unchanged, and define a new Extended HT Control Field. Use the HT Control Field and the Extended HT Control Field to carry the above-mentioned fields.

[0266] In some embodiments, the above-mentioned Scheme 1.1 and Scheme 2.1 can be combined to implement a new embodiment. The above-mentioned Scheme 1.1 and Scheme 2.2 can be combined to implement a new embodiment. The above-mentioned Scheme 1.1 and Scheme 2.3 can be combined to implement a new embodiment. The above-mentioned Scheme 1.1 and Scheme 2.4 can be combined to implement a new embodiment. The above-mentioned Scheme 1.2 and Scheme 2.1 can be combined to implement a new embodiment. The above-mentioned Scheme 1.2 and Scheme 2.2 can be combined to implement a new embodiment. The above-mentioned Scheme 1.2 and Scheme 2.3 can be combined to implement a new embodiment. The above-mentioned Scheme 1.2 and Scheme 2.4 can be combined to implement a new embodiment. The above-mentioned Scheme 1.3 and Scheme 2.1 can be combined to implement a new embodiment. The above-mentioned Scheme 1.3 and Scheme 2.2 can be combined to implement a new embodiment. The above-mentioned Scheme 1.3 and Scheme 2.3 can be combined to implement a new embodiment. The above-mentioned Scheme 1.3 and Scheme 2.4 can be combined to implement a new embodiment.

[0267] Exemplarily, the following three possible combination modes in the embodiments of the present application are taken as examples for illustration, but other possible combination modes are not excluded.

[0268] The first possible combination mode example:

[0269] In some embodiments, the HT Control Field can carry at least one of the following fields:

[0270] Partial SCSID field:

[0271] In some embodiments, the Partial SCSID field belongs to the third field described above.

[0272] In some embodiments, the concatenation of the Partial SCSID field and the TID field is the complete SCSID. For example, the Partial SCSID field is shown in Table 6 below:

[0273] Table 6

[0274] In some embodiments, when the STA and the AP perform SCS setting, the SCSID can be set into two parts as shown in Table 6. One part represents the TID, and the other part represents the Partial SCSID. The Partial SCSID field and the TID field in the QoS Control field are combined to obtain the complete SCSID. The Partial SCSID field is used to indicate the buffer size of the SCS traffic stream and the SCS parameters of the MSDU and A-MSDU in the buffer. For example, the SCS parameters include the QoS characteristics element.

[0275] In some embodiments, the Partial SCSID field is used to indicate the SCS traffic stream under the same STA / TID / transmission direction.

[0276] In some embodiments, when the field value of the Partial SCSID field is set to the minimum value, the TID field in the QoS Control field still represents the value of the TID.

[0277] In some embodiments, when the field value of the Partial SCSID field is set to the maximum value, the TID field in the QoS Control field still represents the value of the TID.

[0278] MSDU Size field:

[0279] In some embodiments, the MSDU Size field belongs to the first field described above.

[0280] In some embodiments, the MSDU Size field is used to indicate the average size of MSDUs or A-MSDUs in the buffer. Illustratively, the MSDU Size field is used to indicate the average number of bits of at least one service data unit.

[0281] In some embodiments, a product value of the average size of MSDUs or A-MSDUs in the buffer and the number of MSDUs or A-MSDUs is calculated, and the product value is used as the size of MSDUs or A-MSDUs in the buffer.

[0282] The Number of MSDUs / A-MSDUs field:

[0283] In some embodiments, the Number of MSDUs / A-MSDUs field belongs to the first field mentioned above.

[0284] In some embodiments, the Number of MSDUs / A-MSDUs field is used to indicate the number of MSDUs or A-MSDUs in the buffer. Illustratively, the Number of MSDUs / A-MSDUs field is used to indicate the number of at least one service data unit.

[0285] In some embodiments, the Number of MSDUs / A-MSDUs field and the Sequence Number field in the Sequence Control field can jointly represent the SN of the last MSDU or A-MSDU in the buffer, i.e., the MSDU or A-MSDU with the largest SN value. Illustratively, assuming that the Number of MSDUs / A-MSDUs field is used to indicate that the number of MSDUs or A-MSDUs is 5, and the Sequence Number field is used to indicate that the SN of the first MSDU or A-MSDU is 10, then jointly the Number of MSDUs / A-MSDUs field and the Sequence Number field can indicate that the SN of the fifth MSDU or A-MSDU is 10-1+5=14.

[0286] In some embodiments, the combined field of the Number of MSDUs / A-MSDUs field and the Sequence Number field in the Sequence Control field can be referred to as the Last MSDU / A-MSDU SN field.

[0287] Expiration Time field:

[0288] In some embodiments, the Expiration Time field belongs to the second field described above.

[0289] In some embodiments, the Expiration Time field is used to indicate the expiration time of at least one service data unit in the buffer. Specifically, the Expiration Time field is used to indicate the expiration time corresponding to each service data unit in the at least one service data unit.

[0290] In some embodiments, the format of the Partial SCSID field, the MSDU Size field, the Number of MSDUs / A-MSDUs field, and the Expiration Time field described above refer to Table 7 below:

[0291] Table 7

[0292] Second possible combination example:

[0293] AC / TID / SCSID field:

[0294] In some embodiments, the AC / TID / SCSID field belongs to the third field described above.

[0295] In some embodiments, the AC / TID / SCSID field can be any one of the AC, the TID, or the SCSID.

[0296] In some embodiments, the AC / TID / SCSID field is used to indicate the AC, the TID, or the SCSID of the MSDU and the A-MSDU. Specifically, the AC / TID / SCSID field is used to indicate the identity corresponding to the at least one service data unit.

[0297] Scaling Factor field:

[0298] In some embodiments, the Scaling Factor field belongs to the first field described above.

[0299] In some embodiments, the Scaling Factor field is the same as the Scaling Factor field in BSR (IEEE 802.11ax).

[0300] In some embodiments, the Scaling Factor field and the Queue Size field in the QoS Control field can be combined to represent the size of at least one service data unit in the buffer. The Scaling Factor field is used to indicate the data unit of the data to be sent, such as MB; the Queue Size field is used to indicate the number of data units of the data to be sent, such as 8. The two fields combined identify the size of the data to be sent in the buffer, such as 8MB.

[0301] Earliest Expiration Time field:

[0302] In some embodiments, the Earliest Expiration Time field belongs to the second field described above.

[0303] In some embodiments, the Earliest Expiration Time field is used to represent the earliest expiration time of the MSDU or A-MSDU in the buffer. Illustratively, when the buffer includes multiple MSDUs or A-MSDUs, each MSDU or A-MSDU corresponds to a respective expiration time. The Earliest Expiration Time field is used to indicate the earliest one of the multiple expiration times corresponding to the multiple MSDUs or A-MSDUs.

[0304] Latest Expiration Time field:

[0305] In some embodiments, the Latest Expiration Time field belongs to the second field described above.

[0306] In some embodiments, the Latest Expiration Time field is used to indicate the latest expiration time among the MSDUs or A-MSDUs in the buffer. Illustratively, when multiple MSDUs or A-MSDUs are included in the buffer, each of the MSDUs or A-MSDUs corresponds to a respective expiration time. The Latest Expiration Time field is used to indicate the latest expiration time among the multiple expiration times corresponding to the multiple MSDUs or A-MSDUs.

[0307] In some embodiments, the Latest Expiration Time field is used to indicate the difference between the Earliest Expiration Time and the Latest Expiration Time.

[0308] In some embodiments, the format of the AC / TID / SCSID field, the Scaling Factor field, the Earliest Expiration Time field, and the Latest Expiration Time field is as shown in Table 8 below:

[0309] Table 8

[0310] A third possible combination example is as follows:

[0311] The Number of ACs / TIDs field:

[0312] In some embodiments, the Number of ACs / TIDs field is the third field described above. Specifically, the Number of ACs / TIDs field is the field used to indicate the number of identifiers corresponding to the at least one service data unit in the buffer.

[0313] In some embodiments, the Number of ACs / TIDs field is used to indicate the number of ACs / TIDs to which the MSDUs and A-MSDUs in the buffer belong. Specifically, the MSDUs and A-MSDUs in the buffer are used to indicate that the MSDUs and A-MSDUs in the buffer come from several ACs or several TIDs.

[0314] Bandwidth field:

[0315] In some embodiments, the Bandwidth field belongs to the first field described above. Specifically, the Bandwidth field is a field in the first field described above for indicating the bandwidth required by the at least one service data unit.

[0316] In some embodiments, the bandwidth indicated by the Bandwidth field corresponds to channel resources (i.e. frequency domain resources) in combination with the TXOP duration (i.e. time domain resources) shown in the TXOP Duration Requested field in the Quality of Service Control field, which collectively represent the transmission requirement of the MSDU or A-MSDU of the buffer. To some extent, the data volume of the MSDU and / or A-MSDU can also be represented.

[0317] MCS field:

[0318] In some embodiments, the MCS field belongs to the first field described above. Specifically, the MCS field is a field in the first field described above for indicating the MCS required by the at least one service data unit.

[0319] In some embodiments, the duration of the TXOP, the bandwidth and the MCS are used to calculate the size of the buffer. For example, by calculating the product of the duration of the TXOP required by the at least one service data unit, the bandwidth required by the at least one service data unit and the bit rate indicated by the MCS required by the at least one service data unit, the product is taken as the size of the at least one service data unit in the buffer.

[0320] Latest Trigger Time / Deadline field:

[0321] In some embodiments, the Latest Trigger Time / Deadline field belongs to the second field described above. Specifically, the Latest Trigger Time / Deadline field is used to indicate the latest time of the channel resources required by the at least one service data unit.

[0322] In some embodiments, the Latest Trigger Time field is used to represent the latest time at which the AP sends a basic trigger frame or allocates or shares channel resources to the STA by MU RTS TXS.

[0323] Trigger Type field:

[0324] In some embodiments, the Trigger Type field belongs to the eighth field described above. Specifically, the Trigger Type field indicates whether the AP needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

[0325] Optionally, the Trigger Type field includes 1 bit.

[0326] In some embodiments, when the Trigger Type field is a first value, it indicates that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; when the Trigger Type field is a second value, it indicates that the AP needs to send a MU RTS TXS frame for channel resource allocation or sharing.

[0327] For example, when the Trigger Type field is 0, it indicates that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; when the Trigger Type field is 1, it indicates that the AP needs to send a MU RTS TXS frame for channel resource allocation or sharing. Or, when the Trigger Type field is 1, it indicates that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; when the Trigger Type field is 0, it indicates that the AP needs to send a MU RTS TXS frame for channel resource allocation or sharing.

[0328] In some embodiments, the Trigger Type field is also used to indicate whether there is Peer-to-Peer (P2P) traffic in the buffer.

[0329] In some embodiments, the format of the Number of ACs / TIDs field, the Bandwidth field, the MCS field, the Latest Trigger Time field, and the Trigger Type field described above refer to Table 9 below:

[0330] Table 9

[0331] Other possible fields that can be carried:

[0332] Retry Counter ID field:

[0333] In some embodiments, the Retry Counter ID field belongs to the fifth field described above.

[0334] In some embodiments, the Retry Counter ID field is used to indicate that the corresponding retry counter is needed for the MSDU or A-MSDU to be checked when the receiving station performs replay detection.

[0335] In some embodiments, the Retry Counter ID field needs to explicitly indicate the SN of the MSDU or A-MSDU.

[0336] In some embodiments, the Retry Counter ID field is used to explicitly indicate the corresponding retry counter of each MSDU or A-MSDU. For example, assuming that two MSDUs, MSDU-1 and MSDU-2, are included in the buffer, the Retry Counter ID field is used to explicitly indicate that MSDU-1 corresponds to retry counter-1 and to explicitly indicate that MSDU-2 corresponds to retry counter-2.

[0337] In some embodiments, the Retry Counter ID field needs to be combined with the AC or TID or SCSID to which each service data unit belongs to indicate the corresponding retry counter of each service data unit. At this time, when the AP uses the Retry Counter ID field to determine the corresponding retry counter of each MSDU or A-MSDU, the AC or TID or SCSID to which at least one service data unit in the buffer belongs also needs to be explicitly indicated. For example, assuming that the Retry Counter ID field is used to indicate that the MSDU belonging to SCSID-1 corresponds to retry counter-1 and to indicate that the MSDU belonging to SCSID-2 corresponds to retry counter-2.

[0338] Queue Size Part 2 field:

[0339] In some embodiments, the Queue Size Part 2 field belongs to the sixth field described above. Specifically, the Queue Size Part 2 field is used to extend the indication of the sequence size corresponding to at least one service data unit in the buffer.

[0340] In some embodiments, the Queue Size Part 2 field is used to supplement the insufficient number of bits of the Queue Size field (which can be understood as the Queue Size Part 1 field) in the QoS Control Field.

[0341] In some embodiments, the Queue Size field and the Queue Size Part 2 field in the QoS Control Field are jointly used to indicate the queue size of the at least one service data unit in the buffer.

[0342] The TXOP Duration Requested Part 2 field:

[0343] In some embodiments, the TXOP Duration Requested Part 2 field belongs to the seventh field described above. Specifically, the TXOP Duration Requested Part 2 field is used to extend the indication of the TXOP duration required by the at least one service data unit.

[0344] In some embodiments, the TXOP Duration Requested Part 2 field is used to supplement the insufficient number of bits of the TXOP Duration Requested field (which can be understood as the TXOP Duration Requested Part-1 field) in the QoS Control Field.

[0345] In some embodiments, the format of the Retry Counter ID field, the Queue Size Part 2 field, and the TXOP Duration Requested Part 2 field described above refer to Table 10 below:

[0346] Table 10

[0347] In some embodiments, the first frame is a QoS DATA frame. Specifically, the QoS DATA frame is different from a QoS NULL frame in that a Sequence Control Field in the QoS DATA frame is used to indicate the SN of the MSDU or A-MSDU contained in the QoS DATA frame.

[0348] In some embodiments, the QoS DATA frame further comprises the following fields:

[0349] a Starting Sequence Number Delta field:

[0350] In some embodiments, the Starting Sequence Number Delta field is the fourth field as described above.

[0351] In some embodiments, the Starting Sequence Number Delta field is used to indicate the difference between the SN of the first MSDU or A-MSDU and the SN in the Sequence Control Field. That is, the SN in the Sequence Control Field + the value of the Starting Sequence Number Delta field = the SN of the first MSDU or A-MSDU.

[0352] For example, assuming the Starting Sequence Number Delta field is used to indicate a SN offset value of 5 and the SN of the MSDU or A-MSDU being transmitted is 10, then the SN of the first MSDU or A-MSDU is 10 + 5 = 15.

[0353] an Ending Sequence Number Delta field:

[0354] In some embodiments, the ending sequence number delta field is used to represent the difference between the value of the SN of the last MSDU or A-MSDU and the value of the SN in the sequence control field. That is, the value of the SN in the sequence control field + the value of the ending sequence number delta field = the value of the SN of the last MSDU or A-MSDU.

[0355] For example, assuming that the ending sequence number delta field is used to indicate that the offset value of the SN is 5, and the SN of the MSDU or A-MSDU currently being transmitted is 10, then the SN of the last MSDU or A-MSDU is 10 + 5 = 15.

[0356] It should be noted that the above fields are only used as exemplary descriptions in the embodiments of the present application, and in other possible embodiments, the order, number, and the up-down relationship between the fields, and the number of bits corresponding to each field can also be other cases, which are not limited in the embodiments of the present application.

[0357] FIG. 8 shows a flowchart of a method for transmitting and receiving a buffer status report according to an exemplary embodiment of the present application. The method is performed by a data sender device and a data receiver device, and the present application takes an example of the data sender device being a STA and the data receiver device being an AP. The method comprises:

[0358] Step 1: The STA transmits a first frame, and the first frame is used to indicate the size and delay requirement of at least one service data unit in the buffer;

[0359] Step 2: The AP receives the first frame, and the first frame is used to indicate the size and delay requirement of at least one service data unit in the buffer.

[0360] Specifically, the detailed description of the first frame is described in the above steps 220 and 420.

[0361] Step 3: The STA transmits at least one service data unit;

[0362] In the case where the STA has transmitted a low-delay buffer status report to the AP, the STA transmits at least one service data unit in the buffer to the AP.

[0363] Step 4: The AP receives at least one service data unit;

[0364] The AP receives at least one service data unit in a buffer sent by the STA.

[0365] Step 5: The AP delivers the at least one service data unit to a next MAC process.

[0366] In some embodiments, after receiving the at least one service data unit, the AP delivers the received service data units to the next MAC process according to the SNs corresponding to the service data units. In the embodiments of the present application, in order to meet the delay requirements of different service data units, the service data units can not be delivered in sequence according to the SNs corresponding to the service data units.

[0367] For example, as shown in FIG. 5, in the case where the AP has received MSDUs with SNs of X+1 and X+2 but not received an MSDU with SN of X, since the MSDUs with SNs of X+1 and X+2 have indicated an expiration time of T1, the MSDUs with SNs of X+1 and X+2 will be delivered to the next MAC process within the time T1 even if the MSDU with SN of X is not received and transmitted.

[0368] Step 6: The AP performs replay detection on the at least one service data unit delivered to the next MAC process.

[0369] In some embodiments, in order to ensure that the same service data unit is not delivered repeatedly, the AP needs to perform replay detection on the delivered service data units after delivering the at least one service data unit to the next MAC process. Since the at least one service data unit is not delivered in sequence according to the SNs, different service data units can use different replay counters in the embodiments of the present application. For example, service data units with the same delay requirement use the same replay counter, and service data units with different delay requirements use different replay counters.

[0370] For example, as shown in FIG. 6, the replay counter IDs corresponding to the MSDUs with SNs of X+1 and X+2 are R2, so the MSDUs with SNs of X+1 and X+2 will be subjected to replay detection based on the replay counter R2 when entering the replay detection stage from the receive reordering buffer.

[0371] In the case that a subsequent MSDU with SN=X is received, since the MSDU with SN=X has indicated an expiration time T2, the AP will deliver the MSDU with SN=X to the next MAC process within T2. However, since the MSDU with SN=X is a MSDU before the MSDUs with SN=X+1 and SN=X+2, if the replay detection is still based on the replay counter R2, the MSDU with SN=X can fail the replay detection. Based on this, in the embodiments of the present application, the replay counter ID corresponding to the MSDU with SN=X is set as R1. When the MSDU with SN=X enters the replay detection stage from the receive reordering buffer, the replay detection will be based on the replay counter R1, so as to ensure that the MSDU with SN=X can pass the replay detection.

[0372] FIG. 9 shows a structure block diagram of a sending device of a buffer status report according to an example embodiment of the present application. The device includes:

[0373] The sending module 710 is configured to send a first frame, the first frame being used to indicate a size of a buffer zone for at least one service data unit and a delay requirement.

[0374] In some embodiments, the first frame includes:

[0375] a first field used to indicate the size of the buffer zone for the at least one service data unit;

[0376] a second field used to indicate the delay requirement.

[0377] In some embodiments, the first field includes at least one of the following fields:

[0378] a field used to indicate an average bit number of the at least one service data unit;

[0379] a field used to indicate a number of the at least one service data unit;

[0380] a field used to indicate a size proportion of a sum of bit numbers of the at least one service data unit to a total bit number of the buffer zone;

[0381] a field used to indicate a sequence size of the at least one service data unit;

[0382] a field used to indicate a scaling factor of the at least one service data unit;

[0383] a field for indicating a required TXOP duration of the at least one service data unit;

[0384] a field for indicating a required bandwidth of the at least one service data unit;

[0385] a field for indicating a required MCS of the at least one service data unit.

[0386] In some embodiments, the second field comprises at least one of the following fields:

[0387] a field for indicating an expiration time corresponding to each of the at least one service data unit;

[0388] a field for indicating an earliest expiration time corresponding to the at least one service data unit;

[0389] a field for indicating a latest expiration time corresponding to the at least one service data unit;

[0390] a field for indicating an offset value of the latest expiration time relative to the earliest expiration time;

[0391] a field for indicating an offset value of the earliest expiration time relative to the latest expiration time;

[0392] a field for indicating a latest time of a required channel resource of the at least one service data unit.

[0393] In some embodiments, the latency requirement is characterized by an absolute time, or the latency requirement is characterized by an offset value relative to a transmission time or a reception time.

[0394] In some embodiments, the first frame is a quality of service null frame (QoS NULL Frame), and the first field and the second field are carried in at least one of a HT control field, a UHR control field, and an extended HT control field of the quality of service null frame (QoS NULL Frame).

[0395] In some embodiments, the first frame is a quality of service data frame (QoS DATA Frame), and the first field and the second field are carried in at least one of a HT control field, a UHR control field, and an extended HT control field of the quality of service data frame (QoS DATA Frame).

[0396] In some embodiments, the HT control field comprises an A control field, and the A control field is used to carry the first field and the second field.

[0397] In some embodiments, all bits of the HT control field are used to carry the first field and the second field.

[0398] In some embodiments, the UHR control field is used to carry the first field and the second field.

[0399] In some embodiments, the HT control field and the extended HT control field are used to carry the first field and the second field.

[0400] In some embodiments, the first frame further comprises a third field used to indicate an identity corresponding to the at least one service data unit.

[0401] In some embodiments, the identity corresponding to the at least one service data unit comprises at least one of an AC, a TID and an SCSID.

[0402] In some embodiments, the third field comprises at least one of: an AC field; a TID field; an SCSID field; a field used to indicate a number of identities; a partial SCSID field; wherein a concatenation of the TID field and the partial SCSID field is a complete SCSID.

[0403] In some embodiments, the first frame is a QoS NULL frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the QoS NULL frame.

[0404] In some embodiments, the first frame is a QoS DATA frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the QoS DATA frame.

[0405] In some embodiments, the first frame is a QoS NULL frame, the TID field is carried in a QoS control field of the QoS NULL frame, and the partial SCSID field is carried in at least one of an HT control field, a UHR control field and an extended HT control field of the QoS NULL frame.

[0406] In some embodiments, the first frame further comprises a fourth field used to indicate a sequence number corresponding to the at least one service data unit.

[0407] In some embodiments, the fourth field comprises at least one of:

[0408] a field used to indicate a minimum sequence number corresponding to the at least one service data unit;

[0409] a field used to indicate a maximum sequence number corresponding to the at least one service data unit;

[0410] a field for indicating an offset value between the minimum sequence number and the sequence number of the current service data unit;

[0411] a field for indicating an offset value between the maximum sequence number and the sequence number of the current service data unit;

[0412] wherein the current service data unit is a service data unit carried in the first frame.

[0413] In some embodiments, the first frame is a quality of service null frame (QoS NULL Frame), and the fourth field is carried in at least one of a sequence control field, an HT control field, a UHR control field, and an extended HT control field of the quality of service null frame (QoS NULL Frame).

[0414] In some embodiments, the first frame further comprises a fifth field for indicating a replay counter used by the at least one service data unit in replay detection.

[0415] In some embodiments, the fifth field complies with at least one of the following principles:

[0416] service data units of the same TA and SCSID use the same replay counter, and service data units of different TA and SCSID use different replay counters;

[0417] service data units of the same latency requirement use the same replay counter, and service data units of different latency requirement use different replay counters;

[0418] the replay counters corresponding to the at least two service data units are different.

[0419] In some embodiments, the first frame further comprises a sixth field for extending the sequence size of the buffer.

[0420] In some embodiments, the sixth field jointly indicates the sequence size of the buffer together with the field in the first field for indicating the sequence size.

[0421] In some embodiments, the first frame further comprises a seventh field for extending the TXOP duration required by the at least one service data unit.

[0422] In some embodiments, the seventh field jointly indicates the TXOP duration required by the at least one service data unit together with the field in the first field for indicating the TXOP duration.

[0423] In some embodiments, the first frame further comprises an eighth field for indicating that the AP needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

[0424] In some embodiments, when the eighth field takes the first value, it is used to indicate that the AP needs to send a basic trigger frame for channel resource allocation or sharing and trigger uplink transmission.

[0425] In some embodiments, when the eighth field takes the second value, it is used to indicate that the AP needs to send an MU RTS TXS frame for channel resource allocation or sharing.

[0426] FIG. 10 shows a structural block diagram of a receiving device of a buffer status report according to an example embodiment of the present application. The device includes:

[0427] The receiving module 810 is configured to receive a first frame, the first frame being used to indicate a size of at least one service data unit in a buffer and a latency requirement.

[0428] In some embodiments, the first frame includes:

[0429] a first field used to indicate the size of the at least one service data unit in the buffer;

[0430] a second field used to indicate the latency requirement.

[0431] In some embodiments, the first field includes at least one of the following fields:

[0432] a field used to indicate an average number of bits of the at least one service data unit;

[0433] a field used to indicate a number of the at least one service data unit;

[0434] a field used to indicate a size ratio of a sum of bit numbers of the at least one service data unit to a total bit number of the buffer;

[0435] a field used to indicate a sequence size of the at least one service data unit;

[0436] a field used to indicate a scaling factor of the at least one service data unit;

[0437] a field used to indicate a required TXOP duration of the at least one service data unit;

[0438] a field used to indicate a required bandwidth of the at least one service data unit;

[0439] a field used to indicate a required MCS of the at least one service data unit.

[0440] In some embodiments, the second field includes at least one of the following fields:

[0441] a field used to indicate an expiration time corresponding to each of the at least one service data unit;

[0442] a field for indicating an earliest expiration time corresponding to the at least one service data unit;

[0443] a field for indicating a latest expiration time corresponding to the at least one service data unit;

[0444] a field for indicating an offset value of the latest expiration time relative to the earliest expiration time;

[0445] a field for indicating an offset value of the earliest expiration time relative to the latest expiration time;

[0446] a field for indicating a latest time of channel resource required by the at least one service data unit.

[0447] In some embodiments, the latency requirement is characterized by an absolute time, or the latency requirement is characterized by an offset value relative to a transmission time or a reception time.

[0448] In some embodiments, the first frame is a quality of service null frame (QoS NULL Frame), and the first field and the second field are carried in at least one of a HT control field, a UHR control field and an extended HT control field of the quality of service null frame (QoS NULL Frame).

[0449] In some embodiments, the first frame is a quality of service data frame (QoS DATA Frame), and the first field and the second field are carried in at least one of a HT control field, a UHR control field and an extended HT control field of the quality of service data frame (QoS DATA Frame).

[0450] In some embodiments, the HT control field comprises an A control field, and the A control field is used to carry the first field and the second field.

[0451] In some embodiments, all bits of the HT control field are used to carry the first field and the second field.

[0452] In some embodiments, the UHR control field is used to carry the first field and the second field.

[0453] In some embodiments, the HT control field and the extended HT control field are used to carry the first field and the second field.

[0454] In some embodiments, in a case that the first service data unit is received and a second service data unit preceding the first service data unit in the reception reordering buffer is not successfully received, the expiration time corresponding to the first service data unit delivers the first service data unit to a next MAC processing flow.

[0455] In some embodiments, the first frame further comprises:

[0456] a third field for indicating an identity corresponding to the at least one service data unit, the identity comprising at least one of an AC, a TID and an SCSID.

[0457] In some embodiments, the third field comprises at least one of: an AC field; a TID field; an SCSID field; a field for indicating a number of identities; a partial SCSID field; wherein a concatenation of the TID field and the partial SCSID field is a complete SCSID.

[0458] In some embodiments, the first frame is a QoS NULL Frame, and the third field is carried in at least one of a QoS Control field, an HT Control field, a UHR Control field and an Extended HT Control field of the QoS NULL Frame.

[0459] In some embodiments, the first frame is a QoS DATA Frame, and the third field is carried in at least one of a QoS Control field, an HT Control field, a UHR Control field and an Extended HT Control field of the QoS DATA Frame.

[0460] In some embodiments, the first frame is a QoS NULL Frame, the TID field is carried in a QoS Control field of the QoS NULL Frame, and the partial SCSID field is carried in at least one of an HT Control field, a UHR Control field and an Extended HT Control field of the QoS NULL Frame.

[0461] In some embodiments, the first frame further comprises: a fourth field for indicating a sequence number corresponding to the at least one service data unit.

[0462] In some embodiments, the fourth field comprises at least one of:

[0463] a field for indicating a minimum sequence number corresponding to the at least one service data unit;

[0464] a field for indicating a maximum sequence number corresponding to the at least one service data unit;

[0465] a field for indicating an offset value between the minimum sequence number and a sequence number of a current service data unit;

[0466] a field for indicating an offset value between the maximum sequence number and the sequence number of the current service data unit;

[0467] wherein the current service data unit is a service data unit carried in the first frame.

[0468] In some embodiments, the first frame is a Quality of Service Null Frame (QoS NULL Frame), and the fourth field is carried in at least one of a Sequence Control field, an HT Control field, a UHR Control field, and an Extended HT Control field of the Quality of Service Null Frame (QoS NULL Frame).

[0469] In some embodiments, the first frame further comprises a fifth field for indicating a replay counter used by the at least one service data unit in replay detection.

[0470] In some embodiments, the fifth field complies with at least one of the following principles:

[0471] Service data units of the same TA and SCSID use the same replay counter, and service data units of different TA and SCSID use different replay counters;

[0472] Service data units of the same latency requirement use the same replay counter, and service data units of different latency requirement use different replay counters;

[0473] The replay counters corresponding to the at least two service data units are different.

[0474] In some embodiments, upon receiving the third service data unit, replay detection is performed on the third service data unit based on the replay counter indicated by the fifth field for the third service data unit.

[0475] In some embodiments, the first frame further comprises a sixth field for extending the sequence size of the buffer, and the sixth field and the field in the first field for indicating the sequence size jointly indicate the sequence size of the buffer.

[0476] In some embodiments, the first frame further comprises a seventh field for extending the TXOP duration required by the at least one service data unit, and the seventh field and the field in the first field for indicating the TXOP duration jointly indicate the TXOP duration required by the at least one service data unit.

[0477] In some embodiments, the first frame further comprises an eighth field for indicating that the access point needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

[0478] In some embodiments, when the eighth field is of a first value, it is used to indicate that the access point needs to send a basic trigger frame for channel resource allocation and trigger uplink transmission.

[0479] In some embodiments, when the eighth field is of a second value, it is used to indicate that the access point needs to send a MU RTS TXS frame for channel resource allocation or sharing.

[0480] It should be noted that the apparatus provided by the above embodiments is only used as an example to illustrate the division of the functional modules in achieving the functions thereof, and in actual applications, the above functions can be completed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules to complete all or part of the above-described functions.

[0481] FIG. 11 shows a structural schematic diagram of a communication device provided by an embodiment of the present application. The communication device can include a processor 901, a receiver 902, a transmitter 903, a memory 904 and a bus 905.

[0482] The processor 901 includes one or more processing cores. The processor 901 performs various functional applications and information processing by running software programs and modules.

[0483] The receiver 902 and the transmitter 903 can be implemented as a transceiver 906, which can be a communication chip.

[0484] The memory 904 is connected to the processor 901 through the bus 905. The memory 904 can be used to store computer programs, and the processor 901 is used to execute the computer programs to implement various steps performed by the AP and / or the STA in the above method embodiments.

[0485] In addition, the memory 904 can be implemented by any type of volatile or non-volatile storage devices or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technology, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc), or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices.

[0486] The embodiment of the present application further provides a computer readable storage medium, wherein the storage medium stores a computer program, and the computer program is used for a processor of a communication device to implement each step in the wireless signal sending method and / or receiving method. In some embodiments, the computer readable storage medium can include a ROM (Read-Only Memory), a RAM (Random-Access Memory), a SSD (Solid State Drives), an optical disc or the like. The random access memory can include a ReRAM (Resistance Random Access Memory) and a DRAM (Dynamic Random Access Memory).

[0487] The embodiment of the present application further provides a chip, which includes a programmable logic circuit and / or program instructions, and when the chip is run on a terminal or a network device, is used to implement each step in the buffer status report sending method and / or receiving method.

[0488] The embodiment of the present application further provides a computer program product or a computer program, which includes computer instructions stored in a computer readable storage medium, and a processor of a terminal or a network device reads and executes the computer instructions from the computer readable storage medium, to implement each step in the buffer status report sending method and / or receiving method.

[0489] Those skilled in the art should be aware that, in one or more examples described above, the functions described in the embodiments of the present application can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium. The computer readable medium includes a computer storage medium and a communication medium, wherein the communication medium includes any medium that facilitates the transfer of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0490] The above description is only exemplary embodiments of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method of transmitting a buffer status report, characterized by, The method is performed by a station, and the method comprises: sending a first frame, the first frame being used to indicate a size of a buffer and a latency requirement of at least one service data unit.

2. The method of claim 1, wherein, The first frame comprises: a first field used to indicate the size of the buffer of the at least one service data unit; a second field used to indicate the latency requirement.

3. The method of claim 2, wherein, The first field comprises at least one of the following fields: a field used to indicate an average bit number of the at least one service data unit; a field used to indicate a number of the at least one service data unit; a field used to indicate a size proportion of a sum of bit numbers of the at least one service data unit in a total bit number of the buffer; a field used to indicate a sequence size of the at least one service data unit; a field used to indicate a scaling factor of the at least one service data unit; a field used to indicate a required transmission opportunity (TXOP) duration of the at least one service data unit; a field used to indicate a required bandwidth of the at least one service data unit; a field used to indicate a required modulation and coding scheme (MCS) of the at least one service data unit.

4. The method of claim 2, wherein, The second field comprises at least one of the following fields: a field used to indicate an expiration time corresponding to each service data unit in the at least one service data unit; a field used to indicate an earliest expiration time corresponding to the at least one service data unit; a field used to indicate a latest expiration time corresponding to the at least one service data unit; a field used to indicate an offset value of the latest expiration time relative to the earliest expiration time; a field used to indicate an offset value of the earliest expiration time relative to the latest expiration time; a field used to indicate a latest time of a required channel resource of the at least one service data unit.

5. The method of claim 4, wherein, The latency requirement is represented by an absolute time, or the latency requirement is represented by an offset value relative to a sending time or a receiving time.

6. The method according to any one of claims 2 to 5, characterized in that, The first frame is a quality of service (QoS) null frame, and the first field and the second field are carried in at least one of a high throughput (HT) control field, an ultra high reliability (UHR) control field, and an extended HT control field of the QoS null frame; or The first frame is a QoS data frame, and the first field and the second field are carried in at least one of an HT control field, a UHR control field, and an extended HT control field of the QoS data frame.

7. The method of claim 6, wherein: the HT control field comprises an A control field, and the A control field is used to carry the first field and the second field; or all bits of the HT control field are used to carry the first field and the second field; or the UHR control field is used to carry the first field and the second field; or the HT control field and the extended HT control field are used to carry the first field and the second field.

8. The method according to any one of claims 2 to 7, characterized in that, The first frame further comprises: a third field used to indicate an identity corresponding to the at least one service data unit, the identity comprising at least one of an access category (AC), a traffic identifier (TID), and a stream classification service identifier (SCSID).

9. The method of claim 8, wherein, The third field comprises at least one of: an AC field; a TID field; an SCSID field; a field for indicating the number of the identities; a partial SCSID field; wherein the concatenation of the TID field and the partial SCSID field is a complete SCSID.

10. The method according to claim 8 or 9, characterized in that, The first frame is a quality of service null frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the quality of service null frame; or, The first frame is a quality of service data frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the quality of service data frame.

11. The method of claim 9, wherein, The first frame is a quality of service null frame, and the TID field is carried in a QoS control field of the quality of service null frame, and the partial SCSID field is carried in at least one of an HT control field, a UHR control field and an extended HT control field of the quality of service null frame.

12. The method according to any one of claims 1 to 11, characterized in that, The first frame further comprises: a fourth field for indicating a sequence number corresponding to the at least one service data unit.

13. The method of claim 12, wherein, The fourth field comprises at least one of: a field for indicating a minimum sequence number corresponding to the at least one service data unit; a field for indicating a maximum sequence number corresponding to the at least one service data unit; a field for indicating an offset value between the minimum sequence number and a sequence number of a current service data unit; a field for indicating an offset value between the maximum sequence number and a sequence number of a current service data unit; wherein the current service data unit is a service data unit carried in the first frame.

14. The method according to claim 12 or 13, characterized in that, The first frame is a quality of service null frame, and the fourth field is carried in at least one of a sequence control field, an HT control field, a UHR control field and an extended HT control field of the quality of service null frame.

15. The method according to any one of claims 1 to 14, characterized in that, The first frame further comprises: a fifth field for indicating a replay counter used by the at least one service data unit in replay detection.

16. The method of claim 15, wherein, The fifth field complies with at least one of the following principles: service data units of a same transmission address (TA) and SCSID use a same replay counter, and service data units of different TAs and SCSIDs use different replay counters; service data units of a same delay requirement use a same replay counter, and service data units of different delay requirements use different replay counters; at least two service data units each correspond to different replay counters.

17. The method of claim 3, wherein, The first frame further comprises: a sixth field for extending indication of a sequence size of the buffer, and the sixth field and a field in the first field for indicating the sequence size jointly indicate the sequence size of the buffer.

18. The method of claim 3, wherein, The first frame further comprises: a seventh field for extending indication of a TXOP duration required by the at least one service data unit, and the seventh field and a field in the first field for indicating the TXOP duration jointly indicate the TXOP duration required by the at least one service data unit.

19. The method of any one of claims 1 to 17, wherein, The first frame further comprises: An eighth field for indicating that the AP needs to send a basic trigger frame or an MU RTS TXS frame for channel resource allocation or sharing.

20. The method of claim 19, wherein, when the eighth field takes a first value, the eighth field is configured to indicate that the AP needs to send the basic trigger frame for channel resource allocation or sharing and trigger uplink transmission; and when the eighth field takes a second value, the eighth field is configured to indicate that the AP needs to send the MU RTS TXS frame for channel resource allocation or sharing.

21. A method of receiving a buffer status report, characterized by, The method is performed by an access point, and the method comprises: receiving a first frame, wherein the first frame is configured to indicate a size of a buffer and a latency requirement for at least one service data unit.

22. The method of claim 21, wherein, The first frame comprises: a first field for indicating the size of the buffer for the at least one service data unit; and a second field for indicating the latency requirement.

23. The method of claim 22, wherein, The first field comprises at least one of: a field for indicating an average number of bits of the at least one service data unit; a field for indicating a number of the at least one service data unit; a field for indicating a size ratio of a sum of bit numbers of the at least one service data unit to a total number of bits of the buffer; a field for indicating a sequence size of the at least one service data unit; a field for indicating a scaling factor of the at least one service data unit; a field for indicating a required TXOP duration of the at least one service data unit; a field for indicating a required bandwidth of the at least one service data unit; and a field for indicating a required MCS of the at least one service data unit.

24. The method of claim 22, wherein, The second field comprises at least one of: a field for indicating an expiration time corresponding to each service data unit of the at least one service data unit; a field for indicating an earliest expiration time corresponding to the at least one service data unit; a field for indicating a latest expiration time corresponding to the at least one service data unit; a field for indicating an offset value of the latest expiration time relative to the earliest expiration time; a field for indicating an offset value of the earliest expiration time relative to the latest expiration time; and a field for indicating a latest time of required channel resource of the at least one service data unit.

25. The method of claim 24, wherein, The latency requirement is represented by an absolute time, or the latency requirement is represented by an offset value relative to a sending time or a receiving time.

26. The method of any one of claims 22 to 25, wherein, The first frame is a quality of service null frame, and the first field and the second field are carried in at least one of a HT control field, a UHR control field, and an extended HT control field of the quality of service null frame; or The first frame is a quality of service data frame, and the first field and the second field are carried in at least one of a HT control field, a UHR control field, and an extended HT control field of the quality of service data frame.

27. The method of claim 26, wherein, the HT control field comprises an A control field, and the A control field is configured to carry the first field and the second field; or all bits of the HT control field are configured to carry the first field and the second field; or The UHR control field is used to carry the first field and the second field; or The HT control field and the extended HT control field are used to carry the first field and the second field.

28. The method of any one of claims 22 to 27, wherein, The method further comprises: In a case that a first service data unit is received and a second service data unit located before the first service data unit in a receiving reordering buffer is not successfully received, the first service data unit is delivered to a next MAC processing flow at an expiration time corresponding to the first service data unit.

29. The method of any one of claims 22 to 28, wherein, The first frame further comprises: A third field used to indicate an identity corresponding to the at least one service data unit, the identity comprising at least one of an AC, a TID and an SCSID.

30. The method of claim 29, wherein, The third field comprises at least one of: an AC field; a TID field; an SCSID field; a field used to indicate a number of the identity; a partial SCSID field; A concatenation of the TID field and the partial SCSID field is a complete SCSID.

31. The method of claim 29 or 30, wherein, The first frame is a quality of service null frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the quality of service null frame; or The first frame is a quality of service data frame, and the third field is carried in at least one of a QoS control field, an HT control field, a UHR control field and an extended HT control field of the quality of service data frame.

32. The method of claim 31, wherein, The first frame is a quality of service null frame, and the TID field is carried in a QoS control field of the quality of service null frame, and the partial SCSID field is carried in at least one of an HT control field, a UHR control field and an extended HT control field of the quality of service null frame.

33. The method of any one of claims 22 to 32, wherein, The first frame further comprises: A fourth field used to indicate a sequence number corresponding to the at least one service data unit.

34. The method of claim 33, wherein, The fourth field comprises at least one of: a field used to indicate a minimum sequence number corresponding to the at least one service data unit; a field used to indicate a maximum sequence number corresponding to the at least one service data unit; a field used to indicate an offset value between the minimum sequence number and a sequence number of a current service data unit; a field used to indicate an offset value between the maximum sequence number and the sequence number of the current service data unit; The current service data unit is a service data unit carried in the first frame.

35. The method of claim 33 or 34, wherein, The first frame is a quality of service null frame, and the fourth field is carried in at least one of a sequence control field, an HT control field, a UHR control field and an extended HT control field of the quality of service null frame.

36. The method of any one of claims 22 to 35, wherein, The first frame further comprises: A fifth field used to indicate a replay counter used by the at least one service data unit in replay detection.

37. The method of claim 36, wherein, The fifth field complies with at least one of the following principles: service data units of a same TA and SCSID use a same replay counter, and service data units of different TAs and SCSIDs use different replay counters; service data units of a same delay requirement use a same replay counter, and service data units of different delay requirements use different replay counters; The replay counters corresponding to the at least two service data units are different.

38. The method of claim 36, wherein, The method further comprises: In case a third service data unit is received, performing replay detection on the third service data unit based on a replay counter indicated for the third service data unit by the fifth field.

39. The method of claim 23, wherein, The first frame further comprises: a sixth field for extending the fifth field to indicate a sequence size of the buffer.

40. The method of claim 23, wherein, The first frame further comprises: a seventh field for extending the first field to indicate a TXOP duration required for the at least one service data unit.

41. The method of any one of claims 22 to 40, wherein, The first frame further comprises: an eighth field for indicating that the access point needs to send a basic trigger frame or a MU RTS TXS frame for channel resource allocation or sharing.

42. The method of claim 41, wherein, the eighth field is set to a first value to indicate that the access point needs to send the basic trigger frame for channel resource allocation and trigger uplink transmission; the eighth field is set to a second value to indicate that the access point needs to send the MU RTS TXS frame for channel resource allocation or sharing.

43. A device for transmitting a buffer status report, the device comprising: The apparatus comprises: a sending module configured to send a first frame, the first frame being used to indicate a size and latency requirement of a buffer for at least one service data unit.

44. A receiving device for a buffer status report, the device comprising: The apparatus comprises: a receiving module configured to receive a first frame, the first frame being used to indicate a size and latency requirement of a buffer for at least one service data unit.

45. A communications device, characterized by The communication device comprises: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the sending method and / or receiving method of the buffer status report according to any one of claims 1 to 42.

46. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, which is loaded and executed by the communication device to implement the sending method and / or receiving method of the buffer status report according to any one of claims 1 to 42.

47. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a computer readable storage medium, which are acquired by the communication device from the computer readable storage medium, so that the processor loads and executes to implement the sending method and / or receiving method of the buffer status report according to any one of claims 1 to 42.

Images