Techniques for buffer status reporting

Abstract

The application relates to devices and components including apparatuses, systems, and methods for buffer status reporting in wireless networks.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 414,843, filed on October 10, 2022, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] The present application relates generally to communication networks, and in particular to techniques for buffer status reporting in such networks. Background Art

[0004] Buffer status reporting is an important mechanism for user equipment (UE) to inform the base station of the amount of uplink data that has arrived in the UE's buffer. The base station can use this information to allocate uplink resources to accommodate the buffered data. Details on the use of buffer status reporting in a 3rd Generation Partnership Project (3GPP) network are provided in 3GPP Technical Specification v17.2.0 (2022-10-01). BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 A network environment according to some embodiments is illustrated.

[0006] Figure 2 Configurable mappings according to some embodiments are illustrated.

[0007] Figure 3 Signaling diagrams according to some embodiments are illustrated.

[0008] Figure 4 Configurable mappings according to some embodiments are illustrated.

[0009] Figure 5 Signaling diagrams according to some embodiments are illustrated.

[0010] Figure 6 An operational flow / algorithm structure according to some embodiments is illustrated.

[0011] Figure 7 A buffer status report medium access control control element is illustrated according to some embodiments.

[0012] Figure 8 Configurable mappings according to some embodiments are illustrated.

[0013] Fig. 9 Signaling diagrams according to some embodiments are illustrated.

[0014] Fig.10 An operational flow / algorithm structure according to some embodiments is illustrated.

[0015] Fig.11 Another operational flow / algorithm structure according to some embodiments is illustrated.

[0016] Fig.12 Another operational flow / algorithm structure according to some embodiments is illustrated.

[0017] Fig.13 Another operational flow / algorithm structure according to some embodiments is illustrated.

[0018] Fig.14 User equipment according to some embodiments is illustrated.

[0019] Fig.15 A network node according to some embodiments is illustrated. DETAILED DESCRIPTION

[0020] The following specific embodiments refer to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces and / or technologies, are described for the purpose of illustration rather than limitation, so as to provide a thorough understanding of various aspects of some embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that various aspects of various aspects can be practiced in other examples that are separated from these specific details. In some cases, descriptions of well-known devices, circuits and methods are omitted so as not to obscure the descriptions of various aspects due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B) or (A and B); and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0021] The following is a glossary of terms that may be used in this disclosure.

[0022] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), and / or a digital signal processor (DSP). In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for executing the functionality of the program code (or a combination of circuits used in an electrical or electronic system). In these aspects, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0023] As used herein, the term "processor circuit" refers to, is part of, or includes: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations; or recording, storing, or transferring digital data. The term "processor circuit" may refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0024] As used herein, the term "interface circuit" refers to, is a part of, or includes a circuit that enables information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces; for example, a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0025] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0026] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or networked resources.

[0027] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computer, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computer, storage or network resources provided by a virtualized infrastructure to an application, device, system, etc. The term "network resource" or "communication resource" may refer to a resource that a computer device / system can access via a communication network. The term "system resource" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0028] As used herein, the term "channel" refers to any tangible or intangible transmission medium for communicating data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection made between two devices for sending and receiving information.

[0029] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0030] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0031] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0032] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single content of an information element or a data element that contains content. An information element may include one or more additional information elements.

[0033] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN). In some embodiments, the base station 108 is a next generation node B (gNB) providing one or more 3GPP new radio (NR) cells. In other embodiments, the base station 108 is an evolved node B (eNB) providing one or more long term evolution (LTE) cells. The air interface via which the UE 104 and the base station 108 communicate may be compatible with 3GPP technical specifications, such as those defining fifth generation (5G) NR or later system standards.

[0034] The UE 104 may transmit a buffer status report (BSR) to the base station 108 to indicate the amount of uplink data that the UE 104 has to send. The BSR may be sent as a medium access control (MAC) control element (CE) in a physical uplink shared channel (PUSCH). The BSR may be associated with a logical channel group (LCG) having one or more logical channels (LCHs). Upon receiving the BSR, the base station 108 may determine an appropriate amount of uplink resources for the UE 104. The base station 108 may then send an uplink grant to the UE 104. The UE 104 may use the UL grant for subsequent uplink transmissions.

[0035] In various embodiments, the UE 104 may send a regular BSR, a periodic BSR, or a padding BSR. A regular BSR may be triggered when new uplink data for an LCH in an LCG becomes available in the MAC buffer and the LCH has a higher priority than any other LCH with buffered data; or when no other LCH has buffered data. A regular BSR may also be triggered when a retransmit BSR timer (retxBSR-Timer) expires and the LCH includes buffered data to be sent. The retransmit BSR timer may be used to avoid a deadlock situation that may occur when the base station 108 fails to receive the BSR, but the UE 104 believes that the BSR was sent successfully. Thus, the retransmit BSR timer provides a limited period of time that the UE 104 will wait for an uplink grant before retransmitting the BSR. The retransmit BSR timer is started when the BSR is multiplexed into a MAC protocol data unit (PDU).

[0036] The periodic BSR may be triggered when a periodic BSR timer (periodicBSR-Timer) expires.

[0037] A padding BSR may be triggered if the allocated uplink resources have a number of padding bits that equals or exceeds the size of the BSR. Thus, a padding BSR may provide an opportunity to utilize unused uplink capacity.

[0038] Existing networks include multiple BSR formats, including short BSR format (fixed size), extended short BSR format (fixed size), long BSR format (variable size), extended long BSR format (variable size), short truncated BSR format (fixed size), long truncated BSR format (variable size), and extended long truncated BSR format (variable size). The selection between these formats in existing networks is fixed in clause 5.4.5 of 3GPP TS 38.321. The selection may be based on the number of LCGs with data available for transmission, whether the MAC entity has a configured logical channel group IAB extension (logicalChannelGroup-IAB-Ext), and for padding BSR, the number of available padding bits compared to the size of the various formats.

[0039] Service types are evolving to accommodate new use cases in developing cellular networks. For example, efforts are underway to improve RAN operations to support services with characteristics associated with extended reality (XR) services, providing, for example, high throughput, low latency, and high reliability. Various enhancements to BSR operations may be used to improve capacity for XR use cases. Although some embodiments are described with reference to XR services, other embodiments may apply similar concepts to other types of services.

[0040] BSR tables with finer granularity than existing tables can be used to enhance BSR for XR use cases. The existing BSR tables in 3GPP TS38.321 have quantization errors at the buffer size level, which increase with increasing buffer size levels. Since the packet size of XR services can be quite large (e.g., reference video frames), quantization errors can lead to degradation of resource efficiency.

[0041] The BSR may be enhanced for XR use cases by including additional types of information. Existing BSRs only provide information about buffer sizes. To facilitate delay-aware scheduling of XR traffic with latency constraints, the BSR may also include information related to the latency status of buffered data. For example, the BSR may include an indication of how long data has been queued or the amount of time remaining until a delivery deadline.

[0042] XR services may operate based on PDU sets. A PDU set that may correspond to an application data unit may include multiple packets / PDUs. The user plane function (UPF) may identify a PDU set based on a PDU set sequence number (SN); the start / end PDU of a PDU set, a PDU SN within a PDU set, or multiple PDUs within a PDU set.

[0043] A Quality of Service (QoS) flow may be identified using a QoS flow ID, and each PDU set within the QoS flow may be identified using a PDU set SN. Each QoS flow may be used to transmit one or more PDU sets.

[0044] The UPF may also identify information related to the PDU set, such as PDU set importance or PDU set dependency. The UPF may provide information related to the PDU set to the RAN.

[0045] QoS parameters for PDU set-based QoS processing may include PDU set delay budget (PSDB), PDU set error rate (PSER), whether to discard the PDU set if the PSDB is exceeded, whether all PDUs are required for application layer use of the PDU set, and PDU set priority.

[0046] Characteristics of the buffered PDU sets (eg, importance level of the PDU sets) may be indicated in the BSR.

[0047] Additional BSR formats and tables may be developed to accommodate finer granularity buffer sizes or BSRs that include additional information (e.g., delay or queue information). However, sending BSRs with increased granularity or additional information may generate increased signaling overhead.

[0048] It may be prudent to consider whether these new formats / tables with increased overhead are needed in all cases. For example, if the buffer size is relatively small, the quantization error using the traditional BSR table may be insignificant. For another example, if the application can still utilize the set of PDUs even if some of these PDUs are not delivered, the RAN may determine not to strive to deliver the set of PDUs urgently, even if there is little time left until the delivery deadline. For yet another example, if the buffered data does not have strict delay constraints, then it may not be necessary to indicate the delay status in the BSR.

[0049] Many considerations in the consideration of whether the new format is a table may be advantageous, possibly related to factors such as RAN load status, RAN scheduling policy, the application of the sending or receiving service, etc. In addition, different XR services may benefit differently from the various information provided by the BSR. For example, a first XR service may require finer granularity buffer level reporting but not delay information, a second XR service may require delay information but not finer granularity buffer level reporting, and a third XR service may require both delay information and finer granularity buffer level reporting. In some instances, this may result in complex BSR format selection rules.

[0050] As briefly mentioned above, the BSR format selection is currently fixed by 3GPP TS. Therefore, such BSR format selection is not flexible enough to accommodate the various considerations mentioned above.

[0051] Embodiments of the present disclosure provide a flexible BSR framework that takes into account both service characteristics and RAN scheduling policies. Other embodiments disclose BSR triggering and new BSR types that can be based on detecting a predetermined triggering event associated with a delay sensitive report. Other embodiments disclose canceling a triggered BSR event based on packet discard.

[0052] Some embodiments may include a configurable mapping between BSR formats and the status of buffered data. For example, for each BSR format, the base station 108 may pre-configure one or more conditions under which such BSR format is to be used.

