Terminal device and terminal device method

Abstract

Provided is a terminal device (10) comprising: a reception unit (122) that receives, from a base station device (20), a radio resource control (RRC) message that includes information for setting an identifier of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling a trigger of a delay information report (DSR); and a control unit (110) that controls the trigger of the DSR on the basis of the remaining time for the earliest deadline of the data of the LCG being below the threshold value and the DSR for the data of the LCG not being transmitted.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on and claims the benefit of priority from Japanese Patent Application No. 2023-62921, filed on April 7, 2023, the entire contents of which are incorporated herein by reference. [Technical Field]

[0002] The present disclosure relates to a terminal device and a method for a terminal device. [Background technology]

[0003] In recent years, technological development related to extended reality (XR) has progressed. 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, 3D time-series image data in real and / or virtual spaces, audio data in 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 quality of the user experience.

[0004] Non-Patent Document 1 discusses the implementation of XR in 5G NR (Fifth Generation New Radio), a wireless specification defined by the Third Generation Partnership Project (3GPP (registered trademark)). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TR 38.838 V17.0.0 (2021-12) [Non-patent document 2] 3GPP TS 38.321 V17.2.0 (2022-09) [Non-patent document 3] 3GPP TS 38.331 V17.2.0 (2022-09) Summary of the Invention

[0006] Non-Patent Document 2 describes a procedure for buffer status reporting (BSR). Furthermore, Non-Patent Document 3 describes parameters for BSR, which are transmitted from a base station device. The BSR indicates the buffer size of uplink data for predetermined data. The predetermined data is data corresponding to one Logical Channel Group (LCG). The terminal device calculates the buffer size for each LCG and transmits a BSR including the calculated buffer size to the base station device. The base station device allocates radio resources to the terminal device based on the BSR.

[0007] XR is expected to be operated under various requirements, including a requirement for low latency. Accordingly, with regard to uplink communication from a terminal device, it is required to allocate radio resources taking the above requirements into consideration. However, in the BSR described in Non-Patent Documents 2 and 3, the terminal device can only transmit one piece of information for predetermined data (i.e., information on buffer size). Since the amount of information reported to the base station device is small, there is a possibility that the base station device will not be able to appropriately allocate radio resources to the terminal device. Therefore, it is being considered to report predetermined information (e.g., information on delay) in addition to the buffer size in the BSR. Furthermore, it is being considered to report the above predetermined information to the base station device using a reporting method other than the BSR.

[0008] The inventors have found that a procedure is required to appropriately determine whether to trigger or transmit a report of the above-mentioned predetermined information. However, Non-Patent Documents 2 and 3 do not describe such a procedure. Note that the above-mentioned problem also occurs in ordinary terminal devices and base station devices other than those implementing XR.

[0009] The present disclosure provides a technique that can appropriately determine whether to trigger or send a report of predetermined information.

[0010] A terminal device according to the present disclosure includes a receiving unit that receives, from a base station device, a Radio Resource Control (RRC) message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs and information indicating a threshold for data of the LCG for controlling triggering of a Delay Status Report (DSR), and a control unit that controls triggering of the DSR based on the fact that the remaining time for the earliest expiration of data of the LCG is below the threshold and that the DSR for data of the LCG has not been transmitted. The control unit cancels the DSR that has been triggered but not canceled when the expiration of data of the LCG associated with the DSR has expired.

[0011] Furthermore, the terminal device method in the present disclosure includes receiving a Radio Resource Control (RRC) message from a base station device, the RRC message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs and information indicating a threshold for data of the LCG for controlling triggering of a Delay Status Report (DSR); controlling triggering of the DSR based on the remaining time for the earliest expiration of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; and canceling the DSR that has been triggered and not canceled when the expiration of the data of the LCG associated with the DSR has expired.

[0012] According to the above configuration, it is possible to appropriately determine whether to trigger or transmit a delay information report. Note that the above configuration may achieve other effects instead of or in addition to the above effect. [Brief explanation of the drawings]

[0013] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which: [Figure 1] FIG. 1 is a diagram showing a communication system S according to a first embodiment. [Figure 2] FIG. 2 is a diagram showing a protocol stack of a U-plane according to the first embodiment; [Figure 3] FIG. 3 is a diagram showing a C-plane protocol stack according to the first embodiment; [Figure 4] FIG. 4 is a block diagram showing a schematic hardware configuration of the terminal device 10 according to the first embodiment. [Figure 5] FIG. 5 is a block diagram showing a schematic functional configuration of the terminal device 10 according to the first embodiment. [Figure 6] FIG. 6 is a block diagram showing a schematic hardware configuration of the base station device 20 according to the first embodiment. [Figure 7] FIG. 7 is a block diagram showing a schematic functional configuration of the base station device 20 according to the first embodiment. [Figure 8] FIG. 8 is a diagram showing a radio frame configuration according to the first embodiment; [Figure 9] FIG. 9 is a diagram showing the configuration of a short BSR. [Figure 10] FIG. 10 shows the configuration of a long BSR. [Figure 11] FIG. 11 is a sequence diagram showing the flow of processing of the terminal device 10 and the base station device 20 according to the first embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the configuration of a long BSR including delay information; [Figure 13] FIG. 13 is a diagram showing another example of the configuration of a long BSR including delay information; [Figure 14] FIG. 14 is a diagram showing another example of the configuration of a long BSR including delay information; [Figure 15] FIG. 15 is a diagram illustrating an example in which a delay information report is transmitted; [Figure 16] FIG. 16 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 1-1 of the first embodiment. [Figure 17] FIG. 17 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 1-2 of the first embodiment. [Figure 18] FIG. 18 is a sequence diagram showing a processing flow of the terminal device 10 according to a modification of the first embodiment. [Figure 19] FIG. 19 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 2-1 of the second embodiment. [Figure 20] FIG. 20 is a sequence diagram showing the flow of processing by the terminal device 10 according to aspect 2-2 of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] The embodiments described below are merely examples of configurations that can realize the present disclosure. Each of the following embodiments can be modified or changed as appropriate depending on the configuration of the device to which the present disclosure is applied and various conditions. Not all of the combinations of elements included in each of the following embodiments are necessarily essential for realizing the present disclosure, and some of the elements can be omitted as appropriate. Therefore, the scope of the present disclosure is not limited to the configurations described in each of the following embodiments. As long as there are no mutual contradictions, configurations that combine multiple configurations described in the following embodiments can also be adopted.

[0016] 1. First embodiment 1.1. Communication Systems 1, a communication system S according to the first embodiment includes one or more terminal apparatuses (Terminal Apparatus) 10, one or more base station apparatuses (Base Station Apparatus) 20, and a core network 30. The communication system S is configured in accordance with predetermined technical specifications (Technical Specifications, TS). For example, the communication system S may comply with technical specifications (e.g., 5G, 5G Advanced, 6G, etc.) defined by 3GPP.

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

[0018] The terminal device 10 is a device that performs wireless communication with the base station device 20 and may be, for example, user equipment (UE) that operates in accordance with the 3GPP 5G NR specification. The terminal device 10 may also be a device that complies with other older or newer 3GPP specifications.

[0019] The terminal device 10 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a laptop 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 provided therein. The terminal device 10 may be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device provided therein. The terminal device 10 may be a sensor or a device provided therein. Note that the terminal device 10 may be called by other names such as a terminal, a mobile station, a mobile terminal, a mobile device, a mobile unit, a subscriber station, a subscriber terminal, a subscriber device, a subscriber unit, a wireless station, a wireless terminal, a wireless device, a wireless unit, a remote station, a remote terminal, a remote device, or a remote unit. The terminal device 10 may be a device adapted to one or more of 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., carrier frequency) and is composed of one component carrier. The term "cell" can refer to wireless communication resources and can also refer to a communication target of the terminal device 10. The base station device 20 wirelessly communicates with the terminal device 10 located in its own cell in the U-plane and C-plane. In other words, the base station device 20 terminates the U-plane protocol and 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 the 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 connects to the UPF in the U-plane.

[0022] The base station device 20 may be, for example, a gNB that provides a U-plane and a C-plane conforming to the 3GPP 5G NR specification to the terminal device 10 and connects to the 3GPP 5GC (5G Core Network). Alternatively, the base station device 20 may be a device conforming to another older or newer 3GPP specification.

[0023] The base station device 20 may be configured with a plurality of unit devices. For example, the base station device 20 may be configured with a central unit (CU), a distributed unit (DU), and a radio unit (RU).

[0024] A radio access network (RAN) is formed by interconnecting multiple base station devices 20. The radio access network formed by the base station devices 20 that are gNBs may be referred to as an NG-RAN. The base station devices 20 that are gNBs may be referred to as NG-RAN nodes.

[0025] The plurality of base station devices 20 are connected to each other via a predetermined interface (for example, an Xn interface). More specifically, for example, the plurality of base station devices 20 are connected to each other via an Xn-U interface in the U-plane, and are connected to each other via an Xn-C interface in the C-plane. Note that the plurality of base station devices 20 may also be connected to each other via other interfaces with different functions or names.

[0026] Each base station device 20 is connected to the core network 30 via 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 via an NG-U interface in the U-plane, and is connected to the AMF of the core network 30 via an NG-C interface in the C-plane. Note that each base station device 20 may also be connected to the core network 30 via another interface with a different function or name.

[0027] The radio protocol architecture between the terminal device 10 and the base station device 20 will be described with reference to Fig. 2. The radio 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 with reference to Fig. 3.

[0028] 2, the U-plane protocol stack includes, from the bottom up, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer. Each of the above layers is terminated at base station device 20 on the network side.

[0029] As shown in Fig. 3, the C-plane protocol stack includes, from the bottom up, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a non-access stratum (NAS). Each of the above layers except the non-access stratum is terminated at the base station device 20 on the network side. The non-access stratum is terminated at the AMF of the core network 30 on the network side.

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

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

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

[0033] The input / output interface 103 is an interface that accepts operations on the terminal device 10 and supplies them to the processor 101, and also presents 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 executes 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 an antenna 105.

[0035] 5, the terminal device 10 has, as functional blocks, a control unit 110 and a communication unit 120. The communication unit 120 has at least one transmission unit 121 and at least one reception 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 realized by the processor 101 and the memory 102. The control unit 110 executes 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 transmits and receives data / information / messages via the communication unit 120.

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

[0038] The control unit 110 operates to execute various processes of the terminal device 10 of this embodiment.

[0039] 6, base station device 20 has, as hardware elements, a processor 201, a memory 202, a network interface 203, a wireless interface 204, and an antenna 205. The above elements provided in base station device 20 are connected to each other by an internal bus. Note that base station device 20 may have hardware elements other than the elements shown in FIG. 6.

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

[0041] The memory 202 is configured by at least one storage medium such as a ROM (Read Only Memory), a RAM, an HDD (Hard Disk Drive), or an 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 device 20. The programs include one or more instructions for operating the base station device 20. The processor 201 implements the functions of the base station device 20 by loading the programs stored in the memory 202 into the memory 202 and / or a system memory (not shown) and executing them.

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

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

