Buffer status report for Extended Reality Services

Abstract

An apparatus, method, and system for buffer status reporting for extended reality services are disclosed. The apparatus (700) includes a transceiver (725) and a processor (705) coupled to the transceiver. The processor (705) is configured to receive an indication from a network indicating whether a fixed-size short-format BSR can be used, determine a buffer size based on a first table with buffer size levels corresponding to a first buffer size field in response to the indication indicating the fixed-size short-format BSR can be used, determine a buffer size based on a second table with buffer size levels corresponding to a second buffer size field in response to an indication indicating the fixed-size short-format BSR cannot be used, and transmit the BSR to the network.

Description

[[Technical Field]]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 246,796, filed September 22, 2021, entitled “BUFFER STATUS REPORTING FOR EXTENDED REALITY SERVICE” by Hossein Bagheri et al., which is incorporated herein by reference.

[0002] The subject matter disclosed herein relates generally to wireless communications, and more specifically to buffer status reporting for extended reality services. [[Background Art]]

[0003] In wireless networks, service-oriented design that accounts for extended reality ("XR") traffic characteristics (e.g., packets having a variable packet arrival rate where packets arrive at 30-120 frames per second with some jitter, and variable large packet sizes) may enable more efficient provision of XR services (e.g., in terms of meeting XR service requirements for a larger number of user equipments ("UEs"), or in terms of power saving for UEs). [[Summary of the Invention]] [[Means for Solving the Problems]]

[0004] A solution for buffer status reporting for extended reality services is disclosed. The solution can be implemented by an apparatus, a system, a method, or a computer program product.

[0005] In one embodiment, the first device includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the device to receive an indication from the network that a fixed-size short-format BSR can be used, to determine the buffer size in response to an indication that a fixed-size short-format BSR can be used, based on a first table having buffer size levels corresponding to a first buffer size field, and to determine the buffer size in response to an indication that a fixed-size short-format BSR cannot be used, based on a second table having buffer size levels corresponding to a second buffer size field, and to send the BSR to the network if the first buffer size field is shorter than the second buffer size field.

[0006] In one embodiment, the first method receives an indication from the network that a fixed-size short-format BSR can be used, determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field in response to an indication that a fixed-size short-format BSR can be used, determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field in response to an indication that a fixed-size short-format BSR cannot be used, and transmits the BSR to the network if the first buffer size field is shorter than the second buffer size field.

[0007] In one embodiment, the second device includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor causes the device to send an indication to the UE indicating a BSR format to be used for the BSR, the BSR format comprising one of a fixed-size long format and a short format, to receive a BSR according to the indicated BSR format, to determine a buffer size based on a first table having buffer size levels corresponding to a first buffer size field in response to an indication that a fixed-size short format BSR can be used, and to determine a buffer size based on a second table having buffer size levels corresponding to a second buffer size field in response to an indication that a fixed-size short format BSR cannot be used, wherein the first buffer size field is shorter than the second buffer size field.

[0008] In one embodiment, the second method transmits a marking to the UE indicating a BSR format to be used for the BSR, the BSR format comprising one of a fixed-size long format and a short format, and the second method receives a BSR according to the indicated BSR format, and in response to a marking indicating that a fixed-size short format BSR can be used, the second method determines a buffer size based on a first table having buffer size levels corresponding to a first buffer size field, and in response to a marking indicating that a fixed-size short format BSR cannot be used, the second method determines a buffer size based on a second table having buffer size levels corresponding to a second buffer size field, wherein the first buffer size field is shorter than the second buffer size field.

[0009] A more detailed description of the embodiments briefly outlined above is made with reference to specific embodiments shown in the accompanying drawings. Understanding that these drawings only illustrate a few embodiments and should therefore not be considered limitations of scope, the embodiments are described and explained with further specificity and detail by using the accompanying drawings. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic block diagram showing one embodiment of a wireless communication system for buffer status reporting for Extended Reality Services. [Figure 2] This figure shows the Short Format Buffer Status Report ("BSR") and the Short Truncated BSR Media Access Control-Control Element ("MAC CE"). [Figure 3] This figure shows long-format BSR, long-truncated BSR, and preemptive BSR MAC CE. [Figure 4] This figure shows the recommended bitrate MAC CE. [Figure 5] This figure shows one embodiment of the LogicalChannelConfig information element ("IE"). [Figure 6] This figure shows one embodiment of the NR protocol stack. [Figure 7] This is a block diagram showing one embodiment of a user device that can be used for buffer status reporting for Extended Reality Services. [Figure 8] This is a block diagram showing one embodiment of a network device that may be used for buffer status reporting for Extended Reality Services. [Figure 9] This flowchart illustrates one embodiment of a method for reporting buffer status for Extended Reality Services. [Figure 10]This flowchart illustrates one embodiment of a method for reporting buffer status for Extended Reality Services. [Modes for carrying out the invention]

[0011] As will be understood by those skilled in the art, embodiments of an embodiment can be embodied as a system, apparatus, method, or program product. Accordingly, an embodiment can take the form of an entire hardware embodiment, an entire software embodiment (including firmware, resident software, microcode, etc.), or an embodiment that combines software and hardware embodiments.

[0012] For example, the disclosed embodiments may be implemented as hardware circuits comprising custom very large-scale integrated circuits ("VLSI") or commercially available semiconductors such as gate arrays, logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, or programmable logic devices. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions.

[0013] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereafter referred to as code. The storage device may be a tangible device, a non-temporary device, and / or a non-transmitting device. The storage device does not have to embody signals. In some embodiments, the storage device utilizes signals solely to access the code.

[0014] Any combination of one or more computer-readable media may be used. A computer-readable media may be a computer-readable storage medium. A computer-readable storage medium may be a storage device that stores code. A storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination thereof.

[0015] More specific examples of storage devices (a non-exclusive list) include electronic connections having one or more wires, portable computer diskettes, hard disks, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EEPROM") or flash memory, portable compact disk read-only memory ("CD-ROM"), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that contains or stores programs for use by, or associated with, an instruction execution system, apparatus, or device.

[0016] The code for performing the actions for the embodiments may be of any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the “C” programming language, and / or machine languages ​​such as assembly language. The code may run entirely on the user’s computer, partially on the user’s computer, as a standalone software package, partially on the user’s computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (“LAN”), a wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be to an external computer (for example, via the Internet using an Internet Service Provider (“ISP”)).

[0017] Furthermore, the features, structures, or characteristics described in the embodiments may be combined in any suitable manner. The following description provides numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, in order to provide a complete understanding of the embodiments. However, those skilled in the art will recognize that embodiments may be practiced without one or more of these specific details, or in conjunction with other methods, components, materials, etc. In other instances, known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of a particular embodiment.

[0018] References to "one embodiment", "an embodiment", or similar expressions throughout this specification mean that the specific feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Accordingly, appearances of the phrases "in one embodiment", "in an embodiment", and similar expressions throughout this specification may, but do not necessarily, all refer to the same embodiment, and unless otherwise explicitly specified, may mean "one or more embodiments, but not all". Unless otherwise explicitly specified, the terms "comprise", "include", "have", and variations thereof mean "including, but not limited to". Unless otherwise explicitly specified, a listed recitation of items does not imply that any or all of such items are mutually exclusive. Unless otherwise explicitly specified, the terms "a", "an", and "the" also refer to "one or more".

[0019] As used herein, a list with the conjunction "and / or" includes any single item in the list or any combination of items in the list. For example, a recitation of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a recitation using the term "one or more of" includes any single item in the list or any combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a recitation using the term "one of" includes only any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include combinations of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and does not include combinations of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C.

[0020] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing apparatus to create a machine, such that when the instructions are executed via the processor of the computer or other programmable data processing apparatus, a means for implementing the function / act specified in the flowchart and / or block diagram is created.

[0021] Code that can instruct a computer, another programmable data processing apparatus, or other devices to function in a particular manner may also be stored in a storage device, such that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the function / act specified in the flowchart and / or block diagram.

[0022] Code that causes a series of operational steps to be performed on a computer, another programmable apparatus, or other devices to produce a computer-implemented process may also be loaded onto the computer, another programmable data processing apparatus, or other devices, such that the code executed on the computer or other programmable apparatus provides a process for implementing the function / act specified in the flowchart and / or block diagram.

[0023] The flowcharts and / or block diagrams in the drawings illustrate the architecture, function, and operation of possible implementations of devices, systems, methods, and program products in various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code containing one or more executable instructions of code for implementing a specified logical function.