[0053] Figure 2 An example of a mapping 200 according to some embodiments is illustrated. Mapping 200 may associate conditions 1 to 4 with BSR formats 1 to 3. As shown, conditions 1 and 3 may be mapped to BSR format 1; condition 2 may be mapped to BSR format 3, and condition 4 may be mapped to BSR format 2. It should be understood that different embodiments may include different numbers of conditions and BSR formats.

[0054] The BSR format may include any of the existing conventional BSR formats discussed above. Additionally / alternatively, the BSR format may include a new format that may be designed for XR services, for example.

[0055] The new BSR format may include a BSR format with a finer granularity for buffer size levels. In some embodiments, the BSR format with a finer granularity for buffer size levels may correspond to a new table that includes a smaller quantization error for higher buffer levels than provided by the existing table.

[0056] Another new BSR format may include a BSR format having information related to the delay or queue status of buffered data.

[0057] Another new BSR format may include a BSR format with information related to the characteristics of the buffered PDU set. These characteristics may include, but are not limited to, importance, priority level, or whether the application layer requires all PDUs in the PDU set.

[0058] The new BSR format may be based on an extension of the BSR format currently present in, for example, 3GPP TS 38.321. In other embodiments, other BSR formats may be used.

[0059] The conditions may refer to the status of buffered data. The conditions may apply only to a subset of LCHs (e.g., at least one LCH in at least one specific LCG). Alternatively, the conditions may apply to any LCH in any LCG. The conditions may be one or more of the following.

[0060] The first condition may relate to whether the application requires all PDUs in the buffered PDU set. For example, if the application requires all PDUs in the buffered PDU set, the base station 108 may configure the UE 104 to use a BSR format with queuing delay information. Conversely, if the application does not require all PDUs in the buffered PDU set, the base station 108 may configure the UE 104 to use a BSR format without queuing delay information, because timely delivery of the PDU set may not be so critical.

[0061] The second condition may relate to whether the remaining time budget until the delivery deadline of the buffered data is less than or greater than a predetermined threshold. For example, if the remaining time budget is less than the predetermined threshold, the base station 108 may configure the UE 104 to use a BSR format with a delayed / queued status of the buffered data.

[0062] The third condition may relate to whether the queuing time of the buffered data is less than or greater than a predetermined threshold. For example, if the queuing time is greater than a predetermined threshold, the base station 108 may configure the UE 104 to use a BSR format with a delay / queuing status of the buffered data.

[0063] The fourth condition may relate to whether the buffered data size is less than or greater than a predetermined threshold. For example, if the buffered data size is greater than a predetermined threshold, the base station 108 may configure the UE 104 to use a BSR format with finer granularity for higher buffer size levels.

[0064] The fifth condition may relate to whether the buffered PDU set is considered an "important" or "unimportant" PDU set. For example, if the buffered PDU set is considered an "important" PDU set, the base station 108 may configure the UE 104 to use a BSR format with an indication of the importance of the PDU set.

[0065] The sixth condition may relate to whether the buffered PDU set is considered a "low priority" or "high priority" PDU set. For example, if the buffered PDU set is considered a "high priority" PDU set, the base station 108 may configure the UE 104 to use a BSR format with an indication of the PDU set priority.

[0066] The seventh condition may relate to whether packet discard is configured for the buffered PDU set or its radio bearer, or whether the BSR is triggered by an event related to packet discard. For example, if packet discard is configured, the base station 108 may configure the UE 104 to use a BSR format with an indication of the packet discard setting, or a BSR table with a quantized remaining time until the delivery deadline of the buffered data, so that the base station can know when the packet can be discarded if it is not delivered.

[0067] In some embodiments, the BSR format may include a combination or joint use of two or more of the formats listed above. For example, the UE 104 may detect a first condition associated with a BSR for buffer size and a second condition associated with a BSR format for delay information of buffered data (or the UE 104 may detect one condition associated with both BSR formats). In this embodiment, a MAC CE with a joint BSR format for buffer size and delay information may be used. Additionally / alternatively, the BSR report may include multiple MAC CEs for BSRs related to buffered data, such as a first MAC CE with a BSR format for buffer size and a second MAC CE with a BSR format for delay information.

[0068] Figure 3is a signaling diagram 300 for a BSR according to some embodiments.

[0069] The signaling diagram 300 may include, at 304, the base station 108 transmitting configuration information to the UE 104. The configuration information may configure a mapping between conditions and BSR formats. These conditions may be related to buffered data status / characteristics.

[0070] The signaling diagram 300 may also include, at 308, the UE 104 detecting a BSR triggering event. The BSR triggering event may be similar to the triggering events described above. For example, the BSR triggering event may be related to new data becoming available in a buffer, detecting unused uplink resources, or expiration of a periodic BSR timer.

[0071] The signaling diagram 300 may also include detecting a buffered data status / characteristic condition at 312. The detected condition may be one or more of the seven conditions described above.

[0072] In some cases, operations 308 and 312 may be combined. For example, the BSR triggering event of 308 may be based on the condition of 312. Thus, when the condition is met, the UE may trigger a BSR.

[0073] The signaling diagram 300 may also include selecting a BSR format based on the detected condition, at 316. The BSR format selected at 316 may be one or more of those formats described elsewhere herein.

[0074] The signaling diagram 300 may also include, at 320, generating a BSR having one or more MAC CEs with a selected BSR format.

[0075] The signaling diagram 300 may also include, at 324, the UE 104 sending a BSR to the base station 108. The BSR may be sent in the allocated uplink resources. In some embodiments, the uplink resources may be allocated specifically for the BSR based on, for example, a request (e.g., a scheduling request) from the UE 104. In other embodiments, the uplink resources may be allocated for another purpose and used opportunistically by the UE 104 to report the BSR.

[0076] In some embodiments, the detection of the buffered data status / characteristic conditions at 312 may not occur immediately after the detection of the triggering event at 308, and may be based on the timing of other operations of the signaling diagram 300. For example, in some embodiments, it may be necessary to detect these conditions as close in time as possible to the transmission of the BSR at 324. This can ensure that the selected BSR format is the most appropriate according to the evolving characteristics of the buffered data. Therefore, in some embodiments, the UE 104 can detect the conditions of the uplink resources to be used for the BSR transmission in advance of the time period in which the UE 104 can perform operations 312, 316, and 320.

[0077] Figure 4 An example of a mapping 400 according to some embodiments is illustrated. Mapping 400 may associate conditions 1 to 4 with BSR tables 1 to 3. As shown, conditions 1 and 3 may be mapped to BSR table 1; condition 2 may be mapped to BSR table 3, and condition 4 may be mapped to BSR table 2. It should be understood that different embodiments may include different numbers of conditions and BSR tables.

[0078] The BSR table may include an existing legacy BSR table, such as those found in 3GPP TS 38.321. For example, the legacy BSR table may be similar to Table 6.1.3.1-1 of 3GPP TS 38.321 for a five-bit buffer size field or Table 6.1.3.1-2 of 3GPP TS 38.321 for an eight-bit buffer size field. Additionally / alternatively, for example, the BSR table may include a new table designed for XR services.

[0079] The new BSR table may include a BSR table with finer granularity for buffer size levels. In some embodiments, the finer granularity may be with respect to the granularity exhibited by the higher buffer size levels of the conventional table. For example, while the conventional BSR table may have a step size that increases with the buffer size level between adjacent buffer size levels, the new BSR table may have a constant step size throughout the table or even a step size that decreases with the buffer size level in order to complement the existing table.

[0080] Another new BSR table may include indexes corresponding to quantized queuing time values.

[0081] Another new BSR table may include an index corresponding to a quantized remaining time until a delivery deadline associated with the buffered data.

[0082] Other BSR tables may also be used. The BSR table may be predefined, for example, by 3GPP TS, or may be configured by the network.

[0083] The conditions may refer to the status of buffered data. The conditions may apply only to a subset of LCHs (e.g., at least one LCH in at least one specific LCG). Alternatively, the conditions may apply to any LCH in any LCG. The conditions may be one or more of the following.

[0084] The first condition may relate to whether the application requires all PDUs in the buffered PDU set. For example, if the application requires all PDUs in the buffered PDU set, the base station 108 may configure the UE 104 to use a BSR table with queuing delay information. Conversely, if the application does not require all PDUs in the buffered PDU set, the base station 108 may configure the UE 104 to use a traditional BSR table without queuing delay information, because timely delivery of the PDU set may not be so critical.

[0085] The second condition may relate to whether the remaining time budget until the delivery deadline of the buffered data is less than or greater than a predetermined threshold. For example, if the remaining time budget is less than the predetermined threshold, the base station 108 may configure the UE 104 to use a BSR table having a quantized remaining time until the delivery deadline of the buffered data.

[0086] The third condition may relate to whether the queuing time of the buffered data is less than or greater than a predetermined threshold. For example, if the queuing time is greater than the predetermined threshold, the base station 108 may configure the UE 104 to use a BSR table with a quantized queuing time of the buffered data.

[0087] The fourth condition may relate to whether the buffered data size is less than or greater than a predetermined threshold. For example, if the buffered data size is greater than a predetermined threshold, the base station 108 may configure the UE 104 to use a BSR table with finer granularity for higher buffer size levels.

[0088] The fifth condition may relate to whether the buffered PDU set is considered an "important" or "unimportant" PDU set. For example, if the buffered PDU set is considered an "important" PDU set, the base station 108 may configure the UE 104 to use a BSR table with explicit or implicit information related to the importance of the PDU set.

[0089] The sixth condition may relate to whether the buffered PDU set is considered a "low priority" or "high priority" PDU set. For example, if the buffered PDU set is considered a "high priority" PDU set, the base station 108 may configure the UE 104 to use a BSR table with explicit or implicit information related to the priority of the PDU set.

