[go: up one dir, main page]

WO2024209027A1 - Signalisation de réseau et configuration de rapport d'id de table de rapport d'état de tampon (bsr) pour des services à débit adaptatif - Google Patents

Signalisation de réseau et configuration de rapport d'id de table de rapport d'état de tampon (bsr) pour des services à débit adaptatif Download PDF

Info

Publication number
WO2024209027A1
WO2024209027A1 PCT/EP2024/059294 EP2024059294W WO2024209027A1 WO 2024209027 A1 WO2024209027 A1 WO 2024209027A1 EP 2024059294 W EP2024059294 W EP 2024059294W WO 2024209027 A1 WO2024209027 A1 WO 2024209027A1
Authority
WO
WIPO (PCT)
Prior art keywords
buffer size
network node
ids
configuration
bsr
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2024/059294
Other languages
English (en)
Inventor
Jose Luis Pradas
Du Ho Kang
Richard TANO
Fabian DE LAVAL
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2024209027A1 publication Critical patent/WO2024209027A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports

Definitions

  • the present disclosure relates to wireless communications, and in particular, to configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services in a wireless communication network.
  • BSR Buffer Status Report
  • ID Table Identity
  • the Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WDs) or user equipments (UEs), as well as communication between network nodes and between UEs.
  • the 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.
  • 5G is the fifth generation of mobile communications, addressing a wide range of use cases from enhanced mobile broadband (eMBB) to ultra-reliable low-latency communications (URLLC) to massive machine type communications (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communications
  • mMTC massive machine type communications
  • 5G includes the NR access stratum interface and the 5G Core Network (5GC).
  • the NR physical and higher layers reuse parts of the LTE specification, and add needed components when motivated by new use cases.
  • XR extended Reality
  • cloud gaming Low-latency high-rate applications such as extended Reality (XR) and cloud gaming are important in 5G era.
  • XR may refer to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables. It is an umbrella term for different types of realities including Virtual reality (VR), Augmented reality (AR), Mixed reality (MR), and the areas interpolated among them.
  • VR Virtual reality
  • AR Augmented reality
  • MR Mixed reality
  • the levels of virtuality range from partially sensory inputs to fully immersive VR.
  • 5G NR is designed to support applications demanding high rate and low latency in line with the requirements posed by the support of XR and cloud gaming applications in NR networks.
  • the objectives of a recent 3 GPP study on XR for NR include identifying the traffic model for each application of interest, the evaluation methodology and the key performance indicators of interest for relevant deployment scenarios, and to carry out performance evaluations accordingly in order to investigate possible standardization enhancements.
  • the low-latency applications like XR and cloud gaming may require bounded latency, not necessarily ultra-low latency.
  • the end-to-end latency budget may be in the range of 20-80 ms, which may need to be distributed over several components including application processing latency, transport latency, radio link latency, etc. For these applications, short transmission time intervals (TTIs) or mini-slots targeting ultra-low latency may not be effective.
  • TTIs transmission time intervals
  • mini-slots targeting ultra-low latency may not be effective.
  • FIG. 1 shows an example of frame latency measured over radio access network (RAN), excluding application & core network latencies. It may be seen that there exist frame latency spikes in RAN. The latency spike occurs due to instantaneous shortage of radio resources or inefficient radio resource allocation in response to varying frame size.
  • the sources for the latency spikes may include queuing delay, time-varying radio environments, time-varying frame sizes, among others. Tools that may help to remove latency spikes are beneficial to enable better 5G support for this type of traffic.
  • the typical frame sizes may range from tens of kilobytes to hundreds of kilobytes.
  • the frame arrival rates may be 60 or 120 frames per second (fps). As an example, a frame size of 100 kilobytes and a frame arrival rate of 120 fps may lead to a rate requirement of 95.8 Mbps.
  • FIG. 2 shows an example of the cumulative distribution functions of the number of transport blocks required to deliver a video frame with size ranging from 20 KB to 300 KB. For example, FIG. 2 shows that for delivering the frames with a size of 200 KB each, the median number of required TBs is 5.
  • XR traffic arrival may be distinct from typical web-browsing and voice over Internet protocol (VoIP) traffic, as shown in FIG. 3. It is expected that the arrival time is quasi-periodic and largely predictable as VoIP. However, its data size is an order of magnitude larger than VoIP, as discussed above. In addition, similar to webbrowsing, the data size may be different at every application protocol data unit (PDU) arrival instance due to dynamics of contents and human motion. Buffer status report in 5G
  • the UE reports to the network node the buffer status waiting for transmission in the Medium Access Control (MAC) Control Element (CE) Buffer Status Report (BSR).
  • MAC Medium Access Control
  • CE Control Element
  • BSR Buffer Status Report
  • Short BSR and Short truncated BSR are shown in FIG. 4 A.
  • Long BSR and Long truncated BSR are shown in FIG. 4B.
  • BSR regular BSR
  • periodic BSR periodic BSR
  • padding BSR padding BSR
  • the regular BSR is triggered if uplink (UL) data for a logical channel which belongs to a logical channel group (LCG) becomes available to the MAC entity; and either this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or none of the logical channels which belong to an LCG contains any available UL data.
  • UL uplink
  • LCG logical channel group
  • the user equipment uses the long BSR format and reports all LCGs which have data. However, if only one LCG has data, the short BSR format is used.
  • the periodic BSR is configured by the network node. When configured, the UE periodically reports the BSR. When more than one LCG has data available for transmission, then the UE uses the long BSR format and reports all LCGs which have data. However, if only one LCG has data, the short BSR format is used.
  • the padding BSR is an opportunistic arrangement that provides buffer status information to the network node when the medium access control (MAC) PDU would contain a number of padding bits equal or larger than one of the BSR formats.
  • the UE adds the padding BSR replacing the corresponding padding bits.
  • the BSR format to be used depends on the number of padding bits, the number of logical channels which have data for transmissions, and the size of the BSR format.
  • the short truncated BSR the long BSR, or the long truncated BSR.
  • the selection of the BSR format depends on the number of available padding bits.
  • the short BSR format is used.
  • one MAC PDU may contain at most one BSR MAC control element
  • Some embodiments advantageously provide methods, systems, and apparatuses for configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • BSR Buffer Status Report
  • ID Table Identity
  • RAN2 has considered the enhancement of existing buffer status report to support high data rate and low latency XR applications.
  • One or more additional BSR table(s) to reduce the quantization errors in BSR reporting (e.g., for high bit rates);
  • Delay knowledge of buffered data consisting of, e.g., remaining time, and distinguishing how much data is buffered for which delay. It is to be determined whether the delay information is reported as part of BSR or as a new MAC CE. Also, how the delay information may be up to date considering, e.g., scheduling and transmission delays needs to be investigated further.
  • Some approaches include a configurable BSR table where the key parameters, e.g., step size/min/max value of the buffer size range, are used to construct a BSR table that best reflects the range of application data size, e.g., video frame, depending on application configuration such as an encoding bit rate. Since it may be common that an application has a wide range of encoding bit rate, it may be a number of BSR tables generated, and a user equipment will choose the most optimal one out of the candidate BSR tables.
  • the key parameters e.g., step size/min/max value of the buffer size range
  • One way is that a user equipment dynamically indicates the BSR table ID in each BSR, where the table ID is chosen from the predetermined set of potential BSR tables.
  • the user equipment indication of the table ID may have a limited number of bits available in BSR format, e.g., 2 to 3 bits, so that only a few possibilities of BSR IDs may be chosen, e.g., 4 to 8 IDs.
  • BSR format e.g. 2 to 3 bits
  • BSR IDs e.g. 4 to 8 IDs.
  • a network e.g., via a network node, configures a user equipment (UE) with a subset of predetermined BSR table options so that the UE may report a chosen BSR table ID from the indicated the subset.
  • UE user equipment
  • a UE may be configured with the subset of BSR tables from which the UE selects one BSR table whose ID is reported in a BSR .
  • a network allows the flexible BSR table choice with the minimal signaling overhead
  • a UE may dynamically choose the most accurate BSR table to keep the highest accuracy of BSR while the application changes its bit rate.
  • a method in a network node configured to communicate with a user equipment, UE includes configuring the UE with a set of buffer size table configurations, each buffer size table configuration being identified by a table ID and including a step size, a minimum buffer size, and a maximum buffer size.
  • the method includes transmitting to the UE a set of table IDs, from which the UE is configured to select a buffer size table configuration.
  • the method also includes receiving from the UE a table ID corresponding to the buffer size table configuration selected by the UE.
  • the set of table IDs is a subset of the table IDs identifying the buffer size table configurations of the set of buffer size table configurations.
  • the received table ID is included in a buffer size table report received from the UE.
  • the set of table IDs transmitted to the UE is selected by the network node based at least in part on traffic characteristics.
  • the set of table IDs transmitted to the UE is selected by the network node based at least in part on an expected quantization error associated with each buffer size table configuration associated with a table ID in the set of table IDs.
  • the method includes configuring the UE with a default buffer size table configuration.
  • the set of table IDs is specific to a logical channel. In some embodiments, the set of table IDs is identified by a table group ID, each table group ID being associated with a different set of buffer size table configurations. In some embodiments, the method includes selecting a table ID from the set of table IDs that minimizes a quantization error associated with a buffer size table configuration.
  • a network node configured to communicate with a user equipment, UE, is provided. The network node is configured to configure the UE with a set of buffer size table configurations, each buffer size table configuration being identified by a table ID and including a step size, a minimum buffer size, and a maximum buffer size.
  • the network node is configured to transmit to the UE a set of table IDs, from which the UE is configured to select a buffer size table configuration.
  • the network node is also configured to receive from the UE a table ID corresponding to the buffer size table configuration selected by the UE.
  • the set of table IDs is a subset of the table IDs identifying the buffer size table configurations of the set of buffer size table configurations.
  • the received table ID is included in a buffer size table report received from the UE.
  • the set of table IDs transmitted to the UE is selected by the network node based at least in part on traffic characteristics.
  • the set of table IDs transmitted to the UE is selected by the network node based at least in part on an expected quantization error associated with each buffer size table configuration associated with a table ID in the set of table IDs.
  • the network node is configured to configure the UE with a default buffer size table configuration.
  • the set of table IDs is specific to a logical channel. In some embodiments, the set of table IDs is identified by a table group ID, each table group ID being associated with a different set of buffer size table configurations. In some embodiments, the network node is configured to select a table ID from the set of table IDs that minimizes a quantization error associated with a buffer size table configuration.
  • a method in a user equipment, UE, configured to communicate with a network node includes receiving a set of table IDs, each table ID identifying a buffer size table configuration, each buffer size table configuration including a step size, a minimum buffer size, and a maximum buffer size.
  • the method includes selecting a buffer size table configuration from a set of buffer size table configurations identified by the set of table IDs.
  • the method also includes transmitting a table ID corresponding to the selected buffer size table configuration.
  • the transmitted table ID is included in a buffer size table report.
  • selecting the buffer size table configuration is based at least in part on a quantization error associated with the buffer size table configuration.
  • the method includes transmitting a capability report indicating a number of supportable buffer size table configurations. In some embodiments, the method includes transmitting a capability report indicating supportable values for step size, minimum buffer size and maximum buffer size.
  • a user equipment configured to communicate with a network node.
  • the UE is configured to receive a set of table IDs, each table ID identifying a buffer size table configuration, each buffer size table configuration including a step size, a minimum buffer size, and a maximum buffer size.
  • the UE is configured to select a buffer size table configuration from a set of buffer size table configurations identified by the set of table IDs.
  • the UE is also configured to transmit a table ID corresponding to the selected buffer size table configuration.
  • the transmitted table ID is included in a buffer size table report.
  • selecting the buffer size table configuration is based at least in part on a quantization error associated with the buffer size table configuration.
  • the UE is configured to transmit a capability report indicating a number of supportable buffer size table configurations.
  • the UE is configured to transmit a capability report indicating supportable values for step size, minimum buffer size and maximum buffer size.
  • FIG. 1 is an example diagram of frame latency measured over radio access network (RAN);
  • RAN radio access network
  • FIG. 2 is an example diagram of cumulative distribution functions
  • FIG. 3 is an example diagram of XR traffic characteristics compared to VoIP and Web-browsing
  • FIG. 4A is an example diagram of Short BSR and Short truncated BSR
  • FIG. 4B is an example diagram of Long BSR and Long truncated BSR
  • FIG. 5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 6 is a block diagram of a host computer communicating via a network node with a user equipment over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a user equipment for executing a client application at a user equipment according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a user equipment for receiving user data at a user equipment according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a user equipment for receiving user data from the user equipment at a host computer according to some embodiments of the present disclosure
  • FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a user equipment for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 11 is a flowchart of an example process in a network node according to some embodiments of the present disclosure.
  • FIG. 12 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure.
  • FIG. 13 is a flowchart of an example process in a network node according to some embodiments of the present disclosure.
  • FIG. 14 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure.
  • FIG. 15 is a diagram of a table ID according to some embodiments of the present disclosure.
  • FIG. 16 is a diagram of a BSR report according to some embodiments of the present disclosure. DETAILED DESCRIPTION
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node may be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (
  • BS base station
  • wireless device or a user equipment (UE) are used interchangeably.
  • the UE herein may be any type of wireless device capable of communicating with a network node or another UE over radio signals, such as wireless device (WD).
  • the UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and/or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • LME laptop mounted equipment
  • CPE Customer Premises Equipment
  • NB-IOT Narrowband loT
  • radio network node may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node IAB node
  • relay node relay node
  • access point radio access point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • the general description elements in the form of “one of A and B” corresponds to A or B.
  • at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B .
  • at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof.
  • functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and/or network nodes.
  • the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.
  • a buffer status report may be referred to as a buffer size table report and a buffer status configuration may be referred to as a buffer size table configuration.
  • Some embodiments provide for configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • BSR Buffer Status Report
  • ID Table Identity
  • FIG. 5 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as UEs 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.
  • a UE 22 may be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a UE 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • UE 22 may be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 5 as a whole enables connectivity between one of the connected UEs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected UEs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected UE 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the UE 22a towards the host computer 24.
  • a network node 16 is configured to include a configuration unit 32, which is configured to perform one or more network node 16 functions described herein, including functions related to configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • BSR Buffer Status Report
  • ID Table Identity
  • a user equipment 22 is configured to include an implementation unit 34, which is configured to perform one or more user equipment 22 functions described herein, including functions related to configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a UE 22 connecting via an OTT connection 52 terminating at the UE 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the user equipment 22.
  • the processing circuitry 42 of the host computer 24 may include a control unit 54 configured to enable the service provider to observe/monitor/ control/transmit to/receive from the network node 16 and/or the user equipment 22.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the UE 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a UE 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include configuration unit 32 configured to perform one or more network node 16 functions described herein, including functions related to configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • BSR Buffer Status Report
  • ID Table Identity
  • the communication system 10 further includes the UE 22 already referred to.
  • the UE 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the UE 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the UE 22 may further comprise software 90, which is stored in, for example, memory 88 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the UE 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the UE 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by UE 22.
  • the processor 86 corresponds to one or more processors 86 for performing UE 22 functions described herein.
  • the UE 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to UE 22.
  • the processing circuitry 84 of the user equipment 22 may include an implementation unit 34 configured to perform one or more user equipment 22 functions described herein, including functions related to configuration of a Buffer Status Report (BSR) Table Identity (ID) for rate adaptive services.
  • BSR Buffer Status Report
  • ID Table Identity
  • the inner workings of the network node 16, UE 22, and host computer 24 may be as shown in FIG. 6 and independently, the surrounding network topology may be that of FIG. 5.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the user equipment 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the UE 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the UE 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the UE 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the UE 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a UE 22 to a network node 16.
  • the UE 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.
  • FIGS. 5 and 6 show various “units” such as configuration unit 32, and implementation unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 5 and 6, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a UE 22, which may be those described with reference to FIG. 6.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the UE 22 (Block SI 04).
  • the network node 16 transmits to the UE 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the UE 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a UE 22, which may be those described with reference to FIGS. 5 and 6.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the UE 22 (Block SI 12).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 9 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a UE 22, which may be those described with reference to FIGS. 5 and 6.
  • the UE 22 receives input data provided by the host computer 24 (Block SI 16).
  • the UE 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the UE 22 provides user data (Block S120).
  • the UE 22 provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the UE 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the UE 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 10 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 5, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a UE 22, which may be those described with reference to FIGS. 5 and 6.
  • the network node 16 receives user data from the UE 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • FIG. 11 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 is configured to configure the user equipment 22 with a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters (Block SI 34).
  • Network node 16 is configured to communicate with the user equipment 22 using a selected one of the subset of BSR table IDs selected by the user equipment (Block S136).
  • the selected one of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • the subset of the plurality of predetermined BSR table IDs is determined based on capabilities of the user equipment.
  • the subset of BSR table IDs is grouped into one or more table group IDs.
  • FIG. 12 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the implementation unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Wireless device 22 is configured to receive an indication of a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters (Block S138).
  • Wireless device 22 is configured to select at least one BSR table ID of the subset of BSR table IDs for communication with a network node (Block S140).
  • the selected one of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • the subset of the plurality of predetermined BSR table IDs is determined based on capabilities of the user equipment. In at least one embodiment, the subset of BSR table IDs is grouped into one or more table group IDs.
  • FIG. 13 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60.
  • Network node 16 is configured to configure the UE 22 with a set of buffer size table configurations, each buffer size table configuration being identified by a table ID and including a step size, a minimum buffer size, and a maximum buffer size (Block S142).
  • the method includes transmitting to the UE 22 a set of table IDs, from which the UE 22 is configured to select a buffer size table configuration (Block S144).
  • the method also includes receiving from the UE 22 a table ID corresponding to the buffer size table configuration selected by the UE 22 (Block S146).
  • the set of table IDs is a subset of the table IDs identifying the buffer size table configurations of the set of buffer size table configurations.
  • the received table ID is included in a buffer size table report received from the UE 22.
  • the set of table IDs transmitted to the UE 22 is selected by the network node based at least in part on traffic characteristics.
  • the set of table IDs transmitted to the UE 22 is selected by the network node based at least in part on an expected quantization error associated with each buffer size table configuration associated with a table ID in the set of table IDs.
  • the method includes configuring the UE 22 with a default buffer size table configuration.
  • the set of table IDs is specific to a logical channel. In some embodiments, the set of table IDs is identified by a table group ID, each table group ID being associated with a different set of buffer size table configurations. In some embodiments, the method includes selecting a table ID from the set of table IDs that minimizes a quantization error associated with a buffer size table configuration.
  • FIG. 14 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure.
  • One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 84 (including the implementation unit 34), processor 86, radio interface 82 and/or communication interface 60.
  • Wireless device 22 is configured to receive a set of table IDs, each table ID identifying a buffer size table configuration, each buffer size table configuration including a step size, a minimum buffer size, and a maximum buffer size (Block S148).
  • the method includes selecting a buffer size table configuration from a set of buffer size table configurations identified by the set of table IDs (Block SI 50).
  • the method also includes transmitting a table ID corresponding to the selected buffer size table configuration (Block SI 52).
  • the transmitted table ID is included in a buffer size table report.
  • selecting the buffer size table configuration is based at least in part on a quantization error associated with the buffer size table configuration.
  • the method includes transmitting a capability report indicating a number of supportable buffer size table configurations. In some embodiments, the method includes transmitting a capability report indicating supportable values for step size, minimum buffer size and maximum buffer size.
  • BSR Buffer Status Report
  • ID Table Identity
  • One or more user equipment (UE) 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, implementation unit 34, etc.
  • One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, configuration unit 32, etc.
  • a network such as via a network node 16, constructs multiple BSR tables in a certain way based on key parameters.
  • a linearly stepped BSR table may be considered.
  • a minimum buffer size Bmin, the step size S, and a maximum buffer size Bmax are used to build a different BSR table.
  • Each set of BSR parameters may be assigned a table ID. It is also possible that the list of tables below may be predetermined.
  • the reported B SR in a UE 22 may include a table ID information so that a network node 16 knows which BSR table is considered to choose a buffer size index.
  • FIG. 15 illustrates the table ID of two bits appended in each Buffer size index.
  • a network such as via a network node 16, indicates to a UE 22 the set of possible Table IDs from which the UE 22 may choose. This will be a subset of the predetermined table IDs.
  • the network e.g., via the network node 16, may indicate maxNrOfTablelD number of Table IDs from M pre-determined table ID list (M greater or equal to maxNrOfTablelD).
  • M pre-determined table ID list
  • a network e.g., via a network node 16, may send a list of table IDs in new information element (IE) bsrFeasibleTablelDs in BSR- config as below.
  • IE new information element
  • a UE 22 may not use any table IDs reported or may not be allowed to report a table ID from any value in the predetermined table ID list.
  • Default behavior of UE 22 may be configured by the network.
  • BSR-Config :: SEQUENCE ⁇ periodicBSR-Timer ENUMERATED ⁇ sfl, sf5, sflO, sfl 6, sf20, sf32, sf40, sf64, sf80, sfl28, sfl 60, sf320, sf640, sfl280, sf2560, infinity ⁇ , retxBSR-Timer ENUMERATED ⁇ sflO, sf20, sf40, sf80, sfl 60, sf320, sf640, sf!280, sf2560, sf5120, sfl 0240, spare5, spare4, spare3, spare2, sparel ⁇ , logicalChannelSR-Delay Timer ENUMERATED ⁇ sf2O, sf40, sf64, sfl 28, sf512, sfl 024, sf2560,
  • bsrFeasibleTablelDs may be indicated per logical channel identity (LCID) or LCG so that a different Table IDs may be selected by a UE 22 depending on LCID or LCG. If the UE 22 reports in the BSR the table index, the UE 22 may report the index that the network allocated to the table ID rather than the table ID as it was pre-defined. In other words, if the network, e.g., via a network node 16, may assign four tables to the UE 22, these four tables could have IDs 30, 55, 78, 99, for instance. When the UE 22 uses table ID 30, then the UE 22 may indicate in the BSR table 1, if this index was assigned for the table.
  • LCID logical channel identity
  • LCG LCG
  • a table group ID of each subset of all possible configured tables are assigned by a network, e.g., via a network node 16, or are predetermined.
  • a network e.g., via a network node 16
  • the Table group ID includes one or more table IDs. This may be less flexible than a subset indication of table IDs, but it requires less signaling overhead.
  • the table group ID may be signaled by higher layers, e.g., radio resource control (RRC) or MAC CE.
  • RRC radio resource control
  • MAC CE MAC CE
  • a UE 22 when a UE 22 receives the subset of table IDs or the table group ID, it refers to the tables belonging to the indicated table IDs. Then, it chooses one specific table ID from the indicated table IDs whenever it reports BSR. The chosen table ID may be added in the BSR. The same procedure may be repeated for all other LCGs or LCIDs if the table IDs are provided per LCID or LCG. Then, an example of BSR report with table ID per LCG is illustrated in FIG. 16.
  • the UE 22 may signal its capability to support multiple configurable table IDs. It may also signal the maximum number of configurable table IDs it may support. It may also signal the possible values of Bmin, Bmax and Stepsize that the network may configure.
  • the capability information may be sent as a part of the UECapabilitylnformation RRC message.
  • Some embodiments may include one or more of the following: Embodiment Al .
  • a network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: configure the wireless device with a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters; and communicate with the wireless device using a selected one of the subset of BSR table IDs selected by the wireless device.
  • WD wireless device
  • processing circuitry configured to: configure the wireless device with a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters; and communicate with the wireless device using a selected one of the subset of BSR table IDs selected by the wireless device.
  • Embodiment A2 The network node of Embodiment Al, wherein the selected one of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • Embodiment A3 The network node of Embodiment Al, wherein the subset of the plurality of predetermined BSR table IDs is determined based on capabilities of the wireless device.
  • Embodiment A4 The network node of any one of Embodiments A1-A3, wherein the subset of BSR table IDs is grouped into one or more table group IDs.
  • Embodiment Bl A method implemented in a network node, the method comprising: configuring a wireless device with a subset of a plurality of predetermined buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters; and communicating with the wireless device using a selected one of the subset of BSR tables selected by the wireless device.
  • Embodiment B2 The method of Embodiment Bl, wherein the selected one of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • Embodiment B3 The method of Embodiment B 1 , wherein the subset of the plurality of predetermined BSR table IDs is determined based on capabilities of the wireless device.
  • Embodiment B4 The method of any one of Embodiments B1-B3, wherein the subset of BSR table IDs is grouped into one or more table group IDs.
  • a wireless device configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive an indication of a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters; and select at least one BSR table ID of the subset of BSR table IDs for communication with the network node.
  • Embodiment C2 The WD of Embodiment Cl, wherein the selected at least one BSR table ID of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • Embodiment C3 The WD of Embodiment Cl, wherein the selected at least one BSR table ID of the subset of BSR table IDs is determined based on capabilities of the wireless device.
  • Embodiment C4 The WD of any one of Embodiments C1-C3, wherein the subset of BSR table IDs is grouped into one or more table group IDs.
  • Embodiment DI A method implemented in a wireless device (WD), the method comprising: receiving an indication of a subset of a plurality of buffer status report, BSR, table identities, IDs, each of the subset of BSR table IDs corresponding to a set of buffer parameters; and selecting at least one BSR table ID of the subset of BSR table IDs for communication with a network node.
  • Embodiment D2 The method of Embodiment DI, wherein the selected at least one BSR table ID of the subset of BSR table IDs is selected based on at least one of a logical channel identity, LCID, and a logical channel group.
  • Embodiment D3 The method of Embodiment DI, wherein the selected at least one BSR table ID of the subset of BSR table IDs is determined based on capabilities of the wireless device.
  • Embodiment D4 The method of any one of Embodiments D1-D3, wherein the subset of BSR table IDs is grouped into one or more table group IDs.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé, un système et un appareil sont divulgués. Dans au moins un mode de réalisation, un nœud de réseau est configuré pour communiquer avec un équipement d'utilisateur (UE). Selon un aspect, un procédé dans un nœud de réseau consiste à configurer l'UE avec un ensemble de configurations de table de taille de tampon, chaque configuration de table de taille de tampon étant identifiée par un ID de table et comprenant une taille de pas, une taille de tampon minimale et une taille de tampon maximale. Le procédé consiste à transmettre à l'UE un ensemble d'ID de table, à partir desquels l'UE est configuré pour sélectionner une configuration de table de taille de tampon. Le procédé consiste en outre à recevoir de la part de l'UE un ID de table correspondant à la configuration de table de taille de tampon sélectionnée par l'UE.
PCT/EP2024/059294 2023-04-06 2024-04-05 Signalisation de réseau et configuration de rapport d'id de table de rapport d'état de tampon (bsr) pour des services à débit adaptatif Pending WO2024209027A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363494582P 2023-04-06 2023-04-06
US63/494,582 2023-04-06

Publications (1)

Publication Number Publication Date
WO2024209027A1 true WO2024209027A1 (fr) 2024-10-10

Family

ID=90720465

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/059294 Pending WO2024209027A1 (fr) 2023-04-06 2024-04-05 Signalisation de réseau et configuration de rapport d'id de table de rapport d'état de tampon (bsr) pour des services à débit adaptatif

Country Status (1)

Country Link
WO (1) WO2024209027A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034537A1 (fr) * 2020-08-12 2022-02-17 Telefonaktiebolaget Lm Ericsson (Publ) Format de rapport d'état de mémoire tampon, table et procédés pour des services de réalité augmentée

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034537A1 (fr) * 2020-08-12 2022-02-17 Telefonaktiebolaget Lm Ericsson (Publ) Format de rapport d'état de mémoire tampon, table et procédés pour des services de réalité augmentée

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CHUNLI WU ET AL: "Capacity improvements", vol. 3GPP RAN 2, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), XP052246151, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_121/Docs/R2-2301517.zip R2-2301517 Capacity Improvements.docx> [retrieved on 20230217] *
ERICSSON: "Discussion on BSR enhancements for XR", vol. RAN WG2, no. e-meeting; 20230417 - 20230426, 6 April 2023 (2023-04-06), XP052365980, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_121bis-e/Docs/R2-2303721.zip R2-2303721 - Discussion on BSR enhancements for XR.docx> [retrieved on 20230406] *
LG ELECTRONICS INC: "BSR format for CA", 3GPP DRAFT; R2-103938 BSR FORMAT FOR CA, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Stockholm, Sweden; 20100628 - 20100702, 22 June 2010 (2010-06-22), XP050605241 *
RICHARD TANO ET AL: "Discussion on BSR enhancements for XR", vol. 3GPP RAN 2, no. Incheon, KR; 20230522 - 20230526, 11 May 2023 (2023-05-11), XP052315047, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_122/Docs/R2-2305828.zip R2-2305828 - Discussion on BSR enhancements for XR.docx> [retrieved on 20230511] *
RICHARD TANO ET AL: "Discussion on XR-specific capacity improvements", vol. 3GPP RAN 2, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), XP052246141, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG2_RL2/TSGR2_121/Docs/R2-2301507.zip R2-2301507 - Discussion on XR-specific capacity improvements.docx> [retrieved on 20230217] *