[0024] It should also be noted that in some alternative implementations, the functions described within a block may exist in a different order than those described in the drawing. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or blocks may, in some cases, be executed in reverse order depending on the functions they relate to. Other steps and methods may be conceivable that are equivalent in function, logic, or effect to one or more blocks, or parts thereof, of the drawing shown.

[0025] Various types of arrows and lines may be used in flowcharts and / or block diagrams, but they are not intended to limit the scope of the corresponding embodiment. In fact, some arrows or other connecting elements may be used only to indicate the logical flow of the embodiment shown. For example, an arrow may indicate a waiting or monitoring period of unspecified length between enumerated steps of the embodiment shown. It should also be noted that each block in a block diagram and / or flowchart, as well as combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a specified function or action, or a combination of dedicated hardware and code.

[0026] The descriptions of elements in each drawing may refer to elements in preceding drawings. Similar numbers refer to similar elements in all drawings, including alternative embodiments of similar elements.

[0027] Generally, this disclosure describes systems, methods, and apparatus for buffer status reporting for extended reality services. In some embodiments, the methods may be performed using computer code incorporated into a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium that, when executed by a processor, causes the apparatus or system to perform at least a portion of the measures described below.

[0028] A service-oriented design that takes into account XR traffic characteristics (for example, variable packet arrival rates where packets arrive at 30-120 frames / second with some jitter, and packets with variable large packet sizes) can enable the delivery of more efficient XR services (for example, in terms of meeting XR service requirements for a larger number of UEs, or in terms of UE power saving). In one embodiment, this disclosure describes an improvement to the BSR for increasing system capacity. Specifically, the subject of this specification describes a buffer size indicator mechanism that is improved to support finer buffer size granularity so that XR services can avoid wasting resources.

[0029] Figure 1 shows a wireless communication system 100 supporting buffer status reporting for Extended Reality Services according to an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network ("RAN") 120, and a mobile core network 130. The RAN 120 and the mobile core network 130 form a mobile communication network. The RAN 120 may consist of a base unit 121 with which the remote unit 105 communicates using a wireless communication link 115. While a specific number of remote units 105, base unit 121, wireless communication link 115, RAN 120, and mobile core network 130 are shown in Figure 1, those skilled in the art will recognize that any number of remote units 105, base unit 121, wireless communication link 115, RAN 120, and mobile core network 130 may be included in the wireless communication system 100.

[0030] In one implementation, RAN120 conforms to a 5G system as defined in the Third Generation Partnership Project ("3GPP" registered trademark) specifications. For example, RAN120 may be a Next Generation Radio Access Network ("NG-RAN") and may implement an NR RAT and / or a 3GPP Long-Term Evolution ("LTE") RAT. In another example, RAN120 may include a non-3GPP RAT (e.g., Wi-Fi®, Institute of Electrical and Electronics Engineers ("IEEE") 802.11 family compliant WLAN). In yet another implementation, RAN120 conforms to an LTE system as defined in the 3GPP specifications. However, more generally, the wireless communication system 100 may implement any other open or proprietary communication network, among others, such as Worldwide Interoperability for Microwave Access ("WiMAX") or IEEE 802.16 family standards. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0031] In one embodiment, the remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., internet-connected televisions), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, and network devices (e.g., routers, switches, modems). In some embodiments, the remote unit 105 may include wearable devices such as smartwatches, fitness bands, and optical head-mounted displays. Furthermore, the remote unit 105 may be referred to as UE, subscriber unit, mobile, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transceiver unit ("WTRU"), device, or other terms used in the art. In various embodiments, the remote unit 105 includes subscriber identification information and / or an identification module ("SIM") and a mobile device ("ME") that provides mobile terminal functions (e.g., radio transmission, handover, speech coding and decoding, error detection and correction, signaling, and access to the SIM). In some embodiments, the remote unit 105 may also include a terminal device ("TE") and / or be incorporated into a consumer electronics appliance or device (e.g., a computing device as described above).

[0032] The remote unit 105 may communicate directly with one or more base units 121 in the RAN 120 via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried via a wireless communication link 123, where the RAN 120 is an intermediate network that provides the remote unit 105 with access to the mobile core network.

[0033] In some embodiments, the remote unit 105 communicates with the application server via a network connection to the mobile core network 130. For example, an application 107 of the remote unit 105 (e.g., a web browser, media client, telephone, and / or a Voice-over-Internet-Protocol ("VoIP") application) may trigger the remote unit 105 to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network 130 via the RAN 120. The mobile core network 130 then uses the PDU session to relay traffic between the remote unit 105 and the application server (e.g., a content server 151 in the packet data network 150). The PDU session represents a logical connection between the remote unit 105 and the user plane function ("UPF") 131.

[0034] To establish a PDU session (or PDN connection), the remote unit 105 must register with the mobile core network 130 (also referred to as "connecting to the mobile core network" in the context of fourth-generation ("4G") systems). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. Thus, the remote unit 105 may have at least one PDU session for communicating with, for example, the packet data network 150 representing the internet. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0035] In the context of a 5G system ("5GS"), the term "PDU session" refers to a data connection that provides an end-to-end ("E2E") user plane ("UP") connection between a remote unit 105 and a specific data network ("DN") via UPF 131. A PDU session supports one or more quality of service ("QoS") flows. In some embodiments, there may be a one-to-one correspondence between QoS flows and QoS profiles so that all packets belonging to a particular QoS flow have the same 5G QoS identifier ("5QI").

[0036] In the context of 4G / LTE systems such as Evolved Packet Systems ("EPS"), a Packet Data Network ("PDN") connection (also called an EPS session) provides an end-to-end (E2E UP) connection between the remote unit and the PDN. The PDN connection procedure establishes a tunnel between the EPS bearer, i.e., the remote unit 105 in the mobile core network 130, and a packet gateway ("PGW", not shown). In some embodiments, there is a one-to-one correspondence between the EPS bearer and the QoS profile so that all packets belonging to a particular EPS bearer have the same QoS class identifier ("QCI").

[0037] The base unit 121 may be distributed across a geographical area. In some embodiments, the base unit 121 may also be called an access terminal, access point, base, base station, Node-B ("NB"), Evolved Node B (abbreviated as eNodeB or "eNB," also known as Evolved Universal Terrestrial Radio Access Network ("E-UTRAN") Node B), 5G / NR Node B ("gNB"), Home Node-B, relay node, RAN node, or any other term used in the art. The base unit 121 is generally part of a RAN, such as RAN 120, which may include one or more controllers commutably coupled to one or more corresponding base units 121. These and other elements of a radio access network are not shown but are generally well known to those skilled in the art. The base unit 121 connects to the mobile core network 130 via RAN 120.

[0038] The base unit 121 may serve several remote units 105 within a serving area, such as a cell or cell sector, via a wireless communication link 123. The base unit 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base unit 121 transmits DL communication signals to serve the remote units 105 in the time domain, frequency domain, and / or spatial domain. Furthermore, DL communication signals may be carried via the wireless communication link 123. The wireless communication link 123 may be any suitable carrier in the licensed radio spectrum or the unlicensed radio spectrum. The wireless communication link 123 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 121. Note that in NR-U operation, the base unit 121 and the remote units 105 communicate over the unlicensed radio spectrum.

[0039] In one embodiment, the mobile core network 130 is a 5GC or Evolved Packet Core ("EPC"), which may be coupled to a packet data network 150, such as the Internet and a private data network, among other data networks. The remote unit 105 may have a contract or other account with the mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network ("PLMN"). This disclosure is not limited to any particular wireless communication system architecture or protocol implementation.

[0040] The mobile core network 130 includes several network functions ("NF"). As shown, the mobile core network 130 includes at least one UPF 131. The mobile core network 130 also includes several control plane ("CP") functions, including, but not limited to, access and mobility management functions ("AMF") 133, session management functions ("SMF") 135, network exposure functions ("NEF"), policy control functions ("PCF") 137, integrated data management functions ("UDM"), and user data repository ("UDR"), which serve the RAN 120.

[0041] UPF131 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for the interconnected data network ("DN") in the 5G architecture. AMF133 is responsible for NAS signaling termination, NAS encryption and integrity protection, registration management, connectivity management, mobility management, access authentication and authorization, and security context management. SMF135 is responsible for session management (i.e., session establishment, correction, and release), remote unit (i.e., UE) IP address allocation and management, DL data notification, and traffic steering configuration for UPF, for proper traffic routing.

[0042] The NEF is responsible for making it easy for customers and network partners to access network data and resources. Service providers can enable new capabilities and open them up through APIs. These APIs allow authorized third-party applications to monitor and configure network behavior for a number of different subscribers (i.e., connected devices with different applications). PCF137 is responsible for the unified policy framework, providing policy rules to CP functions, and accessing contractual information for policy decisions within the UDR.