[0090] The seventh condition may relate to whether packet discard is configured for the buffered PDU set or its radio bearer, or whether the BSR is triggered by an event related to packet discard. For example, if packet discard is configured, the base station 108 may configure the UE 104 to use a BSR table with a quantized remaining time until the delivery deadline of the buffered data, so that the base station can know when the packet can be discarded if it is not delivered.

[0091] In some embodiments, the selection of a BSR table may imply the selection of a BSR format. However, in other embodiments, the selection of a BSR table and a format may be at least partially independent of each other.

[0092] In some cases, the UE 104 may need to use two or more tables from those mentioned above. For example, the UE 104 may detect a first condition associated with a first BSR table (e.g., a BSR table with a finer granularity size for a higher buffer size level), and may detect a second condition associated with a second BSR table (e.g., a BSR table with quantized queuing time) (or the UE 104 may detect a condition associated with two BSR tables). In this embodiment, the UE 104 may generate a MAC CE with a first indication corresponding to the first BSR table and a second indication corresponding to the second BSR table. Additionally / alternatively, the UE 104 may generate a BSR to include multiple MAC CEs related to buffered data, for example, a first MAC CE with a first indication corresponding to the first BSR table and a second MAC CE with a second indication corresponding to the second BSR table.

[0093] Figure 5 is a signaling diagram 500 for a BSR according to some embodiments.

[0094] The signaling diagram 500 may include, at 504, the base station 108 transmitting configuration information to the UE 104. The configuration information may configure a mapping between conditions and the BSR table. These conditions may be related to the buffered data status / characteristics.

[0095] The signaling diagram 500 may also include, at 508, the UE 104 detecting a BSR triggering event. The BSR triggering event may be similar to the triggering events described above. For example, the BSR triggering event may be related to new data becoming available in a buffer, detecting unused uplink resources, or expiration of a periodic BSR timer.

[0096] The signaling diagram 500 may further include detecting a buffered data status / characteristic condition at 512. The detected condition may be one or more of the seven conditions described above.

[0097] In some cases, operations 508 and 512 may be combined. For example, the BSR triggering event of 508 may be based on the condition of 512. Thus, when the condition is met, the UE may trigger a BSR.

[0098] Signaling diagram 500 may also include selecting a BSR table based on the detected condition, at 516. The BSR table selected at 316 may be one or more of those described elsewhere herein.

[0099] The signaling diagram 500 may also include, at 520, generating a BSR having one or more MAC CEs with an indication corresponding to the selected BSR table.

[0100] The signaling diagram 500 may also include, at 524, the UE 104 sending a BSR to the base station 108. The BSR may be sent in the allocated uplink resources. In some embodiments, the uplink resources may be allocated specifically for the BSR based on, for example, a request from the UE 104. In other embodiments, the uplink resources may be allocated for another purpose and used opportunistically by the UE 104 to report the BSR.

[0101] In some embodiments, the detection of the buffered data status / characteristic conditions at 512 may not occur immediately after the detection of the triggering event at 508, and may be based on the timing of other operations of the signaling diagram 500. For example, in some embodiments, it may be necessary to detect these conditions as close in time as possible to the transmission of the BSR at 524. This can ensure that the selected BSR table is the most appropriate according to the evolving characteristics of the buffered data. Therefore, in some embodiments, the UE 104 can detect the conditions of the uplink resources to be used for the BSR transmission in advance of the time period in which the UE 104 can perform operations 512, 516, and 520.

[0102] In some embodiments, the base station 108 may configure a mapping between the BSR timer configuration and various conditions corresponding to the state of the buffered data. Depending on the condition of the state of the buffered data, the UE 104 may then select a BSR configuration corresponding to different values ​​of the BSR-related timers. The BSR-related timers may include, for example, a periodic BSR timer (periodicBSR-Timer), a retransmission BSR timer (retxBSR-Timer), or a logical channel scheduling request delay timer (logicalChannelSR-DelayTimer). The timer value may be configured by RRC in the BSR configuration (BSR-config).

[0103] 3GPP TS 38.321 describes how and when the UE uses various BSR-related timers. For example, clause 5.4.5 specifies that the UE's MAC entity will start or restart the periodicBSR-Timer or retxBSR-Timer in various situations. For example,

[0104] The MAC entity will:

[0105] 1> If the Buffer Status Reporting process determines that at least one BSR has been triggered and has not been cancelled:

[0106] 2> If UL-SCH resources are available for new transmissions and as a result of logical channel prioritization, the UL-SCH resources can accommodate the BSR MAC CE plus its subheader:

[0107] 3> Indicates the multiplexing and assembly process to generate the BSR MAC CE as defined in clause 6.1.3.1;

[0108] 3> Start or restart the periodicBSR-Timer, except when all generated BSRs are long or short truncated or extended long or short truncated BSRs;

[0109] 3> Start or restart retxBSR-Timer.

[0110] 3GPP TS 38.321, clause 5.4.5.

[0111] In some embodiments, the UE 104 may adaptively change, select, or ignore BSR-related timer values ​​when the configured conditions are met. The configured conditions may apply only to a subset of LCHs (e.g., at least one LCH in at least one specific LCG). Alternatively, the conditions may apply to any LCH in any LCG. The conditions may be one or more of the following.

[0112] The first condition may relate to whether the application requires all PDUs in the buffered PDU set. For example, if the application requires all PDUs in the buffered PDU set, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request faster.

[0113] The second condition may relate to whether the remaining time budget until the delivery deadline of the buffered data is less than or greater than a predetermined threshold. For example, if the remaining time budget is less than the predetermined threshold, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request more quickly.

[0114] The third condition may relate to whether the queuing time of the buffered data is less than or greater than a predetermined threshold. For example, if the queuing time is greater than a predetermined threshold, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request more quickly.

[0115] The fourth condition may relate to whether the buffered data size is less than or greater than a predetermined threshold. For example, if the buffered data size is greater than a predetermined threshold, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request more quickly.

[0116] The fifth condition may relate to whether the buffered PDU set is considered to be an "important" or "unimportant" PDU set. For example, if the buffered PDU set is considered to be an "important" PDU set, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request more quickly.

[0117] The sixth condition may relate to whether the buffered PDU set is considered a "low priority" or "high priority" PDU set. For example, if the buffered PDU set is considered a "high priority" PDU set, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request more quickly.

[0118] The seventh condition may relate to whether packet discard is configured for the buffered PDU set or its radio bearer, or whether the BSR is triggered by an event related to packet discard. For example, if packet discard is configured, the base station 108 may configure the UE 104 to use a BSR-related timer with a smaller timer value to trigger a periodic BSR, BSR retransmission, or scheduling request faster to prevent packet discard.

[0119] Figure 6 An operational flow / algorithm structure 600 for BSR based on a mapping of configurations between BSR timer configurations under various conditions according to some embodiments is illustrated. The operational flow / algorithm structure 600 may be implemented by a UE (such as, for example, UE 104 or 1400) or a component thereof (e.g., processing circuit 1404).

[0120] The operational flow / algorithm structure 600 may include, at 604, receiving configuration information having a first BSR timer setting and a second BSR timer setting. The BSR timer setting may include one or more values ​​corresponding to any of the BSR-related timers discussed herein. In some embodiments, one of the BSR timer settings may be configured as a default setting to be used unless another setting is conditionally triggered. In some embodiments, one or more of the BSR timer settings (e.g., default settings) may be predefined by, for example, 3GPP, while other BSR timer settings (e.g., triggered settings) may be dynamically configured by the base station 108.

[0121] In some embodiments, the configuration information may include additional / alternative information, such as, for example, information about a buffer status condition associated with one or more of the BSR timer settings. For purposes of describing this embodiment, the buffer status condition may be associated with the second BSR timer setting. Thus, in this case, the first BSR timer setting may be considered a default BSR timer setting.

[0122] The operational flow / algorithm structure 600 may also include identifying a BSR triggering event, at 608. The triggering event may be associated with a regular, periodic, or filler BSR, as discussed elsewhere herein.

[0123] The operational flow / algorithm structure 600 may also include determining whether the buffered data satisfies a buffer status condition at 612. If the buffered data satisfies the buffer status condition, the operational flow / algorithm structure 600 may proceed to establish a BSR MAC CE at 616 and apply a second BSR timer setting.

[0124] In some cases, operations 608 and 612 may be combined. For example, the BSR triggering event of 608 may be based on the condition of 612. Thus, when the condition is met, the UE may trigger a BSR.

[0125] In the event that the buffered data does not satisfy the buffer status condition, the operational flow / algorithm structure 600 may proceed to establish a BSR MAC CE at 620 and apply the first BSR timer setting.

[0126] In some embodiments, the BSR MAC CE generated and sent in the BSR may include an information type indicator to indicate the type of information included in the BSR MAC CE. The information type may refer to, for example, the BSR table on which the BSR MAC CE is based (e.g., a legacy BSR table or a BSR table with finer granularity at a higher BSR level); the presence of queuing / delay information in the BSR MAC CE; or the presence of PDU set characteristic information in the BSR MAC CE.

[0127] Figure 7 Included is a BSR MAC CE 700 according to some embodiments. UE 104 may generate BSR MAC CE 700 for a BSR to be sent to base station 108.

[0128] The BSR MAC CE 700 may include M octets. In the first octet, the BSR MAC CE 700 may include a type field 704 and an LCG identifier 708. The type field 704 may indicate the type of information to be included. The LCG identifier 708 may identify the LCG to which the BSR relates.

[0129] BSR MAC CE 700 may also include a buffer size 712. The buffer size may be indicated using one or more octets and may indicate the size of the buffer of UE 104. As shown, buffer size 712 is from the second octet to the Kth octet.

[0130] In some embodiments, the BSR MAC CE 700 may also include delay / queue information 716. The delay / queue information 716 may provide information about the delay or queuing status of the buffered data, or the remaining time until the delivery deadline of the buffered data.

