Buffer status report design

Abstract

The present disclosure relates to a method for enhanced buffer status reporting (BSR) in a wireless local area network system (e.g., such as an IEEE 802.11-based system in a wireless local area network). A wireless device may determine, via a buffer status report, that a queue size of a buffer exceeds a reportable limit, e.g., the buffer status report may be reported in a server quality (QoS) control field and / or a BSR subfield of a medium access control (MAC) header of a frame. In addition to this, the wireless device may report a queue size greater than the reportable limit, for example, based on the determination. The queue size greater than the reportable limit may be reported via the frame, e.g., may be carried in an A-control field of the MAC header of the frame.

Description

Technical Field

[0001] This application relates to wireless communications, including technologies and devices for enhanced buffer status reporting (BSR) in wireless local area network systems (e.g., IEEE 802.11-based systems).

[0002] Related technical descriptions

[0003] Wireless communication systems are ubiquitous. Furthermore, wireless communication technology has evolved from solely voice communication to also include the transmission of data such as the internet and multimedia content.

[0004] Mobile electronic devices or stations (STAs) or user equipment (UEs) may take the form of smartphones or tablets typically carried by users. One aspect of wireless communication, typically performed by mobile devices, may include wireless networking, for example, via a wireless local area network (WLAN), which may include devices operating according to one or more communication standards in the IEEE 802.11 family of standards. In a WLAN, certain services may be delayed while other communications within the network are being performed. In at least some cases, this can potentially lead to performance degradation for services where low latency is critical. Therefore, improvements in this area are expected. Summary of the Invention

[0005] This paper provides, in particular, implementation schemes for systems, apparatuses, and methods for implementing enhanced buffer status reporting (BSR) in wireless local area network systems (e.g., IEEE 802.11-based systems).

[0006] A wireless device may include: one or more antennas; one or more radio components operatively coupled to the one or more antennas; and a processor operatively coupled to the one or more radio components. The wireless device may be configured to establish a connection with an access point via a wireless local area network (WLAN) on one or more wireless links, or may be an access point configured to establish a connection with one or more other wireless devices via a WLAN on one or more wireless links. In some embodiments, the wireless device may operate in each of the plurality of wireless links using a corresponding radio component from the one or more radio components.

[0007] For example, in some implementations, the wireless device may determine that the queue size of the buffer exceeds a reportable limit via a buffer status report, for example, in the Server Quality of Service (QoS) control field and / or buffer status report subfield of the Media Access Control (MAC) header of the frame. Alternatively, the wireless device may, for example, report a queue size greater than the reportable limit based on this determination. The queue size greater than the reportable limit may be reported via the frame. In some cases, the queue size greater than the reportable limit may be carried in the A-control field of the MAC header of the frame. As an example, a first portion of the queue size may be reported via the QoS control field or the buffer status report subfield, and a second portion of the queue size may be reported via the A-control field.

[0008] As another example, in some implementations, the wireless device may determine the queue size of the buffer to be reported as part of a buffer status report. In addition, the wireless device may, for example, report the queue size in the buffer status report via a management frame based on this determination. The management frame may include and / or may be an action frame, such as a QoS action frame, a buffer status report frame, and / or an enhanced buffer status report frame.

[0009] As another example, in some implementations, the wireless device may determine the queue size of the buffer to be reported as part of a buffer status report. In addition, the wireless device may, for example, report the queue size in the buffer status report via a Multiple Block Acknowledgment (M-BA) frame based on this determination. The queue size may be reported via a Block Acknowledgment (BA) bitmap field of the M-BA frame. As an example, the BA bitmap field may include a TID field, a scaling factor field, an unscaled value field, and / or an unscaled value extension field.

[0010] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to cellular phones, tablet computers, accessory and / or wearable computing devices, portable media players, base stations, access points and other network infrastructure equipment, servers, unmanned aerial vehicles, unmanned aerial controllers, automobiles and / or motor vehicles, and any computing device in various other computing devices.

[0011] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0012] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0013] Figure 1 An example wireless communication system including a wireless device is illustrated according to some implementation schemes.

[0014] Figure 2 This is a block diagram illustrating an example wireless device according to some implementation schemes.

[0015] Figure 3 This is a block diagram illustrating example network elements or access points according to some implementation schemes.

[0016] Figure 4 This is a block diagram illustrating an example modem or baseband processor according to some implementation schemes.

[0017] Figure 5 Examples of MAC headers based on some implementation schemes are shown.

[0018] Figure 6 Examples of QoS control fields based on some implementation schemes are shown.

[0019] Figure 7 Examples of possible values ​​for the queue size subfield of the QoS control field are shown according to some implementation schemes.

[0020] Figure 8 , Figure 9 and Figure 10 Examples of A-control subfields according to some implementation schemes are shown.

[0021] Figure 11 Examples of management frames according to some implementation schemes are shown.

[0022] Figure 12 Example M-BA frames according to some implementation schemes are shown.

[0023] Figure 13 , Figure 14 and Figure 15 This is a flowchart illustrating an example method for performing an enhanced BSR in a wireless local area network system (e.g., such as an IEEE 802.11-based system) according to some implementation schemes.

[0024] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0025] the term

[0026] The following are definitions of the terms used in this disclosure:

[0027] Memory media—any of various types of non-transitory memory devices or storage devices. The term "memory media" is intended to include any computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDORAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. The term "memory media" may include two or more memory media that may reside in different locations (e.g., different computer systems connected via a network). Memory media may store program instructions (e.g., embodied in a computer program) that can be executed by one or more processors.

[0028] Carrier medium—such as memory media as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media that transmit signals (such as electrical signals, electromagnetic signals or digital signals).

[0029] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), server-based computer systems, wearable computers, networked appliances, internet-connected appliances, smartphones, television systems, grid computing systems, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0030] User equipment (UE) (or “UE device”) — any of various types of computer systems or devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone-based). ™ Android ™This includes mobile phones, tablet computers, portable gaming devices, laptops, wearable devices (e.g., smartwatches, smart glasses, smart goggles, head-mounted displays, etc.), portable internet devices, music players, data storage devices or other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily portable by a user and capable of wireless communication.

