Mobile device, access network node and method

Abstract

The present disclosure relates to a method for a user equipment (UE), the method comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; and determining, based on an amount of uplink data in one or more buffers of the UE, whether to use the first table to determine a first index indicating the first range of amounts of uplink data in one or more buffers of the UE or to use the second table to determine a second index indicating a second range of amounts of uplink data in one or more buffers of the UE; determining the first index or the second index based on an amount of uplink data in one or more buffers of a UE; sending an indication of the first index or the second index to the access network node; if the UE sends the indication of the first index to the access network node, sending an indication to the access network node indicating that the first table was used to generate the first index; and if the UE sends an indication of the second index to the access network node, sending an indication to the access network node indicating that the second table was used to generate the second index.

Description

[Technical Field]

[0001] The present invention relates to communication systems. [Background technology]

[0002] This disclosure is particularly relevant, but not limited to, to wireless communication systems and devices thereof that operate in accordance with 3rd Generation Partnership Project (3GPP®) standards or equivalents or derivatives thereof (including LTE-Advanced, Next Generation, or 5G networks, future generations, and beyond). This disclosure is particularly relevant, but not limited to, to improvements relating to buffer status reporting (BSR) in so-called "5G" or "New Radio" systems (also referred to as "Next Generation" systems) and similar systems.

[0003] Recent developments in 3GPP standards are referred to as the Long-Term Evolution (LTE) of the Evolved Packet Core (EPC) network and the Evolved Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (E-UTRAN), commonly referred to as "4G." Furthermore, the terms "5G" and "New Radio" (NR) refer to evolved communications technologies that are expected to support a variety of applications and services. Various details of 5G networks are described, for example, in the "NGMN 5G White Paper" V1.0 by the Next Generation Mobile Networks (NGMN) Alliance, available at https: / / www.ngmn.org / 5g-white-paper.html. 3GPP plans to support 5G through the so-called 3GPP Next Generation (NextGen) radio access network (RAN) and 3GPP NextGen Core network.

[0004] In 3GPP standards, a NodeB (or eNB in ​​LTE, gNB in ​​5G) is a radio access network (RAN) node (or simply "access node," "access network node," or "base station") through which communication devices (user equipment, or "UE") connect to the core network and communicate with other communication devices and remote servers. For simplicity, this application uses the terms RAN node, base station, or access network node to refer to such access nodes collectively.

[0005] The International Telecommunication Union (ITU) classifies next-generation mobile networks into three categories: Enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low-Latency Communications (URLLC), and Massive Machine-Type Communications (mMTC), which support diverse service requirements. eMBB aims to provide enhanced support for traditional mobile broadband and focuses on services requiring large-scale, guaranteed bandwidth, such as High Definition (HD) video, Virtual Reality (VR), and Augmented Reality (AR). URLLC is a requirement for critical applications that require guaranteed access within very short timeframes, such as autonomous driving and factory automation. MMTC must support a large number of connected devices, such as smart meters and environmental monitoring, but can usually tolerate some access latency. It will be understood that some of these applications may have relatively relaxed Quality of Service / Quality of Experience (QoS / QoE) requirements, while some applications may have relatively stringent QoS / QoE requirements (e.g., high bandwidth and / or low latency).

[0006] The term eXtended Reality (XR) refers to all combined real and virtual environments generated by computer technology and wearables, and related human-machine interactions. This includes representative forms such as Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR), as well as the interpolated areas between them. 3GPP Technical Report (TR) 26.928 V16.1.0 describes eXtended Reality (XR) in the context of 5G wireless and network services. This document introduces baseline technologies for XR-type services and applications, outlines Quality of Experience (QoE) / Quality of Service (QoS) issues for XR-based services, the delivery of XR in 5G systems, and the architectural model for 5G media streaming defined in 3GPP TS 26.501 V16.9.0. In addition to traditional service categories, interactive, streaming, download, and split computing / rendering are identified as new delivery categories for XR. 3GPP TR 38.838 V17.0.0 is a study on XR services, particularly on traffic model and characteristic aspects of XR in Release 17.

[0007] A Buffer Status Report (BSR) is sent from a UE to a base station to indicate the amount of data stored in the UE's buffer for uplink transmission. This information can be used by the base station to schedule the uplink resources that the UE will use to transmit the stored data. The BSR may contain several bits indicating a logical channel (LCH) or logical channel group (LCG) and several bits indicating the corresponding buffer size in the UE. Summary of the Invention [Problem to be solved by the invention]

[0008] XR implementations, given challenging service requirements, require more efficient resource scheduling and allocation. The inventors have discovered that more reliable and accurate buffer status reporting is necessary because a more accurate BSR enables the network to more efficiently schedule uplink communication resources for transmission of uplink data from the UE. However, current buffer status reporting uses a lookup table and corresponding index to indicate the amount of uplink data in the UE's buffer, which has the problem that the accuracy of indicating the amount of uplink data stored in the buffer depends on the reported buffer size. It is desirable for the UE's buffer estimate to be more accurate and closer to the actual UE buffer value, which improves network efficiency and reduces resource utilization (e.g., uplink radio resources), particularly for resource-intensive applications such as XR.

[0009] Furthermore, there is also the issue that BSR transmission is not always reliably triggered. For example, in the case of Regular BSR, the arrival of additional data in the buffer of the same LCH or LCG may not trigger BSR transmission. Similarly, in the case of Padding BSR (included in uplink data messages if the message has sufficient padding bits), the BSR has lower priority than data transmission, and is not included in the transmission unless there are sufficient padding bits, resulting in a problem of not being reliably transmitted to the base station. In the case of Periodical (or Periodic) BSR, there is the issue that BSR transmission frequency may be insufficient (e.g., in the case of burst data arrival), and configuring a periodic BSR with a very short period may be impractical (e.g., inefficient).

[0010] More generally, there is a need for improved mechanisms that provide more accurate and precise BSRs that can be transmitted reliably and efficiently from a UE to a base station. [Means for solving the problem]

[0011] SUMMARY OF THE DISCLOSURE Accordingly, it is an object of the present disclosure to provide a method and associated apparatus that addresses or at least alleviates (at least some of) the above-mentioned problems.

[0012] In one aspect, the present disclosure provides a method for a user equipment (UE), the method comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; determining, based on an amount of uplink data in one or more buffers of the UE, whether to use the first table to determine a first index indicating a first range of amounts of uplink data in one or more buffers of the UE or to use the second table to determine a second index indicating a second range of amounts of uplink data in one or more buffers of the UE; determining the first index or the second index based on an amount of the uplink data in one or more buffers of the UE; sending an indication of the first index or the second index to an access network node; if the UE sends the indication of the first index to the access network node, sending an indication to the access network node indicating that the first table was used to generate the first index; and if the UE sends an indication of the second index to the access network node, sending an indication to the access network node indicating that the second table was used to generate the second index.

[0013] The method may include receiving the second table or information for generating the second table at the UE from the access network node.

[0014] The method may include determining to use the first table to determine the first index if an amount of the uplink data in one or more buffers of a UE is within a first range, and determining to use the second table to determine the second index if the amount of the uplink data in one or more buffers of a UE is within a second range.

[0015] The method may include determining whether to use the first table to determine the first index or the second table to determine the second index based on a comparison of an amount of the uplink data in one or more buffers of a UE to a threshold.

[0016] The first index may indicate a first range of an amount of the uplink data in the one or more buffers of a UE, and the second index may indicate a second range of an amount of the uplink data in the one or more buffers of a UE, and the method may include sending an indication of the first index to a base station if the first range is smaller than the second range, and sending the indication of the second index to the base station if the second range is smaller than the first range.

[0017] Transmitting the indication of the first index or the second index may include transmitting the indication of the first index or the second index in a buffer status report (BSR).

[0018] The indication indicating that the first table was used to generate the first index or the indication indicating that the second table was used to generate the second index may be provided in a medium access control (MAC) control element (CE).

[0019] The method may include sending an indication of a logical channel identity (LCID) to the access network node, the LCID indicating a format of a message used to send the indication of the first index or the second index to the access network node.

[0020] The indication that the first table was used to generate the first index may be provided using a set of one or more bits adjacent to a set of one or more bits used to indicate the first index in the transmission of the indication to the access network node, or the indication that the second table was used to generate the second index may be provided using a set of one or more bits adjacent to a set of one or more bits used to indicate the second index in the transmission of the indication to the access network node.

[0021] The indication that the first table was used to generate the first index or the indication that the second table was used to generate the second index may be provided using one or more bits in a subheader.

[0022] The subheader may be a subheader associated with a medium access control (MAC) control element (CE).

[0023] The method may include determining to use the first table to determine the first index based on a first amount of uplink data in one or more buffers of a UE, determining the first index based on the first amount of uplink data; determining to use the second table to determine the second index based on a second amount of uplink data in one or more buffers of the UE, determining the second index based on the second amount of uplink data; sending an indication of the first index and an indication of the second index to the access network node; sending an indication indicating that the first table was used to generate the first index; and sending an indication indicating that the second table was used to generate the second index.

[0024] One or more bits used to indicate that the first table was used to generate the first index may be adjacent to one or more bits used to indicate that the second table was used to generate the second index.

[0025] In another aspect, the present disclosure provides a method for a user equipment (UE), the method comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE; receiving from an access network node a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE, and if the second table is stored in the UE, determining an index indicating a range of an amount of uplink data in the one or more buffers using the first table or the second table based on the amount of uplink data in the one or more buffers of the UE; sending an indication of the first index or the second index to the access network node in a buffer status report having a first format including an indication of whether a second table was used to determine the index; or, in a second case where the UE has not received a second table or information for generating a second table from the access network node or the second table is not stored in the UE, determining the index using the first table based on an amount of uplink data in the one or more buffers of the UE, and sending an indication of the index to the access network node in a buffer status report having a second format, the second format being different from the first format.

[0026] Sending the indication of the index may include sending the indication of the index to the access network node in a medium access control (MAC) control element (CE).

[0027] The first format may be a first MAC CE format of the MAC CE, and the second format may be a second MAC CE format of the MAC CE.

[0028] The method further includes transmitting a subheader including the MAC CE to the access network node, wherein a subheader format of the subheader used for the first MAC CE format may be the same as a subheader format used for the second MAC CE format.

[0029] The UE may transmit all buffer status reports using the first format in the first case.

[0030] In the first case, the use of the first format may be based on control signaling received from the access network node.

[0031] The control signaling may include an activation signal indicating that the first format is activated or a setup message for the second table, and the method may include, in the first case, determining to send the indication of the index to the access network node in a buffer status report having the first format based on receiving the activation signal or the setup message for the second table.

[0032] The control signaling may include a deactivation signal indicating that the first format is to be deactivated or a release message for the second table, and the method may include, in a first case, determining, based on receiving the deactivation signal or the release message for the second table, to send the indication of the index to the access network node in a buffer status report having the second format.

[0033] In another aspect, the present disclosure provides a method for a user equipment (UE), the method including: storing a first table, for an amount of uplink data within a first range, mapping each of a plurality of first indexes to a respective sub-range of the first range; and storing a second table, for an amount of uplink data within a second range, mapping each of a plurality of second indexes to a respective sub-range of the second range, wherein each of the plurality of first indexes is different from each of the plurality of second indexes; the method further including: if an amount of uplink data in one or more buffers of the UE is within the second range, transmitting to the access network node an index of the plurality of second indexes indicating the sub-range of the amount of uplink data in one or more buffers of the UE; and if the amount of uplink data in one or more buffers of the UE is within the first range but not within the second range, transmitting to the access network node the index of the plurality of first indexes indicating the sub-range of the amount of uplink data in one or more buffers of the UE.

[0034] The second range may be a subset of the first range.

[0035] The number of the first indexes in the first table may be different from the number of the second indexes in the second table.

[0036] At least one sub-range mapped to an index in the second table may be smaller than the sub-range mapped to an index in the first table.

[0037] In another aspect, the present disclosure provides a method for a user equipment (UE), the method including: storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data and a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data; receiving table activation information from an access network node indicating whether the second table is activated in the UE; if the table activation information indicates that the second table is activated in the UE, determining to use the second table to determine an index of the second plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; and sending an indication of the index to the access network node.

[0038] The method may further include receiving table activation information from the access network node indicating that the second table is to be deactivated at the UE; determining to use the first table based on the indication indicating that the second table is to be deactivated at the UE to determine an index of the first plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; and sending an indication of the index to the access network node.

[0039] In another aspect, the present disclosure provides a method for a user equipment (UE), the method including: storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data; receiving table setup information from an access network node for a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data; determining, based on the table setup information, to use the second table to determine an index of the second plurality of indexes that indicates a range of an amount of uplink data in one or more buffers of the UE; and transmitting an indication of the index to the access network node.

[0040] The method may further include receiving table release information from an access network node indicating that the second table is to be released; determining, based on the table release information, to use the first table to determine an index of the first plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; and sending an indication of the index to the access network node.

[0041] The table setup information may include the second table or information for generating the second table at the UE.

[0042] In another aspect, the present disclosure provides a method for a user equipment (UE), the method including storing a table mapping each of a plurality of indexes to a respective range of uplink data, wherein a first index of the plurality of indexes is mapped to a first range of uplink data, a second index of the plurality of indexes is mapped to a second range of uplink data, and a third index of the plurality of indexes is mapped to a third range of uplink data, the first range and the third range being smaller than the second range, an upper limit of the first range being smaller than a lower limit of the second range, and an upper limit of the second range being smaller than a lower limit of the third range, the method further including determining the index of the table indicative of the range of an amount of the uplink data in one or more buffers of the UE based on an amount of uplink data in one or more buffers of the UE, and transmitting the index to an access network node.

[0043] In another aspect, the present disclosure provides a method of an access network node, the method comprising: assigning each of a plurality of second indexes to a user equipment (UE). transmitting to the UE a second table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data in one or more buffers of a user equipment (UE), or information for generating the second table at the UE; receiving from the UE an indication of an index indicating a range of amounts of uplink data in one or more buffers of the UE; if the index is an index determined using a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data in one or more buffers of the UE, receiving from the UE an indication indicating that the first table was used to generate the index and determining the range of amounts of uplink data in one or more buffers of the UE using the first table; if the index is an index determined using the second table, receiving from the UE an indication indicating that the second table was used to generate the index and determining the range of amounts of uplink data in one or more buffers of the UE using the index and the second table.

[0044] In another aspect, the present disclosure provides a method of an access network node, the method comprising: the access network node transmitting each of a plurality of second indexes to a user equipment (UE); and receiving an indication of an index in a buffer status report from the UE in a first case where the access network node transmits to the UE a second table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, or the access network node transmits information for generating the second table at the UE and the second table is stored in the UE, the buffer status report having a first format including an indication of whether the first table or the second table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE was used to determine the index; or receiving an indication of the index in a buffer status report having a second format different from the first format in a second case where the base station has not transmitted to the UE the second table or the information for generating the second table or the second table is not stored in the UE.

[0045] In another aspect, the present disclosure provides a method in an access network node, the method including: transmitting table activation information to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, the table activation information indicating whether to activate a second table in the UE that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in the one or more buffers of the UE; receiving from the UE an indication of an index that indicates the range of an amount of the uplink data in the one or more buffers of the UE; and determining the range of an amount of the uplink data in the one or more buffers of the UE using the index and the second table.

[0046] The method may further include transmitting table activation information to the UE indicating that the second table is deactivated at the UE; receiving an indication of an index from the UE indicating the range of an amount of uplink data in the one or more buffers of the UE; and determining the range of an amount of uplink data in the one or more buffers of the UE using the index and the first table.

[0047] In another aspect, the present disclosure provides a method in an access network node, the method including: transmitting table setup information for a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of a user equipment (UE), the second table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE; receiving from the UE an indication of an index indicating the range of an amount of uplink data in one or more buffers of the UE; and determining the range of an amount of uplink data in the one or more buffers of the UE using the index and the second table.

[0048] The method may further include sending table release information to the UE indicating that the second table is to be released; receiving an indication of an index from the UE indicating the range of an amount of uplink data in one or more buffers of the UE; and determining the range of an amount of uplink data in one or more buffers of the UE using the index and the first table.

[0049] In another aspect, the present disclosure provides a user equipment (UE), the UE comprising: means for storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data and a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data; and means for determining, based on an amount of uplink data in one or more buffers of the UE, whether to use the first table to determine a first index indicating a first range of an amount of uplink data in one or more buffers of the UE or to use the second table to determine a second index indicating a second range of an amount of uplink data in one or more buffers of the UE; determining means configured to determine the first index or the second index based on an amount of uplink data in a table; and transmitting means configured to send an indication of the first index or the second index to an access network node, and, if the UE sends an indication of the first index to the access network node, to send an indication to the access network node indicating that the first table was used to generate the first index, and, if the UE sends an indication of the second index to the access network node, to send an indication to the access network node indicating that the second table was used to generate the second index.

[0050] In another aspect, the present disclosure provides a user equipment (UE), the UE comprising: means for storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE; and, when the UE receives from an access network node a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE, or the second table is stored in the UE, determining an index indicating a range of an amount of uplink data in the one or more buffers using the first table or the second table based on the amount of uplink data in one or more buffers of the UE; and, when the first table or the second table is stored in the UE, or in a second case where the UE has not received the second table or the information for generating the second table from the access network node or the second table is not stored in the UE, determine the index using the first table based on an amount of the uplink data in one or more buffers of the UE and send an indication of the index to the access network node in a buffer status report having a second format, the second format being different from the first format.