[0131] Upon decoding the type field 704, the base station 108 may determine the type of information included in the BSR MAC CE 700. In some embodiments, the type field 704 may be a one-bit field that indicates whether delay / queuing information is present in the BSR MAC CE 700. In other embodiments, the type field 704 may include one or more bits to provide an indication of whether the BSR MAC CE 700 includes additional / alternative buffer related data (e.g., PDU set characteristics, reporting of finer granularity sizes, etc.). The type field 704 may be any number of bits necessary to provide an indication of the type of information being conveyed.

[0132] Figure 8An example of a mapping 800 according to some embodiments is illustrated. Mapping 800 may associate conditions 1 to 4 with BSR MAC CE information types 1 to 3. As shown, conditions 1 and 3 may be mapped to BSR MAC CE information type 1; condition 2 may be mapped to BSR MAC CE information type 3; and condition 4 may be mapped to BSR MAC CE information type 2. It should be understood that different embodiments may include different numbers of conditions and BSR MAC CE information types. These conditions may be similar to those discussed elsewhere herein.

[0133] Fig. 9 is a signaling diagram 900 for BSR according to some embodiments.

[0134] The signaling diagram 900 may include, at 904, the base station 108 transmitting configuration information to the UE 104. The configuration information may configure a mapping between conditions and BSR MAC CE information type values. These conditions may be related to buffered data status / characteristics.

[0135] The signaling diagram 900 may also include, at 908, the UE 104 detecting a BSR triggering event. The BSR triggering event may be similar to the triggering events described above. For example, the BSR triggering event may be related to new data becoming available in a buffer, detecting unused uplink resources, or expiration of a periodic BSR timer.

[0136] The signaling diagram 900 may further include detecting a buffered data status / characteristic condition at 912. The detected condition may be one or more of the seven conditions described above.

[0137] The signaling diagram 900 may further include selecting a BSRMAC CE information type value based on the detected condition, at 916. The BSRMAC CE information type value selected at 916 may be one or more of those described elsewhere herein.

[0138] The signaling diagram 900 may also include, at 920, generating a BSR having one or more MACCEs with a selected information type value.

[0139] The signaling diagram 900 may also include, at 924, the UE 104 sending a BSR to the base station 108. The BSR may be sent in the allocated uplink resources. In some embodiments, the uplink resources may be allocated specifically for the BSR based on, for example, a request from the UE 104. In other embodiments, the uplink resources may be allocated for another purpose and used opportunistically by the UE 104 to report the BSR.

[0140] In some embodiments, the detection of the buffered data status / characteristic conditions at 912 may not occur immediately after the detection of the triggering event at 908, and may be based on the timing of other operations of the signaling diagram 900. For example, in some embodiments, it may be necessary to detect these conditions as close in time as possible to the transmission of the BSR at 924. This can ensure that the selected information type value is the most appropriate according to the evolving characteristics of the buffered data. Therefore, in some embodiments, the UE 104 can detect the conditions of the uplink resources to be used for the BSR transmission in advance of the time period in which the UE 104 can perform operations 912, 916, and 920.

[0141] Fig.10 1000 is an operation flow / algorithm structure according to some embodiments. The operation flow / algorithm structure 1000 may be implemented by a MAC entity in a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processing circuit 1404).

[0142] The operational flow / algorithm structure 1000 may include, at 1004, receiving configuration information that maps buffer conditions to BSR formats, tables, or information type values. The configured mapping may be similar to the configured mapping described elsewhere herein. The BSR formats, tables, or information type values ​​may be related or unrelated to each other. For example, in some embodiments, the buffer status condition may be mapped to the BSR format, table, and information type value, while in other embodiments, the buffer status condition may be mapped only to the BSR format, only to the table, or only to the information type value.

[0143] In some embodiments, the mapping of buffer conditions to BSR formats, tables or information type values ​​may be determined in other ways. For example, the mapping may be predefined by, for example, 3GPP TS.

[0144] The operational flow / algorithm structure 1000 may also include, at 1008, detecting a condition of a buffer corresponding to a buffer condition mapped to a BSR format / table / information type value. In some embodiments, the buffer condition may be mapped to more than one BSR format / table / information type value. These conditions may be similar to any of those conditions discussed elsewhere herein. In some embodiments, the UE may detect multiple conditions mapped to multiple BSR formats / tables / information type values.

[0145] The operational flow / algorithm structure 1000 may also include, at 1012, identifying a BSR format / table / information type value associated with the buffer condition.

[0146] The operational flow / algorithm structure 1000 may also include, at 1016, generating a BSR MAC CE based on the identified BSR format / table / information type value.

[0147] The operational flow / algorithm structure 1000 may also include, at 1020, sending a BSR MAC CE to the base station. In some embodiments, the BSR MAC CE may include information corresponding to a plurality of detected buffer status conditions. In other embodiments, the BSR MAC CE may be included in a BSR with one or more additional BSR MAC CEs corresponding to one or more additional detected buffer status conditions.

[0148] As briefly discussed above, there may be some instances where the application layer does not require all PDUs in a PDU set to use the PDU set. This may result in situations where some packets of the PDU set are dropped before they are sent. This may be based on a QoS parameter indicating whether to drop the PDU set if the PSDB is exceeded; or whether all PDUs are required for the PDU set to be used by the application layer.

[0149] Active packet discarding may occur in one or more of the following instances.

[0150] In the first example, if all packets in a PDU set are required to be successfully delivered in order for an application to utilize the PDU set and at least one of these packets has failed, active packet discarding may occur. In this case, it may not be necessary to send the remaining packets of the PDU set, and therefore, they may be actively discarded.

[0151] In a second example, if at least one critical / essential packet of a PDU set has failed, active packet discarding may occur. In this case, the remaining packets of the PDU set may not need to be sent.

[0152] In the third example, if the packet layer only needs a certain part of the PDU set and the part has been successfully received, active packet discarding may occur. In this case, the transmitter may discard the remaining packets in the PDU set to save power / resources.

[0153] In a fourth example, active packet discarding may be based on interdependencies between different PDU sets. The transmitter may determine whether to discard a PDU set or continue to send the PDU set based on the status of the related PDU set. For example, if the transmission of a first PDU set is necessary (e.g., an I frame), the transmitter may determine whether the PDU set is successfully transmitted before continuing to transmit the related PDU set (e.g., the related P frame).

[0154] In a fifth example, a sender may use proactive packet discarding in order to alleviate traffic congestion.

[0155] When a decision to discard a packet is made, regardless of the reason, packets from one or more PDU sets that are still queued in the logical channel buffer may be cleared. In this case, the packet discard may cause a change in the uplink buffer state, for example, the uplink buffer may become empty or at least less full. The UE may be required to provide the network with a timely indication of the change in buffer state. Therefore, packet discard may be associated with a BSR triggering event.

[0156] Typically, XR traffic may be delay sensitive and may include a requirement to be delivered within a specific time budget (e.g., PSDB) in order to make it useful to the receiving application. As discussed above, to enable delay-aware scheduling, BSR reporting may be enhanced to include information such as queuing delay time or the remaining time until a delivery deadline. This information may allow the base station 108 to allocate uplink resources in a more timely manner. BSR triggering events related to queuing time, such as those described herein, may allow a BSR including queuing delay information to be triggered when buffered data has been waiting in a buffer for more than a certain amount of time.

[0157] Thus, as described, multiple new BSR triggering events may be introduced based on packet drops, long queuing delays, and other PDU set characteristics related to, for example, XR use cases. An embodiment provides a process in which the UE 104 transmits a BSR triggered by such events to the base station 108 in order to update the buffer status in a timely manner. These BSRs may be sent as soon as they are triggered to achieve more efficient resource allocation. Existing BSR mechanisms impose restrictions on triggering or sending BSRs based on delay timers (such as retransmit BSR timers, periodic BSR timers, and logical channel SR delay timers). An embodiment of the present disclosure describes a mechanism for facilitating faster sending of BSRs triggered by predetermined triggering events. The predetermined triggering events may involve XR-related characteristics, such as packet drops, long queuing delays, etc.

[0158] As discussed above, certain types of BSRs may be restricted by running timers. For example, there may be instances where a regular BSR may not be sent if a retransmit BSR timer is running. Various embodiments describe predetermined triggering events that, when detected by the UE 104, permit the UE 104 to consider the expiration of a running delay timer that would otherwise restrict the transmission of a triggered BSR or related SR. To consider the expiration of the delay timer, the UE 104 may affirmatively stop the timer prior to its natural expiration, or may simply ignore the restriction on sending a BSR / SR while the timer is running. As used herein, "natural expiration" of a timer refers to the expiration of the timer based on the passage of time at least equal to the value of the timer.

[0159] In various embodiments, the delay timer that would otherwise limit the transmission of a triggered BSR or related SR may be a retransmission BSR timer, a periodic BSR timer, or a logical channel SR delay timer.

[0160] Predetermined triggering events associated with the uplink transmit buffer that may trigger a BSR or cause the UE 104 to consider the running delay timer expired may include the following events.

[0161] A first triggering event may be detected when a packet drop occurs for one or more logical channels in the logical channel group. In some embodiments, the packet drop may be a triggering event if the amount of data dropped from the buffer is greater than a predetermined threshold. In other embodiments, the packet drop may be a triggering event if, as a result of the packet drop, the level of the buffer becomes less than a predetermined threshold.

[0162] The second trigger event may be detected when a queuing delay time of data buffered for one or more logical channels in the logical channel group exceeds a predetermined threshold.

[0163] A third triggering event may be detected when a remaining time until a delivery deadline of data buffered for one or more logical channels in the logical channel group is below a predetermined threshold.

[0164] When the size of the buffer exceeds a predetermined threshold, a fourth trigger event may be detected.

[0165] A fifth triggering event may be detected when a set of PDUs for a logical channel arrives in the buffer and has a higher importance level or priority level than any other buffered set of PDUs for the logical channel.