[0044] 7, the base station device 20 has, as functional blocks, a control unit 210, a communication unit 220, and a network communication unit 230. The communication unit 220 has 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 realized 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 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. Furthermore, for example, the control unit 210 controls 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 radio interface 204 and an antenna 205. In other words, the communication unit 220 is realized by the radio interface 204 and the antenna 205. The communication unit 220 wirelessly communicates with the terminal device 10 by transmitting and receiving radio signals to and from the terminal device 10. Two or more radio interfaces 204 and two or more antennas 205 may be included in the communication unit 220.

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

[0048] The control unit 210 operates to execute various processes in the base station device 20 of this embodiment.

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

[0050] The transmission method for downlink communication from the base station device 20 to the terminal device 10 is, for example, Orthogonal Frequency Division Multiplexing (OFDM) using a cyclic prefix (CP), that is, CP-OFDM. The transmission method for uplink communication from the terminal device 10 to the base station device 20 is, for example, the above-mentioned CP-OFDM 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 interference and inter-carrier interference, and is inserted at the beginning of an OFDM symbol. There are two types of cyclic prefixes: a normal cyclic prefix and an extended cyclic prefix.

[0052] As radio resources in the frequency domain of OFDM, multiple subcarriers that are orthogonal to each other are used. The multiple subcarriers are arranged in the frequency domain at a predetermined subcarrier spacing (sub-carrier spacing, SCS) Δf. Multiple subcarrier spacings Δf can be applied in a communication system S. The subcarrier spacing Δf is expressed by, for example, the following equation: Δf=2 μ 15[kHz]

[0053] Here, μ is an integer equal to or greater than 0 and can take on at least one of the following values: 0, 1, 2, 3, 4, 5, or 6. Therefore, the subcarrier spacing Δf [kHz] can take on at least one of the following values: 15, 30, 60, 120, 240, 480, or 960. Note that μ may also take on a value of 7 or greater.

[0054] In the time domain of OFDM, a layered radio frame structure is used as shown in Figure 8. One radio frame includes 10 subframes. Subframes are assigned subframe numbers that count up by one from 0 to 9. 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 spacing Δf.

[0055] One subframe includes one or more slots (slot(s)). The number Ns of slots included in one subframe depends on the value of μ mentioned above, and further on the subcarrier spacing Δf. The number Ns of slots is expressed by, for example, the following equation: Ns=2 μ

[0056] One slot contains multiple symbols. The number of symbols in one slot depends on the type of cyclic prefix. For example, if a normal cyclic prefix is ​​used, one slot contains 14 symbols. For example, if an extended cyclic prefix is ​​used, one slot contains 12 symbols.

[0057] As described above, the number of slots and the number of symbols included in each of a radio frame, half frame, and subframe, each of which has a fixed time length, are variable. Therefore, the time length of a slot and the time length of a symbol are also variable.

[0058] A resource element (RE) is a radio resource unit in the time-frequency domain consisting of one subcarrier and one symbol, and a resource block (RB) is a radio resource unit in the time-frequency domain consisting of 12 subcarriers and multiple symbols.

[0059] Each radio frame is assigned a system frame number (SFN), which counts up by one from 0 to 1023. SFN "0" corresponds to the initial SFN value, and SFN "1023" corresponds to the maximum SFN value. Therefore, SFN0 is assigned to the radio frame following a radio frame assigned SFN 1023. Since the time length of a radio frame is 10 ms, the time length 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 cell may correspond to a component carrier in the downlink and / or a component carrier in the uplink. A technology 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 referred to as carrier aggregation.

[0061] Furthermore, the base station device 20 may configure one or more bandwidth parts (Bandwidth Parts, BWPs) for the terminal device 10 with respect to each of one or more serving cells. For example, a downlink bandwidth part (DL-BWP) may be configured in the downlink of one serving cell. Furthermore, an uplink bandwidth part (UL-BWP) may be configured in the uplink of one serving cell. Here, the DL-BWP may include an initial DL-BWP and / or a dedicated DL-BWP. Furthermore, the UL-BWP may include an initial UL-BWP and / or a dedicated UL-BWP. Hereinafter, BWP may include a DL-BWP and / or a UL-BWP.

[0062] 1.3. Channel and Control Information The 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 in the downlink and uplink will be exemplified below.

[0063] The terminal device 10 and the base station device 20 transmit and receive user data and control information using a plurality of hierarchical 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 a physical downlink control channel (PDCCH), a physical broadcast channel (PBCH), and a 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 one physical channel. Examples of transport channels include a Downlink Shared Channel (DL-SCH) and an Uplink Shared Channel (UL-SCH). For example, data in the downlink may also be referred to as DL-SCH data. Also, for example, data in the uplink may also be referred to as UL-SCH data. Here, DL-SCH data includes downlink user data. Also, UL-SCH data includes uplink user data.

[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 a Broadcast Control Channel (BCCH), a Common Control Channel (CCCH), and a Dedicated Control Channel (DCCH).

[0066] The base station device 20 transmits downlink control information (DCI) to the terminal device 10 using a PDCCH, which is a physical channel. The DCI includes information on downlink and uplink resource allocation for the terminal device 10 and 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 defined for transmission of DCI in the PDCCH. A format defined for transmission of DCI in the PDCCH may be referred to as a DCI format. For example, the DCI format may include a DCI format used for scheduling a Physical Downlink Shared Channel (PDSCH) (e.g., a format referred to as DCI format 1_0, DCI format 1_1, and / or DCI format 1_2). Furthermore, for example, the DCI format may include a DCI format used for scheduling a Physical Uplink Shared Channel (PUSCH) (e.g., a format referred to as DCI format 0_0, DCI format 0_1, and / or DCI format 0_2). Furthermore, the DCI format may include a DCI format not used for scheduling a PDSCH and / or a PUSCH. A DCI format used for scheduling a PDSCH and / or a PUSCH may be referred to as a scheduling DCI format. A DCI format that is not used for scheduling a PDSCH and / or a PUSCH may be referred to as a non-scheduling DCI format. In this embodiment, for ease of explanation, a "DCI format" may be simply referred to as a "PDCCH." Furthermore, a "DCI generated according to a DCI format" may be simply referred to as a "DCI format."

[0068] For example, the base station device 20 may configure frequency domain resources and / or time domain resources that the terminal device 10 monitors (i.e., monitors) a PDCCH candidate set. For example, the frequency domain resources that the terminal device 10 monitors the PDCCH candidate set may be referred to as a control resource set (CORESET). Furthermore, the time domain resources that the terminal device 10 monitors the PDCCH candidate set may be referred to as a search space set (SSS). The terminal device 10 may monitor the PDCCH candidate set in one or more CORESETs in the DL-BWP of a serving cell in which 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 monitored DCI format. The above configuration may be referred to as blind decoding.

[0069] Here, a CRC (Cyclic Redundancy Check) scrambled with an RNTI (Radio Network Temporary Identifier) ​​may be added to DCI (or a DCI format) transmitted on the PDCCH. The CRC may also be referred to as a CRC parity bit. Multiple types of RNTIs are defined. For example, the base station device 20 may set each RNTI by transmitting an RRC message including at least one of information indicating a C-RNTI (Cell-RNTI), information indicating a MCS-C-RNTI (Modulation and Coding Scheme Cell-RNTI), and information indicating a CS-RNTI (Configured Scheduling-RNTI). In other words, a CRC scrambled with at least one of a C-RNTI, an MCS-C-RNTI, and a CS-RNTI may be added to DCI (or a DCI format) transmitted on the 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 PUCCH, which is a physical channel. The UCI includes control information such as a scheduling request (SR), an Ack / Nack of a hybrid automatic repeat reQuest (HARQ), and channel state information (CSI). The UCI is mapped to the PUCCH or PUSCH and corresponds to layer 1 signaling.

[0072] The base station device 20 uses DL-SCH, which is a transport channel, to transmit a control element (CE) of the MAC layer to the terminal device 10. The downlink MAC CE is mapped to the PDSCH via DL-SCH and corresponds to Layer 2 signaling.

[0073] The terminal device 10 transmits a control element (CE) of the MAC layer to the base station device 20 using the UL-SCH, which is a transport channel. The uplink MAC CE includes control information such as a buffer status report (BSR). The uplink MAC CE is mapped to a PUSCH via the UL-SCH and corresponds to Layer 2 signaling.

[0074] The base station device 20 transmits (or broadcasts) system information (SI) to the terminal device 10 using the BCCH, which is a logical channel. The SI includes minimum system information (MSI) and other system information (OSI). The MSI includes a master information block (MIB) and system information block 1 (SIB1). The SIB1 may be referred to as remaining minimum system information (RMSI). The OSI includes system information blocks (SIB2 onward) other than SIB1. Of the BCCH, the MIB is mapped to the PBCH via the BCH (Broadcast CHannel), and the SIB is mapped to the PDSCH via the 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 terminal device 10 and the base station device 20 in the RRC layer. Hereinafter, a message exchanged between the base station device 20 and the terminal device 10 in the RRC layer may be referred to as an RRC message. There are multiple types of SRBs (for example, SRB0, SRB1, SRB2, SRB3, and SRB4). SRBs are used for transmitting and receiving RRC messages as well as NAS messages including 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. The CCCH and DCCH are each mapped to the PDSCH via the DL-SCH. The RRC message corresponds to Layer 3 signaling.

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

[0077] The terminal device 10 uses the above-mentioned SRB to transmit an RRC message to the base station device 20. A CCCH or a DCCH is used to transmit the RRC message from the terminal device 10 to the base station device 20. The CCCH and DCCH are each mapped to a PUSCH via a UL-SCH. The RRC message corresponds to Layer 3 signaling.

[0078] As an example of an uplink RRC message, a 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 SRB1. A 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 related to the radio access capability of the terminal device 10.

[0079] As an example of an uplink RRC message, a user equipment assistance information (UE Assistance Information) message will be described. The user equipment assistance information 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 the user equipment assistance information message. The user equipment assistance information message is used to notify the base station device 20 of various information related to the terminal device 10 (UE assistance information).

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

[0081] The terminal device 10 transmits UCI including an SR to the base station device 20 using the configured PUCCH resource. The terminal device 10 may transmit UCI on demand. The terminal device 10 may transmit 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 radio resources of a PUSCH 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 a PUSCH in accordance with an uplink grant procedure. The base station device 20 transmits an uplink grant to the terminal device 10 on the PDCCH. The terminal device 10 transmits the PUSCH in accordance with the uplink grant. For example, the base station device 20 may allocate radio resources for the PUSCH using a DCI format with a CRC scrambled by the C-RNTI and / or MCS-C-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, a new data indicator included in the DCI format to which the CRC scrambled by the C-RNTI and / or MCS-C-RNTI is added 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 a CRC scrambled by the 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, a new data indicator included in the DCI format with a CRC scrambled by the CS-RNTI may be set to 1.

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

[0084] 1.4.4. Buffer Status Report (BSR) The terminal device 10 transmits a BSR by MAC signaling using the allocated PUSCH radio resources. The BSR is configured by a MAC CE included in a MAC PDU (Medium Access Control Protocol Data Unit). The BSR indicates information on the buffer status of uplink data of the MAC entity. The base station device 20 allocates uplink radio resources to the terminal device 10 based on the BSR.

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

[0086] The base station device 20 transmits an RRC message including 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: a periodicBSR-Timer, a retxBSR-Timer, and a logicalChannelSR-DelayTimer.

[0087] 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 transmit an RRC message including the LogicalChannelConfig IE. Furthermore, the terminal device 10 may identify configurations related to logical channels and / or LCGs based on the LogicalChannelConfig IE included in the RRC message. For example, the LogicalChannelConfig IE includes a logicalChannelGroup IE. The logicalChannelGroup IE assigns logical channels to LCGs. For example, an LCG index (ID) may be set for each of one or more logical channels, and an LCG to which the one or more logical channels belong may be set. Note that the LogicalChannelConfig IE may include a logicalChannelGroupIAB-Ext IE. The logicalChannelGroupIAB-Ext IE is applied only to IAB-MT (Integrated Access Backhaul-Mobile Termination). If the logicalChannelGroupIAB-Ext IE is set, the LogicalChannelConfig IE is ignored.

[0088] The terminal device 10 may trigger a BSR according to a predetermined condition. For example, the terminal device 10 may trigger a BSR when any of the following conditions (a1) to (a4) is satisfied for an activated cell group. The following conditions may be referred to as "events." (a1) For a logical channel belonging to a certain LCG, uplink data becomes available in the MAC entity, and one of the following two conditions is met: The uplink data belongs to a logical channel that has a higher priority than the logical channel containing available uplink data that belongs to any LCG. There are no logical channels with available uplink data belonging to any LCG. (a2) Uplink resources are allocated, and the number of padding bits is equal to or greater than the combined size of the BSR MAC CE and its subheader. (a3) The retxBSR-Timer expires and at least one logical channel belonging to the LCG contains uplink data. (a4) The periodic BSR-Timer expires.

[0089] The BSR includes at least a regular BSR, a padding BSR, and a periodic BSR. The regular BSR, the padding BSR, and the periodic BSR may be triggered based on different conditions. For example, the terminal device 10 triggers a regular BSR when any of the above conditions (a1) and (a3) ​​is satisfied. The terminal device 10 triggers a padding BSR when the above condition (a2) is satisfied. The terminal device 10 triggers a periodic BSR when the above condition (a4) is satisfied.

[0090] The BSR includes multiple formats. The multiple formats include at least a short BSR and a long BSR. The MAC PDU including the BSR includes a MAC subheader. The MAC subheader includes a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID). The value of the LCID or eLCID may be referred to as a codepoint. The codepoint value identifies the short BSR and the long BSR.

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

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