[0051] In another aspect, the present disclosure provides a user equipment (UE), the UE comprising: storage means configured to store a first table, for an amount of uplink data within a first range, mapping each of a plurality of first indexes to a respective sub-range of the first range; and to store a second table, for an amount of uplink data within a second range, mapping each of a plurality of second indexes to a respective sub-range of the second range, each of the plurality of first indexes being different from each of the plurality of second indexes; and transmission means configured to transmit, to the access network node, an index of the plurality of second indexes indicating the sub-range of the amount of uplink data in the one or more buffers of the UE if the amount of uplink data in the one or more buffers of the UE is within the second range but not within the second range.

[0052] In another aspect, the present disclosure provides a user equipment (UE), comprising: means for storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data and a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data; means for receiving table activation information from an access network node indicating whether the second table is activated in the UE; means for determining to use the second table if the table activation information indicates that the second table is activated in the UE, and for determining an index of the second plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; and means for transmitting an indication of the index to the access network node.

[0053] In another aspect, the present disclosure provides a user equipment (UE), comprising: means for storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data; means for receiving, from an access network node, table setup information for a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data; means for determining, based on the table setup information, to use the second table and determining an index of the second plurality of indexes that indicates a range of an amount of uplink data in one or more buffers of the UE; and means for transmitting an indication of the index to the access network node.

[0054] In another aspect, the present disclosure provides a user equipment (UE), comprising: means for storing a table mapping each of a plurality of indexes to a respective range of uplink data, wherein a first index of the plurality of indexes is mapped to a first range of uplink data, a second index of the plurality of indexes is mapped to a second range of uplink data, and a third index of the plurality of indexes is mapped to a third range of uplink data, wherein the first range and the third range are smaller than the second range, an upper limit of the first range is smaller than a lower limit of the second range, and an upper limit of the second range is smaller than a lower limit of the third range; the UE further comprises: means for determining the index of the table indicative of the range of an amount of the uplink data in one or more buffers of the UE based on an amount of uplink data in one or more buffers of the UE; and means for transmitting the index to an access network node.

[0055] In another aspect, the present disclosure provides an access network node, the access network node being configured to assign each of a plurality of second indexes to a user equipment (UE). means for transmitting to a UE a second table mapping each of a plurality of first indices to a respective first range of an amount of uplink data in one or more buffers of a UE, or information for generating the second table at the UE; and receiving means configured to receive from the UE an indication of an index indicating a range of an amount of uplink data in one or more buffers of the UE, and, if the index is an index determined using a first table mapping each of a plurality of first indices to a respective first range of an amount of uplink data in one or more buffers of the UE, receive from the UE an indication indicating that the first table was used to generate the index, determine the range of an amount of uplink data in one or more buffers of the UE using the first table, and, if the index is an index determined using the second table, receive from the UE an indication indicating that the second table was used to generate the index, and determine the range of an amount of uplink data in one or more buffers of the UE using the index and the second table.

[0056] In another aspect, the present disclosure provides an access network node, the access network node comprising: a first access network node configured to access a first access network node; and transmitting a second table to the UE that maps each of a plurality of first indexes to a respective second range of amounts of uplink data in one or more buffers of a base station equipment (UE), or in a first case when the access network node transmits information for generating the second table at the UE and the second table is stored in the UE, receiving an indication of an index from the UE in a buffer status report, the buffer status report having a first format including an indication of whether the first table or the second table that maps each of a plurality of first indexes to a respective first range of amounts of uplink data in one or more buffers of the UE was used to determine the index; or in a second case when the base station has not transmitted the second table or the information for generating the second table to the UE or the second table is not stored in the UE, receiving an indication of the index from the UE in a buffer status report having a second format, the second format being different from the first format.

[0057] In another aspect, the present disclosure provides an access network node, the access network node comprising: means for transmitting table activation information to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, the table activation information indicating whether a second table that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE is to be activated in the UE; means for receiving from the UE an indication of an index that indicates the range of an amount of uplink data in the one or more buffers of the UE; and means for determining the range of the amount of uplink data in the one or more buffers of the UE using the index and the second table.

[0058] In another aspect, the present disclosure provides an access network node, the access network node comprising: means for transmitting table setup information for a second table to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, the second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE; means for receiving from the UE an indication of an index that indicates the range of an amount of uplink data in the one or more buffers of the UE; and means for determining the range of the amount of uplink data in the one or more buffers of the UE using the index and the second table. [Brief explanation of the drawings]

[0059] Embodiments of the present disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0060] [Figure 1] FIG. 1 illustrates schematically a mobile (“cellular” or “wireless”) communications system. [Figure 2] FIG. 2 shows a typical frame structure that can be used in the communication system of FIG. [Figure 3] FIG. 3 is a schematic block diagram illustrating the main components of a DU 50 that may be used as part of the RAN equipment 5 of the communication system 1 shown in FIG. [Figure 4] FIG. 4 is a schematic block diagram illustrating the main components of a CU 60 that may be used as part of the RAN equipment 5 of the communications system 1 shown in FIG. [Figure 5] Figure 5 shows the short buffer status report. [Figure 6] FIG. 6 shows the lookup table for the buffer status report. [Figure 7] Figure 7 shows the long buffer status report. [Figure 8] Figure 8 shows the extended short buffer status report. [Figure 9] Figure 9 shows the extended long buffer status report. [Figure 10] FIG. 10 is a schematic diagram illustrating some examples of BSR transmission. [Figure 11] FIG. 11 is a schematic diagram illustrating some examples of BSR transmission. [Figure 12] FIG. 12 is a schematic diagram illustrating some examples of BSR transmission. [Figure 13] FIG. 13 is a schematic diagram illustrating some examples of BSR transmission. [Figure 14] FIG. 14 is a schematic diagram illustrating some examples of BSR transmission. [Figure 15] FIG. 15 is a schematic diagram illustrating some examples of BSR transmission. [Figure 16] FIG. 16 is a schematic diagram illustrating some examples of BSR transmission. [Figure 17] FIG. 17 is a schematic diagram illustrating some examples of BSR transmission. [Figure 18] FIG. 18 is a schematic diagram illustrating some examples of BSR transmission. [Figure 19] FIG. 19 is a schematic diagram illustrating some examples of BSR transmission. [Figure 20] FIG. 20 is a schematic diagram illustrating some examples of BSR transmission. [Figure 21] FIG. 21 is a schematic diagram illustrating some examples of BSR transmission. [Figure 22] FIG. 22 is a schematic diagram illustrating some examples of BSR transmission. [Figure 23] FIG. 23 shows an example of a MAC PDU. [Figure 24] FIG. 24 shows an example of a subheader and the corresponding MAC CE. [Figure 25] FIG. 25 shows a further example of a subheader and corresponding MAC CE. [Figure 26] Figure 26 shows how the UE 3 and base station 5 exchange information regarding one or more BSR tables. [Figure 27] FIG. 27 illustrates an example of a MAC CE that may be used to send an indication of the BSR table used to generate the BSR. [Figure 28] FIG. 28 shows a further example of a MAC CE that may be used to send an indication of the BSR table used to generate the BSR. [Figure 29] FIG. 29 shows a modified MAC CE where 8 bits are used for the buffer size field. [Figure 30] FIG. 30 shows a further example of how to use the MAC CE to indicate the BSR table used by UE3. [Figure 31] FIG. 31 shows an example where the buffer size field is variable length. [Figure 32]FIG. 32 shows an example in which the indication of the BSR table used by UE 3 (T7 to T0) is provided in a sequence of consecutive bits following a field identifying the LCG. [Figure 33] FIG. 33 shows an example in which the subheader of the example of FIG. 24 has been modified to include an eLCID. [Figure 34] FIG. 34 shows another example where the subheader additionally includes a length field. [Figure 35] FIG. 35 shows an example in which UE3 receives a BSR table from the base station. [Figure 36] FIG. 36 shows an example of the first BSR table and the extended BSR table. [Figure 37] FIG. 37 shows an example in which a base station uses a BSR table setup / release indication to control the activation / deactivation of a BSR table. [Figure 38] FIG. 38 shows an example BSR table with improved accuracy for both low buffer size values ​​and a wider range of buffer size values. [Figure 39] FIG. 39 is a schematic block diagram illustrating the main components of a UE of the communication system of FIG. [Figure 40] FIG. 40 is a schematic block diagram illustrating the main components of a base station of the communication system of FIG. [Figure 41] FIG. 41 is a schematic block diagram showing the main components of a core network node or function of the communication system of FIG. DETAILED DESCRIPTION OF THE INVENTION

[0061] overview An exemplary communication system will now be described in general terms, by way of example only, with reference to Figures 1 and 2.

[0062] FIG. 1 illustrates schematically a mobile (“cellular” or “wireless”) communications system 1 to which embodiments of the present disclosure are applicable.

[0063] In network 1, user equipment (UE) 3-1, 3-2, 3-3 (e.g., mobile phones and / or other mobile devices) can communicate with one another via radio access network (RAN) nodes 5 that operate according to one or more compatible radio access technologies (RATs). In the illustrated example, the RAN nodes 5 include NR / 5G base stations or "gNBs" 5 that operate one or more associated cells 9. Communications via the base stations 5 are typically routed through a core network 7 (e.g., a 5G core network or evolved packet core network (EPC)).

[0064] As will be appreciated by those skilled in the art, although FIG. 1 shows three UEs 3 and one base station 5 for illustrative purposes, other base stations 5 and UEs 3 will typically be included when the system is implemented.

[0065] Each base station 5 controls one or more associated cells 9 directly or indirectly via one or more other nodes (such as home base stations, relays, remote radio heads, distributed units, etc.) It will be appreciated that the base stations 5 may be configured to support 4G, 5G, 6G and / or other 3GPP or non-3GPP communication protocols.

[0066] A UE 3 and its serving base station 5 are connected via a suitable radio interface (such as, for example, the so-called "Uu" interface). Neighboring base stations 5 may be connected to each other via a suitable inter-base station interface (such as, for example, the so-called "X2" interface, "Xn" interface, etc.).

[0067] The core network 7 includes multiple logical nodes (or "functions") for supporting communications in the communication system 1. In this example, the core network 7 includes a control plane function (CPF) 10 and one or more user plane functions (UPF) 11. The CPF 10 includes one or more Access and Mobility Management Functions (AMF) 10-1, one or more Session Management Functions (SMF), and multiple other functions 10-n.

[0068] The base stations 5 are connected to core network nodes via appropriate interfaces (or "reference points"), such as the N2 reference point for communication of control signaling between the base stations 5 and the AMF 10-1, and the N3 reference point for communication of user data between the base stations 5 and each UPF 11. The UEs 3 are each connected to the AMF 10-1 via a logical non-access stratum (NAS) connection via the N1 reference point (equivalent to the S1 reference point in LTE). It will be appreciated that the N1 communications are transparently routed via the base stations 5.

[0069] The one or more UPFs 11 are connected to an external data network (eg an IP network such as the Internet) via a reference point N6 for the communication of user data.

[0070] The AMF 10-1 performs mobility management related functions, maintains a NAS signaling connection with each UE 3, and manages UE registrations. The AMF 10-1 is also responsible for managing paging. The SMF 10-2 provides session management functions (forming part of the LTE MME functionality) and also integrates some control plane functions (provided by the LTE Serving Gateway and Packet Data Network Gateway). The SMF 10-2 allocates an IP address to each UE 3.

[0071] The base stations 5 of the communication system 1 are configured to operate at least one cell 9 on an associated TDD carrier operating in unpaired spectrum. It will be appreciated that the base stations 5 may also operate at least one cell 9 on an associated FDD carrier operating in paired spectrum.

[0072] The base station 5 is also configured to transmit control information and user data via a plurality of downlink (DL) physical channels and a plurality of physical signals, which the UE 3 is configured to receive, where the DL physical channels correspond to resource elements (REs) that carry information originating from higher layers, and the DL physical signals correspond to REs used by the physical layer that do not carry information originating from higher layers.

[0073] The physical channels may include, for example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), and a physical downlink control channel (PDCCH). The PDSCH carries data that shares the capacity of the PDSCH based on time and frequency. The PDSCH can carry various data items, including, for example, user data, UE-specific upper layer control messages mapped from higher channels, system information blocks (SIBs), and paging. The PDCCH carries downlink control information (DCI) to support various functions, including, for example, scheduling downlink transmissions on the PDSCH and uplink data transmissions on the physical uplink shared channel (PUSCH). The PBCH provides a Master Information Block (MIB) to the UE. The PBCH, in conjunction with the PDCCH, also supports time and frequency synchronization and assists in cell acquisition, selection, and reselection. The UE 3 may receive a synchronization signal block (SSB) and may assume that the reception opportunities for the PBCH, primary synchronization signal (PSS), and secondary synchronization signal (SSS) are consecutive symbols, forming an SS / PBCH block. The base station 5 may transmit multiple synchronization signal (SS) blocks corresponding to different DL beams. The total number of SS blocks may be limited, for example, to a duration of 5 ms as an SS burst. The periodicity of the SSB transmission may be indicated to the UE using any appropriate signaling (e.g., per serving cell using ssb-periodicityServingCell). The SSB periodicity value may be, for example, 20 ms or greater. During initial cell selection, the UE 3 may be configured to assume that SS bursts occur with a periodicity of two frames.The UE 3 may also be provided with an indication of which SSBs will be transmitted within the 5 ms period (eg, using ssb-PositionsInBurst).

[0074] DL physical signals may include, for example, reference signals (RS) and synchronization signals (SS). Reference signals (sometimes known as pilot signals) are signals with predefined special waveforms that are known to both the UE 3 and the base station 5. Reference signals may include, for example, cell-specific reference signals, UE-specific reference signals (UE-RS), downlink demodulation signals (DMRS), and channel state information reference signals (CSI-RS).

[0075] Similarly, the UE 3 is configured to transmit control information and user data via a plurality of uplink (UL) physical channels corresponding to REs carrying information originating from higher layers, and to transmit UL physical signals corresponding to REs used in the physical layer that do not carry information originating from higher layers, and the base station 5 is configured to receive these. The physical channels may include, for example, a PUSCH, a physical uplink control channel (PUCCH), and / or a physical random-access channel (PRACH). The UL physical signals may include, for example, a demodulation reference signal (DMRS) for UL control / data signals and / or a sounding reference signal (SRS) used for UL channel measurement.

[0076] When a UE 3 first establishes a radio resource control (RRC) connection with a base station 5 via a cell, it registers with the appropriate core network node (e.g. AMF, MME, etc.). The UE 3 is in the so-called RRC connected state, and the associated UE context is maintained by the network. When the UE 3 is in the so-called RRC idle or RRC inactive state, the UE 3 selects a suitable cell to camp on, allowing the network to know the approximate location of the UE 3 (although not necessarily at a cell level).

[0077] It will be appreciated that a UE 3 may support one or more services, each of which typically has associated requirements (e.g., latency / data rate / packet loss requirements, etc.), and that these requirements may vary from service to service. Each UE 3 may be configured with an appropriate power-saving operation, such as discontinuous reception (DRX) or discontinuous transmission (DTX). The power-saving operation may depend on the category of service or services used, the capabilities of the UE 3, and other factors (e.g., QoE / QoS, throughput, serving cell(s), network load, etc.). The DRX configuration used by a UE 3 may be dynamically adjusted to accommodate a wide range of services, such as extended reality (XR) data.

[0078] The base station 5 may be divided into one or more distributed units (DU) 50 and a central unit (CU) 60, where the CU 60 typically performs high-level functions and communication with the next-generation core, and the DU 50 performs low-level functions and communication with nearby UEs 3 (i.e., within the cell operated by the base station 5) via the air interface. This type of base station may be referred to as a "distributed" base station 5 or gNB 5. A distributed gNB 5 includes the following functional units: gNB Central Unit (gNB-CU): A logical node that hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) layers of a gNB (or the RRC and PDCP layers of an en-gNB) and controls the operation of one or more gNB-DUs. The gNB-CU terminates the so-called F1 interface connected to the gNB-DUs. gNB Distributed Unit (gNB-DU): A logical node that hosts the Radio Link Control (RLC), Medium Access Control (MAC) and Physical (PHY) layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. gNB-CU-Control Plane (gNB-CU-CP): A logical node that hosts the control plane portion of the RRC and PDCP protocols of the gNB-CU for the en-gNB or gNB. The gNB-CU-CP terminates the E1 interface connected to the gNB-CU-UP and the F1-C (F1 control plane) interface connected to the gNB-DU. gNB-CU-User Plane (gNB-CU-UP): A logical node that hosts the user plane portion of the PDCP protocol of the gNB-CU for the en-gNB, and the user plane portion of the PDCP protocol and SDAP protocol of the gNB-CU for the gNB. The gNB-CU-UP terminates the E1 interface connected to the gNB-CU-CP and the F1-U (F1 user plane) interface connected to the gNB-DU.

[0079] It will be appreciated that if a distributed base station or similar control plane - user plane (CP-UP) split is employed, the base station 5 is split into separate control plane and user plane entities, each of which may include associated transceiver circuitry, antennas, network interfaces, controllers, memory, operating systems, and communication control modules. If the base station 5 is configured as a distributed base station, the network interfaces also include E1 and F1 interfaces (F1-C for the control plane and F1-U for the user plane) for communicating signals between each function of the distributed base station.