[0031] A wireless device or station (STA) is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. The terms "station" and "STA" are used similarly. A UE is an example of a wireless device.

[0032] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0033] Base station or access point (AP) — The term “base station” has the full breadth of its common meaning and includes at least a wireless communication station installed in a fixed location for communication as part of a wireless communication system. The term “access point” (or “AP”) is often associated with and used similarly to Wi-Fi-based communication.

[0034] A processing element (or processor) is a variety of elements or combinations of elements capable of performing functions in a device (e.g., a communication device or a network infrastructure device). A processor may include, for example: a processor and associated memory, circuitry such as an ASIC (Application-Specific Integrated Circuit), portions or circuitry of individual processor cores, an entire processor core, a processor array, programmable hardware devices such as a field-programmable gate array (FPGA), and / or a large portion of a system comprising multiple processors, as well as any combination of the above elements.

[0035] IEEE 802.11 refers to technologies based on the IEEE 802.11 wireless standard (such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11-2012, 802.11ac, 802.11ad, 802.11ax, 802.11ay, 802.11be, and / or other IEEE 802.11 standards). IEEE 802.11 technology can also be referred to as "Wi-Fi" or "Wireless Local Area Network (WLAN)" technology.

[0036] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In this context, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently powered on. Generally, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0037] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0038] Figures 1 to 2 —Wireless communication system

[0039] Figure 1 An example of a wireless communication system is shown. Note that... Figure 1 This represents one of many possibilities, and the features of this disclosure can be implemented as needed through any of various systems. For example, the situation described herein can be implemented in any type of wireless device. The wireless communication system described below is an example.

[0040] As shown in the figure, an exemplary wireless communication system includes an access point (AP) 102 that communicates with one or more wireless devices 106A, 106B, etc., via a transmission medium. Wireless devices 106A and 106B can be user equipment, such as a station (STA), a non-AP STA, an AP STA, a UE, or other WLAN devices.

[0041] STA 106 can be any device with wireless network connectivity, such as a mobile phone, handheld device, wearable device (e.g., such as a smartwatch, smart glasses, and / or head-mounted display), computer or tablet, unmanned aerial vehicle (UAV), unmanned aerial controller (UAC), automobile, or virtually any other type of wireless device. STA 106 may include a processor (processing element) configured to execute program instructions stored in memory. STA 106 can perform any of the methods described herein by executing one or more of such stored instructions. Alternatively or in addition, STA 106 may include programmable hardware elements such as FPGAs (Field-Programmable Gate Arrays), integrated circuits (e.g., ASICs), programmable logic devices (PLDs), and / or any of various other possible hardware components configured to perform (e.g., individually or in combination) any of the methods described herein or any portion of any of the methods described herein.

[0042] AP 102 can be a standalone AP or an enterprise AP, a transceiver base station (BTS) or a cell site, and may include hardware enabling wireless communication with STA devices 106A and 106B. AP 102 may also be equipped to communicate with network 100 (e.g., the core network of a service provider (e.g., a cellular service provider, internet service provider, and / or operator), a WLAN, an enterprise network, and / or another communication network connected to the internet, and various other possibilities). Therefore, AP 102 facilitates communication between STA devices 106 and / or communication between STA devices 106 and network 100. AP 102 can be configured to provide communication via one or more wireless technologies, such as any, any combination of, and / or all of the following: 802.11 a, 802.11 b, 802.11 g, 802.11 n, 802.11 ac, 802.11 ad, 802.11 ax, 802.11 ay, 802.11 be, and / or other 802.11 versions, and / or cellular protocols such as 6G, 5G, or LTE, including in unlicensed frequency bands.

[0043] The communication area (or coverage area) of AP 102 may be referred to as the Basic Service Area (BSA) or cell. AP 102 and STA 106 can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RAT) or wireless communication technologies such as Wi-Fi, LTE, Advanced LTE (LTE-A), 5G NR, 6G, Ultra Wideband (UWB), etc.

[0044] Therefore, AP 102 and other similar access points (not shown) operating according to one or more wireless communication technologies can be configured as a network that can provide continuous or location-specific services to STA devices 106A to 106B and similar devices within a geographical area, for example, via one or more communication technologies. STAs can roam directly from one AP to another, or can switch between APs and / or network cells (e.g., cellular network cells).

[0045] It should be noted that, at least in some cases, the STA device 106 can communicate using any of a variety of wireless communication technologies. For example, the STA device 106 can be configured to communicate using Wi-Fi, LTE, LTE-A, 5G NR, 6G, Bluetooth, UWB, one or more satellite systems, etc. Other combinations of wireless communication technologies (including more than two wireless communication technologies) are also possible. Similarly, in some cases, the STA device 106 can be configured to communicate using only a single wireless communication technology.

[0046] As shown in the figure, the exemplary wireless communication system may also include an access point (AP) 104 that communicates with the wireless device 106B via a transmission medium. AP 104 also provides a communication connection to network 100. Therefore, a wireless device can connect to either or both of AP 102 (or another cellular base station) and access point 104 (or another access point) to access network 100. For example, a STA may roam from AP 102 to AP 104 based on one or more factors such as mobility, coverage, interference, and / or capability. It should be noted that AP 104 may also allow access to networks different from those allowed by AP 102 (e.g., enterprise Wi-Fi networks, home Wi-Fi networks, etc.).

[0047] STA 106A and STA 106B may include handheld devices (such as smartphones or tablets), wearable devices (such as smartwatches, smart glasses, head-mounted displays), and / or may include any device of various types with wireless communication capabilities. For example, one or more of STA 106A and / or STA 106B may be wireless devices designed for fixed or nomadic deployments, such as home appliances, measuring devices / sensors, control devices, etc.

