MÉTODOS EXECUTADOS POR UM EQUIPAMENTO DE USUÁRIO E POR UM NÓ DE REDE, EQUIPAMENTO DE USUÁRIO, E, NÓ DE REDE

Enhanced BSR reporting through additional BS tables and RRC-based load balancing systems addresses inefficiencies in 5G NR for XR and cloud gaming, ensuring accurate resource allocation and reduced latency.

BR112025024620A2Pending Publication Date: 2026-11-10TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
BR112025024620
Authority / Receiving Office
BR · BR
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing 5G NR systems face challenges in accurately reporting buffer status for high data rate and low latency applications like XR and cloud gaming, leading to inefficient resource allocation and latency spikes due to limited BSR formats and tables, which are inadequate for handling varying frame sizes and periodic traffic patterns.

Method used

Introduce additional Buffer Status Tables (BS) and RRC-based load balancing systems to enhance BSR reporting, allowing for more precise uplink resource allocation by configuring multiple BS tables and incorporating time-related information, along with new BSR formats that indicate the use of legacy or new tables.

Benefits of technology

Improves resource allocation efficiency, reduces latency spikes, and enhances network capacity by providing accurate buffer state information, thereby supporting high data rate and low latency applications effectively.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

A method (1500) performed by a user equipment, UE (712), configured with a plurality of Buffer Status, BS, tables is provided for use in preparing a Buffer Status Report, BSR. The method includes transmitting (1502), to a network node (710), information indicating at least one BS table and / or BS table index used for preparing the BSR.
Need to check novelty before this filing date? Find Prior Art

Description

/ 82 METHODS EXECUTED BY A USER DEVICE AND BY A NETWORK NODE, USER DEVICE, AND, NETWORK NODE TECHNICAL AREA

[001] This description refers generally to wireless communications and, more particularly, to systems and methods that utilize a combined buffer state reporting design for legacy and new XR tables. BACKGROUND

[002] 5G is the fifth generation of mobile communications, encompassing a wide range of use cases, from enhanced mobile broadband (eMBB) to ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC). 5G includes the New Radio (NR) access layer interface and the 5G network core (5th generation CN). The physical and upper layers of NR reuse parts of the Long Term Evolution (LTE) specification and add necessary components when driven by new use cases.

[003] Low latency, high throughput applications, such as Extended Reality (XR) and cloud gaming are important in the 5G era. XR can refer to all combined real and virtual environments and human-machine interactions generated by computing technology and wearable devices. It is an umbrella term for different types of realities, including virtual reality (VR), augmented reality (AR), mixed reality (MR), and the areas interpolated between them. Levels of virtuality range from partial sensory inputs to fully immersive virtual reality.

[004] 5G NR was designed to support applications that require high throughput and low latency, in line with the requirements imposed by support for XR applications and cloud gaming on NR networks. 3rd Generation Partnership Project (3GPP) Version 17 contains an item of Petition 870260001315, dated 07 / 01 / 2026, page 7 / 114 / 82 study on XR evaluations for NR. The main objectives are to identify the traffic model for each application of interest, the evaluation methodology and the main performance indicators of interest for relevant deployment scenarios, and to carry out performance evaluations accordingly, in order to investigate possible standardization improvements in potential subsequent study / work items. Low-latency, high-rate XR applications

[005] Low-latency applications, such as XR and cloud gaming, require limited latency, not necessarily ultra-low latency. The end-to-end latency budget can range from 20 to 80 ms, needing to be distributed among various components, including application processing latency, transport latency, radio link latency, etc. For these applications, short transmission time intervals (TTIs) or mini-slots aimed at ultra-low latency may not be effective.

[006] Figure 1 illustrates an example of frame latency measured in a radio access network (RAN), excluding application and network core latencies. Frame latency spikes can be observed in the RAN. Latency spikes occur due to instantaneous scarcity of radio resources or inefficient allocation of these resources in response to frame size variations. Causes of latency spikes can include queuing delay, time-varying radio environments, time-varying frame sizes, among others. Tools that help eliminate latency spikes are beneficial for enabling better 5G support for this type of traffic.

[007] In addition to limited latency requirements, applications such as XR and cloud gaming also require high-speed transmission. This can be seen in the large frame sizes originating from this type of traffic. Typical frame sizes can range from tens of kilobytes to Petition 870260001315, dated 07 / 01 / 2026, p. 8 / 114 / 82 hundreds of kilobytes. Frame arrival rates can be 60 or 120 frames per second (fps). As a concrete example, a frame size of 100 kilobytes and a frame arrival rate of 120 fps can result in a required rate of 95.8 Mbps.

[008] A large video frame is typically fragmented into smaller Internet Protocol (IP) packets and transmitted as multiple transport blocks (TBs) across multiple TTIs in the RAN. Figure 2 illustrates an example of the cumulative distribution functions of the number of TBs required to deliver a video frame ranging in size from 20 KB to 300 KB. For example, Figure 2 illustrates that to deliver frames with a size of 200 KB each, the median number of TBs required is 5.

[009] Figure 3 illustrates the characteristics of XR traffic compared to Voice over IP (VoIP) and web browsing. Specifically, as illustrated, the characteristics of incoming XR traffic are quite distinct from typical web browsing and VoIP traffic. Arrival time is expected to be nearly periodic and largely predictable, as with VoIP. However, the size of its data is an order of magnitude larger than that of VoIP, as discussed above.Furthermore, similar to web browsing, the size of the data varies with each arrival of a Packet Data Unit (PDU) from the application, due to the dynamics of the content and human movement. 5G buffer status report

[0010] The user equipment (UE) informs the network of the buffer status awaiting transmission in the Buffer Status Report (BSR) of the Medium Access Control Element (MAC CE). According to version 17, there are four different BSR formats that UEs can send to the network: - Short BSR format (fixed size) - Short truncated BSR format (fixed size) Petition 870260001315, dated 07 / 01 / 2026, page 9 / 114 / 82 - Long truncated BSR format (variable size) - long BSR format (variable size)

[0011] Figure 4 illustrates the short BSR format and the short truncated BSR format. Figure 5 illustrates the long BSR format and the long truncated BSR format.

[0012] There are 3 types of BSRs: regular BSR, periodic BSR and filler BSR.

[0013] The regular BSR is triggered if uplink (UL) data for a logical channel belonging to a Logical Channel Group (LCG) becomes available to the MAC entity and this UL data belongs to a logical channel with a higher priority than the priority of any logical channel containing available UL data belonging to any LCG, or if none of the logical channels belonging to an LCG contain available UL data. When more than one LCG has data available for transmission, the UE uses the long BSR format and reports all LCGs that have data. However, if only one LCG has data, the short BSR format is used.

[0014] Periodic BSR is configured by the network. When configured, the UE periodically reports the BSR. When more than one LCG has data available for transmission, the UE uses the long BSR format and reports all LCGs that have data. However, if only one LCG has data, the short BSR format will be used.

[0015] The padding BSR is an opportunistic method for providing buffer state information to the network when the PDU MAC contains a number of padding bits equal to or greater than one of the BSR formats. In this case, the UE would add the padding BSR, replacing the corresponding padding bits. In this case, the BSR format to be used depends on the number of padding bits, the number of logical channels that have data for transmission, and the size of the format. Petition 870260001315, dated 07 / 01 / 2026, p. 10 / 114 / 82 BSR. When more than one LCG has data to transmit, one of the following three formats is used: short truncated BSR, long BSR, or long truncated BSR. The choice of BSR format depends on the number of padding bits available. When only one LCG has data to transmit, then the short BSR format is used.

[0016] For an UE, a PDU MAC can contain at most one CE MAC BSR. 3GPP Standardization

[0017] During version 18, RAN2 discussed improving the existing buffer status report to support high data rate and low latency XR applications.

[0018] To improve uplink resource scheduling for XR, the following BSR enhancements are under discussion during WI release 18: - One or more additional Buffer Status Tables (BS) to reduce quantization errors in BSR reports (e.g., for high bit rates); - Knowledge about the delay of buffered data, including, for example, the remaining time, and the distinction between the amount of buffered data and the delay period. It remains to be determined whether delay information will be reported as part of the BSR or as a new MAC CE. Furthermore, further investigation is needed into how to keep delay information up-to-date, considering, for example, scheduling and transmission delays.

[0019] - Additional BSR triggering conditions to allow timely availability of buffer state information can be investigated further.

[0020] However, there are some challenges currently. For example, only one short BS table and one long BS table can be Petition 870260001315, dated 07 / 01 / 2026, page 11 / 114 / 82 used. Thus, problems arise when there are several short BS tables and / or several BS tables. The problem is amplified when considering new BSR projects, such as, for example, selected table index reports and reports with BSR delays. SUMMARY

[0021] Certain aspects of the description and its modalities can provide solutions to these or other challenges. For example, methods and systems are provided to make available a new BSR format that allows generating reports from both the legacy BS table and index and the new BS tables and indexes. The new formats can also provide time-related information.

[0022] According to certain embodiments, a method of a UE configured with a plurality of BS tables for use in preparing a BSR includes transmitting, to a network node, information indicating at least one BS table and / or BS table index used to prepare the BSR.

[0023] According to certain embodiments, a UE configured with a plurality of BS tables for use in preparing a BSR is configured to transmit, to a network node, information indicating at least one BS table and / or BS table index used to prepare the BSR.

[0024] According to certain embodiments, a method performed by a network node includes receiving, from a UE configured with a plurality of BS tables for use in preparing a BSR, information indicating at least one BS table and / or BS table index used to prepare the BSR.

[0025] According to certain embodiments, a network node is configured to receive, from a UE configured with a plurality of BS tables for use in the preparation of a BSR, information indicating by Petition 870260001315, dated 07 / 01 / 2026, page 12 / 114 / 82 less a BS table and / or BS table index used to prepare the BSR.

[0026] Certain modes may provide one or more of the following technical advantages. For example, certain modes may provide the technical advantage of allowing a network to intelligently understand the type of BSR when a new BSR with a table identifier (ID) is configured. As another example, certain modes may provide a technical advantage by allowing a network to provide the ideal uplink resource allocation size to increase capacity while minimizing resource waste.

[0027] Other advantages can be easily perceived by those who have skills in the area. Certain modalities may not present any, some, or all of the advantages mentioned. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] For a more complete understanding of the described modalities, as well as their characteristics and advantages, please refer to the following description, together with the attached drawings, in which: Figure 1 illustrates an example of frame latency measured in a radio access network (RAN), excluding application and network core latencies; Figure 2 illustrates an example of the cumulative distribution functions of the number of transport blocks needed to deliver a video frame; Figure 3 illustrates the characteristics of XR traffic compared to VoIP and web browsing; Figure 4 illustrates the short BSR format and the truncated short BSR format; Figure 5 illustrates the long BSR shape and the truncated long BSR shape; Petition 870260001315, dated 07 / 01 / 2026, page 13 / 114 / 82 Figure 6 illustrates a graph demonstrating the XR capacity at various eMBB load points with different BS table step sizes (in bytes), according to certain modes; Figure 7 illustrates an example of a table / BS format when each LCG has only one new BSR configured, according to certain modalities; Figure 8 illustrates an example of a Table / BS format when each LCG has more than one new BSR configured, according to certain modalities; Figure 9 illustrates an example of a table / BS format when two new BSR tables per LCG are configured, according to certain modalities; Figure 10: an example of a Table / BS format with two bits for each LCG that has been configured with new tables, according to certain modes; Figure 11 illustrates an example of a Table / BS format in which all buckets contain data, according to certain modalities; Figure 12 illustrates an example of a Table / BS format that indicates two new tables, according to certain modalities; Figure 13 illustrates an example of a Table / BS format that has a longer L / N bit field to indicate the index of the legacy table and the new table together, according to certain modes; Figure 14 illustrates an example of a time-related information report when only the LCG has data, but three delay buckets are present, according to certain modalities; Figure 15 illustrates an example of a Table / BS format when two delay buckets contain data, according to certain modes; Figure 16 illustrates an example of a communication system, according to certain modalities; Petition 870260001315, dated 07 / 01 / 2026, page 14 / 114 / 82 Figure 17 illustrates an example of EU, according to certain modalities; Figure 18 illustrates an example of a network node, according to certain modalities; Figure 19 illustrates a block diagram of a host, according to certain modes; Figure 20 illustrates a virtualization environment in which the functions implemented by some modalities can be virtualized, according to certain modalities; Figure 21 illustrates a host communicating through a network node with a UE via a partially wireless connection, according to certain modes; Figure 22 illustrates an example of a method by a UE configured with a plurality of BS tables for use in the preparation and / or transmission of a BSR, according to certain modalities; Figure 23 illustrates an example of a method using a network node, according to certain modalities; Figure 24 illustrates a method executed by a UE configured with a plurality of BS tables for use in preparing a BSR, according to certain embodiments; and Figure 25 illustrates a method executed by a network node, according to certain modalities. DETAILED DESCRIPTION

[0029] Some of the modalities contemplated in this document will now be described in more detail with reference to the attached drawings. Examples are presented to illustrate the scope of the subject to specialists in the field. Additional information can also be found in the documents provided in the Appendix.

[0030] As used in this document, node may refer to Petition 870260001315, dated 07 / 01 / 2026, page 15 / 114 / 82 a network node or a UE (User Equipment). Examples of network nodes are NodeB, base station (BS), multi-pattern radio node (MSR), such as MSR BS, eNodeB (eNB), gNodeB (gNB), eNB master (MeNB), eNB secondary (SeNB), integrated access backhaul node (IAB), network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling the relay, radio base station (BTS), central unit (e.g., in a gNB), distributed unit (e.g., in a gNB), baseband unit, centralized baseband, CRAN, access point (AP), transmission points, transmission nodes, remote radio unit (RRU), remote radio unit (RRH), nodes in distributed antenna system (DAS), network core node (e.g., Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), operations and maintenance (O&M), operations support system (OSS), self-organizing network (SON), positioning node (e.g., E-SMLC), etc.

[0031] Another example of a node is user equipment (UE), a non-limiting term that refers to any type of wireless device that communicates with a network node and / or another UE in a cellular or mobile communication system. Examples of UE include target device, device-to-device (D2D) UE, vehicle-to-vehicle (V2V) UE, machine-type UE, UE MTC or UE capable of machine-to-machine (M2M) communication, personal digital assistant (PDA), tablet, mobile terminals, smartphone, notebook embedded equipment (LEE), notebook mounted equipment (LME), USB dongles (Unified Serial Bus), etc.

[0032] In some embodiments, the generic terminology radio network node or simply network node (NW node) is used. It can be any type of network node, which may include base station, base radio station, base radio station, base station controller, network controller, Node B Petition 870260001315, dated 07 / 01 / 2026, p. 16 / 114 / 82 evolved (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU), Remote Radio Unit (RRH), Central Unit (e.g., in a gNB), Distributed Unit (e.g., in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc.

[0033] The term radio access technology (RAT) can refer to any RAT, such as Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (EUTRA), Narrowband Internet of Things (NB-IoT), Wi-Fi, Bluetooth, next-generation RAT, NR, 4G, 5G, etc. Any equipment designated by the terms node, network node, or radio network node may be capable of supporting one or multiple RATs.

[0034] The term signal or radio signal used herein may refer to any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signals (RS), such as the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS) signals in the SS / PBCH block (SSB), the Discovery Reference Signal (DRS), the Cell-Specific Reference Signal (CRS), the Positioning Reference Signal (PRS), etc. RSs may be periodic. For example, RS events carrying one or more RSs may occur with a certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0035] Each SSB carries the New Radio Primary Synchronization Signal (NR-PSS), the New Radio Secondary Synchronization Signal (NR-SSS), and the New Radio Physical Transmission Channel (NR-PBCH) in four successive symbols. One or more Synchronization Signal Blocks (SSBs) are transmitted in an SSB burst, which repeats with a certain periodicity, such as 5 ms, 10 ms, 20 ms, 40 ms, Petition 870260001315, dated 07 / 01 / 2026, page 17 / 114 / 82 ms and 160 ms. The UE is configured with SSB information in cells of a given carrier frequency through one or more SS / PBCH block measurement timing (SMTC) configurations. The SMTC configuration comprises parameters such as SMTC periodicity, SMTC event duration, SMTC time offset relative to the reference time (e.g., server cell SFN), etc. Therefore, an SMTC event can also occur with a given periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sensing Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel that carries information from higher layers, such as data, control, etc.Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), PDCCH MTC (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (EPDCCH), etc.

[0036] The term time resource used in this document may correspond to any type of physical resource or radio resource expressed in terms of time duration. Examples of time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, slot, sub-slot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc.

[0037] The work item description for version 18 of XR includes the Petition 870260001315, dated 07 / 01 / 2026, p. 18 / 114 / 82, with the following objectives: - Improvements to BSR, including at least one or more new BS tables; (RAN2); - Delay in the communication of buffered data on the uplink; (RAN2); Please refer to RP-223502, New WID on XR enhancements for NR, 3GPP TSG RAN Meeting No. 98-e, December 12-16, 2022. One of the goals of the Work Item (WI) is to introduce additional BS tables to ensure that more accurate BSR reports are sent to the network. BS reports become less accurate as the reported index increases.

[0038] When deciding how to create the additional BS tables, the following questions should be taken into consideration:

[0039] Only specific value ranges may need to be closely monitored and generate more accurate reports.

[0040] Traffic and its characteristics can vary over time. Video frames are a typical example. Different frame types (e.g., I-frames and P-frames) are distinguished by quite different sizes and variations. Furthermore, adaptation to the sampling rate can also alter the characteristics, even for the same frame type. This results in the need to cover multiple non-consecutive ranges.

[0041] The importance of accuracy may depend on the network. Networks with high idle capacity may not be concerned with having accurate values, while networks with limited capacity may need much more accurate reports.

[0042] The specific ranges that may need to be covered also depend on the typical buffer size, which is affected by other running traffic services and by implemented network and user device (UE) features. Petition 870260001315, dated 07 / 01 / 2026, page 19 / 114 / 82

[0043] According to certain embodiments, for example, the system and methods provide a BSR format for which new BSR tables for XR applications are configured, in addition to the legacy BSR table. In one particular embodiment, for example, an extra bit field indicates the use of the legacy BSR table by logical channel group. Depending on the specific configuration of the new table, several BSR formats are proposed.

[0044] Under certain embodiments, a network has new BS tables that can be indicated by a network, in addition to the legacy short and long BS tables. The number of new BSR tables may be greater than one. When multiple new tables are configured, a UE can report the index of the BS table that is used to report the Buffer state. Thus, under certain embodiments, a new BSR format is designed to ensure UE indication when new BS tables for XR are configured for use in conjunction with a legacy BS table.

[0045] The new long BSR format was designed based on the legacy BSR format. However, according to certain modalities, new fields are added.

[0046] For example, In a particular embodiment, a new additional byte is added, in which each bit indicates whether the legacy table (L) or the new table (N) is being used. Buffer report Creating tables: Static and RRC-based

[0047] Three different options for creating tables were discussed at RAN2: static tables, RRC-based tables, or a combination of static and RRC-based tables.

[0048] If static tables are introduced so that the tables are pre-loaded in the UE; these tables will need to cover the entire range of BS values, since any specific part of the range may be desired. A Petition 870260001315, dated 07 / 01 / 2026, page 20 / 114 / 82, the maximum range of BS values ​​for the 5-bit BS table is currently 150,000 bytes, while for the 8-bit BS table it is 81,338,368 bytes.

[0049] If a network requires a maximum imprecision of 40 bytes, 3750 indexes are needed, resulting in the need for 118 tables, each with 32 indexes. If the imprecision were 100 bytes or 200 bytes, 47 and 24 tables would still be needed, respectively. When this is applied to the 8-bit BS table, it would result in up to approximately 1600 tables with an imprecision of 200 bytes.

[0050] Through simulations, it is possible to investigate which levels of BS table precision are needed to achieve performance improvements. Figure 6 illustrates a graph 50 demonstrating the XR capacity at various eMBB load points with different BS table step sizes (in bytes). More specifically, Figure 6 shows the results of these evaluations, where it can be observed that a smaller BS step size improves network performance by reducing padding in transmissions and thus freeing up resources that can be used to support more eMBB users. Each reduction in step size significantly improves the amount of eMBB data that can be made available. Even reducing the increment size from 500 bytes to 100 bytes already shows a considerable gain. With an XR capacity target of 90% satisfied users, the eMBB load served can be almost four times greater when going from a 2000-byte increment to a 100-byte increment.

[0051] There is a strong relationship between the minimum size value, the maximum size value, the increment, and the number of indexes in the table, and a balance between all these parameters is necessary when deciding on static tables. A simple solution for creating static tables would be to define a maximum and minimum size, as well as a given step size, and then create as many tables as needed to cover the specified range. A second, more elaborate and complex option would be to create multiple Petition 870260001315, dated 07 / 01 / 2026, page 21 / 114 / 82 combinations of minimum and maximum buffer size and step sizes.

[0052] Regardless of the solution adopted for creating static tables, the number of predefined tables is likely to be quite large. Furthermore, the UE would need to specify the index of the table it is using at any given time. This would also require adding many bits to indicate the table index, unless additional solutions are introduced, such as configuring the UE over the network with a limited set of table indexes to be used. But, in that case, the advantage of having static tables is questionable when RRC would still be necessary.

[0053] Static tables therefore have several disadvantages:

[0054] There is a trade-off between the buffer size range, granularity, and the number of static tables created, resulting in limited gains due to inflexible and suboptimal solutions.

[0055] Network conditions are not considered.

[0056] Several tables are needed to handle different combinations of range and precision.

[0057] Many bits are needed to indicate the table index (in addition to the BS index), which generates considerable overhead; or more elaborate solutions may be needed to deal with this overhead.

[0058] The disadvantages described above are eliminated by using RRC-based load balancing tables. The RRC can provide the configuration for building each load balancing table. This allows the necessary flexibility for NW to build tables considering network conditions, network configuration, and specific traffic characteristics. Creating RRC-based load balancing systems is a very simple mechanism for creating load balancing tables, while offering much more flexibility with significantly less overhead than fixed tables. Therefore, the introduction of RRC-based tables is proposed. Petition 870260001315, dated 07 / 01 / 2026, page 22 / 114 / 82

[0059] Therefore, the introduction of RRC-based tables is proposed. For example, according to certain modalities, the network provides one or more configurations for the UE to construct additional BS tables. Each of these configurations can then focus on a buffer range with the precision that the network wishes to have within that range. The use of RRC-based BS tables allows configuring a limited set of tables (e.g., from 1 to 4) to meet cases where different buffer size ranges need to be covered and these ranges cannot be reached by a single table. A larger range with the same step size or number of indexes would result in lower precision.

[0060] The number of tables to configure will depend on the network, as well as the traffic characteristics of the different XR flows. However, a reasonable limit should be set, as the table indexes may also need to be reported by the UE. Thus, 1, 2, or 4 tables per LCG should be considered. The specific value should be set considering the BSR formats and may be different for short BS tables and long BS tables.

[0061] In a particular embodiment, it is proposed that the network set up a table for the newly defined short BSR.

[0062] In a particular embodiment, it is proposed that it is preferable for the network to configure more than one table per LCG for the newly defined long BSR. The value to be selected depends on the BSR format. Configuration of BSR and BS tables

[0063] The network can provide, via RRC, the information elements to build each of the tables. This information is: BS table type, table index, initial value (bytes), maximum value (bytes) and, optionally, the step size. If the step size is explicitly indicated, this may result in not all indexes being assigned to a buffer size range. There is no problem with this, the EU simply wouldn't use them. Petition 870260001315, dated 07 / 01 / 2026, page 23 / 114 / 82, nor would I report them.

[0064] When UE builds the tables, it calculates the step size, if not provided by the network, and starts assigning a range of values ​​to each BS index. The first index would indicate a range equal to the initial value and limited by the initial value plus the step size. This is exemplified in Table 1, where an initial value of 1000 bytes was indicated and the step size was 40 bytes. Table 1: Example of a new BS table_________________ BS index BS value 0 >1000e<1040 1 <1080 2 <1120 3 <1160

[0065] In a particular embodiment, BS tables are defined by: an index, minimum value, maximum value and stepSize.

[0066] In a particular embodiment, if stepSize is not provided, the UE calculates the step size as (maximum value - minimum value) / (number of indices in the BS table).

[0067] In a particular embodiment, the tables are constructed as exemplified in Table 2. For BS index 0, the BS value is defined by: [ > minimum value and < minimum value x (stepSize x (BS index + 1)) For the next BS indices, the BS value is defined by [< minimum value x (stepSize x (BS index + 1))] Until reaching the maximum value.

[0068] As previously agreed, to simplify configuration and implementation, each LCG would be configured to use a set of additional BS tables. This is exemplified in the ASN.1 code below: MAC-CellGroupConfig ::= SEQUENCE { drx-Config SetupRelease { DRX-Config} OPTIONAL, — Need M schedulingRequestConfig Petition 870260001315, dated 07 / 01 / 2026, page 24 / 114 / 82 SchedulingRequestConfig OPTIONAL, — Need M bsr-Config OPTIONAL, — Need M BSR-Config [[ bsTablesList-r18 SEQUENCE(Size (1..maxLCG (8))) of BsTableList OPTIONAL, ]] BsTableList ::= SEQUENCE { logicalChannelGroupIndex ENUMERATED (0..maxLCG-ID), shortBsTableConfigList BsTableConfig OPTIONAL, longBsTableConfigList SEQUENCE(Size (1..aa)) OF BsTableConfig OPTIONAL} BsTableConfig ::= SEQUENCE { index INTEGER (0..aa-1), minValue INTEGER (xx..yy), maxValue INTEGER Petition 870260001315, dated 07 / 01 / 2026, p. 25 / 114 / 82 (nn..mm), stepSize INTEGER (bb..cc) OPTIONAL}

[0069] In a particular embodiment, the network associates an LCG with up to “aa” (aa depends on Proposal 2) tables for a new long BSR.

[0070] In a particular embodiment, the ASN. 1 described above is adopted for the configuration of the BS table based on RRC.

[0071] RAN2 agreed to use linear tables; however, it has not yet been decided whether other approaches can be used to create the tables. Considering that the objective is to minimize imprecision, exponential distributions are not very suitable. The quantization error is very small at the beginning and increases as the indices grow. The lower part of the exponential distribution, which is the only interesting part, could very well be defined by a linear distribution with a small step. Thus, there may be no benefit in introducing any other type of distribution, as it offers no additional gain.

[0072] In a particular embodiment, only linear distribution is allowed for the creation of the BS table. BSR format New short buffer format

[0073] For short BSR, the simplest solution is to allow a new table, which can be different for each LCG. Since the LCG is presented in short BSR format, it is not necessary to specify the table. When the new BS table is used, the UE will use a newly assigned LCID index (obtained from eLCID) for this new type of Short BSR, while the UE will use the legacy LCID index of the Short BSR (61) to report a buffer size outside the range covered by the new table. Petition 870260001315, dated 07 / 01 / 2026, page 26 / 114 / 82

[0074] In a particular embodiment, a new 5-bit BS table can be configured by LCG.

[0075] In a particular embodiment, the new BSR has the same form factor as the legacy short BSR.

[0076] In a particular embodiment, the LCID index in the MAC subheader to identify this new short BSR must be obtained from the eLCID field.

[0077] RAN2 will discuss whether it is possible to configure more tables. New long buffer format

[0078] According to certain modalities, any new long BSR format must continue to report the buffer size to the LCGs that hold data in the buffer. There are three issues to be resolved: Is it possible to configure multiple BS tables for each LCG? And, how many parts should the BS report have? How can I tell if UE is using a legacy BS table or a new BS table?

[0079] If only one new table per logical channel group is configured, an additional byte may be added. Each bit would indicate whether the legacy table (L) or the new table (N) is being used. For example, Figure 7 illustrates an example of a BS 100 table / format when each Logical Channel Group (LCG) has only one new BSR configured, according to certain modes. The example BS 100 table / format may be referred to as 'option one' in this document.

[0080] Specifically, in the example shown in Figure 7, two LCGs would set the L / N flag to “1”, while one LCG would set the “L / N” flag to “0” to indicate that it is using the legacy table. One UE will add three to indicate the BS index for three LCGs, and the reported BS index will match either the new BS table or the legacy BS table, as reported in the L / N flag. Petition 870260001315, dated 07 / 01 / 2026, page 27 / 114 / 82

[0081] This solution only allows the inclusion of a new table, regardless of whether it is specific to each LCG or common to all LCGs.

[0082] However, having more than one new table is quite important, as it may be necessary to cover different ranges. Thus, according to certain modes, two or four tables may be configured. In some specific modes, two or four tables may be preferable. In that case, additional bits will be needed to indicate them in each BS index report.

[0083] Figure 8 illustrates an example of the Table / BS 200 format when each LCG has more than one new BSR configured, according to certain modalities. The example table / BS 200 format may be referred to as 'option two' in this document.

[0084] Specifically, Figure 8 shows an option where L / N would mean legacy or new table, and one or two additional bits, “BS table”, would be used to indicate the new table index in each new octet of the table. In the example in Figure 8, the “BS table” consists of two bits and therefore can indicate one of four new tables. When the UE sets the “L” bit to zero, it will use eight bits to indicate the BS size using the legacy 8-bit BS table. In this example, two LGCs would set the L / N flag to “1” and report the 6- or 7-bit BS length along with the BS table index. On the other hand, an LCG would set the “L / N” flag to “0” to indicate that it is using the legacy table. With this format, up to 4 new BS tables can be configured and used by the UE if two bits are used for the "BS table" field, or two new tables if only one bit is used for the "BS table" field.

[0085] If the number of new BSR tables is limited to two, an additional byte can be added after L / N, indicating which of the two new tables. This allows indicating at least two new tables, while maintaining Petition 870260001315, dated 07 / 01 / 2026, page 28 / 114 / 82 8-bit BS fields, at the cost of an extra byte of overhead. Figure 9 illustrates an example of table / BS format 300 when two new BSR tables per LCG are configured, according to certain modalities. The example table / BS format 300 can be referred to as option 3 in this document and can be an alternative to option 2, discussed above. This allows indicating a maximum of two new tables, maintaining 8-bit BS fields, at the cost of an extra byte of overhead. In this example, two LCGs would set the L / N flag to “1”. For these cases, the T field would indicate one of two new tables specific to that LCG with 1 bit. On the other hand, an LCG would set the “L / N” flag to “0” to indicate that it is using the legacy table.

[0086] For example, in Figure 9, two LGCs would set the L / N flag to “1”. In these cases, the T field would indicate one of two new tables specific to that LCG with 1 bit. On the other hand, an LCG would set the “L / N” flag to “0” to indicate that it is using the legacy table. The extra byte with T fields would only be necessary if one of the LCGs used a new BS table.

[0087] Another alternative is to have two bits for each LCG that has been configured with new tables. One of the values ​​indicates the legacy table (e.g., 00), while the other three values ​​would indicate one of the three tables that could be configured. The L / N field would only be present for LCGs that have been configured to use new tables. Therefore, the overhead of this solution would still be, in most cases, one byte. This option allows configuring three new tables at the cost of only one byte, even when four LCGs are configured with new tables.

[0088] Figure 10 illustrates an example of a Table / BS 400 format with two bits for each LCG that has been configured with new tables, according to certain modalities. The sample Table / BS 400 format may be referred to as option 4 in this document. As illustrated, the two Petition 870260001315, dated 07 / 01 / 2026, p. 29 / 114 / 82. The first LCGs set the L / N flag to the new index of the BS table, while the third LCG set the L / N flag to, for example, 00 to indicate that it is using the legacy table. If these three LCGs are the only ones with data, then only three L / N fields will be present, and not all those represented in Figure 10.

[0089] A summary of the options described is shown in Table 2: Table 2 Option 1 Option 2 Option 3 Option 4 Number of BS tables 1 new 2 new (or 4 new) 2 new 3 new BS field length 8 bits 7 bits (or 6 bits) 8 bits 8 bits Height 1 byte 1 byte 2 bytes 1 to 2 bytes

[0090] From a head-height perspective, option 3 and option 4 are quite similar. At worst, both options occupy two extra bytes. However, in reality, not all LCGs will be configured with new tables, and probably not all LCGs will have data in their buffer at the same time. Thus, option 4 will typically present a 1-byte overhead in normal cases. Another advantage is that, with option 4, NW could configure up to 3 tables for each LCG.

[0091] Considering the advantages and indirect costs, option 4 and option 2 may be the preferable alternatives in certain modalities.

[0092] In a particular embodiment, the BS format can indicate up to three additional 8-bit BS tables (in addition to the legacy table).

[0093] In a particular mode, option 4 can be selected for the table / BS format.

[0094] In a particular embodiment, the eLCID (1 octet) is used for this new long MAC CE BSR. Operation and firing of the BSR

[0095] When the BSR is triggered and the UE calculates the total size of the LCG buffer, there may be cases where more than one table contains an index that represents the size of the UE buffer. In this case, the UE should always select the index that 1) returns the smallest difference between the value Petition 870260001315, dated 07 / 01 / 2026, page 30 / 114 / 82 minimum and maximum value of the represented index and 2) represents the size of the EU buffer.

[0096] When the buffer size value is outside the range covered by the different tables. For example, when only one table contains an index that can represent the UE buffer size, which will usually be the legacy table, the UE uses the corresponding BS tables and formats, in a particular mode.

[0097] In a particular embodiment, when multiple tables contain an index that can represent the UE buffer size, the UE uses the BS table / index that minimizes the index error (smallest difference between the minimum and maximum value represented by the index) and represents the UE buffer size.

[0098] In a particular embodiment, when only one table (including legacy BS tables) contains an index that represents the UE buffer size, the UE must use the corresponding BS table and format.

[0099] Another aspect is the interoperability between legacy BSR systems and new BSR reporting systems. However, interoperability between these two BSRs can be straightforward. If the UE is configured with additional tables, it will always use the table that provides the most accurate buffer state information and use the associated BSR format.

[00100] Legacy BSR triggering mechanisms are considered adequate to meet QoS requirements. However, it may be investigated whether other triggering factors offer additional benefits. On the other hand, XR traffic with high data periodicity may still benefit from frequent BSR transmissions, but this can be accommodated by frequently configuring periodic BSR. These aspects need to be considered if new triggers are suggested.

[00101] In a particular mode, the triggering conditions of Petition 870260001315, dated 07 / 01 / 2026, p. 31 / 114 / 82 Current BSRs are the reference conditions for the new BSR introduced above. Delay Report

[00102] During version 18, System Information (SI) simulations were performed, demonstrating that adding delay information to the BSR is beneficial for XR capacity, using this information in a delay scheduler. See R2-2301507, Discussion on XR-specific capacity improvements, Ericsson, 3GPP TSG-RAN WG2 #121, Feb.-Mar. 2023. Delay scheduling works by efficiently prioritizing users using advance delay information. This led to the conclusion that some delay information should be reported along with buffer data. See RP-223502, New WID on XR improvements for NR, 3GPP TSG RAN Meeting #98-e, December 12-16, 2022. A suitable location for this is in the BSR, as it already contains buffer size information.However, none of the existing BSR formats can be used for this, as space is needed for the delay information, and therefore a new MAC CE must be introduced.

[00103] In a particular embodiment, the delay report must also provide buffer information using newly defined BS tables.

[00104] Some argue that a single delay value is sufficient for reporting. However, examples can demonstrate that generating reports without any detail on the timescale will not work well in all scenarios, such as when there are multiple sets of PDUs simultaneously in the buffer with different remaining times until the deadline. It is therefore important that delay communication be introduced at a more granular level than just communicating a single value. It is important to note that XR traffic requires high latency and therefore data should not remain in the buffer for too long, otherwise it will be considered useless and discarded. Thus, Petition 870260001315, dated 07 / 01 / 2026, page 32 / 114 / 82, it can be assumed that there will be no need to report a large number of delay values; however, the exact number may be decided later, depending on the agreement for the introduction of a new MAC CE. Furthermore, as there may be several traffic flows with different delay requirements originating from a UE, delay reporting should be done by LCG, where preferably only LCIDs with similar delay requirements are grouped. This delay granularity increases the overhead of the reporting process, therefore it is preferable to find a solution that limits this overhead. It is important to note that reporting the exact delay value would create a significant overhead and is therefore impractical.

[00105] In a particular mode, the delay report is made by indicating bucket indices similar to the buffer state, by LCG. Delay report configuration

[00106] Since delay / latency reporting can be done similarly to the buffer size reporting procedure, by indicating an index containing a delay range, these delay / latency tables can be configured by the network and indicated via RRC. In this way, the granularity can be flexible around the most relevant parts. For example, lower indices indicate a smaller delay range.

[00107] In a particular mode, the network configures the minimum and maximum delay, as well as the increments. For example, a minimum value of 0 and a maximum value of 40 ms with 4 steps would return 4 indices indicating a range in one of them from 0 to <10 ms, another from 10 to <20 ms, and so on. The UE would report the buffer size in each of these latency / delay buckets. The latency / delay buckets can indicate the waiting time in the queue, for example.

[00108] In a particular modality, two delay tables per Petition 870260001315, dated 07 / 01 / 2026, page 33 / 114 / 82 LCGs are configured: one for short delay reports and another for long delay reports.

[00109] In a particular modality, a delay table is defined by: - ​​minimum value, - maximum value and - stepSize.

[00110] In one particular mode, up to eight buckets are configured for long-latency reports. In another mode, a single bucket is sufficient for short-delay reports.

[00111] In a particular mode, for long delay reports, if stepSize is not provided, UE calculates the step size as (maximum value - minimum value) / (number of buckets, for example, eight).

[00112] In a particular embodiment, the delay table is constructed as follows: For index 0, the BS value is defined by: [ > minimum value and < minimum value x (stepSize x (BS index + 1)) For the second and third indices, the BS value is defined by [< minimum value x (stepSize x (BS index + 1))] The last bucket index is defined by > minimum value x (stepSize x (BS index + 1)] or > maximum value (if provided).

[00113] In a particular mode, for reports with short delay, minimum and maximum values, or minimum size and increment, are provided.

[00114] For example, an example of ASN.1 for setting up the delays table is provided below:

[00115] MAC-CellGroupConfig ::= SEQUENCE {

[00116] drx-Config SetupRelease { DRX-Config} OPTIONAL, — Need M

[00117] schedulingRequestConfig Petition 870260001315, dated 07 / 01 / 2026, page 34 / 114 / 82 SchedulingRequestConfig OPTIONAL, — Need M

[00118] BSR-Config bsr-Config OPTIONAL, — Need M

[00119]

[00120]

[00121] [[

[00122] DelayTablesList-r18 SEQUENCE(Size (1..maxLCG (8))) of DelayTableList OPTIONAL,

[00123] ]]

[00124] DelayTableList ::= SEQUENCE {

[00125] logicalChannelGroupIndex ENUMERATED (0..maxLCG-ID),

[00126] shortDelayTableConfig DelayTableConfig OPTIONAL,

[00127] longDelayTableConfigList DelayTableConfig OPTIONAL

[00128] }

[00129] DelayTableConfig ::= SEQUENCE {

[00130] minValue INTEGER (xx..yy),

[00131] maxValue INTEGER (nn..mm) OPTIONAL Petição 870260001315, de 07 / 01 / 2026, pág. 35 / 114 / 82

[00132] stepSize INTEGER (bb..cc) OPTIONAL

[00133] } Operação de Relatório de Atraso e disparadores

[00134] Simulations show that advance information about delays is important for the scheduler to make an intelligent selection of users. Thus, information about delays should be communicated as early as possible, preferably already included in the first BSR sent when new data is reported. Therefore, if data has been waiting in the buffer for a while and is approaching the deadline, new BSR reports should include the updated delay values, as this provides the network with more accurate information updates. The frequency of BSR report generation can be controlled through periodic BSR configuration or by triggering the BSR when buffered data enters different delay buckets where there is no data yet.

[00135] In a particular embodiment, the delay report is triggered when new data enters an empty delay bucket. The buckets that trigger the delay report are configured by the network.

[00136] There are mainly two options for the delay information that have been discussed, consisting of the remaining delay until the PDB / PSDB expires or the wait time (i.e., time spent in the buffer). The remaining delay is the most useful metric for the scheduler, but not necessarily the metric that needs to be reported. Both wait time and remaining delay can function as a reporting solution, either by the UE calculating the remaining delay if it knows the target delay, or the remaining delay can be calculated on the network if it knows the wait time. As wait time is a metric generally Petition 870260001315, dated 07 / 01 / 2026, page 36 / 114 / 82 applicable and useful also for other services that do not fall within the critical requirements of the PSDB, there are more benefits in selecting this reporting metric.

[00137] In a particular embodiment, the delay report represents the waiting time of the PDU set since the first packet of the PDU set arrived at the UE buffer.

[00138] In a particular mode, the UE reports the buffer state in each of the delay / latency buckets. Delay report format New Short Delay Report

[00139] For short-delay reports, it is important to keep the overhead limited. Thus, the simplest solution would be to apply a solution similar to the legacy short-delay truncated BSR. This would result in the short-delay report indicating the highest priority LCG that holds data in a specific bucket (configured by the network). This is why the bucket sizes for short-delay and long-delay reports would be different.

[00140] In a particular mode, a short-delay reporting feature is introduced. Its format is the same as the old BSR.

[00141] In a particular mode, a short delay report indicates the highest priority LCG configured with delay reporting, which has data in a bucket configured by the network. New Long Delayed Report

[00142] Ideally, the delay report should be as similar as possible to the BSR report, adding, in addition, a delay indication, for example, an index. Some suggestions have been made to report only one bucket, the one with the highest priority. This solution would require at least one bit to indicate whether the BS report for the bucket is included or not. Adding a bit, in any case, will lead to the addition of an extra byte in the format, if the BS format is used as a base. Thus, if a bit is added... Petition 870260001315, dated 07 / 01 / 2026, page 37 / 114 / 82 extra bytes, it is best to report all buckets that contain data.

[00143] There are several possible formats for transmitting bucket and buffer status. Some formats that meet the reporting requirements are described here and include multiple buckets, a table indication, and the buffer size for each bucket.

[00144] According to a specific modality, for example, for each LCG that has been configured with delay reporting, when the LCG has data, the report includes two fields indicating the presence of the buffer state for a bucket and the table used for that buffer state. Figure 10, described above, exemplifies what the format would be when an LCG is configured with the delay reporting format; there are eight buckets and three new (+legacy) tables can be indicated for each of the buckets. If all buckets contained data, eight 1-byte BS fields would then be displayed.

[00145] In most cases, only some LCGs will be configured with delay reporting, meaning that in most cases the overhead will be limited to two bytes per LCG configured with delay reporting. Figure 11 illustrates an example of a Table / BS 500 format in which all buckets contain data, according to certain modes. The example Table / BS 500 format is referred to as option 5 in this document. Note, however, that when a bucket does not contain data, the corresponding L / N field will not be present. The BS fields would come after the L / N bits.

[00146] In another specific mode, an alternative option is similar to that described above, except that two new tables may be indicated. Figure 12 illustrates an example of a Table / BS 600 format demonstrating this option. The example Table / BS 600 format is referred to as option 6 in this document. Specifically, in the illustrated configuration, an LCG was configured with delayed reporting with eight buckets. Petition 870260001315, dated 07 / 01 / 2026, page 38 / 114 / 82 For each bucket, one bit indicates whether the legacy table or the new tables are being used (L / N bit), and the BS field would consist of 7 bits adjacent to another bit that would point to one of the two possible tables. In this case, two buckets use the new tables, while another bucket uses the old table.

[00147] In this case, 2 bytes would be needed. On the other hand, the number of new tables is limited to two and the BS length is seven bits, which is not necessarily a problem.

[00148] The format options for reporting delays are summarized in Table 3 below: Table 3 Option 1 Option 2 Buckets Nr or delay 8 8 Number of BS tables 3 new 2 (or 4) BS field length 8 bits 7 bits (or 6 bits) Height 2-3 bytes 2 bytes

[00149] In a particular embodiment, a bit is used to indicate the presence of data in a bucket.

[00150] In a particular embodiment related to option one, one byte is inserted to indicate eight buckets, and the BS is reported using Option 4.

[00151] In a particular embodiment, the eLCID (1 octet) is used for this new long-delay reporting MAC CE.

[00152] Based on the discussion above, the following options are proposed:

[00153] Proposal 1 Introduce BS tables based on RRC, i.e., the network provides a configuration for the user to create additional BS tables.

[00154] Proposal 2 NW can configure 1 table for the newly defined short BSR.

[00155] Proposal 3 It is preferable that NW be able to configure more than one table per LCG for the newly defined long BSR. The value to be selected depends on the BSR format (see Section 2.3). Petition 870260001315, dated 07 / 01 / 2026, page 39 / 114 / 82

[00156] Proposal 4 BS tables are defined by means of: an index, minimum value, maximum value and stepSize.

[00157] Proposal 5 If stepSize is not provided, the UE calculates the step size as (maximum value - minimum value) / (number of indices in the BS table).

[00158] Proposal 6 Tables are constructed as exemplified in Figure 2: For BS index 0, the BS value is defined by: [ > minimum value and < minimum value x (stepSize x (BS index + 1)) For the next BS indices, the BS value is defined by [< minimum value x (stepSize x (BS index + 1)] until the maximum value is reached.

[00159] Proposal 7 The NW can associate an LCG with up to “aa” (aa depends on Proposal 2) tables for a new long BSR.

[00160] Proposal 8 Adopt ASN.1 described above for the RRC-based BS table configuration.

[00161] Proposal 9 Only linear distribution is allowed for creating the BS table.

[00162] Proposal 10 A new 5-bit BS table can be configured by LCG (as in Proposal 2).

[00163] Proposal 11 The new BSR has the same format as the previous legacy BSR.

[00164] Proposal 12 The LCID index in the MAC subheader to identify this new short BSR should be obtained from the eLCID field.

[00165] Proposal 13 RAN2 to discuss whether more tables can be configured.

[00166] Proposal 14 BS format can indicate up to 3 additional 8-bit BS tables (in addition to the legacy table).

[00167] Proposal 15 Select option 4 for the table / BS format.

[00168] Proposal 16 The eLCID (1 octet) is used for this new CE of MAC long BSR. Petition 870260001315, dated 07 / 01 / 2026, page 40 / 114 / 82

[00169] Proposal 17 When multiple tables contain an index that can represent the UE buffer size, the UE should use the BS table / index that minimizes the index error (smallest difference between the minimum and maximum value represented by the index) and that represents the UE buffer size.

[00170] Proposal 18 When only one table (including legacy BS tables) contains an index that represents the UE buffer size, the UE should use the corresponding BS table and format.

[00171] Proposal 19 The current BSR triggering conditions are the reference conditions for the new BSR introduced in Section 2.1.

[00172] Proposal 20 Delay Report also provides buffer information using newly defined BS tables.

[00173] Proposal 21 Delay report is made indicating the bucket indices in a manner similar to the buffer state, by LCG.

[00174] Proposal 22 It is possible to configure two delay tables per LCG: one for short delay reports and another for long delay reports.

[00175] Proposal 23 A delay table is defined by: - ​​minimum value, - maximum value and - stepSize.

[00176] Proposal 24 It is possible to configure up to 8 buckets for long-delay reports. 1 bucket is sufficient for short-delay reports (see 2.2.3)

[00177] Proposal 25 For long delay reports, if stepSize is not provided, the UE calculates the step size as (maximum value - minimum value) / (number of buckets, e.g., 8).

[00178] Proposal 26 delay table is constructed as follows: For index 0, the BS value is defined by: [ > minimum value and < minimum value x (stepSize x (BS index + 1)) Second and third indices, the BS value is defined by [< minimum value x (stepSize x (BS index + 1)] The last Petition 870260001315, dated 07 / 01 / 2026, page 41 / 114 / 82 bucket index is defined by > minimum value x stepSize x (BS index + 1)] or > maximum value (if provided)

[00179] Proposal 27 For reports with short delays, it is necessary to provide the minimum and maximum values, or the minimum size and increment.

[00180] Proposal 28 Adopt ASN.1 described above to configure the delays table.

[00181] Proposal 29 The delay report is triggered when new data enters an empty delay bucket. The buckets that trigger the delay report are configured by the network.

[00182] Proposal 30 Communication delay report represents the waiting time for the set of PDUs since the first packet of the set of PDUs has arrived at the UE buffer.

[00183] Proposal 31 The UE reports the buffer state in each of the delay / latency buckets.

[00184] Proposal 32 A notification mechanism with minimum delay is introduced. Its format is the same as the legacy BSR.

[00185] Proposal 33 A short delay report indicates the highest priority LCG configured with delay reporting that has data in a network-configured bucket.

[00186] Proposal 34 A bit is used to indicate the presence of data in a bucket.

[00187] Proposal 35 Adopt option 1: a. 1 byte is entered to indicate 8 buckets.

[00188] b. The BS is reported using Option 4, as per Proposal 15.

[00189] Proposal 36 The eLCID (1 octet) is used for this new long-delay MAC report CE.

[00190] Another alternative is to have a longer bit in the L / N field to indicate both the BS table ID and the use of the legacy table.

[00191] Figure 13 illustrates an example of a Table / BS 400 format. Petition 870260001315, dated 07 / 01 / 2026, page 42 / 114 / 82, which has a longer L / N bit field to indicate the index of the legacy table and the new table together, according to certain modes. For example, as shown in Figure 13, the BSR may have two bits for each LCG that has been configured with new tables; one of the values ​​would indicate the legacy table (e.g., 00), while the other three values ​​would indicate one of the three tables that could be configured. The L / N field would only be present for LCGs that have been configured to use new tables. Therefore, the overhead of this solution would still be, in most cases, one byte. This option is therefore much better, as it allows configuring three new tables at the cost of only one byte, even when four LCGs are configured with new tables.For example, if two LGCs set the L / N indicator to the new index of the BS table, while one LCG set the “L / N” indicator to, for example, “00” to indicate that it is using the legacy table. In this example, there would be only three L / N fields, and not all those represented in Figure 13. In other words, there would be as many “L / N” fields as there are LGCs being reported, each L / N field associated with one LCG.

[00192] In another mode, after specifying the LCG and L / N fields, the bytes for the BS index can be added in a different way. If all L / N fields are set to 1, a new BS index will be added in the order of LCG with “1”, from left to right or from right to left. Similarly, when all L / N fields are set to 0, the legacy BS index is added in the order of LCG with “1” from left to right or from right to left. When the L / N fields with “1” and with “0” are mixed (but still have LCG with “1”), the BS index is added in a different way.

[00193] Add the new BS index from the leftmost position to the rightmost position of LCG=1, and then add the index of Petition 870260001315, dated 07 / 01 / 2026, page 43 / 114 / 82 BS legacy from the leftmost position to the rightmost position of LCG=1.

[00194] Or add the legacy BS index from left to right of LCG=1 and then add the legacy BS index from left to right of LCG=1.

[00195] Or add the BS index with LCG=1 from left to right.

[00196] In a particular mode, a network configures the way to add the base station index and also the direction (i.e., from left to right or from right to left in the LCG byte, in specific modes).

[00197] In addition to the formats above, UE can be configured to report time-related information, such as the remaining Packet Delay Limit (PDB) or the queue wait time. UE would then send a delay buffer status report to the network.

[00198] The format of this delay buffer status report could be, for example, as shown in Figure 14. Specifically, Figure 14 illustrates an example of a Table / BS 500 format for reporting time-related information when only the LCG has data, but three delay buckets are present, according to certain modalities. For example, as illustrated, a one-byte field P is associated with each configured LCG, which reports the delay buffer status information. Each P field indicates whether a BS field will be included and associated with the bucket represented by the P field. Each P field is associated with a range of time values, a bucket. For example, P1 could represent the time between 0 and <5 ms, P2 the time between 5 and <10 ms, P3 the time between 10 and <15 ms, and so on. These buckets would have been previously configured by the network.

[00199] Thus, for each LCG configured to report the status of Petition 870260001315, dated 07 / 01 / 2026, p. 44 / 114 / 82 delay buffer, there will be a 1-byte “P” field, the L / N field or the T field (as explained above in the different examples) and then the BS fields. There will be as many BS fields as there are P fields set to 1 for the given LCG.

[00200] Alternatively, it may be that the 1-byte P-field and 1-byte L / N-field pairs for each LCG are present, and after them, the BS fields associated with each LCG-P-L / N-field trio.

[00201] As an alternative to explicitly including P fields in the delay format, the information could be provided implicitly, always reporting the BS size for the delay buckets configured for the specific LCG. This could still include the L / N bits in the same way as explained previously (e.g., starting with one or more bytes indicating L / N in one or more bits). Another option is to configure the delay buckets with a specific table, i.e., delay bucket 1 always uses the new table X and delay bucket 2 uses the legacy table, and so on. In this way, it is possible to configure any number of delay buckets for each LCG (from one to infinity), as this would only change the number of rows reported for the BS sizes.

[00202] Alternatively, the delay format could include specific delay indices (D) instead of P fields. The delay index could consist of multiple bits and indicate an index to a delay bucket in a pre-configured delay table. These delay buckets could, similarly to P fields, indicate a delay range. In this way, the delay format would only indicate the delay buckets that contain data. The L / N bits are then reported only for the delay buckets that are included in the report. Depending on the number of delay buckets, the number of bits needed to indicate the delay index varies, and the number of rows needed also depends on how many delay buckets contain data. Figure 15 illustrates an example of a Table / BS 600 format, according to Petition 870260001315, dated 07 / 01 / 2026, page 45 / 114 / 82 certain modalities. Specifically, Figure 15 illustrates an example of a delay report format when two delay buckets contain data. For example, in the illustrated configuration, the report includes two delay indexes (D1 and D2) with L / N bits and associated BS tables. In this case, there are four delay buckets, and therefore two bits are needed for each delay index. In this example, since the L / N bits are also two bits, the delay index and the L / N bits fit into one octet.

[00203] In another mode, the L / N field and the P field can be added flexibly, depending on the number of LCGs with “1”. If the LCG field is set to 0, there will be no L / N field corresponding to the LCG, which can reduce overhead. The L / N field can be located after the LCG field or it can be added at the beginning of each BS index byte. This method can be applied to all the methods above.

[00204] In another mode, the number of LCG fields can also vary depending on how many LCGs are configured. If only 2 LCGs are configured by a network, the first byte of the LCG will be reduced to two bits.

[00205] If the L / N, P, or LCG fields are variable, but the BSR format needs to be byte-divisible, reserved bits can be added so that the BSR size is divisible by one byte.

[00206] Figure 16 shows an example of a 700 communication system according to some embodiments. In the example, the 700 communication system includes a 702 telecommunications network which includes an access network 704, such as a radio access network (RAN), and a 706 network core which includes one or more 708 network core nodes. The 704 access network includes one or more access network nodes, such as 710a and 710b network nodes (one or more of which may generally be referred to as 710 network nodes), or any other similar access node from the Project of Petition 870260001315, dated 07 / 01 / 2026, page 46 / 114 / 82 3GPP Partnership or non-3GPP access point. 710 network nodes facilitate direct or indirect connection of user equipment (UE), for example, connecting 712a, 712b, 712c and 712d UEs (one or more of which may be generically referred to as 712 UEs) to the 706 network core via one or more wireless connections.

[00207] Examples of wireless communication via a wireless connection include the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other material conductors. Furthermore, in different embodiments, the 700 communication system may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in data and / or signal communication, whether via wired or wireless connections. The 700 communication system may include and / or interact with any type of communication, telecommunications, data, cellular, radio network, and / or other similar system.

[00208] UEs 712 can be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with network nodes 710 and other communication devices. Similarly, network nodes 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly with UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702.

[00209] In the example shown, the core of network 706 connects network nodes 710 to one or more hosts, such as host 716. These connections can be direct or indirect, through one or more intermediate networks or devices. In other examples, the network nodes may be directly connected. Petition 870260001315, dated 07 / 01 / 2026, p. 47 / 114 / 82 coupled to the hosts. The 706 network core includes one more network core node (e.g., the 708 network core node) which is structured with hardware and software components. The characteristics of these components may be substantially similar to those described in relation to UEs, network nodes and / or hosts, so their descriptions are generally applicable to the corresponding components of the 708 network core node.Examples of network core nodes include functions of one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Residential Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Signature Identifier Unmasking Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[00210] The 716 host may be owned or controlled by a service provider that is not an operator or provider of the 704 access network and / or the 702 telecommunications network, and may be operated by or on behalf of the service provider. The 716 host may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various environmental conditions detected by a plurality of UEs, analytics functionalities, social media, functions to control or interact with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[00211] In general, the 700 communication system in Figure 16 allows connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to Petition 870260001315, dated 07 / 01 / 2026, page 48 / 114 / 82 predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal System for Mobile Telecommunications (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the 802.11 standards of the Institute of Electrical and Electronics Engineers (IEEE) (WiFi); and / or any other appropriate wireless communication standard, such as Worldwide Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi and / or any low-power wide area network (LPWAN) standards, such as LoRa and Sigfox.

[00212] In some examples, the 702 telecommunications network is a cellular network that implements features standardized by 3GPP. Thus, the 702 telecommunications network can support network slicing to provide different logical networks to different devices connected to the 702 telecommunications network. For example, the 702 telecommunications network can provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs and / or Massive Machine-Type Communication (mMTC) / Massive IoT services to other UEs.

[00213] In some examples, UEs 712 are configured to transmit and / or receive information without direct human interaction. For example, a UE may be designed to transmit information to the access network 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. Additionally, a UE may be configured to operate in single-RAT, multi-RAT, or multi-standard mode. For example, a UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., be configured for multi-radio dual connectivity (MR-DC), such as E Petition 870260001315, dated 07 / 01 / 2026, page 49 / 114 / 82 UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Dual Radio Connectivity (EN-DC).

[00214] In the example, hub 714 communicates with access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712c and / or 712d) and network nodes (e.g., network node 710b). In some examples, hub 714 may be a controller, router, content and analytics source, or any of the other communication devices described in this document in relation to the UEs. For example, hub 714 may be a broadband router that allows access to the core network 706 for UEs. As another example, hub 714 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions can be received from UEs, 710 network nodes, or by executable code, script, process, or other instructions on the 714 hub. As another example, the 714 hub can be a data collector that acts as temporary storage for UE data and, in some embodiments, can perform data analysis or other processing.As another example, the 714 hub can be a content source. For instance, for a UE that is a VR headset, display, speaker, or other media delivery device, the 714 hub can retrieve VR resources, video, audio, or other media or sensor-related data via a network node, which the 714 hub then provides to the UE directly after performing local processing and / or after adding additional local content. In another example, the 714 hub acts as a proxy server or orchestrator for UEs, especially if one or more of the UEs are low-power IoT devices.

[00215] Hub 714 may have a constant / persistent or intermittent connection to network node 710b. Hub 714 may also allow a different communication scheme and / or schedule between hub 714 and UEs (e.g., UE 712c and / or 712d), and between hub 714 and the network core. Petition 870260001315, dated 07 / 01 / 2026, page 50 / 114 / 82 706. In other examples, the 714 hub is connected to the 706 network core and / or to one or more UEs via a wired connection. Additionally, the 714 hub can be configured to connect to an M2M service provider via the 704 access network and / or to another UE via a direct connection. In some scenarios, UEs can establish a wireless connection with the 710 network nodes while still connected through the 714 hub via a wired or wireless connection. In some embodiments, the 714 hub may be a dedicated hub – that is, a hub whose primary function is to route communications to / from UEs to / from the 710b network node. In other configurations, the 714 hub may be a non-dedicated hub – that is, a device capable of routing communications between UEs and the 710b network node, but which is also capable of operating as a start and / or end point for communication on specific data channels.

[00216] Figure 17 shows a UE 800, which may be an embodiment of the UE 112 of Figure 16, according to some embodiments. As used in this document, a UE refers to a device capable, configured, organized and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, game console or device, music storage device, playback device, wearable terminal device, wireless endpoint, mobile station, tablet, notebook, notebook embedded equipment (LEE), notebook mounted equipment (LME), smart device, wireless client equipment (CPE), vehicle-mounted or vehicle-embedded / integrated wireless device, etc.Other examples include any UE identified by the 3GPP (3rd Generation Partnership Project), including a narrowband Internet of Things (NB-IoT) UE, a machine-type communication (MTC) UE. Petition 870260001315, dated 07 / 01 / 2026, p. 51 / 114 / 82 and / or an enhanced EU MTC (eMTC).

[00217] A UE can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for side-link communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the device in question. Instead, a UE may represent a device intended for sale or operation by a human user, but which may not be associated, or initially associated, with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale or operation by an end user, but which may be associated with a user or operated on their behalf (e.g., a smart energy meter).

[00218] The UE 800 includes a set of processing circuits 802 that are operationally coupled via a bus 804 to an input / output interface 806, a power supply 808, a memory 810, a communication interface 812 and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 17. The level of integration between the components may vary from one UE to another. In addition, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00219] The 802 processing circuitry is configured to process instructions and data and can be configured to implement any operant sequential state machine to execute instructions stored as machine-readable computer programs in memory 810. The 802 processing circuitry can be implemented as Petition 870260001315, dated 07 / 01 / 2026, page 52 / 114 / 82 one or more state machines implemented in hardware (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the 802 processing circuitry may include multiple central processing units (CPUs).

[00220] In the example, the 806 input / output interface can be configured to provide one or more interfaces for an input device, an output device, or one or more input and / or output devices. Examples of output devices include a loudspeaker, a sound card, a video card, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information on the UE 800. Examples of input devices include a touch or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a touchpad, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to detect user input.A sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device can use the same type of interface port as an input device. For example, a USB (Universal Serial Bus) port can be used to provide both an input and an output device. Petition 870260001315, dated 07 / 01 / 2026, page 53 / 114 / 82

[00221] In some embodiments, the 808 power supply is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), photovoltaic device, or battery, may be used. The 808 power supply may also include a power supply circuit to provide power from the 808 power supply itself and / or from an external power supply to the various parts of the UE 800 via an input circuit or an interface, such as a power cord. The power supply may be, for example, for charging the 808 power supply. The power supply circuit may perform any shaping, conversion, or other modification of the power from the 808 power supply to make the power suitable for the respective UE 800 components to which the power is supplied.

[00222] Memory 810 may be or be configured to include memory types such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, memory 810 includes one or more application programs 814, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and the corresponding data 816. Memory 810 may store, for use by UE 800, any one of a variety of operating systems or combinations of operating systems.

[00223] The 810 memory can be configured to include various physical drives, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, pen drive, key drive, high-density versatile digital disk (HDD). Petition 870260001315, dated 07 / 01 / 2026, page 54 / 114 / 82 DVD), internal hard disk drive, Blu-ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external dual-in-line mini-mold (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory, as a tamper-resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as USIM and / or ISIM, other memory or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC) or a removable UICC, commonly known as a SIM card. The 810 memory may allow the UE 800 to access instructions, application programs and the like, stored on transient or non-transient memory media, to download data or to load data.A manufactured item, such as one that utilizes a communication system, can be tangibly embedded as or in 810 memory, which can be or comprise a device-readable storage medium.

[00224] The processing circuitry 802 can be configured to communicate with an access network or another network using the communication interface 812. The communication interface 812 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 822. The communication interface 812 may include one or more transceivers used for communication, such as communication with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 818 and / or a receiver 820 suitable for providing network communications (e.g., optical, electrical, frequency allocations, and so forth). In addition, the transmitter 818 and the receiver 820 may be coupled to one or more antennas (e.g., antenna 822) and may share Petition 870260001315, dated 07 / 01 / 2026, page 55 / 114 / 82 circuit components, software or firmware, or alternatively be implemented separately.

[00225] In the illustrated configuration, the communication functions of the 812 communication interface may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, Near Field Communication (NFC), location-based communication such as the use of the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. Communications may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11. Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so on.

[00226] Regardless of the sensor type, a UE can provide an output of data captured by its sensors, through its 812 communication interface, via a wireless connection to a network node. The data captured by the sensors of a UE can be communicated wirelessly to a network node via another UE. The output can be periodic (e.g., once every 15 minutes if reporting the detected temperature), random (e.g., to balance the reporting load of multiple sensors), in response to a trigger event (e.g., when humidity is detected, an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient). Petition 870260001315, dated 07 / 01 / 2026, page 56 / 114 / 82

[00227] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless signal, the states of the actuator, motor, or switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[00228] A UE, when in the form of an Internet of Things (IoT) device, can be a device for use in one or more application domains, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of an IoT device are a device that is or is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device,an electric vehicle charging station, a smartwatch, an activity tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable device for tactile augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device, a sensor for monitoring plants or animals, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any type of medical device, such as a heart rate monitor or a robot. Petition 870260001315, dated 07 / 01 / 2026, page 57 / 114 / 82 remotely controlled surgical. A UE in the form of an IoT device comprises a set of circuits and / or software depending on the intended application of the IoT device, in addition to other components as described in relation to the UE 800 shown in Figure 17.

[00229] As another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements and transmits the results of that monitoring and / or measurements to another UE and / or a network node. In this case, the UE can be an M2M device, which, in the context of 3GPP, can be called an MTC device. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle, such as a car, bus, truck, ship, or airplane, or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[00230] In practice, any number of UEs can be used together for a single use case. For example, a first UE could be a drone or be integrated into one and provide information about the drone's speed (obtained via a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes to the remote controller, the first UE can adjust the drone's throttle (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the functionalities described above. For example, a UE could consist of the sensor and the actuator, and handle data communication for both the speed sensor and the actuators.

[00231] Figure 18 shows a network node 900, which may be a modality of the network node 110 in Figure 16, according to some modalities. As used in this document, the term network node refers to a capable, configured, organized and / or operable piece of equipment. Petition 870260001315, dated 07 / 01 / 2026, p. 58 / 114 / 82 to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio base station), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and Node Bs NR (gNBs)).

[00232] Base stations can be categorized based on the amount of coverage they provide (or, in other words, their transmission power level) and, therefore, depending on the amount of coverage provided, can be called femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed base radio station, such as centralized digital units and / or remote radio units (RRUs), sometimes called Remote Radio Units (RRHs). These remote radio units may or may not be integrated with an antenna, being considered radios with integrated antennas. Parts of a distributed base radio station can also be called nodes in a distributed antenna system (DAS).

[00233] Other examples of network nodes include 5G access nodes with multiple transmission points (multi-TRP), multi-standard radio equipment (MSR) such as MSR base stations, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base radio stations (BTSs), transmission points, transmission nodes, multicellular / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operational Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Mobile Service Location Centers (E-SMLCs)) and / or Minimization of Field Tests (MDTs).

[00234] Network node 900 includes a set of circuits Petition 870260001315, dated 07 / 01 / 2026, page 59 / 114 / 82 processing 902, a memory 904, a communication interface 906, and a power supply 908. The network node 900 may be composed of several physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where the network node 900 comprises several separate components (e.g., BTS and BSC components), one or more of these components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In this scenario, each NodeB and RNC pair, in some cases, may be considered a single separate network node. In some embodiments, the network node 900 may be configured to support multiple radio access technologies (RATs).In these configurations, some components can be duplicated (e.g., separate memory 904 for different RATs) and some components can be reused (e.g., the same antenna 910 can be shared by different RATs). The network node 900 can also include multiple sets of the various components illustrated for different wireless technologies integrated into the network node 900, for example, GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies can be integrated into the same chip or into a set of different chips and other components within the network node 900.

[00235] The 902 processing circuit assembly may comprise a combination of one or more of the following components: microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit assembly, field-programmable gate array, or any other suitable computing device, feature, or combination of hardware, software, and / or coded logic, operable to provide, alone or Petition 870260001315, dated 07 / 01 / 2026, page 60 / 114 / 82 together with other components of network node 900, such as memory 904, the functionality of network node 900.

[00236] In some embodiments, the processing circuit assembly 902 includes a system-on-a-chip (SoC). In some embodiments, the processing circuit assembly 902 includes one or more radio frequency (RF) transceiver circuit assemblies 912 and baseband processing circuit assemblies 914. In some embodiments, the radio frequency (RF) transceiver circuit assembly 912 and the baseband processing circuit assembly 914 may be on separate chips (or chip assemblies), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuit assembly 912 and the baseband processing circuit assembly 914 may be on the same chip or chip assemblies, boards, or units.

[00237] Memory 904 may comprise any form of computer-readable volatile or non-volatile memory, including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a pen drive, a compact disc (CD), or a digital video disc (DVD)), and / or any other non-transient, device-readable and / or computer-executable volatile or non-volatile memory devices that store information, data, and / or instructions that can be used by the processing circuitry 902.Memory type 904 can store any suitable instructions, data, or information, including a computer program, software, or application that includes one or more of the following logic, rules, code, tables, and / or other instructions capable of being executed by the set of... Petition 870260001315, dated 07 / 01 / 2026, p. 61 / 114 / 82 processing circuit 902 and used by network node 900. Memory 904 can be used to store any calculations performed by the processing circuit assembly 902 and / or any data received through the communication interface 906. In some embodiments, the processing circuit assembly 902 and memory 904 are integrated.

[00238] The communication interface 906 is used for wired or wireless signaling and / or data communication between a network node, access network, and / or UE. As illustrated, the communication interface 906 comprises port(s) / terminal(s) 916 for sending and receiving data, for example, to and from a network via a wired connection. The communication interface 906 also includes a radio front-end circuit assembly 918 that can be coupled to the antenna 910 or, in certain embodiments, form part of it. The radio front-end circuit assembly 918 comprises filters 920 and amplifiers 922. The radio front-end circuit assembly 918 can be connected to an antenna 910 and a processing circuit assembly 902. The radio input circuit assembly can be configured to condition the signals communicated between the antenna 910 and the processing circuit assembly 902.The radio input circuitry 918 can receive digital data that will be sent to other network nodes or UEs via a wireless connection. The radio front-end circuitry 918 can convert the digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of filters 920 and / or amplifiers 922. The radio signal can then be transmitted through antenna 910. Similarly, upon receiving data, antenna 910 can collect radio signals that are then converted into digital data by the radio front-end circuitry 918. The digital data can be passed to the processing circuitry 902. In other embodiments, the communication interface may comprise different components and / or different combinations of components. Petition 870260001315, dated 07 / 01 / 2026, page 62 / 114 / 82

[00239] In certain alternative embodiments, network node 900 does not include a separate radio front-end circuit assembly 918; instead, processing circuit assembly 902 includes a radio front-end circuit assembly and is connected to antenna 910. Similarly, in some embodiments, all or part of the RF transceiver circuit assembly 912 is part of communication interface 906. In other embodiments, communication interface 906 includes one or more ports or terminals 916, radio front-end circuit assembly 918, and RF transceiver circuit assembly 912 as part of a radio unit (not shown), and communication interface 906 communicates with baseband processing circuit assembly 914, which is part of a digital unit (not shown).

[00240] The 910 antenna may include one or more antennas, or sets of antennas, configured to send and / or receive wireless signals. The 910 antenna may be coupled to the 918 radio front-end circuit assembly and may be any type of antenna capable of transmitting and receiving wireless data and / or signals. In certain embodiments, the 910 antenna is separate from the 900 network node and may be connected to the 900 network node via an interface or port.

[00241] Antenna 910, communication interface 906 and / or processing circuit assembly 902 can be configured to perform any reception operations and / or certain acquisition operations described in this document as being performed by the network node. Any information, data and / or signal can be received from a UE, another network node and / or any other network equipment. Similarly, antenna 910, communication interface 906 and / or processing circuit assembly 902 can be configured to perform any transmission operations described in this document as being performed by the network node. Any information, data and / or signal can be transmitted to a UE, another network node and / or any other network equipment.

[00242] The 908 power supply provides power for the various Petition 870260001315, dated 07 / 01 / 2026, page 63 / 114 / 82 network node 900 components in a manner suitable for the respective components (e.g., at a voltage and current level required for each component). The 908 power supply may further comprise, or be coupled to, a power management circuitry to supply power to the network node 900 components to perform the functionality described in this document. For example, the network node 900 may be connected to an external power source (e.g., the mains power, an electrical outlet) via an input circuitry or interface, such as a power cord, wherein the external power source supplies power to the power supply circuitry of the 908 power supply. As another example, the 908 power supply may comprise a power source in the form of a battery or battery pack that is connected to or integrated into the power supply circuitry.The battery can provide backup power in case the external power source fails.

[00243] Network node 900 configurations may include additional components beyond those shown in Figure 18 to provide certain aspects of network node functionality, including any of the functionalities described in this document and / or any functionality necessary to support the subject matter described herein. For example, network node 900 may include user interface equipment to allow input of information into network node 900 and to allow output of information from network node 900. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 900.

[00244] Figure 19 is a block diagram of a 1000 host, which may be an embodiment of the 716 host of Figure 16, according to various aspects described in this document. As used in this document, the 1000 host may be or comprise various combinations of hardware and / or software, including a standalone server, a blade server, a server Petition 870260001315, dated 07 / 01 / 2026, page 64 / 114 / 82 implemented in the cloud, a distributed server, a virtual machine, a container, or processing resources in a server cluster. Host 1000 can provide one or more services to one or more UEs.

[00245] Host 1000 includes a set of processing circuits 1002 that are operationally coupled via a bus 1004 to an input / output interface 1006, a network interface 1008, a power supply 1010, and a memory 1012. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described in relation to the devices in the preceding figures, such as Figures 8 and 9, so that their descriptions are generally applicable to the corresponding components of host 1000.

[00246] Memory 1012 may include one or more computer programs, including one or more host application programs 1014 and data 1016, which may include user data, for example, data generated by a UE for host 1000 or data generated by host 1000 for a UE. Host 1000 configurations may utilize only a subset or all of the components shown. Host application programs 1014 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for various different classes, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, HUD systems).Host 1014 application programs can also provide user authentication and licensing checks, as well as periodically report the health status, routes, and content availability to a central node, such as a device within. Petition 870260001315, dated 07 / 01 / 2026, page 65 / 114 / 82 or at the edge of a network core. Thus, host 1000 can select and / or indicate a different host for over-the-top services for a UE. Host 1014 application programs can support various protocols such as HTTP Live Streaming Protocol (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Broadcast Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[00247] Figure 20 is a block diagram illustrating a virtualization environment 1100 in which the functions implemented by some modalities can be virtualized. In the present context, virtualizing means creating virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network resources. As used in this document, the term virtualization can be applied to any device described herein, or to components thereof, and refers to an implementation in which at least part of the functionality is implemented as one or more virtual components.Some or all of the functions described in this document can be implemented as virtual components running on one or more virtual machines (VMs) deployed in one or more virtual 1100 environments hosted by one or more hardware nodes, such as a hardware computing device operating as a network node, UE, network core node, or host. Furthermore, in modes where the virtual node does not require radio connectivity (e.g., a network core node or host), the node can be fully virtualized.

[00248] 1102 applications (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some of the features, functions, and / or benefits of some of the modalities described in this document.

[00249] Hardware 1104 includes a set of circuits for Petition 870260001315, dated 07 / 01 / 2026, page 66 / 114 / 82 processing, memory that stores software and / or executable instructions by a set of hardware processing circuits and / or other hardware devices as described in this document, such as a network interface, input / output interface, and so forth. The software may be executed by the processing circuit set to instantiate one or more 1106 virtualization layers (also called hypervisors or virtual machine monitors (VMMs)), provide 1108a and 1108b VMs (one or more of which may generally be referred to as 1108 VMs), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described in this document. The 1106 virtualization layer may present a virtual operating platform that appears as network hardware to the 1108 VMs.

[00250] VMs 1108 comprise virtual processing, virtual memory, virtual network or interface, and virtual storage, and may be run by a corresponding virtualization layer 1106. Different instance modes of a virtual device 1102 may be implemented in one or more VMs 1108, and the modes may be implemented in different ways. Hardware virtualization is, in some contexts, referred to as Network Functions Virtualization (NFV). NFV may be used to consolidate various types of network equipment onto high-volume industry-standard server hardware, physical switches, and physical storage, which may be located in data centers and on customer premises.

[00251] In the context of NFV, a VM 1108 can be a software implementation of a physical machine that executes programs as if they were running on a non-virtualized physical machine. Each of the VMs 1108, and the part of the hardware 1104 that runs that VM, whether hardware dedicated to that VM and / or hardware shared by that VM with other VMs, forms virtual network elements. Petition 870260001315, dated 07 / 01 / 2026, page 67 / 114 / 82 separated. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that are executed in one or more VMs 1108 on hardware 1104 and corresponds to application 1102.

[00252] 1104 hardware can be implemented on a standalone network node with generic or specific components. 1104 hardware can implement some functions through virtualization. Alternatively, 1104 hardware can be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed through 1110 management and orchestration, which, among other things, oversees the lifecycle management of 1102 applications. In some embodiments, 1104 hardware is coupled to one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas.Radio units can communicate directly with other hardware nodes via one or more appropriate network interfaces and can be used in combination with virtual components to provide a virtual node with radio resources, such as a radio access node or a base station. In some embodiments, some signals can be provided using an 1112 control system, which can alternatively be used for communication between hardware nodes and radio units.

[00253] Figure 21 shows a communication diagram of a host 1202 communicating through a network node 1204 with a UE 1206 via a partially wireless connection, according to some example modalities, according to various modalities, of the UE (such as a UE 712a of Figure 16 and / or UE 800 of Figure 17), network node (such as network node 710a of Figure 16 and / or network node 900 of Figure 18) and host (such as host 716 of Figure 16 and / or host 1000 of Figure 19) discussed Petition 870260001315, dated 07 / 01 / 2026, page 68 / 114 / 82, the preceding paragraphs will now be described with reference to Figure 21.

[00254] Like host 1000, host 1202 modalities include hardware, such as a communication interface, processing circuitry, and memory. Host 1202 also includes software, which is stored on or accessible from host 1202 and executable by the processing circuitry. The software includes a host application that can be operated to provide a service to a remote user, such as UE 1206 connecting via an over-the-top (OTT) connection 1250 that extends between UE 1206 and host 1202. In providing the service to the remote user, a host application can provide user data that is transmitted using the OTT connection 1250.

[00255] Network node 1204 includes hardware that enables communication with host 1202 and UE 1206. The 1260 connection can be direct or pass through a network core (such as network core 706 in Figure 16) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[00256] The UE 1206 includes hardware and software, which are stored on or accessible from the UE 1206 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific application, that can be operated to provide a service to a human or non-human user via the UE 1206 with support from host 1202. On host 1202, a running host application can communicate with the running client application via the OTT 1250 connection that terminates on the UE 1206 and host 1202. In providing the service to the user, the UE client application can receive request data from the host application and provide user data in response to the request data. The OTT 1250 connection can transfer both request data and user data. The UE client application can Petition 870260001315, dated 07 / 01 / 2026, page 69 / 114 / 82 interact with the user to generate the user data that he provides to the host application through the OTT 1250 connection.

[00257] The OTT 1250 connection can be extended via a 1260 connection between host 1202 and network node 1204 and via a 1270 wireless connection between network node 1204 and UE 1206 to provide the connection between host 1202 and UE 1206. The 1260 connection and the 1270 wireless connection, over which the OTT 1250 connection can be provided, have been abstractly designed to illustrate communication between host 1202 and UE 1206 via network node 1204, without explicit reference to any intermediate devices and the precise routing of messages through those devices.

[00258] As an example of data transmission via OTT connection 1250, in step 1208, host 1202 provides user data, which can be done by running a host application. In some modes, the user data is associated with a specific human user interacting with UE 1206. In other modes, the user data is associated with a UE 1206 that shares data with host 1202 without explicit human interaction. In step 1210, host 1202 initiates a transmission that carries the user data towards UE 1206. Host 1202 can initiate the transmission in response to a request transmitted by UE 1206. The request can be caused by human interaction with UE 1206 or by the operation of the client application running on UE 1206. The transmission can pass through network node 1204, according to the precepts of the modes described throughout this description.Thus, in step 1212, network node 1204 transmits to UE 1206 the user data that was transported in the transmission initiated by host 1202, according to the principles of the modes described throughout this description. In step 1214, UE 1206 receives the user data transported in the transmission, which can be performed by a client application running on UE 1206 associated with it. Petition 870260001315, dated 07 / 01 / 2026, page 70 / 114 / 82 application host executed by host 1202.

[00259] In some examples, UE 1206 runs a client application that provides user data to host 1202. The user data may be provided in reaction to or in response to data received from host 1202. Thus, in step 1216, UE 1206 may provide user data, which can be done by running the client application. When providing user data, the client application may also consider user input received through an input / output interface of UE 1206. Regardless of the specific way in which the user data was provided, UE 1206 initiates, in step 1218, the transmission of user data to host 1202 through network node 1204. In step 1220, according to the principles of the modes described throughout this description, network node 1204 receives user data from UE 1206 and initiates the transmission of the received user data towards host 1202.In step 1222, host 1202 receives the user data transported in the transmission initiated by UE 1206.

[00260] One or more of the various modalities improve the performance of OTT services provided to UE 1206 using the OTT 1250 connection, in which the wireless 1270 connection forms the last segment. More precisely, the precepts of these modalities can improve one or more of the following aspects: data rate, latency and / or power consumption and thus provide benefits such as, for example, reduced user waiting time, flexibility of file size restrictions, improved content resolution, better responsiveness and / or longer battery life.

[00261] In one example scenario, information about the factory's status can be collected and analyzed by host 1202. As another example, host 1202 can process audio and video data that may have been obtained from a UE for use in map creation. As yet another example, host 1202 can collect and analyze real-time data to assist in Petition 870260001315, dated 07 / 01 / 2026, page 71 / 114 / 82 vehicle congestion control (e.g., controlling traffic lights). As another example, the 1202 host can store surveillance videos uploaded by a UE. As another example, the 1202 host can store or control access to media content, such as video, audio, VR, or AR, which it can stream, multicast, or unicast to UEs. As other examples, the 1202 host can be used for energy pricing, remote control of non-critical electrical loads in terms of time to balance energy generation needs, location services, presentation services (such as compiling diagrams, etc., from data collected from remote devices), or any other data collection, retrieval, storage, analysis, and / or transmission function.

[00262] In some examples, a measurement procedure may be provided to monitor data rate, latency, and other factors in which one or more modes show improvements. An optional network functionality may also exist to reconfigure the OTT 1250 connection between host 1202 and UE 1206 in response to variations in measurement results. The measurement procedure and / or the network functionality to reconfigure the OTT connection may be implemented in software and hardware of host 1202 and / or UE 1206. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT 1250 connection passes; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities.Reconfiguring the OTT 1250 connection may include message format, retransmission settings, preferred routing, etc.; reconfiguration does not need to directly alter the operation of the 1204 network node. Such procedures and functionalities may be known and practiced in the technical field. In certain modes, measurements are required. Petition 870260001315, dated 07 / 01 / 2026, pp. 72 / 114 / 82 may involve proprietary UE signaling that facilitates measurements of transfer rate, propagation times, latency, and the like, by the 1202 host. The measurements may be implemented in such a way that the software causes messages to be transmitted, in particular empty or 'dummy' messages, using the 1250 OTT connection while monitoring propagation times, errors, etc.

[00263] Figure 22 illustrates an example of a method by a UE configured with a plurality of BS tables for use in the preparation and / or transmission of a BSR, according to certain modalities. In the illustrated configuration, the method includes a transmission step in QQ702. For example, in the QQ702 step, the UE can transmit, to a network node, information indicating at least one BS table and / or a BS table index used for the BSR.

[00264] Figure 23 illustrates an example of a method by a network node, according to certain embodiments. In the illustrated configuration, the method includes a receive step at 1402. For example, at step 1402, the network node may receive, from a UE configured with multiple BS tables for use in the preparation and / or transmission of a BSR, information indicating at least one BS table and / or BS table index used for the BSR.

[00265] Figure 24 illustrates a method 1500 executed by a UE 712 configured with a plurality of BS tables for use in preparing a BSR, according to certain changes. As illustrated, the method includes, in step 1502, the transmission to a network node 710 of information indicating at least one BS table and / or BS table index used to prepare the BSR.

[00266] In a particular embodiment, the UE is configured with several long BS tables and the information indicates one of several long BS tables used to prepare the BSR.

[00267] In a particular modality, the information indicates a Petition 870260001315, dated 07 / 01 / 2026, page 73 / 114 / 82 specific long BSR table and / or a long BS table index by logical channel group.

[00268] In a particular embodiment, information is transmitted in a plurality of bit fields, and each bit field stores a bit, a flag and / or a value that indicates, for a respective group of logical channels, a specific BSR table and / or a BS table index used for the BSR of the respective group of logical channels.

[00269] In a particular embodiment, each bit, flag and / or value indicates whether the BS table used to prepare the BSR is version 17 or earlier, or whether the BS table used to prepare the BSR is version 18 or later. Additionally or alternatively, each bit, flag and / or value indicates whether the index of the BS table used to prepare the BSR is version 17 or earlier, or whether the index of the BS table used to prepare the BSR is version 18 or later.

[00270] In a particular embodiment, the UE is configured with several BS tables and the information indicates one of several BS tables used to prepare a short BSR.

[00271] In a particular embodiment, the information is transmitted in a bit field, and the bit field stores a bit, a flag, and / or a value that indicates a specific short BSR table and / or a short BSR table index used for the BSR.

[00272] In a particular embodiment, the information is transmitted with the BSR.

[00273] Figure 25 illustrates a method 1600 executed by a network node 710, according to certain embodiments. As illustrated, the method includes, in step 1602, receiving 1602 from a UE 712, configured with a plurality of BS tables for use in preparing a BSR information indicating at least one BS table and / or BS table index used to prepare the BSR. Petition 870260001315, dated 07 / 01 / 2026, page 74 / 114 / 82

[00274] In a particular embodiment, the UE is configured to use several long BS tables when preparing the BSR, and the information indicates one of several long BS tables used to prepare the BSR.

[00275] In a particular embodiment, the information indicates a specific long BSR table and / or a long BS table index by logical channel group.

[00276] In a particular embodiment, the information is received in a plurality of bit fields, and each bit field stores a bit, a flag and / or a value that indicates, for a respective group of logical channels, a specific BSR table and / or a BS table index used for the BSR of the respective group of logical channels.

[00277] In a particular embodiment, each bit, flag and / or value indicates whether the BS table used to prepare the BSR is version 17 or earlier, or whether the BS table used to prepare the BSR is version 18 or later. Additionally or alternatively, each bit, flag and / or value indicates whether the index of the BS table used to prepare the BSR is version 17 or earlier, or whether the BS table used to prepare the BSR is version 18 or later.

[00278] In a particular embodiment, the UE is configured with several BS tables and the information indicates one of several BS tables used to prepare a short BSR.

[00279] In a particular embodiment, the information is received in a bit field, and the bit field stores a bit, a flag, and / or a value that indicates a specific short BSR table and / or a short BSR table index used for the BSR.

[00280] In a particular embodiment, the information is used to determine the size of an uplink grant.

[00281] In a particular mode, the information is transmitted with the BSR. Petition 870260001315, dated 07 / 01 / 2026, p. 75 / 114 / 82

[00282] Although the computing devices described in this document (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods described herein. The determination, calculation, acquisition, or similar operations described in this document may be performed by a set of processing circuits, which may process information, for example, by converting the obtained information into other information, comparing the obtained or converted information with the information stored in the network node, and / or performing one or more operations based on the obtained or converted information and, as a result of this processing, making a determination.Furthermore, although the components are represented as individual boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise several different physical components that make up a single illustrated component, and functionality may be divided among separate components. For example, a communication interface may be configured to include any of the components described in this document and / or the functionality of the components may be divided between the processing circuitry and the communication interface. In another example, functions that do not require much computing power from any of these components may be implemented in software or firmware, while functions that require a lot of computing power may be implemented in hardware.

[00283] In certain embodiments, some or all of the functionalities described in this document may be provided by a set of circuits of Petition 870260001315, dated 07 / 01 / 2026, page 76 / 114 / 82 processing that executes instructions stored in memory, which, in certain embodiments, may be a product of a computer program in the form of a non-transient, computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored in a separate or discrete storage medium readable by the device, such as, for example, through a physical connection. In any of these specific embodiments, regardless of whether it executes instructions stored in a non-transient, computer-readable storage medium or not, the processing circuitry may be configured to perform the described functionality.The benefits provided by this functionality are not limited to the processing circuitry or other components of the computing device, but are also enjoyed by the computing device as a whole and / or by end users and by a wireless network in general. Example Modalities Example Modalities of Group A

[00284] Example Mode A1. A method executed by a user device (UD) configured with multiple buffer state tables (BS) for use in preparing and / or transmitting a buffer state report (BSR), the method comprising: any steps, features or functions of the user device described above, either alone or in combination with other steps, features or functions described above.

[00285] Example A2. The method of the previous embodiment, additionally comprising one or more additional steps, features or functions of the user's equipment, as described above.

[00286] Example Mode A3. The method of any of the preceding modes, additionally comprising: providing user data; and forwarding the user data to a host computer via Petition 870260001315, dated 07 / 01 / 2026, page 77 / 114 / 82 of the transmission to the network node. Example Modalities of Group B

[00287] Example Mode B1. A method executed by a network node, the method comprises: any steps, resources, or functions of the network node described above, either alone or in combination with other steps, resources, or functions described above.

[00288] Example Mode B2. The method of the previous mode, additionally comprising one or more additional steps, features or functions of the network node described above.

[00289] Example Mode B3. The method of any of the preceding modes, additionally comprising: obtaining user data; and forwarding user data to a user host or equipment. Example Modalities of Group C

[00290] Example Embodiment C1. A method executed by a user device (UD) configured with a plurality of buffer state (BS) tables for use in preparing and / or transmitting a buffer state report (BSR), the method comprising: transmitting, to a network node, information indicating at least one BS table and / or BS table index used for the BSR.

[00291] Example Mode C2. The method of Example Mode C1, wherein at least one of the following options: the UE is configured with a plurality of short BS tables and the information indicates one of the short BS tables used for the BSR, and / or the UE is configured with a plurality of long BS tables and the information indicates one of the long BS tables used for the BSR.

[00292] Example Mode C3. The method of any of the example modes C1 to C2, where the information indicates a specific BSR table and / or a BS table index by logical channel group. Petition 870260001315, dated 07 / 01 / 2026, p. 78 / 114 / 82

[00293] Example Mode C4. The method of any of the example modes C1 to C3, wherein: the information is transmitted in a plurality of bit fields, and each bit field stores a bit, a flag and / or a value that indicates, for a respective plurality of logical channel groups, a specific BSR table and / or a BS table index used for the BSR of the respective logical channel group.

[00294] Example Mode C5. The method of any of the example modes C3 to C4, wherein at least one of the following: each bit, flag and / or value indicates whether a legacy BS table and / or a new BS table is being used, and / or each bit, flag and / or value indicates whether a legacy BS table index and / or a new BS table index is being used.

[00295] Example Mode C6. The method of Example Modes C1 to C5, additionally comprising: providing user data; and forwarding user data to a host via transmission to the network node.

[00296] Example Embodiment C7. A user device comprising a set of processing circuits configured to execute any of the methods of Example Embodiments C1 to C6.

[00297] Example Mode C8. A user device configured to execute any of the methods from Example Modes C1 to C6.

[00298] Example Embodiment C9. A wireless device comprising a set of processing circuits configured to execute any of the methods of Example Embodiments C1 to C6.

[00299] Example Mode C10. A computer program comprising instructions that, when executed on a computer, accomplish any of the methods in Example Modes C1 through C6.

[00300] Example Mode C11. A program product of Petition 870260001315, dated 07 / 01 / 2026, page 79 / 114 / 82 computer comprising a computer program, which comprises instructions that, when executed on a computer, perform any of the methods of Example Modes C1 to C6.

[00301] Example Mode C12. A non-transient, computer-readable storage medium that stores instructions which, when executed by a computer, perform any of the methods in Example Modes C1 through C6. Example Modalities of Group D

[00302] Example Mode D1. A method executed by a network node, the method comprising: receiving, from a User Equipment (UE) configured with a plurality of Buffer State (BS) tables for use in preparing and / or transmitting a Buffer State Report (BSR), information indicating at least one BS table and / or BS table index used for the BSR.

[00303] Example Mode D2. The method of Example Mode D1, comprising at least one of the following options: configuring the UE with a plurality of short BS tables and the information indicates one of the short BS tables used for the BSR, and / or configuring the UE with a plurality of long BS tables and the information indicates one of the long BS tables used for the BSR.

[00304] Example Mode D3. The method of any of the example modes D1 to D2, where the information indicates a specific BSR table and / or a BS table index by logical channel group.

[00305] Example Mode D4. The method of any of the example modes D1 to D3, wherein: the information is received in a plurality of bit fields, and each bit field stores a bit, a flag and / or a value that indicates, for a respective plurality of logical channel groups, a specific BSR table and / or a BS table index used for the BSR of the respective logical channel group. Petition 870260001315, dated 07 / 01 / 2026, p. 80 / 114 / 82

[00306] Example Mode D5. The method of any of the example modes C3 to C4, wherein at least one of the following: Each bit, flag and / or value indicates whether a legacy BS table and / or a new BS table is being used and / or each bit, flag and / or value indicates whether a legacy BS table index and / or a new BS table index is being used.

[00307] Example Embodiment D6. The method of any of the preceding example embodiments, additionally comprising: obtaining user data; and forwarding user data to a user host or equipment.

[00308] Example Mode D7. A network node comprising a set of processing circuits configured to execute any of the methods from Example Modes D1 to D6.

[00309] Example Mode D8. A network node configured to execute any of the methods from Example Modes D1 to D6.

[00310] Example Mode D9. A computer program comprising instructions that, when executed on a computer, accomplish any of the methods in Example Modes D1 through D6.

[00311] Example Mode D10. A computer program product comprising a computer program, which comprises instructions that, when executed on a computer, accomplish any of the methods of Example Modes D1 to D6.

[00312] Example Mode D29. A non-transient, computer-readable storage medium that stores instructions which, when executed by a computer, perform any of the methods in Example Modes D1 through D24. Example Modalities of Group E

[00313] Example Mode E1. A user equipment comprising: a set of processing circuits configured for Petition 870260001315, dated 07 / 01 / 2026, p. 81 / 114 / 82 execute any of the steps of any of the example modes of Groups A and C; and power supply circuit assembly configured to provide power to the processing circuit assembly.

[00314] Example Mode E2. A network node comprising: a set of processing circuits configured to execute any of the steps of any of the example modes of Groups B and D; a set of power supply circuits configured to provide power to the set of processing circuits.

[00315] Example Mode E3.A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; a set of radio front-end circuits connected to the antenna and to a set of processing circuits, and configured to condition the signals communicated between the antenna and the set of processing circuits; the set of processing circuits being configured to perform any of the steps of any of the example embodiments of Groups A and C; an input interface connected to the set of processing circuits and configured to allow information to be entered into the UE to be processed by the set of processing circuits; an output interface connected to the set of processing circuits and configured to output information from the UE that has been processed by the set of processing circuits; and a battery connected to the set of processing circuits and configured to provide power to the UE.

[00316] Example Mode E4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a set of processing circuits configured to provide user data; and a network interface configured to initiate transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises an interface of Petition 870260001315, dated 07 / 01 / 2026, page 82 / 114 / 82 communication and processing circuitry, with the communication interface and processing circuitry of the UE configured to execute any of the steps of any of the example modes of Groups A and C to receive user data from the host.

[00317] Example Mode E5. The host from the previous Example Mode, where the cellular network additionally includes a network node configured to communicate with the UE to transmit user data to the UE from the host.

[00318] Example Mode E6. The host of the 2 previous Example Modes, where: the host processing circuitry is configured to run a host application, thus providing user data; and the host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[00319] Example Mode E7. A method implemented by a host operating in a communication system that additionally includes a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission that carries the user data to the UE through a cellular network comprising the network node, wherein the UE performs any of the operations of any of the modes of Group A to receive the user data from the host.

[00320] Example Mode E8. The method of the previous Example Mode, additionally comprising: on the host, executing a host application associated with a client application running on the UE to receive user data from the UE.

[00321] Example Mode E9. The method of the previous Example Mode, additionally comprising: on the host, the transmission of input data to the client application running on the UE, the data being Petition 870260001315, dated 07 / 01 / 2026, page 83 / 114 / 82 of input provided by the running host application, in which user data is provided by the client application in response to input data from the host application.

[00322] Example Embodiment E10. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a set of processing circuits configured to provide user data; and a network interface configured to initiate transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and a set of processing circuits, the communication interface and the set of processing circuits of the UE being configured to perform any of the steps of any of the example embodiments of Groups A and C to transmit user data to the host.

[00323] Example Mode E11. The host from the previous Example Mode, where the cellular network additionally includes a network node configured to communicate with the UE to transmit user data from the UE to the host.

[00324] Example Mode E12. The host of the 2 previous Example Modes, where: the host processing circuitry is configured to run a host application, thus providing user data; and the host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[00325] Example Mode E13. A method implemented by a host configured to operate in a communication system that additionally includes a network node and a user device (UE), the method comprising: on the host, receiving user data transmitted to the host through the network node by the UE, wherein the UE performs any of the steps Petition 870260001315, dated 07 / 01 / 2026, page 84 / 114 / 82 of any of the example modalities of Groups A and C to transmit user data to the host.

[00326] Example Mode E14. The method of the previous Example Mode, additionally comprising: on the host, executing a host application associated with a client application running on the UE to receive user data from the UE.

[00327] Example Mode E15. The method of the previous Example Mode, additionally comprising: on the host, the transmission of input data to the client application running in the UE, the input data being provided by the host application running, wherein the user data is provided by the client application in response to the input data from the host application.

[00328] Example Embodiment E16. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a set of processing circuits configured to provide user data; and a network interface configured to initiate transmission of user data to a network node on a cellular network for transmission to a user equipment (UE), the network node having a communication interface and a set of processing circuits, the network node's set of processing circuits configured to perform any of the operations of any of the example embodiments of Groups B and D to transmit user data from the host to the UE.

[00329] Example Mode E17. The host of the previous Example Mode, wherein: The host processing circuitry is configured to run a host application that provides user data; and the UE comprises a processing circuitry configured to run a client application associated with the host application to receive user data transmission from the host. Petition 870260001315, dated 07 / 01 / 2026, page 85 / 114 / 82

[00330] Example Embodiment E18. A method implemented on a host configured to operate in a communication system that additionally includes a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission that carries the user data to the UE through a cellular network comprising the network node, wherein the network node performs any of the operations of any of the example embodiments of Groups B and D to transmit the user data from the host to the UE.

[00331] Example Mode E19. The method of the previous Example Mode, additionally comprising, at the network node, the transmission of user data provided by the host to the UE.

[00332] Example Mode E20. The method of either of the 2 previous example modes, wherein user data is provided on the host by the execution of a host application that interacts with a client application running on the UE, the client application being associated with the host application.

[00333] Example Embodiment E21. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: a set of processing circuits configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of user data toward a cellular network node for transmission to the UE, the network node having a communication interface and a set of processing circuits, the network node's set of processing circuits configured to perform any of the operations of any of the example embodiments of Groups B and D to transmit user data from the host to the UE.

[00334] Example Mode E22. The communication system of Petition 870260001315, dated 07 / 01 / 2026, page 86 / 114 / 82 The previous example modality, additionally comprising: the network node; and / or the user's equipment.

[00335] Example Embodiment E23. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a set of processing circuits configured to initiate the reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and a set of processing circuits, the network node's set of processing circuits configured to perform any of the operations of any of the Example Embodiments of Groups B and D to receive user data from a user equipment (UE) to the host.

[00336] Example Mode E24. The host of the 2 previous Example Modes, where: the host processing circuitry is configured to run a host application, thus providing user data; and the host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[00337] Example Mode E25. The host of either of the 2 previous example modes, where the initial receipt of user data comprises the request for user data.

[00338] Example Mode E26. A method implemented by a host configured to operate in a communication system that additionally includes a network node and a user device (UD), the method comprising: on the host, initiating the reception of user data from the UD, the user data originating from a transmission that the network node received from the UD, wherein the network node executes any of the steps of any of the Example Modes of Groups B and D to receive the Petition 870260001315, dated 07 / 01 / 2026, page 87 / 114 / 82 user data from the UE to the host.

[00339] Example Mode E27. The Mode method The previous example also includes, at the network node, the transmission of user data received from the host. Petition 870260001315, dated 07 / 01 / 2026, pages 88 / 114

Claims

1 / 5 CLAIMS 1. Method (1500) executed by a user equipment, UE (712), configured with a plurality of Buffer State tables, BS, for use in preparing a Buffer State Report, BSR, characterized in that the method comprises: transmitting (1502), to a network node (710), information indicating at least one BS table and / or BS table index used to prepare the BSR.

2. Method according to claim 1, characterized in that the UE is configured with a plurality of long BS tables and the information indicates one of the long BS tables used to prepare the BSR.

3. Method according to claim 2, characterized in that the information indicates a specific long BRS table and / or a long BS table index by logical channel group.

4. Method according to claim 2, characterized in that: the information is transmitted in at least one bit field, and each bit field stores a bit, flag and / or value indicating, for a respective plurality of logical channel groups, a specific BSR table and / or BS table index used for the BSR for the respective logical channel group.

5. Method according to claim 4, characterized in that at least one of: each bit, flag and / or value indicates whether the BS table used to prepare the BSR is version 17 or earlier or whether the BS table used to prepare the BSR is version 18 or later, and / or each bit, flag and / or value indicates whether the index of the BS table used to prepare the BSR is version 17 or earlier or whether the index of the BS table used to prepare the BSR is version 18 or later.

6. Method according to claim 1, characterized in that the UE is configured with a plurality of BS tables and the information indicates one of several BS tables used to prepare a short BSR.

7. Method according to claim 6, characterized in that: the information is transmitted in a bit field, and the bit field stores a bit, flag and / or value indicating a specific short BSR table and / or short BSR table index used for the BSR.

8. Method according to any one of claims 1 to 7, characterized in that the information is transmitted with the BSR.

9. Method (1600) executed by a network node (710), characterized in that the method comprises: receiving (1602), from a user equipment, UE (712), configured with a plurality of Buffer State tables, BS, for use in preparing a Buffer State Report, BSR, information indicating at least one BS table and / or BS table index used to prepare the BSR.

10. Method according to claim 9, characterized in that the UE is configured to use a plurality of long BS tables when preparing the BSR and the information indicates one of the long BS tables used to prepare the BSR.

11. Method according to claim 10, characterized in that the information indicates a specific long BRS table and / or a long BS table index by logical channel group.

12. Method according to any one of claims 10 to 11, characterized in that: Petition 870260005592, dated 21 / 01 / 2026, p. 8 / 19 3 / 5 the information is received in at least one bit field, and each bit field stores a bit, flag and / or value indicating, for a respective plurality of logical channel groups, a specific BSR table and / or BS table index used for the BSR for the respective logical channel group.

13. Method according to claim 12, characterized in that at least one of: each bit, flag and / or value indicates whether the BS table used to prepare the BSR is version 17 or earlier or whether the BS table used to prepare the BSR is version 18 or later, and / or each bit, flag and / or value indicates whether the index of the BS table used to prepare the BSR is version 17 or earlier or whether the BS table used to prepare the BSR is version 18 or later.

14. Method according to claim 9, characterized in that the UE is configured with a plurality of BS tables and the information indicates one of several BS tables used to prepare a short BSR.

15. Method according to claim 14, characterized in that: the information is received in a bit field, and the bit field stores a bit, flag and / or value indicating a specific short BSR table and / or short BSR table index used for the BSR.

16. A method according to any one of claims 9 to 14, characterized in that it comprises using the information to determine the size of an upward link grant.

17. Method according to any one of claims 9 to 16, characterized in that the information is transmitted with the BSR.

18. User equipment, UE (712), characterized by the fact Petition 870260005592, dated 21 / 01 / 2026, page 9 / 19 4 / 5 of being configured with a plurality of Buffer State tables, BS, for use in preparing a Buffer State Report, BSR, the UE configured to: transmit, to a network node (710), information indicating at least one BS table and / or BS table index used to prepare the BSR.

19. User equipment (UE) according to claim 18, characterized in that the UE is configured with a plurality of long BS tables and the information indicates one of the long BS tables used to prepare the BSR.

20. User equipment (UE) according to claim 19, characterized in that the information indicates a specific long BRS table and / or a long BS table index by logical channel group.

21. User equipment (UE) according to claim 19, characterized in that: the information is transmitted in at least one bit field, and each bit field stores a bit, flag and / or value indicating, for a respective plurality of logical channel groups, a specific BSR table and / or BS table index used for the BSR for the respective logical channel group.

22. Network node (712), characterized in that it is configured to: receive, from a user device, UE (710), configured with a plurality of Buffer State tables, BS, for use in preparing a Buffer State Report, BSR, information indicating at least one BS table and / or BS table index used to prepare the BSR.

23. Network node according to claim 22, Petition 870260005592, dated 21 / 01 / 2026, page 10 / 19 5 / 5 characterized in that the UE is configured to use a plurality of long BS tables when preparing the BSR and the information indicates one of the long BS tables used to prepare the BSR, wherein preferably the information indicates a specific long BSR table and / or a long BS table index per logical channel group.

24. Network node according to claim 22 or 23, characterized in that: information is received in at least one bit field, and each bit field stores a bit, flag and / or value indicating, for a respective plurality of logical channel groups, a specific BSR table and / or BS table index used for the BSR for the respective logical channel group.

25. Network node according to claim 24, characterized in that at least one of: each bit, flag and / or value indicates whether the BS table used to prepare the BSR is version 17 or earlier or whether the BS table used to prepare the BSR is version 18 or later, and / or each bit, flag and / or value indicates whether the index of the BS table used to prepare the BSR is version 17 or earlier or whether the BS table used to prepare the BSR is version 18 or later.

26. Product, process, system, means, kit or use, characterized by the fact that it comprises one or more elements as described in the descriptive report and / or illustrated in the figures. Petition 870260005592, dated 01 / 21 / 2026, page 11 / 19