[0080] Frame structure 2 shows a typical frame structure used in a communication system 1, in which base stations 5 and UEs 3 communicate with each other using resources organized in the time domain into 10 ms long frames. Each frame contains ten equally sized 1 ms long subframes. Each subframe is divided into one or more slots containing 14 equally long Orthogonal Frequency-Division Multiplexing (OFDM) symbols.

[0081] As shown in FIG. 2, the communication system 1 supports multiple different numerologies (subcarrier spacing (SCS), slot length, and OFDM symbol length). Specifically, each numerology is identified by a parameter μ, where μ=0 represents 15 kHz (corresponding to LTE SCS). Currently, SCS for other values ​​of μ can be derived substantially by scaling up from μ=0 by a power of 2 (i.e., SCS=15×2μkHz). The relationship between the parameter μ and SCS (Δf) is shown in Table 1. [Table 1]

[0082] RAN equipment DU Figure 3 is a schematic block diagram illustrating the main components of a DU 50 that may be used as part of the RAN equipment 5 of the communication system 1 shown in Figure 1. As shown, the DU 50 comprises transceiver circuitry 451 for transmitting signals to and receiving signals from communication devices (such as UE 3) via a radio unit (RU) and associated DU-RU interface 453, and for transmitting signals to and receiving signals from a CU 60 of the RAN equipment 5 via a CU interface 454 (e.g., including an F1 interface that is divided into an F1-U interface and an F1-C interface for user plane signaling and control plane signaling, respectively).

[0083] The DU 50 comprises a controller 457 that controls the operation of the DU 50. The controller 457 is associated with a memory 459. Software may be pre-installed in the memory 459 and / or may be downloaded, for example, via the communication network 1 or a removable data storage device (RMD). The controller 457 is configured, in this example, to control the overall operation of the DU 50 by means of program instructions or software instructions stored in the memory 459.

[0084] As shown, these software instructions include, among other things, an operating system 461, a communication control module 463, an F1 module 465, a DU-RU module 468, a UE profile management module 473, and a mobility module.

[0085] The communication control module 463 is operable to control communications between the DU 50 and one or more RUs 5a (i.e., between the DU 50 and the UE 3), and between the DU 50 and the CU 60. The communication control module 463 is configured to generally control the reception of signals corresponding to uplink communications from the UE 3, and to handle the transmission of downlink communications destined for the UE 3. The communication control module 463 may be configured to control the allocation of uplink resources to the UE 3 (e.g., in response to receiving corresponding buffer status reports from the UE 3).

[0086] The F1 module 465 is responsible for appropriate processing of signals received from or transmitted to the CU 60 via one or more CU interfaces 454 (e.g., F1 interfaces). These signals may be split into user plane signals received from or transmitted to the CU-UP portion of the CU 60 via the F1-U interface, and control plane signals received from or transmitted to the CU-CP portion of the CU 60 via the F1-C interface.

[0087] The DU-RU module 468 is responsible for the appropriate processing of signals received from or transmitted to the RU via one or more RU interfaces 453 (eg, DU-RU interfaces).

[0088] The DU management module 472 is responsible for managing the overall operation of the DU 50 and the overall performance of the tasks required by the DU 50. These tasks include the generation and transmission of appropriate messages using the appropriate signaling application protocol depending on the division of functionality between the RU, DU 50, and CU 60, such as interpreting received MAC signals and generating MAC signals for transmission.

[0089] The UE profile management module 473 is responsible for performing functions related to UE profiles, including (if applicable) receiving and storing UE profiles or associated assistance / preference information from the UE 3 or elsewhere in the network, determining appropriate mobility-specific configurations based on the UE profile / assistance / preference information for implementation in the UE 3 and / or RAN equipment (if applicable), and / or providing configuration information for appropriately configuring the UE with mobility-based configurations (if applicable). The UE profile management module 473 may also store historical mobility information for the UE 3 (e.g., past movements of the UE 3 between different communication cells of the network). It will be understood that, depending on the implementation, the gNB-DU may not implement at least some of these functions.

[0090] The mobility module 475 is responsible for controlling mobility procedures for one or more UEs 3. For example, the mobility module 475 may be configured to perform one or more measurements related to the mobility of the UE 3, select a candidate cell for handover, etc. It will be appreciated that the mobility module 475 may be configured to perform control over any of the mobility methods described below (e.g., handover, etc.).

[0091] CU Figure 4 is a schematic block diagram illustrating the main components of the CU 60 of the RAN equipment of the communication system 1 shown in Figure 1. As shown, the CU 60 comprises a transceiver circuit 551 for transmitting signals to and receiving signals from the DU 50 via one or more DU interfaces 554 (e.g., including an F1 interface divided into an F1-U interface and an F1-C interface for user plane signaling and control plane signaling, respectively), and a transceiver circuit 551 for transmitting signals to and receiving signals from the core network 7 functions via one or more core network interfaces 555 (e.g., including an N2 interface and an N3 interface, etc.).

[0092] The CU 60 comprises a controller 557 that controls the operation of the CU 60. The controller 557 is associated with a memory 559. Software may be pre-installed in the memory 559 and / or may be downloaded, for example, via the communication network 1 or a removable data storage device (RMD). The controller 557 is configured in this example to control the overall operation of the CU 60 by means of program or software instructions stored in the memory 559.

[0093] As shown, these software instructions include an operating system 561, a communication control module 563, an F1 module 565, an E1 module 566, an N2 module 568, an N3 module 569, a CU-UP management module 571, a CU-CP management module 572, a UE profile management module 573, and a mobility module 575. The functionality of mobility module 575 is the same as that described above with reference to FIG.

[0094] The communication control module 563 is operable to control communications between the CU 60 and one or more DUs 50 (i.e., between the CU 60 and the UE 3), and between the CU 60 and the core network 7. The communication control module 563 is configured to generally control the reception of signals corresponding to uplink communications from the UE 3, and to handle the transmission of downlink communications destined for the UE 3.

[0095] The F1 module 565 is responsible for appropriate processing of signals received from or transmitted to the DU 50 via one or more DU interfaces 554 (such as, for example, an F1 interface). These signals may be divided into user plane signals received at or transmitted to the CU-UP part of the CU via the F1-U interface, and control plane signals received at or transmitted to the CU-CP part of the CU via the F1-C interface.

[0096] The E1 module 566 is responsible for the proper processing of signals transmitted between the CU-UP portion of the CU 60 and the CU-CP portion of the CU 60 via a corresponding internal CU interface (eg, an E1 interface).

[0097] The N2 module 568 is responsible for appropriate processing of signals received from or sent to the AMF 8-1 via one or more corresponding core network interfaces 555 (such as the N2 interface).

[0098] The N3 module 569 is responsible for the appropriate processing of signals received from or sent to one or more core network user plane functions via one or more corresponding core network interfaces 555 (such as, for example, an N3 interface).

[0099] The CU-UP management module 571 is responsible for managing the overall operation of the CU-UP portion of the CU 60 and the overall performance of the tasks required by the CU-UP.

[0100] The CU-CP management module 572 is responsible for managing the overall operation of the CU-CP portion of the CU 60 and the overall performance of the tasks required for the CU-CP. These tasks include the generation and transmission of appropriate messages using the appropriate signaling application protocol, such as interpreting received RRC signaling and generating RRC signaling for transmission, depending on the division of functionality between the RU, the DU 50, and the CU 60.

[0101] The UE profile management module 573 is responsible for performing functions related to UE (mobility) profiles, including (if applicable) receiving and storing UE profiles or associated assistance / preference information from the UE 3 or elsewhere in the network, determining appropriate mobility-specific configurations based on the UE profile / assistance / preference information for implementation in the UE 3 and / or the RAN equipment 5, and / or providing configuration information to appropriately configure the UE with mobility-based configurations. The UE profile management module 573 may also store historical mobility information of the UE 3 (e.g., past movements of the UE 3 between different communication cells of the network). It will be understood that, depending on the implementation, the CU 60 may not implement at least some of these functions.

[0102] System Information and SIB It will be appreciated that transmissions in the cell 9 of the base station 5 may include one or more broadcast transmissions and one or more unicast transmissions for reception by the UEs 3. System information (SI) transmitted within the cell may include "minimum SI" (MSI) and "other SI" (OSI). OSI may be broadcast on demand, for example, using the downlink shared channel (DL-SCH). OSI may also be broadcast upon request from a UE 3 in a radio resource control (RRC) idle or RRC inactive state. OSI may also be requested by a UE 3 in an RRC connected state, for example, via one or more dedicated RRC transmissions.

[0103] The SI may include information to enable (e.g., configure) the UE 3 to complete a cell selection, to enable the UE 3 to complete a cell reselection procedure, or to enable the UE 3 to receive one or more paging messages transmitted within a cell. The SI may be broadcast using a Master Information Block (MIB) and one or more System Information Blocks (SIBs).

[0104] The MSI includes a MIB and system information block 1 (SIB1). The MIB includes information used by the UE 3 to receive SIB1, such as the subcarrier spacing of SIB1. The MIB provides information corresponding to a control resource set (CORESET) and a search space. SIB1 may be referred to as the "remaining MSI" (RMSI). SIB1 may be transmitted in a dedicated RRC message, and other SIBs (e.g., SIB2 to SIB9) may be transmitted using one or more other appropriate RRC transmissions. The MIB and SIB1 may provide the UE 3 with an indication of scheduling information for receiving and decoding other SIBs, such as SIB2 to SIB9, and may provide information used by the UE 3 to receive one or more paging messages. The OSI may include, for example, SIB2 to SIB9 transmitted using the DL-SCH in an SI message. A mapping of SIB2 to SIB9 and the corresponding SI messages may be provided to the UE 3 by the base station 5. The MIB and SIB1 to SIB9 are described in further detail in, for example, 3GPP TS38.331. For example, SIB2 provides information about intra-frequency, inter-frequency, and inter-system cell reselection, SIB3 provides cell-specific information about intra-frequency cell reselection, and SIB4 provides information about inter-frequency cell reselection. SIB5 provides information about inter-system cell reselection for 4G (LTE). SIB6 and SIB7 provide information about earthquake and tsunami warning system (ETWS). SIB8 provides information about commercial mobile alert service (CMAS) notifications, for example to provide alert text messages to UE3.SIB9 contains information about coordinated universal time (UTC), global positioning system (GPS) time (eg, for GPS initialization), and local time.

[0105] The SIBs may be broadcast periodically (e.g., according to a predetermined periodic pattern) or may be provided "on-demand," e.g., upon request from UE 3. For example, MIB may be transmitted with a periodicity of 80 ms and repeated within 80 ms, while SIB1 may be transmitted with a periodicity of 160 ms and with a variable transmission repetition period within 160 ms (e.g., 20 ms). SIB1 can be used to indicate to UE 3 which SIBs are transmitted periodically and which SIBs are available on-demand upon request from UE 3. UE 3 may be configured to request on-demand SIBs using a random access preamble (MSG1), also referred to as an MSG1-based on-demand SI request, or an RRC connection request (MSG3), also referred to as an MSG3-based on-demand SI request.