[0093] The second part 920 consists of 5 bits. The second part 920 is information for identifying the total amount of data available for all logical channels included in the LCG indicated by the first part 910. The second part 920 may also be simply referred to as the "buffer size." The second part 920 indicates an index indicating the number of bytes. For example, the second part 920 indicates any value from 0 to 31.

[0094] The short BSR may include a truncated format, which is a format for a high-priority logical channel, and an extended format, which is a format capable of transmitting a larger amount of information.

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

[0096] The LCG field 1010 is composed of 8 bits. In the LCG field 1010, the 8 bits correspond to 8 LCGi, respectively. Here, i is an integer from 0 to 7. The definition of i will remain the same in the following description. The LCG field 1010 may indicate whether a buffer size field for LCGi exists. 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.

[0097] The number of fields included in the buffer size field 1020 varies depending on the value of the LCG field 1010. In the example of Fig. 10, it is assumed that the bit corresponding to LCG1 is 1 and the bit corresponding to LCG2 is 1 in the LCG field 1010. Therefore, the buffer size field 1020 includes a field 1021 corresponding to LCG1 and a field 1022 corresponding to LCG2. Note that, since it is assumed that the bit corresponding to LCG0 is 0 in Fig. 10, the buffer size field 1020 does not include a field corresponding to LCG0.

[0098] Each field included in the buffer size field 1020 is made up of 8 bits. Each field indicates an index that indicates the number of bytes. For example, each field indicates one of the values ​​from 0 to 254.

[0099] Like the short BSR, the long BSR may include a truncated format and an extended format.

[0100] The BSR may also include a preemptive BSR format and an extended preemptive BSR format, which are used in the IAB-MT.

[0101] The terminal device 10 may select either a short BSR or a long BSR according to a predetermined method. For example, in the case of regular BSR and periodic BSR, the terminal device 10 may select either a short BSR or a long BSR as follows: When a MAC PDU including a BSR is built, if two or more LCGs have available data for transmission, the terminal device 10 transmits long BSRs for all LCGs that have available data. Otherwise, the terminal device 10 transmits short BSRs.

[0102] In the case of regular BSR and periodic BSR, for a MAC entity for which the logicalChannelGroup-IABExt IE is configured by a higher layer, the terminal device 10 may select either a short BSR or a long BSR as follows: If two or more LCGs have available data for transmission and the maximum value of LCG IDs among the configured LCGs is less than or equal to 7, the terminal device 10 transmits a long BSR for all LCGs that have available data. If two or more LCGs have available data for transmission and the maximum value of LCG IDs among the configured LCGs is greater than 7, the terminal device 10 transmits an extended long BSR for all LCGs that have available data. If one or more LCGs have available data for transmission, the terminal device 10 transmits an extended short BSR.

[0103] Also, in the case of a padding BSR, the 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 Truncated BSR Extended Long Truncated BSR

[0104] Note that, if at least one BSR is triggered by any of the above conditions (a1) to (a4) and is not canceled, the terminal device 10 may perform the following process: For example, if UL-SCH resources are available for new transmission and the UL-SCH resources can accommodate a BSR MAC CE and its subheader as a result of LCP (Logical Channel Prioritization), the terminal device 10 may generate a BSR MAC CE and transmit the BSR MAC CE.

[0105] When a regular BSR is triggered and the logicalChannelSR-DelayTimer is not running, the terminal device 10 may trigger an SR if the following condition (b1) or (b2) is satisfied. (b1) No UL-SCH resources are available for new transmissions. (b2) The UL-SCH resources available for the new transmission do not satisfy the LCP mapping restriction configured for the logical channel that triggered the BSR.

[0106] The LCP mapping restriction may be the restriction described in Section 5.4.3.1 of Non-Patent Document 2. The restriction may be a restriction set by RRC. The restriction may include, for example, at least one of a restriction on allowed subcarrier spacing for transmission (e.g., allowedSCS-List), a restriction on the maximum PUSCH duration allowed for transmission (e.g., maxPUSCH-Duration), a restriction on whether CG type 1 can be used for transmission (e.g., configuredGrantType1Allowed), a restriction on cells allowed for transmission (e.g., allowedServingCells), a restriction on CGs allowed for transmission (e.g., allowedCG-List), a restriction on allowed PHY priority indices of dynamic grants (DGs) for transmission (e.g., allowedPHY-PriorityIndex), and a restriction on allowed uplink HARQ modes for transmission (e.g., allowedHARQ-mode).

[0107] Furthermore, if the following condition (c1) is satisfied, the terminal device 10 may cancel all triggered BSRs. Furthermore, if the following condition (c2) is satisfied, the terminal device 10 may cancel all BSRs triggered before MAC PDU assembly. (c1) The uplink grant can accommodate all pending data available for transmission, but is not sufficient to additionally accommodate the BSR MAC CE and its subheader. (c2) A MAC PDU is transmitted, the MAC PDU containing a long, extended long, short, or extended short BSR MAC CE, and the BSR MAC CE containing buffer status up to and including the last event that triggered a BSR before MAC PDU assembly.

[0108] 1.5. Extended Reality (XR) This section explains 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. The multiple data streams corresponding to the above data each have different traffic characteristics and quality of service (QoS) requirements.

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

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

[0111] PDU set: A set of one or more PDUs that carry a payload of one unit of information generated at the application level, which corresponds to, for example, a frame or a video slice in an XR service. Data Burst: A set of data multiple PDUs generated and transmitted by an application in a short period of time.

[0112] Furthermore, in XR, a Packet Delay Budget (PDB) requirement is being considered as one of the above QoS requirements. The PDB is the upper bound of the packet delay time allowed between the terminal device 10 and the UPF. Reference 1 also describes that the following new QoS parameters may be introduced: PDU-Set Delay Budget (PSDB): This is the upper bound of the delay time of a PDU set that is allowed 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 a sender and all PDUs in the PDU set that are not successfully delivered to the corresponding upper layer of the receiver.

[0113] 1.6. Delay Information Report Basic Configuration As described above, in the BSR described in Non-Patent Documents 2 and 3, a terminal device can transmit only one piece of information (i.e., information on buffer size) for predetermined data (i.e., uplink data corresponding to one LCG). Since the amount of information reported to the base station device is small, there is a possibility that the base station device will not be able to appropriately allocate radio resources to the terminal device.

[0114] In consideration of the above, this embodiment provides a procedure for transmitting information related to delay by the terminal device 10. Hereinafter, the "information related to delay" will be referred to as "delay information". The terminal device 10 transmits a report including delay information about predetermined data to the base station device 20. Hereinafter, the "report including delay information" will be referred to as a "delay information report". The delay information report may also be referred to as a "Delay Status Report (DSR)".

[0115] The above-mentioned predetermined data means a unit of data to be reported in a delay information report. Hereinafter, the above-mentioned predetermined data may be referred to as "data to be reported" or "unit of data to be reported." According to this configuration, the terminal device 10 can transmit delay information about the data to be reported to the base station device 20.

[0116] The unit of data to be reported may be data corresponding to one LCG. The one LCG may include one or more LCHs (i.e., data corresponding to one or more LCHs). In this configuration, the unit of data to be reported may be a part or all of the data available for one LCG. Note that the unit of data to be reported may be data corresponding to one LCH. The unit of data to be reported may be a part or all of the data available for one LCH.

[0117] The unit of data to be reported may be data corresponding to one PDU. In this configuration, the unit of data to be reported may be a portion of or all of the data available for one PDU. Also, the unit of data to be reported may be data corresponding to one PDU set. In this configuration, the unit of data to be reported may be a portion of or all of the data available for one PDU set. Furthermore, the unit of data to be reported may be data corresponding to multiple PDU sets. For example, the unit of data to be reported may be data (or a portion of data) available for one, multiple, or all PDUs (or PDU sets) belonging to one PDU set.

[0118] The unit of data to be reported may be data corresponding to one data burst. In this configuration, the unit of data to be reported may be a portion or all of the data available for one data burst. Note that the unit of data to be reported may be data corresponding to multiple data bursts. For example, the unit of data to be reported may be data (or a portion of data) available for one, multiple, or all of the data (or data burst) belonging to one data burst.

[0119] The delay information may be information that explicitly indicates a delay. For example, the delay information may be a delay time. The delay information may be an index that indicates a delay time.

[0120] The delay information may be information relating to other time periods. For example, the delay information may be information relating to a time limit for transmission of data. The transmission limit may be referred to as a "transmission deadline" or an "upper bound of delay."

[0121] The delay information may be the remaining time until a predetermined first deadline is reached. The first deadline may be a deadline for completing transmission of part or all of the data to be reported. For example, the first deadline may be the earliest deadline among multiple deadlines for completing transmission of part of the data to be reported. The first deadline may be a deadline determined based on the PDB or PSDB. The PDB or PSDB may be determined based on the corresponding QoS flow. The PDB or PSDB may be provided to the terminal device 10 by the core network 30. The first deadline for a PDU set may be a value calculated by adding the PDB or PSDB of the corresponding QoS flow to the time when data corresponding to a PDU in the PDU set is first buffered in the terminal device 10 or first arrives at the MAC entity. The first deadline for a data burst may be a value calculated by adding the PDB or PSDB of the corresponding QoS flow to the time when data corresponding to a PDU constituting the data burst is first buffered in the terminal device 10 or first arrives at the MAC entity.