[0043] The UDM is responsible for generating authentication and key exchange ("AKA") certificates, handling user identification, access authorization, and contract management. The UDR is a repository of subscriber information and may be used to service several network functions. For example, the UDR may store subscriber data, policy-related data, subscriber-related data that is permitted to be made available to third-party applications, etc. In some embodiments, the UDM occupies the same location as the UDR and is illustrated as a composite entity "UDM / UDR" 139.

[0044] In various embodiments, the mobile core network 130 may also include an authentication server function ("AUSF") (which acts as an authentication server), a network repository function ("NRF") (which performs NF service registration and discovery, enabling NFs to identify appropriate services from one another and communicate with each other via an application programming interface ("API")), or other NFs defined for 5GC. In some embodiments, the mobile core network 130 may also include an authentication, authorization, and billing ("AAA") server.

[0045] In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a specific network slice. Here, “network slice” refers to a portion of the mobile core network 130 optimized for a particular traffic type or communication service. Network instances may be identified by single network slice selection assistance information ("S-NSSAI"), but the set of network slices authorized for use by the remote unit 105 is identified by network slice selection assistance information ("NSSAI").

[0046] Here, “NSSAI” refers to a vector value containing one or more S-NSSAI values. In some embodiments, different network slices may include separate instances of network functions such as SMF135 and UPF131. In some embodiments, different network slices may share some common network functions such as AMF133. Different network slices are not shown in Figure 1 for simplicity of illustration, but their support is assumed. When different network slices are deployed, the mobile core network 130 may include a network slice selection function ("NSSF") which is responsible for selecting a network slice instance to serve the remote unit 105, determining the acceptable NSSAI, and determining the AMF to be configured to be used to serve the remote unit 105.

[0047] While certain numbers and types of network functions are shown in Figure 1, those skilled in the art will recognize that any number and types of network functions may be included in the mobile core network 130. Furthermore, in LTE variants where the mobile core network 130 has an EPC, the shown network functions may be replaced by appropriate EPC entities such as the mobile management entity ("MME"), serving gateway ("SGW"), PGW, and home subscriber server ("HSS"). For example, the AMF 133 may be mapped to the MME, the SMF 135 may be mapped to the control plane portion of the PGW and / or the MME, the UPF 131 may be mapped to the user plane portions of the SGW and PGW, and the UDM / UDR 139 may be mapped to the HSS, and so on.

[0048] Figure 1 shows the components of a 5G RAN and 5G core network, but the embodiments described apply to other types of communication networks and RATs, including variants of IEEE 802.11, Global System for Mobile Communications ("GSM", i.e., 2G digital cellular network), General Packet Radio Service ("GPRS"), UMTS, variants of LTE, CDMA2000, Bluetooth, ZigBee, Sigfox, and others.

[0049] In the following description, the term "gNB" is used for base stations, but it is replaceable by any other radio access node, such as RAN nodes, eNBs, base stations ("BS"), access points ("AP"), NR, etc. Furthermore, the operation is described primarily in the context of 5G NR. However, the proposed strategies / methods are equally applicable to other mobile communication systems that support buffer status reporting for Extended Reality Services.

[0050] As background, according to TS 38.321 (which is incorporated herein by reference), the BSR procedure is used to provide the serving gNB with information about the amount of UL data in a MAC entity. Radio Resource Control ("RRC") configures the following parameters to control the BSR: • periodicBSR-Timer ·retxBSR-Timer ·logicalChannelSR-DelayTimerApplied •logicalChannelSR-DelayTimer • logicalChannelSR-Mask • Logical Channel Group

[0051] Each logical channel may be assigned to a logical channel group ("LCG") using logicalChannelGroup. In one embodiment, the maximum number of LCGs is 8. The MAC entity determines the amount of UL data available to the logical channel by following a data volume calculation procedure, for example, as in TS 38.322 and 38.323. A BSR is triggered if any of the following events occur: • UL data becomes available to MAC entities for logical channels belonging to LCG. • This UL data belongs to a logical channel with a higher priority than any logical channel containing available UL data belonging to any LCG, or If none of the logical channels belonging to the LCG contain any available UL data, then the BSR is referred to below as a "normal BSR". It is one of the following: • When a UL resource is allocated and the number of padding bits is greater than or equal to the size of the buffer status report MAC CE and its subheaders combined, the BSR is referred to below as a "padding BSR". When the retxBSR-Timer expires and at least one of the logical channels belonging to the LCG contains UL data, the BSR is referred to below as a "normal BSR". • The periodicBSR-Timer has expired, and in this case, the BSR is referred to as the "periodic BSR" below. Note 1: When an event that triggers a normal BSR occurs simultaneously for multiple logical channels, each logical channel triggers one separate normal BSR.

[0052] For a standard BSR, the MAC entity shall perform the following actions: 1> If BSR is triggered for a logical channel such that logicalChannelSR-DelayTimerApplied, whose value is true, is configured by a higher layer: 2> Start or restart the logicalChannelSR-DelayTimer. 1> Otherwise: 2> If it is running, stop logicalChannelSR-DelayTimer.

[0053] For regular BSRs and periodic BSRs, the MAC entity shall perform the following: 1> When one or more LCGs have data available for transmission, when a MAC PDU containing a BSR should be constructed: 2> Report a long BSR for all LCGs that have data available for transmission. 1> Otherwise: 2> Report a short BSR.

[0054] With respect to padding BSR, the MAC entity shall perform the following: 1> If the number of padding bits is greater than or equal to the combined size of the short BSR and its subheaders, but less than the combined size of the long BSR and its subheaders: 2> When one or more LCGs have data available for transmission when a BSR should be constructed: 3> If the number of padding bits is equal to the size of the short BSR and its subheader combined: 4> Report the short truncated BSR of the LCG using the highest priority logical channel with data available for transmission. 3> Otherwise: 4> Report the long truncated BSRs of LCGs using logical channels with data available for transmission, in descending order of the highest priority logical channels (with or without data available for transmission) in each of these LCGs, and in ascending order of LCGID if the priorities are equal. 2> Otherwise: 3> Report a short BSR. 1> If the number of padding bits is greater than or equal to the size of the long BSR and its subheader combined: 2> Report a long BSR for all LCGs that have data available for transmission.

[0055] For BSRs triggered by the expiration of the retxBSR-Timer, the MAC entity considers the logical channel that triggered the BSR to be the highest-priority logical channel with data available for transmission at the time the BSR was triggered.

[0056] The MAC entity shall perform the following actions: 1> If the buffer status reporting procedure determines that at least one BSR has been triggered and not canceled: 2> If the UL-SCH resource is available for the new transmission and can accommodate the BSR MAC CE plus its subheaders as a result of logical channel prioritization: 3> Instruct the multiplexing and assembly procedure to generate a BSR MAC CE as defined in Clause 6.1.3.1, 3> Start or restart the periodicBSR-Timer unless all generated BSRs are long truncated BSRs or short truncated BSRs. 3> Start or restart retxBSR-Timer. 2> If a normal BSR is triggered and logicalChannelSR-DelayTimer is not running: 3> If there are no UL-SCH resources available for the new transmission, or 3> If a MAC entity is configured using an uplink grant and a normal BSR is triggered for a logical channel where logicalChannelSR-Mask is set to false, or 3> If the UL-SCH resources available for the new transmission do not satisfy the LCP mapping constraints configured for the logical channel that triggered the BSR (see Clause 5.4.3.1): 4> Trigger a scheduling request. Note 2: If a MAC entity is configured with, receives, or determines to have an uplink grant, the UL-SCH resource is considered available. If a MAC entity determines that the UL-SCH resource is available at a given time, this does not necessarily imply that the UL-SCH resource is available at that time.

[0057] A MAC PDU shall contain at most one BSR MAC CE, even when multiple events trigger a BSR. Normal and periodic BSRs take precedence over padding BSRs. A MAC entity shall restart the retxBSR-Timer when it receives a grant for new data transmission on any UL-SCH.

[0058] A triggered BSR may be canceled if the UL grant can accommodate all available unresolved data for transmission but is insufficient to accommodate the BSR MAC CE and its subheaders. A BSR triggered before the assembly of a MAC PDU shall be canceled if the MAC PDU is transmitted and this PDU contains a long BSR MAC CE or a short BSR MAC CE containing buffer status up to (and including) the last event that triggered the BSR before the assembly of the MAC PDU. Note 3: MAC PDU assembly can occur at any point between the reception of the uplink grant and the actual transmission of the corresponding MAC PDU. BSR and SR can be triggered after the assembly of the MAC PDU, including the BSR MAC CE, but before the transmission of this MAC PDU. In addition, BSR and SR can be triggered during the assembly of the MAC PDU. Note 4: If the HARQ process is configured using cg-RetransmissionTimer, and the BSR is already included in the MAC PDU for transmission on the grant configured by this HARQ process but has not yet been transmitted by a lower layer, how the contents of the BSR are handled depends on the UE implementation.