[0106] The physical broadcast channel (PBCH) can be used to broadcast the MIB. The base station 5 may transmit the PBCH with a synchronization signal (SS) (e.g., a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in an SS / PBCH block. The SS / PBCH block may comprise four orthogonal frequency-division multiplexed (OFDM) symbols mapped to the PSS, SSS, and PBCH associated with a demodulation reference signal (DM-RS). In the frequency domain, the SS / PBCH block consists of 240 consecutive subcarriers. When the UE 3 is in RRC connected mode, the base station 5 may provide the UE 3 with an indication of the resources used for the SS / PBCH, for example, using dedicated signaling (e.g., for the anchor NES cell or for the non-anchor NES cell). The SIB1 may be transmitted using a physical downlink shared channel (PDSCH). The OSI may also be transmitted, for example, using the PDSCH.

[0107] When one or more beamformed transmissions are transmitted within a cell served by base station 5, some of the SIs (e.g., some of the SIBs) may only be transmitted using particular beams or using particular transmission / reception points (TRPs).

[0108] Buffer Status Report (BSR) A Buffer Status Report (BSR), indicating the amount of uplink data in the buffer of the UE 3, is transmitted from the UE 3 to the base station 5. Based on the BSR received from the UE 3, the network can determine uplink communication resources (e.g., radio resources including frequency resources and / or time resources) to allocate to the UE 3 for transmission of the uplink data. The allocated uplink communication resources can be indicated to the UE 3 by a corresponding Uplink Grant message sent to the UE 3. It will be appreciated that an accurate and precise BSR is useful for more efficiently allocating uplink resources to the UE 3.

[0109] As described in more detail below, the BSR can use several different possible formats. The format used for the BSR (e.g., the number of bits used to indicate the amount of uplink data in the UE 3's buffer) may depend on how the transmission of the BSR is triggered, which may be different for regular BSRs, periodic BSRs, and padding BSRs, as described in more detail below. The BSR may indicate the amount of uplink data in the UE 3's buffer for a particular logical channel (LCH) or logical channel group (LCG), and the format of the BSR may depend on the number of LCGs that have uplink data available for transmission. In the case of a padding BSR, which is transmitted depending on the number of padding bits available for BSR transmission, the format of the BSR may depend on the number of padding bits available.

[0110] A logical channel is identified using a corresponding logical channel ID (LCID), which may be used to indicate the format of the BSR. An extended LCID (eLCID) may be provided that extends the range of the LCID field (e.g., using several bits following the LCID, such as 8 bits). For example, an LCID value of 61 may indicate that the BSR is a short BSR, a value of 62 may indicate that the BSR is a long BSR, a value of 59 may indicate that the BSR is a short truncated BSR, and a value of 60 may indicate that the BSR is a long truncated BSR. The LCID may be included in the MAC subheader of a transmission from the UE 3 to the base station 5. Some examples of types of BSRs that may be transmitted from the UE 3 to the base station 5 are described below.

[0111] The Short BSR is a fixed size, uses 5 bits to indicate the amount of uplink data in one or more buffers of the UE 3, and is a report associated with one LCG. The Long BSR is a variable size, uses 8 bits to indicate the amount of uplink data in one or more buffers of the UE 3, and can provide buffer status for multiple LCGs. The Short Truncated BSR is a fixed size, uses 5 bits to indicate the amount of uplink data in one or more buffers of the UE 3, and is a report associated with one LCG. The Long Truncated BSR is a variable size, uses 8 bits to indicate the amount of uplink data in one or more buffers of the UE 3, and can provide buffer status for multiple LCGs.

[0112] The BSR may be transmitted from the UE 3 to the base station 5 as a MAC control element (MAC CE) in a corresponding transport block (TB), for example as part of a MAC protocol data unit (PDU). The MAC PDU may include a subheader and a MAC service data unit (SDU). The subheader may include an LCID indication (which can be used to indicate the format of the BSR). The subheader may also include a length field indicating the length of the corresponding MAC SDU. The subheader may also include a format field indicating the length of the length field (e.g., a value of 0 is used to indicate that the length field is 8 bits long and a value of 1 is used to indicate that the length field is 16 bits long, but other suitable types of indications may also be used and the value does not necessarily have to be 0 or 1).

[0113] Figure 5 shows an example of a Short BSR MAC CE that may be included in a TB for transmission from UE 3 to base station 5, e.g., as part of a MAC PDU. As shown, the short BSR contains 3 bits indicating the LCGID and 5 bits indicating the corresponding buffer size (the amount of uplink data stored in the buffer). The total size of the short BSR is therefore 8 bits.

[0114] The Buffer Size field indicates the amount of uplink data that is in the buffer of the UE 3 after construction of the MAC PDU (e.g. after logical channel prioritization procedure) and that is available for transmission to the base station 5 through all logical channels of the logical channel group (according to the data volume calculation procedure). The size of the RLC header and MAC subheader are not taken into account in the buffer size calculation. The value indicated in the Buffer Size field is used by the base station 5 to identify the corresponding entry in a look-up table that indicates the number of data bytes in the buffer of the UE 3.

[0115] The 5 bits indicating the buffer size can be used to indicate an index from 0 to 31. FIG. 6 shows an exemplary table that can be used to map the indicated index to a buffer size (in this example, the buffer size is in bytes, but is not necessarily limited to this; other suitable data size units can be used instead). This table can be stored and used by the base station 5. For example, if the 5-bit field of the BSR used to indicate the buffer size indicates a value of 22, the corresponding buffer size identified using the lookup table is greater than 7587 bytes and less than or equal to 10570 bytes. It will therefore be understood that the base station 5 can use the table of FIG. 6 to determine the buffer size in the UE 3 based on the BSR. The index mapped to each buffer size value is also referred to as a "code point."

[0116] As shown in Figure 6, the larger the BSR index (buffer size value), the less precise the range of buffer size values. For example, if the indicated index is 3, the buffer size is greater than 14 and less than or equal to 20, which is a range of 6 bytes. On the other hand, if the indicated index is 28, the buffer size is greater than 55474 and less than or equal to 77284, which is a range of 21810 bytes. An improved method for reducing the variability in the precision of buffer size values ​​will be described in more detail later.

[0117] 7 through 9 show further examples of BSRs that may be sent from the UE 3 to the base station 5. FIG. 7 shows an example of a Long BSR MAC CE indicating multiple buffer sizes associated with each of multiple LCGs. The LCGi field indicates the presence of the buffer size field for logical channel group i. When the LCGi field is set to 1, it indicates that the buffer size field for logical channel group i is reported in the BSR. When the LCGi field is set to 0, it indicates that the buffer size field for logical channel group i is not reported in the BSR. For the Long Truncated BSR and Extended Long Truncated BSR formats, this field indicates whether there is data available for logical channel group i. When the LCGi field is set to 1, it indicates that there is data available for logical channel group i. When the LCGi field is set to 0, it indicates that there is no data available for logical channel group i.

[0118] FIG. 8 shows an extended short buffer status report, and FIG. 9 shows an extended long buffer status report. As can be seen, 8 bits (corresponding to an index of 0 to 255) are used to indicate each buffer size. For the Long BSR format, Long Truncated BSR format, Extended Long BSR format, and Extended Long Truncated format, the buffer size fields are included in ascending order based on LCGi (i.e., ascending order of LCGi values). For the Long Truncated BSR format and Extended Long Truncated format, the number of included buffer size fields is maximized without exceeding the number of available padding bits. Similar to the one shown for the 5-bit case in FIG. 6, an exemplary lookup table for an 8-bit buffer size indication is shown in Table 2 below. [Table 2] [Table 3]

[0119] As mentioned above, the BSR MAC CE can use the following formats: - Short BSR format (fixed size) or - Extended Short BSR format (fixed size) or - Long BSR format (variable size) or - Extended Long BSR format (variable size) or - Short Truncated BSR format (fixed size) or - Extended Short Truncated BSR format (fixed size) or - Long Truncated BSR format (variable size), or - Extended Long Truncated BSR format (variable size).

[0120] A BSR may be triggered for a transmission from the UE 3 to the base station 5. For example, a BSR may be triggered when UL data for a logical channel belonging to an LCG becomes available at the MAC entity of the UE 3 and either: - this UL data belongs to a logical channel with higher priority than any logical channel with available UL data belonging to any LCG, or - None of the logical channels belonging to the LCG contain any available UL data, in this case the BSR is also called "Regular BSR". A BSR may also be triggered if the number of padding bits (available for sending BSR) in an uplink data message is equal to or greater than the sum of the size of the Buffer Status Report MAC CE and the size of the corresponding subheader. This type of BSR is also called "Padding BSR".

[0121] The BSR may also be triggered based on a timer (e.g., the retxBSR timer) if at least one of the logical channels belonging to the LCG contains UL data, in which case the BSR is also called a "Regular BSR". The MAC entity may restart the timer when it receives a grant to send new data on any UL-SCH.

[0122] A BSR may also schedule periodic transmissions based on a timer (e.g., a periodic BSR timer), in which case the BSR is also referred to as a "Periodic BSR" or "Periodical BSR."

[0123] In some examples, a MAC PDU may contain at most one BSR MAC CE, even if multiple events trigger the BSR. Regular BSR and Periodic BSR may have higher priority for transmission to base station 5 compared to Padding BSR.

[0124] It will be appreciated that the methods for transmitting (and deciding to transmit) buffer status reports described below can be applied to any suitable type of BSR.

[0125] The BSR is received by the base station 5, which may use it to configure and / or schedule uplink resources for transmission of uplink data from the UE 3 to the base station 5. For example, in configured grant Type 1, the uplink grant is provided by RRC and saved as the configured uplink grant. In configured grant Type 2, the uplink grant is provided by the physical downlink control channel (PDCCH) and saved or cleared as the configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and Type 2 are configured by RRC for a serving cell per bandwidth part (BWP). Multiple configurations can be active simultaneously within the same BWP. In Type 2, activation and deactivation are independent between serving cells. A MAC entity can be configured with both Type 1 and Type 2 for the same BWP. The base station 5 may also (or instead) perform semi-persistent scheduling (SPS) or dynamic grant (DG).

[0126] Further examples of BSRs are described in Technical Specification (TS) 38.321 V17.0.0.

[0127] BSR Transmission An example of a method for transmitting a BSR from the UE 3 to the base station 5 will be described below.

[0128] BSR polling FIG. 10 shows an example of BSR polling via physical downlink control channel (PDCCH) signaling.

[0129] As shown in the figure, the base station 5 transmits an indication to the UE 3 as to whether or not to transmit a BSR. For example, the UE 3 may indicate whether or not to include a regular BSR in the transmission to the base station 5 by including a BSR polling field in the PDCCH. The BSR polling field may be a 1-bit field (e.g., a value of 1 indicates that a BSR is to be transmitted to the base station, and a value of 0 indicates that no BSR transmission is requested). However, any other suitable number of bits may be used for the BSR polling field.

[0130] 11 shows an alternative example in which an indication is included to the MAC CE as to whether to send a BSR, which may indicate whether to send a BSR for each logical channel group.

[0131] When the UE 3 receives the indication, the UE triggers / sends a regular BSR to the base station 5 for all or the indicated logical channel groups.

[0132] Advantageously, the UE 3 can therefore reliably determine that a BSR needs to be sent to the base station 5 .

[0133] Transmission data volume threshold 12 shows an example in which UE 3 receives a threshold for determining whether to send a BSR. UE 3 sends a BSR to base station 5 when the amount of data sent by UE 3 exceeds a value corresponding to the threshold received from base station 5.

[0134] The threshold value is obtained at the base station 5 (e.g., generated or received from the core network or other suitable network node) and transmitted to the UE 3. The threshold value may be received at the base station 5 from any suitable entity in the core network 7 or may be stored at the base station 5 (e.g., configured in a memory of the base station 5). In other words, the threshold value may be configured by any suitable entity in the network 1.

[0135] In this example, the threshold corresponds to the amount of data to be transmitted. Figure 13 shows an example of how the UE 3 uses the threshold to decide to transmit a BSR to the base station 5.

[0136] In step S130, the UE 3 receives from the base station 5 information indicating a threshold for transmitting a BSR.

[0137] In step S131, the UE 3 sends one or more uplink transmissions to transmit uplink data to the base station 5.

[0138] In step S132, the UE 3 determines whether the amount of data (also referred to as the "size" or "amount" of data) to be transmitted to the base station 5 exceeds the amount indicated by the threshold received in step S130. If the amount of uplink data to be transmitted exceeds the threshold, the UE 3 decides to transmit a BSR (e.g., Regular BSR) to the base station 5. If the amount of transmitted uplink data does not exceed the threshold, the UE 3 decides not to transmit a BSR (e.g., Regular BSR) to the base station 5 (alternatively, it may determine that a BSR is not required but can optionally be transmitted to the base station 5).

[0139] The UE3 may further determine whether there is uplink data in the corresponding buffer, and decide to transmit the BSR only if there is data in the corresponding buffer in addition to the amount of data transmitted exceeding the amount indicated by the threshold.

[0140] To determine the amount of data transmitted, UE3 may count the data transmitted for each LCH or LCG individually, or alternatively may count the data for all LCHs (or another suitable group or subset of LCHs) together.

[0141] In step S133, the UE 3 transmits a BSR to the base station 5.

[0142] After the UE 3 sends the BSR to the base station 5, the UE 3 resets the count of the amount of data that the UE 3 has sent and the method returns to step S131.

[0143] Therefore, advantageously, the UE 3 can more reliably transmit a BSR to the base station 5 by comparing the amount of uplink data being transmitted to the base station 5 with a threshold received from the base station 5.

[0144] Amount of data compared to the previously reported buffer size Figure 14 shows how the UE 3 decides to send a BSR based on a comparison of the amount of UL data that has been transmitted or scheduled since the last BSR was sent to the base station 5 and the buffer size reported in the last BSR.

[0145] In step S140, the UE 3 sends a BSR to the base station 5. The BSR includes an indication of the buffer size in the UE 3.

[0146] In step S141, the UE 3 transmits uplink data to the base station 5.

[0147] In step S142, the UE 3 determines that the amount of data (for the LCH or LCG) transmitted to the base station 5 exceeds the buffer size reported in the BSR in step S140, and therefore decides to transmit a BSR to the base station 5. When comparing the buffer size reported in the previous BSR, the UE 3 may optionally include data scheduled for transmission (e.g., data to be transmitted based on a UL grant received from the base station) in addition to data already transmitted to the base station 5. In other words, the UE 3 may determine whether the sum of the data transmitted from the UE 3 to the base station 5 since the previous BSR transmission and the amount of data currently scheduled to be transmitted to the base station 5 exceeds the buffer size reported in the BSR in step S140.

[0148] In step S143, the UE 3 transmits a BSR to the base station 5.

[0149] In this example, UE3 determines to send a BSR when the amount of data transmitted from UE3 to base station 5 is greater than the buffer size reported in the previous BSR, but instead, UE3 may determine to send a BSR when the amount of data transmitted to base station 5 is greater than or equal to the buffer size reported in the previous BSR, or may determine to send a BSR when the amount of data transmitted to base station 5 is within a threshold range of the buffer size reported in the previous BSR.

[0150] The method shown in FIG. 14 can also be called a method based on the "implicit amount of data sent."

[0151] The UE may store a variable corresponding to the unscheduled but reported buffer size for each LCG (e.g., "unscheduledbutReportedBufferSize"). This variable may be set (or reset) to the reported buffer size (e.g., the minimum possible size of the buffer size range corresponding to the index indicated in the BSR) when a BSR corresponding to the LCG is transmitted to the base station 5 (e.g., step S140). The value of the variable stored in the UE 3 may then be decreased (e.g., in step S141) based on the amount of data for the LCG transmitted to the base station 5. If the value of the variable is below a threshold (e.g., 0) and there is data in the corresponding buffer, the UE 3 decides to transmit a BSR to the base station 5.

[0152] Advantageously, therefore, the UE 3 can more reliably transmit a BSR to the base station 5 based on the amount of data that has been transmitted to the base station 5 since the last time a BSR was transmitted.

[0153] The amount of data buffered FIG. 15 illustrates how the UE 3 decides to send a BSR to the base station 5 based on the amount of data buffered at the UE 3.

[0154] In step S150, the UE 3 determines that the amount of data buffered at the UE 3 (e.g., for all LCGs or per LCG) is less than (or alternatively "less than") a configured threshold and therefore decides to send a BSR to the base station 5. The threshold for the UE 3 may be pre-configured at the UE 3 or may be received from another suitable entity in the network 1.

[0155] In step S151, the UE 3 transmits a BSR to the base station 5.

[0156] Advantageously, the UE 3 can therefore more reliably transmit a BSR to the base station 5 based on the amount of data buffered in the UE 3 .

[0157] UL Grant size FIG. 16 illustrates how the UE 3 decides to send a BSR to the base station 5 based on the UL grant size.

[0158] In step S160, the UE 3 determines whether the UL grant size (e.g., the UL grant size received from the base station 5) is greater than a threshold grant size, which may be pre-configured in the UE 3 or received from another suitable entity in the network 1.

[0159] When processing large amounts of data, several uplink dynamic grants may be required. Therefore, when the UL grant size is large, it is advantageous to have an updated and accurate BSR available to the base station 5 in order to allocate one or more appropriate UL grant sizes. Furthermore, when the UL grant size is large, the overhead of including a BSR in the corresponding transmission to the base station 5 is relatively small.

[0160] Therefore, advantageously, the UE 3 can more reliably transmit a BSR to the base station 5 based on the UL grant size, allowing the base station 5 to allocate a more appropriate UL grant size and reduce overall resource usage (e.g., radio resource usage). Furthermore, it has the advantage of being able to transmit a BSR when the relative overhead of the BSR is low.

[0161] Decision based on the size of buffered data and the buffer size reported in the previous BSR

[0162] FIG. 17 shows how UE 3 determines whether to send a BSR based on the amount of data in the UE's buffer and the buffer size reported (or "indicated") in the previous BSR.

[0163] In step S170, the UE 3 transmits a BSR to the base station 5.

[0164] In step S171, the UE 3 transmits data from the buffer to the base station 5 (eg, after receiving an UL grant from the base station 5).

[0165] In step S172, the UE 3 determines that the difference between the maximum buffer size reported in step S170 and the amount of data currently in the buffer is greater than (or equal to or greater than) a threshold, and therefore decides to send a BSR to the base station 5. In making this determination, the UE 3 takes into account the amount of data sent to the base station 5 in step S171. In other words, as shown in the following example, the UE 3 determines whether the difference between the value of the current buffer size that the base station 5 can calculate and the actual buffer size exceeds a threshold.

[0166] In step S173, the UE 3 transmits a BSR to the base station 5.

[0167] The "maximum reported buffer size" is the upper limit of the range indicated in the BSR. For example, referring to Figure 6, if the index reported in the previous BSR is 11, the maximum reported buffer size is 276 (the upper limit of the range of buffer sizes corresponding to that index).

[0168] If B represents the current amount of data in UE3's buffer and E represents the maximum possible buffer size based on the previously transmitted buffer size index (and based on the data transmitted from UE3 to base station 5 since the BSR was transmitted), UE3 determines whether EB (if E >= B) or BE (if B >= E) is greater than threshold T. For example, referring to Table 2 above, if UE3's buffer is initially empty and UE3 subsequently receives a packet of size 60,000 bytes in the buffer, the size of the buffer will be 60,000 bytes, and the index included in the BSR in step S170 will be "139" (because the buffer size is greater than 58,784 but less than or equal to 62,599). In this case, EB = 62,599 - 60,000 = 2,599. Therefore, if threshold T is 1,000, then EB > T. However, because the BSR is triggered to transmit based on data arrival, the UE does not yet transmit another BSR. Thereafter, when the UE is scheduled to transmit and transmits 50,000 bytes of data from the buffer in step S171, B=10,000 (E is calculated taking into account the amount of data to be transmitted, so E=62,599-50,000), E=12,599, and EB=2,599. Since EB is greater than the threshold value of 1,000, there is a relatively large difference between the buffer size calculated or estimated by the base station 5 and the actual buffer size, so the UE decides to send a new BSR to reduce the value of EB, or if more data, such as 2,000 bytes, has arrived in the buffer, B=30,000, E=12,599, and BE=17,401. Since BE is greater than the threshold value of 1,000, there is a relatively large difference between the buffer size calculated or estimated by the base station 5 and the actual buffer size, so when the base station 5 compares the actual buffer size with the actual buffer size, the UE decides to send a new BSR to reduce the value of BE.

[0169] In other words, the transmission of the BSR in step 173 is based on the difference between the actual amount of data buffered at UE3 and the amount of data buffered at UE3 that the base station 5 can determine or estimate (based on the previous BSR and subsequent UL data transmissions received from UE3).

[0170] Advantageously, the UE 3 can therefore provide a more accurate indication of buffer size to the base station 5, allowing the base station 5 to schedule UL resources more efficiently.

[0171] Figure 18 shows a modification of the method of Figure 17, in which UE3 determines that the difference between the minimum buffer size reported in step S170 and the amount of data currently in the buffer is greater than (or equal to or greater than) a threshold value.

[0172] Steps S180, S181, and S183 are the same as steps S170, S171, and S173, respectively.

[0173] In this example, UE3 uses the minimum buffer size reported in step S180. The "reported minimum buffer size" is the lower limit of the range indicated in the BSR. For example, referring to Figure 6, if the index reported in the previous BSR is 11, the maximum reported buffer size is 199 (the lower limit of the range of buffer sizes corresponding to that index).

[0174] If B represents the amount of data currently in UE3's buffer and E' represents the minimum possible buffer size based on the BSR sent in S180 (and based on the data sent from UE3 to base station 5 in S181), UE3 determines whether B-E' is greater than threshold T. For example, referring to Table 2 above, if UE3's buffer is initially empty and UE3 subsequently receives a packet 60,000 bytes in the buffer, the size of the buffer is 60,000 bytes, and the index included in the BSR in step S170 is "139" (because the buffer size is greater than 58,784 but less than or equal to 62,599). In this case, B-E' = 60,000 - 58,784 = 1,216. Therefore, if threshold T is 1,000, B-E' > T. However, because BSRs are sent based on data arrival, the UE does not yet send another BSR. Thereafter, when the UE is scheduled to transmit and transmits 50,000 bytes of data from the buffer in step S181, B=10,000, (E' is calculated taking into account the amount of data to be transmitted, so E'=58,784-50,000), E'=8,784, and B-E'=1,216. Because B-E' is greater than the threshold value of 1,000, there is a relatively large discrepancy between the buffer size calculated or estimated by base station 5 and the actual buffer size, and so the UE decides to transmit a new BSR to reduce the value of B-E'.

[0175] BSR difference information FIG. 19 shows an example in which the UE 3, in addition to transmitting a regular / periodical BSR, transmits an indication of the difference between the maximum possible buffer size based on the current regular / periodical BSR and the size of the current data in the buffer.

[0176] As shown, the UE sends a BSR to the base station 5 and also sends an indication of the difference between the maximum possible buffer size based on the BSR and the size of the current data in the buffer.

[0177] For example, if B represents the amount of data currently in the buffer and E represents the maximum possible buffer size based on the buffer size index in the BSR, the UE 3 may transmit a value of EB (in this example as a MAC CE) to the base station 5. The "maximum possible buffer size" is the upper limit of the range indicated in the BSR. For example, with reference to FIG. 6, if the index reported in the BSR is 11, the maximum reported buffer size is 276 (which is the upper limit of the range of possible buffer size values ​​corresponding to that index). The base station 5 can use the value of EB to more accurately determine the actual buffer size at the UE 3 (e.g., using the buffer size values ​​shown in Table 2 above), and therefore can schedule UL resources more efficiently.

[0178] Figure 20 shows a modification of Figure 19, in which the UE 3 transmits information indicating the difference between the actual amount of data in the buffer and the minimum possible amount of data based on the BSR index / buffer size contained in the BSR. For example, if B represents the current amount of data in the buffer and E' represents the minimum possible buffer size based on the buffer size index in the BSR, the UE 3 may transmit the value of BE (in this example as MAC CE) to the base station 5.

[0179] In the examples of Figures 19 and 20, the indication is sent as a MAC CE, but any other suitable type of transmission from the UE 3 to the base station 5 could be used instead.

[0180] The value of EB in the example of FIG. 19 and the value of BE in the example of FIG. 20 (both also referred to as "buffer size difference") may be transmitted (or triggered) when one or more of the following conditions are met: - Buffer size differences can be sent by the network - Regular / periodical / truncated BSR reports are triggered and included in the available uplink scheduling grants - The difference in buffer sizes is greater than a threshold (e.g., as determined by UE3) - The grant size of the regular / periodical / truncated BSR to be triggered and included in the available uplink scheduling grant is greater than a threshold.

[0181] Buffer Size Table As described above, a 5-bit table or an 8-bit table can be used with a corresponding 5-bit indication or an 8-bit indication in the buffer size field of the BSR. However, referring to FIG. 6, the range of buffer size values ​​becomes less precise as the BSR index (buffer size) becomes larger. For example, if a 5-bit buffer size field is used in the BSR report and the indicated index is 3, the buffer size value is greater than 14 bytes and less than or equal to 20 bytes, which corresponds to a range of 6 bytes. On the other hand, if the indicated index is 28, the buffer size value is greater than 55,474 bytes and less than or equal to 77,284 bytes, which corresponds to a range of 21,810 bytes. In other words, the granularity of the indicated buffer level becomes less precise as the index size becomes larger. However, it is desirable for the base station 5 to have a more precise range of buffer size values. If the UE uses an XR service that generates large data packets, the typical amount of data in the UE 3 buffer may be, for example, approximately 20 MB, and therefore it is advantageous to have a finer granularity for a buffer size value of approximately 20 MB.

[0182] Advantageously, an additional or new table is provided that maps BSR indexes to corresponding buffer size values ​​based on a particular service or device type. For example, for video streaming in an XR implementation, typical packet sizes may fall within a particular range. The table can be configured to set a narrower range (i.e., finer granularity) of buffer size values ​​for typical packet sizes, thereby improving the overall accuracy of the BSR for a particular service scenario (although with coarser granularity for some buffer sizes that are not close to the typical buffer size values).

[0183] FIG. 21 shows a modified version of the table of FIG. 6 in which the mapping between indexes and buffer size values ​​has been changed to provide finer granularity for buffer size values ​​between 4000 bytes and 5000 bytes (e.g., because typical packet sizes for a particular application or service are between 4000 and 5000 bytes). For example, if UE 3's actual buffer size is 4150 bytes, using the table of FIG. 6, the BSR would include an index value of 20, indicating a buffer size value greater than 3909 bytes and less than or equal to 5446 bytes (a range of 1537 bytes). On the other hand, using the table of FIG. 21, the BSR would include an index value of 18, indicating a buffer size value greater than 4100 bytes and less than or equal to 4200 bytes (a narrower range of 100 bytes). Thus, if the actual buffer size is between 4000 and 5000 bytes, the BSR will more accurately indicate the actual buffer size to base station 5, allowing the base station to more efficiently schedule UL resources.

[0184] The UE 3 may store or configure (e.g., receive from the base station 5) multiple mapping tables such as those shown in Figures 6 and 21, and the network may provide the UE 3 with an indication of which table to use to generate the BSR. For example, the network may provide an indication that the UE 3 should use a particular mapping table based on the type of UE 3, based on the services used or requested by the UE 3 (the UE 3 may use a particular table based on network configuration), and / or based on typical buffer sizes reported by one or more UEs 3. Alternatively, the UE 3 may select a table to use and provide an indication of the selected table to the base station 5.

[0185] Alternatively (or additionally), a new BSR MAC CE can be used in which more than 8 bits (e.g., 16 bits) are used to indicate the buffer size value, allowing more indices to be used to map to buffer size values, and each index to map to a narrower range of buffer sizes.

[0186] Grant Assistance Information Figure 22 shows an example in which a UE 3 sends Configured Grant (CG) / Scheduling Request (SR) assistance information to a base station. The assistance information is effective in addressing the problem of potential mismatch between data arrival timing at the UE 3 and CG location. This mismatch can be caused by, for example, jitter or non-integer periodicity (which can be difficult to predict). This problem can be at least partially ameliorated by providing UE-assisted CG configuration (especially CG timing).

[0187] The base station 5 may optimize the power consumption of one or more UEs by configuring so-called Discontinuous Reception (DRX) and / or Discontinuous Transmission (DTX) operation. Both DRX and DTX are based on reducing the duty cycle of the UE's 3 transceiver during active operation. In DRX mode, the base station 5 configures a cycle during which the UE 3 is operational for a certain period of time (called the "active time" or "on period"), and the base station 5 transmits all scheduling and paging information (for this UE) only during this period. Thus, the UE 3 can turn off its transceiver for the remainder of the DRX cycle (also called the "inactive time" or "off period"). In DTX mode, the UE 3 does not turn off its transceiver completely, but continues to monitor the Physical Downlink Control Channel (PDCCH) so that it can receive data from the base station 5 without undue delay. The longer the "off" period relative to the duty cycle, the greater the power savings. However, when operating in DRX and / or DTX mode, the UE 3 can only send / receive data during its active time, so the UE 3's data throughput will decrease in proportion to the power saving effect achieved. Jitter can cause a discrepancy between data arrival and the on period of the DRX cycle. The effect of jitter is that the exact arrival timing of a frame may be slightly earlier or later than expected due to random delays caused by the operation of the frame encoder in the edge server or the network transmission time in the core network.

[0188] A further problem is sometimes referred to as the "non-integer periodicity" of XR data packets (i.e., a non-integer number of subframes). Specifically, in the case of XR, the packet arrival rate is determined by the frame generation rate (e.g., 60 fps). Therefore, the average packet arrival period is given by the reciprocal of the frame rate (e.g., 1 / 60 fps = 16.6667 ms), without taking jitter into account (i.e., assuming a fixed video encoding time and network transmission delay). Therefore, the arrival time of a packet with index k (k = 1, 2, 3, ...) at the base station is given by k / F * 1000 [ms], where F is the given frame generation rate (per second). The difference between the non-integer arrival rate (16.6667 ms in this example) and the nearest period given in subframes (e.g., 17 ms) results in increasingly longer buffer times for subsequent packets. That is, each new data packet corresponding to a new frame can add (and accumulate) a delay of 0.3333 ms.

[0189] 22, in this example, in step S220, the UE 3 transmits assistance information regarding CG and / or SR to the base station 5. This assistance information may include information regarding traffic characteristics (assistance information is also simply referred to as "traffic information"). In step S221, the base station 5 sets the CG / SR based on the received assistance information.

[0190] Information related to traffic characteristics may include: - Periodic traffic timing information, represented as follows: --Periodicity / packet generation rate and traffic offset (e.g., packet arrival timing offset from the start of the corresponding period) - Possible jitter range - Desired / required settings, e.g.: --Uplink CG request, including periodicity (to match the arrival timing of periodic packets), offset, and optionally transport block (TB) size --SR settings including periodicity and offset (to match the arrival timing of periodic packets)

[0191] The UE may transmit the assistance information when requested by the network, or, for example, the UE 3 may transmit the assistance information periodically.

[0192] Therefore, the base station 5 can advantageously use the assistance information to provide improved settings of the CG / SR.

[0193] BSR Table The following describes improved methods of using a BSR table to indicate the amount of uplink data in one or more buffers of the UE 3. It will be understood that these improved methods may be combined with any of the methods described above (e.g., the methods for triggering BSR transmission) as needed. However, it will also be understood that the BSR in the methods described below may be triggered to be transmitted to the base station 5 using other suitable methods and is not limited to the methods for triggering BSR transmission described above.

[0194] An example of a MAC PDU is shown in Figure 23. A MAC PDU is a bit string with a byte-aligned length (e.g., a multiple of 8 bits). A MAC PDU contains one or more MAC sub-PDUs. Each sub-PDU may consist of either a MAC subheader only (including padding), a MAC subheader and a MAC SDU, a MAC subheader and a MAC CE, or a MAC subheader and padding. MAC SDUs are of variable size, and each MAC subheader corresponds to either a MAC SDU, a MAC CE, or padding.

[0195] As shown in the figure, a portion of a MAC PDU (also called a sub-PDU) contains a subheader and a corresponding SDU. Examples of fixed-size short / short truncated BSRs and variable-size long / long truncated BSRs are also shown. Also shown are sub-PDUs with an optional number of padding bits (which allows padding BSRs to be sent).

[0196] Figure 24 shows a modified version of Figure 5, where the subheader is also shown. As shown in Figure 24, the subheader and MAC CE each consist of 8 bits. The bits labeled "R" in the subheader are reserved bits (which may be set to 0). The LCID field contains an indication of the LCID (which is 59 or 61 in this example), which can be used to identify the format of the BSR (e.g., short BSR), as described above. The MAC CE is the same as described above with reference to Figure 5, the LCG ID field identifies the group of logical channels for which the buffer status is being reported, and the buffer size field identifies the total amount of uplink data available, e.g., using an index that identifies an entry in the lookup table of Figure 6 (e.g., based on the data volume calculation procedure).

[0197] Figure 25 shows a modified version of Figure 7, with the subheader also shown. The bits labeled "R" in the subheader are reserved bits (which may be set to 0). The bits labeled "F" are the format field, indicating the length "L" of the length field (e.g., use a value of 0 to indicate that the length field is 8 bits long, or a value of 1 to indicate that the length field is 16 bits long). The LCID field contains an indication of the LCID (60 or 62 in this example), which can be used to identify the format of the BSR (e.g., long BSR), as described above. The length field L indicates the length of the corresponding MAC SDU or MAC CE.

[0198] As described above, the base station uses a corresponding lookup table to determine the buffer size based on the indication in the buffer size field of the BSR received from the UE 3. One or more additional lookup tables may be generated, each mapping a different buffer size range to each index. The buffer size range may be based on the expected amount of data in the buffer (e.g., to improve the accuracy of BSR reports for buffer sizes close to typical buffer sizes). However, a lookup table that uses more code points (indexes) for a particular buffer size range to improve the accuracy of reports may still use fewer code points for another buffer size range, potentially reducing the accuracy of reports for other buffer sizes. In some examples, a particular lookup table (e.g., with higher accuracy for larger buffer size values) may be used when the buffer size is large, and a different lookup table (e.g., with higher accuracy for smaller buffer size values) may be used when the buffer size is small. However, the UE 3 must be able to determine which lookup table to use to generate the buffer size field of the BSR. Similarly, the base station 5 must be able to determine which lookup table corresponds to the buffer size field of the BSR transmitted from the UE 3. An improved method that addresses or at least partially alleviates this problem is described below. Dynamic BSR Table Switch

[0199] Below we describe an improved method that allows the lookup tables (also called BSR tables) used by UE3 to be dynamically changed.

[0200] The manner in which the UE 3 and the base station 5 exchange information regarding one or more BSR tables is shown in Figure 26. In step S260, the UE 3 sends an indication of one or more BSR tables that the UE 3 supports to the base station 5. This indication may be an indication of a particular BSR table that the UE 3 supports, or it may be an indication that the UE 3 can support a new BSR table configured by the network (e.g., by the base station 5).

[0201] In step S261, the base station 5 transmits BSR table configuration information to the UE 3. The BSR table configuration information includes an explicit indication of one or more BSR tables (or one or more additional BSR tables) to be used by the UE 3, or an implicit indication of one or more BSR tables (or one or more additional BSR tables) to be used by the UE 3. The BSR table configuration information includes an indication of whether the UE 3 uses one or more BSR tables preconfigured in the UE 3 or whether it uses one or more additional BSR tables configured by the base station 5. The BSR table configuration information includes an indication of an index / codepoint to be used as a BSR table and a corresponding buffer size range / interval. In other words, the base station 5 may transmit one or more BSR table parameters to the UE 3. The BSR table parameters may include an indication of a first buffer size interval and a step size (which can be used to generate remaining buffer size intervals associated with other indexes / codepoints), or the BSR table parameters may include only an explicit indication of the buffer size interval associated with each index / codepoint. It will be appreciated that one or more other suitable parameters or instructions may alternatively or additionally be used, For example, the base station 5 may transmit to the UE 3 a function (such as a distribution function) for generating the BSR table.

[0202] In step S262, the UE 3 generates a BSR for subsequent transmission to the base station 5. Advantageously, the UE 3 can determine which BSR table to use to generate the BSR. The UE 3 may be configured to use a specific BSR table received from the base station 5 if the UE 3's buffer size (the amount of uplink data in one or more buffers of the UE 3) is within a specific buffer size range, which may be set by the base station 5 using the BSR table configuration information received by the UE 3 in step S261. The UE 3 may be configured to use a specific BSR table if the UE 3's buffer size exceeds a threshold buffer size value or if the UE 3's buffer size is within a specific buffer size value range. The UE 3 may also be configured to use a default or pre-configured BSR table (such as the table described above with reference to FIG. 6) if one or more conditions for using an additional BSR table are not met.

[0203] In a particularly advantageous example, the UE 3 is configured to select the BSR table that provides the highest precision in the BSR report based on the reported buffer size. For example, the UE 3's buffer size may be 8 bytes, in which case it can be indicated using a first BSR table indicating that the buffer size is between 7 and 9 bytes, or using a second BSR table (e.g., index 1 is used in the table shown in FIG. 6) indicating that the buffer size is between 0 and 10 bytes. In this case, the UE 3 is configured to select the first BSR table to use to generate the BSR report because the range of possible buffer size values ​​indicated in the BSR is narrower (i.e., the precision of the BSR report is greater).

[0204] In step S263, the UE 3 transmits a BSR to the base station 5.

[0205] The UE 3 may transmit an indication of the BSR table used to generate the BSR to the base station 5. The indication of the BSR table used to generate the BSR may be transmitted to the base station 5 together with the corresponding BSR, or may be transmitted separately from the BSR in a separate transmission. Alternatively, it may not be necessary to transmit the indication of the BSR table used to generate the BSR to the base station 5 (e.g., if the rules used by the UE 3 to determine which BSR table to use are also stored in the base station 5 and the base station 5 can determine which BSR was used by the UE 3). The indication of the BSR table used to generate the BSR may be an explicit or implicit indication of a particular BSR table, or may be an indication of whether the UE 3 used a default BSR table or a BSR table received from the base station 5.

[0206] An indication of the BSR table used to generate the BSR may be sent to the base station using one or more bits in the subheader of the corresponding MAC CE. For example, in the case of a short BSR or a short truncated BSR, the indication may be sent to the base station 5 using one or both of the reserved fields (labeled "R") in the subheader shown in Figure 24. Similarly, in the case of a long BSR or a long truncated BSR, the reserved bit and / or the format field ("F") shown in Figure 25 may be used for the indication of the BSR table used to generate the BSR. One or more bits in the length field ("L") may be used alternatively or additionally (as not all bits in the length field are necessary to indicate the length of the MAC CE). For example, if the reserved bit, the format field, and one bit in the length field are used to indicate the BSR table used to generate the BSR, three bits may be used together to indicate a total of eight possible values.

[0207] Therefore, advantageously, the UE 3 can determine which BSR table to use to generate the BSR, improving the accuracy of the buffer size indication, and the base station 5 can determine which BSR table the UE 3 will use to generate the BSR.

[0208] In the above example, an indication is provided in the MAC CE subheader indicating which BSR table to use to generate the BSR, so that the buffer size for each LCG is generated using the same BSR table (or, for example, if the indication in the subheader indicates that the UE3 is using a set of default BSR tables according to a pre-configured set of rules). Below, we will describe a further improved method that allows for greater flexibility in the BSR tables that the UE3 can use to report each buffer size, by allowing each LCG to be provided with an indication indicating which BSR table was used to generate the BSR.

[0209] Figure 27 shows an example of a MAC CE that can be used to send an indication of the BSR table used to generate the BSR. In this example, a modified version of the MAC CE of Figure 8 is shown. The MAC CE includes the LCG ID and buffer size as described above with reference to Figure 8. However, advantageously, in this example, the MAC CE also includes one or more bits to indicate the BSR table associated with the index / codepoint identified in the buffer size field. The BSR table indication field may be either one bit or multiple bits (e.g., depending on the number of BSR tables that the UE can use to generate the BSR).

[0210] FIG. 28 illustrates a further example of a MAC CE that may be used to transmit an indication of the BSR table used to generate the BSR. In this example, similar to FIG. 7 above, the buffer sizes of multiple corresponding LCGs are reported. Advantageously, however, in this example, an indication of the BSR table (in this example, fields labeled T: T1, T2, ...) associated with the index / codepoint identified in the buffer size field is provided. The BSR table indication in field T1 indicates the BSR table associated with the buffer size 1 index (i.e., the lookup table used to identify the data size of one or more buffers using the index in the buffer size 1 field). Similarly, the BSR table indication in field T2 indicates the BSR table associated with the buffer size 2 index. It will be appreciated that in the example of FIG. 28, some of the buffer size fields are spread across multiple rows in the table. For example, one bit of the buffer size 2 field is in the row adjacent to field T2, and the remaining four bits are in the subsequent row (similarly, the buffer size 3 and buffer size m fields are split across multiple rows, but each comprise five bits).

[0211] In this example, "m" buffer sizes are reported, and the BSR table indication in field Tm indicates the BSR table associated with the index of buffer size "m". Advantageously, the UE 3 can indicate the BSR table to be used by the UE 3 for each buffer size field (e.g., for each LCG). Thus, the UE 3 may use a different BSR table for each buffer size field. For example, the UE 3 can select the BSR table that most accurately indicates the buffer size to generate an index corresponding to each buffer size field, and the base station 5 can determine the BSR table that the UE 3 uses for each buffer size field.

[0212] In the example of Figure 28, each buffer size field uses 5 bits, but it will be understood that this is not necessarily limited to this. For example, Figure 29 shows a modified MAC CE that uses 8 bits for the buffer size field (and therefore the corresponding BSR table uses an 8-bit index).

[0213] Figure 30 shows a further example of how the MAC CE may be used to indicate to the base station 5 the BSR table that the UE 3 will use. In the example shown in Figure 30, six bits are used for the buffer size field. While six bits are used, it will be appreciated that a fewer number of bits may be used to indicate the lookup table index within the six-bit field. For example, the six-bit field may include one ignored bit (e.g., set to 0) followed by five bits used to identify the index of a five-bit lookup table (such as the table shown in Figure 6). In the example of Figure 30, for each buffer size field, two bits are used for the "T" field, which are used to indicate the BSR table that the UE 3 will use.

[0214] Figure 31 shows a further example where the buffer size fields are variable length. As shown, buffer size 1 is 8 bits long, buffer size 2 is 5 bits long, and buffer size m is 10 bits long.

[0215] Figure 32 shows a further example in which indications of the BSR table to be used by UE3 (T7-T0) are provided in a contiguous bit string following the fields identifying the LCGs (LCG7-LCG0). In this example, all of the indications of the BSR table to be used by UE3 (T7-T0) are placed before the corresponding set of buffer size fields and after the corresponding LCG field (e.g., indicating whether or not that LCG includes a buffer size field).

[0216] In the examples of Figures 28 to 32, one or two bits are used in the "T" field (which indicates the BSR table used by UE3), but this is not necessarily limited to this and any other suitable number of bits may be used instead.

[0217] eLCID FIG. 33 shows an example in which the subheader of the example of FIG. 24 has been modified to include an eLCID. As mentioned above, the eLCID is 8 bits in this example and can be used to extend the LCID field. Advantageously, the eLCID can be used as an indication to the base station 5 of the BSR table or MAC CE format that the UE 3 uses to generate the buffer size field of the corresponding MAC CE. Bits in the eLCID can be used to indicate one or more BSR tables used by the UE 3. The eLCID may explicitly indicate one or more BSR tables used by the UE 3, or it may implicitly indicate one or more BSR tables used by the UE 3 (e.g., by indicating the format of the corresponding MAC CE). The eLCID may also be used to indicate that the UE 3 used a default or pre-configured BSR table (or set of BSR tables) to generate the buffer size field of the corresponding MAC CE. The example shown in FIG. 33 may be used, for example, for a (fixed-size) short BSR or short truncated BSR format.

[0218] Figure 34 shows a further example where the subheader additionally includes a length field "L", which indicates the length of the corresponding MAC CE. The example shown in Figure 34 may be used, for example, for (variable-sized) long BSR or long truncated BSR formats.

[0219] Same LCID but different MAC CE format Below we will describe an example where the UE reuses the same LCID but switches to using a new MAC CE format once an additional BSR table is configured by the base station 5.

[0220] 35, in this example, UE3 is in an RRC connected state. In step S351, UE3 transmits one or more BSRs to base station 5 (for example, using the BSR format shown in FIG. 5 or FIG. 7).

[0221] The first option includes steps S352 and S353. In step S352, the base station 5 sends an RRC reconfiguration message to the UE 3. The RRC reconfiguration message includes an indication of one or more additional BSR tables to be used by the UE 3. As described above, the indication of the BSR table may include a first buffer size interval and a step size (which the UE 3 can use to determine all fields of the BSR table), or the mapping between each index of the lookup table and the corresponding buffer size interval may be explicitly indicated. Based on the new BSR received from the base station 5, the UE 3 determines to use the BSR table received in step S352 for subsequent BSRs to be sent to the base station 5. In other words, in the first option, when the UE 3 receives the new BSR table from the base station 5, the UE 3 determines to use the new BSR table to generate subsequent BSRs to be sent to the base station. The RRC reconfiguration information may include an indication of a MAC CE format to use when sending the BSR to the base station 5. The indicated MAC CE format may be, for example, any of the MAC CE formats shown in Figures 27 to 32. For example, the MAC CE format in Figure 32 may be used, which includes an indication of each BSR table used to generate each buffer size field.

[0222] In step S353, the UE 3 sends a BSR to the base station 5, which is generated using one or more BSR tables received from the base station 5 in step S352. The UE 3 may indicate the BSR type (e.g., short BSR, short truncated BSR, long BSR, or long truncated BSR) using the same LCID as used for the BSR sent in step S351, even if the corresponding MAC CE is using a new format received from (or indicated by) the base station in step S352.

[0223] The second option comprises steps S354 to S356. In step S354, the UE 3 receives one or more BSR tables from the base station 5 as described above with reference to step S352.

[0224] In step S355, the base station 5 transmits BSR format information to the UE 3. The BSR format information includes an indication of whether the UE 3 should use one or more BSR tables received in step S354. In other words, the BSR format information includes information for activating or deactivating the use of the BSR table received in step S354 to generate the corresponding BSR to be sent to the base station 5. Thus, advantageously, the base station 5 can control whether the UE 3 should use the BSR table transmitted to the UE 3 in step S354. Furthermore, more precise control by the base station 5 over the BSR table used by the UE 3 ensures that the base station 5 and the UE 3 maintain a common understanding of which BSR table and MAC CE format are used, reducing the risk of decoding problems at the base station 5 (e.g., if the base station 5 tries to map the MAC CE buffer size field to a buffer size in bytes using a BSR table, but the UE 3 uses a different BSR to generate the buffer size field).

[0225] In this example, the BSR format information includes an indication that the new BSR table indicated to UE3 in step S354 is to be used (activated), and in step S356, UE3 transmits to base station 5 a BSR generated using the one or more BSR tables received from base station 5 in step S354. UE3 may indicate the BSR type (e.g., short BSR, short truncated BSR, long BSR, or long truncated BSR) using the same LCID used for the BSR transmitted in step S351, even if the corresponding MAC CE is using the new format received from (or indicated by) the base station in step S354.

[0226] In the example described above with reference to Figure 35, an RRC reconfiguration message is used to indicate the new BSR table (and corresponding MAC CE format) to UE3, but any other suitable transmission from base station 5 to UE3 may be used instead.

[0227] Extended BSR Table Below, an example is described in which an additional BSR table is used to extend another BSR table.

[0228] Figure 36 shows an example of a primary BSR table and an extended BSR table. In this example, the primary BSR table is the 5-bit table shown in Figure 6 with indexes from 0 to 31. The extended table uses an additional set of indexes from 32 to 63. Advantageously, the use of the extended table can improve the accuracy of the reported buffer sizes for a particular buffer size range.

[0229] In this example, the buffer size values ​​in the extended table correspond to indexes 18-22 in the first table. Therefore, the UE 3 does not use indexes 18-22, but instead uses the corresponding indexes in the extended table. In other words, the UE 3 determines which table to use based on the buffer size reported in the BSR. For example, to indicate a buffer size value of 3565, the UE 3 uses index 37 (which corresponds to buffer sizes 3561-3872 and has a range of 311 values) rather than index 19 (which corresponds to buffer sizes 2807-3909 and has a range of 1103 values). Therefore, the UE 3 can indicate a more accurate buffer size in the BSR it sends to the base station 5.

[0230] In the example of Figure 36, both the first table and the extension table have 32 elements (32 indexes and corresponding buffer size intervals), but this is not necessarily limited to this. The extension table does not necessarily have to have the same number of elements as the first table, and the number of elements does not necessarily have to be 32. Any appropriate number of indexes can be used for either table. In this example, because the total number of indexes is increased from 32 to 64, the buffer size field of the MAC CE can indicate the index using a 6-bit field. As a further example, if the first table is the 8-bit table above (with indexes from 0 to 255), the extension table can have indexes from 256 to 511 (for example). In this case, a 9-bit buffer size field can be used to indicate the index within the MAC CE. As another example, if the first table is the 8-bit table above (with indexes from 0 to 255), the extension table can have indexes from 256 to 1023, in which case a 10-bit buffer size field can be used to indicate the index within the MAC CE (for example, as shown by buffer size m in Figure 31).

[0231] The extended table may be transmitted or indicated to the UE 3 using any of the methods described above. The format of the extended table (e.g., the buffer size interval mapped to each index, or the number of indexes) may be configured by the network. For example, in step S352 of FIG. 35, the extended table may be transmitted or indicated to the UE 3 (and use of the extended table by the UE 3 may be activated / deactivated as described in step S355 above). Alternatively, the extended table may be pre-configured in the UE 3. Similarly, the BSR table to be used by the UE 3 may be indicated to the base station 5 using any of the methods described above (e.g., using one or more bits in the corresponding subheader, such as the reserved bits shown in FIG. 24, or using one or more bits in the MAC CE, e.g., as shown in FIGS. 27-32).

[0232] Semi-static BSR Table Switch The following describes an example in which the base station 5 semi-statically activates / deactivates one or more BSR tables.

[0233] As described above, the UE 3 may send an indication to the base station 5 indicating that the UE 3 supports one or more additional BSR tables (e.g., in addition to a default BSR table preconfigured in the UE 3), or the base station may send the additional BSR tables (or an implicit indication of the BSR tables) to the UE 3. For example, as described above, the base station 5 may send an explicit mapping between each index of the table and a corresponding buffer size interval, or the base station 5 may provide the UE 3 with information for generating the BSR table (e.g., a starting buffer size value and a step size, or alternatively a set of functions or equations may be provided).

[0234] In this example, the base station is configured to activate or deactivate the use of the additional BSR table, similar to step S355 of Figure 35. However, in this example, the base station 5 activates / deactivates the use of the additional BSR table using lower layer signaling, for example using MAC CE or physical signaling.

[0235] If no additional tables are configured or deactivated in the UE 3, the UE 3 may configure the buffer size field of the MAC CE using default or pre-configured BSR tables available in the UE 3. The default or pre-configured BSR tables are also referred to as legacy tables. However, if additional tables are configured and activated in the UE 3 (e.g., in response to receiving a MAC CE from the base station 5 indicating that additional tables should be used), the UE 3 uses one or more additional BSR tables to configure the buffer size field of the MAC CE.

[0236] Static BSR Table Switch The following describes an example in which the base station 5 statically activates / deactivates one or more BSR tables.

[0237] As described above, the UE 3 may send an indication to the base station 5 indicating that the UE 3 supports one or more additional BSR tables (e.g., in addition to a default BSR table preconfigured in the UE 3), or the base station may send the additional BSR tables (or an implicit indication of the BSR tables) to the UE 3. For example, as described above, the base station 5 may send an explicit mapping between each index of the table and a corresponding buffer size interval, or the base station 5 may provide the UE 3 with information for generating the BSR table (e.g., a starting buffer size value and a step size, or alternatively a set of functions or equations may be provided).

[0238] In this example, the base station is configured to activate or deactivate the use of the additional BSR table, similar to step S355 of Figure 35. However, in this example, the base station controls the activation / deactivation by sending a transmission to the UE 3 that includes a BSR table setup indication or a BSR table release indication.

[0239] 37 shows an example in which a base station uses a BSR table setup / release message to control activation / deactivation of use of a BSR table by a UE 3. In step S371, the base station sends a BSR table setup message to the UE 3. The BSR table setup message includes an instruction indicating one or more BSR tables to be used by the UE 3. The BSR table setup message also includes, but is not necessarily limited to, the configuration of the BSR table to be used (e.g., a set of indexes and corresponding buffer size intervals, which may be indicated explicitly or implicitly) (e.g., if a BSR table is already available in the UE 3).

[0240] In step S372, the UE 3 sends one or more BSRs to the base station 5 and sets the buffer size field using the one or more BSR tables indicated / activated in step S371. It will be appreciated that the MAC CE format may be any of the MAC CE formats described above (and the BSR table may also be in any of the formats described above).

[0241] In step S373, the base station 5 sends a BSR table release message to the UE 3. The BSR table release message indicates that the UE 3 will no longer use one or more associated BSR tables (e.g., the tables activated in step S371). In this example, after receiving the transmission of step S373, the UE 3 reverts to using one or more default or pre-configured (or legacy) BSR tables and sends the corresponding BSR(s) in step S374.

[0242] 37, the BSR table setup message and the BSR table release message are shown as dedicated messages, but are not necessarily limited to this. Alternatively, the information in the BSR table setup message may be included in any suitable information element in any other suitable transmission from the base station 5 to the UE 3. Similarly, the information in the BSR table release message may be included in any suitable information element in any other suitable transmission from the base station 5 to the UE 3.

[0243] More BSR Tables Further examples of improved BSR tables are described below.

[0244] As noted above, the size of the buffer size intervals mapped to each index in the table may vary, and therefore the accuracy of the reported buffer sizes may also vary. Also, as noted above, the BSR table may be configured to have smaller buffer size intervals for certain buffer size ranges (e.g., some indexes may correspond to 250-byte buffer size intervals and other indexes may correspond to 100-byte buffer size intervals, as shown in Figure 21).

[0245] In a particularly advantageous example, the BSR table is configured to provide increased precision for multiple buffer size ranges. FIG. 38 shows an example BSR table with increased precision for both low buffer size values ​​and a further range of buffer size values ​​(which may represent, for example, a typical or expected amount of data in the buffer). In this example, a buffer size interval of 2 bytes is used for buffer size values ​​between 0 and 10 bytes. Between 10 and 510 bytes, a lower precision is used because the buffer size interval size is 100 bytes. However, between 510 and 550 bytes, there is a second region of increased precision, where the buffer size interval size is 10 bytes. For buffer sizes above 550 bytes, a larger buffer size interval of 300 bytes is used. Thus, advantageously, increased precision can be provided for both low buffer size values ​​and a further range of buffer size values. This type of setting is particularly advantageous because it provides improved accuracy at low buffer sizes that may occur when transmitting uplink data (where the fractional uncertainty becomes very large if the buffer size interval is large), and further areas of improved accuracy can be set for typical or expected buffer sizes that may occur. For example, if the typical or expected size of data in one or more buffers is 530 bytes, the table in Figure 38 can be used. The typical or expected buffer size may be, for example, a typical pack size of XR data.

[0246] In the example of Figure 38, 32 indices (corresponding to 5 bits) are used, but this is not necessarily a limitation: any other suitable number of indices (and corresponding number of bits in the MAC CE buffer size field) may be used instead.

[0247] User Equipment FIG. 39 is a schematic block diagram illustrating the main components of the UE 3 shown in FIG.

[0248] As shown, the UE 3 includes transceiver circuitry 310 capable of transmitting signals to and receiving signals from a base station 5 via one or more antennas 330 (e.g., including one or more antenna elements). The UE 3 includes a controller 370 that controls the operation of the UE 3. The controller 370 is associated with a memory 390 and is connected to the transceiver circuitry 310. Although not necessary for the operation of the UE 3, the UE 3 may include all of the usual functionality of a traditional UE 3 (e.g., a user interface 350, such as a touchscreen / keypad / microphone / speaker, that allows for direct user control and interaction), which may be provided by any or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in the memory 390 and / or downloaded, for example, via a communications network or a removable data storage device (RMD).

[0249] Controller 370, in this example, is configured to control the overall operation of UE 3 via program or software instructions stored in memory 390. As shown, these software instructions include, among other things, an operating system 410 and a communications control module 430.

[0250] The communications control module 430 is operable to control communications between the UE 3 and its one or more serving base stations 5 (and other communications devices connected to the base stations 5, e.g., other UEs and / or core network nodes). The communications control module 430 is configured to perform overall processing of uplink communications over associated uplink channels (e.g., physical uplink control channel (PUCCH), random access channel (RACH), and / or physical uplink shared channel (PUSCH)), including both dynamic signaling and semi-static signaling (e.g., SRS). The communications control module 430 is also configured to perform overall processing of reception of downlink communications over associated downlink channels (e.g., physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH)), including both dynamic signaling and semi-static signaling (e.g., CSI-RS). The communication control module 430 is responsible for, for example, determining where to monitor downlink control information (such as the CSS / USS to monitor, CORESET, and location of associated PDCCH candidates), determining which resources (including interleaved resources and resources subject to frequency hopping) the UE 3 will use to transmit / receive UL / DL communications, managing frequency hopping at the UE side, determining how to configure slots / symbols (e.g., for UL, DL, or SBFD communications), determining which bandwidth portion(s) are configured for the UE 3, determining how uplink transmissions should be coded, applying SBFD-specific communication configurations appropriately, etc. The communication control module 430 may be configured to control communications according to any of the methods described above (e.g., any of the methods of transmitting a BSR to the base station 5 described above).

[0251] The BSR module 440 is responsible for generating a BSR (e.g., as part of a MAC CE) and determining whether to transmit the BSR to the base station 5. The BSR module 440 may also be responsible for generating and transmitting other appropriate information related to the BSR. The BSR module 440 may be configured to perform any of the methods described above, including generating or transmitting a BSR.

[0252] base station FIG. 40 is a schematic block diagram illustrating the main components of a base station 5 of the communication system 1 shown in FIG. 1. As shown, the base station 5 comprises a transceiver circuit 510 for transmitting signals to and receiving signals from communication devices (such as UE 3) via one or more antennas 530 (e.g., single or multi-panel antenna arrays / large-scale antennas), and a core network interface 550 (e.g., including N2, N3, and other reference points / interfaces) for transmitting signals to and receiving signals from network nodes in the core network 7. Although not shown, the base station 5 may connect to other base stations via an appropriate interface (e.g., the so-called "Xn" interface in NR). The base station 5 comprises a controller 570 that controls the operation of the base station 5. The controller 570 is associated with a memory 590. Software may be pre-installed in the memory 590 and / or downloaded via the communication network 1 or from a removable data storage device (RMD), etc. The controller 570 is configured, in this example, to control the overall operation of the base station 5 by means of program or software instructions stored in memory 590 .

[0253] As shown, these software instructions include, among other things, an operating system 610 and a communications control module 630 .

[0254] The communications control module 630 is operable to control communications between the base station 5 and the UEs 3 and other network entities connected to the base station 5. The communications control module 630 is configured to generally control the reception and decoding of uplink communications over associated uplink channels (e.g., physical uplink control channel (PUCCH), random-access channel (RACH), and / or physical uplink shared channel (PUSCH)), including both dynamic signaling and semi-static signaling (e.g., SRS). The communications control module 630 is also configured to generally handle the transmission of downlink communications over associated downlink channels (e.g., physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH)), including both dynamic signaling and semi-static signaling (e.g., CSI-RS). The communications control module 630 is responsible for managing full-duplex communications (e.g., SBFD), including separating UL and DL communications over different physical antenna elements, if necessary. The communication control module 630 is responsible for, for example, determining configuration locations for the UE 3 to monitor for downlink control information (such as the locations of CSS / USS, CORESET, and associated PDCCH candidates to monitor), determining resources (including interleaved resources and resources subject to frequency hopping) to be scheduled for transmission / reception of UL / DL communications by the UE, managing frequency hopping at the base station side, configuring slots / symbols appropriately (e.g., for UL, DL, or SBFD communications), configuring one or more bandwidth portions for the UE 3, providing related configuration signaling to the UE 3, etc. The communication control module 630 may be configured to control communications according to any of the above-mentioned methods (e.g., sending information to activate / deactivate a BSR table in the UE 3 or to receive a BSR from the UE).