[0122] The remaining time may be a value obtained by subtracting the period during which the predetermined data (that is, the data to be reported) is buffered in the terminal device 10 from the PDB or PSDB of the corresponding QoS flow.

[0123] The remaining time may be a period from a predetermined first time to a first deadline. The first time may be the current time. The first time may be the time when an uplink grant for transmitting a delay information report is allocated. The first time may be the time when the predetermined data (i.e., data to be reported) is buffered in the terminal device 10. The first time may be the time when the data to be reported arrives at a MAC entity in the terminal device 10. In such a configuration, the first deadline may be calculated by adding the PDB or PSDB to the first time.

[0124] The delay information may be information that implicitly indicates a delay. For example, the delay information may be information about data to which a time constraint or requirement is imposed among the data to be reported. Hereinafter, the entire data to be reported will be referred to as "first data," and the data to which a time constraint or requirement is imposed among the data to be reported will be referred to as "second data." The delay information may be information about the size of the second data. For example, the delay information may be an index indicating the number of bytes of the second data.

[0125] The second data is data that should be transmitted with priority. The second data may be referred to as urgent data. The second data may be data that satisfies a delay condition. For example, the second data may be data for which the above-mentioned first deadline is set. The second data may be data for which the above-mentioned remaining time is equal to or less than a predetermined first threshold Th1. The base station device 20 may transmit an RRC message including information indicating the first threshold Th1 to the terminal device 10. The first threshold Th1 may be set for the LCH. For example, the first threshold Th1 may be set as a new element of the LogicalChannelConfig IE. The first threshold Th1 may be set for the LCG. For example, the first threshold Th1 may be set as a new element of the logicalChannelGroup IE. The first threshold Th1 may be set for a PDU or a PDU set. The first threshold Th1 may be set for an IE related to a PDU or a PDU set included in the RRC message. The first threshold Th1 may be set for a data burst. The first threshold value Th1 may be set in an IE related to a data burst included in the RRC message. Note that the base station device 20 may transmit system information (SI, for example, SIB1 and / or an SIB other than SIB1) including information indicating the first threshold value Th1 to the terminal device 10. The base station device 20 may transmit DCI including information indicating the first threshold value Th1 to the terminal device 10.

[0126] In another example, the second data may be data that has a constraint or requirement regarding time-varying delay such as jitter, etc. In yet another example, the second data may be data that has a transmission rate constraint or requirement.

[0127] The base station device 20 can determine the degree of delay based on the size of the second data. If the size of the second data is larger than a predetermined size, the base station device 20 may determine that a delay has occurred in the transmission of the terminal device 10. If the size of the second data is equal to or smaller than the predetermined size, the base station device 20 may determine that no delay has occurred in the transmission of the terminal device 10.

[0128] 1.6.2. Delay Information Report Structure The terminal device 10 may transmit a MAC CE including delay information as a delay information report. For example, the terminal device 10 may transmit a BSR including a delay information report. In this configuration, the terminal device 10 may transmit a BSR including a delay information report according to the following procedure.

[0129] As shown in FIG. 11, the communication unit 220 of the base station device 20 transmits an RRC message to the terminal device 10 (S1101). The RRC message includes parameters related to a BSR. The RRC message may be an RRCReconfiguration message. The control unit 110 of the terminal device 10 generates a BSR based on the parameters included in the RRC message. The BSR includes buffer size information related to the buffer size and delay information. The communication unit 120 of the terminal device 10 transmits the BSR (S1102).

[0130] The terminal device 10 may transmit a long BSR 1200 shown in FIG.

[0131] The first field 1210 may have the same configuration as the LCG field 1010 in Fig. 10. The first field 1210 may also be a field indicating whether the LCGi has available data. For example, if the value of LCGi in the first field 1210 is 1, this may indicate that the LCGi has available data. If the value of LCGi is 0, this may indicate that the LCGi does not have available data.

[0132] In this example, the second field 1220 includes three fields 1221-1223.

[0133] Field 1221 is a field related to LCG1. Field 1221 includes a first portion 1221a and a second portion 1221b. In this example, first portion 1221a is composed of 6 bits, and second portion 1221b is composed of 2 bits. However, this configuration is not limited thereto, and first portion 1221a and second portion 1221b may each be composed of a different number of bits from this example.

[0134] The first portion 1221a represents a buffer size for data corresponding to LCG1. For example, the first portion 1221a may be an index indicating the number of bytes. The control unit 110 may refer to a 6-bit first buffer size table to set the index in the first portion 1221a. The first buffer size table is a table that defines the correspondence between the buffer size and the index.

[0135] The second portion 1221b represents delay information related to the data corresponding to LCG1. The second portion 1221b may be an index representing the delay information. The control unit 110 may refer to a 2-bit delay information table to set the index in the second portion 1221b. The delay information table is a table that defines the correspondence between the delay information and the index.

[0136] Field 1222 is a field related to LCG2. Field 1222 includes a first portion 1222a and a second portion 1222b. The configurations of first portion 1222a and second portion 1222b are the same as those of first portion 1221a and second portion 1221b described above.

[0137] Field 1223 is a field related to LCG3. Field 1223 indicates the buffer size related to the data corresponding to LCG3. Assume that the remaining time for the data corresponding to LCG3 is greater than the first threshold value Th1. That is, the data corresponding to LCG3 is not delayed. In this case, field 1223 may include information related to the buffer size but not delay information. To set an index in field 1223, control unit 110 may refer to a second buffer size table for 8 bits. The second buffer size table is a table that defines the correspondence between buffer sizes and indexes. In this way, control unit 110 may switch between using the first buffer size table and the second buffer size table to set an index corresponding to information related to the buffer size.

[0138] In the above example, the second field 1220 includes three fields 1221 to 1223, but is not limited to this configuration. The number of fields included in the second field 1220 may be variable. In another example, the order of the fields included in the second field 1220 may be determined based on priority.

[0139] 13, each of fields 1221 to 1223 included in second field 1220 may include a first portion corresponding to information related to buffer size and a second portion corresponding to delay information. In the following, only the portions different from the configuration in FIG. 12 will be described, and the portions that are the same as the configuration in FIG. 12 will not be described.

[0140] Field 1223 is a field related to LCG3. Field 1223 includes a first portion 1223a and a second portion 1223b. In this example, first portion 1223a is composed of 6 bits, and second portion 1223b is composed of 2 bits. For example, first portion 1223a may be an index indicating the number of bytes. Control unit 110 may refer to the first buffer size table to set the index in first portion 1223a. As described above, it is assumed that the remaining time for data corresponding to LCG3 is greater than first threshold value Th1. In this case, second portion 1223b may be blank. In another example, second portion 1223b may be a value (or index) indicating that delay information is not reported.

[0141] Furthermore, the configuration of second field 1220 is not limited to the above example. As shown in Fig. 14, second field 1220 may include an 8-bit field 1410 corresponding to information related to buffer size and an 8-bit field 1420 corresponding to delay information. For example, field 1410 represents information related to the buffer size of data corresponding to LCG1, and field 1420 represents delay information related to the data corresponding to LCG1. In this way, buffer size information and delay information related to one LCG may be represented by two different fields.

[0142] Although the configuration of a long BSR has been described in the above example, the present invention is not limited to this example. The above configuration may be applied to a short BSR. For example, the terminal device 10 may transmit a short BSR including delay information (e.g., a buffer size of the second data).

[0143] Although the configuration of a BSR including a delay information report has been described, the present invention is not limited to this configuration. A new MAC CE that transmits delay information may be defined. For example, the terminal device 10 may transmit a MAC CE including delay information as a delay information report. Therefore, "transmission of a BSR including delay information" described in this specification may be replaced with "transmission of a MAC CE including delay information."

[0144] The terminal device 10 may receive first setting information related to the delay information report from the base station device 20. The base station device 20 may transmit an RRC message including the first setting information to the terminal device 10. The base station device 20 may transmit system information (SI, for example, SIB1 and / or an SIB other than SIB1) including the first setting information to the terminal device 10. The base station device 20 may transmit DCI including the first setting information to the terminal device 10.

[0145] The first configuration information may be "information indicating whether to transmit delay information." The first configuration information may indicate "to transmit delay information" or "not to transmit delay information." The first configuration information may be a flag indicating "to transmit delay information" or "not to transmit delay information." For example, the terminal device 10 may transmit delay information when the first configuration information is included in an RRC message. Furthermore, the terminal device 10 may not transmit delay information when the RRC message does not include the first configuration information. The first configuration information may be set for an LCH. The terminal device 10 may determine whether to include delay information related to the LCH in a BSR based on the first configuration information set for the LCH. For example, when the first configuration information indicates to transmit delay information for a certain LCH, the terminal device 10 may include delay information related to the LCH in a BSR. For example, the first configuration information may be set as a new element of a LogicalChannelConfig IE. The first configuration information may be set for an LCG. The terminal device 10 may determine whether to include delay information related to the LCG in a BSR based on the first configuration information set for the LCG. For example, when the first configuration information indicates that delay information is to be transmitted for a certain LCG, the terminal device 10 may include the delay information for the LCG in the BSR. For example, the first configuration information may be set as a new element of the logicalChannelGroup IE. The first configuration information may be set for a PDU or a PDU set. The terminal device 10 may determine whether to include the delay information for the PDU or PDU set in the BSR based on the first configuration information set for the PDU or PDU set. For example, when the first configuration information indicates that delay information is to be transmitted for a certain PDU or PDU set, the terminal device 10 may include the delay information for the PDU or PDU set in the BSR. The first configuration information may be set in an IE related to a PDU or a PDU set included in an RRC message. The first configuration information may be set for a data burst.The terminal device 10 may determine whether to include delay information related to a data burst in a BSR based on first configuration information set for the data burst. For example, when the first configuration information indicates that delay information is to be transmitted for a certain data burst, the terminal device 10 may include the delay information related to the data burst in a BSR. The first configuration information may be set in an IE related to the data burst included in the RRC message.

[0146] The terminal device 10 may receive second setting information related to the delay information report from the base station device 20. The base station device 20 may transmit an RRC message including the second setting information to the terminal device 10. The base station device 20 may transmit system information (SI, for example, SIB1 and / or an SIB other than SIB1) including the second setting information to the terminal device 10. The base station device 20 may transmit DCI including the second setting information to the terminal device 10.

[0147] The second setting information may indicate a type of data to be reported. In this configuration, the terminal device 10 selects a type of data to be reported based on the second setting information. The terminal device 10 may transmit a delay information report for the selected data.

[0148] The second setting information may be explicit information indicating the type of data to be reported, or may be implicit information indicating the type of data to be reported. Examples of explicit information and implicit information are described below.

[0149] - Explicit information The second configuration information may be information indicating any one of an LCH, an LCG, a PDU, a PDU set, and a data burst.

[0150] -Implicit information The second setting information may be the first setting information described above. In this configuration, the terminal device 10 may select the type of data to be reported in accordance with the IE set in the first setting information.