[0048] STA 106B can also be configured to communicate with STA 106A. For example, STA 106A and STA 106B may be able to perform direct device-to-device (D2D) communication. It should be noted that such direct communication between STAs may also be referred to as, or alternatively as, peer-to-peer (P2P) communication. Direct communication may be supported by AP 102 (e.g., AP 102 may facilitate discovery, and various possible forms of assistance), or may be performed in a manner not supported by AP 102. According to various examples, such P2P communication may be performed using any of the following direct communication technologies: 3GPP-based D2D communication technology, Wi-Fi-based P2P communication technology, UWB, BT, and / or various other direct communication technologies.

[0049] STA 106 may include one or more devices or integrated circuits for facilitating wireless communication, potentially including Wi-Fi modems, cellular modems, and / or one or more other wireless modems. The wireless modem may include one or more processors (processor elements) and various hardware components as described herein. STA 106 may perform any method (or any part thereof) of the methods described herein by executing instructions on one or more programmable processors. For example, STA 106 may be configured to perform techniques such as enhanced BSRs for wireless communication systems according to the various methods described herein. Alternatively or otherwise, the one or more processors may be one or more programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), application-specific integrated circuits (ASICs), or other circuitry configured to perform any method or any part thereof of the methods described herein. The wireless modem described herein may be used in STA devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The wireless modem described herein may also be used in APs, base stations, picocells, femtocells, and / or other similar network-side devices.

[0050] STA 106 may include one or more antennas for communicating using two or more wireless communication protocols or radio access technologies (RATs). In some cases, STA device 106 may be configured to communicate using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Alternatively, STA device 106 may include two or more radio components, each of which may be configured to communicate via a corresponding wireless link. Other configurations are also possible.

[0051] Figure 2–Example block diagram of STA device

[0052] Figure 2 An example block diagram of a STA device (such as STA 106) is illustrated. In some cases, STA 106 may additionally or alternatively be referred to as UE 106. STA 106 may also be referred to as a non-AP STA 106. As shown, STA 106 may include a System-on-Chip (SOC) 200, which may include one or more parts configured for various purposes. Some or all of the various illustrated components (and / or other device components not illustrated, e.g., in variant and alternative arrangements) may be “communically coupled” or “operationally coupled”, terms used herein to refer to components that can communicate directly or indirectly when the device is in operation.

[0053] In some cases, the STA 106 can be configured as a multi-link device (MLD). In such cases, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform concurrent data transmission and reception across a single frequency band and / or multiple frequency bands (e.g., such as the 2.4 GHz band, the 5 GHz band, and / or the 6 GHz band) on multiple channels. Therefore, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform multi-link operation (MLO). For example, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured such that a single radio component can simultaneously listen to two or more links).

[0054] As shown, the SOC 200 may include: a processor 202 that executes program instructions for the STA 106; and display circuitry 204 that performs graphics processing and provides display signals to the display 260. The SOC 200 may also include motion sensing circuitry 270, which may use, for example, any motion sensing component such as a gyroscope, accelerometer, and / or various other motion sensing components to detect motion of the STA 106 in one or more dimensions. The processor 202 may also be coupled to a memory management unit (MMU) 240, which may be configured to receive addresses from the processor 202 and translate these addresses into locations in memory (e.g., memory 206, read-only memory (ROM) 250, flash memory 210). The MMU 240 may be configured to perform memory protection and page table translation or setup. In some cases, the MMU 240 may be included as part of the processor 202.

[0055] As shown in the figure, SOC 200 can be coupled to various other circuits of STA 106. For example, STA 106 may include various types of memory (e.g., including NAND flash memory 210), connector interface 220 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 260, and wireless communication circuitry 230 (e.g., for LTE, LTE-A, 5G NR, 6G, Bluetooth, Wi-Fi, NFC, GPS, UWB, peer-to-peer (P2P), device-to-device (D2D), etc.).

[0056] STA 106 may include at least one antenna, and in some cases may include multiple antennas, such as 235A and 235B, for performing wireless communication with access points, base stations, wireless stations, and / or other devices. For example, STA 106 may use antennas 235A and 235B to perform wireless communication. As noted above, STA 106 may be configured in some examples to perform wireless communication using a variety of wireless communication standards or radio access technologies (RATs).

[0057] The wireless communication circuitry 230 may include a Wi-Fi modem 232, a cellular modem 234, and a Bluetooth modem 236. It should be noted that one or more of the Wi-Fi modem 232, cellular modem 234, and / or Bluetooth modem 236 may be configured for MLO, for example, as described above. The Wi-Fi modem 232 enables STA 106 to perform Wi-Fi or other WLAN communications, for example, on an 802.11 network. The Bluetooth modem 236 enables STA 106 to perform Bluetooth communications. The cellular modem 234 may be able to perform cellular communications according to one or more cellular communication technologies, for example, according to one or more 3GPP specifications.

[0058] As described herein, STA 106 may include hardware and software components for implementing aspects of this disclosure. For example, one or more components of the wireless communication circuitry 230 of STA 106 (e.g., Wi-Fi modem 232, cellular modem 234, BT modem 236) may be configured, for example, to implement part or all of the methods for enhanced BSR in a wireless local area network system described herein by means of a processor executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits).

[0059] Figure 3 —Block diagram of the access point

[0060] Figure 3 An example block diagram of Access Point (AP) 104 is shown. In some cases (e.g., in an 802.11 communication context), AP 104 may also be referred to as a Station (STA) or AP STA. Note that... Figure 3 The AP is merely one example of a possible access point. As shown, AP 104 may include a processor 304 capable of executing program instructions for AP 104. Processor 304 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from processor 304 and translate these addresses into locations in memory (e.g., memory 360 and read-only memory (ROM) 350), or into other circuitry or devices.

[0061] In some cases, AP 104 can be configured as a multi-link device (MLD). In such cases, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform concurrent data transmission and reception across a single frequency band and / or multiple frequency bands (e.g., such as the 2.4 GHz band, the 5 GHz band, and / or the 6 GHz band) on multiple channels. Therefore, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform multi-link operation (MLO). For example, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured such that a single radio component can be used to simultaneously listen on two or more links).

