Device and method

Abstract

A device (200) according to one embodiment of the present disclosure comprises a communication processing unit (233) for receiving a message including configuration information for determining whether to use a buffer status report that includes at least one first field and at least one changed second field, and an information acquiring unit (231) for acquiring the configuration information included in the message, wherein: the buffer status report is used to provide information relating to an uplink data volume; the at least one first field indicates at least one logical channel group of which a buffer status is to be reported; and the at least one changed second field corresponds to the at least one logical channel group and relates to the uplink data volume.

Description

Apparatus and method CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Japanese Application No. 2022-127462, filed on August 9, 2022, the contents of which are incorporated herein by reference.

[0002] The present disclosure relates to an apparatus and a method.

[0003] Mobile communication technologies are proposed in 3GPP (3rd Generation Partnership Project) (registered trademark) and defined in technical specifications (TS). In particular, 5G (5th Generation) technologies are currently proposed and defined in TS.

[0004] In the mobile communication system, a base station allocates communication resources for uplink (UL) transmission to a user equipment (UE). As described in Non-Patent Document 1, the user equipment transmits a scheduling request (SR) to the base station to request allocation of communication resources for the UL transmission. The user equipment transmits UL data to the base station using the allocated communication resources.

[0005] Furthermore, as described in Non-Patent Document 1, the UE transmits a buffer status report (BSR) to the base station to provide information about the amount of UL data. The BSR indicates a range of buffer sizes for UL data. This allows the base station to allocate communication resources according to the range of buffer sizes for UL data indicated by the BSR. Note that, since the BSR indicates a range of buffer sizes, it is subject to quantization error. Furthermore, as described in Non-Patent Document 2, the SR parameters and the BSR parameters are configured in the RRC (radio resource control) layer.

[0006] Furthermore, as described in Non-Patent Documents 3 to 5, it has been proposed to apply the above-mentioned mobile communication system to XR (extended reality) services. However, XR service data is characterized by large volume and high variability. Therefore, quantization errors in the BSR waste communication resources and reduce scheduling efficiency. As a countermeasure, for example, Non-Patent Document 3 proposes determining a precise buffer size through the BSR. Furthermore, XR services may have delay requirements (e.g., packet delay budget: PDB). As a countermeasure, for example, Non-Patent Document 4 proposes including delay information in the BSR and performing scheduling that takes delay into account to satisfy the PDB.

[0007] 3GPP TS 38.321 V17.0.0 (2022-03), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17)”3GPP TS 38.331 V17.1.0 (2022-06), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; (RRC) protocol specification (Release 17)”3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203607, “Discussion on XR specific capacity enhancements techniques”3GPP TSG-RAN WG1 Meeting #109-e, Online, May 9th - 20th, 2022, R1-2203639, “Discussion on capacity enhancements for XR”3GPP TSG RAN WG1 #109-e, e-Meeting, May 9th - 20th, 2022, R1-2203928, “Considerations on XR Capacity Improvements”

[0008] As a result of detailed investigations by the inventors, the following problem was found: Although non-patent documents have proposed concepts for scheduling UL data using BSR, they have not proposed any specific methods.

[0009] An object of the present disclosure is to provide an apparatus and method capable of improving the efficiency of UL data scheduling using BSR.

[0010] An apparatus (200) according to one aspect of the present disclosure comprises: a communication processing unit (233) that receives a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; and an information acquisition unit (231) that acquires the configuration information included in the message, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which the buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and relating to the uplink data volume.

[0011] An apparatus (100) according to one aspect of the present disclosure includes an information acquisition unit (141) that acquires configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field, and a communication processing unit (143) that transmits a message including the configuration information, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which the buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and relating to the uplink data volume.

[0012] A method performed by an apparatus (200) according to one aspect of the present disclosure includes receiving a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field, and acquiring the configuration information included in the message, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which the buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and relating to the uplink data volume.

[0013] A method performed by an apparatus (100) according to one aspect of the present disclosure includes: obtaining configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; and transmitting a message including the configuration information, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which the buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and relating to the uplink data volume.

[0014] According to the present disclosure, it is possible to improve the efficiency of UL data scheduling using BSR. Note that the present disclosure may achieve other effects instead of or in addition to the effect.

[0015] 1 is an explanatory diagram showing an example of UL data transmission; FIG. 2 is a diagram showing a Short BSR; FIG. 3 is a diagram showing a buffer size table; FIG. 4 is a diagram showing a Long BSR; FIG. 5 is an explanatory diagram showing an example of a schematic configuration of a system according to an embodiment of the present disclosure; FIG. 6 is a block diagram showing an example of a schematic functional configuration of a base station according to an embodiment of the present disclosure; FIG. 7 is a block diagram showing an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure; FIG. 8 is a block diagram showing an example of a schematic functional configuration of a user equipment according to an embodiment of the present disclosure; FIG. 9 is a block diagram showing an example of a schematic hardware configuration of a user equipment according to an embodiment of the present disclosure; FIG. 10 is a diagram showing an example of a BSR according to a first embodiment of the present disclosure; FIG. 11 is a diagram showing example configuration information for determining whether to use a BSR according to the first embodiment of the present disclosure; FIG. 12 is a diagram for explaining example of the configuration information according to the first embodiment of the present disclosure; FIG. 13 is a sequence diagram for explaining an example of a schematic flow of a process according to the first embodiment of the present disclosure; FIG. 14 is a diagram showing example of the configuration information according to a first modified example 1 of the first embodiment of the present disclosure; FIG. 15 is a diagram for explaining example of the configuration information according to a first modified example 2 of the first embodiment of the present disclosure; FIG. 10 is a diagram for explaining an example of the setting information according to a first modified example 3 of the first embodiment of the present disclosure. FIG. 11 is a diagram for explaining an example of setting information according to a second modified example of the first embodiment of the present disclosure, including the setting information according to a second modified example of the first embodiment of the present disclosure. FIG. 12 is a diagram for explaining an example of the setting information according to a third modified example of the first embodiment of the present disclosure. FIG. 13 is a diagram for explaining an example of the setting information according to a fourth modified example of the second embodiment of the present disclosure. FIG. 14 is a diagram for explaining an example of the setting information according to a fourth modified example of the second embodiment of the present disclosure.

[0016] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, elements that can be similarly described will be designated by the same reference numerals, and redundant description will be omitted.

[0017] The description will be given in the following order: 1. Related art 2. System configuration 3. Base station configuration 4. User equipment configuration 5. First embodiment 5-1. Operation example 5-2. Modification 6. Second embodiment 6-1. Operation example 6-2. Modification

[0018] <1. Related Art> Scheduling requests (SR) and buffer status reports (BSR) will be described as art related to the embodiments of the present disclosure.

[0019] (1) Scheduling Request (SR) The SR is used by the UE to request a base station to allocate communication resources for a new UL transmission. For example, the SR may be used to request uplink-shared channel (UL-SCH) resources for an initial transmission. Here, the UL-SCH may be mapped to a physical uplink shared channel (PUSCH). In this embodiment, UL-SCH data is also referred to as UL data. As communication resources for the SR, multiple bandwidth parts (BWPs) and / or a set of physical uplink control channel (PUCCH) resources across the cell are allocated. For each logical channel, up to one PUCCH resource is allocated for the SR in each BWP. For example, one or more downlink BWPs and / or one or more uplink BWPs may be configured in each of one or more cells (also referred to as serving cells). For example, a set of PUCCH resources may be configured for each of one or more uplink BWPs.

[0020] An example of UL transmission using SR will be described with reference to FIG. 1 . When UL data arrives, the UE triggers SR. The SR is transmitted to the base station using the PUCCH. The base station, upon receiving the SR, allocates resources for UL data transmission to the UE. The UL resource allocation is transmitted to the UE using a physical downlink control channel (PDCCH). The UE, upon receiving the UL resource allocation, transmits UL data to the base station using the allocated PUSCH resources. A BSR may also be transmitted together with the UL data. In this embodiment, the UL resource allocation includes allocation of a UL-SCH and / or allocation of a PUSCH resource. Furthermore, the PUSCH resource allocation includes frequency domain resource assignment for the PUSCH and / or time domain resource assignment for the PUSCH. For example, the base station may transmit downlink control information (DCI) used for scheduling the PUSCH on the PDCCH. That is, the DCI may include information (one or more fields) for allocating resources for the PUSCH.

[0021] SR parameters are configured using SchedulingRequestConfig and / or SchedulingRequestResourceConfig, which are RRC configuration information. For example, SR parameters are parameters used for SR transmission and / or SR resource configuration, and are also referred to as SR configurations. SR parameters may include SchedulingRequestConfig and / or SchedulingRequestResourceConfig. The SR parameters may also include schedulingRequestID, sr-ProhibitTimer, sr-TransMax, periodicityAndOffset, phy-PriorityIndex, and / or resource. Each SR configuration corresponds to one or more logical channels. For example, each SR configuration may correspond to one or more logical channels (and / or beam failure recovery (BFR)) via schedulingRequestID. The schedulingRequestID may be used to identify an SR instance at the MAC layer. The sr-ProhibitTimer may be used to set a timer for SR transmission on the PUCCH. The sr-TransMax may be used to set the maximum number of SR transmissions. The periodicityAndOffset may be used to set the SR periodicity and offset. The phy-PriorityIndex may be used to set the priority of the SR resource in PHY layer prioritization or multiplexing. The parameter "resource" may be used to set the ID (identifier) ​​of the PUCCH resource used for SR transmission. For example, a PUCCH resource corresponding to the PUCCH resource ID included in the SR parameter may be configured for SR transmission based on the SR parameter. The PUCCH resource may be configured using PUCCH format 0 or PUCCH format 1, which includes information used to configure the PUCCH resource.

[0022] Here, the RRC configuration information may include information transmitted and / or received in the RRC layer between the base station and the UE. That is, the base station may transmit an RRC message including an SR configuration to the UE. Alternatively, the UE may receive the RRC message including the SR configuration and perform SR transmission based on the SR configuration. Alternatively, the UE may receive the RRC message including the SR configuration and determine a PUCCH resource to be used for SR transmission based on the SR configuration. For example, the RRC message may include an RRC reconfiguration message.

[0023] (2) Buffer Status Report (BSR) The BSR procedure (also referred to as the Buffer Status Reporting procedure) is used to provide information about the UL data volume in a UE to a base station. That is, the BSR is used in a procedure (Buffer Status Reporting) for providing information about the UL data volume of a MAC entity to a base station. The BSR is transmitted using a MAC Control Element (CE). That is, operations related to the BSR may be performed and / or processed in a MAC layer (e.g., a MAC entity) in the UE. Also, operations related to the BSR may be performed and / or processed in a MAC layer (e.g., a MAC entity) in a base station. In this embodiment, the higher layer includes a layer higher than the MAC layer. For example, the higher layer may include an RRC layer.

[0024] BSR-related parameters are configured using RRC configuration information. BSR parameters include periodicBSR-Timer, retxBSR-Timer, logicalChannelSR-DelayTimerApplied, logicalChannelSR-DelayTimer, logicalChannelSR-Mask, and logicalChannelGroup. The periodicBSR-Timer may be used to set a timer for the BSR period. The retxBSR-Timer may be used to set a timer for BSR retransmission. The logicalChannelSR-DelayTimerApplied may be used to set whether to apply a delay timer for SR transmission for a logical channel. The logicalChannelSR-DelayTimer may be used to set a delay timer for SR transmission for a logical channel. The logicalChannelSR-Mask may be used to set the control of SR triggering when a configured grant is set (i.e., whether to set SR masking). The logicalChannelGroup may be used to set the ID of the logical channel group to which the logical channel belongs. The base station may send an RRC message including BSR-related parameters to the UE. The UE may also receive an RRC message including parameters related to the BSR, and perform reporting (i.e., transmission) of the BSR based on the parameters related to the BSR.

[0025] A BSR is reported for each logical channel group (LCG). Each logical channel is assigned to an LCG by the logicalChannelGroup, which indicates the ID of the LCG.

[0026] A BSR may be triggered when any of the following occurs for an activated cell group. The BSR is classified into Regular BSRs corresponding to (A) and (C), Periodic BSRs corresponding to (D), and Padding BSRs corresponding to (B) according to the following triggering mechanisms: (A) UL data for a logical channel belonging to any LCG becomes available at the MAC entity; (B) UL resources are allocated and the number of padding bits for the UL resources is equal to or greater than the size of the BSR MAC CE; (C) The period indicated by the retxBSR-Timer expires and at least one logical channel belonging to any LCG contains UL data; or (D) The period indicated by the periodicBSR-Timer expires.

[0027] Next, the BSR MAC CE will be described. The BSR MAC CE may correspond to the MAC CE used to transmit the BSR described above. For example, the format of the BSR MAC CE (hereinafter also referred to as the BSR format) is defined as several types (e.g., Short BSR, Long BSR), and is identified by a MAC subheader including an LCID / eLCID. That is, an LCID (Logical Channel Identifier) / eLCID (Extended LCID) may be used to identify the type of the corresponding MAC CE. Furthermore, an LCID / eLCID may be defined for each of a Downlink Shared Channel (DL-SCH) and / or an UL-SCH. Hereinafter, LCID / eLCID refers to an LCID and / or an eLCID.

[0028] The format 20A of the Short BSR will be described with reference to Figures 2 and 3. The size of the Short BSR is fixed. As shown in Figure 2, the Short BSR has an LCG ID field and a Buffer Size field. The LCG ID field identifies the LCG ID for which the buffer size is reported. The size of the LCG ID field is 3 bits. The Buffer Size field identifies the total amount of data available for all logical channels belonging to the LCG indicated by the LCG ID. The size of the Buffer Size field is 5 bits. The Buffer Size field indicates an index corresponding to the buffer size in Table T1 for the 5-bit Buffer Size field shown in Figure 3.

[0029] The format 20B of the Long BSR will be described with reference to FIG. 4. The size of the Long BSR is variable. As shown in FIG. 4, the Long BSR has an LCGi field and a Buffer Size j field. LCGi is the LCG with the i-th ID, and the LCGi field indicates the presence of a Buffer Size field for LCGi. The LCGi field is set to 1 if a buffer size is reported, and set to 0 otherwise. Alternatively, the LCGi field may indicate whether LCGi has available data. The Buffer Size j field identifies the total amount of data available for all logical channels belonging to the corresponding LCGi. The size of the Buffer Size j field is 8 bits. The Buffer Size j field indicates an index corresponding to the buffer size in a table for the 8-bit Buffer Size field (not shown). Note that the Buffer Size j fields are included in ascending order according to the LCGi.

[0030] The BSR format is selected according to the method specified in TS (TS 38.321 5.4.5 and 5 / 4.7).

[0031] For example, in the case of Regular BSR and Periodic BSR, if there are two or more LCGs with available data when the MAC PDU containing the BSR is built, Long BSR is reported, otherwise Short BSR is reported. Furthermore, for MAC entities for which logicalChannelGroup-IABExt is configured by higher layers, Extended Long BSR or Extended Short BSR may be reported.

[0032] For example, in the case of Padding BSR, in addition to the above BSR format, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, and Extended Long Truncated BSR are reported depending on the conditions.

[0033] Furthermore, for example, the Pre-emptive BSR and the Extended Pre-emptive BSR are used by an IAB-MT (Mobile Termination).

[0034] 2. System Configuration An example of the configuration of a system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 5. Referring to Fig. 5, the system 1 includes a base station 100 and a UE 200.

[0035] For example, the system 1 is a system that complies with 3GPP TS. More specifically, the system 1 is a system that complies with 5G or NR (New Radio) TS. Naturally, the system 1 is not limited to this example.

[0036] (1) Base Station 100 The base station 100 is a node in a radio access network (RAN) and communicates with UEs (e.g., UE 200) located within the coverage area 10 of the base station 100.

[0037] For example, the base station 100 communicates with a UE (e.g., UE 200) using a RAN protocol stack. For example, the protocol stack includes radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and a physical (PHY) layer protocol. Alternatively, the protocol stack may include only some of these protocols, rather than all of them.

[0038] For example, the base station 100 is a gNB. The gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and is connected to a 5G Core Network (5GC) via an NG interface. Alternatively, the base station 100 may be an en-gNB. The en-gNB is a node that provides NR user plane and control plane protocol terminations toward the UE and operates as a secondary node in E-UTRA-NR Dual Connectivity (EN-DC).

[0039] The base station 100 may include multiple nodes. The multiple nodes may include a first node hosting a higher layer included in the protocol stack and a second node hosting a lower layer included in the protocol stack. The higher layer may include RRC, SDAP, and PDCP, and the lower layer may include RLC, MAC, and a PHY layer. The first node may be a central unit (CU), and the second node may be a distributed unit (DU). The multiple nodes may include a third node that performs processing below the PHY layer, and the second node may perform processing above the PHY layer. The third node may be a radio unit (RU).

[0040] Alternatively, the base station 100 may be one of the plurality of nodes, or may be connected to other units of the plurality of nodes.

[0041] The base station 100 may be an integrated access and backhaul (IAB) donor or an IAB node.

[0042] (2) UE 200 The UE 200 communicates with the base station. For example, when the UE 200 is located within the coverage area 10 of the base station 100, the UE 200 communicates with the base station 100.

[0043] For example, the UE 200 communicates with a base station (for example, the base station 100) using the above protocol stack.

[0044] Furthermore, the UE 200 transmits an SR and a BSR to the base station as described in <1. Related Art>. Furthermore, the UE 200 may be a device that supports the XR service (in other words, an XR scenario).

[0045] 3. Configuration of Base Station> An example of the configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to FIGS. 6 and 7 .

[0046] (1) Functional Configuration First, an example of the functional configuration of the base station 100 according to the embodiment of the present disclosure will be described with reference to Fig. 6. Referring to Fig. 6, the base station 100 includes a wireless communication unit 110, a network communication unit 120, a storage unit 130, and a processing unit 140.

[0047] The wireless communication unit 110 transmits and receives signals wirelessly. For example, the wireless communication unit 110 receives signals from UEs and transmits signals to UEs.

[0048] The network communication unit 120 receives signals from a network and transmits signals to a network.

[0049] The storage unit 130 stores various information for the base station 100 .

[0050] The processing unit 140 provides various functions of the base station 100. The processing unit 140 includes an information acquisition unit 141, a first communication processing unit 143, and a second communication processing unit 145. The processing unit 140 may further include other components in addition to these components. That is, the processing unit 140 may perform operations other than those of these components. The specific operations of the information acquisition unit 141, the first communication processing unit 143, and the second communication processing unit 145 will be described in detail later.

[0051] For example, the processing unit 140 (first communication processing unit 143) communicates with a UE (e.g., UE 200) via the radio communication unit 110. For example, the processing unit 140 (second communication processing unit 145) communicates with another node (e.g., a network node in a core network or another base station) via the network communication unit 120.

[0052] (2) Hardware Configuration Next, an example of a hardware configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to Fig. 7. Referring to Fig. 7, the base station 100 includes an antenna 181, an RF (radio frequency) circuit 183, a network interface 185, a processor 187, a memory 189, and a storage 191.

[0053] The antenna 181 converts signals into radio waves and radiates the radio waves into space. The antenna 181 also receives radio waves in space and converts the radio waves into signals. The antenna 181 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. The antenna 181 may be a directional antenna and may include multiple antenna elements.

[0054] The RF circuit 183 performs analog processing of signals transmitted and received via the antenna 181. The RF circuit 183 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, and the like.

[0055] The network interface 185 is, for example, a network adapter, and transmits signals to and receives signals from a network.

[0056] The processor 187 performs digital processing of signals transmitted and received via the antenna 181 and the RF circuit 183. This digital processing includes processing of a protocol stack of the RAN. The processor 187 also processes signals transmitted and received via the network interface 185. The processor 187 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0057] The memory 189 stores programs executed by the processor 187, parameters related to the programs, and various other information. The memory 189 may include at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), and a flash memory. All or a portion of the memory 189 may be included within the processor 187.

[0058] The storage 191 stores various information and may include at least one of an SSD (solid state drive) and an HDD (hard disc drive).

[0059] The wireless communication unit 110 may be implemented by an antenna 181 and an RF circuit 183. The network communication unit 120 may be implemented by a network interface 185. The memory unit 130 may be implemented by a storage 191. The processing unit 140 may be implemented by a processor 187 and a memory 189.

[0060] A part or all of the processing unit 140 may be virtualized. In other words, a part or all of the processing unit 140 may be implemented as a virtual machine. In this case, a part or all of the processing unit 140 may operate as a virtual machine on a physical machine (i.e., hardware) including a processor, memory, etc., and a hypervisor.

[0061] Considering the above hardware configuration, base station 100 may include a memory (i.e., memory 189) that stores a program, and one or more processors (i.e., processor 187) that can execute the program, and the one or more processors may execute the program to perform the operations of processing unit 140. The program may be a program that causes the processor to execute the operations of processing unit 140.

[0062] 4. Configuration of User Equipment> An example of the configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to FIGS. 8 and 9 .

[0063] (1) Functional Configuration First, an example of a functional configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to Fig. 8. Referring to Fig. 8, the UE 200 includes a wireless communication unit 210, a storage unit 220, and a processing unit 230.

[0064] The wireless communication unit 210 transmits and receives signals wirelessly. For example, the wireless communication unit 210 receives a signal from a base station and transmits the signal to the base station. For example, the wireless communication unit 210 receives a signal from another UE and transmits the signal to the other UE.

[0065] The storage unit 220 stores various information for the UE 200 .

[0066] The processing unit 230 provides various functions of the UE 200. The processing unit 230 includes an information acquisition unit 231 and a communication processing unit 233. The processing unit 230 may further include other components in addition to these components. That is, the processing unit 230 may also perform operations other than those of these components. The specific operations of the information acquisition unit 231 and the communication processing unit 233 will be described in detail later.

[0067] For example, the processing unit 230 (communication processing unit 233) communicates with a base station (for example, the base station 100) or other UEs via the wireless communication unit 210.

[0068] (2) Hardware Configuration Next, an example of a hardware configuration of the UE 200 according to the embodiment of the present disclosure will be described with reference to Fig. 9. Referring to Fig. 9, the UE 200 includes an antenna 281, an RF circuit 283, a processor 285, a memory 287, and a storage 289.

[0069] The antenna 281 converts signals into radio waves and radiates the radio waves into space. The antenna 281 also receives radio waves in space and converts the radio waves into signals. The antenna 281 may include a transmitting antenna and a receiving antenna, or may be a single antenna for both transmission and reception. The antenna 281 may be a directional antenna and may include multiple antenna elements.

[0070] The RF circuit 283 performs analog processing of signals transmitted and received via the antenna 281. The RF circuit 283 may include a high-frequency filter, an amplifier, a modulator, a low-pass filter, and the like.

[0071] The processor 285 performs digital processing of signals transmitted and received via the antenna 281 and the RF circuitry 283. The digital processing includes processing of a RAN protocol stack. The processor 285 may include multiple processors or may be a single processor. The multiple processors may include a baseband processor that performs the digital processing and one or more processors that perform other processing.

[0072] The memory 287 stores programs executed by the processor 285, parameters related to the programs, and various other information. The memory 287 may include at least one of a ROM, an EPROM, an EEPROM, a RAM, and a flash memory. All or a portion of the memory 287 may be included within the processor 285.

[0073] The storage 289 stores various information and may include at least one of an SSD and an HDD.

[0074] The wireless communication unit 210 may be implemented by an antenna 281 and an RF circuit 283. The memory unit 220 may be implemented by a storage 289. The processing unit 230 may be implemented by a processor 285 and a memory 287.

[0075] The processing unit 230 may be implemented by a System on Chip (SoC) including a processor 285 and a memory 287. The SoC may include an RF circuit 283, and the wireless communication unit 210 may also be implemented by the SoC.

[0076] Considering the above hardware configuration, the UE 200 may include a memory (i.e., memory 287) that stores a program, and one or more processors (i.e., processor 285) that can execute the program, and the one or more processors may execute the program to perform the operation of the processing unit 230. The program may be a program that causes the processor to execute the operation of the processing unit 230.

[0077] 5. First Embodiment In an embodiment of the present disclosure, configuration information for determining whether to use a BSR including a first field and a modified second field (hereinafter also referred to as an enhanced-BSR) is transmitted from a base station to a UE. In the first embodiment of the present disclosure, configuration information for determining whether to use an enhanced-BSR including an extended buffer size field as the modified second field (hereinafter also referred to as a BS (Buffer Size) extended BSR) is transmitted from base station 100 to UE 200.

[0078] <5-1. Operational Example> With reference to FIGS. 10 to 13, an operational example of the base station 100 and the UE 200 according to the first embodiment of the present disclosure will be described.

[0079] (1) Format of the BS Extended BSR The BS Extended BSR according to this embodiment includes a first field and a modified second field. The first field may indicate a logical channel group (LCG) for which the buffer status is reported. The second field corresponds to the logical channel group and is related to the amount of uplink data. The modified second field may be a field in which the size of the second field is increased (hereinafter also referred to as an extended second field). In other words, the extended second field may be larger in size than the second field before extension (i.e., the data length may be longer or the number of bits may be greater). For example, the UE 200 may calculate the amount of data (volume) and determine the amount of uplink data available for the logical channel. As will be described later, the UE 200 may determine a buffer size level based on the amount of uplink data and set an index corresponding to the determined buffer size level in the second field.

[0080] Specifically, the extended second field is a Buffer Size field (hereinafter also referred to as the extended Buffer Size field) that indicates information used to indicate the total amount of data for the logical channels of the corresponding logical channel group. The extended Buffer Size field of the BS-enhanced BSR is longer than the Buffer Size field of the legacy BSR (hereinafter also referred to as the legacy Buffer Size field). The legacy BSR is the BSR from which the enhanced-BSR is modified. For example, the legacy BSR may be a BSR classified as a Regular BSR, Periodic BSR, or Padding BSR. That is, the legacy BSR may be a Short BSR, Long BSR, Extended Short BSR, Extended Long BSR, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, Extended Long Truncated BSR, Pre-emptive BSR, or Extended Pre-emptive BSR. Furthermore, for example, a code point (or an index) corresponding to each of the legacy BSRs may be specified as the value of LCID / eLCID for the UL-SCH. That is, a code point (or an index) corresponding to each of Short BSR, Long BSR, Extended Short BSR, Extended Long BSR, Short Truncated BSR, Long Truncated BSR, Extended Short Truncated BSR, Extended Long Truncated BSR, Pre-emptive BSR, and / or Extended Pre-emptive BSR may be specified as the value of LCID / eLCID for the UL-SCH. For example, UE 200 may transmit any of the legacy BSRs identified by the value of LCID / eLCID based on a setting from base station 100 and / or a condition.

[0081] The format of the BS-extended BSR according to this embodiment will be described in detail with reference to Fig. 10. Fig. 10 shows an example of the MAC CE format of the BS-extended BSR in which the Buffer Size field of the legacy Long BSR is extended. Note that the BS-extended BSR is not limited to the legacy Long BSR, and may be a BSR in which the Buffer Size field of the legacy BSR in another format is extended.

[0082] For example, the BS Extended BSR includes an LCGi field as the first field and an Extended Buffer Size j field as the extended second field, as shown in format 21 in Figure 10. The LCGi field indicates the presence of an Extended Buffer Size j field for LCGi.

[0083] The Extended Buffer Size j field is used to identify the total amount of data available in all logical channels belonging to the corresponding LCGi. The size of a given Extended Buffer Size j field is, for example, 16 bits (or 8 bits), which is longer than the 8-bit (or 5-bit) size of the Legacy Buffer Size j field. The Legacy Buffer Size j field is the Buffer Size field from which the Extended Buffer Size j field is changed. Note that the size of the Extended Buffer Size j field is not limited to this and may be any other size (e.g., 24 bits) longer than the Legacy Buffer Size j field. The size of the Extended Buffer Size j field may also vary depending on the corresponding LCGi. Here, 8 bits is also referred to as 1 octet. In other words, 16 bits is also referred to as 2 octets.

[0084] The Extended Buffer Size j field indicates an index corresponding to a Buffer Size (e.g., a Buffer Size level, a Buffer Size value, or a Buffer Size range) in a table for a 16-bit Buffer Size field (not shown), and the Extended Buffer Size j fields are included in ascending order according to LCGi (e.g., according to the value of i in LCGi).

[0085] The BS-extended BSR is distinguished from BSRs of other formats. For example, an LCID / eLCID indicating the BS-extended BSR is defined. For example, a code point (or index) corresponding to the BS-extended BSR may be specified as the LCID / eLCID value for the UL-SCH. This enables the BS-extended BSR to be transmitted as a MAC CE. The MAC CE of the BS-extended BSR may be included in a MAC PDU (protocol data unit) and transmitted. For example, a MAC PDU may include one or more MAC subPDUs, and each MAC subPDU may include a MAC subheader and a MAC CE. Here, the MAC subheader may include the LCID / eLCID. That is, a MAC subheader including the LCID / eLCID indicating the BS-extended BSR and the MAC CE of the BS-extended BSR are included in the MAC subPDU, and the MAC PDU including the MAC subPDU is transmitted.

[0086] (2) BS Extended BSR Configuration Information Configuration information for determining whether to use the BS Extended BSR according to this embodiment (hereinafter also referred to as BS Extended BSR Configuration Information) is defined. The BS Extended BSR Configuration Information is included in the logical channel configuration information. As a result, the BS Extended BSR is configured for each logical channel. The BS Extended BSR Configuration Information will be described in detail with reference to Figures 11 and 12.

[0087] Specifically, the BS extended BSR configuration information is included in LogicalChannelConfig. That is, the configuration information of the logical channel may correspond to LogicalChannelConfig. For example, LogicalChannelConfig may be used to configure parameters of the logical channel. Furthermore, LogicalChannelConfig may include parameters related to the BSR. For example, one or more parameters included in LogicalChannelConfig may be used to identify one logical channel. For example, LogicalChannelConfig may include a parameter (logicalChannelGroup) indicating an index of a logical channel group to which the one logical channel belongs. That is, the logical channel group to which the one logical channel belongs may be identified based on the parameter indicating the index of the logical channel group. For example, the base station 100 may transmit LogicalChannelConfig including one or more parameters for the one logical channel to the UE 200. Here, the base station 200 may transmit an RRC message including the LogicalChannelConfig to the UE 200. Furthermore, the UE 200 may identify the one logical channel based on one or more parameters included in LogicalChannelConfig. For example, the UE 200 may identify the logical channel group to which the one logical channel belongs based on a parameter indicating the index of the logical channel group included in the LogicalChannelConfig. Here, as described above, the UE 200 may transmit a BSR for a logical channel group to which one or more logical channels belong. As a specific example of the above, as shown in information 31 in Fig. 11 , BSR-BSExtApplied as BS extended BSR configuration information may be included as a parameter of the LogicalChannelConfig.

[0088] The BS extended BSR configuration information is a flag. For example, as shown in Table 41 of FIG. 12 , when BSR-BSExtApplied is present, it indicates that UE 200 is configured to report the BS extended BSR. Conversely, when BSR-BSExtApplied is absent, it indicates that UE 200 is not configured to report the BS extended BSR, i.e., is configured to report the legacy BSR. Note that the BS extended BSR configuration information is not limited to a flag indicating whether or not the BS extended BSR is used, but may be a flag indicating whether or not the BS extended BSR is used, depending on its value. For example, the BS extended BSR configuration information may indicate whether or not the legacy BSR is used when its value is 0, and whether or not the BS extended BSR is used when its value is 1. Here, the presence of BSR-BSExtApplied may correspond to the presence of BSR-BSExtApplied in LogicalChannelConfig. In other words, the presence of BSR-BSExtApplied may correspond to the presence of BSR-BSExtApplied included in LogicalChannelConfig. Furthermore, the case where BSR-BSExtApplied does not exist may correspond to the case where BSR-BSExtApplied does not exist in LogicalChannelConfig. In other words, the case where BSR-BSExtApplied does not exist may correspond to the case where BSR-BSExtApplied is not included in LogicalChannelConfig. Below, we will mainly describe the case where BSR-BSExtApplied exists or the case where BSR-BSExtApplied does not exist, but the case where BSR-BSExtApplied exists may be replaced by the case where the value of the BS extended BSR configuration information is 1. Furthermore, the case where BSR-BSExtApplied does not exist may be replaced by the case where the value of the BS extended BSR configuration information is 0. Furthermore, the case where BSR-BSExtApplied exists may also be described as the case where BSR-BSExtApplied is configured.In addition, the case where BSR-BSExtApplied does not exist is also referred to as the case where BSR-BSExtApplied is not set.

[0089] (3) Message Including Configuration Information The configuration information for determining whether to use the BS extended BSR according to this embodiment is transmitted in a message, which may be an RRC message.

[0090] For example, the BS extended BSR configuration information is transmitted in an RRC message including LogicalChannelConfig. The RRC message may be, for example, RRCReconfiguration, RRCResume, or RRCSetup. Alternatively, an RRC message different from the above-described RRC message may be used. Here, the base station 100 may transmit LogicalChannelConfig including the BS extended BSR configuration information to the UE 200. For example, the base station 100 may transmit an RRC message including LogicalChannelConfig to the UE 200. The UE 200 may determine a BSR-related operation based on the BS extended BSR configuration information. For example, the UE 200 may identify a logical channel group to which a logical channel belongs based on the BS extended BSR configuration information, and transmit a BSR for the logical channel group.

[0091] (4) Operation of UE 200 Based on Configuration Information The UE 200 according to this embodiment receives configuration information for determining whether to use the BS-extended BSR according to this embodiment. The UE 200 acquires the configuration information from a message including the received configuration information. The UE 200 determines the BSR to use based on the acquired configuration information.

[0092] Specifically, UE 200 determines whether to use the BS-extended BSR based on the BS-extended BSR configuration information acquired from the received RRC message. For example, UE 200 determines whether to use the BS-extended BSR for each logical channel based on the BS-extended BSR configuration information included in the configuration information of the logical channel. UE 200 uses the BS-extended BSR when reporting the buffer status for the LCG to which the logical channel for which it has been determined that the BS-extended BSR should be used belongs.

[0093] For example, if the LogicalChannelConfig included in the received RRC message includes BSR-BSExtApplied as shown in Figure 11, UE200 uses the BS extended BSR as the BSR for the LCG that includes the logical channel to which the LogicalChannelConfig is set.

[0094] (5) Processing Flow An example of processing according to this embodiment will be described with reference to FIG.

[0095] The base station 100 sets configuration information for determining whether to use enhanced-BSR (i.e., BS extended BSR configuration information in this embodiment) in an RRC message (step S310). For example, the base station 100 acquires BSR-BSExtApplied as shown in Fig. 11 and sets BSR-BSExtApplied to LogicalChannelConfig.

[0096] The base station 100 transmits an RRC message including the BS extended BSR setting information to the UE 200 (step S320). For example, the base station 100 transmits to the UE 200 an RRC message (e.g., RRCReconfiguration, RRCResume, or RRCSetup) including LogicalChannelConfig in which BSR-BSExtApplied is set.

[0097] When the UE 200 receives the RRC message including the BS extended BSR setting information, the UE 200 transmits an RRC message in response to the RRC message to the base station 100 (step S330). For example, when the UE 200 receives an RRC message including LogicalChannelConfig in which BSR-BSExtApplied is set, the UE 200 transmits an RRC message in response (for example, RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete) to the base station 100.

[0098] The UE 200 determines whether to use enhanced-BSR based on the received configuration information (step S340). For example, when a BSR is triggered, the UE 200 uses the BS-enhanced BSR if the LogicalChannelConfig for any logical channel belonging to the LCG reporting the buffer status in the BSR includes BSR-BSExtApplied. Otherwise, the UE 200 uses a legacy BSR, i.e., a BSR with a non-extended Buffer Size field. That is, the UE 200 may report a BS-enhanced BSR (i.e., enhanced-BSR MAC CE) based on the setting of BSR-BSExtApplied for at least one logical channel belonging to the LCG for which the BSR is reported. Alternatively, the UE 200 may report a legacy BSR based on the setting of BSR-BSExtApplied for none of the logical channels belonging to the LCG for which the BSR is reported. That is, the UE 200 may determine whether to report a BS enhanced BSR (e.g., enhanced-BSR MAC CE) based on whether BSR-BSExtApplied is configured (e.g., whether BSR-BSExtApplied is configured by a higher layer). Also, the UE 200 may determine whether to transmit a BS enhanced BSR (e.g., enhanced-BSR MAC CE) based on whether BSR-BSExtApplied is included in the LogicalChannelConfig.

[0099] Here, the BS extended BSR format may be used for Regular BSR, Periodic BSR, and / or Padding BSR. For example, for Regular BSR, Periodic BSR, and / or Padding BSR, UE 200 may report the BS extended BSR based on the setting of BSR-BSExtApplied. For example, for Regular BSR, Periodic BSR, and / or Padding BSR, UE 200 may report the BS extended BSR based on the setting of BSR-BSExtApplied and the existence of two or more LCGs with available data when the MAC PDU including the BSR was built. Also, for Regular BSR, Periodic BSR, and / or Padding BSR, UE 200 may report the BS extended BSR based on the setting of BSR-BSExtApplied and the existence of one or more LCGs with available data when the MAC PDU including the BSR was built. Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, UE 200 may report a BS-extended BSR based on the fact that BSR-BSExtApplied is configured, there are two or more (or one or more) LCGs with available data when the MAC PDU containing the BSR is built, and the ID of the largest LCG among the configured LCGs is greater than 7. Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, UE 200 may report a BS-extended BSR based on the fact that BSR-BSExtApplied is configured, there are two or more (or one or more) LCGs with available data when the MAC PDU containing the BSR is built, and the ID of the largest LCG among the configured LCGs is greater than 256. Here, UE 200 may report a BS-extended BSR for all LCGs with available data for transmission.

[0100] Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, the UE 200 may report a Legacy BSR based on the fact that BSR-BSExtApplied is not configured. Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, the UE 200 may report a Legacy BSR based on the fact that BSR-BSExtApplied is configured and there is one LCG with available data when the MAC PDU including the BSR is built. Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, the UE 200 may report a Legacy BSR based on the fact that BSR-BSExtApplied is configured and there are two or more LCGs with available data when the MAC PDU including the BSR is built and the ID of the largest LCG among the configured LCGs is 7 or less. Furthermore, for a Regular BSR, a Periodic BSR, and / or a Padding BSR, the UE 200 may report a legacy BSR based on the following: BSR-BSExtApplied is configured; there are two or more LCGs with available data when the MAC PDU containing the BSR is built; and the ID of the largest LCG among the configured LCGs is 256 or less. Here, the UE 200 may report legacy BSRs for all LCGs with available data for transmission. As described above, for example, the legacy BSR may be a Short BSR, a Long BSR, an Extended Short BSR, an Extended Long BSR, a Short Truncated BSR, a Long Truncated BSR, an Extended Short Truncated BSR, an Extended Long Truncated BSR, a Pre-emptive BSR, or an Extended Pre-emptive BSR.

[0101] Here, the maximum number of LCGs configured using logicalChannelGroup may be eight (e.g., eight LCG IDs from 0 to 7). That is, the ID of an LCG configured using logicalChannelGroup may be any value from 0 to 7. Also, the maximum number of LCGs configured using logicalChannelGroup-IAB-Ext-r17 may be 256 (e.g., 256 LCG IDs from 0 to 255). UE 200 may report a legacy BSR for LCGs corresponding to ID values ​​that can be configured using logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17.

[0102] Furthermore, for the Padding BSR, the UE 200 may report a BS-extended BSR based on the fact that BSR-BSExtApplied is set and the number of padding bits is larger than the size of the legacy BSR (and / or the subheader of the legacy BSR). For the Padding BSR, the UE 200 may report a legacy BSR based on the fact that BSR-BSExtApplied is set and the number of padding bits is smaller than the size of the legacy BSR (and / or the subheader of the legacy BSR). Here, the UE 200 may report BS-extended BSRs or legacy BSRs for all LCGs having data available for transmission. Furthermore, the UE 200 may report a BS-extended BSR or legacy BSR for an LCG to which a logical channel determined based on the prioritization belongs, among logical channels having data available for transmission.

[0103] The UE 200 transmits the enhanced-BSR MAC CE to the base station 100 (step S350). For example, the UE 200 generates a BS enhanced BSR MAC CE by setting an index corresponding to the UL data buffer size in the extended buffer size field according to the LCG, as shown in FIG. 10 . The UE 200 transmits the generated BS enhanced BSR MAC CE to the base station 100. For example, the UE 200 may transmit the enhanced-BSR MAC CE by applying a logical channel prioritization (LCP) procedure. Here, the logical channel prioritization procedure may be a procedure applied when an initial transmission is performed. For example, in the logical channel prioritization procedure, logical channels (e.g., MAC CEs of logical channels) may be prioritized in the following order: In the following, a logical channel with a higher priority is listed first. - MAC CE for C-RNTI or data from UL-CCCH - MAC CE for (Extended) BSR, with the exception of BSR included for padding - MAC CE for (Extended) Pre-emptive BSR - data from any Logical Channel, except data from UL-CCCH - MAC CE for BSR included for padding For example, enhanced-BSR MAC CE may have higher priority than MAC CE for (Extended) BSR, with the exception of BSR included for padding. For example, enhanced-BSR MAC CE may be specified to have lower priority than MAC CE for C-RNTI or data from UL-CCCH, but higher priority than MAC CE for (Extended) BSR. Also, enhanced-BSR MAC CE may have higher priority than MAC CE for (Extended) Pre-emptive BSR.For example, the enhanced-BSR MAC CE may be specified to have lower priority than MAC CE for (Extended) BSR, with the exception of BSR included for padding, but higher priority than MAC CE for (Extended) Pre-emptive BSR. Furthermore, the enhanced-BSR MAC CE may be specified to have higher priority than data from any logical channel, except data from UL-CCCH. For example, the enhanced-BSR MAC CE may be specified to have lower priority than MAC CE for (Extended) Pre-emptive BSR, but higher priority than data from any logical channel, except data from UL-CCCH. Furthermore, the enhanced-BSR MAC CE may be specified to have higher priority than MAC CE for BSR included for padding. For example, the enhanced-BSR MAC CE may be specified to have lower priority than data from any logical channel, except data from UL-CCCH, but higher priority than MAC CE for BSR included for padding. For example, the UE 200 may report the enhanced-BSR MAC CE according to the priority in the logical channel prioritization (LCP) procedure.

[0104] Thus, according to an embodiment of the present disclosure, a message is transmitted and received that includes configuration information for determining whether to use a BSR that includes at least one first field and at least one modified second field, the BSR being used to provide information about the amount of UL data, the at least one first field indicating at least one LCG for which a buffer status is reported, and the at least one modified second field corresponding to the at least one LCG and relating to the amount of UL data.

[0105] This allows for more information about the amount of UL data in the BSR than in a BSR that includes the first and second fields (i.e., a legacy BSR). Therefore, it is possible to improve the efficiency of scheduling UL data using the BSR. In particular, it is possible to implement a method for scheduling XR data using an XR-specific BSR, thereby improving the efficiency of scheduling XR data using an XR-specific BSR.

[0106] The setting information is included in the setting information of the logical channel. This allows the setting information to be set for each logical channel. In particular, since the logical channel can be associated with XR traffic, the setting information can be set for XR traffic.

[0107] Furthermore, the setting information is a flag, which allows the setting information to be handled with a small amount of data, thereby suppressing an increase in communication resources for signaling the setting information.

[0108] Furthermore, the at least one modified second field is the second field with an increased size. This allows the amount of information regarding the UL data amount to be increased by following the method of the second field. For example, the range or granularity of the UL data amount that can be handled can be expanded. That is, the upper limit of the UL data amount can be raised or the granularity can be further refined.

[0109] Furthermore, the at least one modified second field is a Buffer Size field indicating information used to indicate the total amount of data for each logical channel of the at least one corresponding LCG. This allows the range or granularity of the buffer size that can be handled by the Buffer Size field to be expanded. As a result, it is possible to reduce quantization errors for UL data (e.g., XR data) that has a large volume and fluctuates greatly.

[0110] 5-2. Modifications> First to fourth modification examples according to the first embodiment of the present disclosure will be described with reference to Figures 14 to 20. Note that two or more of these modification examples may be combined.

[0111] (1) First Modification: Another Example of BS Extended BSR Configuration Information In the above-described embodiment of the present disclosure, the BS extended BSR configuration information is a flag. However, the BS extended BSR configuration information according to the embodiment of the present disclosure is not limited to this example.

[0112] As a first modification of this embodiment, the BS extended BSR configuration information may be information regarding the length of at least one modified second field. Specifically, the BS extended BSR configuration information is information indicating the length of the second field whose size has been increased. The BS extended BSR configuration information according to this modification will be described in detail with reference to Figures 14 and 15.

[0113] For example, as shown in information 33 in FIG. 14 , BSR-BufferSizeFieldLength as BS extended BSR setting information is included as a parameter of LogicalChannelConfig. For example, as shown in table 43 in FIG. 15 , BSR-BufferSizeFieldLength indicates the length of the Buffer Size field. Whether BSR-BufferSizeFieldLength exists indicates whether the BS extended BSR is used. For example, if BSR-BufferSizeFieldLength exists, it indicates that UE 200 is configured to report a BS extended BSR and indicates the length of the extended Buffer Size field in the BS extended BSR. Conversely, if BSR-BufferSizeFieldLength does not exist, it indicates that UE 200 is not configured to report a BS extended BSR, i.e., is configured to report a legacy BSR.

[0114] Furthermore, BSR-BufferSizeFieldLength may indicate information for indicating the length of the Buffer Size field. For example, BSR-BufferSizeFieldLength indicates an index corresponding to the length of the Buffer Size field (for example, the value or range of the length).

[0115] Furthermore, as a first modified example 2 of this embodiment, the BS extended BSR configuration information may be information for identifying an LCG that uses the BS extended BSR. That is, the BS extended BSR configuration information may indicate the ID of an LCG. For example, the BS extended BSR configuration information may indicate the ID of an LCG to which a logical channel belongs. For example, the UE 200 may determine the ID of the LCG to which a logical channel belongs based on the ID of the LCG indicated by the BS extended BSR configuration information. The BS extended BSR configuration information according to this modified example will be described in detail with reference to Figures 16 and 17.

[0116] For example, as shown in information 35 in FIG. 16 , logicalChannelGroup-XR-Ext-r18 as BS extended BSR configuration information is included as a parameter of LogicalChannelConfig. For example, as shown in table 45 in FIG. 17 , logicalChannelGroup-XR-Ext-r18 may indicate an LCG ID. For example, logicalChannelGroup-XR-Ext-r18, if present, may indicate the LCG ID to which the logical channel belongs. Furthermore, logicalChannelGroup-XR-Ext-r18 may indicate that the UE 200 is configured to report a BS extended BSR for the LCG ID. Furthermore, if logicalChannelGroup-XR-Ext-r18 does not exist, it may indicate that the UE 200 is not configured to report a BS extended BSR, i.e., is configured to report a legacy BSR.

[0117] Note that when logicalChannelGroup-XR-Ext-r18 is configured, other LCG ID configurations may be ignored. In this case, for example, logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 as shown in FIG. 16 may be ignored. That is, when logicalChannelGroup-XR-Ext-r18 indicating an LCG ID is included in the logical channel config, UE 200 may ignore logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 included in the logical channel config. As described above, logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 indicate an LCG ID. Here, the maximum number of LCGs configured using logicalChannelGroup-XR-Ext-r18 may be eight (e.g., eight LCG IDs from 0 to 7, or eight LCG IDs from 8 to 15). That is, the ID of an LCG set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 7 (or any value from 8 to 15). For example, by setting the ID of an LCG set using logicalChannelGroup-XR-Ext-r18 to 8 to 15, it is possible to set an LCG ID that is different from the ID of an LCG set using logicalChannelGroup (i.e., 0 to 7). Furthermore, the maximum number of LCGs that can be set using logicalChannelGroup-XR-Ext-r18 may be 16 (for example, 16 LCG IDs from 0 to 15, or 16 LCG IDs from 8 to 23). That is, the ID of an LCG set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 15 (or any value from 8 to 23).For example, by setting the number of LCG IDs to 16 using logicalChannelGroup-XR-Ext-r18, it becomes possible to set more LCG IDs than the number of LCG IDs (i.e., 8) set using logicalChannelGroup. Furthermore, the maximum number of LCGs set using logicalChannelGroup-XR-Ext-r18 may be 256 (e.g., 256 LCG IDs from 0 to 255, or 256 LCG IDs from 256 to 511). That is, the ID of an LCG set using logicalChannelGroup-XR-Ext-r18 may be any value from 0 to 255 (or any value from 256 to 511). For example, by setting the ID of an LCG set using logicalChannelGroup-XR-Ext-r18 from 256 to 511, it becomes possible to set an LCG ID that is different from the ID of an LCG set using logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 (i.e., 0 to 255). In this way, when logicalChannelGroup-XR-Ext-r18 is set for UE200, by ignoring the settings of other LCG IDs, it becomes possible to easily perform operations related to BSR without setting an LCG ID using different parameters.

[0118] In addition, as a first modification 3 of this embodiment, the BS extended BSR configuration information may be information used to indicate the type of UL data, such as pose / control or video.

[0119] For example, as shown in information 37 in Fig. 18, BSR-DataType-XR as BS extended BSR setting information is included as a parameter of LogicalChannelConfig. For example, as shown in table 47 in Fig. 19, when BSR-DataType-XR exists, it indicates that UE 200 is configured to report a BS extended BSR for the LCG to which the logical channel to which the UL data of the indicated type belongs belongs. Conversely, when BSR-DataType-XR does not exist, it indicates that UE 200 is not configured to report a BS extended BSR, i.e., is configured to report a legacy BSR.

[0120] As described above, according to the first modification of the present embodiment, the BS extended BSR configuration information may be information regarding at least one changed length of the second field. This allows the information regarding the changed length of the second field to indicate whether the BS extended BSR is to be used. This reduces the need for additional communication resources for signaling the BS extended BSR configuration information. Furthermore, since the BS extended BSR configuration information indicates the length of the increased second field, the size of the changed second field can be dynamically changed.

[0121] According to the first modified example 2 of this embodiment, the BS-extended BSR configuration information may be information for identifying an LCG that uses the BS-extended BSR. In this way, whether to use the BS-extended BSR and the LCG ID are combined into one piece of information, so that it is possible to specify the LCG ID of a logical channel and simultaneously determine whether to use the BS-extended BSR.

[0122] Furthermore, according to the first modified example 3 of this embodiment, the BS extended BSR configuration information may be information used to indicate the type of UL data. This makes it possible to indicate whether or not to use the BS extended BSR for each type of UL data. Therefore, an appropriate BSR can be selected depending on the type of UL data. In particular, the characteristics of XR data vary greatly depending on the data type. Therefore, selecting an appropriate BSR depending on the type of XR data enables scheduling appropriate for the XR data.

[0123] (2) Second Modification: Another Example of Configuration Information Including BS Extended BSR Configuration Information In the above-described embodiment of the present disclosure, the BS extended BSR configuration information is included in the configuration information of the logical channel. However, the BS extended BSR configuration information according to the embodiment of the present disclosure is not limited to this example.

[0124] As a second modification 1 of this embodiment, the BS extended BSR configuration information may be included in the LCG configuration information. As a result, the BS extended BSR is configured for each LCG. This modification will be described in detail with reference to Figure 20.

[0125] For example, LCG configuration information 51 is newly added as RRC configuration information, and the BS extended BSR configuration information is included in the LCG configuration information 51 as shown in Fig. 20. The LCG configuration information 51 is included in an RRC message and transmitted to the UE 200.

[0126] As a second modification of this embodiment, the BS extended BSR configuration information may be included in the SR configuration information, whereby the BS extended BSR is configured for each SR.

[0127] For example, the BS extended BSR configuration information is included in SchedulingRequestConfig or SchedulingRequestResourceConfig, which are examples of SR configuration information 53 as shown in FIG. 20, and is associated with a schedulingRequestID. Here, the schedulingRequestID is also included in the logical channel configuration information. Therefore, the UE 200 refers to the BS extended BSR configuration information included in the SR configuration information 53 via the schedulingRequestID configured for the logical channel belonging to the LCG, and determines whether to use the BS extended BSR for the LCG. In other words, the BS extended BSR is indirectly configured for each logical channel via the schedulingRequestID.

[0128] As a second modification 3 of the present embodiment, the BS extended BSR configuration information may be included in the BSR configuration information. That is, the BS extended BSR indicates whether to use the BS extended BSR as the BSR of the UE 200. In this way, the BS extended BSR is configured for each UE 200.

[0129] For example, the BS extended BSR setting information is included in BSR-Config, which is an example of BSR setting information 55, as shown in Fig. 20. The UE 200 refers to the BS extended BSR setting information included in BSR-Config and determines whether to use the BS extended BSR.

[0130] As described above, according to the second modification 1 of the present embodiment, the BS extended BSR configuration information may be included in the LCG configuration information. This allows the BS extended BSR configuration information to be configured for each LCG. Since the BSR is reported for each LCG, processing can be reduced compared to when the BS extended BSR is configured for each logical channel.

[0131] According to the second modification 2 of the present embodiment, the BS extended BSR configuration information may be included in the SR configuration information. This allows the BS extended BSR configuration information to be configured for each SR. Therefore, it is possible to collectively manage whether or not to use the BS extended BSR for at least one logical channel configured for the same SR.

[0132] According to the second modification 3 of the present embodiment, the BS extended BSR configuration information may be included in the BSR configuration information. This allows the BS extended BSR configuration information to be configured for each UE 200. Therefore, all BSRs used by the UE 200 can be switched simultaneously to be either the BS extended BSR or not.

[0133] (3) Third Modification: Another Example of the Format of the BS Extended BSR In the embodiment of the present disclosure described above, the BS extended BSR includes the first field and a modified second field. However, the BS extended BSR according to the embodiment of the present disclosure is not limited to this example.

[0134] In a third variation of this embodiment, the BS-extended BSR may further include at least one second field, where the at least one extended second field corresponds to an LCG among the plurality of LCGs that is identified based on the BS-extended BSR configuration information, and the at least one second field corresponds to an LCG among the plurality of LCGs other than the LCG identified based on the BS-extended BSR configuration information. In other words, only the Buffer Size field corresponding to the LCG among the plurality of LCGs that is identified based on the BS-extended BSR configuration information is extended.

[0135] Specifically, the BS-extended BSR includes multiple LCG fields, at least one extended buffer size field, and at least one legacy buffer size field, where the at least one extended buffer size field corresponds to an LCG that is determined to use the BS-extended BSR based on the BS-extended BSR configuration information, and the at least one legacy buffer size field corresponds to an LCG other than the LCG.

[0136] This modification will be described in detail with reference to Fig. 10. For example, assume that in format 21 of Fig. 10, Buffer Size 1 corresponds to LCG0 and Buffer Size 2 corresponds to LCG1. If it is determined to use the BS-extended BSR for LCG0, the BS-extended BSR includes a Buffer Size 1 field, which is longer than the legacy Buffer Size field, as the extended Buffer Size field. If it is not determined to use the BS-extended BSR for LCG1, the BS-extended BSR includes a Buffer Size 2 field as the legacy Buffer Size field.

[0137] According to the third modification of the present embodiment, the BS-extended BSR further includes at least one second field, where the at least one LCG is a plurality of LCGs, and the at least one extended second field corresponds to an LCG among the plurality of LCGs that is specified based on the BS-extended BSR configuration information, and the at least one second field corresponds to an LCG among the plurality of LCGs other than the LCG specified based on the configuration information. This allows only the second field that needs to be extended to be extended, thereby preventing an excessive increase in the size of the BSR. As a result, it is possible to prevent waste of communication resources due to BSR transmission.

[0138] (4) Fourth Modification: Compliance with Other TS In the above-described example of the embodiment of the present disclosure, the system 1 is a system that complies with the 5G or NR TS. However, the system 1 according to the embodiment of the present disclosure is not limited to this example.

[0139] In a fourth modification of this embodiment, the system 1 may be a system conforming to another 3GPP TS. As an example, the system 1 may be a system conforming to LTE (Long Term Evolution), LTE-A (LTE Advanced), or 4G TS, and the base station 100 may be an eNB (evolved Node B). Alternatively, the base station 100 may be an ng-eNB. As another example, the system 1 may be a system conforming to 3G TS, and the base station 100 may be a Node B. As yet another example, the system 1 may be a system conforming to next-generation (e.g., 6G) TS.

[0140] Alternatively, the system 1 may be a system conforming to a TS of another standardization body for mobile communications.

[0141] 6. Second Embodiment In a second embodiment of the present disclosure, configuration information for determining whether to use a BSR whose modified second field includes delay information (hereinafter also referred to as a delayed BSR) is transmitted from the base station 100 to the UE 200. Note that a description of the contents that are substantially the same as those in the first embodiment will be omitted.

[0142] 6-1. Operational Example> An exemplary operation of the base station 100 and the UE 200 according to the second embodiment of the present disclosure will be described with reference to FIGS.

[0143] (1) Format of the Delayed BSR The modified second field of the delayed BSR according to this embodiment includes a second field and a third field different from the second field. In other words, the modified second field is obtained by adding the third field to the second field.

[0144] Specifically, the modified second field includes a Buffer Size field as the second field and a Delay Information field as the third field. The Delay Information field indicates information used to indicate delay information of an LCG. The Delay Information field indicates information used to indicate the remaining time until the allowable delay of data belonging to the corresponding LCG.

[0145] The format of the delayed BSR according to this embodiment will be described in detail with reference to Figures 21A and 21B. Figures 21A and 21B show an example of the MAC CE format of a delayed BSR in which the Buffer Size field of a legacy Long BSR has been modified. Note that the delayed BSR is not limited to a legacy Long BSR, and may be a BSR in which the Buffer Size field of a legacy BSR in any of the above-mentioned other formats has been modified.

[0146] For example, a delayed BSR includes an LCGi field as a first field and a reduced Buffer Size j field and a Delay Info j field as modified second fields, as shown in format 23A of Figure 21 A. The LCGi field indicates the presence of the reduced Buffer Size j field and the Delay Info j field for LCGi.

[0147] The reduced Buffer Size j field, like the legacy Buffer Size j field, identifies the total amount of data available in all logical channels belonging to the corresponding LCGi. The size of the reduced Buffer Size j field is, for example, 6 bits, which is shorter than the 8-bit size of the legacy Buffer Size j field. Note that the size of the reduced Buffer Size j field is not limited to this and may be any other size shorter than the legacy Buffer Size j field. Furthermore, the size of the reduced Buffer Size j field may vary depending on the corresponding LCGi.

[0148] The reduced Buffer Size j field indicates an index corresponding to a Buffer Size (eg, a Buffer Size level, a Buffer Size value, or a Buffer Size range) in a table for a 6-bit Buffer Size field (not shown), for example.

[0149] The Delay Info j field as the third field indicates information used to indicate delay information of the corresponding LCGi. The size of the Delay Info j field is, for example, 2 bits, which is shorter than the size of the legacy Buffer Size j field, which is 8 bits. The sum of the size of the reduced Buffer Size j field and the size of the Delay Info j field is equal to the size of the legacy Buffer Size j field. Note that the size of the Delay Info j field is not limited to this and may be any other size shorter than the legacy Buffer Size j field. Furthermore, the size of the Delay Info j field may differ depending on the corresponding LCGi.

[0150] The Delay Info j field indicates the remaining time until the allowable delay of data belonging to the corresponding LCG (e.g., indicated in units of ms, slots, or subframes). Note that the Delay Info j field may indicate an index corresponding to the remaining time (e.g., a value or range of the remaining time), or may indicate a flag corresponding to the remaining time (e.g., a flag indicating the length of the remaining time).

[0151] The reduced Buffer Size j field and the Delay Info j field are treated as a single entity, and combinations of these are included in ascending order according to LCGi.

[0152] Alternatively, for example, the delayed BSR may include an LCGi field as a first field and a legacy Buffer Size j field and a Delay Info i field as modified second fields, as shown in format 23B of FIG. 21B.

[0153] In format 23A, the Delay Info j field replaces part of the Legacy Buffer Size field, but in format 23B, the Delay Info i field is added to the Legacy Buffer Size field. For example, the Delay Info i field is added between the LCGi field and the Legacy Buffer Size field. Note that the Delay Info i field may also be added after the Legacy Buffer Size field.

[0154] The content and size of the Delay Info i field are the same as those of format 23 A. The Buffer Size j field and the Delay Info i field are included in ascending order according to LCGi.

[0155] A delayed BSR is distinguished from BSRs of other formats. For example, an LCID / eLCID indicating a delayed BSR is defined. This allows the delayed BSR to be transmitted as a MAC CE. The MAC CE of the delayed BSR may be included in a MAC PDU for transmission. That is, a MAC subheader including an LCID / eLCID indicating a delayed BSR and the MAC CE of the delayed BSR are included in a MAC subPDU, and the MAC PDU including the MAC subPDU is transmitted.

[0156] (2) Delayed BSR Configuration Information Configuration information for determining whether to use a delayed BSR according to this embodiment (hereinafter also referred to as delayed BSR configuration information) is defined. The delayed BSR configuration information is included in the logical channel configuration information. As a result, a delayed BSR is configured for each logical channel. The delayed BSR configuration information will be described in detail with reference to Figures 22 and 23.

[0157] Specifically, the delayed BSR setting information is included in LogicalChannelConfig. For example, as shown in information 39 in Fig. 22 , BSR-DelayApplied as delayed BSR setting information may be included as a parameter of LogicalChannelConfig. Note that LogicalChannelConfig according to this embodiment may be substantially the same as LogicalChannelConfig described in the first embodiment except for BSR-BSExtApplied, and the part related to BSR-BSExtApplied may be replaced with BSR-DelayApplied.

[0158] The delayed BSR configuration information is also a flag. For example, as shown in Table 49 of FIG. 23 , when BSR-DelayApplied is present, it indicates that UE 200 is configured to report a delayed BSR. Conversely, when BSR-DelayApplied is absent, it indicates that UE 200 is not configured to report a delayed BSR, i.e., is configured to report a legacy BSR. Note that the delayed BSR configuration information is not limited to a flag indicating whether a delayed BSR is used or not depending on whether it exists, but may also be a flag indicating whether a delayed BSR is used or not depending on its value. For example, the delayed BSR configuration information may indicate whether a legacy BSR is used or not when its value is 0, and indicate whether a delayed BSR is used or not when its value is 1.

[0159] (3) Message Containing Configuration Information The message containing delayed BSR configuration information is substantially the same as the message containing BS extended BSR configuration information, and therefore a description thereof will be omitted.

[0160] (4) Operation of UE 200 Based on Configuration Information The UE 200 according to this embodiment determines whether to use a delayed BSR based on the delayed BSR configuration information acquired from a received RRC message. For example, the UE 200 determines whether to use a delayed BSR for a logical channel based on the delayed BSR configuration information included in the configuration information of the logical channel. The UE 200 uses the delayed BSR when reporting the buffer status for the LCG to which the logical channel for which it has been determined that the delayed BSR should be used belongs.

[0161] For example, if the LogicalChannelConfig included in the received RRC message includes BSR-DelayApplied as shown in FIG. 22, UE 200 uses a delayed BSR as the BSR for the LCG that includes the logical channel for which the LogicalChannelConfig is set.

[0162] (5) Processing Flow An example of processing according to this embodiment will be described with reference to Fig. 13. Note that the processing from step S310 to step S340 is implemented by replacing the BS-Extended BSR according to the first embodiment with a Delayed BSR, and replacing the BSR-BSExtApplied according to the first embodiment with BSR-DelayApplied, and therefore the description thereof will be omitted.

[0163] The UE 200 transmits the enhanced-BSR MAC CE to the base station 100 (step S350). For example, the UE 200 generates a delayed BSR MAC CE by setting an index corresponding to the buffer size of the UL data in the corresponding reduced Buffer Size field and setting delay information in the corresponding Delay Info field for each LCG, as shown in FIG. 21A . Alternatively, the UE 200 generates a delayed BSR MAC CE by setting an index corresponding to the buffer size of the UL data in the corresponding Buffer Size field and setting delay information in the corresponding Delay Info field for each LCG, as shown in FIG. 21B . The UE 200 transmits the generated delayed BSR MAC CE to the base station 100. Note that the UE 200 may transmit the enhanced-BSR MAC CE (i.e., the MAC CE of the delayed BSR) by applying the Logical Channel Prioritization (LCP) procedure, as in the first embodiment.

[0164] Thus, according to an embodiment of the present disclosure, the modified second field included in the enhanced-BSR includes a second field and a third field different from the second field, thereby allowing for the addition of information with content and / or format different from the information indicated by the second field.

[0165] Furthermore, the second field is a Buffer Size field indicating information used to indicate the total amount of data for each logical channel of the corresponding at least one LCG, and the third field is a field indicating information used to indicate delay information for the corresponding at least one LCG, where the delay information indicates information used to indicate the remaining time until the allowable delay of data belonging to the corresponding at least one LCG. This makes it possible to report delay information for buffered data. Therefore, scheduling can be performed taking the delay information into consideration for the data. In particular, since a PDB may be imposed on XR data, reporting delay information for the XR data using a delayed BSR enables scheduling that satisfies the PDB.

[0166] <6-2. Modifications> First to fifth modifications of the second embodiment of the present disclosure will be described. Note that two or more of these modifications may be combined.

[0167] (1) First Modification: Another Example of Delayed BSR Configuration Information In the above-described embodiment of the present disclosure, the delayed BSR configuration information is a flag. However, the delayed BSR configuration information according to the embodiment of the present disclosure is not limited to this example.

[0168] In a first modification of the present embodiment, the delayed BSR setting information may be information about the length of at least one modified second field. Specifically, the delayed BSR setting information is information indicating the length of the third field. The delayed BSR setting information according to this modification will be described in detail with reference to Figures 14 and 15.

[0169] For example, instead of the BSR-BufferSizeFieldLength shown in information 33 of Fig. 14, BSR-DelayInfoFieldLength as delayed BSR setting information is included as a parameter of LogicalChannelConfig. For example, BSR-DelayInfoFieldLength indicates the length of the Delay Info field, like BSR-BufferSizeFieldLength shown in table 43 of Fig. 15. For example, if BSR-DelayInfoFieldLength exists, it indicates that UE 200 is configured to report a delayed BSR and indicates the length of the Delay Info field in the delayed BSR. Conversely, if BSR-DelayInfoFieldLength does not exist, it indicates that UE 200 is not configured to report a delayed BSR, i.e., is configured to report a legacy BSR.

[0170] Furthermore, BSR-DelayInfoFieldLength may indicate information for indicating the length of the Delay Info field. For example, BSR-DelayInfoFieldLength indicates an index corresponding to the length of the Delay Info field (for example, the value or range of the length).

[0171] In this manner, according to the first modification of the present embodiment, the delayed BSR setting information may be information regarding the length of at least one modified second field. In addition, the delayed BSR setting information may indicate the length of the third field, thereby enabling the lengths of the third field and the modified second field to be dynamically changed.

[0172] In addition, as a first modification 2 of this embodiment, the delayed BSR configuration information may be information for identifying an LCG that uses the delayed BSR. Note that this modification is realized by replacing the BS extended BSR according to the first modification 2 of the first embodiment with the delayed BSR, and therefore a description thereof will be omitted.

[0173] In addition, as a first modification 3 of this embodiment, the delayed BSR configuration information may be information used to indicate the type of UL data. Note that this modification is realized by replacing the BS extended BSR according to the first modification 3 of the first embodiment with a delayed BSR, and therefore a description thereof will be omitted.

[0174] (2) Second Modification: Another Example of Configuration Information Including Delayed BSR Configuration Information In the above-described embodiment of the present disclosure, the delayed BSR configuration information is included in the configuration information of the logical channel. However, the delayed BSR configuration information according to the embodiment of the present disclosure is not limited to this example.

[0175] As a second modification 1 of this embodiment, the delayed BSR configuration information may be included in the configuration information of the LCG. Note that this modification is realized by replacing the BS extended BSR according to the second modification 1 of the first embodiment with the delayed BSR, and therefore a description thereof will be omitted.

[0176] In addition, as a second modification 2 of this embodiment, the delayed BSR configuration information may be included in the SR configuration information. Note that this modification is realized by replacing the BS extended BSR according to the second modification 2 of the first embodiment with the delayed BSR, and therefore a description thereof will be omitted.

[0177] In addition, as a second modification 3 of this embodiment, the delayed BSR configuration information may be included in the BSR configuration information. Note that this modification is realized by replacing the BS extended BSR according to the second modification 3 of the first embodiment with the delayed BSR, and therefore a description thereof will be omitted.

[0178] (3) Third Modification: Another Example of the Format of the Delayed BSR In the embodiment of the present disclosure described above, the delayed BSR includes the first field and a modified second field. However, the delayed BSR according to the embodiment of the present disclosure is not limited to this example.

[0179] In a third variation of this embodiment, the delayed BSR may further include at least one second field, where the at least one modified second field corresponds to an LCG among the plurality of LCGs that is identified based on the delayed BSR configuration information, and the at least one second field corresponds to an LCG among the plurality of LCGs other than the LCG identified based on the delayed BSR configuration information. In other words, a third field is added only to the second field corresponding to the LCG among the plurality of LCGs that is identified based on the delayed BSR configuration information, and only the second field is modified.

[0180] Specifically, the Delayed BSR includes multiple LCG fields, at least one pair of a Reduced Buffer Size field and a Delay Info field, and at least one Legacy Buffer Size field. The at least one pair of a Reduced Buffer Size field and a Delay Info field corresponds to an LCG among the multiple LCGs that is determined to use the Delayed BSR based on the Delayed BSR configuration information. The at least one Legacy Buffer Size field corresponds to an LCG other than the above LCG among the multiple LCGs.

[0181] This modification will be described in detail with reference to Fig. 21A. For example, assume that in format 23A of Fig. 21A, Buffer Size 1 corresponds to LCG0 and Buffer Size 3 (not shown) corresponds to LCG1. If it is determined that a Delayed BSR is to be used for LCG0, the Delayed BSR includes a set of a 6-bit Buffer Size 1 field and a 2-bit Delay Info 1 field as a set of reduced Buffer Size and Delay Info fields. If it is not determined that a Delayed BSR is to be used for LCG1, the Delayed BSR includes an 8-bit Buffer Size 3 field as a legacy Buffer Size field.

[0182] Alternatively, the Delayed BSR may include multiple LCG fields, at least one set of a Legacy Buffer Size field and a Delay Info field, and at least one Legacy Buffer Size field without a Delay Info field. The at least one set of a Legacy Buffer Size field and a Delay Info field corresponds to an LCG among the multiple LCGs that is determined to use the Delayed BSR based on the Delayed BSR configuration information. The at least one Legacy Buffer Size field without a Delay Info field corresponds to an LCG other than the LCG among the multiple LCGs.

[0183] This modification will be described in detail with reference to Figure 21B. For example, assume that in format 23B of Figure 21B, Buffer Size 1 corresponds to LCG0 and Buffer Size 3 (not shown) corresponds to LCG1. If it is determined that a Delayed BSR is to be used for LCG0, the Delayed BSR includes a set of an 8-bit Buffer Size 1 field and a 2-bit Delay Info 0 field as the set of legacy Buffer Size and Delay Info fields. On the other hand, if it is not determined that a Delayed BSR is to be used for LCG1, the Delayed BSR includes an 8-bit Buffer Size 3 field as the legacy Buffer Size field, and does not include Delay Info 1, unlike Figure 23B.

[0184] In this way, according to the third modification of the present embodiment, it is possible to change only the second field that requires the addition of delay information, thereby preventing the size of the BSR from increasing excessively, thereby reducing the waste of communication resources due to the BSR transmission.

[0185] (4) Fourth Modification: Another Example of the Field Indicating Delay Information In the above-described embodiment of the present disclosure, the modified second field includes the second field and the third field. However, the modified second field according to the embodiment of the present disclosure is not limited to this example.

[0186] As a fourth variation of this embodiment, the modified second field may be a single field that serves as both the second field and the third field. Specifically, the at least one modified second field is a field indicating information used to indicate the total amount of data of each logical channel of the corresponding at least one LCG and delay information of the corresponding at least one LCG.

[0187] The format of the Delayed BSR according to this modification will be described in detail with reference to Figure 24. Figure 24 shows an example of the MAC CE format of a Delayed BSR in which the Buffer Size field of a Legacy Long BSR has been modified. Note that the Delayed BSR according to this modification is not limited to a Legacy Long BSR, but may be a BSR in which the Buffer Size field of a Legacy BSR in another format has been modified.

[0188] For example, as shown in format 25 of Figure 24, a delayed BSR includes multiple LCG fields and at least one Buffer Size / Delay Info field. The LCGi field indicates the presence of a Buffer Size / Delay Info j field for LCGi. The Buffer Size / Delay Info field indicates an index corresponding to a set of buffer size and delay information. A table is defined that indicates the correspondence between the index and the set of buffer size and delay information. Note that the Buffer Size / Delay Info j fields are included in ascending order according to LCGi.

[0189] 24 shows an example in which the size of the Buffer Size / Delay Info field is the same as the size of the legacy Buffer Size field, but it may be larger or smaller than the size of the legacy Buffer Size field. For example, the size of the Buffer Size / Delay Info field may be 16 bits, 24 bits, or more.

[0190] In addition, as in a third modification of this embodiment, the delayed BSR may further include at least one second field. In other words, only the second field corresponding to the LCG identified based on the delayed BSR configuration information among the multiple LCGs is changed to a Buffer Size / Delay Info field.

[0191] According to the fourth modification of the present embodiment, at least one modified second field in the delayed BSR is a field indicating information used to indicate the total amount of data for each logical channel of the corresponding at least one LCG and the delay information for the corresponding at least one LCG. This allows the BSR to manage the buffer size and the delay information in a single field. This simplifies the BSR reception process (i.e., field analysis process).

[0192] (5) Fifth Modification: Compliance with Other TS In the above-described example of the embodiment of the present disclosure, the system 1 is a system that complies with 5G or NR TS. However, the system 1 according to the embodiment of the present disclosure is not limited to this example. The system 1 may be a system that complies with another TS, as in the fourth modification of the first embodiment.

[0193] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely examples and that various modifications are possible without departing from the scope and spirit of the present disclosure.

[0194] For example, the steps in the processes described herein do not necessarily have to be performed in chronological order according to the order depicted in the flowcharts or sequence diagrams. For example, the steps in the processes may be performed in an order different from that depicted in the flowcharts or sequence diagrams, or may be performed in parallel. Furthermore, some of the steps in the processes may be deleted, and additional steps may be added to the processes.

[0195] For example, a method including the operation of one or more components of the apparatus described herein may be provided, or a program for causing a computer to execute the operation of the components may be provided. Also, a non-transitory tangible computer-readable storage medium having the program recorded thereon may be provided. It should be understood that such methods, programs, and non-transitory tangible computer-readable storage media are also included in the present disclosure.

[0196] For example, one or more components of the base station described herein may be included in or provided as a module for the base station, i.e., a module for the base station may be provided that performs the processing for the base station described herein.

[0197] For example, one or more components of a user equipment (UE) described herein may be included in or provided as a module for the UE, i.e., a module for the UE may be provided that performs the UE processing described herein.

[0198] For example, in this disclosure, user equipment (UE) may be referred to by other names such as terminal apparatus, terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, radio station, radio terminal, radio device, radio unit, wireless station, wireless terminal, wireless device, wireless unit, access station, access terminal, access device, access unit, remote station, remote terminal, remote device, or remote unit.

[0199] For example, in the present disclosure, the UE may be a mobile phone terminal such as a smartphone, a tablet terminal, a personal computer, a mobile router, or a wearable device. Alternatively, the UE may be a device installed on a mobile object, or the mobile object itself. The mobile object may be a vehicle such as a car or train, an air vehicle such as an airplane or drone, or another mobile object such as a ship. Alternatively, in the present disclosure, the UE may be other Internet of Things (IoT) devices such as sensors and cameras. The UE may be mobile or fixed.

[0200] For example, in the present disclosure, "transmit" may mean performing processing at least one layer in a protocol stack used for transmission, or may mean physically transmitting a signal wirelessly or via a wire. Alternatively, "transmit" may mean a combination of performing processing at least one layer and physically transmitting a signal wirelessly or via a wire. Similarly, "receive" may mean performing processing at least one layer in a protocol stack used for reception, or may mean physically receiving a signal wirelessly or via a wire. Alternatively, "receive" may mean a combination of processing at least one layer and physically receiving a signal wirelessly or via a wire. The at least one layer may be rephrased as at least one protocol.

[0201] For example, in this disclosure, "obtain / acquire" may mean obtaining information from stored information, from information received from other nodes, or by generating the information.

[0202] For example, in this disclosure, "include" and "comprise" do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items.

[0203] For example, in this disclosure, "or" does not mean an exclusive or, but rather a logical or.

[0204] The technical features included in the above-described embodiments may be expressed as the following features: Naturally, the present disclosure is not limited to the following features.

[0205] (Feature 1) An apparatus (200) comprising: a communication processing unit (233) that receives a message including configuration information for determining whether to use a buffer status report including at least one first field and at least one changed second field; and an information acquisition unit (231) that acquires the configuration information included in the message, wherein the buffer status report is used to provide information about an uplink data amount, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one changed second field corresponding to the at least one logical channel group and related to the uplink data amount.

[0206] (Feature 2) The device according to Feature 1, wherein the setting information is included in setting information for a logical channel.

[0207] (Feature 3) The device according to Feature 1, wherein the setting information is included in setting information of a logical channel group.

[0208] (Feature 4) The device according to Feature 1, wherein the setting information is included in setting information of a scheduling request.

[0209] (Feature 5) The device according to Feature 1, wherein the setting information is included in setting information for a buffer status report.

[0210] (Feature 6) The device according to any one of Features 1 to 5, wherein the setting information is a flag.

[0211] (Feature 7) The device according to any one of Features 1 to 5, wherein the setting information is information about the length of the at least one changed second field.

[0212] (Feature 8) The device according to any one of Features 1 to 3, wherein the setting information is information for identifying a logical channel group that uses the buffer status report.

[0213] (Feature 9) The device according to any one of Features 1 to 5, wherein the setting information is information used to indicate a type of uplink data.

[0214] (Feature 10) The device described in any one of Features 1 to 9, wherein the buffer status report further includes at least one second field, wherein the at least one logical channel group is a plurality of logical channel groups, wherein the at least one modified second field corresponds to a logical channel group among the plurality of logical channel groups that is identified based on the configuration information, and wherein the at least one second field corresponds to a logical channel group among the plurality of logical channel groups other than the logical channel group that is identified based on the configuration information.

[0215] (Feature 11) The apparatus according to any one of Features 1 to 10, wherein the at least one modified second field is the second field whose size has been increased.

[0216] (Feature 12) The device according to Feature 11, wherein the at least one modified second field is a buffer size field indicating information used to indicate a total amount of data for each logical channel of the corresponding at least one logical channel group.

[0217] (Feature 13) The device according to any one of Features 1 to 10, wherein the at least one modified second field includes the second field and a third field different from the second field.

[0218] (Feature 14) The device described in Feature 13, wherein the second field is a buffer size field indicating information used to indicate a total amount of data for each logical channel of the corresponding at least one logical channel group, the third field is a field indicating information used to indicate delay information for the corresponding at least one logical channel group, and the delay information indicates information used to indicate a remaining time until an allowable delay of data belonging to the corresponding at least one logical channel group.

[0219] (Feature 15) The device described in any one of Features 1 to 10, wherein the at least one modified second field is a field indicating information used to indicate a total amount of data of each logical channel of the corresponding at least one logical channel group and delay information of the corresponding at least one logical channel group, and the delay information indicates information used to indicate a remaining time until an allowable delay of data belonging to the corresponding at least one logical channel group.

[0220] (Feature 16) The device according to any one of Features 1 to 15, wherein the device is a user device or a module for a user device.

[0221] (Feature 17) An apparatus (100) comprising: an information acquisition unit (141) that acquires configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; and a communication processing unit (143) that transmits a message including the configuration information, wherein the buffer status report is used to provide information about an amount of uplink data, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and related to the amount of uplink data.

[0222] (Feature 18) The device according to Feature 17, wherein the device is a base station or a module for a base station.

[0223] (Feature 19) A method performed by an apparatus (200), comprising: receiving a message including configuration information for determining whether to use a buffer status report, the buffer status report including at least one first field and at least one modified second field; and acquiring the configuration information included in the message, wherein the buffer status report is used to provide information about an amount of uplink data, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and related to the amount of uplink data.

[0224] (Feature 20) A method performed by an apparatus (100), comprising: obtaining configuration information for determining whether to use a buffer status report including at least one first field and at least one modified second field; and transmitting a message including the configuration information, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and related to the uplink data volume.

[0225] (Feature 21) A program causing a computer to execute the following steps: receive a message including configuration information for determining whether to use a buffer status report, the buffer status report including at least one first field and at least one modified second field; and obtain the configuration information included in the message, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group, and related to the uplink data volume.

[0226] (Feature 22) A program causing a computer to execute the following steps: obtaining configuration information for determining whether to use a buffer status report, the buffer status report including at least one first field and at least one modified second field; and transmitting a message including the configuration information, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group, and related to the uplink data volume.

[0227] (Feature 23) A non-transitive tangible recording medium having recorded thereon a program causing a computer to execute the following steps: receive a message including configuration information for determining whether to use a buffer status report, the message including at least one first field and at least one modified second field; and obtain the configuration information included in the message, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and related to the uplink data volume.

[0228] (Feature 24) A non-transitive tangible medium having recorded thereon a program causing a computer to execute the following steps: obtain configuration information for determining whether to use a buffer status report, the buffer status report including at least one first field and at least one modified second field; and transmit a message including the configuration information, wherein the buffer status report is used to provide information about an uplink data volume, the at least one first field indicating at least one logical channel group for which a buffer status is reported, and the at least one modified second field corresponding to the at least one logical channel group and related to the uplink data volume.

Claims

1. A method for receiving a Radio Resource Control (RRC) message from a base station device, the RRC message including delay information and including a Logical Channel Identifier (LCGID) for identifying a Logical Channel Group (LCG), the LCG ID being an identifier used for transmitting a Media Access Control (MAC) Control Element (MAC CE) identified by a MAC subheader including a Logical Channel Identifier (LCID); a communication processing unit configured to transmit, when the LCG ID is included in the RRC message, a MAC protocol data unit (MAC PDU) including the MAC subheader including the MAC CE for the LCG identified by the LCG ID and the LCID for identifying the MAC CE to the base station device; The MAC CE includes a first field, a second field, and a third field; The first field indicates that the second field and the third field are present for the LCG identified by the LCG ID, the second field is a buffer size field corresponding to the LCG identified by the LCG ID; The third field is a field indicating, as the delay information, the remaining time of data corresponding to the LCG identified by the LCG ID in milliseconds, and indicating the remaining time as a range. Communications equipment.

2. A processing unit for applying a logical channel prioritization procedure when transmitting the MAC CE, The processing unit includes: Prioritizing the MAC CE lower than a MAC CE for a Cell Radio Network Temporary Identifier (C-RNTI); Prioritizing said MAC CE higher than a MAC CE for a buffer status report included for padding. The communication device according to claim 1 .

3. The buffer size field indicates a total amount of data for each logical channel included in the LCG identified by the LCG ID.

3. A communication device according to claim 1 or 2.

4. transmitting a Radio Resource Control (RRC) message to a communication device (200) including delay information and including a LCG identifier (LCGID) for identifying a Logical Channel Group (LCG), the LCG identifier being an identifier used for transmitting a Media Access Control (MAC) Control Element (MAC CE) identified by a MAC subheader including a Logical Channel Identifier (LCID); a communication processing unit (143) for receiving, when the LCG ID is included in the RRC message, a MAC protocol data unit (MAC PDU) including the MAC subheader including the MAC CE for the LCG identified by the LCG ID and the LCID for identifying the MAC CE from the communication device; The MAC CE includes a first field, a second field, and a third field; The first field indicates that the second field and the third field are present for the LCG identified by the LCG ID, the second field is a buffer size field corresponding to the LCG identified by the LCG ID; The third field is a field indicating, as the delay information, the remaining time of data corresponding to the LCG identified by the LCG ID in milliseconds, and indicating the remaining time as a range. Base station equipment.

5. When the MAC CE is transmitted, a logical channel prioritization procedure is applied; The MAC CE is prioritized lower than a MAC CE for a Cell Radio Network Temporary Identifier (C-RNTI); The MAC CE is prioritized higher than the MAC CE for the buffer status report included for padding. The base station device according to claim 4.

6. The buffer size field indicates a total amount of data for each logical channel included in the LCG identified by the LCG ID. The base station device according to claim 4 or 5.

7. A method for receiving a Radio Resource Control (RRC) message from a base station device, the RRC message including delay information and including a Logical Channel Identifier (LCGID) for identifying a Logical Channel Group (LCG), the LCG ID being an identifier used for transmitting a Media Access Control (MAC) Control Element (MAC CE) identified by a MAC subheader including a Logical Channel Identifier (LCID); When the LCG ID is included in the RRC message, a MAC Protocol Data Unit (MAC PDU) including the MAC CE for the LCG identified by the LCG ID and the MAC subheader including the LCID for identifying the MAC CE is transmitted to the base station device; The MAC CE includes a first field, a second field, and a third field; The first field indicates that the second field and the third field are present for the LCG identified by the LCG ID, the second field is a buffer size field corresponding to the LCG identified by the LCG ID; The third field is a field indicating, as the delay information, the remaining time of data corresponding to the LCG identified by the LCG ID in milliseconds, and indicating the remaining time as a range. Method of communication device.

8. applying a logical channel prioritization procedure when transmitting the MAC CE; In the logical channel prioritization procedure, Prioritizing the MAC CE lower than a MAC CE for a Cell Radio Network Temporary Identifier (C-RNTI); Prioritizing said MAC CE higher than a MAC CE for a buffer status report included for padding. The method of claim 7.

9. The buffer size field indicates a total amount of data for each logical channel included in the LCG identified by the LCG ID.

9. The method according to claim 7 or 8.