[0151] When the first configuration information is configured for a MAC cell group, this may indicate that the unit of data to be reported is data corresponding to one LCG. For example, the first configuration information may be configured in an IE related to the MAC cell group included in the RRC message. An example of such an IE is a BSR-config IE. As another example, when the first configuration information is configured for an LCG, this may indicate that the unit of data to be reported is data corresponding to one LCG. For example, the first configuration information may be configured in an IE related to the LCG. An example of such an IE is a logicalChannelGroup IE.

[0152] If the first configuration information is set for a PDU or a PDU set, this may indicate that the unit of data to be reported is data corresponding to a PDU or one or more PDU sets. For example, the first configuration information may be set in an IE related to a PDU or a PDU set included in an RRC message.

[0153] If the first configuration information is set for a data burst, this may indicate that the unit of data to be reported is data corresponding to one or more data bursts. For example, the first configuration information may be set in an IE related to a data burst included in an RRC message.

[0154] For example, the terminal device 10 may perform control so as to trigger (and / or transmit) a delay information report when the RRC message includes information indicating the first threshold Th1. That is, when the RRC message includes information indicating the first threshold Th1, the terminal device 10 may include a delay information report in the BSR based on the first threshold Th1. Furthermore, when the RRC message does not include information indicating the first threshold Th1, the terminal device 10 may perform control so as not to trigger (and / or transmit) a delay information report. That is, when the RRC message does not include information indicating the first threshold Th1, the terminal device 10 may not include a delay information report in the BSR.

[0155] The MAC PDU may include identification information for identifying whether it is a delay information report. For example, the MAC subheader includes an LCID or eLCID value (i.e., a code point). An LCID or eLCID value indicating a delay information report may be defined. The following LCID or eLCID values ​​may be defined based on the type of data to be reported. The MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one LCH. The MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one LCG. The MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one PDU. The MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one or more PDU sets. The MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one or more data bursts.

[0156] If the BSR includes a delay information report, the following LCID or eLCID values ​​may be defined based on the type of data being reported: The BSR includes a delay information report, and the unit of data to be reported is data corresponding to one LCH. The BSR includes a delay information report, and the unit of data to be reported is data corresponding to one LCG. The BSR includes a delay information report, and the unit of data to be reported is data corresponding to one PDU. The BSR includes a delay information report, and the unit of data to be reported corresponds to one or more PDU sets. The BSR includes a delay information report, and the unit of data to be reported is data corresponding to one or more data bursts.

[0157] Additionally, a value of LCID or eLCID may be defined that indicates whether the BSR includes a delay information report and is in one of the following formats: Short BSR Long BSR Short Truncated BSR Long Truncated BSR Extended Short Truncated BSR Extended Long Truncated BSR Pre-emptive BSR Extended Preemptive BSR

[0158] In another example, the MAC CE including the delay information report may include the above-mentioned identification information. For example, the BSR may further include a field including identification information indicating that the BSR includes delay information.

[0159] 1.6.3. Conditions that trigger delay information reporting The terminal device 10 may trigger a delay information report according to a predetermined condition. Hereinafter, the condition is referred to as a "trigger condition." The trigger condition may include at least one of the above conditions (a1) to (a4).

[0160] Furthermore, the trigger condition may include at least one of the following conditions (d1) to (d4): (d1) There is data in which the remaining time is equal to or less than the first threshold value Th1. (d2) The on-duration of discontinuous reception (DRX) has started. (d3) There is a PDU set or a data burst to be transmitted, or a PDU set or a data burst has been buffered. (d4) The PDU set is discarded.

[0161] For example, assume that the terminal device 10 triggers a delay information report due to condition (d1). Here, the unit of data to be reported is data corresponding to an LCG. Furthermore, the first threshold Th1 is 5 ms. As shown in FIG. 15, at time t1, data corresponding to LCG1 satisfies condition (d1). The terminal device 10 triggers a delay information report. The delay information report includes information on the remaining time as delay information for each LCG. The base station device 20 receives the delay information report and recognizes that the remaining time for the data corresponding to LCG1 is 5 ms and that the remaining time for the data corresponding to LCG2 is 8 ms. At time t4, 3 ms after time t1, the data corresponding to LCG1 and the data corresponding to LCG2 satisfy condition (d1). Therefore, the terminal device 10 triggers a delay information report again. However, the remaining times included in the delay information report have only advanced by 3 ms. Therefore, it is highly likely that the information is already known to the base station device 20. In the example of Fig. 15, delay information reports are triggered unnecessarily, which may increase the communication load (i.e., overhead). Note that this problem may occur under conditions other than condition (d1), for example, under any of conditions (a1) to (a4) and (d2) to (d4). It is desired to prevent unnecessary delay information reports from being triggered frequently.

[0162] In consideration of the above, the terminal device 10 determines whether to trigger (or transmit) a delay information report using a predetermined condition that restricts the transmission of the delay information report. Hereinafter, the condition is referred to as a "restriction condition." The restriction condition includes at least one of the following conditions (e1) and (e2): (e1) The first timer is running. (e2) A delay information report for the given data triggered at the current time has already been sent.

[0163] The terminal device 10 does not trigger or transmit a delay information report if the restriction condition is satisfied in a situation where the trigger condition is satisfied. The terminal device 10 triggers or transmits a delay information report if the restriction condition is not satisfied in a situation where the trigger condition is satisfied. Details of each of aspect 1-1 in which condition (e1) is used and aspect 1-2 in which condition (e2) is used will be described below.

[0164] -Aspect 1-1 The above-mentioned first timer is a timer for setting a period during which a delay information report is not triggered or transmitted. In other words, the first timer is a prohibition timer for prohibiting triggering or transmission of a delay information report. The first timer expires after a predetermined period. The period of the first timer may be selected from among a plurality of values. The terminal device 10 does not trigger or transmit a delay information report while the first timer is running. When the first timer is not running, the terminal device 10 triggers or transmits a delay information report. For example, when information indicating the first timer is included in an RRC message, the terminal device 10 may perform control to trigger (and / or transmit) a delay information report. That is, the terminal device 10 may not trigger or transmit a delay information report while information indicating the first timer is included in an RRC message and the first timer is running. Furthermore, the terminal device 10 may trigger or transmit a delay information report while the RRC message includes information indicating the first timer and the first timer is not running. Furthermore, the terminal device 10 may perform control so as not to trigger or transmit a delay information report when the RRC message does not include information indicating the first timer.

[0165] 16, the control unit 110 determines whether the trigger condition is satisfied (S1601). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not transmit a delay information report.

[0166] On the other hand, if the trigger condition is satisfied, the control unit 110 determines whether the condition (e1) is satisfied (S1602). If the condition (e1) is satisfied, the communication unit 120 does not transmit a delay information report. On the other hand, if the condition (e1) is not satisfied, the communication unit 120 transmits a delay information report (S1603).

[0167] Based on the delay information report, the control unit 210 of the base station device 20 allocates radio resources to the terminal device 10. The control unit 210 may preferentially allocate radio resources to data that has experienced a delay.

[0168] Note that condition (e1) may be applied to a specific condition among the trigger conditions. For example, condition (e1) may be applied to condition (d1). For example, when condition (d1) is satisfied and condition (e1) is also satisfied, the communication unit 120 does not transmit a delay information report. When condition (d1) is satisfied and condition (e1) is not satisfied, the communication unit 120 transmits a delay information report. When at least one of conditions (a1) to (a4) and (d2) to (d4) is satisfied, the communication unit 120 may transmit a delay information report without determining whether condition (e1) is satisfied. In another example, when condition (d1) is satisfied, the terminal device 10 may start or restart the first timer. When at least one of conditions (a1) to (a4) and (d2) to (d4) is satisfied, the terminal device 10 may not start or restart the first timer. Transmission of delay information reports is more likely to occur for condition (d1) than for other conditions. This configuration can effectively prevent unnecessary delay information reports from being frequently triggered.

[0169] Note that only the transmission of a BSR including a delay information report may be restricted using a restriction condition. That is, condition (e1) may be applied to a BSR including a delay information report, and condition (e1) may not be applied to a BSR not including a delay information report (i.e., a BSR shown in FIG. 9 or 10). Therefore, even if condition (e1) is satisfied, communication unit 120 may transmit a BSR not including a delay information report.

[0170] The first timer may be started or restarted when a delay information report is triggered or transmitted. In a configuration in which a BSR includes a delay information report, the first timer may be started or restarted when the BSR is triggered or transmitted. In another example, the first timer may be started or restarted when a BSR including a delay information report is triggered or transmitted. That is, the first timer may not be started or restarted when a BSR not including a delay information report is triggered or transmitted.

[0171] Also, in a configuration in which the BSR includes a delay information report, the first timer may be used as a period during which an SR is not triggered or transmitted. That is, the terminal device 10 does not trigger or transmit an SR while the first timer is running.

[0172] The terminal device 10 may store information regarding the first timer in the terminal device 10 itself in advance. The terminal device 10 may receive information regarding the first timer from the base station device 20. The base station device 20 may select one value from a plurality of values ​​related to the first timer and transmit the selected value to the terminal device 10. The base station device 20 may transmit an RRC message including information regarding the first timer to the terminal device 10. The base station device 20 may transmit system information (SI, for example, SIB1 and / or an SIB other than SIB1) including information regarding the first timer to the terminal device 10. The base station device 20 may transmit DCI including information regarding the first timer to the terminal device 10.

[0173] The information about the first timer may be included in a parameter related to the BSR, for example, the information about the first timer may be included in a BSR-config IE.

[0174] The first timer may be set for an LCH or an LCG. Information about the first timer may be set in an IE related to the LCH or the LCG. Examples of such IEs include a LogicalChannelConfig IE and a logicalChannelGroup IE. In this configuration, when a delay information report for the LCH or the LCG for which the first timer is set is triggered or transmitted, the first timer is started or restarted. Therefore, while the first timer is running, a delay information report for the LCH or the LCG for which the first timer is set is not triggered or transmitted.

[0175] The first timer may be set for a PDU or a PDU set. Information about the first timer may be set in an IE associated with the PDU or the PDU set. For example, information about the first timer may be set in an IE associated with the PDU or the PDU set included in an RRC message. In this configuration, when a delay information report is triggered or transmitted for the PDU or the PDU set for which the first timer is set, the first timer is started or restarted. Therefore, while the first timer is running, a delay information report for the PDU or the PDU set for which the first timer is set is not triggered or transmitted.

[0176] The first timer may be set for the data burst. Information about the first timer may be set in an IE associated with the data burst. For example, the information about the first timer may be set in an IE associated with the data burst included in an RRC message. In this configuration, when a delay information report is triggered or transmitted for the data burst for which the first timer is set, the first timer is started or restarted. Therefore, while the first timer is running, a delay information report for the data burst for which the first timer is set is not triggered or transmitted.

[0177] The terminal device 10 may receive third setting information related to the delay information report from the base station device 20. The base station device 20 may transmit an RRC message including the third setting information to the terminal device 10. The base station device 20 may transmit system information (SI, for example, SIB1 and / or an SIB other than SIB1) including the third setting information to the terminal device 10. The base station device 20 may transmit DCI including the third setting information to the terminal device 10.