[0062] AP 104 may include at least one network port 370. Network port 370 may be configured to be coupled to a network and provide network access to multiple devices such as STA device 106, as described above in this document. Figure 1 As described in the text.

[0063] Network port 370 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider (e.g., an operator and / or cellular carrier). The core network may provide mobility-related services and / or other services to multiple devices, such as STA device 106. In some cases, network port 370 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other STA devices served by a cellular service provider).

[0064] AP 104 may include one or more radio components 330A-330N and at least one antenna 334 (and may include multiple antennas), which may be coupled to one or more corresponding communication links. Antenna 334 may be configured to operate as a wireless transceiver in conjunction with one or more other components, and may also be configured to communicate with STA device 106 via radio components 330A-330N. Note that one or more of the radio components 330A-330N may be configured for MLO, for example, as described above. Antennas 334A-N communicate with one or more corresponding radio components 330A-N via communication links 332A-N. Communication link 332 may be a receive link, a transmit link, or both. Radio components 330A-N may be configured to communicate according to various wireless communication standards, including but not limited to LTE, LTE-A, 5G NR, 6G, UWB, Wi-Fi, BT, etc. AP 104 may be configured to operate on multiple wireless links using one or more radio components 330A-N. In some implementations, each radio component can be used to operate on the corresponding wireless link.

[0065] AP 104 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, AP 104 may include multiple radio components that enable network entities to communicate according to various wireless communication technologies. For example, as one possibility, AP 104 may include 4G or 5G radio components for performing communication according to 3GPP wireless communication technologies, and Wi-Fi radio components for performing communication according to one or more Wi-Fi specifications. In this case, AP 104 may be able to operate as both a cellular base station and a Wi-Fi access point. As another possibility, AP 104 may include multimode radio components capable of performing communication according to any of the various wireless communication technologies (e.g., 5G NR and Wi-Fi, 5G NR and LTE, etc.). As yet another possibility, AP 104 may be configured to function exclusively as a Wi-Fi access point, for example, in the absence of cellular communication capabilities.

[0066] As further described herein, AP 104 may include hardware and software components for implementing or supporting the features described herein, such as an enhanced BSR in a wireless local area network system (e.g., a system based on IEEE 802.11), and various other possible features. The processor 304 of AP 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium) to operate multiple wireless links using multiple corresponding radio components. Alternatively, processor 304 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or otherwise), the processor 304 of AP 104, in conjunction with one or more of other components 330, 332, 334, 340, 350, 360, 370, may be configured to implement or support some or all of the features described herein.

[0067] Figure 4 —Block diagram of a modem or baseband processor

[0068] Figure 4 An example block diagram of a modem 400 is shown, which may also be referred to as a baseband processor 400. Modem 400 can provide signal processing functionality for one or more wireless communication technologies such as Wi-Fi, Bluetooth, and / or cellular (e.g., 3GPP) communication technologies. Therefore, as an option, modem 400 may represent a Wi-Fi modem; for example, Figure 4 The illustrated modem 400 can represent Figure 2 One possible example of the illustrated Wi-Fi modem 232. Alternatively, modem 400 could represent a cellular modem or a cellular baseband processor; for example... Figure 4 The illustrated modem 400 can represent Figure 2 One possible example of the illustrated cellular modem 234. As a further possibility, modem 400 could represent a Bluetooth modem; for example, Figure 4 The illustrated modem 400 can represent Figure 2 This is one possible example of the illustrated Wi-Fi modem 236. In some cases, modem 400 may implement functionality to support communication according to various wireless communication technologies. In at least some cases, modem 400 may run a real-time operating system, for example, to facilitate the performance of time-dependent wireless communication functionality.

[0069] In some cases, modem 400 can be configured to perform concurrent data transmission and reception across multiple channels in a single and / or multiple frequency bands (e.g., such as the 2.4 GHz band, 5 GHz band, and / or 6 GHz band). Therefore, modem 400 can be configured to perform multi-link operation (MLO). For example, modem 400 can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured to allow a single radio component to simultaneously listen to two or more links).

[0070] Modem 400 may include processing circuitry 402, which may include one or more processor cores, ASICs, programmable hardware elements, digital signal processors, and / or other processing elements. The processing circuitry may be able to prepare baseband signals for up-conversion and transmission by the radio circuitry of a wireless device, and / or process baseband signals for reception and down-conversion by the radio circuitry of the wireless device. Such processing may include signal modulation, encoding, decoding, etc., among various possible functions. The processing circuitry may also be able to, or alternatively, perform functionality of one or more baseband and / or other layers / sublayers of the protocol stack for a wireless communication technology implemented by modem 400, such as physical layer (PHY) functionality, media access control (MAC) functionality, logical link control (LLC) functionality, radio resource control (RRC) functionality, radio link control (RLC) functionality, etc. In some cases, modem 400 itself may include at least some radio circuitry (e.g., for performing input baseband signal to radio frequency signal conversion and / or input radio frequency signal to baseband signal conversion). Alternatively or additionally, some or all of these functions may be performed by separate radio / transceiver components of the wireless device.

[0071] The modem 400 may also include a memory 404, which may include a non-transitory computer-readable storage medium. The memory 404 may include program instructions for performing signal processing and / or any of the various possible general-purpose processing functions. The processing circuitry 402 may be able to execute the program instructions stored in the memory 404. The memory 404 may also store data generated and / or used during processing performed by the processing circuitry 402.

[0072] As shown in the figure, the modem 400 may also include, for example, for communication with wireless devices (such as...) Figures 1 to 3Interface circuitry that communicates with other components of the illustrated STA 106 or AP 104 (such as the application processor, radio / transceiver circuitry, and / or any of the various other components). Such an interface can be implemented in any of a variety of ways; for example, as one possibility, the modem 400 may have a direct interface to the transceiver circuitry of the wireless device and may have additional indirect interfaces via the system bus to the application processor and / or other components of the wireless device. Other configurations are also possible.