[0255] The BSR module 650 is responsible for sending / receiving any BSR-related information sent / received to / from the UE 3, e.g., as part of any of the methods described above. For example, the BSR module 650 may generate an indication that the UE 3 should send a BSR to the base station 5.

[0256] The uplink (UL) scheduling module 670 is responsible for generating UL grants for data transmissions from the UE 3 to the base station 5, for example as part of any of the methods described above. The base station may schedule or allocate resources for UL transmissions to the UE 3 based on the BSR received from the UE 3.

[0257] Core Network Nodes / Functions Figure 41 is a block diagram illustrating the main components of a core network node or function, such as the AMF, CPF, UPF, SMF, OAM, etc. As shown, the core network function includes a transceiver circuit 710 operable to transmit signals to and receive signals from other nodes (including UE 3, base stations 5, and other core network nodes) via a network interface 720. A controller 730 controls the operation of the core network function in accordance with software stored in memory 740. The software may be pre-installed in memory 740 and / or may be downloaded via the communication network 1 or from, for example, a removable data storage device (RMD). The software includes, among other things, an operating system 750 and a communication control module 760.

[0258] The communications control module 760 is responsible for handling (generating / sending / receiving) signaling between core network functions and other nodes such as UE 3, base stations 5, and other core network nodes (e.g., as part of any of the methods described above).