[0178] The third configuration information may be "information indicating whether to apply the first timer." The third configuration information may indicate "to apply the first timer" or "to not apply the first timer." The third configuration information may be a flag indicating "to apply the first timer" or "to not apply the first timer." The third configuration information may be configured for the LCH. For example, the third configuration information may be configured as a new element of the LogicalChannelConfig IE. The third configuration information may be configured for the LCG. For example, the third configuration information may be configured as a new element of the logicalChannelGroup IE. The third configuration information may be configured for a PDU or a PDU set. The third configuration information may be configured in an IE related to a PDU or a PDU set included in an RRC message. The third configuration information may be configured for a data burst. The third configuration information may be configured in an IE related to a data burst included in an RRC message.

[0179] When third configuration information indicating that the first timer is not applied is set for an LCH or an LCG and a delay information report for the LCH or LCG is triggered, the terminal device 10 may stop the first timer. When third configuration information indicating that the first timer is not applied is set for a PDU or a PDU set and a delay information report for the PDU or the PDU set is triggered, the terminal device 10 may stop the first timer. When third configuration information indicating that the first timer is not applied is set for a data burst and a delay information report for the data burst is triggered, the terminal device 10 may stop the first timer.

[0180] -Aspect 1-2 If the condition (e2) is satisfied, it means that a delay information report for the currently triggered predetermined data has been transmitted in the past. If the condition (e2) is satisfied, it may mean that the delay information report for the currently triggered predetermined data is included in a previously transmitted delay information report. If the condition (e2) is not satisfied, it means that a delay information report for the currently triggered predetermined data has not yet been transmitted, that is, a delay information report for new data has been triggered.

[0181] In the example of FIG. 15, a delay information report is triggered for data corresponding to LCG1 and data corresponding to LCG2 at time t4. However, delay information reports for these data have already been transmitted at time t1. In such a case, condition (e2) is satisfied, and therefore the terminal device 10 does not transmit a delay information report at time t4. For example, if a delay information report for new data (e.g., data corresponding to LCG3) is subsequently triggered, condition (e2) is not satisfied. Therefore, the terminal device 10 transmits a delay information report for the data corresponding to LCG3.

[0182] If the condition (e2) is not satisfied, the delay information report to be transmitted may include delay information reports that have already been transmitted and delay information reports for new data. If the condition (e2) is not satisfied, the delay information report to be transmitted may include only delay information reports for new data.

[0183] 17, the control unit 110 determines whether the trigger condition is satisfied (S1701). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not transmit a delay information report.

[0184] On the other hand, if the trigger condition is satisfied, the control unit 110 determines whether the condition (e2) is satisfied (S1702). If the condition (e2) is satisfied, the communication unit 120 does not transmit a delay information report. On the other hand, if the condition (e2) is not satisfied, the communication unit 120 transmits a delay information report (S1703).

[0185] Note that condition (e2) may be applied to a specific condition among the trigger conditions. For example, condition (e2) may be applied to condition (d1). For example, if condition (d1) is satisfied and condition (e2) is also satisfied, the communication unit 120 does not transmit a delay information report. If condition (d1) is satisfied and condition (e2) is not satisfied, the communication unit 120 transmits a delay information report. If at least one of conditions (a1) to (a4) and (d2) to (d4) is satisfied, the communication unit 120 may transmit a delay information report without determining whether condition (e2) is satisfied. Condition (d1) is more likely to result in the transmission of delay information reports more frequently than other conditions. This configuration can effectively prevent unnecessary delay information reports from being frequently triggered.

[0186] If the unit of data to be reported corresponds to one or more PDU sets, the terminal device 10 may operate as follows: Assume that a trigger condition (e.g., condition (d1)) is met for a certain PDU and a delay information report for the PDU set to which that PDU belongs is transmitted. After that, even if the trigger condition is met for another PDU included in the PDU set to which that PDU belongs, the terminal device 10 does not trigger or transmit a delay information report for that PDU set.

[0187] According to the above configuration, by applying at least one of the conditions (e1) and (e2), it is possible to prevent unnecessary delay information reports from being frequently triggered, thereby reducing the possibility of an increase in communication load.

[0188] Note that the aspects 1-1 and 1-2 may be combined. That is, the terminal device 10 may trigger or transmit a delay information report using the conditions (e1) and (e2). For example, when the trigger condition is satisfied but both the conditions (e1) and (e2) are not satisfied, the communication unit 120 may transmit a delay information report.

[0189] In another example, one of the conditions (e1) and (e2) may take priority. For example, when the control unit 110 starts the flow of FIG. 18, it determines whether the trigger condition is satisfied (S1801). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not transmit a delay information report.

[0190] On the other hand, if the trigger condition is satisfied, the control unit 110 determines whether the condition (e1) is satisfied (S1802). If the condition (e1) is satisfied, the control unit 110 determines whether the condition (e2) is satisfied (S1803). If the condition (e2) is satisfied, the communication unit 120 does not transmit a delay information report.

[0191] On the other hand, if the condition (e1) is not satisfied in step S1802, the communication unit 120 transmits a delay information report (S1804). Also, if the condition (e2) is not satisfied in step S1803, the communication unit 120 transmits a delay information report (S1804).

[0192] In this way, when the condition (e1) is satisfied and the condition (e2) is not satisfied, the communication unit 120 may transmit a delay information report. That is, even if the first timer is running, when a delay information report for new data is triggered, the communication unit 120 may transmit a delay information report.

[0193] 2. Second embodiment Next, the configuration of the second embodiment will be described. Below, only the parts that are different from the first embodiment will be described, and the parts that are the same as the first embodiment will not be described. Therefore, as long as there is no mutual contradiction, the configuration of the first embodiment and its modified examples can be applied to the configuration described in this embodiment.

[0194] The delay information report includes delay information of uplink data that has a low delay requirement. Therefore, if the transmission of the delay information report is delayed, the delay information report may become unnecessary information for the base station device 20. For example, in the example of FIG. 15, assume that the delay information report that should be transmitted at time t1 is delayed by 5 ms or more. In this case, information regarding the remaining time corresponding to LCG1 may become unnecessary information for the base station device 20. Furthermore, if an unnecessary delay information report is transmitted, the communication load (i.e., overhead) may increase.

[0195] In consideration of the above, in a situation where a delay information report is triggered by the above trigger condition, the terminal device 10 determines whether the available uplink resources can accommodate the delay information report. Based on the determination, the terminal device 10 executes a predetermined process related to the transmission of the delay information report. The above predetermined process includes, for example, at least one of transmitting a scheduling request (SR) and canceling the transmission of the delay information report. Aspects 2-1 and 2-2 will be described below.

[0196] -Aspect 2-1 The terminal device 10 determines whether the following condition (f1) is satisfied in a situation in which a delay information report is triggered. (f1) Uplink resources are available to accommodate the delay information report, i.e., uplink resources are available for new transmission of the delay information report, and uplink resources are available to accommodate the delay information report.

[0197] If the condition (f1) is satisfied, the terminal device 10 transmits a delay information report. On the other hand, if the condition (f1) is not satisfied, that is, if it is determined that the uplink resources cannot accommodate the delay information report, the terminal device 10 executes a process for transmitting an SR as the above-mentioned predetermined process. The above-mentioned process for transmitting an SR may include one or more processes related to the SR. The above-mentioned process for transmitting an SR may include transmitting an SR. Therefore, the terminal device 10 may execute a process for transmitting an SR based on the fact that the uplink resources cannot accommodate the delay information report in a situation in which the delay information report is triggered. The base station device 20 allocates uplink resources to the terminal device 10 in accordance with the SR. The terminal device 10 can transmit the delay information report using the allocated uplink resources.

[0198] 19, the control unit 110 determines whether the trigger condition is satisfied (S1901). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not transmit a delay information report.

[0199] On the other hand, if the trigger condition is met, the control unit 110 determines whether the condition (f1) is met (S1902). If the condition (f1) is met, the communication unit 120 transmits a delay information report (S1903). On the other hand, if the condition (f1) is not met, this means that there are no uplink resources available for the delay information report. Therefore, the communication unit 120 transmits an SR to the base station device 20 (S1904).

[0200] If the condition (f1) is not satisfied, the control unit 110 may determine whether a second timer for delaying the transmission of the SR is running. For example, the second timer may be a logicalChannelSR-DelayTimer. If the second timer is running, the communication unit 120 may not transmit the SR. If the second timer is not running, the communication unit 120 may transmit the SR.

[0201] In another example, the communication unit 120 may transmit an SR even if the second timer is running. That is, the communication unit 120 may transmit an SR regardless of whether the second timer is running. Since the delay information report includes delay information of uplink data that has a low delay requirement, it is preferable that the delay information report be transmitted to the base station device 20 as soon as possible. According to this configuration, uplink resources for transmitting the delay information report can be allocated to the terminal device 10 earlier.

[0202] Note that condition (f1) may be applied to a specific condition among the trigger conditions. For example, condition (f1) may be applied to condition (d1). For example, if condition (d1) is satisfied and condition (f1) is not satisfied, the communication unit 120 transmits an SR. If a delay information report is triggered by condition (d1), this means that there is little time remaining until the transmission of the delay information report is completed. By applying condition (f1) to condition (d1), uplink resources for transmitting the delay information report can be allocated to the terminal device 10 more quickly.

[0203] If condition (f1) is met and the trigger target (i.e., data corresponding to an LCH, LCG, PDU, PDU set, or data burst) does not satisfy the above LCP mapping restrictions, the communication unit 120 does not need to send an SR.

[0204] According to the above configuration, by transmitting an SR, it is possible to allocate uplink resources to the terminal device 10. For example, when a delay information report is triggered by condition (d1), the base station device 20 can receive the delay information report before the first deadline for data corresponding to the delay information included in the delay information report expires. The base station device 20 can appropriately allocate uplink resources to the terminal device 10.

[0205] -Aspect 2-2 The terminal device 10 determines whether the following condition (g1) is satisfied in a situation where a delay information report is triggered. (g1) Uplink resources are available to accommodate the delay information report by the predetermined second deadline, i.e., uplink resources are available for new transmission of the delay information report, and uplink resources are available to accommodate the delay information report by the second deadline.

[0206] The terminal device 10 may determine the second deadline of the condition (g1) based on the remaining time. That is, the second deadline may be the same as the first deadline described above. More specifically, the second deadline may be a deadline by which transmission of part or all of the data to be reported must be completed. The second deadline may be a deadline determined based on the PDB or PSDB. The second deadline may be a deadline determined based on the PDB or PSDB set for part or all of the data to be reported. The second deadline may be a value obtained by adding the PDB or PSDB to the first time. The second deadline may be a value earlier than the value obtained by adding the PDB or PSDB to the first time.

[0207] If the condition (g1) is satisfied, the terminal device 10 transmits a delay information report. On the other hand, if the condition (g1) is not satisfied, the terminal device 10 cancels the transmission or triggering of the delay information report as the above-mentioned predetermined processing. That is, the transmission or triggering of the delay information report is canceled based on the fact that the uplink resources cannot accommodate the delay information report by the second deadline in a situation where the delay information report is triggered. In other words, if the condition (g1) is not satisfied, the terminal device 10 cancels the trigger for the delay information report (that is, the trigger due to the trigger condition being satisfied).

[0208] The condition (g1) may be replaced with a condition that the trigger for the delay information report has not been canceled by the second deadline. Therefore, the terminal device 10 may cancel the transmission or trigger of the delay information report based on the fact that the trigger for the delay information report has not been canceled by the second deadline.