[0059] In one embodiment, the BSR MAC CE is LCG ID, LCG iIt has a field called buffer size. Tables 6.1.3.1-1 and 6.1.3.1-2 in TS 38.321 (incorporated herein by reference) provide buffer size levels (in bytes) for 5-bit and 8-bit buffer size fields, respectively. The buffer size field length for short BSR format and short truncated BSR format is 5 bits, and the buffer size field length for long BSR format and long truncated BSR format is 8 bits. Figure 2 shows short BSR and short truncated BSR MAC CEs, while Figure 3 shows long BSR, long truncated BSR, and preemptive BSR MAC CEs.

[0060] In one embodiment, the recommended bitrate MAC CE is identified by a MAC subheader with a logical channel identifier ("LCID"), as defined in Tables 6.2.1-1 and 6.2.1-2 of TS 38.321 (incorporated herein by reference), for the bitrate recommendation message from gNB to UE and the bitrate recommendation query message from UE to gNB, respectively. It has a fixed size and consists of two octets, as defined below (as shown in Figure 4). - LCID: This field identifies the logical channel to which the recommended bitrate or recommended bitrate query is applicable. The field length is 6 bits. - Uplink / Downlink (UL / DL): This field indicates whether the recommended bitrate or recommended bitrate query applies to the uplink or downlink. The field length is 1 bit. A UL / DL field set to 0 indicates the downlink. A UL / DL field set to 1 indicates the uplink. - Bitrate: This field indicates an index on Table 6.1.3.20-1. The field length is 6 bits. In bitrate recommendations, the value indicates the recommended bitrate. In bitrate recommendation queries, the value indicates the desired bitrate. - X: Bitrate multiplier. For UEs that support the recommended bitrate multiplier, when bitRateMultiplier is configured for the logical channel indicated by the LCID field, setting the X field to "1" indicates that the actual bitrate value corresponds to the value indicated by the bitrate field multiplied by bitRateMultiplier as defined in TS 38.331. - A spare bit set to R:0. [Table 1]

[0061] In one embodiment, Extended Reality ("XR") and Cloud Gaming ("CG") are key applications of 5G media being considered in the industry. According to TR 26.928, XR is a general term for different types of reality, including: Virtual reality ("VR") is a rendered version of a delivered visual and auditory scene. The rendering is designed to mimic the sensory stimuli of real-world visuals and sounds as natural as possible to the observer or user as they move within a limited range depending on the application. While not always necessary, virtual reality usually requires the user to wear a head-mounted display ("HMD"), completely replacing the user's field of view with simulated visual components, wear headphones, and provide the user with accompanying sounds. In VR, it is also usually necessary to track the user's head and movements in some way to allow the simulated visual and auditory components to be updated to ensure that objects and sound sources remain in harmony with the user's movements. Additional means of interacting with the virtual reality simulation may be provided, but are not always necessary. Augmented reality ("AR") is a system in which a user is provided with additional information or artificially generated objects or content superimposed on their current environment. Such additional information or content is usually visual and / or audible, and the observation of the current environment may be direct, without intermediate perception, processing, and rendering, or indirect, such that the perception of the environment may be relayed through sensors and augmented or processed. Mixed reality ("MR") is an evolved form of augmented reality in which several virtual elements are inserted into a physical scene, intended to provide the illusion that these elements are part of a real-world scene. Extended reality ("XR") refers to all kinds of synthetic environments and human-machine interactions that combine reality and virtuality, generated by computer technology and wearables. It includes representative forms such as AR, MR, and VR, and the areas in between. The level of virtuality ranges from partial perceptual input to fully immersive VR. A key aspect of XR is the extension of human experience, particularly relating to the sense of presence (represented by VR) and cognitive acquisition (represented by AR).

[0062] In the measures described below, the terms "mini-slot," "sub-slot," or "aggregated slot" may also be used instead of "slot," and the concepts of slot / mini-slot / sub-slot / aggregated slot may be explained as defined in TS 38.211 / TS 38.213 / TS 38.214 (which are incorporated herein by reference).

[0063] References to TS 38.211, TS 38.212, TS 38.213, and TS 38.214 throughout this disclosure refer to the current version of the specification, V16.6.0, and references to TS 38.321 refer to the current version of the specification, V16.5.0.

[0064] Several embodiments are described below. According to one possible embodiment, one or more elements or features from one or more of the embodiments described may be combined.

[0065] Given UL AR traffic at 60fps with a data rate of 10Mbps (e.g., a stream aggregating scene, video, data, and audio streams), each frame / packet averages approximately 20834 bytes. Considering packet size variability (e.g., following a truncated normal distribution of [STD,MAX,MIN]:[10.5,150,50]% of the average packet size), the buffer size level in the BSR MAC-CE may not be sufficiently accurate. For example, for 20834 bytes, a 5-bit BSR table, for example, using / indicating BS (buffer size) index 25 in a short BSR, where that BS index 25 can support up to 28581 bytes (the BS value corresponding to index 24 is less than or equal to 20516 bytes), could result in a difference of approximately 27% between the actual buffer size and the maximum buffer size (the gNB would need to allocate approximately 27% more resources). Given the low packet error rate requirement for XR (e.g., 1%), such a difference in allocated resources can lead to inefficient resource allocation. Below, we propose various measures to improve the display of buffer sizes.

[0066] In one embodiment, the UE is configured with a first table (e.g., a first set thereof) containing buffer size levels (in bytes) having "k" bits (e.g., "k=5") for the buffer size field of the BSR MAC-CE, and the UE determines a second table (e.g., a second set thereof) containing buffer size levels having "k" bits (e.g., "k=5") for the buffer size field of the BSR MAC-CE.

[0067] In such embodiments, the UE uses a first table for a first set of LCGs and a second table for a second set of LCGs, where the set may contain one LCG and at least one buffer size level differs between the two tables. In one embodiment, the second table may have buffer level sizes that are closer to each other over a range of buffer sizes (for example, for AR traffic, considering that STD is, for example, around 10.5% of the average packet size (m), from -3*STD+m to 3*STD+m, or in another example, a range of buffer sizes (Min%, Max%) of the average packet size), where "Min%" and "Max%" are percentages.

[0068] In another embodiment, the UE is configured with a first buffer size level table associated with at least a first LCG and a second buffer size level table associated with at least a second LCG, wherein at least one buffer size level differs between the two tables. The UE uses the first buffer size level table to report the buffer size associated with at least the first LCG in the BSR when the first logical channel group has available data, and uses the second buffer size level table to report the buffer size associated with at least the second LCG in the BSR when the second logical channel group has available data.

[0069] In one embodiment, a second table is configured for the UE. For a short BSR, the UE is configured using an 8-bit buffer size table (Table 6.1.3.1-2 in TS 38.321) or a subset of values ​​from the 8-bit buffer size table as a second table for the LCG set. An example of a 5-bit second table for a short BSR is provided in Table 1 (Table 2) below (changes are in bold italics, and the new values ​​are taken from the 8-bit buffer size table in TS 38.321). [Table 2] [Table 3]

[0070] In one embodiment, a second table is derived based on several traffic parameters, including average packet size and traffic packet statistics such as STD and fps. The traffic parameters (such as average packet size and average packet jitter) may be shown in the BSR or associated with the LCG ID.

[0071] In one embodiment, the second table is the first table for the short format BSR, and the UE is configured using an 8-bit buffer size table for all LCGs (Table 6.1.3.1-2 in TS 38.321).

[0072] In one embodiment, the UE uses a second table (based on an 8-bit buffer size table (Table 6.1.3.1-2 in TS 38.321)) for a certain period of time (determined, for example, by the expiration of a timer) after a particular traffic (e.g., XR traffic including scenes and / or video for the UL) has been scheduled.

[0073] In one embodiment, upon receiving a MAC CE / Downlink Control Information ("DCI") indication, the UE uses a second table (based on an 8-bit buffer size table (Table 6.1.3.1-2 in TS 38.321)). A MAC CE / DCI indication may indicate the activation / initiation of potential XR traffic. A DCI indication may be a DCI that enables a configured grant transmission at a specific period (e.g., 4ms).