[0166] When the number of PDUs in the buffered PDU set is higher than a predetermined threshold, a sixth triggering event may be detected.

[0167] When a data burst having a size greater than a predetermined threshold arrives in the buffer, a seventh trigger event may be detected. As used herein, a data burst may refer to a collection of data provided by an application in a short period of time. The collection of data may include PDUs from one or more PDU sets.

[0168] The predetermined thresholds used in various triggering events may be predefined by, for example, 3GPP TS, or may be dynamically configured by the base station 108. The configuration of the predetermined thresholds may be through RRC or MAC signaling.

[0169] Fig.111100 is an operation flow / algorithm structure according to some embodiments. The operation flow / algorithm structure 1100 may be implemented by a MAC entity in a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processor 1404).

[0170] The operational flow / algorithm structure 1100 may include, at 1104, detecting an event associated with the buffer. The event may include a change in a condition of the buffer. For example, the event may involve new uplink data being added to the buffer, uplink data being removed from the buffer, or a change in the timing status of uplink data within the buffer.

[0171] The operational flow / algorithm structure 1100 may also include, at 1112, determining that a delay timer associated with the BSR type is running.

[0172] Some types of BSRs may be associated with a delay timer, while other types of BSRs may not be associated with a delay timer. For example, a BSR not associated with a delay timer may occur if triggered by uplink data for a logical channel in a logical channel group becoming available in a buffer, and: the logical channel has a higher priority than any other logical channel with available uplink data; or the other logical channels in the logical channel group do not contain available uplink data. When conditions permit the sending of a fill BSR, another BSR not associated with a delay timer may be triggered, as discussed elsewhere herein. However, other generated BSRs may be associated with a delay timer and may be triggered only upon expiration of an associated delay timer. For example, the retransmission of a regular BSR for data present in a buffer may be limited by a retransmission BSR timer. For another example, the sending of a periodic BSR timer may be limited by a periodic BSR timer. For another example, the sending of an SR for a regular BSR for a logical channel with logicalChannelSr-DelayTimerApplied set to true may be limited by a logical channel SR delay timer.

[0173] The operation flow / algorithm structure 1100 may also include determining whether the event detected at 1104 is a predetermined trigger event at 1116. The predetermined trigger event may be any one of the seven predetermined trigger events described above.

[0174] Although the present embodiment describes detecting an event associated with a buffer and determining whether the event is equal to a predetermined trigger event, other embodiments may include detecting multiple events associated with a buffer and determining whether the multiple detected events are equal to a specific combination of multiple predetermined trigger events selected from seven predetermined trigger events.

[0175] If it is determined at 1116 that the detected event is not equal to a predetermined triggering event, the operational flow / algorithm structure 1100 may proceed to wait until the natural expiration of the delay timer to trigger a BSR type BSR / SR at 1120. Thus, in this example, the natural expiration of the delay timer may serve as a trigger for the transmission of the BSR / SR.

[0176] If it is determined at 1116 that the detected event is equal to a predetermined triggering event, the operational flow / algorithm structure 1100 may proceed to consider the delay timer expired and trigger the BSR / SR at 1124. In this way, further delays in time-sensitive BSR transmissions may be avoided.

[0177] As described elsewhere herein, existing 3GPP specifications define three general BSR types, such as regular BSR, periodic BSR, and padding BSR. In some embodiments, new types of BSRs may be defined to accommodate delay-sensitive BSR transmissions.

[0178] The new type of BSR may be referred to as a delay-sensitive BSR and may take precedence over regular BSRs, periodic BSRs, and padding BSRs. In some embodiments, a delay-sensitive BSR may be considered a special type of regular BSR.

[0179] A delay-sensitive BSR or its associated SR may be triggered regardless of whether a delay timer (e.g., a retransmission BSR timer, a periodic BSR timer, or a logical channel SR delay timer) is running. Thus, a delay-sensitive BSR may not be associated with a delay timer at all.

[0180] The delay-sensitive BSR may be triggered by one or more predetermined triggering events among the seven predetermined triggering events mentioned above.

[0181] In some implementations, to accommodate delay-sensitive BSR, clause 5.4.5 of 3GPP TS 38.321 may be updated with the following underlined portion:

[0182] A BSR shall be triggered if any of the following events occurs for an activated cell group:

[0183] - For logical channels belonging to the LCG, UL data becomes available to the MAC entity; and

[0184] - the UL data belongs to a logical channel having a higher priority than any logical channel containing available UL data belonging to any LCG; or

[0185] - Any logical channel belonging to the LCG does not contain any available UL data.

[0186] In this case, the BSR is referred to as the “regular BSR” hereinafter;

[0187] - UL resources are allocated and the number of padding bits is equal to or greater than the size of the buffer status report MAC CE plus its subheader, in which case the BSR is referred to as a "padding BSR" in the following;

[0188] - Packet discard occurs for one or more LCHs in the LCG, and buffers are If the queuing delay of the data exceeds the threshold, the remaining delivery of the data buffered in one or more LCHs in the LCG is minimized. The deadline is lower than the threshold, the buffer size exceeds the threshold, and the important or high priority PDU set has arrived in the buffer. The number of PDUs in the PDU set is higher than the threshold, or a data burst with a size larger than the threshold has arrived in the buffer In this case, the BSR is hereinafter referred to as "delay-sensitive BSR";

[0189] - retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains UL data, in which case the BSR is referred to as "normal BSR" hereinafter;

[0190] - The periodicBSR-Timer expires, in which case the BSR is referred to as a "periodic BSR" hereinafter.

[0191] Clause 5.4.5 of 3GPP TS 38.321 may also be updated to take into account the priority of delay-sensitive BSRs as follows: "A MAC PDU shall contain at most one BSR MAC CE, even when multiple events have triggered a BSR. Delay Sensitive The BSR shall take precedence over the regular BSR, periodic BSR and padding BSR. Regular BSR and periodic BSR shall take precedence over padding BSR. "

[0192] Fig.12 12 is an operation flow / algorithm structure 1200 according to some embodiments. The operation flow / algorithm structure 1200 may be implemented by a MAC entity in a UE (eg, UE 104 or UE 1400) or a component thereof (eg, processor 1404).

[0193] The operational flow / algorithm structure 1200 may include detecting a trigger event associated with the buffer at 1204. The trigger event may include one or more of the seven predetermined trigger events described elsewhere herein.

[0194] The operation flow / algorithm structure 1200 may also include, at 1208, triggering a delay-sensitive BSR based on detecting a triggering event. The delay-sensitive BSR may be a new type of BSR that is not associated with a delay timer. As discussed above, the delay-sensitive BSR may take precedence over a regular BSR, a periodic BSR, and a padding BSR.

[0195] The operational flow / algorithm structure 1200 may also include sending a delay-sensitive BSR at 1212. Since the delay-sensitive BSR is not associated with a delay timer and takes precedence over other BSRs, its sending may be performed without delay, thereby resulting in timely delivery of relevant information.

[0196] In some embodiments, packet discard may be used as a basis for cancelling a previously triggered BSR. For example, a BSR may be initially triggered when UL data for a logical channel belonging to an LCG becomes available. However, packet discard may occur in the UL data for the logical channel even before the triggered BSR is sent on the MAC PDU. When the buffer becomes empty due to packet discard (e.g., UL data is no longer available), the event that triggered the BSR may no longer be valid, and the triggered BSR may therefore be canceled. However, at the same time, another BSR may be triggered due to packet discard according to some embodiments previously described.

[0197] Fig.13 1300 is an operational flow / algorithm structure describing cancellation of a triggered BSR according to some embodiments. The operational flow / algorithm structure 1300 may be implemented by a MAC entity in a UE (e.g., UE 104 or UE 1400) or a component thereof (e.g., processor 1404).

[0198] The operation flow / algorithm structure 1300 may include triggering a BSR based on uplink data of the logical channel in the buffer at 1304. The BSR may be triggered based on any of the triggering events described herein. The triggering event may be related to the seven predetermined triggering events or any other triggering event described herein.

[0199] The operational flow / algorithm structure 1300 may also include discarding a packet of uplink data from the buffer at 1308. The packet may be discarded as a result of an active packet discard operation as described elsewhere herein.

[0200] The operational flow / algorithm structure 1300 may also include canceling the BSR based on discarding the packet, at 1312. In some embodiments, the UE may also stop a delay timer associated with the BSR based on canceling the BSR.

[0201] In some embodiments, if the buffer of one or more LCH / LCG becomes empty after the packet is discarded, the triggered BSR may be cancelled. Otherwise, if the buffer of one or more LCH / LCG is not empty after the packet is discarded, the triggered BSR may not be cancelled.

[0202] In some embodiments, the BSR may be cancelled if the aggregate size of one or more packets dropped from the buffer is greater than a predetermined threshold size. In other embodiments, the BSR may be cancelled if the buffer size becomes less than a predetermined threshold as a result of one or more packets being dropped from the buffer.

[0203] Fig.14 UE 1400 according to some embodiments is illustrated. UE 1400 may be similar to Figure 1 UE 104 and is substantially interchangeable therewith.

[0204] UE 1400 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an XR device, glasses, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a camcorder), a wearable device (e.g., a smart watch), or an IoT device.

[0205] UE 1400 may include a processor 1404, RF interface circuitry 1408, memory / storage 1412, a user interface 1416, a sensor 1420, a driver circuit 1422, a power management integrated circuit (PMIC) 1424, antenna structures 1426, and a battery 1428. The components of UE 1400 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logic component, hardware, software, firmware, or a combination thereof. Fig.14 The block diagram of UE 1400 is intended to show a high-level view of some of the components of UE 1400. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0206] Components of UE 1400 may be coupled to various other components via one or more interconnects 1432, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, or optical connection that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0207] The processor 1404 may include processor circuits such as, for example, a baseband processor circuit (BB) 1404A, a central processor unit circuit (CPU) 1404B, and a graphics processor unit circuit (GPU) 1404C. The processor 1404 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1412) to cause the UE 1400 to perform operations as described herein.