[0209] Furthermore, if there are no uplink resources available for new transmission and capable of accommodating the delay information report before the second deadline has elapsed, the terminal device 10 may cancel the transmission or triggering of the delay information report. In another example, if a delay information report is triggered but the delay information report cannot be transmitted before the delay information included in the delay information report expires, the terminal device 10 may cancel the transmission or triggering of the delay information report.

[0210] 20 starts, the control unit 110 determines whether the trigger condition is satisfied (S2001). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not transmit a delay information report.

[0211] On the other hand, if the trigger condition is satisfied, the control unit 110 determines whether the condition (g1) is satisfied (S2002). If the condition (g1) is satisfied, the communication unit 120 transmits a delay information report (S2003). On the other hand, if the condition (g1) is not satisfied, the communication unit 120 cancels the transmission or triggering of the delay information report (S2004). Note that the control unit 110 may cancel the transmission or triggering of the delay information report and transmit an instruction to cancel to the communication unit 120.

[0212] If the above condition (c1) or (c2) is satisfied, the communication unit 120 may cancel the transmission or trigger of the delay information report.

[0213] Condition (g1) may be applied to a specific condition among the trigger conditions. For example, condition (g1) may be applied to condition (d1). For example, if condition (d1) is satisfied and condition (g1) is not satisfied, the communication unit 120 cancels the transmission or triggering of the delay information report. If the delay information report is triggered by condition (d1), this means that there is little time remaining until the transmission of the delay information report is completed. In such a case, even if the delay information report is transmitted to the base station device 20, the data corresponding to the delay information included in the delay information report may have passed the first deadline. In other words, the delay information included in the delay information report may not be useful information for the base station device 20, but may be unnecessary information. If unnecessary delay information reports are transmitted, the communication load may increase. This configuration makes it possible to prevent the transmission of unnecessary delay information reports.

[0214] The terminal device 10 may start a third timer when a delay information report is triggered (i.e., when a trigger condition is satisfied), and may determine the second deadline based on the third timer. The third timer expires at a predetermined period. The period of the third timer may be selected from among a plurality of values. For example, the terminal device 10 may determine that the condition (g1) is not satisfied when the third timer expires. The terminal device 10 may receive an RRC message including information regarding the third timer from the base station device 20.

[0215] In the configuration of the BSR including the delay information report, information regarding the third timer may be included in an IE related to the BSR (eg, a BSR-Config IE).

[0216] The third timer may be set for an LCH or an LCG. Information about the third timer may be set in an IE related to the LCH or the LCG. Examples of such IEs include a LogicalChannelConfig IE and a logicalChannelGroup IE. In this configuration, the third timer is started when a delay information report for an LCH or an LCG for which the third timer is set is triggered. Therefore, when the third timer expires, transmission or triggering of a delay information report for an LCH or an LCG for which the third timer is set is canceled. Note that a delay information report for an LCH or an LCG for which the third timer is not set may be transmitted. In other words, triggering of a delay information report for an LCH or an LCG for which the third timer is not set does not have to be canceled.

[0217] The third timer may be set for a PDU or a PDU set. Information about the third timer may be set in an IE associated with the PDU or the PDU set. For example, information about the third timer may be set in an IE associated with the PDU or the PDU set included in an RRC message. In this configuration, the third timer is started when a delay information report for the PDU or the PDU set for which the third timer is set is triggered. Therefore, when the third timer expires, transmission or triggering of the delay information report for the PDU or the PDU set for which the third timer is set is canceled. Note that a delay information report for a PDU or a PDU set for which the third timer is not set may be transmitted. In other words, triggering of a delay information report for a PDU or a PDU set for which the third timer is not set does not have to be canceled.

[0218] The third timer may be set for the data burst. Information about the third timer may be set in an IE associated with the data burst. For example, information about the third timer may be set in an IE associated with the data burst included in an RRC message. In this configuration, the third timer is started when a delay information report for the data burst for which the third timer is set is triggered. Therefore, when the third timer expires, transmission or triggering of the delay information report for the data burst for which the third timer is set is canceled. Note that a delay information report for a data burst for which the third timer is not set may be transmitted. In other words, triggering of a delay information report for a data burst for which the third timer is not set does not need to be canceled.

[0219] According to the above configuration, it is possible to prevent unnecessary transmission of delay information reports. Since uplink resources are not used for unnecessary delay information reports, it is possible to reduce the possibility of an increase in communication load.

[0220] Aspect 2-1 and aspect 2-2 may be combined. That is, the terminal device 10 may execute predetermined processing related to the transmission of a delay information report using conditions (f1) and (g1). For example, the control unit 110 may determine whether condition (g1) is satisfied after executing step S1904 of the flow in FIG. 19 . If condition (g1) is not satisfied, the communication unit 120 may cancel the transmission or triggering of the delay information report. In this way, if there are no uplink resources that can accommodate the delay information report by the second deadline after the terminal device 10 transmits the SR, the terminal device 10 may cancel the transmission or triggering of the delay information report.

[0221] 3. Variations Although the present disclosure has been described based on the above embodiment, it is understood that the present disclosure is not limited to the embodiment or structure. The present disclosure also encompasses various modifications and modifications within the equivalent range. Other combinations including one or more elements included in the above embodiment are also within the scope and spirit of the present disclosure.

[0222] 16 to 18, the determination of the restriction condition (condition (e1) and / or (e2)) is performed after the determination of the trigger condition, but this configuration is not limited to this. For example, the determination of the restriction condition may be performed before the determination of the trigger condition. The terminal device 10 may decide whether to determine the trigger condition based on whether the restriction condition is satisfied. For example, if the restriction condition is satisfied, the terminal device 10 does not determine the trigger condition. That is, the delay information report is not triggered. If the restriction condition is not satisfied, the terminal device 10 determines the trigger condition. Therefore, the first embodiment may include "an aspect in which the terminal device 10 cancels the trigger for the delay information report using the restriction condition after the trigger condition is satisfied" and "an aspect in which the terminal device 10 does not determine the trigger condition for the delay information report based on the fact that the restriction condition is satisfied."

[0223] In FIG. 19, the determination of the trigger condition is performed before the determination of the condition (f1), but this configuration is not limiting. For example, the determination of the condition (f1) may be performed before the determination of the trigger condition. The terminal device 10 may decide whether to determine the trigger condition based on whether the condition (f1) is satisfied. If the condition (f1) is satisfied, the terminal device 10 determines the trigger condition. If the condition (f1) is not satisfied, the terminal device 10 executes processing for transmitting an SR. Therefore, aspect 2-1 of the second embodiment may include "an aspect in which the terminal device 10 executes processing for transmitting an SR when the trigger condition is satisfied and the condition (f1) is not satisfied" and "an aspect in which the terminal device 10 executes processing for transmitting an SR without determining the trigger condition when the condition (f1) is not satisfied."

[0224] In FIG. 20, the determination of the trigger condition is performed before the determination of the condition (g1), but this configuration is not limited to this. For example, the determination of the condition (g1) may be performed before the determination of the trigger condition. The terminal device 10 may decide whether to determine the trigger condition based on whether the condition (g1) is satisfied. If the condition (g1) is satisfied, the terminal device 10 determines the trigger condition. If the condition (g1) is not satisfied, the terminal device 10 does not determine the trigger condition. That is, the delay information report is not triggered. Therefore, aspect 2-2 of the second embodiment may include "an aspect in which the terminal device 10 cancels a trigger for a delay information report (i.e., a trigger due to the trigger condition being satisfied) if the condition (g1) is not satisfied" and "an aspect in which the terminal device 10 does not determine the trigger condition for a delay information report if the condition (g1) is not satisfied."

[0225] The words, phrases, and other expressions used in the above embodiments are merely examples 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 technical specifications (e.g., technical specifications cited in this specification).

[0226] The information transmitted and received in the above embodiment may be contained in the same or a different message or element already described in the technical specifications, or may be contained in a newly defined message or element. The information transmitted and received in the above embodiment may be transmitted and received using a different layer and / or a different channel than those in the above embodiment.

[0227] The means and / or functions provided by the devices described in the above embodiments can be provided by software recorded in a tangible memory device and a computer that executes the software, software alone, hardware alone, or a combination thereof. For example, if any of the above devices is provided by electronic circuits that are hardware, it can be provided by digital circuits including a large number of logic circuits, or analog circuits.

[0228] The device described in the above embodiment executes a program stored in a non-transitory tangible storage medium, and the execution of the program executes a method corresponding to the program.

[0229] 4. Additional Notes Some or all of the above embodiments and modified examples may be described as, but are not limited to, the following notes. Hereinafter, a relationship is expressed in which a note that is subordinate to multiple notes is subordinate to another note that is subordinate to multiple notes. All of the following subordinate relationships of notes are included in the above embodiments.

[0230] (Appendix 1) a control unit (110) configured to determine whether available uplink resources can accommodate a delay information report in a situation where a delay information report including delay information regarding a delay for a predetermined data is triggered; a communication unit (120) configured to execute a predetermined process related to the transmission of the delay information report based on the determination; A terminal device (10) comprising:

[0231] (Appendix 2) The communication unit Based on the available uplink resources being unable to accommodate the delay information report in a situation where the delay information report is triggered, The predetermined processing is configured to execute a processing for transmitting a scheduling request (SR). 10. The terminal device according to claim 1.

[0232] (Appendix 3) The communication unit In a situation where the delay information report is triggered, if the available uplink resources cannot accommodate the delay information report and a timer for delaying the transmission of the SR is running, not performing a process for transmitting the SR; When the delay information report is triggered, if the available uplink resources cannot accommodate the delay information report and the timer is not running, perform a process for transmitting the SR. It is configured as follows: 10. A terminal device as described in Appendix 2.

[0233] (Appendix 4) the communication unit is configured to receive a radio resource control (RRC) message from a base station device (20); The timer is a logicalChannelSR-DelayTimer included in the RRC message. 4. A terminal device as described in Appendix 3.

[0234] (Appendix 5) The communication unit In a situation where the delay information report is triggered, even if the available uplink resources cannot accommodate the delay information report and a timer for delaying the transmission of the SR is running, a process for transmitting the SR is performed. It is configured as follows: 10. A terminal device as described in Appendix 2.

[0235] (Appendix 6) the communication unit is configured to receive a radio resource control (RRC) message from a base station device (20); The timer is a logicalChannelSR-DelayTimer included in the RRC message. 6. The terminal device according to claim 5.

[0236] (Appendix 7) The control unit uses a trigger condition related to the remaining time until the deadline for transmitting the predetermined data to generate the delay information report. of configured to trigger, The communication unit If the remaining time is equal to or less than a predetermined threshold and the available uplink resources cannot accommodate the delay information report, perform a process for transmitting the SR. It is configured as follows: 10. A terminal device as described in Appendix 2.

[0237] (Appendix 8) The communication unit Based on the fact that the available uplink resources cannot accommodate the delay information report by a predetermined time limit in a situation in which the delay information report is triggered, The predetermined process is configured to cancel transmission or trigger of the delay information report. 10. The terminal device according to claim 1.

[0238] (Appendix 9) the control unit is configured to trigger the delay information report using a trigger condition related to a remaining time until a deadline for transmitting the predetermined data is reached; The communication unit configured to cancel transmission or triggering of the delay information report if the remaining time is equal to or less than a predetermined threshold and the available uplink resources cannot accommodate the delay information report by the predetermined deadline. 9. The terminal device according to claim 8.