[0074] In one embodiment, the UE indicates which table is used for buffer size indication (for example, per LCG).

[0075] In one embodiment, the UE indicates a set of parameters (for example, the average packet size related to the LCG) that the gNB may use to determine the buffer size level based on the indicated set of indices and parameters.

[0076] In one embodiment, the network configures the UE to use either a default first table for LCG (the 5-bit short BS field in Table 6.1.3.1-1 in TS 38.321) or a second table.

[0077] In one embodiment, the network may configure the UE using buffer size levels for a second table. For example, based on a bitmap ("Bi") of possible sets of buffer size values ​​(for example, bit field Bi corresponds to buffer size level BSi), the Bi field is set to "1" to indicate that buffer size level BSi exists and maps to a code point in the buffer size field. The Bi field is set to "0" to indicate that buffer size level BSi does not exist and does not map to a code point in the buffer size field. The code point to which the buffer size level maps is determined by its ordinal position among all buffer size levels where the Bi field is set to 1, i.e., a first buffer size level where the Bi field is set to 1 maps to code point value 0, a second buffer size level where the Bi field is set to 1 maps to code point value 1, and so on. The maximum number of buffer size levels for a short BSR is 32.

[0078] In one embodiment, the LCG is assigned to a set of XR-related traffic (e.g., AR traffic).

[0079] In one embodiment, two LCG types may be defined. One LCG type may belong to XR-related traffic, and the other LCG type may cover the rest of possible traffic. One LCG type may be associated with I-frames, and the other LCG type may be associated with P-frames.

[0080] In one embodiment, the MAC entity performs the following actions with respect to a normal BSR. 1> When a MAC PDU containing a BSR should be constructed, if one or more LCGs have data available for transmission: 2> Report a first type long BSR for all first type LCGs that have data available for transmission. 2> Report a second type long BSR for all second type LCGs that have data available for transmission. 1> Otherwise: 2> Report a short BSR.

[0081] The first LCG type and the second LCG type may use different or the same table for buffer size. In one embodiment, separate resources may be required for high / medium reliability compared to resources required for low / normal priority. Also, since different traffic may have different packet delay limits ("PDBs"), a gNB with use-awareness (knowledge of some aspect of traffic, such as reliability / delay requirements) may benefit from having different (long) BSRs.

[0082] In one embodiment, for a normal BSR, the MAC entity reports a long BSR to all LCGs that have data available for transmission when one or more LCGs have data available for transmission when a MAC PDU containing the BSR should be constructed. The UE indicates which LCG has the majority (or more than "x") of the data to be transmitted (e.g., in a BSR MAC-CE), so the gNB can use the traffic parameters / characteristics of the LCG with the majority of the data to efficiently allocate resources.

[0083] If a short BSR uses an 8-bit buffer size field table, padding bits are added to the short BSR to make it 16 bits instead of 8 bits. A field in the MAC subheader of a short MAC CE may indicate whether the short BSR is an 8-bit MAC CE or a 16-bit MAC CE. For example, one bit might be a spare bit in the MAC subheader. In another alternative example, a new spare LCID might indicate a 16-bit short BSR MAC CE.

[0084] In one embodiment, the UE is configured to report a long BSR or long truncated BSR MAC CE when the UE reports the buffer status of a pre-configured LCG, for example, an LCG used for XR-related traffic. The UE also reports a long BSR or truncated long BSR MAC CE even when the buffer status is reported for a single LCG. In one implementation, a field in the MAC subheader or MAC CE may indicate that the UE has no data available for transmission for other LCGs.

[0085] In one embodiment, multiple tables are predetermined or configured for the UE, each defining a set of buffer size levels (e.g., in bytes) for a buffer size field of a given X bits (e.g., X=5 or 8). In one embodiment, the UE receives information or indications of the buffer size level tables (equivalently, sets of buffer size levels) associated with a logical channel in a logical channel configuration, as shown in Figure 5. The UE does not expect logical channels with the same logical channel group identification information to be configured using different buffer size level tables (e.g., different sets of buffer size levels). The UE uses the indicated buffer size level tables to send buffer status reports for the logical channels.

[0086] In one embodiment, the LogicalChannelConfig IE shown in Figure 5 is used to configure logical channel parameters. In one embodiment, the logicalChannelGroup parameter 502 is the ID of the logical channel group to which the logical channel belongs, as defined in TS 38.321. In one embodiment, the bsr-TableID parameter 504 is the ID of the buffer size level table to be used for buffer status reporting for the logical channel. The UE does not expect logical channels with the same logical channel group ID to be configured with different bsr-TableID values. If not configured, the UE uses a default buffer size level table for a given X-bit (X=5 or 8) buffer size field.

[0087] For example, the logical channel configuration includes parameters relating to the nature of the UL data traffic associated with the LCG, such as a field indicating whether group-of-picture ("GOP")-based video coding is used for LCG-related traffic, or slice-based video coding (for example, as used in H.264 Advanced Video Coding). This field may have field values ​​indicating other types of traffic (for example, web browsing).

[0088] In one embodiment, which addresses a mechanism for providing a more accurate recommended bitrate MAC CE, a new value for bitRateMultiplier (e.g., a value other than those already provided in the bitRateMultiplier-r16 RRC parameter, i.e., 40, 70, 100, 200) may be used to increase the granularity of the recommended bitrate. In one example, an offset is configured (e.g., -2), and the bitrate multiplier is determined based on the bitRateMultiplier and offset indicated by the RRC. In another example, the new value for offset / bitrate multiplier is applicable only to a range of values ​​(e.g., values ​​in the range of 2000 to 4000) in the bitrate field used to determine the recommended bitrate (e.g., Table 6.1.3.20-1 in TS 38.321).

[0089] Figure 6 shows an NR protocol stack 600 according to an embodiment of the present disclosure. Figure 6 shows a remote unit 101, a base unit 121, and a mobile core network 130, which represent a set of UEs that interact with RAN nodes and NFs (e.g., AMFs) in the core network. As shown, the protocol stack 600 comprises a user plane protocol stack 601 and a control plane protocol stack 603. The user plane protocol stack 604 includes a physical ("PHY") layer 605, a MAC sublayer 610, a radio link control ("RLC") sublayer 615, a packet data convergence protocol ("PDCP") sublayer 620, and a service data adaptive protocol ("SDAP") layer 625. The control plane protocol stack 603 also includes a physical layer 605, a MAC sublayer 610, an RLC sublayer 615, and a PDCP sublayer 620. The control plane protocol stack 603 also includes the RRC sublayer and the non-accessible layer ("NAS") layer 635.

[0090] The AS protocol stack for the control plane protocol stack 603 consists of at least the RRC, PDCP, RLC, and MAC sublayers, as well as the physical layer. The AS protocol stack for the user plane protocol stack 601 consists of at least the SDAP, PDCP, RLC, and MAC sublayers, as well as the physical layer. Layer 2 ("L2") is divided into the SDAP, PDCP, RLC, and MAC sublayers. Layer 3 ("L3") includes the RRC sublayer 630 and NAS layer 635 for the control plane, and includes, for example, the Internet Protocol ("IP") layer or PDU layer (not shown) for the user plane. Layers L1 and L2, such as PUCCH / PUSCH or MAC CE, are called "lower layers," while L3 and above (e.g., transport layer, application layer), such as RRC, are called "higher layers" or "upper layers."

[0091] The physical layer 605 provides the transport channel to the MAC sublayer 610. The MAC sublayer 610 provides the logical channel to the RLC sublayer 615. The RLC sublayer 615 provides the RLC channel to the PDCP sublayer 620. The PDCP sublayer 620 provides radio bearers to the SDAP sublayer 625 and / or the RRC layer 630. The SDAP sublayer 625 provides QoS flows to the mobile core network 130 (e.g., 5GC). The RRC layer 630 performs carrier aggregation and / or dual connectivity addition, modification, and release. The RRC layer 630 also manages the establishment, configuration, maintenance, and release of signaling radio bearers ("SRBs") and data radio bearers ("DRBs"). In some embodiments, the RRC entity functions for radio link failure detection and recovery therefrom.

[0092] Figure 7 shows a user equipment device 700 that may be used for buffer status reporting for Extended Reality Services according to embodiments of the present disclosure. In various embodiments, the user equipment device 700 is used to implement one or more of the measures described above. The user equipment device 700 may be an embodiment of a UE such as the remote unit 105 and / or UE205, as described above. Furthermore, the user equipment device 700 may include a processor 705, memory 710, input device 715, output device 720, and transceiver 725. In some embodiments, the input device 715 and output device 720 are combined into a single device such as a touchscreen. In some embodiments, the user equipment device 700 may not include any input device 715 and / or output device 720. In various embodiments, the user equipment device 700 may include one or more of the processor 705, memory 710, and transceiver 725, and may not include the input device 715 and / or output device 720.