[0259] Modifications and Substitutions As will be appreciated by those skilled in the art, several modifications and alternatives to the above-described embodiments are possible while having the benefit of the disclosure contained herein.

[0260] Although the BSR has been described above with reference to uplink data for XR, it is not necessarily limited to this, and instead may be applied to other suitable methods of reporting buffer status.

[0261] Although some of the above examples report buffer sizes per LCG, this is not necessarily the case, and buffer sizes may instead be reported per LCH or at a finer granularity.

[0262] It will be appreciated that any of the above methods may be combined, as needed. For example, the extended BSR table described with reference to FIG. 36 or the BSR table described with reference to FIG. 38 may be used in the semi-static BSR table switching method described above or the static BSR table switching scheme (shown in FIG. 37). In fact, the extended BSR table or the BSR table of FIG. 38 is particularly advantageous when used in the semi-static BSR table switching method or the static BSR table switching method because these tables are particularly suited for use in static or semi-static configuration methods, as they can provide relatively small buffer size intervals (i.e., increased precision) for both low buffer sizes (e.g., typical buffer sizes for XR data) and a range of other buffer sizes.

[0263] The new BSR table and the extended BSR table have been described above. The new BSR table and the extended BSR table may be configured (or reconfigured) per LCG, per LCH, or per data radio bearer (DRB). The size of each buffer size field in the MAC CE corresponding to different LCGs / LCHs / DRBs may be different, or may be provided in one long / long truncated MAC CE. However, the length of each buffer size field can nevertheless be determined and decoded by the base station 5 (e.g., using information provided in the MAC CE or the corresponding subheader, as described above).