[0073] In at least some cases, the hardware and software components of modem 400 may be configured to implement or support the features described herein (such as an enhanced BSR in a wireless local area network system, e.g., a system based on IEEE 802.11) and various other possible features. For example, the processing circuitry 402 of modem 400 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on memory (e.g., a non-transitory computer-readable storage medium) 404 and / or using dedicated hardware components.

[0074] Enhanced BSR

[0075] In current implementations, for example, since at least the release of IEEE 802.11ax, Buffer Status Reports (BSRs) have been supported to assist Access Points (APs) in uplink scheduling. For instance, a BSR helps the AP allocate sufficient uplink resources in a trigger frame transmitted from the AP to the wireless station. In addition, to report a BSR, the wireless station can transmit it in a Quality of Service (QoS) data frame or a QoS empty frame. The wireless station can contend for media access and transmit a QoS frame (data or empty) to the AP (e.g., an unrequested BSR), or respond to a trigger frame received from the AP with a QoS frame (e.g., a requested BSR). A BSR can be included in the QoS control field or the BSR control subfield of the Media Access Control (MAC) header of the QoS frame.

[0076] In IEEE 802.11bn, reporting per-Service Identifier (TID) queues for larger queues under Ultra-High Reliability (UHR) is enabled as an optional feature. The maximum approximate queue size per TID that can be reported is limited to 2,147,328 octets. Currently, there is no mechanism for reporting larger queue sizes per TID. Therefore, improvements are expected.

[0077] The implementation described herein provides an enhanced Buffer Status Report (BSR). Specifically, the implementation described herein provides methods and mechanisms for reporting queue sizes per TID greater than 2,147,328 octets. For example, in some implementations, the A-control field in the MAC header can be used to report additional queue sizes exceeding 2,147,328 octets. In other words, the QoS / BSR control field can be used to indicate a buffer and / or queue size of 2,147,328 octets, and the A-control field can be used to report buffer and / or queue sizes exceeding 2,147,328 octets. As another example, in some implementations, the A-control field in the MAC header can be used to report buffer and / or queue sizes as part of the BSR. In other words, the A-control field can be used to report buffer and / or queue sizes regardless of their actual size.

[0078] For example, in some cases, a non-AP station (e.g., a wireless station, such as wireless station 106) may report a queue size larger than the current limit (e.g., 2,147,328 octets) via the A-control field in the MAC header, for example, in the buffer status report. Figure 5 As shown, the MAC header may include various fields such as a frame control field (2 octets), a duration field (2 octets), multiple address fields (up to 6 octets per address field) (e.g., address fields 1, 2, 3, and 4), a sequence control field (2 octets), a QoS (Quality of Service) control field (up to 2 octets), an HT field (up to 4 octets), a frame body field (the variable being length / size), and / or a frame checksum (FCS) field (4 octets). Additionally, as... Figure 6 As shown, the QoS control field may include up to 4 bits (e.g., bits 0 to 3) for specifying the Service Identifier (TID), up to 2 bits (e.g., bits 5 to 6) for indicating the acknowledgment policy indicator, 1 bit (e.g., bit 7) for indicating the presence of the Aggregated MAC Service Data Unit (A-MSDU), and up to 8 bits (e.g., bits 8 to 15) for indicating the queue size. In addition, Figure 7The possible values ​​for the queue size subfield of the QoS control field are illustrated. As shown, the range of queue size can be indicated by a combination of the scaling factor (SF) and the unscaled value (UE). Therefore, to indicate that a non-AP station has a queue size greater than the current limit to report, the non-AP station can use the queue size subfield in the MAC header of the frame.<SF, UV> The value is set to <3, 62>, where 3 indicates the scaling factor and 62 indicates the unscaled value. Additionally, non-AP stations may carry another subfield defined in the A-control field (e.g., a variant of the HT control field) in the frame's MAC header (e.g., such as...). Figure 8 (as illustrated), to indicate an additional amount of queue size that cannot be indicated in the QoS control field. Specifically, the additional amount of queue size can be indicated via the Unscaled Value Extension (UVE) field of the A-control field, where the value of the UVE can be a function of the queue size (QS), scaling factor (SF), and current limit (CL), for example, as shown in Equation [1].

[0079] [1]

[0080] In some cases, the scaling factor can remain constant between the QS subfield and the A-control frame. In other cases, the scaling factor can be indicated via the A-control frame, for example, by reusing the reserved bits illustrated. In some cases, the maximum value of the UVE that can be used in equation [1] can be set to 254, where the value 255 is reserved for a queue size greater than the maximum queue size that can be indicated for the UVE value 254. In some cases, the size (e.g., number of bits) of the UVE in the A-control field can be specified such that there are remaining bits in the A-control field for non-AP stations to report uplink power margins via the A-control field. For example, as Figure 8 As shown, the UVE field in the A-control field can be an 8-bit field, for example, an 8-bit UV field corresponding to an extension of the UV field in the QoS QS subfield. In some cases, the maximum reported QS can be limited to 10,470,400. Additionally, as shown, two bits can be reserved, for example, for later use, such as indicating a scaling factor.

[0081] In some cases, such as when the HT control field exists in an MPDU aggregated within an aggregated Media Access Control (MAC) Protocol Data Unit (A-MPDU), all MPDUs of the same frame type (e.g., with the same value for the type subfield of the frame control field) within that A-MPDU contain the same HT control field. This can be challenging when reporting large queue sizes for more than one TID, as all A-MPDUs will contain the same HT control field. It should be noted that non-AP STAs can aggregate BSRs for up to eight TIDs by transmitting A-MPDUs with QoS empty frames. Therefore, in some cases, A-MPDUs can be configured to carry different A-control values ​​when used to report enhanced BSRs for more than one TID. Such a scheme can be used by client devices to report enhanced BSRs in A-MPDUs with multiple QoS empty frames, each carrying a single TID BSR. Furthermore, in some cases, A-MPDUs can be configured to carry different A-control field values ​​when used to report enhanced BSRs from more than one TID. In such cases, a limit can be defined on the number of different A-control field values ​​that can be included in the A-MPDU, for example, to limit complexity. For instance, this limit could be set to 2, 4, and / or 8 TIDs. Additionally, in some other cases, an A-control field can be defined that carries an enhanced BSR corresponding to a single TID, for example, such as... Figure 9 As illustrated. In such cases, all A-control subfields in the A-MPDU can carry the same content, and the A-control subfield carrying the enhanced BSR can have additional subfields to indicate the TID corresponding to the enhanced BSR, for example, such as Figure 9 As illustrated, such a field can be 4 bits (or more or fewer bits). Note that for other TIDs, client devices (e.g., non-AP STAs) may follow a baseline (e.g., traditional) mechanism to indicate that they carry more than 2,147,328 octets (if any).