[0093] As shown, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735, where the transceiver 725 communicates with one or more base units 121. In addition, the transceiver 725 may support at least one network interface 740 and / or application interface 745. The application interface 745 may support one or more APIs. The network interface 740 may support 3GPP reference points such as Uu and PC5. Other network interfaces 740 may be supported, as will be understood by those skilled in the art.

[0094] In one embodiment, the processor 705 may include any known controller capable of executing computer-readable instructions and / or logical operations. For example, the processor 705 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field-programmable gate array ("FPGA"), digital signal processor ("DSP"), coprocessor, application-specific processor, or similar programmable controller. In some embodiments, the processor 705 executes instructions stored in memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to memory 710, input device 715, output device 720, and transceiver 725. In some embodiments, the processor 705 may include an application processor (also known as the "main processor") that manages application area and operating system ("OS") functions, and a baseband processor (also known as the "baseband radio processor") that manages radio functions.

[0095] In one embodiment, memory 710 is a computer-readable storage medium. In some embodiments, memory 710 includes a volatile computer storage medium. For example, memory 710 may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 710 includes a non-volatile computer storage medium. For example, memory 710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 710 includes both volatile and non-volatile computer storage mediums.

[0096] In some embodiments, memory 710 stores data relating to buffer status reports for Extended Reality Services. For example, memory 710 may store parameters, configurations, resource allocations, policies, etc., as described above. In some embodiments, memory 710 also stores program code and associated data, such as an operating system or other controller algorithms running on user equipment 700, and one or more software applications.

[0097] In one embodiment, the input device 715 may include any known computer input device, such as a touch panel, buttons, a keyboard, a stylus, or a microphone. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 715 includes a touchscreen so that text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touchscreen.

[0098] In one embodiment, the output device 720 is designed to output visual, audible, and / or tactile signals. In some embodiments, the output device 720 includes an electronically controllable display or display device capable of outputting visual data to the user. For example, the output device 720 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc., to the user. In another, but not limited, example, the output device 720 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display, that is separate from the rest of the user equipment device 700 but communicatively coupled to it. Furthermore, the output device 720 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0099] In some embodiments, the output device 720 includes one or more speakers for producing sound. For example, the output device 720 may produce an audible warning or notification (e.g., a beep or chime). In some embodiments, the output device 720 includes one or more haptic devices for producing vibration, motion, or other tactile feedback. In some embodiments, all or part of the output device 720 may be integrated with the input device 715. For example, the input device 715 and the output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 720 may be located near the input device 715.

[0100] The transceiver 725 includes at least one transmitter 730 and at least one receiver 735. As described herein, the transceiver 725 may be used to provide UL communication signals to the base unit 121 and to receive DL communication signals from the base unit 121. Similarly, as described herein, the transceiver 725 may be used to transmit and receive SL signals (e.g., V2X communication). Although only one transmitter 730 and one receiver 735 are shown, the user equipment 700 may have any suitable number of transmitters 730 and receivers 735. Furthermore, the transmitters 730 and receivers 735 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 725 includes a first transmitter / receiver pair used to communicate with a mobile communication network over the licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over the unlicensed radio spectrum.

[0101] In some embodiments, a first transmitter / receiver pair used to communicate with a mobile communications network over the licensed radio spectrum, and a second transmitter / receiver pair used to communicate with the mobile communications network over the unlicensed radio spectrum, may be combined into a single transceiver unit, for example, a single chip that performs functions for use with both the licensed and unlicensed radio spectrums. In some embodiments, the first and second transmitter / receiver pairs may share one or more hardware components. For example, several transceivers 725, transmitters 730, and receivers 735 may be implemented as physically separate components that access shared hardware and / or software resources, such as a network interface 740.

[0102] In various embodiments, one or more transmitters 730 and / or one or more receivers 735 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, system-on-chip, ASIC, or other type of hardware component. In some embodiments, one or more transmitters 730 and / or one or more receivers 735 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 740 or other hardware components / circuits, may be integrated into a single chip along with any number of transmitters 730 and / or receivers 735. In such embodiments, the transmitters 730 and receivers 735 may be logically configured as transceivers 725 using one or more common control signals, or as modular transmitters 730 and receivers 735 implemented on the same hardware chip or multi-chip module.

[0103] In one embodiment, the processor 705 receives an indication from the network that a fixed-size short-format BSR can be used, and in response to an indication that a fixed-size short-format BSR can be used, determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field, and in response to an indication that a fixed-size short-format BSR cannot be used, determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field, and sends the BSR to the network if the first buffer size field is shorter than the second buffer size field.

[0104] In one embodiment, the first buffer size field, the second buffer size field, or both, determine the total amount of data available after the media access control packet data unit has been constructed, according to a data volume calculation procedure across the logical channels of the logical channel group.

[0105] In one embodiment, the indicator is a wireless resource control indicator.

[0106] In one embodiment, the indicator is a media access control-control element indicator or a downlink control information indicator, and the indicator is applicable for a certain period of time or until the timer expires.

[0107] In one embodiment, the first table has a 5-bit buffer size level, and the second table has an 8-bit buffer size level.

[0108] In one embodiment, the label further includes a logical channel group identifier, and the label indicates whether a fixed-size short-format BSR can be used for the logical channel group identifier.

[0109] In one embodiment, the markings indicate that a fixed-size short-format BSR can be used for a first logical channel group identifier, and that a fixed-size short-format BSR cannot be used for a second logical channel group identifier.

[0110] In one embodiment, the processor 705 is configured to determine a first logical channel identifier corresponding to a short-format BSR associated with a first logical channel group identifier, and a second logical channel identifier corresponding to a long-format BSR associated with a second logical channel group identifier, and to prepare at least one of the short-format BSR and the long-format BSR.

[0111] In one embodiment, the processor 705 is configured to determine whether a BSR is triggered, determine the logical channel group that should be included in the BSR, determine the BSR format for the triggered BSR according to the indicated and determined logical channel group, and transmit the BSR according to the determined BSR format.

[0112] In one embodiment, at least one of the first table and the second table is shown for the logical channels in the corresponding logical channel configuration.

[0113] In one embodiment, the logical channels of a logical channel group have at least the same first table, the same second table, or both.

[0114] In one embodiment, the processor 705 is configured to report long-format BSRs based on a second table for logical channel groups that have data available for transmission, in response to one or more logical channel groups having data available for transmission when a medium access control packet data unit including a BSR is constructed.

[0115] Figure 8 shows one embodiment of a network device 800 that may be used for buffer status reporting for Extended Reality Services according to embodiments of the present disclosure. In some embodiments, the network device 800 may be one embodiment of a RAN node such as the base unit 121 and / or / gNB and supporting hardware, as described above. Furthermore, the network device 800 may include a processor 805, memory 810, input device 815, output device 820, and transceiver 825. In some embodiments, the network device 800 does not include any input device 815 and / or output device 820.

[0116] As shown, the transceiver 825 includes at least one transmitter 830 and at least one receiver 835, where the transceiver 825 communicates with one or more remote units 105. In addition, the transceiver 825 may support at least one network interface 840 and / or application interface 845. The application interface 845 may support one or more APIs. The network interface 840 may support 3GPP reference points such as Uu, N1, N2, N3, N5, N6, and / or N7 interfaces. Other network interfaces 840 may be supported as understood by those skilled in the art.

[0117] In one embodiment, the processor 805 may include any known controller capable of executing computer-readable instructions and / or logical operations. For example, the processor 805 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, DSP, coprocessor, application-specific processor, or similar programmable controller. In some embodiments, the processor 805 executes instructions stored in memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to memory 810, input device 815, output device 820, and transceiver 825. In some embodiments, the processor 805 may include an application processor (also known as the “main processor”) that manages the application area and OS functions, as well as a baseband processor (also known as the “baseband radio processor”) that manages radio functions. In various embodiments, the processor 805 controls the network device 800 to implement the network entity behavior (e.g., gNB) described above for buffer status reporting for Extended Reality Services.

[0118] In one embodiment, memory 810 is a computer-readable storage medium. In some embodiments, memory 810 includes a volatile computer storage medium. For example, memory 810 may include RAM, including DRAM, SDRAM, and / or SRAM. In some embodiments, memory 810 includes a non-volatile computer storage medium. For example, memory 810 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 810 includes both volatile and non-volatile computer storage mediums.