Similar Documents

Publication Publication Date Title
US11889342B2 (en) Method and apparatus for quality of service management
US10827501B2 (en) Techniques for providing proximity services (ProSe) priority-related information to a base station in a wireless network
US10660118B2 (en) Logical channel priority reconfiguration for MAC-CES in NR
US20220022093A1 (en) Method and apparatus for buffer status report enhancement
US20200008250A1 (en) Wireless Connection Establishment Method And Apparatus
RU2736577C1 (ru) Профили передачи для nr
JP7488377B2 (ja) マルチキャスト通信のための方法および装置
US11716739B2 (en) Method and apparatus for uplink transmission
EP4458085A1 (fr) Conception de bsr sensible au retard pour applications xr
US20250126614A1 (en) Managing configured grants for xr applications
AU2017253580A1 (en) A radio network node, a wireless device and methods therein for reference signal configuration
US20240121666A1 (en) Method and apparatus for flow control
US12273284B2 (en) Network slicing in cellular systems
US12245263B2 (en) Semi-persistent scheduling for multiple services
US20250113363A1 (en) Skipping transmission of uplink control information
WO2024209095A1 (fr) Abandon d&#39;ensemble d&#39;unités de données de protocole (pdu) sur la base d&#39;une signalisation d&#39;importance d&#39;ensemble de pdu (psi), configuration et comportement d&#39;équipement utilisateur (ue)
WO2024096788A1 (fr) Dispositif sans fil et nœud de réseau pour saut flexible d&#39;occasions de mesure
US20200359410A1 (en) Method and apparatus for adaptive scheduling and transmission
CN115811706B (zh) 信道状态参数的传输方法和通信装置
WO2024209027A1 (fr) Signalisation de réseau et configuration de rapport d&#39;id de table de rapport d&#39;état de tampon (bsr) pour des services à débit adaptatif
EP3854163B1 (fr) Procédé et appareil pour un contrôle adaptatif de priorité entre des informations de commande et des données utilisateur
WO2025172863A1 (fr) Gestion de calculs pour un volume tampon critique de retard
JP2025529651A (ja) サイドリンク同一チャネル共存リソース選択情報共有のための通信装置、通信方法及び集積回路
CN117560112A (zh) 一种信息传输方法、装置及通信设备
CN119383658A (zh) 一种数据传输方法、装置及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24718124

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE