Terminal device, method for terminal device, and base station device

Abstract

A terminal device (10): receives a radio resource control (RRC) message including information indicating a first remaining time threshold used for triggering a delay status report (DSR) and information indicating a list of second remaining time thresholds used for reporting a delay status in the DSR; triggers the DSR on the basis of the first remaining time threshold if the first remaining time threshold is set for a logical channel group (LCG); and transmits a DSR Medium Access Control Control Element (MAC CE) if the list of second remaining time thresholds is set.

Description

Terminal device, method of terminal device, and base station device Cross-reference to related applications

[0001] This application is based on Japanese Patent Application No. 2025-17320 filed on February 5, 2025, claims the benefit of its priority, and all the contents of the patent application are incorporated herein by reference.

[0002] This disclosure relates to a terminal device, a method of a terminal device, and a base station device.

[0003] In recent years, technological developments related to Extended Reality (XR) have been progressing. XR is a concept that includes multimedia integration technologies such as Virtual Reality (VR), Augmented Reality (AR), Mixed Reality (MR), and Substitutional Reality (SR). In XR, three-dimensional time-series image data in the real space and / or virtual space, audio data of multiple channels (stereo, 5.1ch, etc.), other data presented to the user, control data, etc. are transmitted and received in parallel. XR requires low latency and high reliability to maintain and improve the user experience quality.

[0004] Non-Patent Document 1 and Non-Patent Document 2 describe the technical specifications defined by the Third Generation Partnership Project (3GPP (registered trademark)), including the technical specifications for supporting XR.

[0005] 3GPP TS 38.321 V18.1.0 (2024-03)3GPP TS 38.331 V18.1.0 (2024-03)

[0006] Non-patent document 1 describes the technical specifications for Delay Status Reporting (DSR). DSR is used by terminal equipment to provide base station equipment with the delay status (or delay information) of a Logical Channel Group (LCG). The DSR includes information about the remaining time and information about the buffer size as the delay status.

[0007] XR operates under various requirements, including low latency. Considering this, DSR enhancements have been proposed. However, Non-Patent Document 1 does not describe the configuration and / or procedures when the DSR is enhanced. Therefore, the inventors have identified a problem: terminal devices may not be able to properly generate or transmit the enhanced DSR. This problem can also occur in ordinary terminal devices other than those implementing XR.

[0008] This disclosure provides a technology that enables a terminal device to appropriately generate or transmit an extended DSR.

[0009] The terminal device in this disclosure includes: a receiving unit that receives a Radio Resource Control (RRC) message containing information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR) and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; a control unit that, if the first remaining time threshold is set for a Logical Channel Group (LCG), triggers the DSR for a Logical Channel (LCH) belonging to the LCG based on the first remaining time threshold; and a transmitting unit that, if the DSR is triggered and the list of second remaining time thresholds is set, transmits a DSR MAC CE (Medium Access Control Control Element). The DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG. The amount of data indicated by the buffer size field associated with the smallest threshold in the list of second remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data.

[0010] The method of a terminal device in this disclosure includes receiving a Radio Resource Control (RRC) message containing information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; triggering the DSR for a Logical Channel (LCH) belonging to a Logical Channel Group (LCG) based on the first remaining time threshold if the first remaining time threshold is set for the LCG; and transmitting a DSR MAC CE (Medium Access Control Control Element) if the DSR is triggered and the list of second remaining time thresholds is set. The DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG. The amount of data indicated by the buffer size field associated with the smallest threshold in the list of second remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data.

[0011] The base station device in this disclosure includes a transmitting unit (221) that transmits a Radio Resource Control (RRC) message including information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR) and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; and a receiving unit (222) that receives a DSR MAC CE (Medium Access Control Control Element) from a terminal device (10) when the DSR is triggered for a Logical Channel Group (LCG) based on the first remaining time threshold set for the LCG, and the list of second remaining time thresholds is set. The DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG. The amount of data indicated by the buffer size field associated with the smallest threshold in the list of second remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data.

[0012] With the above configuration, the terminal device can appropriately generate or transmit the extended DSR. In addition, other effects may be achieved in lieu of or in conjunction with the above effect.

[0013] The above-mentioned and other purposes, features and advantages of this disclosure will be further clarified by the following detailed description with reference to the attached drawings. The drawings are as follows: Figure 1 is a diagram showing the communication system S; Figure 2 is a diagram showing the U-plane protocol stack; Figure 3 is a diagram showing the C-plane protocol stack; Figure 4 is a block diagram showing the schematic hardware configuration of the terminal device 10; Figure 5 is a block diagram showing the schematic functional configuration of the terminal device 10; Figure 6 is a block diagram showing the schematic hardware configuration of the base station device 20; Figure 7 is a block diagram showing the schematic functional configuration of the base station device 20; Figure 8 is a diagram showing the radio frame configuration; and Figure 9 is a short BSR (Buffer Status) diagram. Figure 10 shows the configuration of a long BSR, Figure 11 shows an example of a BSR table (i.e., the first table), Figure 12 shows an example of an additional BSR table (i.e., the second table), Figure 13 shows the configuration of a refined long BSR, Figure 14 is a sequence diagram showing the processing flow of terminal device 10 and base station device 20, Figure 15 is a diagram illustrating an example of delay critical UL data related to a discard timer, and Figure 16 shows a DSR (Delay Status) Figure 17 is a diagram showing the configuration of the Reporting), Figure 18 is a diagram showing an example of data buffered in each LCG, Figure 19 is a diagram showing an example of the configuration of the second DSR, Figure 20 is a diagram showing an example of data buffered in LCG1 and specific data, Figure 21 is a diagram showing an example of the configuration of the second DSR, Figure 22 is a diagram showing an example of the configuration of the second DSR, Figure 23 is a diagram showing an example of the configuration of the second DSR, Figure 24 is a diagram showing an example of the configuration of the second DSR, Figure 25 is a diagram showing an example of the configuration of the second DSR, Figure 26 is a diagram showing an example of the configuration of the second DSR, and Figure 27 is a diagram showing an example of the configuration of the second DSR.

[0014] Embodiments of this disclosure will be described in detail below with reference to the attached drawings. In this specification and in the drawings, elements that can be similarly described are denoted by the same reference numerals, and redundant descriptions can be omitted.

[0015] The embodiments described below are merely examples of configurations that can realize this disclosure. Each of the embodiments below can be modified or changed as appropriate depending on the configuration of the apparatus to which this disclosure applies and various conditions. Not all combinations of elements included in each of the embodiments below are essential to realize this disclosure, and some elements can be omitted as appropriate. Therefore, the scope of this disclosure is not limited to the configurations described in each of the embodiments below. Configurations combining multiple configurations described in the embodiments below can also be adopted, as long as they are not contradictory.

[0016] 1. First Embodiment 1.1. Communication System As shown in Figure 1, the communication system S comprises one or more terminal devices 10, one or more base station devices 20, and a core network 30. The communication system S is configured according to predetermined technical specifications. For example, the communication system S may conform to the technical specifications defined by 3GPP (e.g., 5G, 5G Advanced, 6G, etc.).

[0017] In communication system S, the user plane, where user data is transmitted and received, and the control plane, where control data is transmitted and received, are configured separately. In other words, communication system S supports C / U separation. The user plane is abbreviated as the U plane, and the control plane is abbreviated as the C plane.

[0018] The terminal device 10 is a device that communicates wirelessly with the base station device 20, and may be, for example, user equipment (UE) that operates in accordance with the 3GPP 5G NR technical specifications. Alternatively, the terminal device 10 may be a device that conforms to other older or newer 3GPP technical specifications.

[0019] The terminal device 10 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a notebook PC, a communication module, a communication card, or an IoT device such as a surveillance camera or a robot. The terminal device 10 may be a vehicle (e.g., a car, a train, etc.) or a device installed therein. The terminal device 10 may be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device installed therein. The terminal device 10 may be a sensor or a device installed thereon. The terminal device 10 may also be called by other names such as terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, wireless station, wireless terminal, wireless device, wireless unit, remote station, remote terminal, remote device, remote unit, etc. The terminal device 10 is preferably a device adapted to one or more of the following: enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC).

[0020] The base station device 20 manages at least one cell. A cell constitutes the smallest unit of a communication area. For example, one cell belongs to one frequency (e.g., a carrier frequency) and consists of one component carrier. The term "cell" may represent a radio communication resource, or it may represent the communication target of the terminal device 10. The base station device 20 communicates wirelessly with the terminal device 10 located within its cell in the U-plane and C-plane. In other words, the base station device 20 terminates the U-plane protocol and the C-plane protocol for the terminal device 10.

[0021] The base station device 20 communicates with the core network 30 in the U-plane and C-plane. More specifically, the core network 30 includes multiple logical nodes, including an Access and Mobility Management Function (AMF) and a User Plane Function (UPF). The base station device 20 connects to the AMF in the C-plane and to the UPF in the U-plane.

[0022] The base station equipment 20 may, for example, be a gNB that provides the terminal equipment 10 with U-planes and C-planes in accordance with the 3GPP 5G NR technical specifications and connects to the 3GPP 5GC (5G Core Network). Alternatively, the base station equipment 20 may be equipment that conforms to other older or newer 3GPP technical specifications.

[0023] The base station device 20 may be composed of multiple unit devices. For example, the base station device 20 may be composed of a Central Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0024] A Radio Access Network (RAN) is formed by the interconnection of multiple base station devices 20. The Radio Access Network formed by base station devices 20 that are gNBs may be referred to as an NG-RAN. A base station device 20 that is a gNB may be referred to as an NG-RAN node.

[0025] Multiple base station devices 20 are connected to each other by a predetermined interface (e.g., an Xn interface). More specifically, for example, multiple base station devices 20 are connected to each other by an Xn-U interface in the U-plane and by an Xn-C interface in the C-plane. Alternatively, multiple base station devices 20 may be connected to each other by other interfaces with different functions or names.

[0026] Each base station device 20 is connected to the core network 30 by a predetermined interface (for example, an NG interface). More specifically, for example, each base station device 20 is connected to the UPF of the core network 30 by an NG-U interface in the U-plane and to the AMF of the core network 30 by an NG-C interface in the C-plane. Alternatively, each base station device 20 may be connected to the core network 30 by other interfaces with different functions or names.

[0027] Referring to Figure 2, the wireless protocol architecture between the terminal device 10 and the base station device 20 will be described. Furthermore, referring to Figure 3, the wireless protocol architecture between the terminal device 10 and the base station device 20 and between the terminal device 10 and the core network 30 will be described.

[0028] As shown in Figure 2, the U-plane protocol stack consists of the following layers, from bottom to top: the Physical (PHY) layer, the MAC (Medium Access Control) layer, the Radio Link Control (RLC) layer, the Packet Data Convergence Protocol (PDCP) layer, and the Service Data Adaptation Protocol (SDAP) layer. Each of these layers is terminated on the network side by the base station equipment 20.

[0029] As shown in Figure 3, the C-plane protocol stack is structured as follows, from the bottom up: Physical (PHY) layer, MAC (Medium Access Control) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Non-Access Stratum (NAS). Each of the above layers, except for the Non-Access Stratum, is terminated at the base station equipment 20 on the network side. The Non-Access Stratum is terminated at the AMF of the core network 30 on the network side.

[0030] As shown in Figure 4, the terminal device 10 has a processor 101, memory 102, input / output interface 103, wireless interface 104, and antenna 105 as hardware elements. The above elements provided in the terminal device 10 are interconnected by an internal bus. Note that the terminal device 10 may have hardware elements other than those shown in Figure 4.

[0031] The processor 101 is an arithmetic element that realizes various functions of the terminal device 10. The processor 101 may be a System-on-a-Chip (SoC) that includes elements such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a memory controller.

[0032] Memory 102 is composed of at least one storage medium, such as RAM (Random Access Memory) or eMMC (embedded Multi Media Card). Memory 102 is an element that temporarily or permanently stores programs and data used to perform various processes in the terminal device 10. The programs include one or more instructions for the operation of the terminal device 10. The processor 101 realizes the functions of the terminal device 10 by loading the programs stored in memory 102 into memory 102 and / or system memory (not shown) and executing them.

[0033] The input / output interface 103 is an interface that receives operations to the terminal device 10 and supplies them to the processor 101, as well as presenting various information to the user. The input / output interface 103 is, for example, a touch panel.

[0034] The wireless interface 104 is a circuit that performs various signal processing to realize wireless communication, and includes a baseband processor and an RF circuit. The wireless interface 104 transmits and receives wireless signals to and from the base station device 20 via the antenna 105.

[0035] As shown in Figure 5, the terminal device 10 has a control unit 110 and a communication unit 120 as functional blocks. The communication unit 120 has at least one transmitting unit 121 and at least one receiving unit 122.

[0036] The control unit 110 may include at least one processor 101 and at least one memory 102. In other words, the control unit 110 may be implemented by the processor 101 and the memory 102. The control unit 110 performs various control processes in the terminal device 10. For example, the control unit 110 controls wireless communication with the base station device 20 via the communication unit 120. That is, the control unit 110 sends and receives data / information / messages via the communication unit 120.

[0037] The communication unit 120 includes a wireless interface 104 and an antenna 105. In other words, the communication unit 120 is implemented by the wireless interface 104 and the antenna 105. The communication unit 120 communicates wirelessly with the base station device 20 by sending and receiving wireless signals to and from the base station device 20. Two or more wireless interfaces 104 and two or more antennas 105 may be included in the communication unit 120.

[0038] When the control unit 110 operates, various processes of the terminal device 10 are executed.

[0039] As shown in FIG. 6, the base station apparatus 20 includes, as hardware elements, a processor 201, a memory 202, a network interface 203, a radio interface 204, and an antenna 205. The above elements provided in the base station apparatus 20 are interconnected by an internal bus. Note that the base station apparatus 20 may have hardware elements other than those shown in FIG. 6.

[0040] The processor 201 is an arithmetic element that realizes various functions of the base station apparatus 20. The processor 201 may be a CPU, and may further include other processors such as a GPU.

[0041] The memory 202 is composed of at least one storage medium such as a ROM (Read Only Memory), a RAM, a HDD (Hard Disk Drive), or a SSD (Solid State Drive). The memory 202 is an element that temporarily or permanently stores programs and data used to execute various processes in the base station apparatus 20. The above program includes one or more instructions for the operation of the base station apparatus 20. The processor 201 realizes the functions of the base station apparatus 20 by expanding and executing the program stored in the memory 202 in the memory 202 and / or a system memory not shown.

[0042] The network interface 203 is an interface used to transmit and receive signals to and from other base station apparatuses 20 and the core network 30.

[0043] The radio interface 204 is a circuit that executes various signal processes for realizing radio communication, and includes a baseband processor and an RF circuit. The radio interface 204 transmits and receives radio signals to and from the terminal device 10 via the antenna 205.

[0044] As shown in FIG. 7, the base station apparatus 20 includes, as functional blocks, a control unit 210, a communication unit 220, and a network communication unit 230. The communication unit 220 includes at least one transmission unit 221 and at least one reception unit 222.

[0045] The control unit 210 may include at least one processor 201 and at least one memory 202. In other words, the control unit 210 may be implemented by the processor 201 and the memory 202. The control unit 210 executes various control processes in the base station device 20. For example, the control unit 210 controls the wireless communication with the terminal device 10 via the communication unit 220. That is, the control unit 210 transmits and receives data / information / messages via the communication unit 220. Also, for example, the control unit 210 controls the communication with other nodes (e.g., other base station devices 20, nodes of the core network 30) via the network communication unit 230.

[0046] The communication unit 220 includes a wireless interface 204 and an antenna 205. In other words, the communication unit 220 is implemented by the wireless interface 204 and the antenna 205. The communication unit 220 wirelessly communicates with the terminal device 10 by transmitting and receiving wireless signals to and from the terminal device 10. Two or more wireless interfaces 204 and two or more antennas 205 may be included in the communication unit 220.

[0047] The network communication unit 230 includes a network interface 203. In other words, the network communication unit 230 is implemented by the network interface 203. The network interface 203 transmits and receives signals to and from a network (and thus the other nodes described above).

[0048] By operating the control unit 210, various processes of the base station device 20 are executed.

[0049] 1.2. Wireless Resources The terminal device 10 and the base station device 20 wirelessly communicate with each other using wireless resources in the frequency domain and the time domain. Hereinafter, the wireless resources will be described.

[0050] The transmission method for downlink communication from the base station equipment 20 to the terminal equipment 10 is, for example, orthogonal frequency division multiplexing (OFDM) using a cyclic prefix (CP), i.e., CP-OFDM. The transmission method for uplink communication from the terminal equipment 10 to the base station equipment 20 is, for example, the CP-OFDM described above, or DFTS-OFDM, in which CP-OFDM is applied after transform precoding that performs discrete Fourier transform (DFT) spreading.

[0051] A cyclic prefix is ​​a redundant signal that functions as a guard period (GP) to prevent inter-symbol and inter-carrier interference, and is inserted at the beginning of an OFDM symbol. There are two types of cyclic prefixes: normal cyclic prefixes and extended cyclic prefixes.

[0052] In OFDM, multiple mutually orthogonal subcarriers are used as the frequency domain radio resource. These multiple subcarriers are arranged in the frequency domain at a predetermined subcarrier spacing (SCS) Δf. Multiple subcarrier spacings Δf can be applied in a communication system S. The subcarrier spacing Δf can be expressed, for example, by the following equation: Δf = 2 μ 15 [kHz]

[0053] Here, μ is a non-negative integer that can take at least one of the values ​​0, 1, 2, 3, 4, 5, or 6. Therefore, the subcarrier interval Δf [kHz] can take at least one of the values ​​15, 30, 60, 120, 240, 480, or 960. Note that μ may also take a value of 7 or greater.

[0054] In the time domain of OFDM, a hierarchical radio frame structure is used, as shown in Figure 8. One radio frame contains 10 subframes. Subframes are assigned subframe numbers that count up from 0 to 9 in increments of 1. One radio frame is divided into two half frames. The time length of a radio frame is 10 ms, the time length of a half frame is 5 ms, and the time length of a subframe is 1 ms. These time lengths do not depend on the subcarrier interval Δf.

[0055] A subframe contains one or more slots (slot(s)). The number of slots Ns in a subframe depends on the value of μ mentioned above, and consequently, the subcarrier interval Δf. The number of slots Ns can be expressed, for example, by the following formula: Ns = 2 μ

[0056] A single slot contains multiple symbols. The number of symbols a slot contains depends on the type of cyclic prefix used. For example, when a standard cyclic prefix is ​​used, a single slot contains 14 symbols. For example, when an extended cyclic prefix is ​​used, a single slot contains 12 symbols.

[0057] As described above, the number of slots and symbols contained in each of the wireless frames, half frames, and subframes, which have a fixed time length, are variable. Therefore, the time length of the slots and the time length of the symbols are also variable.

[0058] A Resource Element (RE) is a time-frequency domain radio resource unit consisting of one subcarrier and one symbol. A Resource Block (RB) is a time-frequency domain radio resource unit consisting of twelve subcarriers and multiple symbols.

[0059] Each wireless frame is assigned a System Frame Number (SFN), which counts up from 0 to 1023 in increments of 1. SFN "0" corresponds to the initial value of the SFN, and SFN "1023" corresponds to the maximum value of the SFN. Therefore, the wireless frame following a wireless frame assigned SFN 1023 will be assigned SFN 0. Since the duration of a wireless frame is 10 ms, the duration of one cycle of the System Frame Number is 10240 ms (= 10.24 seconds).

[0060] Here, the base station device 20 may configure one or more serving cells for the terminal device 10. The serving cells may correspond to component carriers in the downlink and / or component carriers in the uplink. The technique in which one or more serving cells are configured and the base station device 20 and the terminal device 10 perform wireless communication may also be called carrier aggregation.

[0061] Furthermore, the base station device 20 may set one or more bandwidth parts (BWPs) for each of one or more serving cells to the terminal device 10. For example, a downlink bandwidth part (DownLink Bandwidth Part, DL-BWP) may be set for the downlink of one serving cell. Also, an uplink bandwidth part (UpLink Bandwidth Part, UL-BWP) may be set for the uplink of one serving cell. Herein, DL-BWP may include an initial DL-BWP and / or a dedicated DL-BWP. Similarly, UL-BWP may include an initial UL-BWP and / or a dedicated UL-BWP. Hereinafter, BWP may include DL-BWP and / or UL-BWP.

[0062] 1.3. The channel, the control information terminal device 10, and the base station device 20 transmit and receive user data and control information to and from each other. The transmission and reception of control information on the downlink and uplink are illustrated below.

[0063] The terminal device 10 and the base station device 20 transmit and receive user data and control information using a hierarchical array of channels. A physical channel is a channel used for physical communication between the terminal device 10 and the base station device 20. Examples of physical channels include the Physical Downlink Control Channel (PDCCH), the Physical Broadcast Channel (PBCH), and the Physical Uplink Control Channel (PUCCH).

[0064] A transport channel is a channel located above a physical channel and is mapped to a physical channel in the PHY layer. Multiple transport channels may be mapped to a single physical channel. Examples of transport channels include DownLink Shared Channels (DL-SCH) and UpLink Shared Channels (UL-SCH). For example, data on a downlink may also be referred to as DL-SCH data. Similarly, data on an uplink may also be referred to as UL-SCH data. Here, DL-SCH data includes user data on the downlink, and UL-SCH data includes user data on the uplink.

[0065] A logical channel is a channel located above a transport channel and is mapped to a transport channel in the MAC layer. Multiple logical channels may be mapped to one transport channel, and one logical channel may be mapped to multiple transport channels. Logical channels are classified according to the characteristics of the information they transmit. Examples of logical channels include Broadcast Control Channels (BCCH), Common Control Channels (CCCH), and Dedicated Control Channels (DCCH).

[0066] The base station device 20 transmits Downlink Control Information (DCI) to the terminal device 10 using the physical channel PDCCH. The DCI includes information regarding resource allocation for the downlink and uplink to the terminal device 10, as well as control information for the terminal device 10. The DCI is mapped to the PDCCH and corresponds to Layer 1 signaling.

[0067] Here, one or more formats may be specified for the transmission of DCI in a PDCCH. A format specified for the transmission of DCI in a PDCCH may be called a DCI format. For example, a DCI format may include a DCI format used for scheduling a Physical Downlink Shared Channel (PDSCH) (e.g., formats referred to as DCI format 1_0, DCI format 1_1, and / or DCI format 1_2). Also, for example, a DCI format may include a DCI format used for scheduling a Physical Uplink Shared Channel (PUSCH) (e.g., formats referred to as DCI format 0_0, DCI format 0_1, and / or DCI format 0_2). Furthermore, a DCI format may include a DCI format not used for scheduling PDSCH and / or PUSCH. A DCI format used for scheduling PDSCH and / or PUSCH may be called a scheduling DCI format. A DCI format not used for scheduling PDSCH and / or PUSCH may be referred to as a non-scheduling DCI format. Hereafter, for ease of explanation, "DCI format" may be simply referred to as "PDCCH." Also, "DCI generated according to the DCI format" may be simply referred to as "DCI format."

[0068] For example, the base station device 20 may configure frequency domain resources and / or time domain resources for the terminal device 10 to monitor (i.e., monitor) a set of candidate PDCCHs. For example, the frequency domain resources for which the terminal device 10 monitors a set of candidate PDCCHs may be called a control resource set (CORESET). The time domain resources for which the terminal device 10 monitors a set of candidate PDCCHs may be called a search space set (SSS). The terminal device 10 may monitor a set of candidate PDCCHs in one or more CORESETs in the DL-BWP of the serving cell where PDCCH monitoring is configured, according to the corresponding search space set. Here, monitoring may imply attempting to decode each of the PDCCH candidates according to the DCI format being monitored. This configuration may be called blind decoding.

[0069] Here, a Cyclic Redundancy Check (CRC) scrambled by an RNTI (Radio Network Temporary Identifier) ​​may be added to the DCI (or DCI format) transmitted via PDCCH. The CRC may also be called a CRC parity bit. Several types of RNTIs are defined. For example, the base station device 20 may set each RNTI by transmitting an RRC message that includes at least one of the following: information indicating a C-RNTI (Cell-RNTI), information indicating an MCS-C-RNTI (Modulation and Coding Scheme Cell-RNTI), and information indicating a CS-RNTI (Configured Scheduling-RNTI). That is, a CRC scrambled by at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI may be added to the DCI (or DCI format) transmitted via PDCCH.

[0070] The terminal device 10 may monitor (and / or receive) the PDCCH and detect (and / or receive) the DCI format.

[0071] The terminal device 10 transmits Uplink Control Information (UCI) to the base station device 20 using the physical channel PUCCH. The UCI includes control information such as scheduling requests (SR), hybrid automatic repeat requests (HARQ) Ack / Nack, and channel state information (CSI). The UCI is mapped to PUCCH or PUSCH and corresponds to Layer 1 signaling.

[0072] The base station device 20 transmits MAC layer control elements (CEs) to the terminal device 10 using the transport channel DL-SCH. The MAC CEs on the downlink are mapped to the PDSCH via DL-SCH, which corresponds to Layer 2 signaling.

[0073] The terminal device 10 transmits MAC layer control elements (CEs) to the base station device 20 using the transport channel UL-SCH. The uplink MAC CEs include control information such as buffer status reports (BSRs). The uplink MAC CEs are mapped to PUSCH via UL-SCH and correspond to Layer 2 signaling.

[0074] The base station device 20 transmits (or broadcasts) system information (SI) to the terminal device 10 using a logical channel called BCCH. SI includes minimum system information (MSI) and other system information (OSI). MSI includes a master information block (MIB) and system information block 1 (SIB1). SIB1 may be called remaining minimum system information (RMSI). OSI includes system information blocks other than SIB1 (SIB2 and so). Of the BCCH, MIB is mapped to PBCH via BCH (Broadcast Channel), and SIB is mapped to PDSCH via DL-SCH.

[0075] The base station device 20 transmits control information in the RRC layer to the terminal device 10 using a signaling radio bearer (SRB) established between the base station device 20 and the terminal device 10 in the RRC layer. Hereinafter, messages exchanged between the base station device 20 and the terminal device 10 in the RRC layer may be referred to as RRC messages. Multiple types of SRBs exist (e.g., SRB0, SRB1, SRB2, SRB3, SRB4). In addition to RRC messages, SRBs are used to send and receive NAS messages, which include control information in the NAS layer. CCCH or DCCH is used to transmit RRC messages from the base station device 20 to the terminal device 10. CCCH and DCCH are mapped to PDSCH via DL-SCH, respectively. RRC messages correspond to Layer 3 signaling.

[0076] As an example of a downlink RRC message, the RRC Reconfiguration message will be described. The RRC Reconfiguration message is an RRC message transmitted from the base station equipment 20 to the terminal equipment 10 using SRB1 or SRB3. DCCH is used to transmit the RRC Reconfiguration message. The RRC Reconfiguration message is used to reconfigure or modify the connection between the base station equipment 20 and the terminal equipment 10.

[0077] The terminal device 10 transmits RRC messages to the base station device 20 using the SRB described above. CCCH or DCCH is used to transmit RRC messages from the terminal device 10 to the base station device 20. CCCH and DCCH are mapped to PUSCH via UL-SCH, respectively. RRC messages correspond to Layer 3 signaling.

[0078] As an example of an uplink RRC message, the User Equipment Capability Information (UECapabilityInformation) message will be described. The User Equipment Capability Information message is an RRC message transmitted from the terminal device 10 to the base station device 20 using the SRB1. DCCH is used to transmit the User Equipment Capability Information message. The User Equipment Capability Information message is used to notify the base station device 20 of information regarding the radio access capability of the terminal device 10.

[0079] As an example of an uplink RRC message, a User Equipment Assistance Information (UEAssistanceInformation, UAI) message will be described. A UAI message is an RRC message transmitted from the terminal device 10 to the base station device 20 using SRB1 or SRB3. DCCH is used to transmit UAI messages. UAI messages are used to notify the base station device 20 of various information (e.g., UE assistance information) regarding the terminal device 10.

[0080] 1.4. Uplink Scheduling 1.4.1. Scheduling Request (SR) An SR is used by the terminal device 10 to request the allocation of a PUCCH radio resource from the base station device 20. An SR may also be used to request a UL-SCH resource for initial transmission. The base station device 20 allocates a PUCCH resource to the terminal device 10 for sending the SR. The base station device 20 sends an RRC message containing the parameters of the SR to the terminal device 10. The parameters of the SR are included in a SchedulingRequestResourceConfig IE, which is an example of an Information Element (IE) of the RRC.

[0081] The terminal device 10 transmits a UCI including an SR to the base station device 20 using the configured PUCCH resources. The terminal device 10 may transmit the UCI on demand. The terminal device 10 may transmit the UCI at a configured periodicity. For example, the terminal device 10 may transmit an SR set to "0" (negative SR) and / or an SR set to "1" (positive SR). The base station device 20 allocates PUCCH radio resources to the terminal device 10 according to the SR.

[0082] 1.4.2. Dynamic Grant (DG) DG is a scheduling method for allocating radio resources for PUSCH according to the uplink grant procedure. The base station device 20 transmits an uplink grant to the terminal device 10 using PDCCH. The terminal device 10 transmits PUSCH according to the uplink grant. For example, the base station device 20 may allocate radio resources for PUSCH using a DCI format with CRC scrambled by C-RNTI and / or MCS-C-RNTI (i.e., a DCI format used for scheduling PUSCH), and the terminal device 10 may perform uplink transmission using the allocated radio resources for PUSCH. Here, the New Data Indicator to be included in the DCI format with CRC scrambled by C-RNTI and / or MCS-C-RNTI may be set to 0 or 1. Furthermore, the base station device 20 may allocate radio resources for the PUSCH using a DCI format with CRC scrambled by CS-RNTI (i.e., a DCI format used for scheduling the PUSCH), and the terminal device 10 may perform uplink transmission using the allocated radio resources for the PUSCH. Here, the new data indicator to be included in the DCI format with CRC scrambled by CS-RNTI may be set to 1.

[0083] 1.4.3. Configured Grant (CG) CG is a scheduling method for allocating PUSCH radio resources without the dynamic uplink grant procedure described above. There are two types of CG: Type 1 and Type 2. The base station device 20 sends an RRC message containing the CG parameters to the terminal device 10. The CG parameters are included in ConfiguredGrantConfig IE, which is an example of an RRC information element (IE). ConfiguredGrantConfig IE includes a parameter periodicity related to the transmission period using PUSCH. The parameter periodicity is set in units of slots or symbols. Alternatively, the parameter periodicity may be set in units of frames per second (FPS). In Type 1, the terminal device 10 starts transmitting signals at the set period without a DCI trigger. In Type 2, the base station device 20 sends DCI scrambled with CS-RNTI to the terminal device 10. CS-RNTI is used to activate periodic transmission. In response to the activation by DCI scrambled by CS-RNTI, terminal device 10 starts transmitting using PUSCH at a set period.

[0084] 1.5. Logical Channel Prioritization (LCP) The terminal device 10 generates a MAC PDU (Medium Access Control Protocol Data Unit) for uplink transmission according to the uplink grant from the base station device 20. When a new transmission is performed, the terminal device 10 multiplexes data from multiple different logical channels (LCHs) to generate a MAC PDU. At this time, the terminal device 10 generates the MAC PDU according to LCP. LCP is a priority process for multiplexing data from multiple different LCHs.

[0085] For example, the base station device 20 may send an RRC message containing parameters related to LCP to the terminal device 10. For example, the RRC message may include a LogicalChannelConfig IE. The terminal device 10 may generate a MAC PDU based on the LogicalChannelConfig IE included in the RRC message. The LogicalChannelConfig IE may include the following parameters: priority: A value in the range of 1 to 16, representing priority. The smaller the value of the parameter priority, the higher the priority. Hereafter, this priority will be referred to as "LCH priority" to distinguish it from other priorities. In the following description, the expression "a relatively small value of the parameter priority" may be rephrased as "a relatively high LCH priority." The expression "a relatively large value of the parameter priority" may be rephrased as "a relatively low LCH priority." prioritizedBitRate (PBR): Represents the preferred bitrate. bucketSizeDuration (BSD): Represents the bucket size duration. The bucket size is determined by PBR × BSD.

[0086] In LCP, the base station device 20 can set mapping restrictions on the terminal device 10.

[0087] The terminal device 10 may perform the above mapping restriction based on the LogicalChannelConfig IE included in the RRC message. The LogicalChannelConfig IE may include at least one of the following parameters described in Section 5.4.3.1.1 of Non-Patent Literature 1: allowedSCS-List: Represents the allowed subcarrier interval for transmission. maxPUSCH-Duration: Represents the allowed maximum PUSCH duration for transmission. configuredGrantType1Allowed: Represents whether type 1 of the CG can be used for transmission. allowedServingCells: Represents the allowed cells for transmission. allowedCG-List: Represents the allowed CGs for transmission. allowedPHY-PriorityIndex: Represents the allowed PHY priority index of the DG for transmission. allowedHARQ-mode: Represents the allowed uplink HARQ mode for transmission.

[0088] For example, if an allowedCG-List is set for an LCH, the terminal device 10 can map the data of that LCH only to the MAC PDU corresponding to the CG included in the allowedCG-List.

[0089] For example, when a new transmission is performed, the MAC entity of terminal device 10 may select an LCH that satisfies the conditions indicated by the mapping constraints, in accordance with section 5.4.3.1.2 of Non-Patent Document 1.

[0090] Subsequently, the MAC entity allocates resources to the selected LCHs in order of LCH priority (i.e., in order of decreasing parameter priority). For example, the MAC entity allocates the amount of data prioritized by the PBR for each LCH to resources within the MAC PDU in order of LCH priority. If there are still resources available within the MAC PDU after all LCHs have been allocated data prioritized by the PBR, the MAC entity allocates the LCH data to the available resources within the MAC PDU in order of LCH priority. The terminal device 10 continues to perform the above procedure until all LCH data is depleted or all available resources within the MAC PDU are depleted.

[0091] More specifically, the MAC entity of terminal device 10 may allocate resources to the selected LCH in accordance with section 5.4.3.1.3 of Non-Patent Document 1. The MAC entity of terminal device 10 may perform the following processes (a1) to (a3).

[0092] (a1) For example, the MAC entity allocates resources to multiple LCHs selected for an uplink grant where Bj > 0, in order of LCH priority. If the PBR of an LCH is set to infinity, the MAC entity allocates resources to all data that can be transmitted on that LCH before satisfying the PBR of the LCH with a lower LCH priority.

[0093] Bj is a variable used in terminal device 10 in LCP. The subscript j here is used for mapping to LCH. Bj is maintained for each LCHj. When an LCH is established, the MAC entity initializes Bj of that LCHj to zero. With respect to LCHj, the MAC entity increments Bj by PBR × T before each instance of LCP, where T is the time elapsed since Bj was last incremented. If Bj is larger than the bucket size (i.e., PBR × BSD), the MAC entity sets Bj to the bucket size.

[0094] (a2) The MAC entity decrements Bj by the total size of the MAC SDUs (Service Data Units) served to LCHj.

[0095] (a3) If resources are available, all selected LCHs are served in order of LCH priority. That is, the MAC entity allocates the remaining data from all selected LCHs to resources in order of LCH priority. Regardless of the value of Bj, the MAC entity will continue to allocate the remaining data to resources until either the data for that LCH runs out or the uplink grant resources run out.

[0096] 1.6. Extended Reality (eXtended Reality, XR) This section describes the characteristics of traffic generated in XR. In XR, multiple types of data (video data, audio data, user data, control data, etc.) are transmitted and received in parallel. Each of the multiple data streams corresponding to the above data has different traffic characteristics and QoS requirements.

[0097] The timing of sending and receiving the above data may experience time shifts, which can be described as jitter, variability, or fluctuation, due to factors such as video and audio encoding and network delays.

[0098] Reference 1 states that the following definitions may be introduced regarding transmission and reception in XR. [Reference 1] 3GPP TR 23.700-60 V1.1.0 (2022-09)

[0099] PDU Set: A set of one or more PDUs that carry a payload of a single unit of information generated at the application level. The application level mentioned above corresponds, for example, to a frame or video slice in an XR service. Data Burst: A set of datamultiple PDUs generated and transmitted by an application over a short period of time. The PDUs in a PDU set may correspond to PDCP SDUs (Service Data Units).

[0100] Furthermore, in XR, the Packet Delay Budget (PDB) requirement is being considered as one of the above QoS requirements. PDB is the upper bound of the packet delay time that is permissible between the terminal device 10 and the UPF. Reference 1 also states that the following new QoS parameters may be introduced: PDU-Set Delay Budget (PSDB): The upper bound of the PDU set delay time that is permissible between the terminal device 10 and the UPF. PDU-Set Error Rate (PSER): The upper bound of the error rate calculated between a PDU set processed by the sender and all PDUs in a PDU set that were not successfully delivered to the upper layer of the corresponding receiver.

[0101] 1.7. Buffer Status Reporting (BSR) The terminal device 10 transmits a BSR by MAC signaling using the allocated PUSCH radio resources. The BSR consists of MAC CEs included in the MAC PDU. The BSR is used to indicate information about the buffer status of uplink data in the MAC entity. Based on the BSR, the base station device 20 allocates radio resources for the uplink to the terminal device 10.

[0102] In the BSR, LCHs are assigned to logical channel groups (LCGs). Each LCG contains one or more LCHs. The terminal device 10 calculates the buffer size for uplink data for each LCG. The terminal device 10 transmits the buffer size corresponding to each LCG to the base station device 20 as the BSR.

[0103] The base station device 20 transmits an RRC message containing BSR parameters to the terminal device 10. The BSR parameters are included in a BSR-Config IE, which is an example of an RRC information element (IE). For example, the BSR-Config IE includes three timers: periodicBSR-Timer, retxBSR-Timer, and logicalChannelSR-DelayTimer.

[0104] Furthermore, parameters related to the LCG are included in the LogicalChannelConfig IE, which is an example of an RRC information element (IE). That is, the base station device 20 may send an RRC message containing the LogicalChannelConfig IE to the terminal device 10. The terminal device 10 may also identify settings related to the LCH and / or LCG based on the LogicalChannelConfig IE included in the RRC message. For example, the LogicalChannelConfig IE includes a logicalChannelGroup IE. The logicalChannelGroup IE assigns the LCH to the LCG. For example, an LCG index (ID) may be set for each of one or more LCHs, and the LCG to which the one or more LCHs belong may be set. Note that the LogicalChannelConfig IE may include a logicalChannelGroupIAB-Ext IE. The logicalChannelGroupIAB-Ext IE applies only to IAB-MT (Integrated Access Backhaul-Mobile Termination). If the logicalChannelGroupIAB-Ext IE is set, the LogicalChannelConfig IE is ignored.

[0105] Terminal device 10 may trigger BSR according to predetermined conditions. For example, terminal device 10 may trigger BSR for an activated cell group when any of the following conditions (b1) to (b4) are met. The following conditions may also be referred to as "events". (b1) With respect to an LCH belonging to a certain LCG, uplink data becomes available in the MAC entity, and one of the following two conditions is met: - The above uplink data belongs to an LCH that has a higher LCH priority than an LCH belonging to any LCG that contains available uplink data. - There is no LCH belonging to any LCG that contains available uplink data. (b2) Uplink resources are allocated, and the number of padding bits is equal to or greater than the size of the BSR MAC CE and its subheader combined. (b3) The retxBSR-Timer expires, and at least one LCH belonging to an LCG contains uplink data. (b4) The periodicBSR-Timer expires.

[0106] The BSR includes at least a Regular BSR, a Padding BSR, and a Periodic BSR. The Regular BSR, Padding BSR, and Periodic BSR may be triggered based on different conditions. For example, terminal device 10 triggers the Regular BSR when either of the above conditions (b1) and (b3) is met. Terminal device 10 triggers the Padding BSR when the above condition (b2) is met. Terminal device 10 triggers the Periodic BSR when the above condition (b4) is met.

[0107] Furthermore, with respect to a BSR triggered by the expiration of the retxBSR-Timer, the terminal device 10 may consider the LCH that triggered the BSR to be the LCH with the highest LCH priority that has data available for transmission at the time the BSR was triggered.

[0108] A BSR includes multiple formats, including at least a short BSR and a long BSR. A MAC PDU containing a BSR includes a MAC subheader, which includes a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID). The value of the LCID or eLCID may be called a Codepoint. The Codepoint value identifies the format of the BSR.

[0109] A short BSR is a format for reporting the buffer status (i.e., buffer size) of a single LCG. As shown in Figure 9, a short BSR includes one field 900 having a fixed size of 8 bits. Field 900 includes a first part 910 and a second part 920.

[0110] The first portion 910 consists of 3 bits. The first portion 910 is information for identifying the LCG on which the buffer status is reported. The first portion 910 is sometimes referred to as the "LCG ID field".

[0111] The second portion 920 consists of 5 bits. The second portion 920 is information for identifying the total amount of data available in all LCHs included in the LCG indicated by the first portion 910. The second portion 920 is sometimes simply referred to as the "buffer size". The second portion 920 indicates an index indicating the number of bytes. The terminal device 10 refers to a predetermined BSR table and sets the second portion 920 to the index corresponding to the buffer size. The BSR table has 32 index values ​​(for example, also referred to as "code points"). For example, the second portion 920 indicates one of the values ​​from 0 to 31. The value of each index corresponds to a range of buffer sizes. That is, the above BSR table defines the correspondence between the index and the range of buffer sizes. The smaller the index value, the smaller the buffer size corresponding to that index value. The larger the index value, the larger the buffer size corresponding to that index value.

[0112] Short BSR may also include the Truncated format, which is a format for padded BSR, and the Extended format, which is a format that can transmit more information.

[0113] A long BSR is a format for reporting the buffer status (i.e., buffer size) of multiple LCGs. As shown in Figure 10, a long BSR has a variable size. A long BSR includes an LCG field 1010 and a buffer size field 1020.

[0114] The LCG field 1010 consists of 8 bits. In the LCG field 1010, each of the 8 bits corresponds to 8 LCGi. Here, i is an integer from 0 to 7. The definition of i remains the same in the following explanation. The LCG field 1010 may also indicate whether a buffer size field exists for LCGi. For example, if the value of LCGi in the LCG field 1010 is 1, this indicates that a buffer size field corresponding to LCGi exists. If the value of LCGi is 0, this indicates that a buffer size field corresponding to LCGi does not exist.

[0115] The number of fields included in the buffer size field 1020 is variable depending on the value of the LCG field 1010. Assume that in the LCG field 1010, the bit corresponding to LCG1 is 1 and the bit corresponding to LCG2 is 1. Therefore, the buffer size field 1020 includes field 1021 corresponding to LCG1 and field 1022 corresponding to LCG2. Note that in Figure 10, it is assumed that the bit corresponding to LCG0 is 0, so the buffer size field 1020 does not include the field corresponding to LCG0.

[0116] Each field in the buffer size field 1020 consists of 8 bits. Each field indicates the buffer size to be reported (e.g., the size of the data available for transmission). Each field indicates an index showing the number of bytes.

[0117] The terminal device 10 refers to the BSR table 1100 shown in Figure 11 and sets the buffer size field 1020 to the index corresponding to the buffer size.

[0118] The BSR table 1100 has 255 index values ​​(also referred to as "code points"). The index values ​​range from 0 to 254. Each index value corresponds to a range of buffer sizes. That is, the BSR table 1100 defines the correspondence between indexes and buffer size ranges. The smaller the index value, the smaller the buffer size corresponding to that index value. The larger the index value, the larger the buffer size corresponding to that index value. Furthermore, the range of buffer sizes corresponding to each of the 255 index values ​​is defined according to a predetermined exponential function. Therefore, the larger the index value, the larger the range of buffer sizes corresponding to that index value.

[0119] Furthermore, the BSR may include a refined long BSR as a format to accommodate XR traffic. An additional BSR table 1200, shown in Figure 12, may be defined for the refined long BSR. Hereafter, the BSR table 1100 in Figure 11 will be referred to as the "first table 1100," and the BSR table 1200 in Figure 12 will be referred to as the "second table 1200."

[0120] The second table 1200, like the first table 1100, is a table for an 8-bit buffer status field. Therefore, the second table 1200 may have 256 index values. The index may be a value between 0 and 255. Each index value may correspond to a range of buffer sizes. That is, the second table 1200 may define a correspondence between an index and a range of buffer sizes. For example, the smaller the index value, the smaller the buffer size corresponding to that index value. The larger the index value, the larger the buffer size corresponding to that index value. Furthermore, the range of buffer sizes corresponding to each of the 256 index values ​​may be defined according to a predetermined exponential function.

[0121] Furthermore, the range and / or granularity of the second table 1200 differ from those defined in the first table 1100. Here, the range of the second table 1200 may mean the range between the minimum and maximum buffer sizes in the second table 1200. Also, the granularity of the second table 1200 may mean the degree of fineness or coarseness of the division width when the range of the second table 1200 is divided by the number of indexes (for example, 256). Note that if the range of each buffer size corresponding to the index value is defined according to a predetermined exponential function, the larger the index value, the larger the division width (i.e., the range of the buffer size) corresponding to that index value may be.

[0122] For example, the range of the second table 1200 may be narrower than the range of the first table 1100. That is, the range narrower than the first table 1100 may be divided into 256 parts, and index values ​​may be assigned to each divided range. Therefore, the granularity of the second table 1200 may be finer than that of the first table 1100.

[0123] The base station device 20 may send an RRC message to the terminal device 10 that includes parameters for the second table 1200. These parameters may be included in a MAC-CellGroupConfig IE, which is an example of an RRC information element (IE). For example, these parameters may be included in additionalBS-TableAllowed, which is included in MAC-CellGroupConfig IE.

[0124] `additionalBS-TableAllowed` may also be "information indicating whether the terminal device 10 is allowed to use the second table 1200 for the LCG." For example, `additionalBS-TableAllowed` is a bit sequence (i.e., a bitmap) containing multiple bits. For example, the leftmost bit corresponds to LCG ID "0". The second bit from the left corresponds to LCG ID "1". If the value of the bit is 1, this may indicate that the terminal device 10 is allowed to use the second table 1200 in addition to the first table 1100 when reporting the buffer size of the LCG corresponding to that bit. If the value of the bit is 0, this may indicate that the terminal device 10 is not allowed to use the second table 1200 when reporting the buffer size of the LCG corresponding to that bit. That is, if the value of the bit is 0, this may indicate that only the first table 1100 is to be used when reporting the buffer size of the LCG corresponding to that bit.

[0125] As shown in Figure 13, the refined long BSR includes an LCG field 1310, a BT field 1320, and a buffer size field 1330.

[0126] The LCG field 1310 consists of 8 bits. The LCG field 1310 has the same configuration as the LCG field 1010 in Figure 10. The LCG field 1310 may also indicate whether a buffer size field for LCGi exists.

[0127] The BT field 1320 consists of 8 bits. The BT field 1320 exists only when the value of the corresponding LCG field 1310 is set to 1; otherwise, it is "reserved". Each bit of the BT field 1320 indicates which table was used for the buffer size field 1330 for LCGi. That is, the value of BTi indicates whether the first table 1100 or the second table 1200 was used to indicate the buffer size of LCGi. If the value of BTi is 0, this may indicate that the first table 1100 was used to indicate the buffer size of LCGi. If the value of BTi is 1, this may indicate that the second table 1200 was used to indicate the buffer size of LCGi.

[0128] The number of fields included in the buffer size field 1330 is variable depending on the value of the LCG field 1310. Assume that in the LCG field 1310, the bit corresponding to LCG1 is 1 and the bit corresponding to LCG2 is 1. Therefore, the buffer size field 1330 includes field 1331 corresponding to LCG1 and field 1332 corresponding to LCG2. Note that in Figure 13, it is assumed that the bit corresponding to LCG0 is 0, so the buffer size field 1330 does not include the field corresponding to LCG0.

[0129] Furthermore, we assume that in the BT field 1320, the bit of BT1 corresponding to LCG1 is 0, and the bit of BT2 corresponding to LCG2 is 1. Therefore, the field 1331 corresponding to LCG1 is set by referring to the first table 1100. Also, the field 1332 corresponding to LCG2 is set by referring to the second table 1200.

[0130] The MAC PDU may also include identification information to determine whether the BSR is a refined long BSR. For example, the MAC subheader may include an LCID or eLCID value (i.e., a code point). An LCID or eLCID value may be defined to indicate that the BSR is a refined long BSR.

[0131] Furthermore, like short BSRs, long BSRs may include both Truncated and Extended formats.

[0132] Furthermore, BSR may include the Pre-emptive BSR format and the Extended Pre-emptive BSR format. These formats are used in IAB-MT.

[0133] For regular BSRs and periodic BSRs, a MAC entity whose logicalChannelGroup-IABExt IE is configured by a higher layer may choose to use a long BSR, an extended long BSR, or an extended short BSR, as follows: (c1) When a MAC PDU containing a BSR is built, if two or more LCGs have data available for transmission: (c2) If the maximum value of the LCG IDs in the configured LCGs is 7 or less: The terminal device 10 transmits (or reports) a long BSR for all LCGs that have data available. (c2) Otherwise: The terminal device 10 transmits (or reports) an extended long BSR for all LCGs that have data available. (c1) Otherwise, the terminal device 10 transmits (or reports) an extended short BSR.

[0134] Furthermore, in the case of regular BSRs and periodic BSRs, MAC entities for which logicalChannelGroup-IABExt IE is not set by a higher layer may choose one of short BSRs, long BSRs, or refined long BSRs as follows: (d1) If, for at least one LCG with additionalBS-TableAllowed set, the amount of UL data available for transmission is within the buffer size indicated by the second table 1200: The terminal device 10 transmits (or reports) refined long BSRs for all LCGs that have data available for transmission. (d1) Otherwise: (d2) If, when a MAC PDU containing BSRs is constructed, two or more LCGs have data available for transmission: The terminal device 10 transmits (or reports) long BSRs for all LCGs that have data available. (d2) If not, and one LCG has available data, and additionalBS-TableAllowed is set, and a MAC PDU containing BSRs is constructed, and the amount of UL data available for transmission is greater than the largest buffer size indicated in the second table 1200: The terminal device 10 transmits (or reports) a long BSR. (d2) Otherwise: The terminal device 10 transmits (or reports) a short BSR.

[0135] In addition, in the case of padding BSR, terminal device 10 may transmit any of the following BSR formats according to the conditions that are met: • Short BSR • Long BSR • Short Truncated BSR • Long Truncated BSR • Extended Short BSR • Extended Long BSR • Extended Short Truncated BSR • Extended Long Truncated BSR • Refined Long BSR

[0136] For example, in the case of a padded BSR, a MAC entity for which logicalChannelGroup-IABExt IE is not set by a higher layer may select the BSR format as follows: (e1) If the number of padding bits is equal to or greater than the combined size of the short BSR and its subheader, and less than the combined size of the long BSR and its subheader: (e2) If, when the BSR is constructed, two or more LCGs have data available for transmission: (e3) If the number of padding bits is equal to the combined size of the short BSR and its subheader: The terminal device 10 transmits (or reports) a short Truncated BSR of the LCG that includes the LCH with the highest LCH priority among the LCHs that have data available for transmission. (e3) Otherwise: The terminal device 10 transmits (or reports) long Truncated BSRs for each LCG, in descending order of the LCH having the highest LCH priority, regardless of whether the LCH has data available for transmission or not. If the LCH priorities are the same, the terminal device 10 transmits (or reports) long Truncated BSRs in ascending order of LCG ID. (e2) Otherwise: The terminal device 10 transmits (or reports) short BSRs. (e1) If otherwise, and with respect to at least one LCG for which additionalBS-TableAllowed is set, the amount of UL data available for transmission is within the range of the buffer size indicated in the second table 1200, and the number of padding bits is equal to or greater than the combined size of the refined long BSR and its subheader: The terminal device 10 transmits (or reports) the refined long BSR for all LCGs that have data available for transmission.(e1) If not, and the number of padding bits is equal to or greater than the combined size of the long BSR and its subheader: The terminal device 10 transmits (or reports) the long BSR for all LCGs that have data available for transmission.

[0137] For example, in the case of a padded BSR, a MAC entity in which logicalChannelGroup-IABExt IE is set by a higher layer may select the BSR format as follows: (f1) When the number of padding bits is equal to or greater than the combined size of an Extended Short BSR and its subheader, and less than the combined size of an Extended Long BSR and its subheader: (f2) When the BSR is constructed, two or more LCGs have data available for transmission: (f3) When the number of padding bits is less than the combined size of an Extended Long Truncated BSR with a buffer size field of zero and its subheader: The terminal device 10 transmits (or reports) an Extended Short Truncated BSR of an LCG that includes the LCH with the highest LCH priority among the LCHs that have data available for transmission. (f3) Otherwise: The terminal device 10 transmits (or reports) Extended Long Truncated BSRs for each LCG, in descending order of the LCH priority with respect to whether or not each LCG has data available for transmission, regardless of whether or not it has data available for transmission. If the priorities are the same, the terminal device 10 transmits (or reports) Extended Long Truncated BSRs in ascending order of LCG ID. (f2) Otherwise: The terminal device 10 transmits (or reports) Extended Short BSRs. (f1) Otherwise, if the number of padding bits is equal to or greater than the combined size of the Extended Long BSR and its subheader: The terminal device 10 transmits (or reports) Extended Long BSRs for all LCGs that have data available for transmission.

[0138] As described above, the terminal device 10 may select the BSR format based on the number of padding bits and the LCH priority.

[0139] The following describes the procedure by which the terminal device 10 transmits BSR MAC CE to the base station device 20.

[0140] As shown in Figure 14, the communication unit 220 of the base station device 20 transmits an RRC message to the terminal device 10 (S1401). The RRC message includes parameters related to BSR. The RRC message may also be an RRC Reconfiguration message.

[0141] The control unit 110 of the terminal device 10 triggers a BSR based on the parameters included in the RRC message. For example, the control unit 110 triggers a BSR based on at least one of the above conditions (b1) to (b4). The communication unit 120 of the terminal device 10 transmits a BSR (S1402). The control unit 210 of the base station device 20 allocates radio resources to the terminal device 10 based on the BSR.

[0142] 1.8. Delay Status Reporting (DSR) The terminal device 10 transmits a DSR by MAC signaling using the radio resources of the allocated PUSCH. The DSR consists of MAC CEs included in the MAC PDU. The DSR is used by the terminal device 10 to provide the LCG delay status to the base station device 20. Based on the DSR, the base station device 20 allocates radio resources for the uplink to the terminal device 10.

[0143] The terminal device 10 reports a delay status (or delay information) for each LCG in the DSR. The delay status may include the remaining time until a predetermined deadline is reached. For example, the remaining time may be the remaining time of the PDCP discard timer.

[0144] The base station device 20 transmits an RRC message containing parameters related to DSR to the terminal device 10. For example, the information regarding the PDCP discard timer may be included in a PDCP-Config IE, which is an example of an RRC information element (IE). The PDCP discard timer may be set for a Data Radio Bearer (DRB). The PDCP entity of the terminal device 10 may start the PDCP discard timer associated with the PDCP SDU based on the receipt of the PDCP SDU from the upper layer.

[0145] Furthermore, parameters related to DSR may be included in the MAC-CellGroupConfig IE, which is an example of an RRC information element (IE). For example, the MAC-CellGroupConfig IE contains information for triggering DSR. Specifically, the MAC-CellGroupConfig IE may include remainingTimeThreshold. remainingTimeThreshold may be set for each LCG. Specifically, remainingTimeThreshold may be set in association with the LCG ID. remainingTimeThreshold may be a threshold used for the remaining time mentioned above to trigger DSR for LCHs belonging to a certain LCG.

[0146] The MAC entity of terminal device 10 may trigger a DSR if the LCG is configured for a DSR as follows: The MAC entity may trigger a DSR for each LCH belonging to the LCG when both of the following conditions (g1) and (g2) are met: (g1) The shortest remaining time of the running PDCP discard timer for all data buffered in the LCH or LCG (i.e., PDCP SDUs) that has not been transmitted by any MAC PDU and / or reported as data volume in the DSR MAC CE is less than the remainingTimeThreshold set for the LCH or LCG. (g2) There are no pending DSRs for the LCH or LCG.

[0147] If a DSR is triggered, the DSR may be considered pending until it is canceled. A MAC entity may cancel a pending DSR if all PDCP SDUs associated with the pending DSR are discarded, or if a MAC PDU is sent that includes either all PDCP SDUs associated with the DSR or a DSR MAC CE containing delay information for all PDCP SDUs associated with the DSR. Here, a PDCP SDU that has not been sent to any MAC PDU and is a delayed critical PDCP SDU associated with the LCH or LCG that triggered the DSR may be considered associated with the DSR.

[0148] If there is at least one pending DSR, the MAC entity may instruct the UL-SCH resource to generate a DSR MAC CE if it is available for a new transmission and can accommodate the DSR MAC CE and its subheader. Alternatively, if there is at least one pending DSR, the MAC entity may trigger an SR if it is not available for a new transmission or cannot accommodate the DSR MAC CE and its subheader, and there are no pending SRs (i.e., scheduling requests) already triggered by the same LCH's DSR procedure. Alternatively, if there is at least one pending DSR, the MAC entity may trigger an SR if there are no pending SRs already triggered by the same LCH's DSR procedure and the MAC entity has a CG set.

[0149] Furthermore, the terminal device 10 may report a predetermined data size for each LCG in the DSR. For example, this predetermined data may be the size of data with a short remaining time, and may be referred to as "Delay-Critical UL data".

[0150] For a given LCG, the amount of delayed critical UL data may be calculated for the corresponding PDCP entity and RLC entity as follows:

[0151] A PDCP entity may calculate the amount of delayed critical PDCP data considering the following (h1) to (h5): (h1) Delayed critical PDCP SDU for which no PDCP data PDU has been constructed; (h2) PDCP data PDU containing a delayed critical PDCP SDU and not transmitted to a lower layer; (h3) PDCP control PDU; (h4) PDCP SDU retransmitted in AM DRB; (h5) PDCP data PDU retransmitted in AM DRB.

[0152] If pdu-SetDiscard is not set, a delayed critical PDCP SDU is a PDCP SDU whose remaining time until the PDCP discard timer expires is less than remainingTimeThreshold. pdu-SetDiscard is a parameter that indicates whether the terminal device 10 performs PDU set-based discard processing on the PDCP entity. pdu-SetDiscard may be included in PDCP-Config IE. If pdu-SetDiscard is set, a delayed critical PDCP SDU is a PDCP SDU belonging to a PDU set whose remaining time until the PDCP discard timer expires is less than remainingTimeThreshold for at least one PDCP SDU. Note that AM DRB is a data radio bearer that uses RLC AM (Acknowledge Mode).

[0153] An RLC entity may calculate the amount of delayed critical RLC data by considering the following (i1) to (i4): (i1) Delayed critical RLC SDU or delayed critical RLC SDU segment not included in the RLC data PDU; (i2) RLC data PDU containing a delayed critical RLC SDU or delayed critical RLC SDU segment and pending for initial transmission; (i3) RLC data PDU pending for retransmission in the RLC AM; (i4) RLC control PDU (e.g., STATUS PDU).

[0154] A delayed-critical RLC SDU is an RLC SDU that corresponds to a PDCP PDU that has been identified as "delayed-critical" by the PDCP. If a PDCP entity has become a delayed-critical PDCP SDU and the corresponding PDCP data PDU has already been sent to a lower layer, the PDCP entity may indicate to the lower layer (i.e., the RLC layer) that the PDCP data PDU is delayed-critical.

[0155] As shown in Figure 15, a PDCP SDU in which the remaining time of the PDCP discard timer is less than the remainingTimeThreshold may be considered a delayed critical PDCP SDU. A PDCP data PDU that includes a delayed critical PDCP SDU and has not been transmitted to a lower layer may also be considered delayed critical UL data. A PDCP entity may show an RLC entity a PDU that includes a PDCP SDU in which the remaining time of the PDCP discard timer is less than the remainingTimeThreshold, and such PDU may be considered a delayed critical RLC SDU. A PDU that includes a delayed critical RLC SDU may also be considered delayed critical UL data.

[0156] For example, terminal device 10 may transmit the DSR MAC CE shown in Figure 16. As shown in Figure 16, the DSR MAC CE includes an LCG field 1610 and a delay information field 1620.

[0157] The LCG field 1610 consists of 8 bits. In the LCG field 1610, each of the 8 bits corresponds to 8 LCGi. The LCG field 1610 may indicate whether delay information for LCGi (i.e., remaining time and buffer size, described later) exists in the delay information field 1620. For example, if the value of LCGi in the LCG field 1610 is 1, this may indicate that delay information for LCGi exists in the delay information field 1620. That is, this may indicate that delay information for LCGi will be reported. If the value of LCGi is 0, this may indicate that delay information for LCGi does not exist in the delay information field 1620. That is, this may indicate that delay information for LCGi will not be reported.

[0158] The number of fields included in the delay information field 1620 is variable depending on the value of the LCG field 1610. Assume that in the LCG field 1610, the bit corresponding to LCG1 is 1 and the bit corresponding to LCG2 is 1. Therefore, the delay information field 1620 includes a set of fields 1630 corresponding to LCG1. The set of fields 1630 includes a first field 1631 and a second field 1632. Furthermore, the delay information field 1620 includes a set of fields 1640 corresponding to LCG2. The set of fields 1640 includes a first field 1641 and a second field 1642. Assume that in the LCG field 1610, the bit corresponding to LCG0 is 0. Therefore, the delay information field 1620 does not include a set of fields corresponding to LCG0.

[0159] The following describes the set of fields 1630 corresponding to LCG1. The first field 1631 includes at least a first portion 1631a and a second portion 1631b. In the first field 1631, "R" is the reserved bit.

[0160] The first portion 1631a consists of one bit. The first portion 1631a exists only if additionalBS-TableAllowed is set for the corresponding LCG and the buffer size indicated by the corresponding second field 1632 is not zero. Otherwise, the first portion 1631a may be "reserved" or set to 0. If the first portion 1631a exists, it may indicate which of the first table 1100 and the second table 1200 was used to indicate the buffer size of LCG1. That is, the first portion 1631a may indicate which of the first table 1100 and the second table 1200 set the second field 1632. If the value of the first portion 1631a is 0, this may indicate that the first table 1100 was used to set the second field 1632. If the value of the first portion 1631a is 1, this may indicate that the second table 1200 was used to set the second field 1632.

[0161] The second portion 1631b consists of 6 bits. The second portion 1631b represents the remaining time for the data corresponding to LCG1. More specifically, the second portion 1631b may indicate the shortest remaining time of the running PDCP discard timer at the time of the first symbol of the first transmission of the PUSCH containing the DSR MAC CE, among all PDCP SDUs not transmitted by any MAC PDU.

[0162] The second field 1632 consists of 8 bits. The second field 1632 indicates the total amount of delayed critical UL data for LCG1. If additionalBS-TableAllowed is set and the buffer size (i.e., the total amount of delayed critical UL data) is within the range of the buffer size indicated by the second table 1200, the MAC entity sets the second field 1632 using the second table 1200. Otherwise, the MAC entity sets the second field 1632 using the first table 1100.

[0163] The set of fields 1640 corresponding to LCG2 has the same configuration as the set of fields 1630 corresponding to LCG1. The first field 1641 has the same configuration as the first field 1631. The first field 1641 includes at least a first portion 1641a and a second portion 1641b. For example, the first portion 1641a indicates whether the second field 1642 was set in the first table 1100 or the second table 1200. For example, the second portion 1641b represents the remaining time for the data corresponding to LCG2. The second field 1642 has the same configuration as the second field 1632. For example, the second field 1642 indicates the total amount of delayed critical UL data for LCG2.

[0164] The MAC PDU may also include identification information to determine whether it is a DSR MAC CE. For example, the MAC subheader may include an LCID or eLCID value indicating that it is a DSR MAC CE.

[0165] The following describes the procedure by which the terminal device 10 transmits DSR MAC CE to the base station device 20.

[0166] As shown in Figure 17, the communication unit 220 of the base station device 20 transmits an RRC message to the terminal device 10 (S1701). The RRC message includes parameters related to DSR. The RRC message may also be an RRC Reconfiguration message.

[0167] The control unit 110 of the terminal device 10 triggers a DSR based on the parameters included in the RRC message. For example, if an LCG is set up for a DSR, the control unit 110 triggers a DSR for each LCH belonging to that LCG when both (g1) and (g2) above are satisfied. The control unit 110 generates the DSR shown in Figure 16. The communication unit 120 of the terminal device 10 transmits the DSR (S1702).

[0168] The control unit 210 of the base station device 20 allocates radio resources to the terminal device 10 based on the DSR. The control unit 210 may determine the degree of delay based on the delay information included in the DSR. For example, the control unit 210 may determine the degree of delay based on the remaining time and the amount of delay-critical UL data. Based on the degree of delay, the control unit 210 may allocate radio resources for uplink communication from the terminal device 10.

[0169] 1.9. Specific Data The data (h1) and (h2) above in the PDCP layer are considered delayed critical UL data based on the remaining time of the PDCP discard timer. The data (i1) and (i2) above in the RLC layer also correspond to data indicated as delayed critical by the PDCP layer and can be said to be data associated with the PDCP discard timer. Such data considered delayed critical in relation to (or based on) the PDCP discard timer may be referred to as "first data".

[0170] On the other hand, the data (h3) to (h5) above in the PDCP layer are considered delayed critical UL data regardless of the remaining time of the PDCP discard timer. Similarly, the data (i3) to (i4) above in the RLC layer are also considered delayed critical UL data regardless of instructions from the PDCP layer (i.e., regardless of the remaining time of the PDCP discard timer). Hereafter, the data (h3) to (h5) and the data (i3) to (i4) above will be collectively referred to as "specific data". Specific data may also be referred to as "delayed critical UL data not associated with the PDCP discard timer". Furthermore, specific data may be referred to as "second data" to distinguish it from the first data described above.

[0171] The specific data may include at least one of the following (j1) to (j3) and (k1) to (k2).

[0172] PDCP Layer: (j1) PDCP Control PDU. For example, the PDCP Control PDU may include a PDCP Status Report and a PDCP Sequence Number Gap Report. (j2) PDCP SDU retransmitted when the upper layer requests PDCP entity re-establishment and / or uplink data switching in the case of AM DRB. (j3) PDCP Data PDU retransmitted when the upper layer requests PDCP data recovery from the radio bearer in the case of AM DRB. The PDCP Data PDU may be all PDCP Data PDUs sent to a re-established or released AM RLC entity that have not been confirmed to have been successfully delivered by the lower layer.

[0173] RLC layer: (k1) RLC data PDUs held for retransmission in the RLC AM. For example, the RLC data PDU may be data that is considered to be subject to retransmission, as indicated by the status PDU as Nack. (k2) RLC control PDU. For example, the RLC control PDU may be a STATUS PDU.

[0174] Hereafter, at least one of the above (j1) to (j3) in the PDCP layer may be referred to as the "first specific data." Also, at least one of the above (k1) to (k2) in the RLC layer may be referred to as the "second specific data."

[0175] 1.10. DSR Enhancement XR operates under various requirements, including low latency requirements. In consideration of this, terminal device 10 may transmit an enhanced DSR. Hereafter, the existing DSR shown in Figure 16 will be referred to as the "first DSR". In contrast, in this embodiment, terminal device 10 may transmit (or generate) a DSR MAC CE that is different from the first DSR. Hereafter, the DSR MAC CE may be referred to as the "second DSR" or "enhanced DSR". The second DSR may include information not included in the first DSR. In one example, the second DSR may include the information included in the first DSR described in Figure 16, plus additional information.

[0176] For example, the second DSR may include multiple pairs of remaining time and buffer size for a single LCG. For this configuration, one or more additional remaining time thresholds may be set. Hereafter, remainingTimeThreshold will be referred to as the "first remaining time threshold." The above-mentioned "additional remaining time thresholds" will be referred to as the "second remaining time threshold."

[0177] The first remaining time threshold may be the threshold used to trigger a DSR, and may be referred to as the "triggering threshold." One first remaining time threshold may be set for each LCG.

[0178] The second remaining time threshold may be a threshold used to report pairs of remaining time and buffer size (e.g., additional pairs), and may be referred to as a "reporting threshold." One or more second remaining time thresholds may be set for each LCG.

[0179] As shown in Figure 18, a first remaining time threshold and one or more second remaining time thresholds may be set for each LCG. In the example in Figure 18, a first remaining time threshold Th1a and three second remaining time thresholds Th2a, Th2b, and Th2c are set for LCG1. Similarly, a first remaining time threshold Th1a and three second remaining time thresholds Th2a, Th2b, and Th2c are set for LCG2. In this example, Th1a > Th2a > Th2b > Th2c. Therefore, the first remaining time threshold Th1a may be referred to as "the largest remaining time threshold among the first remaining time threshold and one or more second remaining time thresholds." The second remaining time threshold Th2a may be referred to as "the largest remaining time threshold among the second remaining time thresholds." The second remaining time threshold Th2c may also be referred to as "the smallest remaining time threshold among the first remaining time threshold and one or more second remaining time thresholds" or "the smallest remaining time threshold among the second remaining time thresholds."

[0180] In the example in Figure 18, the first remaining time threshold Th1a is the largest of the first and second remaining time thresholds, but the example is not limited to this. For example, the first remaining time threshold Th1a may be set within the range between the second remaining time threshold Th2a and the second remaining time threshold Th2c. The first remaining time threshold Th1a may be smaller than the second remaining time threshold Th2c. Alternatively, the first remaining time threshold Th1a may be set to a value equal to any of the second remaining time thresholds Th2a, Th2b, and Th2c. Furthermore, in the example in Figure 18, three second remaining time thresholds are set for LCG1 and LCG2, but the example is not limited to this. For example, two second remaining time thresholds may be set for each LCG. Alternatively, for example, a different number of second remaining time thresholds may be set for each LCG.

[0181] The data buffered in LCG1 and LCG2 is divided into multiple parts based on a first remaining time threshold Th1a and three second remaining time thresholds Th2a, Th2b, and Th2c. For example, the data is divided into the following portions: • Data where the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a • Data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2a and greater than or equal to the second remaining time threshold Th2b • Data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2b and greater than or equal to the second remaining time threshold Th2c • Data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c

[0182] With respect to LCG1, data 1801 is data where the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a. Data 1801 may be considered delayed critical UL data. The control unit 110 may consider data 1801 to be data reported by the second DSR. The size of data 1801 is X1. Furthermore, the remaining time of data 1801 (e.g., the shortest remaining time of the running PDCP discard timer) is T1.

[0183] With respect to LCG1, there is no data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2a and greater than or equal to the second remaining time threshold Th2b. With respect to LCG1, the control unit 100 may consider that there is no data reported by the second DSR within the range defined by the second remaining time threshold Th2a and the second remaining time threshold Th2b.

[0184] With respect to LCG1, data 1802 is data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2b and greater than or equal to the second remaining time threshold Th2c. Data 1802 may be considered delayed critical UL data. The control unit 110 may consider data 1802 to be data reported by the second DSR. The size of data 1802 is X2. Furthermore, the remaining time of data 1802 (e.g., the shortest remaining time of the running PDCP discard timer) is T2.

[0185] With respect to LCG1, there is no data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c. With respect to LCG1, the control unit 100 may assume that there is no data reported by the second DSR within the range of less than the second remaining time threshold Th2c.

[0186] With respect to LCG2, there is no data where the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a. With respect to LCG2, the control unit 100 may assume that there is no data reported by the second DSR within the range defined by the first remaining time threshold Th1a and the second remaining time threshold Th2a.

[0187] With respect to LCG2, there is no data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2a and greater than or equal to the second remaining time threshold Th2b. With respect to LCG2, the control unit 100 may consider that there is no data reported by the second DSR within the range defined by the second remaining time threshold Th2a and the second remaining time threshold Th2b.

[0188] With respect to LCG2, data 1803 is data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2b and greater than or equal to the second remaining time threshold Th2c. Data 1803 may be considered delayed critical UL data. The control unit 110 may consider data 1803 to be data reported by the second DSR. The size of data 1803 is X3. Furthermore, the remaining time of data 1803 (e.g., the shortest remaining time of the running PDCP discard timer) is T3.

[0189] With respect to LCG2, there is no data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c. With respect to LCG2, the control unit 100 may assume that there is no data reported by the second DSR within the range of less than the second remaining time threshold Th2c.

[0190] In the above example, the terminal device 10 may transmit the DSR MAC CE shown in Figure 19 as a second DSR. As shown in Figure 19, the second DSR includes an LCG field 1910 and a delay information field 1920.

[0191] The LCG field 1910 has the same configuration as the LCG field 1610 in Figure 16. Therefore, a detailed explanation is omitted. Assume that in the LCG field 1910, the bit corresponding to LCG1 is 1 and the bit corresponding to LCG2 is 1. Therefore, the delay information field 1920 includes a set of first fields 1930 corresponding to LCG1, a set of second fields 1940 corresponding to LCG1, and a set of third fields 1950 corresponding to LCG2. Assume that in the LCG field 1910, the bit corresponding to LCG0 is 0. Therefore, the delay information field 1920 does not include a set of fields corresponding to LCG0.

[0192] The first set of fields 1930 corresponds to a first pair of remaining time field and buffer size field corresponding to LCG1. In this example, the first set of fields 1930 includes fields for reporting information about the data 1801 in Figure 18 (i.e., delayed critical UL data). For example, the first set of fields 1930 includes fields 1931 and 1932.

[0193] Field 1931 includes a first portion 1931a, a second portion 1931b, and a third portion 1931c. The first portion 1931a may have the same configuration as the first portion 1631a in Figure 16, and may indicate which of the first table 1100 and the second table 1200 was used to set up field 1932.

[0194] The second portion 1931b may indicate whether there are additional pairs of remaining time and buffer size. The second portion 1931b may be referred to as the "E field". If the second portion 1931b is 1, this may indicate that there are additional pairs of remaining time and buffer size. The second portion 1931b may indicate that there are no more pairs of remaining time and buffer size (i.e., the set of first fields 1930 is the last pair). If the second portion 1931b is 0, this may indicate that the set of first fields 1930 is the last pair with respect to LCG1. In this example, since there is a second set of fields 1940 with respect to LCG1, the second portion 1931b may be 1. The second portion 1931b may also indicate whether there is a certain pair of remaining time and buffer size. The second part 1931b may indicate whether a particular part exists among a plurality of parts that can be divided based on a first remaining time threshold Th1a and three second remaining time thresholds Th2a, Th2b, and Th2c. For example, the second part 1931b may indicate whether there exists data in which the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a.

[0195] The third portion 1931c may indicate the remaining time corresponding to data 1801. In this example, the third portion 1931c may indicate the remaining time T1.

[0196] Field 1932 may indicate the buffer size X1 of data 1801.

[0197] The second set of fields 1940 corresponds to a second pair of remaining time field and buffer size field corresponding to LCG1. In this example, the second set of fields 1940 includes fields for reporting information about the data 1802 in Figure 18 (i.e., delayed critical UL data). For example, the second set of fields 1940 includes fields 1941 and 1942.

[0198] Field 1941 includes a first portion 1941a, a second portion 1941b, and a third portion 1941c. The first portion 1941a may have the same configuration as the first portion 1931a and may indicate which of the first table 1100 and the second table 1200 was used to set up field 1942.

[0199] The second portion 1941b may have the same configuration as the second portion 1931b. In this example, since the set of second fields 1940 is the last pair relating to LCG1, the second portion 1941b may be 0.

[0200] The third portion 1941c may have the same configuration as the third portion 1931c, and may indicate the remaining time corresponding to data 1802. In this example, the third portion 1941c may indicate the remaining time T2.

[0201] Field 1942 may indicate the buffer size X2 for data 1802.

[0202] The third set of fields 1950 corresponds to the first pair of remaining time field and buffer size field corresponding to LCG2. In this example, the third set of fields 1950 includes fields for reporting information about the data 1803 in Figure 18 (i.e., delayed critical UL data). For example, the third set of fields 1950 includes fields 1951 and 1952.

[0203] Field 1951 includes a first part 1951a, a second part 1951b, and a third part 1951c. Field 1951 has the same structure as field 1931. Note that the second part 1951b may be 0, since the set of the third field 1950 is the last pair relating to LCG2. The third part 1951c may indicate the remaining time T3 of data 1803. Field 1952 has the same structure as field 1932. Field 1952 may indicate the buffer size X3 of data 1803.

[0204] According to the above configuration, the terminal device 10 can generate or transmit a second DSR based on a first remaining time threshold and one or more second remaining time thresholds. However, since the above-mentioned specific data is not associated with the PDCP discard timer, the terminal device 10 has the problem that it cannot generate or select an appropriate field for the specific data in the second DSR.

[0205] In relation to the above problem, the control unit 110 of the terminal device 10 may generate or transmit a second DSR as follows.

[0206] Information regarding the first remaining time threshold may be set for the second DSR. Hereafter, the information regarding the first remaining time threshold will be referred to as "first threshold information". The first threshold information may be included in the MAC-CellGroupConfig IE of the RRC message, as described above.

