Apparatus and method

Abstract

A device (200) according to one embodiment of the present disclosure is provided with: a communication processing unit (233) that receives a message including configuration information for determining whether or not 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, the buffer status report for providing information on the amount of uplink data, and the at least one first field indicating at least one logical channel group for which the buffer status is reported, the at least one altered second field corresponds to the at least one logical channel group and is related to an uplink data amount.

Description

[0001] Cross-references to related applications

[0002] This application is based on Japanese Patent Application No. 2022-127462 filed on August 9, 2022, and the contents thereof are cited herein. Technical Field

[0003] The present disclosure relates to apparatus and methods. Background Art

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

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

[0006] In addition, as described in non-patent document 1, the UE sends a buffer status report (buffer status report: BSR) for providing information about the amount of UL data to the base station. In the BSR, the range of the buffer size of the UL data is shown. Therefore, the base station can allocate communication resources corresponding to the range of the buffer size of the UL data shown in the BSR. In addition, the BSR indicates the range of the buffer size, so there is a quantization error. In addition, as described in non-patent document 2, the parameters of the SR and the parameters of the BSR are configured in the RRC (radio resource control) layer.

[0007] Furthermore, recently, 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, the data of the XR service has the characteristics of large capacity and high volatility. Therefore, the quantization error in the BSR leads to waste of communication resources and deterioration of scheduling efficiency. As a countermeasure, for example, in non-patent document 3, it is proposed to determine the accurate cache size through BSR. In addition, the XR service may have a delay requirement (for example, packet delay Budget: PDB). As a countermeasure, for example, in non-patent document 4, it is proposed to include delay information in the BSR and perform scheduling that takes delay into account to satisfy the PDB.

[0008] Non-patent literature

[0009] Non-patent document 1: 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)"

[0010] Non-patent document 2: 3GPP TS 38.331 V17.1.0 (2022-06), "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 17)"

[0011] Non-patent document 3: 3GPP TSG RAN WG1#109-e, e-Meeting, May 9th-20th, 2022, R1-2203607, “Discussion on XR specific capacity enhancements techniques”

[0012] Non-patent document 4: 3GPP TSG-RAN WG1 Meeting #109-e, Online, May 9th-20th, 2022, R1-2203639, “Discussion on capacity enhancements for XR”

[0013] Non-patent document 5: 3GPP TSG RAN WG1#109-e, e-Meeting, May 9th-20th, 2022, R1-2203928, “Considerations on XR Capacity Improvements” Summary of the invention

[0014] The inventors conducted detailed research and found the following problem: That is, in non-patent literature, although the concept of scheduling UL data using BSR is proposed, no specific method is proposed.

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

[0016] The device (200) involved in one embodiment of the present disclosure includes: a communication processing unit (233) receiving a message containing configuration information, wherein the configuration information is used to determine whether to use a cache status report containing at least one first field and at least one changed second field; and an information acquisition unit (231) acquiring the configuration information contained in the message, wherein the cache status report is used to provide information about the amount of uplink data, wherein the at least one first field indicates at least one logical channel group whose cache status is reported, and the at least one changed second field corresponds to the at least one logical channel group and is related to the amount of uplink data.

[0017] The device (100) involved in one embodiment of the present invention includes: an information acquisition unit (141) for acquiring configuration information, wherein the configuration information is used to determine whether to use a cache status report including at least one first field and at least one changed second field; and a communication processing unit (143) for sending a message including the configuration information, wherein the cache status report is used to provide information about the amount of uplink data, wherein the at least one first field indicates at least one logical channel group whose cache status is reported, and the at least one changed second field corresponds to the at least one logical channel group and is related to the amount of uplink data.

[0018] A method performed by a device (200) according to one embodiment of the present disclosure includes: receiving a message containing configuration information, the configuration information being used to determine whether to use a cache status report containing at least one first field and at least one changed second field; and obtaining the configuration information contained in the message, the cache status report being used to provide information about the amount of uplink data, the at least one first field indicating at least one logical channel group for which the cache status is reported, the at least one changed second field corresponding to the at least one logical channel group and being related to the amount of uplink data.

[0019] A method performed by a device (100) according to one embodiment of the present disclosure includes: obtaining configuration information, the configuration information being used to determine whether to use a cache status report comprising at least one first field and at least one changed second field; and sending a message comprising the configuration information, the cache status report being used to provide information about the amount of uplink data, the at least one first field indicating at least one logical channel group for which the cache status is reported, the at least one changed second field corresponding to the at least one logical channel group and being related to the amount of uplink data.

[0020] According to the present disclosure, the efficiency of scheduling UL data using BSR can be improved. In addition, according to the present disclosure, other effects can be exerted in place of or together with this effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is an explanatory diagram showing an example of UL data transmission.

[0022] Figure 2 is a diagram showing a short BSR.

[0023] Figure 3 is a diagram showing a table of cache sizes.

[0024] Figure 4 is a diagram showing a long BSR.

[0025] Figure 5 It is an explanatory diagram showing an example of a schematic configuration of a system according to an embodiment of the present disclosure.

[0026] Figure 6 This is a block diagram showing an example of a schematic functional structure of a base station involved in an embodiment of the present disclosure.

[0027] Figure 7 This is a block diagram showing an example of a schematic hardware configuration of a base station according to an embodiment of the present disclosure.

[0028] Figure 8 This is a block diagram showing an example of a schematic functional structure of a user equipment involved in an embodiment of the present disclosure.

[0029] Fig. 9 This is a block diagram showing an example of a schematic hardware configuration of a user equipment according to an embodiment of the present disclosure.

[0030] Fig.10 This is a diagram showing an example of the BSR according to the first embodiment of the present disclosure.

[0031] Fig.11 It is a diagram showing an example of configuration information for determining whether to use the BSR according to the first embodiment of the present disclosure.

[0032] Fig.12 It is a diagram for explaining an example of the above-mentioned configuration information involved in the first embodiment of the present disclosure.

[0033] Fig.13 This is a sequence diagram for explaining an example of a schematic flow of processing according to the first embodiment of the present disclosure.

[0034] Fig.14 It is a diagram showing an example of the above-mentioned configuration information according to the first modification example 1 of the first embodiment of the present disclosure.

[0035] Fig.15 This is a diagram for explaining an example of the above-mentioned configuration information according to the first modification example 1 of the first embodiment of the present disclosure.

[0036] Fig.16 It is a diagram showing an example of the above-mentioned configuration information according to the first modification example 2 of the first embodiment of the present disclosure.

[0037] Fig.17 This is a diagram for explaining an example of the above-mentioned configuration information according to the first modification example 2 of the first embodiment of the present disclosure.

[0038] Fig.18 It is a diagram showing an example of the above-mentioned configuration information according to the first modification example 3 of the first embodiment of the present disclosure.

[0039] Fig.19 This is a diagram for explaining an example of the above-mentioned configuration information according to the first modification example 3 of the first embodiment of the present disclosure.

[0040] Fig. 20 It is a diagram showing an example of the configuration information including the above-mentioned configuration information according to the second modification example of the first embodiment of the present disclosure.

[0041] Fig.21AThis is a diagram showing an example of a BSR according to the second embodiment of the present disclosure.

[0042] Fig. 21B This is a diagram showing another example of the BSR according to the second embodiment of the present disclosure.

[0043] Fig. 22 It is a diagram showing an example of configuration information for determining whether to use the BSR according to the second embodiment of the present disclosure.

[0044] Fig.23 It is a diagram for explaining an example of the above-mentioned configuration information according to the second embodiment of the present disclosure.

[0045] Fig.24 This is a diagram showing an example of a BSR according to a fourth modification example of the second embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, in the present specification and the accompanying drawings, for elements that can be described in the same manner, repeated descriptions may be omitted by attaching the same reference numerals.

[0047] The description is made in the following order.

[0048] 1. Related technologies

[0049] 2. System structure

[0050] 3. Structure of base station

[0051] 4. Structure of User Equipment

[0052] 5. First Implementation

[0053] 5-1. Action example

[0054] 5-2. Modification

[0055] 6. Second Implementation

[0056] 6-1. Action example

[0057] 6-2. Modification

[0058] <1. Related technologies>

[0059] As technologies related to the embodiments of the present disclosure, a scheduling request (SR) and a buffer status report (BSR) will be described.

[0060] (1) Scheduling Request (SR)

[0061] SR is used for UE to request the base station for allocation of communication resources for new UL transmission. For example, SR can be used to request resources for the uplink shared channel (UL-SCH) for initial transmission. Here, UL-SCH can be mapped to the physical uplink shared channel (PUSCH). In this embodiment, the data of UL-SCH is also recorded as UL data. A set of multiple BWPs (bandwidth part) and / or physical uplink control channel (PUCCH) resources throughout the cell are allocated as communication resources for SR. For each logical channel, a maximum of one PUCCH resource is allocated to each BWP for SR. For example, in each of one or more cells (also called service cells), one or more downlink BWPs and / or one or more uplink BWPs can be configured. For example, a set of PUCCH resources can be configured for one or more uplink BWPs respectively.

[0062] Reference Figure 1 , an example of UL transmission using SR is described. If UL data arrives, the UE triggers SR. Use PUCCH to send SR to the base station. The base station that receives the SR allocates resources for UL data transmission to the UE. Use the physical downlink control channel (physical downlink control channel: PDCCH) to send UL resource allocation to the UE. The UE that receives the UL resource allocation uses the allocated PUSCH resources to send UL data to the base station. The BSR can also be sent together with the UL data. In this embodiment, the UL resource allocation includes the allocation of UL-SCH and / or the allocation of PUSCH resources. In addition, the allocation of PUSCH resources includes the resource allocation in the frequency domain of PUSCH (frequency domain resource assignment) and / or the resource allocation in the time domain of PUSCH (time domain resource assignment). For example, the base station can send the downlink control information (downlink control information: DCI) used for scheduling of PUSCH through PDCCH. That is, the DCI may include information (one or more fields) for allocating resources for PUSCH.

[0063] The parameters of SR are configured using SchedulingRequestConfig and / or SchedulingRequestResourceConfig which are RRC configuration information. For example, SR parameters are parameters used in the transmission of SR and / or the configuration of SR resources, also known as SR configuration. The parameters of SR include SchedulingRequestConfig and / or SchedulingRequestResourceConfig. In addition, the parameters of SR may also include schedulingRequestID, sr-ProhibitTimer, sr-TransMax, periodicityAndOffset, phy-PriorityIndex and / or resource, etc. Each SR configuration corresponds to one or more logical channels. For example, each SR configuration corresponds to one or more logical channels (and / or BFR (beam failure recovery)) via schedulingRequestID. SchedulingRequestID can be used to identify SR instances at the MAC layer. sr-ProhibitTimer can be used to configure the timer for SR transmission in PUCCH. sr-TransMax can be used to configure the maximum number of SR transmissions. periodicityAndOffset can be used to configure the period and offset of the SR. phy-PriorityIndex can be used to configure the priority of the SR resources in the priority assignment or multiplexing of the PHY layer. The parameter "resource" can be used to configure the ID (identifier) ​​of the PUCCH resource used for the transmission of the SR. For example, for the transmission of the SR based on the parameters of the SR, the PUCCH resources corresponding to the ID of the PUCCH resources included in the parameters of the SR can be configured. The PUCCH resources can be configured by PUCCH format 0 or PUCCH format 1 containing information for configuring the resources of the PUCCH.

[0064] Here, the RRC configuration information may include information sent and / or received in the RRC layer between the base station and the UE. That is, the base station may send an RRC message including the SR configuration to the UE. In addition, the UE may receive an RRC message including the SR configuration, and perform SR transmission based on the SR configuration. In addition, the UE may receive an RRC message including the SR configuration, and determine the PUCCH resources used for SR transmission based on the SR configuration. For example, the RRC message may include an RRC reconfiguration message.

[0065] (2) Buffer Status Report (BSR)

[0066] The BSR process (also called buffer status report) is used to provide information related to the UL data volume (capacity) in the UE to the base station. That is, the BSR is used in the process (buffer status report) for providing information related to the UL data volume of the MAC entity to the base station. The BSR is sent using a MAC CE (Control Element). That is, actions related to the BSR can be performed and / or processed in the MAC layer (e.g., MAC entity) in the UE. In addition, actions related to the BSR can be performed and / or processed in the MAC layer (e.g., MAC entity) in the base station. In this embodiment, the high layer includes a layer higher than the MAC layer. For example, the high layer may include an RRC layer.

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

[0068] The BSR is reported for each logical channel group (LCG). Each logical channel is allocated to any LCG by a logicalChannelGroup indicating the ID of the LCG.

[0069] For the activated cell group, if any of the following situations occurs, the BSR can be triggered. In addition, according to the following triggering mechanism, the BSR is classified into regular BSR corresponding to (A) and (C), periodic BSR corresponding to (D), and padding BSR corresponding to (B).

[0070] (A) UL data of logical channels belonging to any LCG becomes available to the MAC entity.

[0071] (B) UL resources are allocated, and the number of padding bits of the UL resources is greater than or equal to the size of the BSR MAC CE.

[0072] (C) The indication period of retxBSR-Timer expires, and at least one of the logical channels belonging to any LCG contains UL data.

[0073] (D) The period indicated by the periodicBSR-Timer expires.

[0074] Next, the BSR MAC CE is explained. The BSR MAC CE may correspond to the MAC CE used for the transmission of the above-mentioned BSR. For example, the format of the BSR MAC CE (hereinafter, also referred to as the BSR format) is specified as several types (for example, short BSR, long BSR), which are identified by a MAC subheader containing LCID / eLCID. That is, LCID (Logical Channel Identifier, logical channel identifier) / eLCID (extended LCID, extended logical channel identifier) ​​can be used to identify the type of the corresponding MAC CE. In addition, respective LCID / eLCIDs for the downlink shared channel (Downlink-Shared Channel: DL-SCH) and / or UL-SCH may be specified. Below, LCID / eLCID represents LCID and / or eLCID.

[0075] Reference Figure 2 and Figure 3 , the format 20A of the short BSR is described. The size of the short BSR is fixed. Figure 2As shown in FIG. 1 , the short BSR has an LCG ID field and a buffer size field. The LCG ID field is used to identify the LCG ID that reports the buffer size. The size of the LCG ID field is 3 bits. The buffer size field is used to identify 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 the Figure 3 The index corresponding to the cache size in Table T1 for the 5-bit cache size field is shown.

[0076] Reference Figure 4 , the format of the long BSR 20B is described. The size of the long BSR is variable. Figure 4 As shown, the long BSR has an LCGi field and a cache size j field. LCGi is the LCG holding the i-th ID, and the LCGi field indicates the existence of the cache size field for LCGi. The LCGi field is set to 1 when the cache size is reported, and is set to 0 otherwise. Alternatively, the LCGi field may also indicate whether the LCGi has available data. The cache size j field is used to identify the total amount of data available for all logical channels belonging to the corresponding LCGi. The size of the cache size j field is 8 bits. The cache size j field indicates an index corresponding to the cache size in a table regarding the 8-bit cache size field not shown in the figure. In addition, the cache size j field is included in ascending order corresponding to the LCGi.

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

[0078] For example, in the case of a regular BSR and a periodic BSR, when there are two or more LCGs with available data when encapsulating a MAC PDU containing a BSR, a long BSR is reported, and in other cases, a short BSR is reported. Furthermore, for a MAC entity configured with logicalChannelGroup-IABExt by a higher layer, an extended long BSR or an extended short BSR can be reported.

[0079] In addition, for example, in the case of a padding BSR, in addition to the above-mentioned BSR format, a short truncated BSR, a long truncated BSR, an extended short truncated BSR, and an extended long truncated BSR are further reported according to conditions.

[0080] In addition, for example, preemptive BSR and extended preemptive BSR are used by IAB-MT (Mobile Termination).

[0081] <2. System structure>

[0082] Reference Figure 5 , an example of the structure of the system 1 involved in the embodiment of the present disclosure is described. Figure 5 , system 1 includes a base station 100 and a UE 200.

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

[0084] (1) Base station 100

[0085] The base station 100 is a node of a radio access network (RAN) and communicates with UEs (eg, UE 200 ) located within a coverage area 10 of the base station 100 .

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

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

[0088] The base station 100 may include a plurality of nodes. The plurality of nodes may include a first node that uses the higher layer included in the above-mentioned protocol stack as a host, and a second node that uses the lower layer included in the protocol stack as a host. The above-mentioned higher layer may include RRC, SDAP and PDCP, and the above-mentioned lower layer may include RLC, MAC and PHY layer. The above-mentioned first node may be a CU (central unit), and the above-mentioned second node may be a DU (distributed unit). In addition, the above-mentioned plurality of nodes may include a third node that performs lower-level processing of the PHY layer, and the above-mentioned second node may perform upper-level processing of the PHY layer. The third node may be a RU (radio unit).

[0089] Alternatively, the base station 100 may be one of the multiple nodes mentioned above, and may also be connected to other units among the multiple nodes mentioned above.

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

[0091] (2)UE 200

[0092] UE 200 communicates with the base station. For example, when UE 200 is located in the coverage area 10 of the base station 100, UE 200 communicates with the base station 100.

[0093] For example, UE 200 communicates with a base station (eg, base station 100) using the above-mentioned protocol stack.

[0094] In addition, the UE 200 sends the SR and BSR as described in <1. Related Art> to the base station. In addition, the UE 200 may be a device supporting an XR service (in other words, an XR scenario).

[0095] <3. Structure of base station>

[0096] Reference Figure 6 and Figure 7 , an example of the structure of the base station 100 involved in the embodiment of the present disclosure is described.

[0097] (1) Functional structure

[0098] First, refer to Figure 6 , an example of the functional configuration of the base station 100 according to the embodiment of the present disclosure is described. Figure 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 .

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

[0100] The network communication unit 120 receives signals from the network and sends signals to the network.

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

[0102] 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. In addition, the processing unit 140 may further include other components other than these components. That is, the processing unit 140 may also perform operations other than the operations 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.

[0103] For example, the processing unit 140 (first communication processing unit 143) communicates with the UE (e.g., UE 200) via the wireless communication unit 110. For example, the processing unit 140 (second communication processing unit 145) communicates with other nodes (e.g., network nodes or other base stations in the core network) via the network communication unit 120.

[0104] (2) Hardware structure

[0105] Next, refer to Figure 7 , an example of the hardware configuration of the base station 100 involved in the embodiment of the present disclosure is described. Figure 7 The base station 100 has an antenna 181, an RF (radio frequency) circuit 183, a network interface 185, a processor 187, a memory 189 and a storage device 191.

[0106] Antenna 181 converts the signal into radio waves and radiates the radio waves into space. In addition, antenna 181 receives radio waves in space and converts the radio waves into signals. Antenna 181 may include a transmitting antenna and a receiving antenna, or may be a single antenna for transmitting and receiving. Antenna 181 may be a directional antenna or may include multiple antenna elements.

[0107] The RF circuit 183 performs analog processing on the signal transmitted or 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.

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

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

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

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

[0112] 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 storage unit 130 may be implemented by a storage device 191. The processing unit 140 may be implemented by a processor 187 and a memory 189.

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

[0114] Considering the above hardware structure, the base station 100 may include a memory storing a program (i.e., the memory 189) and one or more processors (i.e., the processor 187) capable of executing the program, and the one or more processors may execute the program to perform the operation of the processing unit 140. The program may be a program for causing the processor to perform the operation of the processing unit 140.

[0115] <4. Structure of user equipment>

[0116] Reference Figure 8 and Fig. 9 , an example of the structure of UE 200 involved in an embodiment of the present disclosure is described.

[0117] (1) Functional structure

[0118] First, refer to Figure 8 , an example of the functional structure of UE 200 involved in the embodiment of the present disclosure is described. Figure 8 UE 200 has a wireless communication unit 210, a storage unit 220 and a processing unit 230.

[0119] The wireless communication unit 210 transmits and receives signals wirelessly. For example, the wireless communication unit 210 receives signals from a base station and transmits signals to a base station. For example, the wireless communication unit 210 receives signals from other UEs and transmits signals to other UEs.

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

[0121] 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. In addition, the processing unit 230 may further include other components other than these components. That is, the processing unit 230 may perform operations other than the operations of these components. The specific operations of the information acquisition unit 231 and the communication processing unit 233 will be described in detail later.

[0122] 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 .

[0123] (2) Hardware structure

[0124] Next, refer to Fig. 9 , an example of the hardware structure of the UE 200 involved in the embodiment of the present disclosure is described. Fig. 9 UE 200 has an antenna 281, an RF circuit 283, a processor 285, a memory 287 and a storage device 289.

[0125] Antenna 281 converts the signal into radio waves and radiates the radio waves into space. In addition, antenna 281 receives radio waves in space and converts the radio waves into signals. Antenna 281 may include a transmitting antenna and a receiving antenna, or may be a single antenna for transmitting and receiving. Antenna 281 may be a directional antenna or may include multiple antenna elements.

[0126] The RF circuit 283 performs analog processing on the signal transmitted or 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.

[0127] The processor 285 performs digital processing of signals sent and received via the antenna 281 and the RF circuit 283. The digital processing includes processing of the protocol stack of the RAN. The processor 285 may include multiple processors, or may be a single processor. The multiple processors may include a baseband processor that performs the above-mentioned digital processing and one or more processors that perform other processing.

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

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

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

[0131] The processing unit 230 may be implemented by a SoC (System on Chip) 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.

[0132] Considering the above hardware structure, the UE 200 may have a memory storing a program (i.e., the memory 287), and one or more processors capable of executing the program (i.e., the processor 285), and the one or more processors may execute the above program to perform the operation of the processing unit 230. The above program may be a program for causing the processor to perform the operation of the processing unit 230.

[0133] <5. First embodiment>

[0134] In an embodiment of the present disclosure, configuration information for determining whether to use a BSR (hereinafter, also referred to as an enhanced BSR (enhanced BSR)) is sent from a base station to a UE, wherein the BSR includes a first field and a changed second field. In a first embodiment of the present disclosure, configuration information for determining whether to use an enhanced BSR (hereinafter, also referred to as a BS (buffer size) extended BSR) is sent from a base station 100 to a UE 200, wherein the enhanced BSR includes an extended buffer size field as the changed second field.

[0135] <5-1. Operation example>

[0136] Reference Figure 10 to Figure 13 , an example of the operation of the base station 100 and the UE 200 involved in the first embodiment of the present disclosure is described.

[0137] (1) Format of BS Extended BSR

[0138] The BS extended BSR involved in this embodiment includes a first field and a changed second field, and the first field can indicate the logical channel group (LCG) for which the cache status is reported. In addition, the second field corresponds to the logical channel group and is related to the amount of uplink data. In addition, the changed second field can be a field in which the size of the second field is increased (hereinafter, also referred to as the extended second field). In other words, the size of the extended second field can be larger than the size of the second field before the extension (that is, it can be longer in data length or more in number of bits). For example, UE 200 can calculate the amount of data (capacity) and determine the amount of uplink data that can be used for the logical channel. In addition, as described below, UE 200 can determine the level of cache size based on the amount of uplink data, and set an index corresponding to the determined level of cache size to the second field.

[0139] Specifically, the extended second field is a cache size field representing information (hereinafter, also referred to as an extended cache size field), which is used to indicate the total amount of data of the logical channel of the corresponding logical channel group. The extended cache size field of the BS extended BSR is longer than the cache size field of the traditional BSR (hereinafter, also referred to as the traditional cache size field). The traditional BSR is a BSR based on the change of the enhanced BSR. For example, the traditional BSR may be a BSR classified as the conventional BSR, periodic BSR, or padding BSR mentioned above. That is, the traditional 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 preemptive BSR, or an extended preemptive BSR. In addition, for example, the code points (or, indexes) corresponding to each of the traditional BSRs may be specified as the values ​​of the LCID / eLCID relative to the UL-SCH. That is, as the value of LCID / eLCID with respect to UL-SCH, code points (or, indexes) 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, preemptive BSR and / or extended preemptive BSR may be specified. For example, UE 200 may send any of the conventional BSRs identified by the value of LCID / eLCID based on the configuration and / or conditions from base station 100.

[0140] Reference Fig.10 , the format of the BS extended BSR involved in this embodiment is described in detail. Fig.10 An example of the MAC CE format of the BS extended BSR in which the buffer size field of the conventional long BSR is extended is shown. In addition, the BS extended BSR is not limited to the conventional long BSR, and may be a BSR in which the buffer size field of the conventional BSR of another format is extended.

[0141] For example, the BS extends the BSR as Fig.10 As shown in the format 21 of FIG. 21, the first field includes the LCGi field, and the second field includes the extended cache size j field as an extension. The LCGi field indicates the existence of the extended cache size j field for LCGi.

[0142] The extended cache size j field is used to identify the total amount of data available for all logical channels belonging to the corresponding LCGi. The size of an extended cache size j field is, for example, 16 bits (or, 8 bits), which is 8 bits (or, 5 bits) longer than the size of the traditional cache size j field. The traditional cache size j field is a cache size field that is the basis for the change of the extended cache size j field. In addition, the size of the extended cache size j field is not limited thereto, and can be any other size (for example, 24 bits, etc.) that is longer than the traditional cache size j field. In addition, the size of the extended cache size j field may vary according to the corresponding LCGi. Here, 8 bits are also referred to as an eight-bit byte. That is, 16 bits are also referred to as two eight-bit bytes.

[0143] The extended cache size j field indicates, for example, an index corresponding to a cache size (e.g., a cache size level, a cache size value, or a cache size range) in a table of 16-bit cache size fields (not shown). In addition, the extended cache size j field is included in ascending order corresponding to LCGi (e.g., corresponding to the value of i of LCGi).

[0144] The BS extended BSR is different from other formats of BSR. For example, an LCID / eLCID indicating the BS extended BSR is defined. For example, as the value of the LCID / eLCID relative to the UL-SCH, a corresponding code point (or, index) can be specified for the BS extended BSR. As a result, the BS extended BSR becomes able to be sent as a MAC CE. In addition, the MAC CE of the BS extended BSR can be included in a MAC PDU (protocol data unit) and sent. For example, it may be that the MAC PDU includes one or more MAC sub-PDUs, each MAC sub-PDU includes a MAC sub-header and a MAC CE. Here, the MAC sub-header may include LCID / eLCID. That is, the MAC sub-header including the LCID / eLCID indicating the BS extended BSR and the MAC CE of the BS extended BSR are included in the MAC sub-PDU, and the MAC PDU including the MAC sub-PDU is sent.

[0145] (2) BS Extended BSR Configuration Information

[0146] The configuration information for determining whether to use the BS extended BSR involved in this embodiment (hereinafter, also referred to as BS extended BSR configuration information) is defined. The BS extended BSR configuration information is included in the configuration information of the logical channel. Thus, the BS extended BSR is configured for each logical channel. Fig.11 and Fig.12 , the BS extended BSR configuration information is described in detail.

[0147] Specifically, the BS extended BSR configuration information is included in the LogicalChannelConfig. That is, the configuration information of the above-mentioned logical channel may correspond to the LogicalChannelConfig. For example, the LogicalChannelConfig may be used to configure the parameters of the logical channel. In addition, the LogicalChannelConfig may include parameters related to the above-mentioned BSR. For example, one or more parameters contained in the LogicalChannelConfig may be used to identify a logical channel. For example, the LogicalChannelConfig may include a parameter (logicalChannelGroup) indicating the index of the 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 send a LogicalChannelConfig containing one or more parameters relative to the one logical channel to the UE 200. Here, the base station 200 may send an RRC message containing the LogicalChannelConfig to the UE 200. In addition, the UE 200 may identify the one logical channel based on one or more parameters contained in the LogicalChannelConfig. For example, UE 200 may identify the logical channel group to which the one logical channel belongs based on the parameter indicating the index of the logical channel group included in LogicalChannelConfig. Here, as described above, UE 200 may send a BSR for the logical channel group to which one or more logical channels belong. As a specific example, Fig.11 As shown in information 31, BSR-BSExtApplied as BS extended BSR configuration information may be included as a parameter of LogicalChannelConfig.

[0148] In addition, the BS extended BSR configuration information is a flag. Fig.12As shown in Table 41, BSR-BSExtApplied, when present, indicates that UE 200 is configured to report BS extended BSR. Conversely, the absence of BSR-BSExtApplied indicates that UE 200 is not configured to report BS extended BSR, that is, it indicates that it is configured to report traditional BSR. In addition, BS extended BSR configuration information is not limited to a flag that indicates whether to use BS extended BSR by its presence, but may also be a flag that indicates whether to use BS extended BSR by its value. For example, the BS extended BSR configuration information indicates the use of traditional BSR when the value is 0, and indicates the use of BS extended BSR when the value is 1. Here, the presence of BSR-BSExtApplied may refer to the situation corresponding to the presence of BSR-BSExtApplied in LogicalChannelConfig. That is, the presence of BSR-BSExtApplied may refer to the situation corresponding to the inclusion of BSR-BSExtApplied in LogicalChannelConfig. In addition, the case where BSR-BSExtApplied does not exist may refer to the case where BSR-BSExtApplied does not exist in LogicalChannelConfig. That is, the case where BSR-BSExtApplied does not exist may refer to the case where BSR-BSExtApplied is not included in LogicalChannelConfig. Below, the case where BSR-BSExtApplied exists or the case where BSR-BSExtApplied does not exist is mainly recorded, but the case where BSR-BSExtApplied exists can be replaced with the case where the value of BS extended BSR configuration information is 1. In addition, the case where BSR-BSExtApplied does not exist can be replaced with the case where the value of BS extended BSR configuration information is 0. In addition, the case where BSR-BSExtApplied exists is also recorded as the case where BSR-BSExtApplied is configured. In addition, the case where BSR-BSExtApplied does not exist is also recorded as the case where BSR-BSExtApplied is not configured.

[0149] (3) Messages containing configuration information

[0150] The configuration information for determining whether to use the BS extended BSR according to the present embodiment is included in a message and transmitted. The message may be an RRC message.

[0151] For example, the BS extended BSR configuration information is sent via an RRC message including a LogicalChannelConfig. The RRC message may be, for example, RRCReconfiguration, RRCResume, or RRCSetup. In addition, an RRC message different from the above-mentioned RRC message may be used. Here, the base station 100 may send a LogicalChannelConfig including the BS extended BSR configuration information to the UE 200. For example, the base station 100 may send an RRC message including the LogicalChannelConfig to the UE 200. In addition, the UE 200 may determine an action related to the BSR based on the BS extended BSR configuration information. For example, the UE 200 may identify the logical channel group to which the logical channel belongs based on the BS extended BSR configuration information, and send a BSR for the logical channel group.

[0152] (4) Actions of UE 200 Based on Configuration Information

[0153] 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 the received message containing the configuration information. The UE 200 determines the BSR to be used based on the acquired configuration information.

[0154] Specifically, the UE 200 determines whether to use the BS extended BSR based on the BS extended BSR configuration information obtained from the received RRC message. For example, the 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. The UE 200 uses the BS extended BSR when reporting the cache status for the LCG to which the logical channel determined to use the BS extended BSR belongs.

[0155] For example, the LogicalChannelConfig included in the received RRC message contains Fig.11 In the case of BSR-BSExtApplied as shown, UE 200 uses the BS extended BSR as the BSR for the LCG including the logical channel configured with the LogicalChannelConfig.

[0156] (5) Processing flow

[0157] Reference Fig.13 , an example of the processing involved in this embodiment is described.

[0158] The base station 100 sets the configuration information for determining whether to use the enhanced BSR (ie, in this embodiment, the BS extended BSR configuration information) to the RRC message (step S310). Fig.11 As shown in the BSR-BSExtApplied, set BSR-BSExtApplied to LogicalChannelConfig.

[0159] Base station 100 sends an RRC message including BS extended BSR configuration information to UE 200 (step S320). For example, base station 100 sends an RRC message (eg, RRCReconfiguration, RRCResume, or RRCSetup) including LogicalChannelConfig with BSR-BSExtApplied set to UE 200.

[0160] If UE 200 receives an RRC message including BS extended BSR configuration information, an RRC message as a response to the RRC message is sent to base station 100 (step S330). For example, if UE 200 receives an RRC message including LogicalChannelConfig set to BSR-BSExtApplied, an RRC message (e.g., RRCReconfigurationComplete, RRCResumeComplete, or RRCSetupComplete) as a response is sent to base station 100.

[0161] UE 200 determines the use of enhanced BSR based on the received configuration information (step S340). For example, if the BSR is triggered, UE 200 uses the BS extended BSR when BSR-BSExtApplied is included in the LogicalChannelConfig of any logical channel belonging to the LCG that reports the cache status through the BSR. In other cases, UE 200 uses the traditional BSR, that is, the BSR in which the cache size field is not extended. That is, UE 200 can report the BS extended BSR (that is, enhanced BSR MAC CE) based on the configuration of BSR-BSExtApplied for at least one of the logical channels belonging to the LCG for the reported BSR. In addition, UE 200 can report the traditional BSR based on the fact that BSR-BSExtApplied is not configured for any of the logical channels belonging to the LCG for the reported BSR. That is, UE 200 can determine whether to report BS extended 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). In addition, UE 200 can determine whether to send BS extended BSR (e.g., enhanced BSR MAC CE) based on whether LogicalChannelConfig includes BSR-BSExtApplied.

[0162] Here, the format of the BS extended BSR can be used for a regular BSR, a periodic BSR and / or a padding BSR. For example, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 can report the BS extended BSR based on whether BSR-BSExtApplied is configured. For example, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 can report the BS extended BSR based on the following situation, which means that BSR-BSExtApplied is configured, and there are more than two LCGs with available data when encapsulating the MAC PDU containing the BSR. In addition, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 can report the BS extended BSR based on the following situation, which means that BSR-BSExtApplied is configured, and there are more than one LCGs with available data when encapsulating the MAC PDU containing the BSR. In addition, for a normal BSR, a periodic BSR, and / or a padding BSR, the UE 200 may report a BS extended BSR based on the following situation, which means that BSR-BSExtApplied is configured, there are more than two (or, more than one) LCGs with available data when encapsulating a MAC PDU containing a BSR, and the ID of the largest LCG among the configured LCGs is greater than 7. In addition, for a normal BSR, a periodic BSR, and / or a padding BSR, the UE 200 may report a BS extended BSR based on the following situation, which means that BSR-BSExtApplied is configured, there are more than two (or, more than one) LCGs with available data when encapsulating a MAC PDU containing a BSR, and the ID of the largest LCG among the configured LCGs is greater than 256. Here, the UE 200 may report the BS extended BSR for all LCGs that have data available for transmission.

[0163] In addition, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 may report a traditional BSR based on the fact that BSR-BSExtApplied is not configured. In addition, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 may report a traditional BSR based on the fact that BSR-BSExtApplied is configured and there is one LCG with available data when encapsulating a MAC PDU containing a BSR. In addition, for a regular BSR, a periodic BSR and / or a padding BSR, the UE 200 may report a traditional BSR based on the fact that BSR-BSExtApplied is configured and there are two or more LCGs with available data when encapsulating a MAC PDU containing a BSR, and the ID of the largest LCG among the configured LCGs is 7 or less. In addition, for a regular BSR, a periodic BSR, and / or a padding BSR, the UE 200 may report a legacy BSR based on the following situation: BSR-BSExtApplied is configured, there are two or more LCGs with available data when encapsulating a MAC PDU containing a BSR, and the ID of the largest LCG among the configured LCGs is 256 or less. Here, the UE 200 may report a legacy BSR 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 preemptive BSR, or an extended preemptive BSR.

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

[0165] In addition, for the padding BSR, UE 200 may report a BS extended BSR based on the following situation, which means that BSR-BSExtApplied is configured and the number of padding bits is greater than the size of the traditional BSR (and / or the subheader of the traditional BSR). In addition, for the padding BSR, UE 200 may report a traditional BSR based on the following situation, which means that BSR-BSExtApplied is configured and the number of padding bits is less than the size of the traditional BSR (and / or the subheader of the traditional BSR). Here, UE 200 may report a BS extended BSR or a traditional BSR for all LCGs that have data available for transmission. In addition, UE200 may report a BS extended BSR or a traditional BSR for the following LCG, which is an LCG to which a logical channel determined based on priority assignment belongs among logical channels that have data available for transmission.

[0166] UE 200 sends the enhanced BSR MAC CE to base station 100 (step S350). Fig.10 The extended cache size field corresponding to the LCG as shown is set with an index corresponding to the cache size of the UL data, and a BS extended BSR MAC CE is generated. UE 200 sends the generated BS extended BSR MAC CE to the base station 100. For example, UE 200 can apply the logical channel prioritization (LCP) process to send an enhanced BSR MAC CE. Here, the logical channel prioritization process can be a process applied when performing initial transmission. For example, in the logical channel prioritization process, logical channels (e.g., MAC CE of logical channels) can be prioritized in the following order. In the following description, logical channels with high priority are listed at the beginning.

[0167] -MAC CE for C-RNTI or data from UL-CCCH

[0168] -MAC CE for (Extended) BSR, with exception of BSR included for padding (MAC CE for (Extended) BSR, excluding BSR included for padding)

[0169] -MAC CE for (Extended) Pre-emptive BSR

[0170] -data from any Logical Channel, except data from UL-CCCH (data from any logical channel except data from UL-CCCH)

[0171] -MAC CE for BSR included for padding

[0172] For example, the enhanced BSR MAC CE may have a higher priority than the MAC CE for (Extended) BSR, with exception of BSR included for padding. For example, it may be specified that the enhanced BSR MAC CE has a lower priority than the MAC CE for C-RNTI or data from UL-CCCH, and a higher priority than the MAC CE for (Extended) BSR. In addition, the enhanced BSR MAC CE may have a higher priority than the MAC CE for (Extended) Pre-emptive BSR. For example, it may be specified that the enhanced BSR MAC CE has a lower priority than the MAC CE for (Extended) BSR, with exception of BSR included for padding, and a higher priority than the MAC CE for (Extended) Pre-emptive BSR. In addition, the enhanced BSR MAC CE may have a higher priority than data from any Logical Channel, except data from UL-CCCH. For example, it may be specified that the enhanced BSR MAC CE has a lower priority than the MAC CE for (Extended) Pre-emptive BSR, and a higher priority than data from any Logical Channel, except data from UL-CCCH. In addition, the enhanced BSR MAC CE may have a higher priority than the MAC CE for BSR included for padding. For example, it may be specified that the enhanced BSR MAC CE has a lower priority than data from any Logical Channel, except data from UL-CCCH, and a higher priority than the 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) process.

[0173] In this way, according to an embodiment of the present disclosure, a message containing configuration information for determining whether to use BSR is sent and received, the BSR contains at least one first field and at least one changed second field, and the BSR is used to provide information about the UL data volume, the at least one first field indicates at least one LCG whose cache status is reported, and the at least one changed second field corresponds to the at least one LCG and is related to the UL data volume.

[0174] As a result, compared with a BSR including the first field and the second field (i.e., a conventional BSR), the amount of information related to the amount of UL data in the BSR can be increased. Therefore, the efficiency of scheduling UL data using the BSR can be improved. In particular, the method for scheduling XR data using an XR-specific BSR can be concretized, and the efficiency of scheduling XR data using an XR-specific BSR can be improved.

[0175] In addition, the configuration information is included in the configuration information of the logical channel. Thus, the configuration information can be configured for each logical channel. In particular, the logical channel can establish a corresponding relationship with the XR service, so the configuration information can be configured for the XR service in essence.

[0176] In addition, the configuration information is a flag, so that the configuration information can be processed with a small amount of data, thereby suppressing the increase of communication resources used for signaling of the configuration information.

[0177] In addition, the at least one changed second field is the second field whose size is increased. Thus, the amount of information related to the UL data amount can be increased by following the practice of the second field. For example, the range or granularity of the UL data amount processed can be expanded. That is, the upper limit of the UL data amount can be increased or the granularity can be subdivided.

[0178] In addition, the at least one changed second field is a cache size field indicating information for indicating the total amount of data of each logical channel of the corresponding at least one LCG. Thus, the range or granularity of the cache size that can be processed in the cache size field can be expanded. Therefore, the quantization error of UL data (such as XR data) with a large and large capacity change can be reduced.

[0179] <5-2. Modifications>

[0180] Reference Figures 14 to 20 , the first to fourth modified examples involved in the first embodiment of the present disclosure are described. In addition, two or more of these modified examples may be combined.

[0181] (1) First Modification: Another Example of BS Extended BSR Configuration Information

[0182] In the above-mentioned embodiment of the present disclosure, the BS extended BSR configuration information is a flag. However, the BS extended BSR configuration information involved in the embodiment of the present disclosure is not limited to this example.

[0183] As a first variation example 1 of this embodiment, the BS extended BSR configuration information may be information related to the length of at least one changed second field. Specifically, the BS extended BSR configuration information is information indicating the length of the second field whose size is increased. Fig.14 and Fig.15 , the BS extended BSR configuration information involved in this variant is described in detail.

[0184] For example, Fig.14 As shown in information 33 of the BS, the BSR-BufferSizeFieldLength as the BS extended BSR configuration information is included as a parameter of the LogicalChannelConfig. Fig.15 As shown in Table 43 of , BSR-BufferSizeFieldLength indicates the length of the buffer size field. The BSR-BufferSizeFieldLength indicates whether the BS extended BSR is used by the presence or absence. For example, the BSR-BufferSizeFieldLength indicates that the UE 200 is configured to report the BS extended BSR when it exists, and indicates the length of the extended buffer size field in the BS extended BSR. On the contrary, the absence of the BSR-BufferSizeFieldLength indicates that the UE 200 is not configured to report the BS extended BSR, that is, it is configured to report the traditional BSR.

[0185] In addition, BSR-BufferSizeFieldLength may represent information indicating the length of the buffer size field. For example, BSR-BufferSizeFieldLength indicates an index corresponding to the length of the buffer size field (eg, a value or range of the length).

[0186] In addition, as a first variant example 2 of the present embodiment, the BS extended BSR configuration information may be information for identifying an LCG using the BS extended BSR. That is, the BS extended BSR configuration information may indicate an ID of an LCG. For example, the BS extended BSR configuration information may indicate an ID of an LCG to which a logical channel belongs. For example, the UE 200 may determine an ID of an LCG to which a logical channel belongs based on the ID of an LCG indicated by the BS extended BSR configuration information. Fig.16 and Fig.17 , the BS extended BSR configuration information involved in this variant is described in detail.

[0187] For example, Fig.16As shown in information 35, the parameter of LogicalChannelConfig includes logicalChannelGroup-XR-Ext-r18 as BS extended BSR configuration information. Fig.17 As shown in Table 45, logicalChannelGroup-XR-Ext-r18 can indicate an LCG ID. For example, logicalChannelGroup-XR-Ext-r18, when present, can indicate the LCG ID to which the logical channel belongs. In addition, logicalChannelGroup-XR-Ext-r18 can indicate that for the LCG ID, UE 200 is configured to report a BS extended BSR. In addition, the absence of logicalChannelGroup-XR-Ext-r18 can indicate that UE 200 is not configured to report a BS extended BSR, that is, is configured to report a traditional BSR.

[0188] In addition, when logicalChannelGroup-XR-Ext-r18 is configured, the configuration of other LCGIDs can be ignored. In this case, for example, Fig.16The logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 as shown. That is, in the case where the logicalChannelGroup-XR-Ext-r18 indicating the LCG ID is included in the logical channel config, the UE 200 can ignore the logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 contained in the logical channel config. As described above, the logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 indicates the LCG ID. Here, the maximum number of LCGs configured using logicalChannelGroup-XR-Ext-r18 can be 8 (for example, 8 LCGs with IDs from 0 to 7, or 8 LCGs with IDs from 8 to 15). That is, the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 can be any value from 0 to 7 (or, any value from 8 to 15). For example, by setting the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 to 8 to 15, it is possible to configure an ID of an LCG different from the ID of the LCG configured using logicalChannelGroup (i.e., from 0 to 7). In addition, the maximum number of LCGs configured using logicalChannelGroup-XR-Ext-r18 can be 16 (e.g., 16 LCGs with IDs from 0 to 15, or 16 LCGs with IDs from 8 to 23). That is, the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 can be any value from 0 to 15 (or, any value from 8 to 23). For example, by setting the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 to 16, it is possible to configure an ID of more LCGs than the number of IDs of the LCGs configured using logicalChannelGroup (i.e., 8). In addition, the maximum number of LCGs configured using logicalChannelGroup-XR-Ext-r18 can be 256 (e.g., 256 LCG IDs from 0 to 255, or 256 LCG IDs from 256 to 511). That is, the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 can be any value from 0 to 255 (or, any value from 256 to 511).For example, by setting the ID of the LCG configured using logicalChannelGroup-XR-Ext-r18 to 256 to 511, it is possible to configure an ID of an LCG different from the ID of the LCG configured using logicalChannelGroup and / or logicalChannelGroup-IAB-Ext-r17 (i.e., from 0 to 255). In this way, when logicalChannelGroup-XR-Ext-r18 is configured, UE 200 can easily perform an action on the BSR by ignoring the configuration of other LCG IDs without configuring the LCG ID using different parameters.

[0189] In addition, as a first variation 3 of this embodiment, the BS extended BSR configuration information may be information for indicating the type of UL data. For example, the type of UL data may be pose / control or video.

[0190] For example, Fig.18 As shown in information 37, the parameter of LogicalChannelConfig includes BSR-DataType-XR as BS extended BSR configuration information. Fig.19 As shown in Table 47, the presence of BSR-DataType-XR indicates that for the LCG to which the logical channel that caches the UL data of the indicated type belongs, UE 200 is configured to report the BS extended BSR. Conversely, the absence of BSR-DataType-XR indicates that UE 200 is not configured to report the BS extended BSR, that is, it is configured to report the traditional BSR.

[0191] Thus, according to the first variant example 1 of the present embodiment, the BS extended BSR configuration information may be information related to the length of at least one changed second field. Thus, it is also possible to indicate whether to use the BS extended BSR by means of information related to the length of the changed second field. Therefore, it is possible to suppress the increase in communication resources for signaling of the BS extended BSR configuration information. In addition, the BS extended BSR configuration information indicates the length of the second field whose size is increased, thereby enabling the size of the changed second field to be dynamically changed.

[0192] In addition, according to the first variant example 2 of the present embodiment, the BS extended BSR configuration information may be information for identifying the LCG using the BS extended BSR. In this way, by aggregating whether to use the BS extended BSR and the LCG ID into one information, it is possible to determine whether to use the BS extended BSR while determining the LCG ID of the logical channel.

[0193] In addition, according to the first variant example 3 of the present embodiment, the BS extended BSR configuration information may be information for indicating the type of UL data. Thus, it is possible to indicate whether to use the BS extended BSR for each type of UL data. Therefore, it is possible to select an appropriate BSR corresponding to the type of UL data. In particular, the characteristics of XR data vary greatly depending on the type of data. Therefore, by selecting an appropriate BSR corresponding to the type of XR data, scheduling suitable for XR data can be performed.

[0194] (2) Second Modification Example: Another Example of Configuration Information Including BS Extended BSR Configuration Information

[0195] In the above-mentioned embodiments 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 involved in the embodiments of the present disclosure is not limited to this example.

[0196] As a second variation example 1 of this embodiment, the BS extended BSR configuration information may be included in the configuration information of the LCG. Thus, the BS extended BSR is configured for each LCG. Fig. 20 This modification example will be described in detail.

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

[0198] In addition, as a second variation 2 of this embodiment, the BS extended BSR configuration information may be included in the SR configuration information. In this way, the BS extended BSR is configured for each SR.

[0199] For example, the BS extended BSR configuration information is included in the Fig. 20 The SchedulingRequestConfig or SchedulingRequestResourceConfig of an example of the SR configuration information 53 as shown in the figure establishes a corresponding relationship with the schedulingRequestID. Here, the schedulingRequestID is also included in the configuration information of the logical channel. Therefore, the UE 200 determines whether to use the BS extended BSR for the LCG by referring 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. In other words, it can be considered that the BS extended BSR is indirectly configured for each logical channel via the schedulingRequestID.

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

[0201] For example, the BS extended BSR configuration information is included in the Fig. 20 The BSR-Config is an example of BSR configuration information 55 as shown in FIG. UE 200 refers to the BS extended BSR configuration information included in BSR-Config to determine whether to use the BS extended BSR.

[0202] Thus, according to the second variant 1 of this embodiment, the BS extended BSR configuration information can be included in the configuration information of the LCG. Thus, the BS extended BSR configuration information can be configured for each LCG. Since the BSR is reported for the LCG, the processing can be reduced compared to the case where the BS extended BSR is configured for the logical channel.

[0203] In addition, according to the second variant 2 of this embodiment, the BS extended BSR configuration information may be included in the SR configuration information. Thus, the BS extended BSR configuration information can be configured for each SR. Therefore, for at least one logical channel configured for the same SR, whether to use the BS extended BSR can be uniformly managed.

[0204] In addition, according to the second variation 3 of this embodiment, the BS extended BSR configuration information may be included in the BSR configuration information. Thus, the BS extended BSR configuration information can be configured for each UE 200. Therefore, it is possible to switch all BSRs used by the UE 200 to be BS extended BSRs in a unified manner.

[0205] (3) Third Modification: Another Example of BS Extended BSR Format

[0206] In the above-mentioned embodiment of the present disclosure, the BS extended BSR includes the first field and the modified second field. However, the BS extended BSR involved in the embodiment of the present disclosure is not limited to this example.

[0207] As a third variation of this embodiment, the BS extended BSR may further include at least one second field. The at least one extended second field corresponds to an LCG determined based on the BS extended BSR configuration information among the multiple LCGs, and the at least one second field corresponds to an LCG other than the LCG determined based on the BS extended BSR configuration information among the multiple LCGs. In other words, only the cache size field corresponding to the LCG determined based on the BS extended BSR configuration information among the multiple LCGs is extended.

[0208] Specifically, the BS extended BSR includes multiple LCG fields, at least one extended cache size field, and at least one traditional cache size field. The at least one extended cache size field corresponds to an LCG in the multiple LCGs that is determined to use the BS extended BSR based on the BS extended BSR configuration information. In addition, the at least one traditional cache size field corresponds to an LCG in the multiple LCGs other than the above LCGs.

[0209] Reference Fig.10 , this modification example is described in detail. For example, Fig.10 In the format 21 of FIG. 1 , it is assumed that cache size 1 corresponds to LCG0 and cache size 2 corresponds to LCG1. In the case where it is determined that the BS extended BSR is used for LCG0, the BS extended BSR includes a cache size 1 field that is longer than the traditional cache size field as an extended cache size field. In addition, in the case where it is not determined that the BS extended BSR is used for LCG1, the BS extended BSR includes a cache size 2 field as a traditional cache size field.

[0210] Thus, according to the third variant of the present embodiment, the BS extended BSR further includes at least one second field, at least one LCG is a plurality of LCGs, at least one extended second field corresponds to an LCG determined based on the BS extended BSR configuration information among the plurality of LCGs, and at least one second field corresponds to an LCG other than the LCG determined based on the configuration information among the plurality of LCGs. Thus, only the second field that needs to be extended can be extended, and the excessive increase in the size of the BSR can be suppressed. As a result, the waste of communication resources caused by BSR transmission can be suppressed.

[0211] (4) Fourth Modification: Cases that Conform to Other TSs

[0212] In the above-mentioned example of the embodiment of the present disclosure, the system 1 is a system that complies with TS of 5G or NR. However, the system 1 involved in the embodiment of the present disclosure is not limited to this example.

[0213] In the fourth variant of the present embodiment, system 1 may be a system that complies with other TS of 3GPP. As an example, system 1 may be a system that complies with TS of LTE (Long Term Evolution), LTE-A (LTE Advanced) or 4G, and base station 100 may be eNB (evolved Node B). Alternatively, base station 100 may be ng-eNB. As another example, system 1 may be a system that complies with TS of 3G, and base station 100 may be NodeB. As another example, system 1 may be a system that complies with TS of the next generation (e.g., 6G).

[0214] Alternatively, the system 1 may be a system compliant with TS of other standardization organizations regarding mobile communications.

[0215] <6. Second embodiment>

[0216] In the second embodiment of the present disclosure, configuration information for determining whether the changed second field uses a BSR including delay information (hereinafter also referred to as delayed BSR) is transmitted from base station 100 to UE 200. Note that description of substantially the same contents as those of the first embodiment will be omitted.

[0217] <6-1. Operation example>

[0218] Refer to Figure 21~ Fig.24 , an example of the operation of the base station 100 and the UE 200 involved in the second embodiment of the present disclosure is described.

[0219] (1) Delayed BSR format

[0220] The modified second field of the delayed BSR according to the present embodiment includes the 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.

[0221] Specifically, the changed second field includes a cache 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 the LCG. The delay information indicates information used to indicate the remaining time until the allowed delay of data belonging to the corresponding LCG.

[0222] Reference Fig.21A and Fig. 21B , the format of the delayed BSR involved in this embodiment is described in detail. Fig.21A and Fig. 21B The buffer size field of the conventional long BSR is an example of the MAC CE format of the modified delayed BSR. In addition, the delayed BSR is not limited to the conventional long BSR, and the buffer size field of the conventional BSR in the other formats mentioned above may also be the modified BSR.

[0223] For example, delaying BSR such as Fig.21A As shown in the format 23A of FIG. 23A, the first field includes the LCGi field, and the second field after the change includes the reduced cache size j field and the delay information (Delay Info) j field. The LCGi field indicates the existence of the reduced cache size j field and the delay information j field for LCGi.

[0224] The reduced cache size j field is used to identify the total amount of data available for all logical channels belonging to the corresponding LCGi, similar to the traditional cache size j field. The size of the reduced cache size j field is, for example, 6 bits, which is shorter than the size of the traditional cache size j field, which is 8 bits. In addition, the size of the reduced cache size j field is not limited thereto, and can be any other size that is shorter than the traditional cache size j field. In addition, the size of the reduced cache size j field can be different according to the corresponding LCGi.

[0225] The Reduced Cache Size j field indicates an index corresponding to a cache size (eg, a cache size level, a cache size value, or a cache size range) in, for example, a table regarding a 6-bit cache size field not shown.

[0226] The delay information j field as the third field represents information used to indicate the delay information of the corresponding LCGi. The size of the delay information j field is, for example, 2 bits, which is shorter than the size of the traditional cache size j field of 8 bits. The sum of the size of the reduced cache size j field and the size of the delay information j field is equal to the size of the traditional cache size j field. In addition, the size of the delay information j field is not limited thereto, and can be any other size that is shorter than the traditional cache size j field. In addition, the size of the delay information j field can be different according to the corresponding LCGi.

[0227] The delay information j field indicates the remaining time until the allowed delay of the data belonging to the corresponding LCG (for example, shown in units of ms, time slots, or subframes). In addition, the delay information j field may indicate an index corresponding to the remaining time (for example, a value or range of the remaining time), and may indicate a flag corresponding to the remaining time (for example, a flag indicating the size of the remaining time).

[0228] The reduced buffer size j field and the delay information j field are processed integrally, and their combination is included in ascending order corresponding to LCGi.

[0229] Alternatively, for example, the delayed BSR may be Fig. 21B As shown in format 23B, the first field includes the LCGi field, and the changed second field includes the traditional cache size j field and the delay information i field.

[0230] In format 23A, the delay information j field replaces a portion of the traditional cache size field, and in format 23B, the delay information i field is appended to the traditional cache size field. For example, the delay information i field is appended between the LCGi field and the traditional cache size field. In addition, the delay information i field can also be appended after the traditional cache size field.

[0231] The content and size of the delay information i field are the same as those of the format 23A. The buffer size j field and the delay information i field are included in ascending order corresponding to the LCGi.

[0232] There is a difference between delayed BSR and other BSR formats. For example, an LCID / eLCID indicating a delayed BSR is defined. As a result, the delayed BSR can be sent as a MAC CE. In addition, the MAC CE of the delayed BSR can be included in the MAC PDU and sent. That is, the MAC subheader including the LCID / eLCID indicating the delayed BSR and the MAC CE of the delayed BSR are included in the MAC sub-PDU, and the MAC PDU including the MAC sub-PDU is sent.

[0233] (2) Delayed BSR configuration information

[0234] The configuration information for determining whether to use the delayed BSR involved in this embodiment (hereinafter, also referred to as delayed BSR configuration information) is defined. The delayed BSR configuration information is included in the configuration information of the logical channel. Thus, the delayed BSR is configured for each logical channel. Fig. 22 and Fig.23 , the delayed BSR configuration information is explained in detail.

[0235] Specifically, the delayed BSR configuration information is included in LogicalChannelConfig. Fig. 22 As shown in information 39, BSR-DelayApplied as delayed BSR configuration information may be included as a parameter of LogicalChannelConfig. In addition, the LogicalChannelConfig involved in this embodiment may be substantially the same as the LogicalChannelConfig described in the first embodiment except for BSR-BSExtApplied, and the part about BSR-BSExtApplied may be replaced by BSR-DelayApplied.

[0236] In addition, the delayed BSR configuration information is a flag. Fig.23As shown in Table 49, BSR-DelayApplied, when present, indicates that UE 200 is configured to report a delayed BSR. Conversely, the absence of BSR-DelayApplied indicates that UE 200 is not configured to report a delayed BSR, that is, is configured to report a conventional BSR. In addition, the delayed BSR configuration information is not limited to a flag indicating whether a delayed BSR is used by its presence, but may also be a flag indicating whether a delayed BSR is used by its value. For example, the delayed BSR configuration information indicates the use of a conventional BSR when the value is 0, and indicates the use of a delayed BSR when the value is 1.

[0237] (3) Messages containing configuration information

[0238] The message including the delayed BSR configuration information is substantially the same as the message including the BS extended BSR configuration information, and thus the description thereof is omitted.

[0239] (4) Actions of UE 200 Based on Configuration Information

[0240] The UE 200 involved in this embodiment determines whether to use the delayed BSR based on the delayed BSR configuration information obtained from the received RRC message. For example, the UE 200 determines whether to use the delayed BSR for the 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 of the LCG to which the logical channel to which the delayed BSR is determined to be used belongs.

[0241] For example, the LogicalChannelConfig included in the received RRC message of UE 200 includes: Fig. 22 In the case of BSR-DelayApplied as shown, the delayed BSR is used as the BSR for the LCG including the logical channel configured with the LogicalChannelConfig.

[0242] (5) Processing flow

[0243] Reference Fig.13 , an example of the processing involved in this embodiment is described. In addition, the processing from step S310 to step S340 can be implemented by replacing the BS extended BSR involved in the first embodiment with a delayed BSR, and replacing the BSR-BSExtApplied involved in the first embodiment with BSR-DelayApplied, so the description is omitted.

[0244] UE 200 sends the enhanced BSR MAC CE to base station 100 (step S350). Fig.21AFor each LCG as shown in FIG. 1 , an index corresponding to the buffer size of UL data is set for the corresponding reduced buffer size field, and delay information is set for the corresponding delay information field to generate a delayed BSR MAC CE. Alternatively, UE 200 may generate a delayed BSR MAC CE for the LCG as shown in FIG. Fig. 21B For each LCG as shown, an index corresponding to the cache size of UL data is set for the corresponding cache size field, and delay information is set for the corresponding delay information field, and a delayed BSR MAC CE is generated. UE 200 sends the generated delayed BSR MAC CE to base station 100. In addition, UE 200 can apply the logical channel priority (LCP) process and send an enhanced BSR MAC CE (i.e., a delayed BSR MAC CE) in the same way as in the first embodiment.

[0245] Thus, according to the embodiment of the present disclosure, the modified second field included in the enhanced BSR includes the second field and a third field different from the second field. Thus, information with different content and / or format from the information indicated by the second field can be added.

[0246] In addition, the second field is a cache size field indicating information for indicating the total amount of data of each logical channel of the corresponding at least one LCG, and the third field is a field indicating information for indicating delay information of the corresponding at least one LCG, and the delay information indicates information for indicating the remaining time until the allowed delay of data belonging to the corresponding at least one LCG. Thus, delay information about cached data can be reported. Therefore, scheduling can be performed for the data taking into account the delay information. In particular, PDB can be set for XR data, so by using the delayed BSR to report delay information for XR data, scheduling that satisfies the PDB becomes possible.

[0247] <6-2. Modifications>

[0248] First to fifth modified examples according to the second embodiment of the present disclosure are described. In addition, two or more of these modified examples may be combined.

[0249] (1) First Modification: Another Example of Delaying BSR Configuration Information

[0250] In the above-mentioned embodiment of the present disclosure, the delayed BSR configuration information is a flag. However, the delayed BSR configuration information involved in the embodiment of the present disclosure is not limited to this example.

[0251] As a first variation example 1 of this embodiment, the delayed BSR configuration information may be information related to the length of at least one changed second field. Specifically, the delayed BSR configuration information is information indicating the length of the third field. Fig.14 and Fig.15 , the delayed BSR configuration information involved in this variant is described in detail.

[0252] For example, replacing Fig.14 The BSR-BufferSizeFieldLength shown in information 33 includes the BSR-DelayInfoFieldLength as the delayed BSR configuration information as a parameter of LogicalChannelConfig. For example, BSR-DelayInfoFieldLength is as follows: Fig.15 The length of the delay information field is indicated, as shown in Table 43 of BSR-BufferSizeFieldLength. For example, the presence of BSR-DelayInfoFieldLength indicates that the UE 200 is configured to report a delayed BSR and indicates the length of the delay information field in the delayed BSR. Conversely, the absence of BSR-DelayInfoFieldLength indicates that the UE 200 is not configured to report a delayed BSR, that is, is configured to report a conventional BSR.

[0253] In addition, BSR-DelayInfoFieldLength may represent information for indicating the length of the delay information field. For example, BSR-DelayInfoFieldLength indicates an index corresponding to the length of the delay information field (eg, a value or range of the length).

[0254] Thus, according to the first variant example 1 of this embodiment, the delayed BSR configuration information may be information related to the length of at least one changed second field. In addition, the delayed BSR configuration information indicates the length of the third field, thereby dynamically changing the length of the third field and the changed second field.

[0255] In addition, as a first variation 2 of this embodiment, the delayed BSR configuration information may be information for identifying the LCG using the delayed BSR. In addition, this variation can be implemented by replacing the BS extended BSR involved in the first variation 2 of the first embodiment with a delayed BSR, so the description is omitted.

[0256] In addition, as the first variation 3 of this embodiment, the delayed BSR configuration information may be information for indicating the type of UL data. In addition, this variation can be implemented by replacing the BS extended BSR involved in the first variation 3 of the first embodiment with a delayed BSR, so the description is omitted.

[0257] (2) Second Modification Example: Another Example of Configuration Information Including Delayed BSR Configuration Information

[0258] In the above-mentioned embodiments 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 involved in the embodiments of the present disclosure is not limited to this example.

[0259] As a second variation 1 of this embodiment, delayed BSR configuration information may be included in the configuration information of LCG. In addition, this variation can be implemented by replacing the BS extended BSR involved in the second variation 1 of the first embodiment with delayed BSR, so the description is omitted.

[0260] In addition, as a second variation 2 of this embodiment, delayed BSR configuration information may be included in SR configuration information. In addition, this variation can be implemented by replacing the BS extended BSR involved in the second variation 2 of the first embodiment with delayed BSR, so the description is omitted.

[0261] In addition, as a second variation 3 of this embodiment, delayed BSR configuration information may be included in BSR configuration information. In addition, this variation can be implemented by replacing the BS extended BSR involved in the second variation 3 of the first embodiment with delayed BSR, so the description is omitted.

[0262] (3) Third Modification: Another Example of the Format of Delayed BSR

[0263] In the above-mentioned embodiment of the present disclosure, the delayed BSR includes the first field and the changed second field. However, the delayed BSR involved in the embodiment of the present disclosure is not limited to this example.

[0264] As a third variation of this embodiment, the delayed BSR may further include at least one second field. At least one changed second field corresponds to an LCG determined based on the delayed BSR configuration information among the multiple LCGs, and at least one second field corresponds to an LCG other than the LCG determined based on the delayed BSR configuration information among the multiple LCGs. In other words, only the third field is added to the second field corresponding to the LCG determined based on the delayed BSR configuration information among the multiple LCGs, and only the second field is changed.

[0265] Specifically, the delayed BSR includes a plurality of LCG fields, at least one group of a reduced buffer size field and a delay information field, and at least one traditional buffer size field. The at least one group of a reduced buffer size field and a delay information field corresponds to an LCG in the plurality of LCGs that determines to use the delayed BSR based on the delayed BSR configuration information. In addition, at least one traditional buffer size field corresponds to an LCG other than the above LCG in the plurality of LCGs.

[0266] Reference Fig.21A, this modification example is described in detail. For example, Fig.21A In format 23A, it is assumed that cache size 1 corresponds to LCG0, and cache size 3 (not shown) corresponds to LCG1. When it is determined that the delayed BSR is used for LCG0, the delayed BSR includes a set of a 6-bit cache size 1 field and a 2-bit delay information 1 field as a set of a reduced cache size field and a delay information field. In addition, when it is not determined that the delayed BSR is used for LCG1, the delayed BSR includes an 8-bit cache size 3 field as a conventional cache size field.

[0267] Alternatively, the delayed BSR may include a plurality of LCG fields, a group of at least one traditional cache size field and a delay information field, and at least one traditional cache size field without a delay information field. The group of at least one traditional cache size field and a delay information field corresponds to an LCG in the plurality of LCGs that determines to use the delayed BSR based on the delayed BSR configuration information. In addition, the at least one traditional cache size field without a delay information field corresponds to an LCG in the plurality of LCGs other than the above-mentioned LCG.

[0268] Reference Fig. 21B , this modification example is described in detail. For example, Fig. 21B In the format 23B of FIG. 1, it is assumed that cache size 1 corresponds to LCG0, and cache size 3 (not shown) corresponds to LCG1. When it is determined that the delayed BSR is used for LCG0, the delayed BSR includes a set of an 8-bit cache size 1 field and a 2-bit delay information 0 field as a set of a conventional cache size field and a delay information field. In addition, when it is not determined that the delayed BSR is used for LCG1, the delayed BSR includes an 8-bit cache size 3 field as a conventional cache size field, and Fig.23 B is different and does not contain delay information 1.

[0269] Thus, according to the third variation of the present embodiment, only the second field that requires the addition of delay information can be changed, and the size of the BSR can be prevented from increasing excessively. As a result, the waste of communication resources caused by BSR transmission can be prevented.

[0270] (4) Fourth Modification: Another Example of a Field Indicating Delay Information

[0271] In the above-mentioned embodiment of the present disclosure, the second field after the change includes the second field and the third field. However, the second field after the change involved in the embodiment of the present disclosure is not limited to this example.

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

[0273] Reference Fig.24 , the format of the delayed BSR involved in this variant is described in detail. Fig.24 This is an example of a MAC CE format indicating that the buffer size field of the conventional long BSR is a modified delayed BSR. In addition, the delayed BSR involved in this modification is not limited to the conventional long BSR, and the buffer size field of the conventional BSR of other formats may be a modified BSR.

[0274] For example, Fig.24 As shown in the format 25 of , the delay BSR includes multiple LCG fields and at least one cache size / delay information field. The LCGi field indicates the existence of the cache size / delay information j field for LCGi. The cache size / delay information field indicates an index corresponding to a group of cache size and delay information. A table indicating the correspondence between the index and the group of cache size and delay information is defined. In addition, the cache size / delay information j field is included in ascending order corresponding to LCGi.

[0275] also, Fig.24 An example is shown in which the size of the cache size / delay information field is the same as the size of the conventional cache size field, but it may also be smaller than the size of the conventional cache size field. For example, the size of the cache size / delay information field may be 16 bits, 24 bits, or more.

[0276] In addition, as in the third variation 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 determined based on the delayed BSR configuration information among the multiple LCGs is changed to the buffer size / delay information field.

[0277] Thus, according to the fourth variant of the present embodiment, in the delayed BSR, at least one second field after the change is a field indicating the following information, which is used to indicate the total amount of data of each logical channel of the corresponding at least one LCG and the delay information of the corresponding at least one LCG. Thus, in the BSR, the buffer size and delay information can be managed by one field. Therefore, the reception processing of the BSR (i.e., field parsing processing) can be simply performed.

[0278] (5) Fifth Modification: Cases Complying with Other TSs

[0279] In the above example of the embodiment of the present disclosure, the system 1 is a system that complies with TS of 5G or NR. However, the system 1 involved in the embodiment of the present disclosure is not limited to this example. The system 1 may be a system that complies with other TSs, similarly to the fourth variant of the first embodiment.

[0280] The embodiments of the present disclosure have been described above, but the present disclosure is not limited to the embodiments. It should be understood by those skilled in the art that the embodiments are merely illustrative and that various modifications can be made without departing from the scope and concept of the present disclosure.

[0281] For example, the steps in the process described in this specification do not have to be executed in a time series in the order described in the flowchart or sequence diagram. For example, the steps in the process may be executed in an order different from the order described in the flowchart or sequence diagram, or may be executed in parallel. In addition, part of the steps in the process may be deleted, or further steps may be added to the process.

[0282] For example, a method for performing the actions of one or more components of the device described in this specification may be provided, and a program for causing a computer to perform the actions of the above components may be provided. In addition, a computer-readable non-transitory physical recording medium storing the program may be provided. Of course, such methods, programs, and computer-readable non-transitory physical recording media (non-transitory tangible computer-readable storage medium) are also included in the present disclosure.

[0283] For example, one or more components of the base station described in this specification may be included in a module for the base station, and the module may be provided. In other words, a base station module that performs the processing of the base station described in this specification may be provided.

[0284] For example, one or more components of the user equipment (UE) described in this specification may be included in a module for the UE, and the module may be provided. In other words, a module for the UE that performs the processing of the UE described in this specification may be provided.

[0285] For example, in the present disclosure, user equipment (UE) may also be referred to 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 and other names.

[0286] For example, in the present disclosure, 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, UE may be a device provided on a mobile body, or the mobile body itself. The mobile body may be a vehicle such as a car or an electric car, or an aircraft such as an airplane or a drone, or other mobile bodies such as a ship. Alternatively, in the present disclosure, UE may be other IoT (Internet of Things) devices such as sensors and cameras. UE may be mobile or fixed.

[0287] For example, in the present disclosure, "transmit" may refer to the processing of at least one layer within the protocol stack used for transmission, or may refer to physically sending a signal wirelessly or by wire. Alternatively, "transmit" may refer to a combination of processing at least one layer above and physically sending a signal wirelessly or by wire. Similarly, "receive" may refer to the processing of at least one layer within the protocol stack used for reception, or may refer to physically receiving a signal wirelessly or by wire. Alternatively, "receive" may refer to a combination of processing at least one layer above and physically receiving a signal wirelessly or by wire. The above at least one layer may be referred to as at least one protocol.

[0288] For example, in the present disclosure, "obtain" or "acquire" may refer to obtaining information from stored information, or may refer to obtaining information from information received from other nodes, or may refer to obtaining the information by generating information.

[0289] For example, in the present disclosure, “include” and “comprise” do not mean that only the listed items are included, but mean that only the listed items may be included, or further items may be included in addition to the listed items.

[0290] For example, in the present disclosure, "or" does not mean a logical exclusive OR but a logical OR.

[0291] In addition, the technical features included in the above-mentioned embodiments can be expressed as the following features. Of course, the present disclosure is not limited to the following features.

[0292] (Feature 1)

[0293] A device (200), comprising:

[0294] A communication processing unit (233) receives a message including configuration information, wherein the configuration information is used to determine whether to use a cache status report including at least one first field and at least one changed second field; and

[0295] An information acquisition unit (231) acquires the configuration information contained in the message.

[0296] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0297] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0298] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0299] (Feature 2)

[0300] According to the aforementioned device of feature 1,

[0301] The aforementioned configuration information is included in the configuration information of the logical channel.

[0302] (Feature 3)

[0303] According to the aforementioned device of feature 1,

[0304] The aforementioned configuration information is included in the configuration information of the logical channel group.

[0305] (Feature 4)

[0306] According to the aforementioned device of feature 1,

[0307] The aforementioned configuration information is included in the configuration information of the scheduling request.

[0308] (Feature 5)

[0309] According to the aforementioned device of feature 1,

[0310] The aforementioned configuration information is included in the configuration information of the cache status report.

[0311] (Feature 6)

[0312] The device according to any one of features 1 to 5,

[0313] The aforementioned configuration information is a flag.

[0314] (Feature 7)

[0315] The device according to any one of features 1 to 5,

[0316] The aforementioned configuration information is information related to the length of the aforementioned at least one changed second field.

[0317] (Feature 8)

[0318] The device according to any one of features 1 to 3,

[0319] The aforementioned configuration information is information for identifying a logical channel group using the aforementioned buffer status report.

[0320] (Feature 9)

[0321] The device according to any one of features 1 to 5,

[0322] The aforementioned configuration information is information for indicating the type of uplink data.

[0323] (Feature 10)

[0324] The device according to any one of features 1 to 9,

[0325] The cache status report further includes at least one second field.

[0326] The aforementioned at least one logical channel group is a plurality of logical channel groups,

[0327] The at least one changed second field corresponds to a logical channel group determined based on the configuration information among the plurality of logical channel groups.

[0328] The at least one second field corresponds to a logical channel group among the plurality of logical channel groups except a logical channel group determined based on the configuration information.

[0329] (Feature 11)

[0330] The device according to any one of features 1 to 10,

[0331] The at least one changed second field is the second field whose size is increased.

[0332] (Feature 12)

[0333] According to the aforementioned device of feature 11,

[0334] The at least one changed second field is a cache size field indicating information, where the information is used to indicate the total amount of data of each logical channel of the corresponding at least one logical channel group.

[0335] (Feature 13)

[0336] The device according to any one of features 1 to 10,

[0337] The at least one changed second field includes the second field and a third field different from the second field.

[0338] (Feature 14)

[0339] According to the aforementioned device of feature 13,

[0340] The second field is a cache size field indicating information, the information being used to indicate the total amount of data of each logical channel of the corresponding at least one logical channel group.

[0341] The third field is a field indicating information, and the information is used to indicate delay information of the corresponding at least one logical channel group.

[0342] The delay information indicates information indicating a remaining time until the data belonging to the corresponding at least one logical channel group is allowed to be delayed.

[0343] (Feature 15)

[0344] The device according to any one of features 1 to 10,

[0345] The at least one changed second field is a field indicating information, the information being used to indicate the 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,

[0346] The delay information indicates information indicating a remaining time until the data belonging to the corresponding at least one logical channel group is allowed to be delayed.

[0347] (Feature 16)

[0348] The device according to any one of features 1 to 15,

[0349] The aforementioned apparatus is a user equipment or a module used for the user equipment.

[0350] (Feature 17)

[0351] A device (100), comprising:

[0352] An information acquisition unit (141) acquires configuration information, wherein the configuration information is used to determine whether to use a cache status report including at least one first field and at least one changed second field; and

[0353] The communication processing unit (143) sends a message including the above configuration information,

[0354] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0355] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0356] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0357] (Feature 18)

[0358] According to the aforementioned device of feature 17,

[0359] The aforementioned apparatus is a base station or a module used for a base station.

[0360] (Feature 19)

[0361] A method, performed by a device (200), comprising:

[0362] receiving a message including configuration information for determining whether to use a cache status report including at least one first field and at least one changed second field; and

[0363] Obtain the aforementioned configuration information contained in the aforementioned message,

[0364] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0365] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0366] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0367] (Feature 20)

[0368] A method, performed by a device (100), comprising:

[0369] obtaining configuration information, the configuration information being used to determine whether to use a cache status report including at least one first field and at least one changed second field,

[0370] Send a message containing the above configuration information,

[0371] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0372] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0373] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0374] (Feature 21)

[0375] A program that causes a computer to:

[0376] receiving a message including configuration information for determining whether to use a cache status report including at least one first field and at least one changed second field; and

[0377] Obtain the aforementioned configuration information contained in the aforementioned message,

[0378] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0379] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0380] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0381] (Feature 22)

[0382] A program that causes a computer to:

[0383] obtaining configuration information, the configuration information being used to determine whether to use a cache status report including at least one first field and at least one changed second field; and sending a message including the configuration information,

[0384] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0385] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0386] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0387] (Feature 23)

[0388] A non-transitory tangible recording medium is a computer-readable non-transitory tangible recording medium, and contains a program for causing a computer to execute the following steps:

[0389] receiving a message including configuration information for determining whether to use a cache status report including at least one first field and at least one changed second field; and

[0390] Obtain the aforementioned configuration information contained in the aforementioned message,

[0391] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0392] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0393] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

[0394] (Feature 24)

[0395] A non-transitory tangible recording medium is a computer-readable non-transitory tangible recording medium, and contains a program for causing a computer to execute the following steps:

[0396] obtaining configuration information, the configuration information being used to determine whether to use a cache status report including at least one first field and at least one changed second field; and sending a message including the configuration information,

[0397] The aforementioned buffer status report is used to provide information about the amount of uplink data.

[0398] The at least one first field indicates at least one logical channel group for which the buffer status is reported,

[0399] The at least one changed second field corresponds to the at least one logical channel group and is related to the uplink data volume.

Claims

1. An apparatus (200), comprising: A communication processing unit (233) receives a message including configuration information, wherein the configuration information is used to determine whether to use a cache status report including at least one first field and at least one changed second field; as well as An information acquisition unit (231) acquires the configuration information contained in the message, The buffer status report is used to provide information about the amount of uplink data, The at least one first field indicates at least one logical channel group for which buffer status is reported, The at least one changed second field corresponds to the at least one logical channel group and is related to an uplink data amount.

2. The device according to claim 1, The configuration information is included in the configuration information of the logical channel.

3. The device according to claim 1, The configuration information is a flag.

4. The device according to claim 1, The configuration information is information related to the length of the at least one changed second field.

5. The device according to claim 1, The configuration information is information for identifying a logical channel group using the buffer status report.

6. The device according to claim 1, The configuration information is information for indicating the type of uplink data.

7. The device according to claim 1, The cache status report further comprises at least one second field, The at least one logical channel group is a plurality of logical channel groups, The at least one changed second field corresponds to a logical channel group determined based on the configuration information among the plurality of logical channel groups, The at least one second field corresponds to a logical channel group other than a logical channel group determined based on the configuration information, among the plurality of logical channel groups.

8. The device according to any one of claims 1 to 7, The at least one altered second field is the second field whose size is increased.

9. The device according to claim 8, The at least one changed second field is a cache size field indicating information, where the information is used to indicate the total amount of data of each logical channel of the corresponding at least one logical channel group.

10. The device according to any one of claims 1 to 7, The at least one changed second field includes the second field and a third field different from the second field.

11. The device according to claim 10, The second field is a cache size field indicating information, where the information is used to indicate the total amount of data of each logical channel of the corresponding at least one logical channel group. The third field is a field indicating information, where the information is used to indicate delay information of the corresponding at least one logical channel group. The delay information indicates information indicating a remaining time until an allowed delay of data belonging to the corresponding at least one logical channel group.

12. The device according to any one of claims 1 to 7, The at least one changed second field is a field indicating information, the information being 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, The delay information indicates information indicating a remaining time until an allowed delay of data belonging to the corresponding at least one logical channel group.

13. An apparatus (100), comprising: An information acquisition unit (141) acquires configuration information, wherein the configuration information is used to determine whether to use a cache status report including at least one first field and at least one changed second field; as well as The communication processing unit (143) sends a message including the configuration information. The buffer status report is used to provide information about the amount of uplink data, The at least one first field indicates at least one logical channel group for which buffer status is reported, The at least one changed second field corresponds to the at least one logical channel group and is related to an uplink data amount.

14. A method, performed by an apparatus (200), the method comprising: receiving a message including configuration information for determining whether to use a cache status report including at least one first field and at least one changed second field; as well as obtaining the configuration information contained in the message, The buffer status report is used to provide information about the amount of uplink data, The at least one first field indicates at least one logical channel group for which buffer status is reported, The at least one changed second field corresponds to the at least one logical channel group and is related to an uplink data amount.

15. A method, performed by an apparatus (100), comprising: Obtaining configuration information, the configuration information being used to determine whether to use a cache status report including at least one first field and at least one changed second field; as well as sending a message containing said configuration information, The buffer status report is used to provide information about the amount of uplink data, The at least one first field indicates at least one logical channel group for which buffer status is reported, The at least one changed second field corresponds to the at least one logical channel group and is related to an uplink data amount.

Images