[0264] In the MAC CE examples shown in Figures 28-32, the fields indicating the BSR table used by the UE 3 (such as the "T" fields T7-T0 in Figure 32) may be used if the UE 3 uses a default or pre-configured (e.g., legacy) BSR table. In this case, the fields indicating the BSR table used by the UE 3 for a particular LCG / LCH / DRB may simply indicate that the default / pre-configured / legacy BSR table was used.

[0265] In any of the above examples, the MAC CE may include data volume information associated with the delay information (e.g., remaining time for uplink transmission of uplink data). The delay information may be reported depending on the BSR format. If the BSR format is dynamically selected (e.g., by the UE), the UE may always report the delay information each time it selects a new BSR format. Alternatively, the UE 3 may follow an RRC configuration procedure or an RRC preconfiguration procedure controlled by the base station 5. For example, the UE may select a new BSR format, and if the RRC configuration message indicates that the UE 3 includes the delay information (or indicates that the UE 3 conditionally includes the delay information depending on one or more conditions), the UE 3 may include the delay information. If the base station 5 explicitly instructs the base station 5 to switch / activate / deactivate the BSR table (e.g., according to any of the above methods), the UE 3 may be configured to always report the delay information each time the base station 5 instructs the base station 5 to use / activate the BSR table. Alternatively, the UE 3 may explicitly instruct whether to report the delay information.

[0266] For example, for clarity, although specific terms for cellular communication generations (e.g., 2G, 3G, 4G, 5G, 6G, etc.) may be used to refer to particular communication entities, the technical features described for a particular entity are not limited to devices of that particular communication generation, and it will be understood that these technical features may be implemented in any functionally equivalent communication entity regardless of the terms used to refer to them.

[0267] In the above description, the UE and base station are described for ease of understanding as having several separate functional components or modules. While these modules may be provided in this manner in certain applications, such as when an existing system is modified to implement the present disclosure, in other applications, such as systems designed from the beginning with the features of the present invention in mind, these modules may be incorporated into an overall operating system or code, and therefore may not be identifiable as separate entities.

[0268] In the above embodiments, several software modules have been described. As will be understood by those skilled in the art, these software modules may be provided in compiled or uncompiled form, and may be supplied as signals via a computer network or via a recording medium. Furthermore, the functions performed by some or all of these software modules may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred to facilitate updating the functions of the base station or UE.

[0269] Each controller may comprise any suitable form of processing circuitry, including, for example, but not limited to, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuitry, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control buses, data buses and / or address buses), direct memory access (DMA) functionality, hardware or software-implemented counters, pointers, and / or timers, etc. Various other modifications will be apparent to those skilled in the art and will not be described in further detail herein.

[0270] A base station may be configured as a "distributed" base station with a central unit "CU" and one or more individual distributed units (DUs).

[0271] User equipment (or "UE," "mobile station," "mobile device," or "wireless device") in this disclosure is an entity connected to a network via an air interface.

[0272] It should be noted that the present invention is not limited to dedicated communication devices, but may be applied to any device having the communication function described below.

[0273] The terms "user equipment" or "UE" (as used in 3GPP), "mobile station," "mobile device," and "wireless device" are generally intended to be synonymous with each other and include standalone mobile stations such as terminals, cell phones, smartphones, tablets, cellular IoT devices, IoT devices, and machines. It will be understood that the terms "mobile station" and "mobile device" also include devices that remain fixed for extended periods of time.

[0274] The UE may be, for example, production or manufacturing equipment and / or energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal generators, nuclear generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or application systems thereof, tools, dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing equipment, printing and / or related machinery, paper processing machinery, chemical machinery, mining and / or construction machinery and / or related equipment, agricultural, forestry and / or fishing machinery and / or implements, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems of any of the foregoing equipment or machinery, etc.).

[0275] The UE may be, for example, a transportation device (such as a railcar, automobile, motorcycle, bicycle, train, bus, cart, rickshaw, ship or other water vehicle, aircraft, rocket, satellite, drone, balloon, etc.), or may be, for example, an information and communications device (such as an electronic computer and related devices, communication and related devices, electronic components, etc.).

[0276] The UE may be, for example, refrigeration machines, refrigeration machine applications, commercial and / or service industry equipment, vending machines, automated service machines, office machines or equipment, consumer electronic devices and appliances (e.g., audio equipment, video equipment, loudspeakers, radios, televisions, microwave ovens, rice cookers, coffee makers, dishwashers, washing machines, dryers, electronic fans or related equipment, vacuum cleaners, etc.).

[0277] The UE may be, for example, an electrical application system or device (such as an x-ray system, a particle accelerator, a radioisotope device, a sonic device, an electromagnetic application device, an electronic power application device, etc.).

[0278] The UE may be, for example, an electronic lamp, lighting fixture, measuring, analytical, testing, or surveying or sensing equipment (e.g., smoke detectors, motion sensors, radio frequency tags, etc.), a watch or clock, laboratory equipment, optical equipment, medical equipment and / or systems, weapons, tableware, hand tools, etc.

[0279] The UE may be, for example, a personal digital assistant or related device with wireless capabilities (such as a wireless card or module designed to be attached to or inserted into another electronic device (e.g., a personal computer, electrical measurement equipment)).

[0280] The UE may be a device or part of a system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below in relation to the "internet of things (IoT)."

[0281] Internet of Things devices (or "things") are equipped with appropriate electronics, software, sensors, network connectivity, etc., and are able to collect and exchange data among themselves and with other communicating devices. IoT devices may comprise automated machines that follow software instructions stored in their internal memory. IoT devices may operate without the need for human supervision or operation. IoT devices may also remain stationary or inactive for long periods of time. IoT devices may be implemented as part of (typically) stationary equipment. IoT devices may be integrated into non-stationary equipment (e.g., vehicles) or attached to animals or people being monitored / tracked.

[0282] It will be understood that IoT technology can be implemented in any communication device that can connect to a communication network and send / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in a memory.

[0283] It will be appreciated that IoT devices are also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) devices. It will be appreciated that a UE may support one or more IoT or MTC applications. Some examples of MTC applications are shown in the table below. This list is not exhaustive but is intended to illustrate some examples of machine-type communication applications. [Table 4]

[0284] Applications, services, and solutions may include Mobile Virtual Network Operator (MVNO) services, emergency wireless communication systems, Private Branch eXchange (PBX) systems, PHS / digital cordless communication systems, Point of sale (POS) systems, advertise calling systems, Multimedia Broadcast and Multicast Service (MBMS), Vehicle to Everything (V2X) systems, train radio systems, location-related services, disaster / emergency wireless communication services, community services, video streaming services, femtocell application services, Voice over LTE (VoLTE) services, billing services, wireless on-demand services, roaming services, activity monitoring services, carrier / communication network selection services, function restriction services, Proof of Concept (PoC) services, personal information management services, ad hoc networks / Delay Tolerant Networking (DTN) services, and the like.

[0285] Furthermore, the above-mentioned UE categories are merely examples of application of the technical ideas and embodiments described in this specification. Of course, these technical ideas and embodiments are not limited to the above-mentioned UEs, and various modifications are possible.

[0286] Many other variations will be apparent to those skilled in the art and will not be described in further detail here.

[0287] Many other variations will be apparent to those skilled in the art and will not be described in further detail here.