[0207] Furthermore, one or more second remaining time thresholds may be set for each LCH or LCG. A list having one or more second remaining time threshold values ​​may be set. Hereafter, information regarding one or more such second remaining time thresholds will be referred to as "second threshold information". The base station device 20 may include the second threshold information in the RRC message transmitted in S1701 of Figure 17. The second threshold information may be set in an IE associated with the MAC cell group included in the RRC message. An example of such an IE is the MAC-CellGroupConfig IE. The second threshold information may be set for the LCH. The second threshold information may be set in an IE associated with the LCH included in the RRC message. An example of such an IE is the LogicalChannelConfig IE. The second threshold information may be set for the LCG. The second threshold information may be set in association with the LCG ID. The second threshold information may be set in an IE associated with the LCG included in the RRC message. An example of such an IE is the LCG-DSR-Config IE. The base station device 20 may also transmit the second threshold information to the terminal device 10 using at least one of the following: RRC message, MAC CE, and DCI.

[0208] The control unit 110 (e.g., MAC entity) may trigger a DSR for each LCH or LCG based on a first remaining time threshold. For example, the control unit 110 may trigger a DSR based on (g1) and / or (g2) above. More specifically, the control unit 110 may trigger a DSR for each LCH belonging to the LCG when both (g1) and (g2) above are satisfied.

[0209] If a DSR is triggered, the control unit 110 may generate or transmit a first DSR and / or a second DSR based on at least one of the following conditions (l1) and (l2): (l1) There is a UL-SCH resource available for a new transmission, and the UL-SCH resource is capable of accommodating the first and / or second DSR MAC CE and its subheader as a result of LCP. (l2) Configuration information for transmitting the second DSR (hereinafter simply referred to as "configuration information") is set.

[0210] For example, based on (l1) above, the control unit 110 may operate as follows: If there is a UL-SCH resource available for a new transmission and that UL-SCH resource can accommodate a second DSR MAC CE and its subheader as a result of LCP, the control unit 110 may generate or transmit a second DSR. Otherwise, if there is a UL-SCH resource available for a new transmission and that UL-SCH resource can accommodate a first DSR MAC CE and its subheader as a result of LCP, the control unit 110 may generate or transmit a first DSR.

[0211] Regarding (l2), the above setting information may be one or more second remaining time thresholds. That is, the setting information may be second threshold information.

[0212] With respect to (l2), the configuration information may also be information indicating whether or not the terminal device 10 is permitted to report a second DSR. The "information indicating whether or not the terminal device 10 is permitted to report a second DSR" may also be a flag indicating either "the terminal device 10 is permitted to report a second DSR" or "the terminal device 10 is not permitted to report a second DSR". For example, the configuration information may be a flag indicating either "the terminal device 10 is permitted to report a second DSR" or "the terminal device 10 is not permitted to report a second DSR" for a cell group or LCH or LCG. For example, if the configuration information is 1, this may indicate "the terminal device 10 is permitted to report a second DSR". If the configuration information is 0, this may indicate "the terminal device 10 is not permitted to report a second DSR".

[0213] For example, the control unit 110 may operate as follows based on (l2) above: If setting information is set for at least one LCH or LCG, the control unit 110 may generate or transmit a second DSR. Otherwise, the control unit 110 may generate or transmit a first DSR. Also, if setting information is not set for at least one LCH or LCG, the control unit 110 may generate or transmit a first DSR.

[0214] More specifically, if a second threshold information is set for at least one LCH or LCG, the control unit 110 may generate or transmit a second DSR. Otherwise, the control unit 110 may generate or transmit a first DSR. Also, if a second threshold information is not set for at least one LCH or LCG, the control unit 110 may generate or transmit a first DSR.

[0215] The control unit 110 may include at least one of the following pieces of information (m1) to (m5) in the second DSR.

[0216] (m1) The second DSR of the LCG field may include an LCG field. The LCG field may have the same configuration as the LCG field 1610 in Figure 16. That is, the LCG field may consist of 8 bits. In the LCG field, each of the 8 bits may correspond to 8 LCGi. The LCG field may indicate whether delay information for LCGi is included in the second DSR. For example, if the value of LCGi in the LCG field is 1, this may indicate that at least one of the information (m2) to (m5) described later is included in the second DSR with respect to LCGi. If the value of LCGi is 0, this may indicate that at least one of the information (m2) to (m5) is not included in the second DSR with respect to LCGi.

[0217] (m2) Information on buffer size and remaining time pairs The second DSR may include information on buffer size and remaining time pairs. For example, the second DSR may include a field relating to buffer size and remaining time pairs. As described above, this field is referred to as the "E field".

[0218] The E field may be associated with each LCG. The E field may indicate that there are additional pairs of remaining time and buffer size with respect to the associated LCG. That is, the E field may indicate that there are additional pairs of (m4) and (m5) described below with respect to the associated LCG.

[0219] For example, the E field may have the same configuration as the second part 1931b of Figure 19. For example, if the E field is 1, this may indicate that an additional pair of remaining time and buffer size is reported for the relevant LCG. If the E field is 0, this may indicate that no additional pairs of remaining time and buffer size are reported for the relevant LCG. In another example, the E field may indicate that there are no more pairs of remaining time and buffer size for the relevant LCG (i.e., the pair containing the E field is the last pair). In yet another example, the E field may indicate that a particular pair of remaining time and buffer size exists for the relevant LCG. That is, the E field may indicate that the specific pairs of (m4) and (m5) described below exist for the relevant LCG.

[0220] If the above configuration information is not set, or if the configuration information indicates that "the terminal device 10 is not permitted to report a second DSR", the E field may be "reserved" or set to a predetermined value (for example, 0).

[0221] (m3) The second DSR field relating to the buffer size table may include a field indicating which of the first table 1100 and the second table 1200 was used to set (m4) described below. Hereafter, this field will be referred to as the "BT field".

[0222] The BT field may have the same configuration as the first part 1931a of Figure 19. That is, the BT field may consist of 1 bit. The BT field may exist only if additionalBS-TableAllowed is set for the corresponding LCGi and the buffer size indicated by the corresponding buffer size field is not zero. Otherwise, the BT field may be "reserved" or set to 0. If the BT field exists, it may indicate which of the first table 1100 and the second table 1200 was used to set (m4) described later. Note that if the second DSR includes two or more buffer size fields for LCGi, it may also include two or more BT fields for LCGi. That is, the second DSR may include a BT field for each buffer size field.

[0223] One or more BT fields may exist for a given LCG based on the E field. For example, if the E field indicates that no additional pairs of remaining time and buffer size are reported for a given LCG, then one BT field may exist for that LCG. If the E field indicates that additional pairs of remaining time and buffer size are reported for a given LCG, then two or more BT fields may exist for that LCG.

[0224] (m4) Information regarding buffer size The second DSR may include information regarding buffer size. For example, the second DSR may include one or more fields relating to the buffer size for the corresponding LCGi. Hereafter, such fields will be referred to as "buffer size fields".

[0225] The amount of data (or buffer size) indicated by the buffer size field may include the following embodiments m4-1 to m4-5.

[0226] (Aspect m4-1) The buffer size field may indicate the amount of data relating to the corresponding LCGi. For example, the buffer size field may indicate the total amount or a portion of the data available to all LCHs belonging to the corresponding LCGi.

[0227] (Aspect m4-2) The buffer size field may indicate a data amount calculated based on at least one of a first remaining time threshold and a second remaining time threshold. The buffer size field may indicate a data amount having a corresponding remaining time for the PDCP discard timer, based on at least one of the first remaining time threshold and the second remaining time threshold. For example, the buffer size field may indicate a data amount having a remaining time for the PDCP discard timer that falls within the range of remaining times determined based on at least one of the first remaining time threshold and the second remaining time threshold. That is, the buffered data may be divided into multiple parts based on at least one of the first remaining time threshold, the second remaining time threshold, and the remaining time for the data, and the buffer size field may indicate the amount of data in each divided part. For example, the buffer size field may indicate a data amount that satisfies at least one of the following conditions (n1) to (n4): (n1) The remaining time for the PDCP discard timer is below the first remaining time threshold. (n2) The remaining time for the PDCP discard timer is above the first remaining time threshold. (n3) The remaining time of the PDCP discard timer exceeds the second remaining time threshold. (n4) The remaining time of the PDCP discard timer falls below the second remaining time threshold.

[0228] For example, the buffer size field may indicate the amount of data calculated based on two or more combinations selected from a first remaining time threshold and one or more second remaining time thresholds. As shown in the example in Figure 18, the buffer size field may indicate any of the following (o1) to (o4): (o1) The amount of data for which the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a. (o2) The amount of data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2a and greater than or equal to the second remaining time threshold Th2b. (o3) The amount of data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2b and greater than or equal to the second remaining time threshold Th2c. (o4) The amount of data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c.

[0229] (Aspect m4-3) The buffer size field may indicate the total amount of delayed critical UL data calculated based on at least one of (h1) to (h5) and (i1) to (i4) above. In another example, the buffer size field may indicate a portion of the delayed critical UL data calculated based on at least one of (h1) to (h5) and (i1) to (i4) above. For example, the buffer size field may indicate the amount of data that satisfies at least one of the above conditions (n1) to (n4) out of the total amount of delayed critical UL data calculated based on (h1) to (h5) and (i1) to (i4) above. As shown in the example in Figure 18, the buffer size field may indicate any of (o1) to (o4) out of the total amount of delayed critical UL data calculated based on (h1) to (h5) and (i1) to (i4) above. In another example, the buffer size field may represent the total amount of data other than the delayed critical UL data calculated based on at least one of the above (h1) to (h5) and (i1) to (i4). For example, the buffer size field may represent the amount of data that satisfies at least one of the above conditions (n1) to (n4) from the total amount of data other than the delayed critical UL data calculated based on the above (h1) to (h5) and (i1) to (i4). The buffer size field may represent any of the above (o1) to (o4) from the total amount of data other than the delayed critical UL data calculated based on the above (h1) to (h5) and (i1) to (i4).

[0230] (Aspect m4-4) The buffer size field may indicate the total amount of specific data. The total amount of specific data may be the sum of the data (j1) to (j3) and (k1) to (k2) described above. The buffer size field may indicate a portion of the specific data. The amount of a portion of the specific data may be the sum of at least one of the data (j1) to (j3) and (k1) to (k2) described above. The amount of a portion of the specific data may be the sum of the first specific data or the sum of the second specific data. If the specific data includes data associated with the PDCP discard timer, the buffer size field may indicate the amount of data from the total amount of specific data that satisfies at least one of the above conditions (n1) to (n4).

[0231] (Aspect m4-5) The above aspects m4-1 to m4-4 may be combined. That is, the buffer size field may indicate the total amount of data or a portion of the data amount obtained by combining the above aspects m4-1 to m4-4. For example, the buffer size field may indicate the total amount of data or a portion of the data amount for a given LCG based on at least one of a first remaining time threshold and a second remaining time threshold set for that LCG. As another example, the buffer size field may indicate a value that takes into account two or more data amounts selected from the above aspects m4-1 to m4-4. For example, the buffer size field may indicate the sum of two or more data amounts selected from the above aspects m4-1 to m4-4 for a given LCG.

[0232] For example, the second DSR may include one or more buffer size fields for a given LCG based on the E field. For example, if the E field for a given LCG indicates that no additional pairs of remaining time and buffer size are reported, the second DSR may include one buffer size field for that LCG. If the E field for a given LCG indicates that additional pairs of remaining time and buffer size are reported, the second DSR may include two or more buffer size fields for that LCG.

[0233] In another example, the second DSR may always include two or more buffer size fields with respect to LCGi, based on the value of LCGi in the LCG field. For example, if the value of LCGi in the LCG field is 1, the second DSR may include two or more buffer size fields corresponding to LCGi.

[0234] In another example, if the above configuration information is set for a certain LCGi, the second DSR may include two or more buffer size fields for that LCGi.

[0235] In another example, the second DSR may include one or more corresponding buffer size fields based on the fact that data exists in a given LCG having remaining time corresponding to a portion divided based on a first remaining time threshold and / or a second remaining time threshold. Alternatively, the second DSR may include two or more corresponding buffer size fields based on the fact that data exists in a given LCG having remaining time corresponding to two or more portions divided based on a first remaining time threshold and / or a second remaining time threshold, respectively (i.e., buffered).

[0236] In a configuration where the second DSR includes two or more buffer size fields for a given LCG, the two or more buffer size fields may include two or more buffer fields selected from embodiments m4-1 to m4-5.

[0237] (m5) The second DSR field relating to remaining time may include information relating to remaining time. For example, the second DSR may include one or more fields relating to remaining time. Hereafter, such fields will be referred to as the "remaining time field".

[0238] The remaining time field may indicate the remaining time for the data buffered in the corresponding LCGi. For example, the remaining time field may indicate the remaining time based on the running PDCP discard timer for the data buffered in the LCGi.

[0239] For example, the corresponding data may be any of the following (p1) to (p4): (p1) Data buffered in LCGi and not transmitted in any MAC PDU (e.g., PDCP SDU) (p2) Data calculated based on a first remaining time threshold, one or more second remaining time thresholds and at least one of the remaining time (p3) Delay critical UL data calculated based on at least one of the above (h1) to (h5) and (i1) to (i4) (p4) Specific data

[0240] For example, the remaining time field may indicate the remaining time of the data corresponding to the buffer size field of (m4) above. The remaining time field may indicate the remaining time of the data corresponding to any of the buffer size fields of embodiments m4-1 to m4-5 above. Here, if the corresponding buffer size field is embodiment m4-4, the remaining time field may be "reserved" or set to a predetermined value (e.g., 0). The remaining time field may indicate the remaining time of the data corresponding to the paired buffer size field.

[0241] The remaining time field may indicate the shortest (or smallest) remaining time among the running PDCP discard timers in the corresponding data. The remaining time field may indicate the longest (or largeest) remaining time among the running PDCP discard timers in the corresponding data.

[0242] The remaining time field may indicate the remaining time calculated based on the time of the first symbol of the initial transmission of the PUSCH including the second DSR. The remaining time field may indicate the shortest remaining time of the running PDCP discard timer at the time of the first symbol of the initial transmission of the PUSCH including the second DSR.

[0243] For example, the remaining time field may indicate the shortest remaining time of the running PDCP discard timer at the time of the first symbol of the initial transmission of the PUSCH containing the second DSR, among all PDCP SDUs that are buffered in LCGi and have not been transmitted by any MAC PDU.

[0244] For example, the remaining time field may indicate the shortest remaining time of the running PDCP discard timer at the time of the first symbol of the initial transmission of the PUSCH containing the second DSR, among all PDCP SDUs that are buffered in LCGi and have not been transmitted by any MAC PDU, and that satisfy at least one of the above conditions (n1) to (n4). For example, the data that satisfies at least one of the above conditions (n1) to (n4) may be the data in the example in Figure 18. For example, the data that satisfies at least one of the above conditions (n1) to (n4) may be any of (o1) to (o4) above.

[0245] For example, the second DSR may include one or more remaining time fields for a given LCG based on the E field. For example, if the E field for a given LCG indicates that no additional pairs of remaining time and buffer size are reported, the second DSR may include one remaining time field for that LCG. If the E field for a given LCG indicates that additional pairs of remaining time and buffer size are reported, the second DSR may include two or more remaining time fields for that LCG.

[0246] In another example, the second DSR may always include two or more remaining time fields with respect to LCGi, based on the value of LCGi in the LCG field. For example, if the value of LCGi in the LCG field is 1, the second DSR may include two or more remaining time fields corresponding to LCGi.

[0247] In another example, if the above configuration information is set for a certain LCGi, the second DSR may include two or more remaining time fields for that LCGi.