[0208] In some embodiments, the baseband processor circuit 1404A can access the communication protocol stack 1436 in the memory / storage device 1412 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1404A can access the communication protocol stack 1436 to perform the following operations: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1408.

[0209] The baseband processor circuit 1404A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0210] The memory / storage 1412 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1436) that may be executed by one or more processors in the processor 1404 to cause the UE 1400 to perform various operations described herein. The memory / storage 1412 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some embodiments, some of the memory / storage 1412 may be located on the processor 1404 itself (e.g., L1 cache and L2 cache), while other memory / storage 1412 is located external to the processor 1404 but accessible via a memory interface. The memory / storage 1412 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0211] The RF interface circuit 1408 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1400 to communicate with other devices through a radio access network. The RF interface circuit 1408 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, and control circuits.

[0212] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1426 and continue to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1404.

[0213] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the signal through a power amplifier before the RF signal is radiated across the air interface via the antenna structure 1426.

[0214] In various embodiments, the RF interface circuit 1408 may be configured to send / receive signals in a manner compatible with NR access technology.

[0215] The antenna structure 1426 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. The antenna structure 1426 may have antenna panels that are omnidirectional, directional, or a combination thereof to achieve beamforming and multiple input / multiple output communications. The antenna structure 1426 may include microstrip antennas, printed antennas manufactured on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. The antenna structure 1426 may have one or more panels designed for a specific frequency band, including a frequency band in FR1 or FR2.

[0216] The user interface 1416 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1400. The user interface 1416 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual components for accepting input, and in particular includes one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, or a headset, etc. The output device circuit includes any physical or virtual components for displaying information or otherwise delivering information (such as sensor readings, actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1400.

[0217] Sensors 1420 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to some other device, module, or subsystem. Examples of such sensors include: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0218] The driver circuit 1422 may include software and hardware elements that operate to control a particular device embedded in, attached to, or otherwise communicatively coupled to the UE 1400. The driver circuit 1422 may include various drivers to allow other components to interact with or control various I / O devices that may be present in or connected to the UE 1400. For example, the driver circuit 1422 may include circuits that facilitate coupling a UICC (e.g., UICC 148) to the UE 1400. For additional examples, the driver circuit 1422 may include: a display driver for controlling and allowing access to a display device; a touch screen driver for controlling and allowing access to a touch screen interface; a sensor driver for obtaining sensor readings of the sensor 1420 and controlling and allowing access to the sensor 1420; a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; an audio driver for controlling and allowing access to one or more audio devices.

[0219] The PMIC 1424 may manage the power provided to various components of the UE 1400. Specifically, for the processor 1404, the PMIC 1424 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0220] In some embodiments, the PMIC 1424 may control or otherwise be a part of various power saving mechanisms of the UE 1400, including DRX, as discussed herein.

[0221] The battery 1428 can power the UE 1400, but in some examples, the UE 1400 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. The battery 1428 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1428 can be a typical lead-acid car battery.

[0222] Fig.15 Illustrated is a network node 1500 according to some embodiments. The network node 1500 may be similar to, and substantially interchangeable with, a base station 108 or a server in a core network or an external data network.

[0223] The network node 1500 may include a processor 1504 , RF interface circuitry 1508 (if implemented as an access node), core network (CN) interface circuitry 1512 , memory / storage circuitry 1516 , and antenna structures 1526 .

[0224] Components of network node 1500 may be coupled to various other components via one or more interconnects 1528 .

[0225] The processor 1504, RF interface circuit 1508, memory / storage circuit 1516 (including communication protocol stack 1510), antenna structure 1526 and interconnect 1528 may be similar to those of reference Fig.14 Like named elements are shown and described.

[0226] The CN interface circuit 1512 may provide a connection to a core network (e.g., a 5GC using a 5th generation core network (5GC) compatible network interface protocol such as a carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the network node 1500 via optical fiber or wireless backhaul. The CN interface circuit 1512 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1512 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0227] In some embodiments, the network node 1500 may use antenna structures 1526, CN interface circuits, or other interface circuits to couple to a transmit receive point (TRP).

[0228] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 the authorized use should be clearly stated to users.

[0229] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following embodiments section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the examples section.

[0230] Example

[0231] In the following sections, additional exemplary aspects are provided.

[0232] Embodiment 1 includes a method of operating a user equipment (UE), the method comprising: determining a mapping of multiple buffer conditions to one or more buffer status report (BSR) formats; detecting a condition of the UE's buffer corresponding to a first buffer condition among the multiple buffer conditions; selecting a BSR format associated with the first buffer condition among the one or more BSR formats based on the mapping; generating a BSR medium access control (MAC) control element (CE) having the BSR format; and sending the BSR MAC CE to a base station.

[0233] Embodiment 2 includes the method according to embodiment 1 or some other embodiment herein, further comprising: receiving configuration information from the base station; and determining the mapping based on the configuration information.

[0234] Embodiment 3 includes a method according to embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on a determination of all protocol data units (PDUs) in a set of PDUs that an application needs to buffer.

[0235] Embodiment 4 includes a method as in embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a remaining time until a delivery deadline of the buffered data and a predetermined threshold.

[0236] Embodiment 5 includes a method according to embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a queue time of buffered data with a predetermined threshold.

[0237] Embodiment 6 includes a method as in embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on a comparison of an amount of buffered data to a predetermined threshold.

[0238] Embodiment 7 includes a method according to embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on an importance or priority associated with a set of buffered protocol data units (PDUs).

[0239] Embodiment 8 includes a method according to embodiment 1 or some other embodiment herein, wherein the first buffer condition is based on whether a packet is discarded for a set of PDUs configured for buffering or a radio bearer corresponding to the set of PDUs buffered.

[0240] Embodiment 9 includes a method according to any one of embodiments 1 to 8 or some other embodiment herein, wherein the buffer includes services for one or more logical channels (LCHs) in one or more logical channel groups (LCGs), and the buffer condition is associated with one or more of the multiple LCHs or with any of the multiple LCHs.

[0241] Embodiment 10 includes a method according to embodiment 1 or some other embodiment of the present invention, wherein the condition is a first condition, the BSR format is a first BSR format, the BSRMAC CE is a first BSRMAC CE, and the method further includes: detecting a second condition of the buffer, the second condition corresponding to a second buffer condition among the multiple buffer conditions; identifying a second BSR format associated with the second buffer condition among the one or more BSR formats based on the configuration information; generating a second BSR MAC CE having the second BSR format; and sending the second BSR MAC CE together with the first BSR MAC CE to the base station.

[0242] Embodiment 11 includes a method according to embodiment 1 or some other embodiment of the present invention, wherein the BSR format is a first BSR format, the BSR MAC CE is a first BSR MAC CE, and the method further includes: selecting a second BSR format associated with the buffer condition from among the one or more BSR formats based on the mapping; generating a second BSR MAC CE having the second BSR format; and sending the second BSR MAC CE together with the first BSR MAC CE to the base station.

[0243] Embodiment 12 includes a method according to embodiment 1 or some other embodiment of the present invention, wherein generating the BSR MAC CE includes: identifying an information type value based on the condition of the buffer; and including the information type value in a type field of the BSR MAC CE to indicate the type of information included in the BSR MAC CE.

[0244] Embodiment 13 includes a method according to embodiment 12 or some other embodiment herein, wherein the type of information includes: queuing information associated with the buffer, delay information associated with the buffer, or characteristics of a set of protocol data units (PDUs) in the buffer.

[0245] Embodiment 14 includes a method of operating a user equipment (UE), the method comprising: determining a mapping of multiple buffer conditions to one or more buffer status report (BSR) tables; detecting a condition of the UE's buffer corresponding to a first buffer condition among the multiple buffer conditions; selecting a BSR table associated with the first buffer condition among the one or more BSR tables based on the mapping; generating a BSR medium access control (MAC) control element (CE) having an index selected from the BSR table; and sending the BSR MAC CE to a base station.

[0246] Embodiment 15 includes a method according to embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on a determination of whether all protocol data units (PDUs) in a set of PDUs need to be buffered by the application.

[0247] Embodiment 16 includes the method of embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a remaining time until a delivery deadline of the buffered data and a predetermined threshold.

[0248] Embodiment 17 includes a method according to embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a queue time of the buffered data with a predetermined threshold.

[0249] Embodiment 18 includes the method of embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on a comparison of an amount of buffered data to a predetermined threshold.

[0250] Embodiment 19 includes a method according to embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on an importance or priority associated with a set of buffered protocol data units (PDUs).

[0251] Embodiment 20 includes a method according to embodiment 14 or some other embodiment herein, wherein the first buffer condition is based on whether packet discard is configured for a set of PDUs buffered.

[0252] Embodiment 21 includes a method according to any one of embodiments 14 to 20 or some other embodiment herein, wherein the buffer includes services for one or more logical channels (LCHs) in one or more logical channel groups (LCGs), and the buffer condition is associated with one or more of the multiple LCHs or with any of the multiple LCHs.

[0253] Embodiment 22 includes a method according to embodiment 14 or some other embodiment of the present invention, wherein the condition is a first condition, the BSR table is a first BSR table, the BSR MAC CE is a first BSR MAC CE, the index is a first index, and the method further includes: detecting a second condition of the buffer, the second condition corresponding to a second buffer condition among the multiple buffer conditions; identifying a second BSR table associated with the second buffer condition among the one or more BSR tables based on the configuration information; generating a second BSR MAC CE having a second index selected from the second BSR table; and sending the second BSR MAC CE together with the first BSR MAC CE to the base station.

[0254] Embodiment 23 includes a method for operating a user equipment (UE), the method comprising: receiving configuration information from a base station, the configuration information being used to map multiple buffer conditions to one or more buffer status report (BSR) timer configurations; detecting a condition of the buffer of the UE corresponding to a first buffer condition among the multiple buffer conditions; identifying a BSR timer configuration associated with the first buffer condition among the multiple BSR timer configurations based on the configuration information; and setting a timer based on the BSR timer configuration.

[0255] Embodiment 24 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on a determination of all protocol data units (PDUs) in a set of PDUs that the application needs to buffer.

[0256] Embodiment 25 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a remaining time until a delivery deadline of the buffered data and a predetermined threshold.

[0257] Embodiment 26 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on a comparison of a queue time of the buffered data with a predetermined threshold.

[0258] Embodiment 27 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on a comparison of the amount of buffered data to a predetermined threshold.

[0259] Embodiment 28 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on an importance or priority associated with a set of buffered protocol data units (PDUs).

[0260] Embodiment 29 includes a method according to embodiment 23 or some other embodiment herein, wherein the first buffer condition is based on whether the packet discard is configured for a buffered PDU set or a radio bearer corresponding to the buffered PDU set.

[0261] Embodiment 30 includes a method according to any one of embodiments 23 to 29 or some other embodiment herein, wherein the buffer includes services for multiple logical channels (LCHs) in one or more logical channel groups (LCGs), and the first buffer condition is associated with one of the multiple LCHs or is associated with any of the multiple LCHs.

[0262] Embodiment 31 includes a method according to embodiment 23 or some other embodiment herein, wherein the timer is a periodic BSR timer, a retransmission BSR timer, or a logical channel scheduling request delay timer.

[0263] Embodiment 32 comprises a method, the method comprising: generating configuration information for mapping a plurality of buffer conditions to one or more buffer status report (BSR) formats, BSR tables, or BSR timer configurations; and sending the configuration information to a user equipment.

[0264] Embodiment 33 includes a method according to embodiment 32 or some other embodiment herein, the method further comprising: generating the configuration information based on characteristics associated with uplink traffic from the UE.

[0265] Embodiment 34 includes a method of operating a user equipment (UE), the method comprising: detecting an event associated with a buffer; determining that a delay timer associated with a buffer status report (BSR) type is running; determining that the event is a predetermined trigger event; and triggering a BSR of the BSR type or a scheduling request (SR) for the BSR before the natural expiration of the delay timer based on determining that the event is the predetermined trigger event.

[0266] Embodiment 35 includes a method according to embodiment 34 or some other embodiment of the present invention, the method further comprising: considering that the delay timer will expire before the natural expiration based on determining that the event is the predetermined triggering event; and triggering the BSR or the SR for the BSR based on determining that the delay timer has expired.

[0267] Embodiment 36 includes the method according to embodiment 35 or some other embodiment of the present invention, and the method further includes: stopping the delay timer before the natural expiration based on determining that the event is the predetermined triggering event, wherein the determination of the expiration of the delay timer is based on the stopping of the delay timer.

[0268] Embodiment 37 includes a method according to embodiment 34 or some other embodiment herein, wherein the method includes triggering the BSR before the natural expiration of the delay timer, and: the delay timer is a retransmission BSR timer and the BSR type is a regular BSR type; or the delay timer is a periodic BSR timer and the BSR type is a periodic BSR type.

[0269] Embodiment 38 includes a method according to embodiment 34 or some other embodiment herein, wherein the method includes triggering the SR for the BSR before the natural expiration of the delay timer, the delay timer is a logical channel SR delay timer, and the BSR type is a regular BSR type.

[0270] Embodiment 39 includes a method according to embodiment 34 or some other embodiment herein, wherein the BSR corresponds to a logical channel and the predetermined triggering event includes discarding packets associated with the logical channel from the buffer.

[0271] Embodiment 40 comprises a method according to embodiment 34 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and the predetermined trigger event comprises a queuing delay time for data associated with the logical channel in the buffer exceeding a predetermined threshold.

[0272] Embodiment 41 comprises a method according to embodiment 34 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and the predetermined trigger event comprises a remaining time until a delivery deadline for data associated with the logical channel in the buffer being less than a predetermined threshold.

[0273] Embodiment 42 includes a method according to embodiment 34 or some other embodiment herein, wherein the predetermined triggering event includes an amount of data in the buffer exceeding a predetermined threshold.

[0274] Embodiment 43 comprises a method according to embodiment 34 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and the predetermined trigger event comprises a first set of protocol data units (PDUs) arriving in the buffer with a first priority or importance level, the first priority or importance level being greater than any priority or importance level of a set of PDUs associated with the logical channel in the buffer when the first set of PDUs arrives in the buffer.

[0275] Embodiment 44 includes a method according to embodiment 34 or some other embodiment herein, wherein the predetermined triggering event includes a number of protocol data units (PDUs) in a set of PDUs in the buffer exceeding a predetermined threshold.

[0276] Embodiment 45 includes the method of embodiment 34 or some other embodiment herein, wherein the predetermined triggering event includes a burst of data arriving in the buffer with a size exceeding a predetermined threshold.

[0277] Embodiment 46 includes a method of operating a user equipment (UE), the method comprising: detecting a trigger event associated with a buffer; triggering a BSR type that takes precedence over a regular buffer status report (BSR) type, a periodic BSR type, and a fill BSR type based on detecting the trigger event; and sending the BSR.

[0278] Embodiment 47 includes a method according to embodiment 46 or some other embodiment herein, wherein the BSR type is not associated with a retransmission BSR timer, a periodic BSR timer, or a logical channel scheduling request delay timer.

[0279] Embodiment 48 includes a method according to embodiment 46 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and detecting the triggering event includes: determining to discard packets associated with the logical channel from the buffer.

[0280] Embodiment 49 comprises a method according to embodiment 46 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and detecting the triggering event comprises: determining that a queuing delay time for data associated with the logical channel in the buffer exceeds a predetermined threshold.

[0281] Embodiment 50 includes a method according to embodiment 46 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and detecting the triggering event includes: determining that the remaining time until the delivery deadline for data associated with the logical channel in the buffer is less than a predetermined threshold.

[0282] Embodiment 51 includes a method according to embodiment 46 or some other embodiment herein, wherein detecting the triggering event includes: determining that the amount of data in the buffer exceeds a predetermined threshold.

[0283] Embodiment 52 includes a method according to embodiment 46 or some other embodiment herein, wherein the BSR corresponds to a logical channel, and detecting the triggering event includes: determining that a first set of protocol data units (PDUs) having a first priority or importance level arrives in a buffer; and determining that the first priority or importance level is greater than any priority or importance level of a set of PDUs associated with the logical channel in the buffer when the first set of PDUs arrives in the buffer.

[0284] Embodiment 53 includes a method according to embodiment 46 or some other embodiment herein, wherein detecting the triggering event includes: determining that a number of protocol data units (PDUs) in a set of PDUs in the buffer exceeds a predetermined threshold.

[0285] Embodiment 54 includes the method of embodiment 46 or some other embodiment herein, wherein detecting the triggering event includes determining that a burst of data arrives in the buffer with a size exceeding a predetermined threshold.

[0286] Embodiment 55 comprises a method of operating a user equipment (UE), the method comprising: triggering a buffer status report associated with a buffer; discarding packets of uplink data from the buffer after triggering the buffer status report; and canceling the buffer status report based on discarding the packets from the buffer.

[0287] Embodiment 56 includes the method according to embodiment 51 or some other embodiment herein, the method further comprising: stopping a delay timer associated with the buffer status report based on canceling the buffer status report.

[0288] Embodiment 57 includes a method according to embodiment 51 or some other embodiment herein, the method further comprising: discarding one or more packets of the uplink data from the buffer, the one or more packets including the packet; determining that the size of an aggregation of the one or more packets is greater than a predetermined threshold size; and canceling the buffer status report based on determining that the size of the aggregation is greater than the predetermined threshold size.

[0289] Another embodiment may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Embodiments 1 to 57 or any other method or process described herein.

[0290] Another embodiment may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 57, or any other method or process described herein.

[0291] Another embodiment may include a method, technique or process described or related to any one of Embodiments 1 to 57 or a portion or part thereof.

[0292] Another embodiment may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform methods, techniques, or processes described in or related to any one of embodiments 1 to 57 or portions thereof.

[0293] Another embodiment comprises a signal as described or relating to any one of embodiments 1 to 57 or parts or components thereof.

[0294] Another embodiment may include a datagram, information element, packet, frame, segment, PDU or message as described or related to any one of embodiments 1 to 57 or parts or parts thereof or otherwise described in the present disclosure.

[0295] Another embodiment may include a signal encoded with data as described or associated with any one of embodiments 1 to 57, or portions or parts thereof, or as otherwise described in this disclosure.

[0296] Another embodiment may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described or related to any one of embodiments 1 to 57 or parts or components thereof or otherwise described in the present disclosure.

[0297] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process described in or related to any one or part of Embodiments 1 to 57.

[0298] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process described or related to any one or part of embodiments 1 to 57.

[0299] Another embodiment may include a signal in a wireless network as shown and described herein.

[0300]

[0013] Another embodiment may include a method of communicating in a wireless network as shown and described herein.

[0301]

[0013] Another embodiment may include a system for providing wireless communications as shown and described herein.

[0302]

[0013] Another embodiment may include an apparatus for providing wireless communications as shown and described herein.

[0303] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the various aspects to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various aspects.

[0304] Although the above aspects have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. A method of operating a user equipment (UE), the method comprising: determining a mapping of a plurality of buffer conditions to one or more buffer status report (BSR) formats; detecting a condition of a buffer of the UE corresponding to a first buffer condition of the plurality of buffer conditions; selecting, based on the mapping, a BSR format of the one or more BSR formats associated with the first buffer condition; generating a BSR medium access control (MAC) control element (CE) having the BSR format; and The BSR MAC CE is sent to the base station.

2. The method according to claim 1, further comprising: receiving configuration information from the base station; as well as The mapping is determined based on the configuration information.

3. A method according to claim 1, wherein the first buffer condition is based on: a determination of whether the application requires all PDUs in a buffered protocol data unit (PDU) set; a comparison of the remaining time until the delivery deadline of the buffered data with a predetermined threshold; a comparison of the queuing time of the buffered data with a predetermined threshold; a comparison of the amount of buffered data with a predetermined threshold; an importance or priority associated with the buffered protocol data unit (PDU) set; or whether packet discarding is configured for the buffered PDU set or the radio bearer corresponding to the buffered PDU set.

4. The method according to any one of claims 1 to 3, wherein the buffer includes services of multiple logical channels (LCHs) for one or more logical channel groups (LCGs), and the first buffer condition is associated with one or more of the multiple LCHs or with any of the multiple LCHs.

5. The method according to claim 1, wherein the condition is a first condition, the BSR format is a first BSR format, the BSR MAC CE is a first BSR MAC CE, and the method further comprises: detecting a second condition of the buffer zone, the second condition corresponding to a second buffer zone condition among the plurality of buffer zone conditions; identifying, based on configuration information from the base station, a second BSR format of the one or more BSR formats associated with the second buffer condition; generating a second BSR MAC CE having the second BSR format; as well as The second BSR MAC CE is sent to the base station together with the first BSR MAC CE.

6. The method of claim 1, wherein the BSR format is a first BSR format, The BSR MAC CE is a first BSR MAC CE, and the method further includes: selecting, based on the mapping, a second BSR format of the one or more BSR formats associated with the first buffer condition; generating a second BSR MAC CE having the second BSR format; as well as The second BSR MAC CE is sent to the base station together with the first BSR MAC CE.

7. The method according to claim 1, wherein generating the BSR MAC CE comprises: identifying an information type value based on the condition of the buffer; as well as including the information type value in a type field of the BSR MAC CE to indicate the type of information included in the BSR MAC CE, The type of the information includes: queuing information associated with the buffer, delay information associated with the buffer, or characteristics of a set of protocol data units (PDUs) in the buffer.

8. A method of operating a user equipment (UE), the method comprising: determining a mapping of a plurality of buffer conditions to one or more buffer status report (BSR) tables; detecting a condition of a buffer of the UE corresponding to a first buffer condition of the plurality of buffer conditions; selecting, based on the mapping, a BSR table of the one or more BSR tables associated with the first buffer condition; generating a BSR medium access control (MAC) control element (CE) having an index selected from the BSR table; and The BSR MAC CE is sent to the base station.

9. A method according to claim 8, wherein the first buffer condition is based on: a determination of whether the application requires all PDUs in a buffered protocol data unit (PDU) set; a comparison of the remaining time until the delivery deadline of the buffered data with a predetermined threshold; a comparison of the queuing time of the buffered data with a predetermined threshold; a comparison of the amount of buffered data with a predetermined threshold; or an importance or priority associated with the buffered protocol data unit (PDU) set; whether packet discarding is configured for the buffered PDU set.

10. A method according to claim 8 or 9, wherein the buffer includes services of multiple logical channels (LCHs) for one or more logical channel groups (LCGs), and the first buffer condition is associated with one or more of the multiple LCHs or with any of the multiple LCHs.

11. The method according to claim 8, wherein the condition is a first condition, the BSR table is a first BSR table, the BSR MAC CE is a first BSR MAC CE, the index is a first index, and the method further comprises: detecting a second condition of the buffer zone, the second condition corresponding to a second buffer zone condition among the plurality of buffer zone conditions; identifying, based on configuration information from the base station, a second BSR table of the one or more BSR tables associated with the second buffer condition; generating a second BSR MAC CE having a second index selected from the second BSR table; as well as The second BSR MAC CE is sent to the base station together with the first BSR MAC CE.

12. A method of operating a user equipment (UE), the method comprising: receiving configuration information from a base station, the configuration information being used to map a plurality of buffer conditions to one or more buffer status report (BSR) timer configurations; detecting a condition of a buffer of the UE corresponding to a first buffer condition of the plurality of buffer conditions; identifying, based on the configuration information, a BSR timer configuration of the one or more BSR timer configurations associated with the first buffer condition; as well as A timer is set based on the BSR timer configuration.

13. A method according to claim 12, wherein the first buffer condition is based on: a determination of whether the application requires all PDUs in a buffered protocol data unit (PDU) set; a comparison of the remaining time until the delivery deadline of the buffered data with a predetermined threshold; a comparison of the queuing time of the buffered data with a predetermined threshold; a comparison of the amount of buffered data with a predetermined threshold; an importance or priority associated with the buffered protocol data unit (PDU) set; or whether packet discarding is configured for the buffered PDU set or the radio bearer corresponding to the buffered PDU set.

14. A method according to claim 12 or 13, wherein the buffer includes services of multiple logical channels (LCHs) for one or more logical channel groups (LCGs), and the first buffer condition is associated with one LCH among the multiple LCHs or is associated with any LCH among the multiple LCHs.

15. The method of claim 12, wherein the timer is a periodic BSR timer, a retransmission BSR timer, or a logical channel scheduling request delay timer.

16. A method comprising: generating configuration information for mapping a plurality of buffer conditions to one or more buffer status report (BSR) formats, BSR tables, or BSR timer configurations; as well as The configuration information is sent to a user equipment (UE).

17. The method according to claim 16, further comprising: The configuration information is generated based on characteristics associated with uplink traffic from the UE.

18. A method of operating a user equipment (UE), the method comprising: Detecting events associated with a buffer; determining that a delay timer associated with a buffer status report (BSR) type is running; determining that the event is a predetermined triggering event; as well as A BSR of the BSR type or a scheduling request (SR) for the BSR is triggered before natural expiration of the delay timer based on determining that the event is the predetermined triggering event.

19. The method according to claim 18, further comprising: considering that the delay timer will expire prior to the natural expiration based on determining that the event is the predetermined triggering event; as well as The BSR or the SR for the BSR is triggered based on determining that the delay timer expires.

20. The method according to claim 19, further comprising: stopping the delay timer prior to the natural expiration based on determining that the event is the predetermined triggering event, Wherein said determining that said delay timer has expired is based on said stopping said delay timer.

21. The method of claim 18, wherein the method comprises triggering the BSR prior to the natural expiration of the delay timer, and: The delay timer is a BSR retransmission timer, and the BSR type is a normal BSR type; or The delay timer is a periodic BSR timer, and the BSR type is a periodic BSR type.

22. The method of claim 18, wherein the method comprises triggering the SR for the BSR before the natural expiration of the delay timer, the delay timer is a logical channel SR delay timer, and the BSR type is a regular BSR type.

23. The method of claim 18, wherein the BSR corresponds to a logical channel, and the predetermined triggering event comprises: discarding packets associated with the logical channel from the buffer; a queuing delay time for data associated with the logical channel in the buffer exceeds a predetermined threshold; a remaining time until a delivery deadline for data associated with the logical channel in the buffer is less than a predetermined threshold; Or a first set of protocol data units (PDUs) arrives in the buffer with a first priority or importance level, which is greater than any priority or importance level of a set of PDUs associated with the logical channel in the buffer when the first set of PDUs arrives in the buffer.

24. The method of claim 18, wherein the predetermined triggering event comprises an amount of data in the buffer exceeding a predetermined threshold.

25. The method of claim 18, wherein the predetermined triggering event comprises a number of protocol data units (PDUs) in a set of PDUs in the buffer exceeding a predetermined threshold.

26. The method of claim 18, wherein the predetermined triggering event comprises the arrival of a burst of data in the buffer at a size exceeding a predetermined threshold.

27. A method of operating a user equipment (UE), the method comprising: detecting trigger events associated with the buffer; triggering a buffer status report (BSR) type having priority over a regular BSR type, a periodic BSR type, and a padding BSR type based on detecting the triggering event; as well as Send the BSR.

28. The method of claim 27, wherein the BSR corresponds to a logical channel and detecting the triggering event comprises: It is determined that packets associated with the logical channel were discarded from the buffer.

29. The method of claim 27, wherein the BSR corresponds to a logical channel and detecting the triggering event comprises: determining that a queuing delay time for data associated with the logical channel in the buffer exceeds a predetermined threshold; Determining that the remaining time until a delivery deadline for data associated with the logical channel in the buffer is less than a predetermined threshold; or determining that a first set of protocol data units (PDUs) having a first priority or importance level arrives in the buffer, and determining that the first priority or importance level is greater than any priority or importance level of a set of PDUs associated with the logical channel in the buffer when the first set of PDUs arrives in the buffer.

30. The method of claim 27, wherein detecting the triggering event comprises: It is determined that the amount of data in the buffer exceeds a predetermined threshold.

31. The method of claim 27, wherein detecting the triggering event comprises: determining that a number of protocol data units (PDUs) in a set of PDUs in the buffer exceeds a predetermined threshold; or A burst of data is determined to arrive in the buffer with a size exceeding a predetermined threshold.

32. A method of operating a user equipment (UE), the method comprising: triggering a buffer status report associated with the buffer; discarding packets of uplink data from the buffer after triggering the buffer status report; as well as The buffer status report is canceled based on discarding the packet from the buffer.

33. The method according to claim 32, further comprising: A delay timer associated with the buffer status report is stopped based on canceling the buffer status report.

34. The method of claim 32, further comprising: discarding one or more packets of the uplink data from the buffer, the one or more packets including the packet; determining that a size of an aggregate of the one or more packets is greater than a predetermined threshold size; as well as The buffer status report is cancelled based on determining that the aggregate size is greater than the predetermined threshold size.

Images