[0119] In some embodiments, memory 810 stores data relating to buffer status reports for the Extended Reality Service. For example, memory 810 may store parameters, configurations, resource allocations, policies, etc., as described above. In some embodiments, memory 810 also stores program code and associated data, such as an OS or controller algorithm and one or more software applications running on the network device 800.

[0120] In one embodiment, the input device 815 may include any known computer input device, such as a touch panel, buttons, a keyboard, a stylus, or a microphone. In some embodiments, the input device 815 may be integrated with an output device 820, such as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 815 includes a touchscreen so that text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. In some embodiments, the input device 815 includes two or more different devices, such as a keyboard and a touchscreen.

[0121] In one embodiment, the output device 820 may include any known electronically controllable display or display device. The output device 820 is designed to output visual, audible, and / or tactile signals. In some embodiments, the output device 820 includes an electronic display capable of outputting visual data to a user. Furthermore, the output device 820 may be a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0122] In some embodiments, the output device 820 includes one or more speakers for producing sound. For example, the output device 820 may produce an audible warning or notification (e.g., a beep or chime). In some embodiments, the output device 820 includes one or more haptic devices for producing vibration, motion, or other tactile feedback. In some embodiments, all or part of the output device 820 may be integrated with the input device 815. For example, the input device 815 and the output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of the output device 820 may be located near the input device 815.

[0123] As discussed above, transceiver 825 may communicate with one or more remote units and / or one or more interworking functions that provide access to one or more PLMNs. Transceiver 825 may also communicate with one or more network functions (for example, in the mobile core network 80). Transceiver 825 operates under the control of processor 805 to transmit and receive messages, data, and other signals. For example, processor 805 may selectively enable transceivers (or parts thereof) at specific times to transmit and receive messages.

[0124] The transceiver 825 may include one or more transmitters 830 and one or more receivers 835. In some embodiments, one or more transmitters 830 and / or one or more receivers 835 may share transceiver hardware and / or circuitry. For example, one or more transmitters 830 and / or one or more receivers may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, the transceiver 825 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0125] In one embodiment, the processor 905 transmits an indication to the UE showing the BSR format to be used for the BSR, and the BSR format comprises one of a fixed-size long format and a short format. The processor receives the BSR according to the indicated BSR format and, in response to an indication that a fixed-size short format BSR can be used, determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field. In response to an indication that a fixed-size short format BSR cannot be used, the processor 905 determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field, configured such that the first buffer size field is shorter than the second buffer size field.

[0126] Figure 9 is a flowchart of Method 900 for buffer status reporting for Extended Reality Services. Method 900 may be performed by a UE device as described herein, for example, a remote unit 105 and / or a user equipment device 700. In some embodiments, Method 900 may be performed by a processor that executes program code, for example, a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0127] In one embodiment, method 900 starts and receives an indication from the network that a fixed-size short-format BSR can be used (905). In one embodiment, in response to an indication that a fixed-size short-format BSR can be used, method 900 determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field (910). In one embodiment, in response to an indication that a fixed-size short-format BSR cannot be used, method 900 determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field (915), where the first buffer size field is shorter than the second buffer size field. In one embodiment, method 900 transmits the BSR to the network (920), and method 900 ends.

[0128] Figure 10 is a flowchart of Method 1000 for buffer status reporting for Extended Reality Services. Method 1000 may be performed by network devices such as those described herein, e.g., gNB, base station 121, and / or network equipment device 800. In some embodiments, Method 1000 may be performed by a processor that executes program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0129] In one embodiment, method 1000 starts by sending a notification to the UE indicating the BSR format to be used for the BSR (1005), the BSR format comprising one of a fixed-size long format and a short format. In one embodiment, method 1000 receives a BSR according to the indicated BSR format (1010). In one embodiment, in response to a notification indicating that a fixed-size short format BSR can be used, method 1000 determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field (1015). In one embodiment, in response to a notification indicating that a fixed-size short format BSR cannot be used, method 1000 determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field (1020), the first buffer size field being shorter than the second buffer size field, and method 1000 terminates.

[0130] A first apparatus for buffer status reporting for Extended Reality Services is disclosed. The first apparatus may include UE equipment as described herein, for example, remote unit 105 and / or user equipment equipment 700. In some embodiments, the first apparatus may include a processor that executes program code, for example, a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0131] In one embodiment, the first device includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor is configured to cause the device to receive an indication from the network that a fixed-size short-format BSR can be used, to determine a buffer size based on a first table having buffer size levels corresponding to a first buffer size field in response to an indication that a fixed-size short-format BSR can be used, to determine a buffer size based on a second table having buffer size levels corresponding to a second buffer size field in response to an indication that a fixed-size short-format BSR cannot be used, and to send a BSR to the network if the first buffer size field is shorter than the second buffer size field.

[0132] In one embodiment, the first buffer size field, the second buffer size field, or both, determine the total amount of data available after the media access control packet data unit has been constructed, according to a data volume calculation procedure across the logical channels of the logical channel group.

[0133] In one embodiment, the indicator is a wireless resource control indicator.

[0134] In one embodiment, the indicator is a media access control-control element indicator or a downlink control information indicator, and the indicator is applicable for a certain period of time or until the timer expires.

[0135] In one embodiment, the first table has a 5-bit buffer size level, and the second table has an 8-bit buffer size level.

[0136] In one embodiment, the label further includes a logical channel group identifier, and the label indicates whether a fixed-size short-format BSR can be used for the logical channel group identifier.

[0137] In one embodiment, the markings indicate that a fixed-size short-format BSR can be used for a first logical channel group identifier, and that a fixed-size short-format BSR cannot be used for a second logical channel group identifier.

[0138] In one embodiment, the processor is configured to cause the device to determine a first logical channel identifier corresponding to a short-format BSR associated with a first logical channel group identifier, and a second logical channel identifier corresponding to a long-format BSR associated with a second logical channel group identifier, and to prepare at least one of the short-format BSR and the long-format BSR.

[0139] In one embodiment, the processor is configured to cause the device to determine whether a BSR is triggered, to determine the logical channel group that should be included in the BSR, to determine the BSR format for the triggered BSR according to the indicated and determined logical channel group, and to transmit the BSR according to the determined BSR format.

[0140] In one embodiment, at least one of the first table and the second table is shown for the logical channels in the corresponding logical channel configuration.

[0141] In one embodiment, the logical channels of a logical channel group have at least the same first table, the same second table, or both.

[0142] In one embodiment, the processor is configured to cause the device to report a long-format BSR based on a second table for logical channel groups that have data available for transmission, in response to one or more logical channel groups having data available for transmission when a medium access control packet data unit including a BSR is constructed.

[0143] A first method for buffer status reporting for Extended Reality Services is disclosed. The first method may be performed by a UE device, such as the remote unit 105 and / or user equipment device 700, as described herein. In some embodiments, the first method may be performed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0144] In one embodiment, the first method receives an indication from the network that a fixed-size short-format BSR can be used, determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field in response to an indication that a fixed-size short-format BSR can be used, determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field in response to an indication that a fixed-size short-format BSR cannot be used, and transmits the BSR to the network if the first buffer size field is shorter than the second buffer size field.

[0145] In one embodiment, the first buffer size field, the second buffer size field, or both, determine the total amount of data available after the media access control packet data unit has been constructed, according to a data volume calculation procedure across the logical channels of the logical channel group.

[0146] In one embodiment, the indicator is a wireless resource control indicator.

[0147] In one embodiment, the indicator is a media access control-control element indicator or a downlink control information indicator, and the indicator is applicable for a certain period of time or until the timer expires.

[0148] In one embodiment, the first table has a 5-bit buffer size level, and the second table has an 8-bit buffer size level.

[0149] In one embodiment, the label further includes a logical channel group identifier, and the label indicates whether a fixed-size short-format BSR can be used for the logical channel group identifier.

[0150] In one embodiment, the markings indicate that a fixed-size short-format BSR can be used for a first logical channel group identifier, and that a fixed-size short-format BSR cannot be used for a second logical channel group identifier.

[0151] In one embodiment, the first method determines a first logical channel identifier corresponding to a short-format BSR associated with a first logical channel group identifier, and a second logical channel identifier corresponding to a long-format BSR associated with a second logical channel group identifier, and prepares at least one of the short-format BSR and the long-format BSR.

[0152] In one embodiment, the first method determines whether a BSR is triggered, determines the logical channel group to be included in the BSR, determines the BSR format for the triggered BSR according to the indicated and determined logical channel group, and transmits the BSR according to the determined BSR format.

[0153] In one embodiment, at least one of the first table and the second table is shown for the logical channels in the corresponding logical channel configuration.