[0248] In another example, the second DSR may include one or more corresponding remaining time fields based on the fact that data exists (i.e., is buffered) in a given LCG having remaining time corresponding to a portion divided based on a first remaining time threshold and / or a second remaining time threshold. Alternatively, the second DSR may include two or more corresponding remaining time fields based on the fact that data exists (i.e., is buffered) in a given LCG having remaining time corresponding to two or more portions divided based on a first remaining time threshold and / or a second remaining time threshold.

[0249] A MAC PDU containing a DSR may include identification information to determine whether the DSR is a first DSR or a second DSR. For example, the first and second DSRs may be identified by a MAC subheader containing an LCID or eLCID value (i.e., a code point). The MAC subheader of a MAC PDU containing a second DSR may include an LCID or eLCID value to identify the second DSR. The LCID or eLCID value for identifying the second DSR may be different from the LCID or eLCID value for identifying the first DSR.

[0250] An LCP priority may be set for the second DSR. The priority of the second DSR may be set to be the same as the priority of the first DSR.

[0251] In the following, the manner in which the terminal device 10 generates or selects fields for specific data in the second DSR will be described. The settings for describing these manners will be described. As shown in Figure 20, a first remaining time threshold and a plurality of second remaining time thresholds are set for LCG1. In Figure 20, the setting of the first remaining time threshold and the plurality of second remaining time thresholds is the same as in the example in Figure 18. A first remaining time threshold Th1a and three second remaining time thresholds Th2a, Th2b, and Th2c are set for LCG1. In this example, Th2a > Th2a > Th2b > Th2c. Also, the data buffered in LCG1 (i.e., data 1801 and data 1802) is the same as in the example in Figure 18, so a detailed explanation is omitted.

[0252] In the example in Figure 20, with respect to LCG1, in addition to data 1801 and data 1802, there is specific data 2001. For example, the size of specific data 2001 is Y1. Specific data 2001 includes a first specific data 2002 and a second specific data 2003. The size of the first specific data 2002 is Y2, and the size of the second specific data 2003 is Y3.

[0253] The following describes each of the three modes q1 to q3 in which the terminal device 10 generates or selects a field for specific data in the second DSR.

[0254] (Aspect q1) The control unit 110 of the terminal device 10 may include individual fields or sets of fields for specific data in the second DSR.

[0255] The control unit 110 may transmit or generate the DSR MAC CE shown in Figure 21 as a second DSR. With respect to the DSR MAC CE shown in Figure 21, the same reference numerals are used for the same components as in Figure 19, thus omitting redundant explanations.

[0256] Assume that the bit corresponding to LCG1 in the LCG field 1910 is 1. Therefore, the delay information field 1920 includes a set of first fields 1930 corresponding to LCG1, a set of second fields 1940 corresponding to LCG1, and a set of third fields 2110 corresponding to LCG1. Assume that the bit corresponding to LCG0 in the LCG field 1910 is 0. Therefore, the delay information field 1920 does not include a set of fields corresponding to LCG0.

[0257] The first set of fields 1930 has the same configuration as the first set of fields 1930 in Figure 19. Since there is a second set of fields 1940 with respect to LCG1, the second portion 1931b (i.e., field E) may be a value (e.g., 1) indicating the existence of an additional pair of remaining time and buffer size. The third portion 1931c may indicate the remaining time corresponding to the data 1801 in Figure 20. In this example, the third portion 1931c may indicate the remaining time T1. Field 1932 may indicate the buffer size X1 of the data 1801.

[0258] The second set of fields 1940 has the same configuration as the second set of fields 1940 in Figure 19. Since there is a third set of fields 2110 with respect to LCG1, the second portion 1941b (i.e., field E) may be a value (e.g., 1) indicating the existence of an additional pair of remaining time and buffer size. The third portion 1941c may indicate the remaining time corresponding to the data 1802 in Figure 20. In this example, the third portion 1941c may indicate the remaining time T2. Field 1942 may indicate the buffer size X2 of the data 1802.

[0259] The third set of fields 2110 may be a set of individual fields for the specific data 2001 in Figure 20. The third set of fields 2110 includes field 2111 and field 2112.

[0260] Field 2111 includes a first portion 2111a, a second portion 2111b, and a third portion 2111c.

[0261] The first portion 2111a may be the field corresponding to (m3) above (i.e., the BT field). The first portion 2111a may indicate which of the first table 1100 and the second table 1200 was used to set up the field 2112.

[0262] The second portion 2111b may be the field corresponding to (m2) above (i.e., the E field). Since the set of third fields 2110 corresponding to LCG1 is the last pair with respect to LCG1, the second portion 2111b may be a value (e.g., 0) indicating that there are no additional pairs of remaining time and buffer size.

[0263] The third portion 2111c included in the set of third fields 2110 for specific data may be "reserved" or set to a predetermined value (for example, 0). In this example, the third portion 2111c is set to 0. If the specific data corresponding to the set of third fields 2110 is data that has remaining time, the third portion 2111c may indicate that remaining time.

[0264] Field 2112 may indicate the buffer size Y1 of the specific data 2001. Field 2112 may indicate the total amount of the specific data or a portion of the specific data. Field 2112 may indicate the total amount of the above-mentioned (j1) to (j3) and (k1) to (k2) data. Field 2112 may indicate the amount of at least one of the above-mentioned (j1) to (j3) and (k1) to (k2) data. For example, field 2112 may indicate the buffer size Y2 of the first specific data 2002 in Figure 20. Field 2112 may indicate the buffer size Y3 of the second specific data 2003 in Figure 20.

[0265] The control unit 110 may include a set of fields for specific data in the second DSR with respect to LCG1. For example, as shown in Figure 22, the delay information field 1920 may include a set of fields 2210 corresponding to the first specific data 2002 and a set of fields 2220 corresponding to the second specific data 2003.

[0266] The field set 2210 includes field 2211 and field 2212. Field 2211 includes a first portion 2211a, a second portion 2211b, and a third portion 2211c. The first portion 2211a may be the field corresponding to (m3) above (i.e., the BT field). The second portion 2211b may be the field corresponding to (m2) above (i.e., the E field). Because the field set 2220 exists, the second portion 2211b may be a value (e.g., 1) indicating the existence of an additional pair of remaining time and buffer size. The third portion 2211c may be set to 0. Field 2212 may indicate the buffer size Y2 of the first specific data 2002.

[0267] The field set 2220 includes field 2221 and field 2222. Field 2221 includes a first portion 2221a, a second portion 2221b, and a third portion 2221c. The first portion 2221a may be the field corresponding to (m3) above (i.e., the BT field). The second portion 2221b may be the field corresponding to (m2) above (i.e., the E field). Since the field set 2220 is the last pair with respect to LCG1, the second portion 2221b may be a value (e.g., 0) indicating that there are no additional pairs of remaining time and buffer size. The third portion 2221c may be set to 0. Field 2222 may indicate the buffer size Y3 of the second specific data 2003.

[0268] The example in Figure 22 shows, but is not limited to, sets of fields 2210 and 2220 corresponding to the first specific data 2002 and the second specific data 2003. Depending on the type or characteristics of the specific data, the specific data may be divided into multiple parts. The second DSR may include multiple buffer size fields indicating the amount of the multiple data parts.

[0269] According to the above configuration, the terminal device 10 can report the buffer size to the base station device 20 for each specific type or characteristic of data.

[0270] (Aspect q2) The control unit 110 may transmit or generate a DSR MAC CE as a second DSR, as shown in Figure 23. In this example, the control unit 110 determines a field or set of fields for reporting specific data based on a set remaining time threshold (i.e., a first remaining time threshold and / or one or more second remaining time thresholds).

[0271] Assume that the bit corresponding to LCG1 in the LCG field 1910 is 1. Therefore, the delay information field 1920 includes a set of first fields 1930 corresponding to LCG1, a set of second fields 1940 corresponding to LCG1, and a set of third fields 2310 corresponding to LCG1. Assume that the bit corresponding to LCG0 in the LCG field 1910 is 0. Therefore, the delay information field 1920 does not include a set of fields corresponding to LCG0.

[0272] The first set of fields 1930 has the same configuration as the first set of fields 1930 in Figure 21, so a detailed explanation is omitted. The second set of fields 1940 also has the same configuration as the second set of fields 1940 in Figure 21, so a detailed explanation is omitted.

[0273] The third set of fields 2310 may be a set of fields for reporting data corresponding to the smallest threshold among the first remaining time threshold and / or one or more second remaining time thresholds. That is, the control unit 110 may use a field corresponding to the smallest threshold among the first remaining time threshold and / or one or more second remaining time thresholds set in a certain LCG to report the remaining time and / or buffer size of specific data buffered in the LCG. For example, in Figure 20, there is no data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c. Even in such a case, information regarding the specific data 2001 may be reported using a set of fields for data corresponding to the smallest threshold among the first remaining time threshold Th1 and the second remaining time thresholds Th2a, Th2b, Th2c (hereinafter referred to as the "first minimum threshold"). For example, the control unit 110 may determine a first minimum threshold Th2c and generate a set of fields (i.e., a third set of fields 2310) for reporting data corresponding to the first minimum threshold Th2c. The control unit 110 may use the third set of fields 2310 to report information about specific data 2001.

[0274] The third set of fields 2310 includes fields 2311 and 2312. Field 2311 includes a first portion 2311a, a second portion 2311b, and a third portion 2311c. The first portion 2311a may be the field corresponding to (m3) above (i.e., the BT field). The second portion 2311b may be the field corresponding to (m2) above (i.e., the E field). Since the third set of fields 2310 corresponding to LCG1 is the last pair with respect to LCG1, the second portion 2311b may be a value (e.g., 0) indicating that there are no additional pairs of remaining time and buffer size.

[0275] If the specific data corresponding to the set of third fields 2310 is data that does not have a remaining time, the third portion 2311c may be "reserved" or set to a predetermined value (for example, 0). In this example, the third portion 2311c is set to 0. If the specific data corresponding to the set of third fields 2310 is data that has a remaining time, the third portion 2311c may indicate that remaining time.

[0276] Field 2312 may indicate the buffer size Y1 of specific data 2001. Field 2312 may indicate the total amount of specific data or a portion of specific data. Field 2312 may indicate the total amount of the above (j1) to (j3) and (k1) to (k2) data. Field 2312 may indicate the amount of at least one of the above (j1) to (j3) and (k1) to (k2) data. For example, field 2312 may indicate the buffer size Y2 of the first specific data 2002. Field 2312 may indicate the buffer size Y3 of the second specific data 2003.

[0277] Regarding LCG1, let's assume that there is data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c, the buffer size of the data is X4, and the remaining time of the data is T4. In this case, the control unit 110 may set the third set of fields 2310 as shown in Figure 24. The differences from Figure 23 will be explained below. The third part 2311c may indicate the remaining time T4 of the data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c. Furthermore, the control unit 110 may perform a predetermined calculation (e.g., addition) on the buffer size X4 using the buffer size Y1 of the specific data 2001. The field 2312 may indicate the sum of the buffer size X4 of the data for which the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2c and the buffer size Y1 of the specific data 2001 (X4 + Y1). The information regarding the specific data here is not limited to the buffer size Y1 of the specific data 2001. The information relating to the specific data may be the total amount of the data (j1) to (j3) and (k1) to (k2) described above, or it may be the amount of at least one of the data (j1) to (j3) and (k1) to (k2) described above. The information relating to the specific data may be the buffer size Y2 of the first specific data 2002, or the buffer size Y3 of the second specific data 2003.

[0278] Furthermore, information regarding data that is prioritized among specific data may be stored in the third set of fields 2310. For example, retransmitted data in RLC AM (i.e., (k1) above) is prioritized over initial data in the RLC layer. Information regarding such data may be reported using a set of fields for reporting data corresponding to a first minimum threshold (i.e., the third set of fields 2310).

[0279] In another example, information regarding specific data 2001 may be reported using a set of fields for reporting data corresponding to the largest threshold among a first remaining time threshold Th1 and second remaining time thresholds Th2a, Th2b, and Th2c (hereinafter referred to as the "first maximum threshold"). That is, the control unit 110 may report the remaining time and / or buffer size of specific data buffered in a certain LCG using a field corresponding to the largest threshold among a first remaining time threshold and / or one or more second remaining time thresholds set in the LCG. In the example of Figure 20, the control unit 110 may determine the first maximum threshold Th1a and include information regarding specific data 2001 in the first set of fields 1930 for reporting data 1801 corresponding to the first maximum threshold Th1a.

[0280] As shown in Figure 25, the control unit 110 may perform a predetermined calculation (e.g., addition) on the buffer size X1 of data 1801 using the buffer size Y1 of specific data 2001. For example, field 1932 may show the sum of the buffer size X1 of data 1801 and the buffer size Y1 of specific data 2001 (X1 + Y1). Similarly, the information regarding the specific data here is not limited to the buffer size Y1 of the specific data 2001. The information regarding the specific data may be the total amount of the data (j1) to (j3) and (k1) to (k2) above, or the amount of at least one of the data (j1) to (j3) and (k1) to (k2) above. The information regarding the specific data may be the buffer size Y2 of the first specific data 2002, or the buffer size Y3 of the second specific data 2003.

[0281] Furthermore, even if the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and there is no data 1801 whose remaining time is greater than or equal to the second remaining time threshold Th2a, information regarding the specific data 2001 may be reported using the first set of fields 1930. In this case, the third portion 1931c may be "reserved" or set to a predetermined value (e.g., 0). Field 1932 may indicate the buffer size Y1 of the specific data 2001.

[0282] In the example above, information about specific data is stored in a single set of fields, but the example is not limited to this. Information about specific data may be stored in two or more sets of fields. For example, in the configuration of Figure 23, information about a part of the specific data may be stored in a second set of fields 1940, and information about other parts of the specific data may be stored in a third set of fields 2310. For example, information about the first specific data 2002 may be stored in the second set of fields 1940, and information about the second specific data 2003 may be stored in the third set of fields 2310.

[0283] (Aspect q3) The control unit 110 may transmit or generate a DSR MAC CE as a second DSR, as shown in Figure 26. In this example, the control unit 110 generates one or more fields corresponding to one or more data to be reported for a given LCG. From the generated one or more fields, the control unit 110 selects or determines a field or set of fields for reporting specific data based on a plurality of remaining time thresholds (i.e., a first remaining time threshold and / or one or more second remaining time thresholds).

[0284] In the example shown in Figure 20, data 1801 and data 1802 are buffered in LCG1. As described above, data 1801 is data where the remaining time of the PDCP discard timer is less than the first remaining time threshold Th1a and greater than or equal to the second remaining time threshold Th2a. Data 1802 is data where the remaining time of the PDCP discard timer is less than the second remaining time threshold Th2b and greater than or equal to the second remaining time threshold Th2c. As shown in Figure 26, the control unit 110 generates a set of first fields 1930 and a set of second fields 1940 corresponding to the data to be reported (i.e., data 1801 and data 1802). The control unit 110 determines the set of fields from the set of first fields 1930 and the set of second fields 1940 that corresponds to the smallest remaining time threshold (hereinafter referred to as the "second minimum threshold"). More specifically, the control unit 110 determines a second minimum threshold Th2b and determines a second set of fields 1940 for reporting data 1802 corresponding to the second minimum threshold Th2b as a set of fields for reporting information about specific data. That is, the control unit 110 may report the remaining time and / or buffer size of specific data buffered in a certain LCG using the field corresponding to the data with the smallest remaining time among the fields relating to a certain LCG included in the second DSR. The control unit 110 may also report the remaining time and / or buffer size of specific data buffered in a certain LCG using the field corresponding to data if data with a remaining time corresponding to a portion divided based on a first remaining time threshold and / or one or more second remaining time thresholds set for a certain LCG exists in the LCG (i.e., is buffered)