[0288] For example, all or part of the embodiments disclosed above can be described as follows, but are not limited to these. (Appendix 1) 1. A method for a user equipment (UE), comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data, and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; determining, based on an amount of uplink data in one or more buffers of a UE, whether to use a first table to determine a first index indicating a first range of an amount of uplink data in one or more buffers of the UE, or to use a second table to determine a second index indicating a second range of an amount of uplink data in one or more buffers of the UE; determining the first index or the second index based on an amount of the uplink data in one or more buffers of a UE; sending an indication of the first index or the second index to an access network node; if the UE sends an indication of the first index to the access network node, sending an indication to the access network node indicating that the first table was used to generate the first index; If the UE sends an indication of the second index to the access network node, sending an indication to the access network node indicating that the second table was used to generate the second index; A method comprising: (Appendix 2) the second table, or information for generating the second table in the UE, receiving from the access network node; The method described in Appendix 1. (Appendix 3) determining, if an amount of the uplink data in one or more buffers of a UE is within a first range, to use the first table to determine the first index; determining, if an amount of the uplink data in one or more buffers of a UE is within a second range, to use the second table to determine the second index; 3. The method of claim 1 or 2, comprising: (Appendix 4) determining whether to use the first table to determine the first index or the second table to determine the second index based on a comparison of an amount of the uplink data in one or more buffers of a UE with a threshold; 3. The method according to claim 1 or 2. (Appendix 5) the first index indicating a first range of an amount of the uplink data in the one or more buffers of a UE; the second index indicates a second range of the amount of the uplink data in the one or more buffers of the UE; transmitting the indication of the first index to a base station if the first range is smaller than the second range, and transmitting the indication of the second index to the base station if the second range is smaller than the first range. 5. The method of any one of appendices 1 to 4. (Appendix 6) transmitting the indication of the first index or the second index includes transmitting the indication of the first index or the second index in a buffer status report (BSR). 6. The method of any one of appendices 1 to 5. (Appendix 7) the indication that the first table was used to generate the first index or the indication that the second table was used to generate the second index is provided in a medium access control (MAC) control element (CE). 7. The method of any one of appendices 1 to 6. (Appendix 8) sending an indication of a logical channel identity (LCID) to the access network node, the LCID indicating a format of a message used to send the indication of the first index or the second index to the access network node. 8. The method of any one of appendices 1 to 7. (Appendix 9) the indication that the first table was used to generate the first index is provided using a set of one or more bits adjacent to a set of one or more bits used to indicate the first index in transmission to the access network node; or the indication that the second table was used to generate the second index is provided using a set of one or more bits adjacent to a set of one or more bits used to indicate the second index in transmission to the access network node. 9. The method of any one of appendices 1 to 8. (Appendix 10) the indication that the first table was used to generate the first index or the indication that the second table was used to generate the second index is provided using one or more bits of a subheader. 7. The method of any one of appendices 1 to 6. (Appendix 11) the subheader is a subheader associated with a medium access control (MAC) control element (CE); 11. The method described in Appendix 10. (Appendix 12) determining to use the first table to determine the first index based on a first amount of uplink data in one or more buffers of the UE, and determining the first index based on the first amount of uplink data; determining to use the second table to determine the second index based on a second amount of uplink data in one or more buffers of the UE, and determining the second index based on the second amount of uplink data; sending an indication of the first index and an indication of the second index to the access network node; sending an indication that the first table was used to generate the first index; sending an indication that the second table was used to generate the second index; 12. The method of any one of appendices 1 to 11, comprising: (Appendix 13) one or more bits used to indicate that the first table was used to generate the first index are adjacent to one or more bits used to indicate that the second table was used to generate the second index. 12. The method described in Appendix 12. (Appendix 14) 1. A method for a user equipment (UE), comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE; In a first case, the UE receives from an access network node a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE, and the second table is stored in the UE; determining, based on an amount of uplink data in the one or more buffers of the UE, an index indicating a range of the amount of uplink data in the one or more buffers using the first table or the second table; sending an indication of the first index or the second index to the access network node in a buffer status report having a first format including an indication of whether the first table or the second table was used to determine the index; or In a second case where the UE has not received the second table or the information for generating the second table from the access network node, or the second table is not stored in the UE, determining the index using the first table based on an amount of the uplink data in the one or more buffers of a UE; sending an indication of the index to the access network node in a buffer status report having a second format, the second format being different from the first format; A method comprising: (Appendix 15) transmitting the indication of the index includes transmitting the indication of the index to the access network node in a medium access control (MAC) control element (CE). The method described in Appendix 14. (Appendix 16) The first format is a first MAC CE format of the MAC CE, and the second format is a second MAC CE format of the MAC CE. The method described in Appendix 15. (Appendix 17) and transmitting a subheader including the MAC CE to the access network node, wherein a subheader format of the subheader used for the first MAC CE format is the same as a subheader format used for the second MAC CE format. The method described in Appendix 16. (Appendix 18) the UE transmits all buffer status reports using the first format in the first case; 18. The method of any one of appendices 14 to 17. (Appendix 19) in the first case, the use of the first format is based on control signaling received from the access network node; 18. The method of any one of appendices 14 to 17. (Appendix 20) the control signaling includes an activation signal indicating that the first format is activated or a setup message for the second table; determining, in the first case, based on receiving the activation signal or the setup message for the second table, to send the indication of the index to the access network node in a buffer status report having the first format. 19. The method described in Appendix 19. (Appendix 21) the control signaling includes a deactivation signal indicating that the first format is to be deactivated or a release message for the second table; determining, in the first case, based on receiving the deactivation signal or the release message for the second table, to send the indication of the index to the access network node in a buffer status report having the second format. 19. The method described in Appendix 19. (Appendix 22) 1. A method for a user equipment (UE), comprising: storing a first table mapping each of a plurality of first indices to a respective sub-range of a first range for an amount of uplink data within the first range; and storing a second table mapping each of a plurality of second indexes to a respective sub-range of a second range for an amount of uplink data within the second range; each of the plurality of first indexes is different from each of the plurality of second indexes; If the amount of uplink data in one or more buffers of the UE is within the second range, sending the index of the plurality of second indexes, which indicates the sub-range of the amount of uplink data in one or more buffers of the UE, to the access network node; If the amount of uplink data in the one or more buffers of the UE is within the first range but not within the second range, transmitting the index of the plurality of first indexes indicating the sub-range of the amount of uplink data in the one or more buffers of the UE to the access network node. method. (Appendix 23) the second range is a subset of the first range. 23. The method described in Appendix 22. (Appendix 24) the number of the first indexes in the first table is different from the number of the second indexes in the second table; 24. The method according to claim 22 or 23. (Appendix 25) At least one subrange mapped to an index in the second table is smaller than the subrange mapped to an index in the first table; 25. The method of any one of appendices 22 to 24. (Appendix 26) 1. A method for a user equipment (UE), comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data, and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; receiving table activation information from an access network node indicating whether the second table is activated in the UE; If the table activation information indicates that the second table is activated in the UE, determining to use the second table to determine an index of the second plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; sending an indication of said index to said access network node; A method comprising: (Appendix 27) receiving table activation information from the access network node indicating that the second table is to be deactivated at the UE; determining, based on the indication that the second table is deactivated at the UE, to use the first table to determine an index of the first plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; sending an indication of said index to said access network node; 27. The method of claim 26, further comprising: (Appendix 28) 1. A method for a user equipment (UE), comprising: storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data; receiving table setup information from the access network node for a second table mapping each of a plurality of second indexes to a respective second range of amount of uplink data; determining, based on the table setup information, to use the second table to determine an index of the second plurality of indexes indicating a range of an amount of uplink data in one or more buffers of a UE; sending an indication of said index to said access network node; A method comprising: (Appendix 29) receiving table release information from an access network node indicating that the second table is to be released; determining, based on the table release information, to use the first table to determine an index of the first plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of a UE; sending an indication of said index to said access network node; 29. The method of claim 28, further comprising: (Appendix 30) the table setup information includes the second table or information for generating the second table in the UE; 29. The method of claim 28 or 29. (Appendix 31) 1. A method for a user equipment (UE), comprising: storing a table mapping each of a plurality of indexes to a respective range of uplink data; a first index of the plurality of indexes is mapped to a first range of uplink data; a second index of the plurality of indexes is mapped to a second range of uplink data; a third index of the plurality of indexes is mapped to a third range of uplink data; the first range and the third range are smaller than the second range; the upper limit of the first range is less than the lower limit of the second range, and the upper limit of the second range is less than the lower limit of the third range; determining the index of the table indicating the range of the amount of uplink data in one or more buffers of the UE based on the amount of uplink data in one or more buffers of the UE; transmitting the index to an access network node. method. (Appendix 32) 1. A method of an access network node, comprising: transmitting to a user equipment (UE) a second table mapping each of a plurality of second indexes to a respective second range of amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE; receiving an indication of an index from the UE indicating a range of an amount of uplink data in one or more buffers of the UE; if the index is an index determined using a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, receiving an indication from the UE indicating that the first table was used to generate the index, and determining the range of the amount of uplink data in one or more buffers of the UE using the first table; If the index is an index determined using the second table, receiving an indication from the UE indicating that the second table was used to generate the index, and determining the range of the amount of the uplink data in one or more buffers of the UE using the index and the second table; A method comprising: (Appendix 33) 1. A method of an access network node, comprising: In a first case, the access network node transmits to a user equipment (UE) a second table that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or the access network node transmits information for generating the second table at the UE, and the second table is stored in the UE; receiving an indication of an index from the UE in a buffer status report, the buffer status report having a first format including an indication of whether a first table or the second table mapping each of a plurality of first indices to a respective first range of amount of uplink data in one or more buffers of the UE was used to determine the index; or In a second case where the base station has not transmitted the second table or the information for generating the second table to the UE, or the second table is not stored in the UE, receiving an indication of the index from the UE in a buffer status report having a second format, the second format being different from the first format; A method comprising: (Appendix 34) 1. A method of an access network node, comprising: transmitting table activation information to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, the table activation information indicating whether to activate a second table in the UE that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in the one or more buffers of the UE; receiving an indication of an index from the UE indicating the range of the amount of the uplink data in the one or more buffers of the UE; using the index and the second table to determine the range of the amount of uplink data in the one or more buffers of the UE; A method comprising: (Appendix 35) sending table activation information to the UE indicating that the second table is deactivated in the UE; receiving an indication of an index from the UE indicating the range of an amount of uplink data in the one or more buffers of the UE; using the index and the first table to determine the range of the amount of uplink data in the one or more buffers of the UE; 35. The method of claim 34, further comprising: (Appendix 36) 1. A method of an access network node, comprising: transmitting table setup information for a second table to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, the second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE; receiving an indication of an index from the UE indicating the range of an amount of uplink data in the one or more buffers of the UE; using the index and the second table to determine the range of the amount of uplink data in the one or more buffers of the UE; A method comprising: (Appendix 37) sending table release information to the UE indicating that the second table is released; receiving an indication of an index from the UE indicating the range of an amount of uplink data in one or more buffers of the UE; using the index and the first table to determine the range of amounts of the uplink data in one or more buffers of the UE; 37. The method of claim 36, further comprising: (Appendix 38) A user equipment (UE), means for storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data, and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; determining, based on an amount of uplink data in one or more buffers of the UE, whether to use the first table to determine a first index indicating a first range of an amount of uplink data in one or more buffers of the UE, or to use the second table to determine a second index indicating a second range of an amount of uplink data in one or more buffers of the UE; determining means configured to determine the first index or the second index based on an amount of the uplink data in one or more buffers of a UE; sending an indication of the first index or the second index to an access network node; sending an indication to the access network node indicating that the first table was used to generate the first index when the UE sends an indication of the first index to the access network node; transmitting means configured to, when the UE sends an indication of the second index to the access network node, send an indication to the access network node indicating that the second table was used to generate the second index; A UE equipped with: (Appendix 39) A user equipment (UE), means for storing a first table mapping each of a plurality of first indices to a respective first range of an amount of uplink data in one or more buffers of the UE; In a first case, the UE receives from an access network node a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE, and the second table is stored in the UE; determining, based on an amount of uplink data in the one or more buffers of the UE, an index indicating a range of the amount of uplink data in the one or more buffers using the first table or the second table; sending an indication of the first index or the second index to the access network node in a buffer status report having a first format including an indication of whether the first table or the second table was used to determine the index; or In a second case where the UE has not received the second table or the information for generating the second table from the access network node, or the second table is not stored in the UE, determining the index using the first table based on an amount of the uplink data in one or more buffers of a UE; sending an indication of the index to the access network node in a buffer status report having a second format, the second format being different from the first format; UE configured to: (Appendix 40) A user equipment (UE), storing a first table mapping each of a plurality of first indices to a respective sub-range of a first range for an amount of uplink data within the first range; storage means configured to store a second table mapping each of a plurality of second indices to a respective sub-range of a second range for an amount of uplink data within said second range; each of the plurality of first indexes is different from each of the plurality of second indexes; If the amount of uplink data in the one or more buffers of the UE is within the second range, sending the index of the plurality of second indexes, which indicates the sub-range of the amount of uplink data in the one or more buffers of the UE, to the access network node; transmitting means configured to, if the amount of uplink data in the one or more buffers of the UE is within the first range but not within the second range, transmit the index of the plurality of first indexes indicating the sub-range of the amount of uplink data in the one or more buffers of the UE to the access network node; UE. (Appendix 41) A user equipment (UE), means for storing a first table mapping each of a plurality of first indexes to a respective first range of amounts of uplink data, and a second table mapping each of a plurality of second indexes to a respective second range of amounts of uplink data; means for receiving table activation information from an access network node, the table activation information indicating whether the second table is activated in the UE; means for determining to use the second table if the table activation information indicates that the second table is activated in the UE, and for determining an index of the second plurality of indexes that indicates the range of an amount of uplink data in one or more buffers of the UE; means for transmitting an indication of said index to said access network node; A UE equipped with: (Appendix 42) A user equipment (UE), means for storing a first table mapping each of a plurality of first indices to a respective first range of amount of uplink data; means for receiving, from the access network node, table setup information for a second table that maps each of a plurality of second indexes to a respective second range of amount of uplink data; means for determining to use the second table based on the table setup information and for determining an index of the second plurality of indexes that indicates a range of an amount of uplink data in one or more buffers of a UE; means for transmitting an indication of said index to said access network node; A UE equipped with: (Appendix 43) A user equipment (UE), means for storing a table mapping each of a plurality of indexes to a respective range of uplink data; a first index of the plurality of indexes is mapped to a first range of uplink data; a second index of the plurality of indexes is mapped to a second range of uplink data; a third index of the plurality of indexes is mapped to a third range of uplink data; the first range and the third range are smaller than the second range; the upper limit of the first range is less than the lower limit of the second range, and the upper limit of the second range is less than the lower limit of the third range; means for determining the index of the table indicating the range of the amount of uplink data in one or more buffers of the UE based on the amount of uplink data in one or more buffers of the UE; means for transmitting said index to an access network node; A UE that further comprises: (Appendix 44) means for transmitting to a user equipment (UE) a second table mapping each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or information for generating the second table at the UE; receiving an indication of an index from the UE indicating a range of an amount of uplink data in one or more buffers of the UE; if the index is an index determined using a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, receive an indication from the UE that the first table was used to generate the index, and determine the range of the amount of uplink data in one or more buffers of the UE using the first table; receiving means configured to receive, if the index is an index determined using the second table, an indication from the UE indicating that the second table was used to generate the index, and to determine the range of the amount of the uplink data in one or more buffers of the UE using the index and the second table; An access network node comprising: (Appendix 45) an access network node, In a first case, the access network node transmits to a user equipment (UE) a second table that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE, or the access network node transmits information for generating the second table at the UE, and the second table is stored in the UE; receiving an indication of an index from the UE in a buffer status report, the buffer status report having a first format including an indication of whether a first table or a second table mapping each of a plurality of first indices to a respective first range of an amount of uplink data in one or more buffers of the UE was used to determine the index; or In a second case where the base station has not transmitted the second table or the information for generating the second table to the UE, or the second table is not stored in the UE, receiving an indication of the index from the UE in a buffer status report having a second format, the second format different from the first format; an access network node configured to: (Appendix 46) means for transmitting, to a user equipment (UE), a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, table activation information indicating whether a second table that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE is to be activated in the UE; means for receiving, from the UE, an indication of an index indicating the range of an amount of uplink data in the one or more buffers of the UE; means for determining the range of amounts of the uplink data in one or more buffers of the UE using the index and the second table; An access network node comprising: (Appendix 47) means for transmitting, to a user equipment (UE) that stores a first table that maps each of a plurality of first indexes to a respective first range of an amount of uplink data in one or more buffers of the UE, table setup information for a second table that maps each of a plurality of second indexes to a respective second range of an amount of uplink data in one or more buffers of the UE; means for receiving, from the UE, an indication of an index indicating the range of an amount of uplink data in the one or more buffers of the UE; means for determining the range of the amount of the uplink data in the one or more buffers of the UE using the index and the second table; An access network node comprising:

[0289] This application claims the benefit of priority from UK Patent Application No. 2301599.3, filed February 3, 2023, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]

[0290] 1. Communication Systems 3. User Equipment 5 base station 7 Core Network 9 cells 10 CONTROL PLANE FUNCTION 11 USER PLANE FUNCTION 451 Transceiver Circuit 453 RU interface 454 CU interface 457 Controller 459 memory 461 Operating Systems 463 Communication Control Module 465 F1 Module 468 DU-RU module 472 DU Management Module 473 UE Profile Management Module 475 Mobility Module 551 Transceiver Circuit 554 DU interface 555 CU interface 557 Controller 559 memory 561 Operating Systems 563 Communication Control Module 565 F1 Module 566 F2 module 568 N2 Module 569 N3 Module 571 CU-UP Management Module 572 CU-CP Management Module 573 UE Profile Management Module 575 Mobility Module 310 Transceiver Circuit 330 Antenna 350 User Interface 370 Controller 390 memory 410 Operating Systems 430 Communication Control Module 440 BSR Module 510 Transceiver Circuit 530 Antenna 550 User Interface 570 Controller 590 memory 610 Operating System 630 Communication Control Module 650 BSR Module 670 UL Scheduling Module 710 Transceiver Circuit 720 Network Interface 730 Controller 740 memory 750 Operating Systems 760 Communication Control Module

Claims

1. 1. A method for user equipment (UE), comprising: storing a plurality of tables, each of the plurality of tables mapping a respective one of a plurality of indexes to a respective range of amount of uplink data; determining a particular table from the plurality of tables based on an amount of uplink data in at least one buffer of the UE to determine an index indicating a range of an amount of uplink data in the at least one buffer; sending an indication of the index and an indication of the particular table to an access network node; A method comprising:

2. and determining the index by determining the particular table if the amount of uplink data in the at least one buffer is within a particular range. The method of claim 1.

3. and determining the index based on a comparison of the amount of uplink data in the at least one buffer with a threshold.

3. The method according to claim 1 or 2.

4. said determining is performed by determining a particular table in which said index corresponds to a minimum step size of a respective range corresponding to an amount of said uplink data in said at least one buffer; 4. The method according to any one of claims 1 to 3.

5. First information for activating the particular table stored in the UE; or second information for generating the specific table in the UE; from the access network node.

5. The method according to any one of claims 1 to 4.

6. the determining is performed by determining the particular table based on the first information or the second information. The method of claim 5.

7. receiving instructions to activate use of the particular table; the determining is performed by determining the particular table based on the instruction to activate use of the particular table.

6. The method according to any one of claims 1 to 5.

8. said determining being performed for each transmission of a status report of said at least one buffer; 6. The method according to any one of claims 1 to 5.

9. the indication of one of the tables is included in a Media Access Control Control Element (MAC-CE) sub-header.

9. The method according to any one of claims 1 to 8.

10. Each value of a logical channel identity (LCID) corresponding to each of the plurality of tables is common among the plurality of tables.

10. The method of claim 9.

11. The values ​​of logical channel identities (LCIDs) corresponding to the plurality of tables are different among the plurality of tables.

10. The method of claim 9.

12. a format of each of the MAC-CEs corresponding to each of the plurality of tables is common among the plurality of tables; 12. The method according to any one of claims 9 to 11.

13. The formats of the MAC-CEs corresponding to the plurality of tables are different among the plurality of tables.

12. The method according to any one of claims 9 to 11.

14. The number of the index indications included in the MAC-CE is the number of at least one logical channel group indicated in said MAC-CE; the number of at least one buffer size indicated in the MAC-CE, or the number of at least one logical channel indicated in said MAC-CE; is the same as 14. The method according to any one of claims 9 to 13.

15. The number of the at least one buffer size indicated in the MAC-CE is: the number of the at least one logical channel group indicated in the MAC-CE, or the number of the at least one logical channel indicated in the MAC-CE; greater than 15. The method of claim 14.

16. the range of values ​​of the corresponding index mapped to the particular table is consecutive to the range of values ​​of the corresponding index mapped to another table of the plurality of tables; 16. The method of any one of claims 1 to 15.

17. the corresponding index mapped to the particular table is a combination of the corresponding index mapped to the other table and at least one other bit; 17. The method of claim 16.

18. transmitting delay information of the transmission of the uplink data to the access network node together with the indication of the index and the indication of the particular table.

18. The method of any one of claims 1 to 17.

19. a first step size of a first respective range of the amount of uplink data mapped to a particular table of the plurality of tables is smaller than a second step size of a second respective range of the amount of uplink data mapped to another table of the plurality of tables; 19. The method of any one of claims 1 to 18.

20. 1. A method of an access network node, comprising: transmitting to a user equipment (UE) information of a specific table mapping each of a plurality of indexes to a respective range of amounts of uplink data in at least one buffer of the UE; receiving an index indication from the UE indicating a range of an amount of uplink data in the at least one buffer; the particular table is determined by the UE based on the amount of the uplink data in the at least one buffer to determine the index; method.

21. A user equipment (UE), means for storing a plurality of tables, each of the plurality of tables mapping a respective one of a plurality of indexes to a respective range of amounts of uplink data; means for determining a specific table from the plurality of tables based on an amount of uplink data in at least one buffer of the UE, and determining an index indicating a range of an amount of uplink data in the at least one buffer; means for transmitting an indication of said index and an indication of said particular table to an access network node; A UE comprising:

22. means for transmitting to a user equipment (UE) information of a specific table mapping each of a plurality of indexes to a respective range of amounts of uplink data in at least one buffer of the UE; means for receiving from the UE an indication of an index indicating a range of an amount of uplink data in the at least one buffer; the particular table is determined by the UE based on the amount of the uplink data in the at least one buffer to determine the index; Access network node.

Images