[0082] Additionally, in some cases, an A-control field can be defined that carries an enhanced BSR corresponding to multiple TIDs (e.g., more than one TID). In some cases, TIDs corresponding to one or more specific access classes (ACs) can be included in the A-control subfield. For example, ACs corresponding to video (AC_VI) and / or voice (AC_VO) can be included in the A-control field. In such schemes, these TIDs can be reported sequentially, such as TID 4, 5, 6, 7, 8, etc. Furthermore, zero or special values ​​can be reported when no additional queue size is attached for a particular TID. Additionally, if a fixed scaling factor is assumed, each TID can use 6 bits (instead of 8 bits), resulting in a total of 24 bits and allowing 2 bits to be reserved for future use (e.g., future definition). Therefore, in such cases, the A-control information length can be up to 26 bits. As another example, the TID corresponding to video (AC-VI) and best-effort (AC_BE) can be included in the A-control field, for example, because AC_VO can have a shallow buffer and may not require BSR extension. In such cases, a 6-bit UVE corresponding to the extension of the UV reported in the QoS QS subfield can be reported on a per-TID basis, for example, such as Figure 10 As illustrated, the A-control subfield may include a control ID value and multiple 6-bit UVE fields, such as UVE TID 4, UVE TID 5, UVE TID 0, and UVE TID 3. In some cases, a larger scaling factor (SF) (e.g., a multiple of 32,768) may be used to ensure that the expected maximum queue size value is reported overridden.

[0083] In some cases, management frames can be used to instruct additional BSRs (and / or existing BSRs). For example, action frames can be defined for existing categories (e.g., QoS action frames) or new categories to report BSRs and / or additional BSRs (e.g., enhanced BSRs). In such cases, stations can use such management frames to report BSRs / enhanced BSRs. Figure 11 Examples of management frames for reporting BSR / enhanced BSR according to some implementation schemes are illustrated. As shown, such management frames may include frame control fields, duration fields, destination address (DA) fields, sender address (SA) fields, basic service set (BSS) identifier (ID) fields, sequence control fields, category fields, action fields, field / element fields, and / or frame checksum (FCS) fields. In some cases, as shown, the action and field / element fields may include BSR information for one or more TIDs. For example, this BSR information may include TID fields, scaling factor (SF) fields, unscaled value (UV) fields, and / or UVE fields.

[0084] In some cases, assuming that Multi-Station Block Acknowledgment (M-BA) frames are being considered for providing feedback in Ultra-High Reliability (UHR) mode, enhanced BSRs can be incorporated into M-BA frames. In some cases, a per-Associated Identifier (AID) TID information field can be defined in the M-BA frame to report BSRs and / or enhanced BSRs. Such schemes allow the aggregation of BSRs / enhanced BSRs for multiple TIDs in one or more per-AID TID information fields using a single M-BA frame. Furthermore, such feedback can be aggregated with other per-AID TID information fields carrying other feedback, such as coexistence.

[0085] For example, Figure 12An M-BA frame according to some implementation schemes is illustrated. As shown, an M-BA frame may include a frame control field, a duration field, a receiver address (RA) field, a transmitter address (TA) field, a block acknowledgment (BA) control field, a frame checksum (FCS) field, and / or a BA information field. The frame control field may include 2 octets. The duration field may include 2 octets. The RA field may include 6 octets. The TA field may include 6 octets. The BA control field may include 2 octets. The FCS field may include 4 octets. However, in other specific implementations, any / all of these fields may include a different number of octets. Additionally, the length of the BA information field may be variable. The BA information field may include one or more per-AID TID information fields. For example, as shown, the per-AID TID information field may include an AID TID information field, a block acknowledgment start sequence control field, and a block acknowledgment bitmap field containing and / or including feedback information. The AID TID information field may include a 16-bit sum field for AID 11, acknowledgment (ACK) type, and TID. In some implementations, the ACK type field and / or TID field may be used to indicate the type of per-AID TID information used for feedback. The block ACK start sequence control field may include 16 bits, with 4 bits used for the fragment number field and 12 bits used for the start sequence number field. In other implementations, one or more other bit lengths may be used. The fragment number field may provide and / or indicate the length of the feedback (e.g., the length of the enhanced BSR in the block ACK bitmap subfield). The start sequence number field may indicate the type of feedback, such as whether the feedback is an enhanced BSR. The block ACK bitmap field may include a TID field, a scaling factor (SF) field, an unscaled value (UV) field, and / or an enhanced UV (UVE) field. In some implementations, the UVE field may be optional. In some implementations, the SF and UV fields may be used as a baseline for calculating the initial queue size, and the product of the values ​​indicated in the SF and UVE fields may be added to this baseline to determine the final queue size. In some implementations, SF and UV may be defined to cover queue sizes up to 10,470,400.

[0086] Figure 13 , Figure 14 and Figure 15 This is a flowchart illustrating example methods for performing an enhanced BSR in a wireless local area network system (e.g., such as an IEEE 802.11-based system) according to some implementation schemes. In various implementation schemes, some of the elements shown may be performed concurrently in a different order than shown, may be replaced by one or more other elements, or may be omitted. Additional elements may also be performed as needed.

[0087] Figure 13 , Figure 14 and Figure 15 The elements of the element can be generated by wireless devices (such as, Figures 1 to 4 This can be implemented as illustrated and relative to the AP 104 or STA 106 described in these figures, or more generally, it can be implemented as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures. For example, the processor of such a device (such as in...) Figure 4 The illustrated and described baseband processor 400 and / or other hardware may be configured to cause the device to perform any combination of the elements shown and / or other elements.

[0088] It should be noted that Figure 13 , Figure 14 and Figure 15 At least some of the elements are described in a manner relating to the use of communication technologies and / or features associated with the IEEE 802.11 specification document, but such description is not intended to limit this disclosure, and Figure 13 , Figure 14 and Figure 15 All aspects of the elements can be used in any suitable wireless communication system as needed. Go to Figure 13 As shown in the figure, this method can be operated as follows.

[0089] At 1302, the wireless device and / or the baseband processor of the wireless device (such as wireless device 106) may determine that the queue size of the buffer exceeds the reportable limit via a buffer status report, for example, in the Server Quality of Service (QoS) control field and / or the buffer status report subfield of the Media Access Control (MAC) header of the frame.

[0090] At 1304, the wireless device and / or the baseband processor of the wireless device may, for example, report a queue size greater than the reportable limit based on the determination.

[0091] For example, in some cases, a queue size exceeding the reportable limit may be reported via the A-Control field in the MAC header of the frame. In some cases, a first portion of the queue size may be reported via the QoS Control field or the Buffer State Report subfield. Additionally, a second portion of the queue size may be reported via the A-Control field. The first portion may be indicated as a range via a combination of a scaling factor field and an unscaled value field for the queue size. Alternatively, the second portion may be an additional amount of the queue size exceeding the reportable limit. As an example, the second portion may be indicated via an unscaled value extension field. The value of the unscaled value extension field may be a function of the queue size, the reportable limit, and the scaling factor. As another example, the second portion may be indicated via an unscaled value extension field and a scaling factor field. Furthermore, the value of the scaling factor field in the A-Control field may differ from the value of the scaling factor field in the QoS Control field or the Buffer State Report subfield.

[0092] In some cases, the A-control field may include an unscaled value extension field and a scaling factor field. The queue size may be reported as a function of the values ​​of the unscaled value extension field and the scaling factor field. Additionally, the A-control field may include a Service Identifier (TID) field. In some cases, the frame may be the first frame included in an Aggregated MAC Protocol Data Unit (A-MPDU). In such cases, the queue size may be the first queue size associated with the first TID, and the A-MPDU may also include at least a second frame associated with the second TID. Furthermore, in such cases, the wireless device and / or the baseband processor of the wireless device may determine, via the buffer status report in the QoS control field or buffer status report subfield of the MAC header of the second frame, that the second queue size associated with the second TID in the buffer exceeds the reportable limit, and based on this determination, report the second queue size exceeding the reportable limit via the A-control field of the MAC header of the second frame.

[0093] In some cases, the A-control field may include an unscaled value extension field and a scaling factor field. The queue size may be reported as a function of the values ​​of the unscaled value extension field and the scaling factor field. Additionally, the A-control field may include a TID field. In some cases, the frame may be the first frame included in the A-MPDU, and the queue size may be a first queue size associated with a first TID. Furthermore, the A-MPDU may include at least a second frame associated with a second TID, and the TID field may indicate the TID associated with the queue size.

[0094] In some cases, the A-control field may include an unscaled value extension field and a scaling factor field. The queue size may be reported as a function of the values ​​of the unscaled value extension field and the scaling factor field. Additionally, the A-control field may include a TID field. In some cases, the frame may be the first frame included in the A-MPDU, and the queue size may be a first queue size associated with the first TID. Furthermore, the A-MPDU may include at least a second frame associated with a second TID, and the TID field may indicate the access category associated with the queue size.

[0095] In some cases, the A-control field may include an unscaled value extension field and a scaling factor field. The queue size may be reported as a function of the values ​​of the unscaled value extension field and the scaling factor field. Additionally, the A-control field may include a TID field. In some cases, the frame may be the first frame included in the A-MPDU, and the queue size may be a first queue size associated with the first TID. The A-MPDU may also include at least a second frame associated with a second TID, and the TID field may include one or more TID fields. The one or more TID fields may be associated with an access category, and the queue size may be applicable to the TID associated with that access category.

[0096] In some cases, the A-control field may include one or more unscaled value extension fields. In such cases, a first unscaled value extension field may correspond to a first TID, and at least a second unscaled value extension field may correspond to a second TID. The first service TID may be associated with a first access category. Alternatively, the second service TID may be associated with a second access category.

[0097] As another example, in some cases, the queue size may be carried in a management frame. This management frame may include and / or may be an action frame. The action frame may include and / or may be a QoS action frame, a buffer status report frame, and / or an enhanced buffer status report frame. In some cases, the management frame may include at least an action field and a field / element field. The action field and the field / element field may include information associated with the buffer status report. This information may include a TID field, a scaling factor field, an unscaled value field, and / or an unscaled value extension field.

[0098] As another example, in some cases, the queue size can be carried in a Multi-Block Acknowledgment (M-BA) frame. The queue size can be reported via the BA bitmap field of the M-BA frame. The BA bitmap field may include a TID field, a scaling factor field, an unscaled value field, and / or an unscaled value extension field. In some cases, the values ​​of the scaling factor field and the unscaled value field can be used to indicate the initial queue size. Alternatively, the product of the scaling factor field value and the unscaled value extension field value can be added to the initial queue size to determine the queue size. In some cases, the buffer status report can be a per-Associated Identifier (AID) TID information field. Additionally, the buffer status report can be aggregated with other per-AID TID information fields to carry additional feedback. This additional feedback may include at least coexistence information.

[0099] Go to Figure 14 As shown in the figure, this method can be operated as follows.

[0100] At 1402, the wireless device and / or the baseband processor of the wireless device (such as wireless device 106) can determine the queue size of the buffer to be reported as part of the buffer status report.

[0101] At 1404, the wireless device and / or its baseband processor may, for example, report the queue size in the buffer status report via a management frame based on this determination. The management frame may include and / or may be an action frame. The action frame may include and / or may be a QoS action frame, a buffer status report frame, and / or an enhanced buffer status report frame. In some cases, the management frame may include at least an action field and a field / element field. The action field and the field / element field may include information associated with the buffer status report. This information may include a TID field, a scaling factor field, an unscaled value field, and / or an unscaled value extension field.

[0102] Go to Figure 15 As shown in the figure, this method can be operated as follows.

[0103] At 1502, the wireless device and / or the baseband processor of the wireless device (such as wireless device 106) can determine the queue size of the buffer to be reported as part of the buffer status report.

[0104] At 1504, the wireless device and / or its baseband processor may, for example, report the queue size in the buffer status report via an M-BA frame based on this determination. The queue size may be reported via the BA bitmap field of the M-BA frame. The BA bitmap field may include a TID field, a scaling factor field, an unscaled value field, and / or an unscaled value extension field.

[0105] In some cases, the values ​​of the scaling factor field and the unscaled value field can be used to indicate the initial queue size. Alternatively, the queue size can be determined by adding the product of the scaling factor field value and the unscaled value extension field value to the initial queue size.

[0106] In some cases, the buffer status report may be a per-Associated Identifier (AID) TID information field. Alternatively, the buffer status report may be aggregated with other per-AID TID information fields to carry additional feedback. This additional feedback may include at least coexistence information.

[0107] Therefore, according to Figure 13 , Figure 14 and Figure 15 This approach could potentially provide enhanced buffer status reporting in WLAN settings, for example, by offering better efficiency in terms of report queue size. At least according to some implementations, such techniques can reduce throughput loss and improve power consumption.

[0108] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0109] In addition to the exemplary embodiments described above, further embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0110] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0111] In some implementations, the device (e.g., AP 104 or STA 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from the memory medium and execute the program instructions, wherein the program instructions are executable to implement any method implementation (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets) of the various method implementations described herein. The device may be implemented in any of a variety of forms.

[0112] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for providing a buffer status report, the method comprising: The buffer queue size exceeding the reportable limit is determined at least based on the buffer status report in the Server Quality of Service (QoS) control field or the buffer status report subfield of the frame's Media Access Control (MAC) header; and Based at least on the determination, the report is larger than the reported buffer queue size.

2. The method according to claim 1, The buffer queue size that is larger than the reportable limit is indicated in the Enhanced Buffer Status Report (EBSR) in the A-Control field of the MAC header of the frame.

3. The method according to claim 2, The EBSR includes at least the queue size indicator field and the business identifier (TID) field.

4. The method according to claim 3, The value of the buffer queue size indicator field is based on an unscaled value, which is a function of the queue size, scaling factor, and the reportable limit.

5. The method according to claim 3, The frame is associated with an Aggregated MAC Protocol Data Unit (A-MPDU), the buffer queue size is the size of a first buffer queue associated with a first TID, and the A-MPDU also includes at least a second frame associated with a second TID.

6. The method according to claim 5, further comprising: The buffer's second buffer queue size associated with the second TID exceeds the reportable limit, as determined by the QoS control field or the buffer status report subfield in the MAC header of the second frame. as well as Based on the determination, a second buffer queue size greater than the reportable limit is reported via the A-control field of the MAC header of the second frame.

7. The method according to claim 3, in, The TID field: Indicates the TID associated with the size of the buffer queue; Indicates the access category associated with the size of the buffer queue; or It includes one or more TID fields associated with the access category, and wherein the buffer queue size is adapted to the TID associated with the access category.

8. The method according to claim 3, The buffer queue size indicator field consists of 8 bits, and the TID field consists of 4 bits.

9. The method according to claim 1, The A-Control field of the MAC header includes two or more unscaled value extension fields.

10. The method according to claim 1, The first unscaled value extension field corresponds to the first business identifier (TID) associated with the first access category, and at least the second unscaled value extension field corresponds to the second TID associated with the second access category.

11. The method according to claim 1, Wherein the buffer queue size that is larger than the reportable limit is carried in the A-control field of the MAC header of the frame; The first portion of the buffer queue size is reported via the QoS control field or the buffer status report subfield; and The second part of the buffer queue size is reported via the A-control field.

12. The method according to claim 11, The first portion is indicated as a range via a combination of the scaling factor field and the unscaled value field of the queue size, and the second portion is an additional amount of the buffer queue size that is greater than the reportable limit.

13. The method according to claim 11, The second part is indicated via an unscaled value extended field; and The value of the unscaled value extension field is a function of the buffer queue size, the reportable limit, and the scaling factor.

14. The method according to claim 11, The second part is indicated via the unscaled value extension field and the scaling factor field; and The value of the scaling factor field in the A-control field is different from the value of the scaling factor field in the QoS control field or the buffer status report subfield.

15. The method according to claim 11, The A-control field mentioned therein includes one or more unscaled value extension fields.

16. The method according to claim 15, The first unscaled value extension field corresponds to the first business identifier (TID), and at least the second unscaled value extension field corresponds to the second TID; Wherein the first TID is associated with the first access category; and The second TID is associated with the second access category.

17. The method according to claim 1, The buffer queue size that is larger than the reportable limit is carried in the management frame.

18. A baseband processor, the baseband processor comprising: Memory; and A processing circuit, which communicates with the memory and is configured to cause the wireless station to perform operations including the method according to any one of claims 1 to 17.

19. A wireless station, the wireless station comprising: One or more antennas; One or more radio components, said one or more radio components being operatively coupled to said one or more antennas; and A baseband processor, the baseband processor being operatively coupled to the one or more radio components; and The baseband processor is configured to cause the wireless station to perform the method according to any one of claims 1 to 17.

20. A computer program comprising instructions executable by processing circuitry to cause a wireless station to perform the method according to any one of claims 1 to 17.

Images