[0285] As shown in Figure 26, the control unit 110 may perform a predetermined calculation (e.g., addition) on the buffer size X2 of data 1802 using the buffer size Y1 of specific data 2001. For example, field 1942 may show the sum of the buffer size X2 of data 1802 and the buffer size Y1 of specific data 2001 (X2 + Y1). Similarly, the information regarding the specific data here is not limited to the buffer size Y1 of the specific data 2001. The information regarding the specific data may be the total amount of the data (j1) to (j3) and (k1) to (k2) above, or the amount of at least one of the data (j1) to (j3) and (k1) to (k2) above. The information regarding the specific data may be the buffer size Y2 of the first specific data 2002, or the buffer size Y3 of the second specific data 2003.

[0286] Furthermore, information regarding data that is prioritized among specific data may be stored in the third set of fields 2310. For example, retransmitted data in RLC AM (i.e., (k1) above) is prioritized over initial data in the RLC layer. Information regarding such data may be reported using a set of fields for reporting data corresponding to a minimum threshold (i.e., the third set of fields 2310).

[0287] In another example, information regarding specific data may be reported using a set of fields from the first set of fields 1930 and the second set of fields 1940 that corresponds to the largest remaining time threshold (hereinafter referred to as the "second maximum threshold"). In the example of Figure 20, the control unit 110 may determine the second maximum threshold Th1a and determine the first set of fields 1930 for reporting the data 1801 corresponding to the second maximum threshold Th1a as the set of fields for reporting information regarding specific data.

[0288] As shown in Figure 27, the control unit 110 may perform a predetermined calculation (e.g., addition) on the buffer size X1 of data 1801 using the buffer size Y1 of specific data 2001. For example, field 1932 may show the sum of the buffer size X1 of data 1801 and the buffer size Y1 of specific data 2001 (X1 + Y1). Similarly, the information regarding specific data here is not limited to the buffer size Y1 of specific data 2001. The information regarding specific data may be the total amount of the above-mentioned (j1) to (j3) and (k1) to (k2) data, or the amount of at least one of the above-mentioned (j1) to (j3) and (k1) to (k2) data. The information regarding specific data may be the buffer size Y2 of the first specific data 2002, or the buffer size Y3 of the second specific data 2003.

[0289] Furthermore, embodiments q1 to q3 described above may be applied to LCGs for which the above-described configuration information has been set. Conversely, if no configuration information has been set for a given LCG, the terminal device 10 may include the buffer size of the specific data buffered in that LCG in the total amount of delayed critical UL data when reporting it. For example, if no configuration information has been set for a given LCG, the terminal device 10 may set the total amount of delayed critical UL data calculated based on (h1) to (h5) and (i1) to (i4) described above in the buffer size field for that LCG.

[0290] With the above configuration, when a DSR is triggered for a certain LCH or LCG, the terminal device 10 can generate or select an appropriate field for specific data in the second DSR.

[0291] Note that the specific data is not limited to the examples above. For example, the specific data may be "delay-critical UL data that satisfies specific conditions." For example, the specific data may be "delay-critical UL data excluding data determined based on a first remaining time threshold and / or a second remaining time threshold." In another example, the specific data may be "delay-critical UL data that has not yet been reported after DSR MAC CE has reported information regarding data determined based on a first remaining time threshold and / or a second remaining time threshold." In yet another example, the specific data may be "delay-critical UL data that remains to be reported at the time DSR MAC CE is built and information regarding data determined based on a first remaining time threshold and / or a second remaining time threshold is included (stored) in DSR MAC CE."

[0292] 2. Modifications Although this disclosure is described in accordance with the embodiments described above, it is understood that this disclosure is not limited to such embodiments or structures. This disclosure also includes various modifications and variations within the scope of equivalents. Other combinations including one or more elements included in the embodiments described above also fall within the scope and idea of ​​this disclosure.

[0293] The words, phrases, and other expressions used in the above embodiments are merely illustrative and may be replaced with substantially identical or similar expressions. In particular, since the technology according to the above embodiments relates to technical specifications, the expressions in the above embodiments may be replaced with substantially identical or similar expressions in the technical specifications (for example, the technical specifications referenced in this specification).

[0294] The information transmitted and received in the above embodiments may be transmitted and received in the same or different messages or the same or different elements already described in the technical specifications, or it may be transmitted and received in newly defined messages or elements. The information transmitted and received in the above embodiments may be transmitted and received using different layers and / or different channels than those in the above embodiments.

[0295] The means and / or functions provided by the apparatus described in the above embodiments can be provided by software recorded in a physical memory device and a computer that runs it, by software only, by hardware only, or by a combination thereof. For example, if any of the above apparatuses are provided by an electronic circuit which is hardware, it can be provided by a digital circuit including a number of logic circuits, or by an analog circuit.

[0296] The apparatus described in the above embodiment executes a program stored on a non-transitory tangible storage medium. The execution of this program then executes a method corresponding to the program.

[0297] 3. Addendums The above embodiments and modifications, in whole or in part, may also be described as follows, but are not limited to the contents of the addendums below. Hereinafter, a relationship is expressed in which an addendum that is subordinate to multiple addendums is subordinate to an addendum that is subordinate to multiple addendums. All of the addendum dependency relationships expressed below are included in the above embodiments.

[0298] (Note A1) A terminal device (10) comprising: a control unit (110) configured to generate either a first DSR or a second DSR different from the first DSR when a Delay Status Reporting (DSR) is triggered; and a communication unit (120) configured to transmit the generated first DSR or second DSR to a base station device (20), wherein the control unit is configured to include in the second DSR first information relating to first data buffered in a Logical Channel Group (LCG) and associated with the discard timer, which is divided into multiple parts based on the multiple remaining time thresholds, and second information relating to second data buffered in the LCG and not associated with the discard timer, when a plurality of remaining time thresholds for the discard timer are set,

[0299] (Appendix A2) The terminal device according to Appendix A1, wherein the control unit is configured to generate a first field containing the first information and a second field containing the second information with respect to the LCG in the second DSR.

[0300] (Appendix A3) The terminal device according to Appendix A1, wherein the control unit is configured to generate a field in the second DSR for reporting data corresponding to the smallest of the plurality of remaining time thresholds with respect to the LCG, and to include the second information in the field.

[0301] (Appendix A4) The terminal device according to Appendix A1, wherein the control unit is configured to generate a field in the second DSR for reporting data corresponding to the largest of the plurality of remaining time thresholds with respect to the LCG, and to include the second information in the field.

[0302] (Appendix A5) The terminal device according to Appendix A1, wherein the control unit is configured to generate one or more fields corresponding to one or more data when there is one or more data to be reported to the LCG, select a field from the one or more fields based on the plurality of remaining time thresholds, and include the second information in the selected field.

[0303] (Appendix A6) The terminal device according to Appendix A5, wherein the control unit is configured to include the second information in a field for reporting data corresponding to the smallest remaining time threshold among the one or more fields.

[0304] (Appendix A7) The terminal device according to Appendix A5, wherein the control unit is configured to include the second information in a field for reporting data corresponding to the largest remaining time threshold among the one or more fields.

[0305] (Note A8) The terminal device according to any one of Notes A1 to A7, wherein the control unit is configured to generate the second DSR when it receives setting information indicating that it is permissible to report the second DSR.

[0306] (Note A9) The terminal device described in Note A8, which sets the aforementioned setting information for a cell group, logical channel (LCH), or LCG.

[0307] (Appendix A10) The terminal device according to any one of Appendix A1 to A9, wherein the second data is data excluding delayed critical uplink data determined based on at least one of the plurality of remaining time thresholds.

[0308] (Note A11) The terminal device as described in Note A10, wherein the second data includes at least one of the following: a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), a PDCP SDU (Service Data Unit) that is retransmitted when the upper layer requests at least one of PDCP entity re-establishment and uplink data switching in the case of an AM (Acknowledge Mode) DRB (Data Radio Bearer), a PDCP data PDU that is retransmitted when the upper layer requests PDCP data recovery from the radio bearer in the case of an AM DRB, an RLC (Radio Link Control) AM data PDU that is pending for retransmission, and an RLC control PDU.

[0309] (Appendix A12) A method of a terminal device (10) comprising: generating a first DSR and a second DSR different from the first DSR when a Delay Status Reporting (DSR) is triggered; and transmitting the generated first DSR or second DSR to a base station device (20), wherein the method further comprises, when a plurality of remaining time thresholds for a discard timer are set, first information relating to first data buffered in a Logical Channel Group (LCG) and associated with the discard timer, which is divided into a plurality of parts based on the plurality of remaining time thresholds, and second information relating to second data buffered in the LCG and not associated with the discard timer, in the second DSR.

[0310] (Note A13) A program that causes a processor (101) in a terminal device (10) to generate either a first DSR or a second DSR different from the first DSR when a Delay Status Reporting (DSR) is triggered, and to transmit the generated first DSR or second DSR to a base station device (20), wherein the program further causes the processor to include in the second DSR first information relating to first data buffered in a Logical Channel Group (LCG) and associated with the discard timer, which is divided into multiple parts based on the multiple remaining time thresholds, and second information relating to second data buffered in the LCG and not associated with the discard timer, when a plurality of remaining time thresholds for the discard timer are set.

[0311] (Appendix A14) A non-transitional tangible recording medium recording a program that causes a processor (101) in a terminal device (10) to generate either a first DSR or a second DSR different from the first DSR when a Delay Status Reporting (DSR) is triggered, and to transmit the generated first DSR or second DSR to a base station device (20), wherein the program further causes the processor to include in the second DSR first information relating to first data buffered in a Logical Channel Group (LCG) and associated with the discard timer, which is divided into multiple parts based on the multiple remaining time thresholds, and second information relating to second data buffered in the LCG and not associated with the discard timer, when a plurality of remaining time thresholds for the discard timer are set.

[0312] (Note B1) The system includes: a receiving unit (122) that receives a Radio Resource Control (RRC) message containing information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; a control unit (110) that, if the first remaining time threshold is set for a Logical Channel Group (LCG), triggers the DSR for Logical Channels (LCH) belonging to the LCG based on the first remaining time threshold; and a transmitting unit (121) that, if the DSR is triggered and the list of second remaining time thresholds is set, transmits a DSR MAC CE (Medium Access Control Control Element), wherein the DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG. The amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes a predetermined amount of data, the predetermined data being data relating to the LCG, including a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data, in a terminal device (10).

[0313] (Note B2) The terminal device as described in Note B1, wherein the DSR MAC CE includes a remaining time field indicating the remaining time for data relating to the LCG, and if the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero.

[0314] (Note B3) The terminal device according to Note B1 or B2, wherein the DSR MAC CE includes an LCG field indicating whether or not the buffer size field and the remaining time field relating to the LCG are included, and a field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG are included.

[0315] (Note B4) Receiving a Radio Resource Control (RRC) message including information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; if the first remaining time threshold is set for a Logical Channel Group (LCG), triggering the DSR for a Logical Channel (LCH) belonging to the LCG based on the first remaining time threshold; and if the DSR is triggered and the list of second remaining time thresholds is set, transmitting a DSR MAC CE (Medium Access Control Control Element), wherein the DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG, and the amount of data indicated by the buffer size field associated with the smallest threshold in the list of second remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data, according to the method of the terminal device (10).

[0316] (Note B5) The method according to Note B4, wherein the DSR MAC CE includes a remaining time field indicating the remaining time of data relating to the LCG, and if the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero.

[0317] (Appendix B6) The method according to Appendix B4 or B5, wherein the DSR MAC CE includes an LCG field indicating whether or not the buffer size field and the remaining time field relating to the LCG are included, and a field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG is included.

[0318] (Note B7) A transmitting unit (221) transmits a Radio Resource Control (RRC) message including information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR; and a receiving unit (222) receives a DSR MAC CE (Medium Access Control Control Element) from a terminal device (10) when the DSR is triggered for a Logical Channel Group (LCG) based on the first remaining time threshold set for the LCG, and the list of second remaining time thresholds is set, wherein the DSR MAC CE includes a buffer size field indicating the amount of data relating to the LCG, and the amount of data indicated by the buffer size field associated with the smallest threshold in the list of second remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data, as defined by the base station equipment (20).

[0319] (Note B8) The base station device as described in Note B7, wherein the DSR MAC CE includes a remaining time field indicating the remaining time for data relating to the LCG, and if the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero.

[0320] (Note B9) The base station device according to Note B7 or B8, wherein the DSR MAC CE includes an LCG field indicating whether or not the buffer size field and the remaining time field relating to the LCG are included, and a field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG are included.

[0321] The disclosures in the above-mentioned prior art documents and references are incorporated into this specification by reference.

Claims

A receiving unit (122) that receives a Radio Resource Control (RRC) message including information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR, If the first remaining time threshold is set for a Logical Channel Group (LCG), a control unit (110) triggers the DSR for a Logical Channel (LCH) belonging to the LCG based on the first remaining time threshold, A transmitting unit (121) transmits a DSR MAC CE (Medium Access Control Control Element) when the DSR is triggered and the second remaining time threshold list is set. Equipped with, The DSR MAC CE includes a buffer size field indicating the amount of data related to the LCG, The amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data. Terminal device (10). 　 The DSR MAC CE includes a remaining time field indicating the remaining time for the data relating to the LCG, If the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero. The terminal device according to claim 1. 　 The aforementioned DSR MAC CE is, An LCG field indicating whether or not the buffer size field and the remaining time field related to the LCG are included, and A field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG is included, The terminal device according to claim 1 or 2. 　 Receiving a Radio Resource Control (RRC) message that includes information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR, If the first remaining time threshold is set for a Logical Channel Group (LCG), the DSR is triggered for the Logical Channel (LCH) belonging to the LCG based on the first remaining time threshold. If the DSR is triggered and the second remaining time threshold list is set, send a DSR MAC CE (Medium Access Control Control Element), Includes, The DSR MAC CE includes a buffer size field indicating the amount of data related to the LCG, The amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data. A method for the terminal device (10). 　 The DSR MAC CE includes a remaining time field indicating the remaining time for the data relating to the LCG, If the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero. The method according to claim 4. 　 The aforementioned DSR MAC CE is, An LCG field indicating whether or not the buffer size field and the remaining time field related to the LCG are included, and A field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG is included, The method according to claim 4 or 5. 　 A transmitting unit (221) transmits a Radio Resource Control (RRC) message that includes information indicating a first remaining time threshold used to trigger Delay Status Reporting (DSR), and information indicating a list of second remaining time thresholds used to report the delay status in the DSR. Based on the first remaining time threshold set for the Logical Channel Group (LCG), the DSR is triggered for a Logical Channel (LCH) belonging to the LCG, and if the list of second remaining time thresholds is set, the receiving unit (222) receives the DSR MAC CE (Medium Access Control Control Element) from the terminal device (10), Equipped with, The DSR MAC CE includes a buffer size field indicating the amount of data related to the LCG, The amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes a predetermined amount of data. The predetermined data is data relating to the LCG, and includes a PDCP (Packet Data Convergence Protocol) control PDU (Protocol Data Unit), an RLC (Radio Link Control) control PDU, retransmitted PDCP data, and retransmitted RLC data. Base station device (20). 　 The DSR MAC CE includes a remaining time field indicating the remaining time for the data relating to the LCG, If the amount of data indicated by the buffer size field associated with the smallest threshold in the second list of remaining time thresholds includes only the predetermined amount of data, the remaining time field associated with the smallest threshold in the second list of remaining time thresholds is set to zero. The base station device according to claim 7. 　 The aforementioned DSR MAC CE is, An LCG field indicating whether or not the buffer size field and the remaining time field related to the LCG are included, and A field indicating whether or not an additional pair of the buffer size field and the remaining time field relating to the LCG is included, The base station device according to claim 7 or 8.

Images