[0154] In one embodiment, the logical channels of a logical channel group have at least the same first table, the same second table, or both.

[0155] In one embodiment, the first method reports a long-format BSR based on a second table for logical channel groups that have data available for transmission, in response to the fact that one or more logical channel groups have data available for transmission when a medium access control packet data unit including a BSR is constructed.

[0156] A second apparatus for buffer status reporting for Extended Reality Services is disclosed. The second apparatus may include network equipment as described herein, e.g., a gNB, a base station 121, and / or network equipment equipment 800. In some embodiments, the second apparatus may include a processor for executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, and the like.

[0157] In one embodiment, the second device includes a transceiver and a processor coupled to the transceiver. In one embodiment, the processor causes the device to send a marking to the UE indicating a BSR format to be used for the BSR, the BSR format comprising one of a fixed-size long format and a short format, to receive a BSR according to the indicated BSR format, to determine a buffer size based on a first table having buffer size levels corresponding to a first buffer size field in response to a marking indicating that a fixed-size short format BSR can be used, and to determine a buffer size based on a second table having buffer size levels corresponding to a second buffer size field in response to a marking indicating that a fixed-size short format BSR cannot be used, such that the first buffer size field is shorter than the second buffer size field.

[0158] A second method for buffer status reporting for Extended Reality Services is disclosed. The second method may be performed by network devices such as those described herein, e.g., gNB, base station 121, and / or network equipment device 800. In some embodiments, the second method may be performed by a processor that executes program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0159] In one embodiment, the second method transmits a marking to the UE indicating the BSR format to be used for the BSR, and the BSR format comprises one of a fixed-size long format and a short format, and the second method receives a BSR according to the indicated BSR format, and in response to a marking indicating that a fixed-size short format BSR can be used, the second method determines the buffer size based on a first table having buffer size levels corresponding to a first buffer size field, and in response to a marking indicating that a fixed-size short format BSR cannot be used, the second method determines the buffer size based on a second table having buffer size levels corresponding to a second buffer size field, and the first buffer size field is shorter than the second buffer size field.

[0160] The embodiments described may be practiced in other specific forms. The embodiments described should be considered in all respects as illustrative and not restrictive. Accordingly, the scope of the invention is indicated by the appended claims rather than by the above description. All modifications within the meaning of the claims and the scope of equivalents should be included within the scope of the claims. [Explanation of symbols]

[0161] 105 Remote Unit 107 Apps 120 Wireless Access Networks 121 Base Unit 123 UL / DL 130 Mobile Core Network 131 UPF 133 AMF 135 SMF 137 PCF 139 UDM / UDR 150 Data Networks 151 Application Server 600 NR protocol stack 601 User Plane Control Stack 603 Control Plane Protocol Stack 605 PHY Layer 610 MAC sublayer 615 RLC sublayer 620 PDCP sublayer 625 SDAP sublayer 630 RRC Layers 635 NAS Layers 700 User Equipment 705 Processor 710 memory 715 Input Devices 720 Output Devices 725 Transceiver 730 Transmitter 735 Receiver 740 Network Interfaces 745 Application Interfaces 800 Network Equipment 805 Processor 810 memory 815 Input Devices 820 Output Devices 825 Transceiver 830 Transmitter 835 Receiver 840 Network Interfaces 845 Application Interface

Claims

1. User equipment (UE) for wireless communications, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, The markings indicate that the first BSR format is available for a first logical channel group identifier and that the first BSR format is not available for a second logical channel group identifier, in a UE.

2. The UE according to claim 1, wherein the first buffer size field, or the second buffer size field, or both, determine the total amount of data available after the media access control packet data unit has been created, according to a data volume calculation procedure across the logical channels of the logical channel group.

3. The UE according to claim 1, wherein the marking is a wireless resource control marking.

4. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, The marking is a media access control-control element marking or a downlink control information marking, and the marking is applicable for a certain period of time or until a timer expires, in a UE.

5. The UE according to claim 1, wherein the first table has a 5-bit buffer size level and the second table has an 8-bit buffer size level.

6. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, The marking further comprises a logical channel group identifier, and the marking indicates whether the first BSR format is available for the logical channel group identifier, UE.

7. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to determine a first logical channel identifier corresponding to a BSR of a first BSR format associated with a first logical channel group identifier, and a second logical channel identifier corresponding to a second BSR format associated with a second logical channel group identifier, and to prepare at least one of the BSR of the first BSR format and the BSR of the second BSR format.

8. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, The aforementioned at least one processor provides the UE, Determine whether the BSR is triggered. Determine the logical channel group that should be included in the aforementioned BSR, In accordance with the above markings and the determined logical channel group, the BSR format for the triggered BSR is determined. The BSR is transmitted according to the BSR format determined above. The UE is configured in such a way.

9. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, The first table or the second table is shown for the logical channels in the corresponding logical channel configuration, UE.

10. User equipment (UE) for wireless communication, At least one memory, The system comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE, To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, A UE in which the logical channels of a logical channel group are associated with the first table, the second table, or both.

11. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to report a second BSR format based on the second table for logical channel groups having data available for transmission, in response that one or more logical channel groups have data available for transmission when a medium access control packet data unit including the BSR is created.

12. The steps include receiving an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the steps include determining the buffer size based on a first table having buffer size levels corresponding to a first buffer size field, In response to the indication that the first BSR format is unavailable, a step of determining the buffer size based on a second table having buffer size levels corresponding to a second buffer size field, wherein the first buffer size field is shorter than the second buffer size field; The step of sending a BSR based on the buffer size is included, A method in which the marking indicates that the first BSR format is available for a first logical channel group identifier and that the first BSR format is not available for a second logical channel group identifier.

13. The method according to claim 12, wherein the first buffer size field, or the second buffer size field, or both, determine the total amount of data available after the media access control packet data unit has been created, according to a data volume calculation procedure across the logical channels of the logical channel group.

14. Network equipment (NE) for wireless communications, At least one memory, The system comprises at least one processor coupled to the at least one memory, wherein the processor provides the NE, Send a BSR format indicator that should be used for the Buffer Status Report (BSR). The BSR is received according to the aforementioned BSR format. It is configured in such a way, The marking indicates that the first BSR format is available for a first logical channel group identifier and that the first BSR format is not available for a second logical channel group identifier. The buffer size is determined based on a first table having buffer size levels corresponding to a first buffer size field, in response to the indication that the first BSR format is available. The determination of the buffer size is performed based on a second table having buffer size levels corresponding to a second buffer size field, in response to the indication that the first BSR format is unavailable. NE where the first buffer size field is shorter than the second buffer size field.

15. The NE according to claim 14, wherein the first table has a 5-bit buffer size level and the second table has an 8-bit buffer size level.

16. A processor for wireless communication, It comprises at least one controller coupled to at least one memory, and the at least one controller provides the processor with To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, A processor in which the markings indicate that the first BSR format is available for a first logical channel group identifier and that the first BSR format is not available for a second logical channel group identifier.

17. The processor according to claim 16, wherein the first buffer size field, or the second buffer size field, or both, determine the total amount of data available after a medium access control packet data unit has been created, according to a data volume calculation procedure across the logical channels of a logical channel group.

18. The processor according to claim 16, wherein the marking is a wireless resource control marking.

19. A processor for wireless communication, It comprises at least one controller coupled to at least one memory, and the at least one controller provides the processor with To receive an indication of whether the first Buffer Status Report (BSR) format is available, In response to the indication that the first BSR format is available, the buffer size is determined based on a first table having buffer size levels corresponding to the first buffer size field. In response to the indication that the first BSR format is unavailable, the buffer size is determined based on a second table having buffer size levels corresponding to a second buffer size field, where the first buffer size field is shorter than the second buffer size field. Send a BSR based on the aforementioned buffer size. It is configured in such a way, A processor in which the indication is a media access control-control element indication or a downlink control information indication, and the indication is applicable for a certain period of time or until a timer expires.

20. The processor according to claim 16, wherein the first table has a 5-bit buffer size level and the second table has an 8-bit buffer size level.

21. The step of transmitting a BSR format marking to be used for a buffer status report (BSR), The steps of receiving a BSR according to the aforementioned BSR format and Includes, The marking indicates that the first BSR format is available for a first logical channel group identifier and that the first BSR format is not available for a second logical channel group identifier. The buffer size is determined based on a first table having buffer size levels corresponding to a first buffer size field, in response to the indication that the first BSR format is available. The determination of the buffer size is performed based on a second table having buffer size levels corresponding to a second buffer size field, in response to the indication that the first BSR format is unavailable. A method wherein the first buffer size field is shorter than the second buffer size field.

Images