[0239] (Appendix 10) The control unit configured to determine the predetermined deadline based on the remaining time. 10. The terminal device according to claim 9.

[0240] (Appendix 11) The control unit and determining the predetermined deadline based on a Packet Delay Budget (PDB) or a Protocol Data Unit-Set Delay Budget (PSDB). 9. The terminal device according to claim 8.

[0241] (Appendix 12) The control unit starting a timer when the delay information report is triggered; Determine the predetermined deadline based on the timer It is configured as follows: 9. The terminal device according to claim 8.

[0242] (Appendix 13) the communication unit is configured to receive a radio resource control (RRC) message from a base station device (20); The timer is included in the RRC message. 13. The terminal device of claim 12.

[0243] (Appendix 14) The delay information report is a buffer status report (BSR) including the delay information and buffer size information regarding a buffer size. A terminal device according to any one of Supplementary Notes 1 to 13.

[0244] (Appendix 15) The delay information is information about delay times, or Information about data subject to time constraints or requirements That is, A terminal device according to any one of Supplementary notes 1 to 14.

[0245] (Appendix 16) The predetermined data is Data corresponding to one logical channel, Data corresponding to one Logical Channel Group (LCG), Data corresponding to one or more Protocol Data Unit Sets (PDU Sets), or Data corresponding to one or more Data Bursts That is, 16. A terminal device according to any one of Supplementary Notes 1 to 15.

[0246] (Appendix 17) In a situation where a delay information report including delay information regarding a delay for a predetermined data is triggered, determining whether available uplink resources can accommodate the delay information report; Based on the determination, performing a predetermined process related to transmitting the delay information report; A method for a terminal device (10) comprising:

[0247] (Appendix 18) A processor (101) in a terminal device (10) In a situation where a delay information report including delay information regarding a delay for a predetermined data is triggered, determining whether available uplink resources can accommodate the delay information report; Based on the determination, performing a predetermined process related to transmitting the delay information report; A program that executes the following.

[0248] (Appendix 19) A processor (101) in a terminal device (10) In a situation where a delay information report including delay information regarding a delay for a predetermined data is triggered, determining whether available uplink resources can accommodate the delay information report; Based on the determination, performing a predetermined process related to transmitting the delay information report; A non-transient tangible recording medium on which a program for executing the above is recorded.

[0249] (Appendix 20) a communication unit (220) configured to receive a delay information report from the terminal device (10), the delay information including delay information regarding a delay for a predetermined data; a control unit (210) configured to allocate radio resources to the terminal device based on the delay information report; Equipped with In a situation where the delay information report is triggered in the terminal device, if an uplink resource available in the terminal device cannot accommodate the delay information report, the communication unit is configured to receive a scheduling request (Scheduling Request, SR) from the terminal device. Base station equipment (20).

[0250] (Appendix 21) The control unit is configured to allocate radio resources to the terminal device in accordance with the SR. 21. The base station apparatus according to claim 20.

[0251] (Appendix 22) receiving a delay information report from a terminal device (10) including delay information regarding a delay for a predetermined data; Based on the delay information report, a radio resource is allocated to the terminal device. puppy And, In a situation where the delay information report is triggered in the terminal device, if the uplink resources available in the terminal device cannot accommodate the delay information report, receiving a scheduling request (SR) from the terminal device; A method for a base station device (20) including:

[0252] (Appendix 23) A processor (201) in a base station device (20) receiving a delay information report from a terminal device (10) including delay information regarding a delay for a predetermined data; Based on the delay information report, a radio resource is allocated to the terminal device. puppy And, In a situation where the delay information report is triggered in the terminal device, if the uplink resources available in the terminal device cannot accommodate the delay information report, receiving a scheduling request (SR) from the terminal device; A program that executes the following.

[0253] (Appendix 24) A processor (201) in a base station device (20) receiving a delay information report from a terminal device (10) including delay information regarding a delay for a predetermined data; Based on the delay information report, a radio resource is allocated to the terminal device. puppy And, In a situation where the delay information report is triggered in the terminal device, if the uplink resources available in the terminal device cannot accommodate the delay information report, receiving a scheduling request (SR) from the terminal device; A non-transient tangible recording medium on which a program for executing the above is recorded.

[0254] (Appendix 25) a receiving unit (122) that receives, from a base station device (20), a radio resource control (RRC) message including information for setting an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling a trigger of a delay status report (DSR); a control unit (110) that controls triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; Equipped with The control unit cancels the DSR that has been triggered and has not been canceled when the data of the LCG associated with the DSR expires. Terminal device (10).

[0255] (Appendix 26) The DSR is a field whose bits indicate whether a buffer size field for each LCG is present; a field indicating the time remaining for the earliest deadline for the data of the LCG; a field indicating a buffer size for the LCG; Including, 26. The terminal device of claim 25.

[0256] (Appendix 27) The control unit switching between a first table and a second table different from the first table, and setting the field indicating the buffer size; 27. The terminal device of claim 26.

[0257] (Appendix 28) The DSR is a field whose bits indicate whether a buffer size field for each LCG is present; a field containing information about data of the LCG whose remaining time is below the threshold; Including, 26. The terminal device of claim 25.

[0258] (Appendix 29) The DSR is a Medium Access Control Element (MAC CE) including a subheader including an extended Logical Channel Identifier (eLCID) for identifying the DSR. A terminal device according to any one of Supplementary notes 25 to 28.

[0259] (Appendix 30) receiving a Radio Resource Control (RRC) message from a base station device (20), the message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling triggering of a Delay Status Report (DSR); Controlling the triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; canceling the DSR that has been triggered and not canceled when the data of the LCG associated with the DSR expires; Contains A method for a terminal device (10).

[0260] (Appendix 31) The DSR is a field whose bits indicate whether a buffer size field for each LCG is present; a field indicating the time remaining for the earliest deadline for the data of the LCG; a field indicating a buffer size for the LCG; Including, 31. A method for a terminal device according to claim 30.

[0261] (Appendix 32) and switching between a first table and a second table different from the first table to set the field indicating the buffer size. 32. A method for a terminal device according to claim 31.

[0262] (Appendix 33) The DSR is a field whose bits indicate whether a buffer size field for each LCG is present; a field containing information about data of the LCG whose remaining time is below the threshold; Including, 31. A method for a terminal device according to claim 30.

[0263] (Appendix 34) The DSR is a Medium Access Control Element (MAC CE) including a subheader including an extended Logical Channel Identifier (eLCID) for identifying the DSR. A method for a terminal device according to any one of Supplementary Notes 30 to 33.

[0264] (Appendix 35) A processor (101) in a terminal device (10) receiving a Radio Resource Control (RRC) message from a base station device (20), the message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling triggering of a Delay Status Report (DSR); Controlling the triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; canceling the DSR that has been triggered and not canceled when the data of the LCG associated with the DSR expires; A program that executes the following.

[0265] (Appendix 36) A processor (101) in a terminal device (10) receiving a Radio Resource Control (RRC) message from a base station device (20), the message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling triggering of a Delay Status Report (DSR); Controlling the triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; canceling the DSR that has been triggered and not canceled when the data of the LCG associated with the DSR expires; A non-transient tangible recording medium on which a program for executing the above is recorded.

[0266] The disclosures of the above prior art documents and references are incorporated herein by reference.

Claims

1. a receiving unit (122) that receives, from a base station device (20), a radio resource control (RRC) message including information for setting an identifier (ID) of a logical channel group (LCG) to which a logical channel (Logical CHannel, LCH) belongs, and information indicating a threshold value for the LCG for triggering a delay status report (DSR); a control unit (110) that triggers the DSR based on the remaining time for the earliest deadline of a given data being below the threshold and the DSR for the given data not being transmitted; Equipped with The control unit cancels the DSR that has been triggered and has not been canceled when the predetermined data associated with the DSR expires. Terminal device (10).

2. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a remaining time field indicating the remaining time for the earliest deadline for data for the LCG; the buffer size field indicating a buffer size for data for the LCG; Including, The terminal device according to claim 1 .

3. The control unit using either a first table or a second table to set the buffer size field indicating the buffer size; The terminal device according to claim 2 .

4. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a field containing information about the size of data for the LCG whose remaining time is below the threshold; Including, The terminal device according to claim 1 .

5. the predetermined data is data for the LCH, The control unit triggering the DSR based on the remaining time for the earliest deadline of data for the LCH being below the threshold and the DSR for data for the LCH not being transmitted; The terminal device according to claim 1 .

6. The DSR is a MAC CE (Medium Access Control Element) identified by an extended logical channel identifier (eLCID) included in a MAC (Medium Access Control) subheader. The terminal device according to any one of claims 1 to 5.

7. receiving a Radio Resource Control (RRC) message from a base station device (20), the message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information indicating a threshold for the LCG for triggering a Delay Status Report (DSR); triggering the DSR based on the remaining time for an earliest deadline for a given data item being below the threshold and the DSR for the given data item not being sent; canceling the DSR that has been triggered and not canceled when the predetermined data associated with the DSR expires; Contains A method for a terminal device (10).

8. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a remaining time field indicating the remaining time for the earliest deadline for data for the LCG; the buffer size field indicating a buffer size for data for the LCG; Including, The method of claim 7.

9. The method further includes using either a first table or a second table to set the buffer size field indicating the buffer size. The method of claim 8.

10. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a field containing information about the size of data for the LCG whose remaining time is below the threshold; Including, The method of claim 7.

11. the predetermined data is data for the LCH, The method comprises: Triggering the DSR based on the remaining time for the earliest deadline of data for the LCH being below the threshold and the DSR for data for the LCH not being transmitted. Further comprising: The method of claim 7.

12. The DSR is a MAC CE (Medium Access Control Element) identified by an extended logical channel identifier (eLCID) included in a MAC (Medium Access Control) subheader. A method for a terminal device according to any one of claims 7 to 11.

13. a transmitter (221) for transmitting, to a terminal device (10), a radio resource control (RRC) message including information for setting an identifier (ID) of a logical channel group (LCG) to which a logical channel (Logical CHannel, LCH) belongs, and information indicating a threshold value for the LCG for triggering a delay status report (DSR); a receiving unit (222) that receives the DSR triggered based on the remaining time for the earliest deadline of predetermined data being below the threshold and the DSR for the predetermined data not being transmitted from the terminal device; Equipped with When the predetermined data associated with the DSR expires, the DSR that has been triggered and has not been canceled is canceled. Base station device (20).

14. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a remaining time field indicating the remaining time for the earliest deadline for data for the LCG; the buffer size field indicating a buffer size for data for the LCG; Including, The base station device according to claim 13.

15. the buffer size field is set using either a first table or a second table; The base station device according to claim 14.

16. The DSR is an LCG field, each bit of which indicates whether a buffer size field for each LCG is present; a field containing information about the size of data for the LCG whose remaining time is below the threshold; Including, The base station device according to claim 13.

17. the predetermined data is data for the LCH, The receiving unit receiving, from the terminal device, the DSR triggered based on the remaining time for the earliest deadline of data for the LCH being below the threshold and the DSR for data for the LCH not being transmitted; The base station device according to claim 13.

18. The DSR is a MAC CE (Medium Access Control Element) identified by an extended logical channel identifier (eLCID) included in a MAC (Medium Access Control) subheader. The base station device according to any one of claims 13 to 17.

Images