Terminal device and method of terminal device

Abstract

A terminal device (10) is provided with: a reception unit (122) that receives, from a base station device (20), a radio resource control (RRC) message including information for configuring an identifier of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information for indicating a threshold value of data for the LCG for controlling the triggering of a delay status report (DSR); a control unit (110) for controlling the triggering of the DSR on the basis that the remaining time of the earliest deadline of the data for the LCG is lower than the threshold value and the DSR for the data for the LCG is not transmitted; and a transmission unit (121) that transmits the DSR and the scheduling request (SR).

Description

Cross-references of related applications

[0001] This application claims priority to Japanese Patent Application No. 2023-62920, filed on April 7, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to a terminal device and a method for using the terminal device. Background Technology

[0003] In recent years, research and development related to extended reality (XR) has been progressing. XR is a concept that integrates multimedia technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and substitutional reality (SR). In XR, three-dimensional time-series image data from real and / or virtual spaces, multi-channel (stereo, 5.1ch, etc.) audio data, other data presented to the user, and control data are transmitted and received in parallel. XR requires low latency and high reliability to maintain and improve the user experience quality.

[0004] Non-patent document 1 discusses the implementation of XR in 5G NR (Fifth Generation New Radio), which is a radio specification defined by the Third Generation Partnership Project (3GPP (registered trademark)). Existing technical documents Non-patent literature

[0005] Non-patent literature 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 The problem that the invention aims to solve

[0006] Incidentally, Non-Patent Document 2 describes a process for Buffer Status Reporting (BSR). Furthermore, Non-Patent Document 3 describes parameters sent from a base station device, specifically parameters used for the BSR. The BSR indicates the buffer size of uplink data for predetermined data. This predetermined data corresponds to data within a Logical Channel Group (LCG). The terminal device calculates the buffer size for each LCG and sends 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] Suppose XR is used under various requirements, including low latency. Consequently, for uplink communication from the terminal device, the aforementioned requirements need to be considered when allocating radio resources. However, in the BSR described in Non-Patent Documents 2 and 3, the terminal device can only send one piece of information (i.e., information related to buffer size) for predetermined data. Due to the limited amount of information reported to the base station device, there is a possibility that the base station device may not be able to properly allocate radio resources to the terminal device. Therefore, it is explored to report predetermined information (e.g., latency-related information) in addition to reporting the buffer size in the BSR. Furthermore, it is also explored to report the aforementioned predetermined information to the base station device using reporting methods other than the BSR.

[0008] The inventors discovered the following problem: the need for a process to appropriately determine whether to trigger or send the aforementioned predetermined information report. On the other hand, no such process is described in Non-Patent Documents 2 and 3. Furthermore, the aforementioned problem also occurs in conventional terminal devices and base station devices outside of XR implementations. Solution for solving the problem

[0009] This disclosure provides technology for appropriately determining whether to trigger or send a report of pre-defined information.

[0010] The terminal device in this disclosure includes: a receiving unit that receives Radio Resource Control (RRC) messages from a base station device, the RRC messages including information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information indicating a threshold for controlling the triggering of a Delay Status Report (DSR) for data of the aforementioned LCG; a control unit that controls the triggering of the aforementioned DSR based on the remaining time of the earliest deadline for the data of the aforementioned LCG being less than the aforementioned threshold, and the aforementioned DSR for the data of the aforementioned LCG not being transmitted; and a transmitting unit that transmits the aforementioned DSR and a scheduling request (SR). When the aforementioned DSR is triggered, the transmitting unit transmits the aforementioned DSR based on having uplink resources capable of accommodating the aforementioned DSR, and transmits the aforementioned SR based on not having uplink resources capable of accommodating the aforementioned DSR.

[0011] Furthermore, the method of the terminal device in this disclosure includes: receiving a Radio Resource Control (RRC) message from a base station device, wherein the RRC message includes information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information indicating a threshold for controlling the triggering of a Delay Status Report (DSR) for data of the aforementioned LCG; controlling the triggering of the aforementioned DSR based on the remaining time of the earliest deadline for the data of the aforementioned LCG being less than the aforementioned threshold, and the aforementioned DSR for the data of the aforementioned LCG not being transmitted; and transmitting the aforementioned DSR and a scheduling request (SR). The transmission includes: transmitting the aforementioned DSR based on having uplink resources capable of accommodating the aforementioned DSR when the aforementioned DSR is triggered; and transmitting the aforementioned SR based on not having uplink resources capable of accommodating the aforementioned DSR. Invention Effects

[0012] Based on the above configuration, it is possible to appropriately determine whether to trigger or send a delay information report. Furthermore, the above configuration can be used to replace this effect or to achieve other effects in conjunction with it. Attached Figure Description

[0013] The foregoing and other objects, features, and advantages of this disclosure will become clearer from the following detailed description, taken in conjunction with the accompanying drawings. The drawings are as follows: Figure 1 This is a diagram illustrating the communication system S according to the first embodiment. Figure 2 This is a diagram illustrating the protocol stack of the U-plane involved in the first embodiment. Figure 3 This is a diagram illustrating the protocol stack of the C-plane according to the first embodiment. Figure 4 This is a block diagram illustrating a schematic hardware configuration of the terminal device 10 according to the first embodiment. Figure 5 This is a block diagram illustrating a general functional configuration of the terminal device 10 according to the first embodiment. Figure 6 This is a block diagram illustrating a schematic hardware configuration of the base station device 20 according to the first embodiment. Figure 7 This is a block diagram illustrating a general functional configuration of the base station device 20 according to the first embodiment. Figure 8 This is a diagram illustrating the wireless frame configuration according to the first embodiment. Figure 9 This is a diagram showing the configuration of the short BSR. Figure 10 This is a diagram showing the configuration of a long BSR. Figure 11 This is a sequence diagram illustrating the processing flow of the terminal device 10 and the base station device 20 according to the first embodiment. Figure 12 This is a diagram illustrating an example of a configuration for a long BSR that includes delay information. Figure 13 This is another example of a configuration that includes delay information in a long BSR. Figure 14 This is another example of a configuration that includes delay information in a long BSR. Figure 15 This is a diagram illustrating an example of a delayed information report being sent. Figure 16 This is a sequence diagram illustrating the processing flow of the terminal device 10 according to aspect 1-1 of the first embodiment. Figure 17 This is a sequence diagram illustrating the processing flow of the terminal device 10 according to aspects 1-2 of the first embodiment. Figure 18 This is a sequence diagram illustrating the processing flow of the terminal device 10 involved in a variant of the first embodiment. Figure 19 This is a sequence diagram illustrating the processing flow of the terminal device 10 according to aspect 2-1 of the second embodiment. Figure 20 This is a sequence diagram illustrating the processing flow of the terminal device 10 according to aspect 2-2 of the second embodiment. Detailed Implementation

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, in this specification and the accompanying drawings, elements that can be described in the same way are labeled with the same reference numerals, thus omitting repeated descriptions.

[0015] The embodiments described below are merely examples of configurations that can implement this disclosure. These embodiments can be appropriately modified or changed depending on the configuration of the device to which this disclosure is applied and various conditions. Not all combinations of elements included in the following embodiments are necessary to implement this disclosure, and some elements can be appropriately omitted. Therefore, the scope of this disclosure is not limited to the configurations described in the following embodiments. Configurations combining multiple configurations described in the following embodiments can also be used, provided they do not contradict each other.

[0016] 1. First Implementation Method 1.1. Communication System like Figure 1 As shown, the communication system S in the first embodiment includes one or more terminal apps 10, one or more base station apps 20, and a core network 30. The communication system S is configured according to predetermined technical specifications (TS). For example, the communication system S may comply with the technical specifications specified by 3GPP (e.g., 5G, 5G Advanced, 6G, etc.).

[0017] In a communication system S, a user plane for sending and receiving user data and a control plane for sending and receiving control data are specifically configured. That is, communication system S supports C / U separation. The user plane is abbreviated as U plane, and the control plane as C plane.

[0018] Terminal device 10 can be a device that wirelessly communicates with base station device 20, such as a user equipment (UE) operating in accordance with the 3GPP 5G NR specification. Alternatively, terminal device 10 can also be a device that complies with other older or newer 3GPP specifications.

[0019] Terminal device 10 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a laptop PC (personal computer), a communication module, a communication card, or an IoT (Internet of Things) device such as a surveillance camera and a robot. Terminal device 10 may also be a vehicle (e.g., a car, a tram, etc.) or a device mounted thereon. Terminal device 10 may also be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device mounted thereon. Terminal device 10 may also be a sensor or a device mounted thereon. Furthermore, terminal device 10 may also be referred to as a terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber equipment, subscriber unit, wireless station, wireless terminal, wireless equipment, wireless unit, remote station, remote terminal, remote equipment, remote unit, and other names. Terminal device 10 may also 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] Base station equipment 20 manages at least one cell. A cell is the smallest unit constituting a communication area. For example, a cell belongs to a frequency (e.g., a carrier frequency) and includes one component carrier. The term "cell" sometimes refers to a wireless communication resource and sometimes to a communication target of terminal equipment 100. Base station equipment 20 wirelessly communicates with terminal equipment 10 located in the cell in both the U-plane and the C-plane. In other words, base station equipment 20 terminates both the U-plane and C-plane protocols for terminal equipment 10.

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

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

[0023] The base station equipment 20 may include multiple unit devices. For example, the base station equipment 20 may include a central unit (CU), a distributed unit (DU), and a radio unit (RU).

[0024] Multiple base station devices 20 are interconnected to form a Radio Access Network (RAN). The radio access network formed by the base station devices 20 acting as gNBs can also be referred to as NG-RAN (Next Generation Radio Access Network). The base station devices 20 acting as gNBs can also be referred to as NG-RAN nodes.

[0025] Multiple base station devices 20 are interconnected via predetermined interfaces (e.g., Xn interfaces). More specifically, for example, multiple base station devices 20 are interconnected in the U plane via Xn-U interfaces and in the C plane via Xn-C interfaces. Furthermore, multiple base station devices 20 may also be interconnected 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 (e.g., 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 to the AMF of the core network 30 via an NG-C interface in the C plane. Furthermore, each base station device 20 may also connect to the core network 30 via other interfaces with different functions or names.

[0027] Reference Figure 2 The wireless protocol architecture between terminal device 10 and base station device 20 is explained. Additionally, refer to... Figure 3 The wireless protocol architecture between terminal device 10 and base station device 20, and between terminal device 10 and core network 30, is explained.

[0028] like Figure 2 As shown, in the U-plane protocol stack, starting from the bottom, the layers are arranged sequentially as follows: Physical (PHY) layer, Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, and Service Data Adaptation Protocol (SDAP) layer. Each of these layers terminates at point 20 on the network side of the base station equipment.

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

[0030] like Figure 4 As shown, the terminal device 10 includes a processor 101, a memory 102, an input / output interface 103, a wireless interface 104, and an antenna 105 as hardware elements. These elements in the terminal device 10 are interconnected via an internal bus. Furthermore, the terminal device 10 may also include... Figure 4 Hardware elements other than those shown.

[0031] The processor 101 is a computing element that implements 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 includes at least one storage medium such as RAM (Random Access Memory) or eMMC (embedded Multi Media Card). The memory 102 is an element that temporarily or permanently stores programs and data used to perform various processes in the terminal device 10. The programs include one or more commands for operating the terminal device 10. The processor 101 implements the functions of the terminal device 10 by decompressing the programs stored in the memory 102 into the memory 102 and / or system memory (not shown) and executing them.

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

[0034] Wireless interface 104 is a circuit that performs various signal processing for implementing wireless communication, including a baseband processor and RF circuitry. Wireless interface 104 transmits and receives wireless signals with base station equipment 20 via antenna 105.

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

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

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

[0038] The terminal device 10 of this embodiment performs various processes through the operation of the control unit 110.

[0039] like Figure 6 As shown, the base station device 20 includes a processor 201, a memory 202, a network interface 203, a wireless interface 204, and an antenna 205 as hardware elements. These elements in the base station device 20 are interconnected via an internal bus. Alternatively, the base station device 20 may also include... Figure 6 Hardware elements other than those shown.

[0040] The processor 201 is a computing element that implements various functions of the base station device 20. The processor 201 can be a CPU, or it can include other processors such as a GPU.

[0041] The memory 202 includes at least one storage medium selected from ROM (Read Only Memory), RAM, HDD (Hard Disk Drive), SSD (Solid State Drive), etc. The memory 202 is an element that temporarily or permanently stores programs and data used to perform various processes in the base station device 20. The programs include one or more commands for the operation of the base station device 20. The processor 201 implements the functions of the base station device 20 by decompressing the programs stored in the memory 202 into the memory 202 and / or system memory (not shown) and executing them.

[0042] Network interface 203 is an interface used to send and receive signals with other base station equipment 20 and core network 30.

[0043] The wireless interface 204 is a circuit that performs various signal processing functions to enable wireless communication, including a baseband processor and RF circuitry. The wireless interface 204 transmits and receives wireless signals with the terminal device 10 via the antenna 205.

[0044] like Figure 7 As shown, the base station equipment 20 includes a control unit 210, a communication unit 220, and a network communication unit 230 as functional blocks. The communication unit 220 includes at least one transmitting unit 221 and at least one receiving unit 222.

[0045] The control unit 210 may include at least one processor 201 and at least one memory 202. In other words, the control unit 210 may be implemented by the processor 201 and the memory 202. The control unit 210 performs various control processes in the base station device 20. For example, the control unit 210 controls wireless communication with the base station device 10 via the communication unit 220. That is, the control unit 210 transmits and receives data / information / messages via the communication unit 220. In addition, 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 wireless interface 204 and an antenna 205. In other words, the communication unit 220 is implemented by the wireless interface 204 and the antenna 205. The communication unit 220 communicates wirelessly with the terminal device 10 by sending and receiving wireless signals. The communication unit 220 may include two or more wireless interfaces 204 and two or more antennas 205.

[0047] The network communication unit 230 includes a network interface 203. In other words, the network communication unit 230 is implemented by the network interface 203. The network interface 203 sends and receives signals with the network (and consequently, the other nodes mentioned above).

[0048] The base station device 20 of this embodiment performs various processes through the operation of the control unit 210.

[0049] 1.2. Wireless Resources Terminal device 10 and base station device 20 communicate wirelessly with each other using wireless resources in the frequency and time domains. The wireless resources are described below.

[0050] The downlink communication transmission method from base station device 20 to terminal device 10 is, for example, orthogonal frequency division multiplexing (OFDM) using a cyclic prefix (CP), i.e., CP-OFDM. The uplink communication transmission method from terminal device 10 to base station device 20 is, for example, the aforementioned CP-OFDM, or DFTS-OFDM (Discrete Fourier Transform Spread Spectrum Orthogonal Frequency Division Multiplexing) applying CP-OFDM after perform transform precoding of 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 it is inserted at the beginning of an OFDM symbol. As categories of cyclic prefixes, there are normal cyclic prefixes and extended cyclic prefixes.

[0052] Multiple mutually orthogonal subcarriers are used as frequency-domain radio resources in OFDM. These subcarriers are arranged in the frequency domain with a predetermined subcarrier spacing (SCS) Δf. In a communication system S, multiple subcarrier spacings Δf can be applied. The subcarrier spacing Δf can be represented, for example, by the following formula.

[0053] Here, μ is an integer greater than or equal to 0, and can take at least any of the values ​​0, 1, 2, 3, 4, 5, and 6. Therefore, the subcarrier spacing Δf [kHz] can take at least any of the values ​​15, 30, 60, 120, 240, 480, and 960. In addition, μ can also take values ​​greater than or equal to 7.

[0054] In the time domain of OFDM, such as Figure 8As shown, a hierarchical radio frame configuration is used. A radio frame consists of 10 subframes. Subframes are assigned subframe numbers that are counted upwards from 0 to 9. A radio frame is divided into two half-frames. The duration of a radio frame is 10 ms, the duration of a half-frame is 5 ms, and the duration of a subframe is 1 ms. These durations do not depend on the subcarrier spacing Δf.

[0055] A subframe comprises one or more slots. The number of slots Ns in a subframe depends on the value of μ mentioned above, and thus on the subcarrier spacing Δf. The number of slots Ns can be represented, for example, by the following formula.

[0056] A time slot includes multiple symbols. The number of symbols in a time slot depends on the type of cyclic prefix. For example, with a regular cyclic prefix, a time slot includes 14 symbols. With an extended cyclic prefix, a time slot includes 12 symbols.

[0057] As mentioned above, the number of time slots and symbols in each of the radio frames, half-frames, and subframes, which have fixed durations, is variable. Therefore, the duration of the time slots and the duration of the symbols are also variable.

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

[0059] Radio frames are assigned a System Frame Number (SFN) that increments by 1 from 0 to 1023. SFN "0" represents the initial SFN value, and SFN "1023" represents the maximum SFN value. Therefore, the next radio frame after a radio frame assigned SFN 1023 is assigned SFN 0. Since the duration of a radio frame is 10ms, the duration of one cycle of the System Frame Number is 10240ms (=10.24 seconds).

[0060] Here, base station equipment 20 can configure one or more serving cells for terminal equipment 10. A serving cell may correspond to a component carrier in the downlink and / or a component carrier in the uplink. The technique of configuring one or more serving cells and performing wireless communication between base station equipment 20 and terminal equipment 10 can also be referred to as carrier aggregation.

[0061] Additionally, base station equipment 20 can configure one or more bandwidth parts (BWPs) for terminal equipment 10 for each of one or more serving cells. For example, a downlink bandwidth part (DL-BWP) can be configured in the downlink of a serving cell. Additionally, an uplink bandwidth part (UL-BWP) can be configured in the uplink of a serving cell. Here, the DL-BWP can include an initial DL-BWP and / or a dedicated DL-BWP. Similarly, the UL-BWP can include an initial UL-BWP and / or a dedicated UL-BWP. Hereinafter, BWPs can include DL-BWPs and / or UL-BWPs.

[0062] 1.3. Channel and Control Information Terminal device 10 and base station device 20 send and receive user data and control information to each other. The following example illustrates the sending and receiving of control information in the downlink and uplink.

[0063] Terminal device 10 and base station device 20 use multiple layered channels to send and receive user data and control information. Physical channels are channels used for physical communication between terminal device 10 and base station device 20. Examples of physical channels include the Physical Downlink Control Channel (PDCCH), Physical Broadcast Channel (PBCH), and Physical Uplink Control Channel (PUCCH).

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

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

[0066] Base station device 20 uses the PDCCH as the physical channel to send downlink control information (DCI) to terminal device 10. The DCI includes information related to the resource allocation for the downlink and uplink of terminal device 10, as well as control information for terminal device 10. The DCI is mapped to the PDCCH, which is equivalent to Layer 1 signaling.

[0067] Here, one or more formats can be specified for DCI transmissions in the PDCCH. The format specified for DCI transmissions in the PDCCH can be referred to as a DCI format. For example, a DCI format may include a DCI format for scheduling the Physical Downlink Shared Channel (PDSCH) (e.g., formats referred to as DCI format 1_0, DCI format 1_1, and / or DCI format 1_2). Additionally, for example, a DCI format may include a DCI format for scheduling the Physical Uplink Shared Channel (PUSCH) (e.g., formats referred to as DCI format 0_0, DCI format 0_1, and / or DCI format 0_2). Furthermore, a DCI format may include a DCI format not used for scheduling the PDSCH and / or PUSCH. A DCI format used for scheduling the PDSCH and / or PUSCH can be referred to as a scheduled DCI format. A DCI format not used for scheduling the PDSCH and / or PUSCH can be referred to as a non-scheduled DCI format. In this embodiment, for ease of explanation, "DCI format" is sometimes simply referred to as "PDCCH". In addition, "DCI generated according to DCI format" is sometimes simply referred to as "DCI format".

[0068] For example, base station device 20 can be configured to monitor (i.e., supervise) the frequency domain resources and / or time domain resources of the PDCCH candidate set. For example, the frequency domain resources monitored by terminal device 10 for the PDCCH candidate set can be referred to as a control resource set (CORESET). Additionally, the time domain resources monitored by terminal device 10 for the PDCCH candidate set can be referred to as a search space set (SSS). Terminal device 10 can monitor the PDCCH candidate set in one or more CORESETs within the DL-BWP of the serving cell configured with PDCCH monitoring, according to the corresponding search space set. Here, monitoring can mean attempting to decode each of the PDCCH candidates according to the monitored DCI format. This configuration can be referred to as blind decoding.

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

[0070] Terminal device 10 can monitor (and / or receive) PDCCH and detect (and / or receive) DCI format.

[0071] Terminal device 10 uses PUCCH, which serves as the physical channel, to send uplink control information (UCI) to base station device 20. UCI includes control information such as scheduling requests (SR), Ack / Nack for Hybrid Automatic Repeat reQuest (HARQ), and channel state information (CSI). UCI is mapped to PUCCH or PUSCH, equivalent to Layer 1 signaling.

[0072] Base station equipment 20 uses DL-SCH as the transport channel to send MAC layer control element (CE) to terminal equipment 10. The downlink MAC CE is mapped to PDSCH via DL-SCH, which is equivalent to layer 2 signaling.

[0073] Terminal device 10 uses UL-SCH as the transmission channel to send MAC layer control elements (CEs) to base station device 20. The uplink MAC CE includes control information such as buffer status reports (BSRs). The uplink MAC CE is mapped to PUSCH via UL-SCH, equivalent to Layer 2 signaling.

[0074] Base station equipment 20 uses the BCCH (Broadcast Channel) as a logical channel to send (or notify) system information (SI) to terminal equipment 10. SI includes Minimum System Information (MSI) and Other System Information (OSI). MSI includes the Master Information Block (MIB) and System Information Block 1 (SIB 1). SIB 1 can be referred to as Remaining Minimum System Information (RMSI). OSI includes system information blocks other than SIB1 (SIB 2 onwards). In the BCCH, MIB is mapped to PBCH via BCH (Broadcast Channel), and SIB is mapped to PDSCH via DL-SCH.

[0075] Base station device 20 uses the Signaling Radio Bearer (SRB) established between terminal device 10 and base station device 20 in the RRC layer to send control information in the RRC layer to terminal device 10. Hereinafter, messages exchanged between base station device 20 and terminal device 10 in the RRC layer can be referred to as RRC messages. There are several types of SRBs (e.g., SRB 0, SRB 1, SRB 2, SRB 3, SRB 4). In addition to RRC messages, SRBs are also used for sending and receiving NAS messages, which include control information in the NAS layer. CCCH or DCCH is used to send RRC messages from base station device 20 to terminal device 10. CCCH and DCCH are mapped to PDSCH via DL-SCH, respectively. RRC messages are equivalent to Layer 3 signaling.

[0076] As an example of a downlink RRC message, the RRC Reconfiguration message will be explained. The RRC Reconfiguration message is an RRC message sent from base station device 20 to terminal device 10 using SRB 1 or SRB 3. The DCCH is used to send the RRC Reconfiguration message. The RRC Reconfiguration message is used to perform reconfiguration or modification related to the connection between base station device 20 and terminal device 10.

[0077] Terminal device 10 uses the aforementioned SRB to send an RRC message to base station device 20. CCCH or DCCH is used to send the RRC message from terminal device 10 to base station device 20. CCCH and DCCH are mapped to PUSCH via UL-SCH, respectively. The RRC message is equivalent to Layer 3 signaling.

[0078] As an example of an uplink RRC message, the User Equipment Capability Information (UECapabilityInformation) message will be explained. The UECapability Information message is an RRC message sent from terminal device 10 to base station device 20 using SRB 1. The DCCH is used to send the UECapability Information message. The UECapability Information message is used to notify base station device 20 of information related to the radio access capability of terminal device 10.

[0079] As an example of an uplink RRC message, the UE Assistance Information (UE Assistance Information) message will be explained. The UE Assistance Information message is an RRC message sent from terminal device 10 to base station device 20 using SRB 1 or SRB 3. The DCCH is used to send the UE Assistance Information message. The UE Assistance Information message is used to notify base station device 20 of various information (UE assistance information) related to terminal device 10.

[0080] 1.4. Uplink Scheduling 1.4.1. Scheduling Request (SR) The SR (Request for Radio Resources) is used by terminal device 10 to request PUSCH (Programmed Receiver) resource allocation from base station device 20. The SR can also be used to request UL-SCH resources for initial transmission. Base station device 20 allocates PUSCH resources to terminal device 10 for sending the SR. Base station device 20 sends an RRC (Resource Control Code) message to terminal device 10, including the parameters of the SR. The parameters of the SR are included in the SchedulingRequestResourceConfig IE, which is an example of an Information Element (IE) in RRC.

[0081] Terminal device 10 uses configured PUCCH resources to send a UCI including a SR to base station device 20. Terminal device 10 can send UCIs on demand. Terminal device 10 can also send UCIs at configuration periods. For example, terminal device 10 can send an SR set to "0" (negative SR) and / or an SR set to "1" (positive SR). Base station device 20 allocates PUSCH radio resources to terminal device 10 based on the SR.

[0082] 1.4.2. Dynamic Grant (DG) DG is a scheduling method for allocating PUSCH radio resources according to the uplink granting process. Base station device 20 sends an uplink grant to terminal device 10 on the PDCCH. Terminal device 10 performs PUSCH transmission according to the uplink grant. For example, base station device 20 may allocate PUSCH radio resources using a DCI format accompanied by a CRC scrambled with C-RNTI and / or MCS-C-RNTI (i.e., a DCI format for scheduling PUSCH), and terminal device 10 may use the allocated PUSCH radio resources to perform uplink transmission. Here, the New Data Indicator included in the DCI format with a CRC scrambled with C-RNTI and / or MCS-C-RNTI can be set to 0 or 1. Alternatively, base station device 20 may allocate PUSCH radio resources using a DCI format accompanied by a CRC scrambled with CS-RNTI (i.e., a DCI format for scheduling PUSCH), and terminal device 10 may use the allocated PUSCH radio resources to perform uplink transmission. Here, the new data indicator included in the DCI format, which is accompanied by CRC scrambling using CS-RNTI, can be set to 1.

[0083] 1.4.3. Configured Grant (CG) CG is a scheduling method for allocating PUSCH radio resources without the aforementioned dynamic uplink granting process. CG includes two types: Type 1 and Type 2. Base station device 20 sends an RRC message including the parameters of the CG to terminal device 10. The parameters of the CG are included in the ConfiguredGrantConfig IE, which is an example of an Information Element (IE) of RRC. The ConfiguredGrantConfig IE includes the parameter periodicity related to the period of transmission using PUSCH. Furthermore, the periodicity parameter is configured in units of time slots or symbols. Alternatively, the periodicity parameter can also be configured in units of frames per second (FPS). In Type 1, terminal device 10 begins transmitting signals at the configured period without triggering by DCI. On the other hand, in Type 2, base station device 20 sends a DCI scrambled using CS-RNTI to terminal device 10. CS-RNTI is used to activate periodic transmissions. Terminal device 10 responds to the activation of DCI scrambled by CS-RNTI by initiating transmission using PUSCH at a configured period.

[0084] 1.4.4. Cache Status Report (BSR) Terminal device 10 uses the allocated PUSCH radio resources to send a BSR via MAC signaling. The BSR includes a MAC CE, which is included in a MAC PDU (Medium Access Control Protocol Data Unit). The BSR indicates information related to the buffer status of uplink data for the MAC entity. Based on the BSR, base station device 20 allocates uplink radio resources to terminal device 10.

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

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

[0087] Additionally, parameters associated with the LCG are included in the LogicalChannelConfig IE, which is an example of an Information Element (IE) in RRC. That is, base station device 20 can send an RRC message including the LogicalChannelConfig IE. Furthermore, terminal device 10 can determine the configuration related to logical channels and / or LCGs based on the LogicalChannelConfig IE included in the RRC message. For example, the LogicalChannelConfig IE includes the logicalChannelGroup IE. Logical channels are assigned to LCGs by the logicalChannelGroup IE. For example, an index (ID) of the LCG can be configured for each of one or more logical channels, and the LCG to which the one or more logical channels belong can be configured. Furthermore, the LogicalChannelConfig IE sometimes includes the logicalChannelGroupIAB-Ext IE. The logicalChannelGroupIAB-Ext IE is only applicable to IAB-MT (Integrated Access Backhaul-Mobile Termination). If the logicalChannelGroupIAB-Ext IE is configured, the LogicalChannelConfig IE is ignored.

[0088] Terminal device 10 can trigger BSR according to predetermined conditions. For example, terminal device 10 can trigger BSR when any of the following conditions (a1) to (a4) are met for an activated cell group. In addition, the following conditions may also be referred to as "events". (a1) For a logical channel belonging to a specific LCG, the uplink data is available in the MAC entity and either of the following conditions is met. The aforementioned uplink data belongs to a logical channel, which has a higher priority than any logical channel belonging to any LCG that includes available uplink data. There is no logical channel belonging to any LCG that includes available uplink data. (a2) Uplink resources are allocated and the number of padding bits is greater than or equal to the size after adding the BSR MAC CE and its subheader. (a3) The retxBSR-Timer expires, and at least one logical channel belonging to the LCG includes uplink data. (a4) periodicBSR-Timer expires.

[0089] BSRs include at least Regular BSRs, Padding BSRs, and Periodic BSRs. Regular BSRs, Padding BSRs, and Periodic BSRs can be triggered based on different conditions. For example, if either condition (a1) or (a3) ​​above is met, the terminal device 10 triggers a Regular BSR. If condition (a2) above is met, the terminal device 10 triggers a Padding BSR. If condition (a4) above is met, the terminal device 10 triggers a Periodic BSR.

[0090] BSRs include multiple formats. These formats include at least a short BSR and a long BSR. A MAC PDU that includes a 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 can be referred to as a codepoint. Short and long BSRs are identified by the codepoint value.

[0091] A Short BSR is a format used to report the cache status (i.e., cache size) of an LCG. For example... Figure 9 As shown, the short BSR includes a fixed-size field 900 with 8 bits. Field 900 includes a first part 910 and a second part 920.

[0092] Part 910 consists of 3 bits. Part 910 contains information that identifies the LCG whose cache state is being reported. Part 910 is sometimes referred to as the "LCG ID field".

[0093] Part 920 comprises 5 bits. Part 920 contains information identifying the total amount of data available on all logical channels within the LCG indicated by Part 910. Part 920 is sometimes simply referred to as the "buffer size". Part 920 indicates an index that indicates the number of bytes. For example, Part 920 indicates any value from 0 to 31.

[0094] In addition, short BSRs can include truncated and extended formats. The truncated format is used for high-priority logical channels, while the extended format is capable of transmitting more information.

[0095] Long BSRs are a format used to report the cache status (i.e., cache size) of multiple LCGs. For example... Figure 10 As shown, the long BSR has a variable size. The long BSR includes an LCG field 1010 and a cache size field 1020.

[0096] LCG field 1010 consists of 8 bits. In LCG field 1010, each of the 8 bits corresponds to one of the 8 LCGs i. Here, i is an integer from 0 to 7. The definition of i is the same in the following description. LCG field 1010 can indicate whether a cache size field corresponding to LCG i exists. For example, when the value of LCG i in LCG field 1010 is 1, this indicates that a cache size field corresponding to LCG i exists. When the value of LCG i is 0, this indicates that a cache size field corresponding to LCG i does not exist.

[0097] The number of fields included in the cache size field 1020 varies depending on the value of the LCG field 1010. Figure 10 In the example, suppose that in LCG field 1010, the bit corresponding to LCG 1 is 1, and the bit corresponding to LCG 2 is 1. Therefore, cache size field 1020 includes field 1021 corresponding to LCG 1 and field 1022 corresponding to LCG 2. Furthermore, suppose that in... Figure 10 The bit corresponding to LCG 0 is 0, therefore, the field corresponding to LCG 0 is not included in the cache size field 1020.

[0098] Each field included in the cache size field 1020 consists of 8 bits. Each field indicates an index, which in turn indicates the number of bytes. For example, each field indicates a value from 0 to 254.

[0099] In addition, similar to short BSRs, long BSRs can include truncated and extended formats.

[0100] In addition, BSRs can include both Pre-emptive and Extended Pre-emptive BSR formats. These formats are used in IAB-MT.

[0101] Terminal device 10 can select either a short BSR or a long BSR according to a predetermined method. For example, in the case of regular BSRs and periodic BSRs, terminal device 10 can 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, terminal device 10 sends a long BSR for all LCGs with available data. Otherwise, terminal device 10 sends a short BSR.

[0102] In the case of regular and periodic BSRs, for the MAC entity configured by the upper layer for the logicalChannelGroup-IABExt IE, terminal device 10 can select either a short BSR or a long BSR as follows: When two or more LCGs have available data for transmission, and the maximum value of the LCG ID among the configured LCGs is 7 or less, terminal device 10 sends a long BSR for all LCGs with available data. When two or more LCGs have available data for transmission, and the maximum value of the LCG ID among the configured LCGs is greater than 7, terminal device 10 sends an extended long BSR for all LCGs with available data. When one or more LCGs have available data for transmission, terminal device 10 sends an extended short BSR.

[0103] In addition, when filling in a BSR, the terminal device 10 may send 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 Truncation BSR

[0104] Furthermore, if at least one BSR is triggered by any of the conditions (a1) to (a4) above and is not canceled, the terminal device 10 may perform the following processing. For example, if the UL-SCH resources are available for a new transmission and the UL-SCH resources are capable of accommodating the BSR MAC CE and its sub-header as a result of LCP (Logical Channel Prioritization), the terminal device 10 may generate a BSR MAC CE and send 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 either of the following conditions (b1) or (b2) is met. (b1) There are no UL-SCH resources available for the new transmission. (b2) The UL-SCH resources available for new transmission do not meet the LCP mapping restriction configured for the logical channel that triggers BSR.

[0106] The aforementioned LCP mapping restrictions may be those described in section 5.4.3.1 of Non-Patent Document 2. These restrictions may be restrictions configured by the RRC. For example, these restrictions may include at least one of the following: restrictions related to the permitted subcarrier spacing for transmission (e.g., allowedSCS-List), restrictions related to the maximum permitted PUSCH duration for transmission (e.g., maxPUSCH-Duration), restrictions related to whether CG type 1 can be used for transmission (e.g., configuredGrantType1Allowed), restrictions related to the permitted cells for transmission (e.g., allowedServingCells), restrictions related to the permitted CGs for transmission (e.g., allowedCG-List), restrictions related to the permitted PHY priority index for dynamic grant (DG) for transmission (e.g., allowedPHY-PriorityIndex), and restrictions related to the permitted uplink HARQ mode for transmission (e.g., allowedHARQ-mode).

[0107] Additionally, if the following condition (c1) is met, the terminal device 10 may cancel all triggered BSRs. Furthermore, if the following condition (c2) is met, the terminal device 10 may cancel all BSRs triggered before MAC PDU assembly. (c1) The uplink grant is sufficient to accommodate all pending data that can be used for transmission, but not sufficient to accommodate the BSR MAC CE and its subheadings. (c2) A MAC PDU is sent, which includes a long, extended long, short, or extended short BSR MAC CE, which includes (and includes) the cached state up to (and including) the last event that triggered the BSR before the MAC PDU is assembled.

[0108] 1.5. Extended Reality (XR) This section describes the characteristics of services occurring in XR. In XR, various types of data (video data, audio data, user data, control data, etc.) are sent and received in parallel. Each of these data streams has different service characteristics and Quality of Service (QoS) requirements.

[0109] During the timing of sending and receiving the aforementioned data, due to factors such as video or audio encoding and network latency, time shifts may sometimes occur, manifesting as jitter, variability, or fluctuation.

[0110] Reference 1 describes the sending and receiving in XR, and the following definitions can be introduced. [Reference 1] 3GPP TR 23.700-60 V1.1.0 (2022-09)

[0111] A PDU set is a collection of PDUs that contain one or more PDUs, each carrying a unit of payload containing information generated at the application level. For example, the application level mentioned above corresponds to a frame or video slice in an XR service. A data burst is a set of data multiplexed PDUs generated and sent by an application within a short period of time.

[0112] Furthermore, in XR, as part of the aforementioned QoS requirements, the requirements for Packet Delay Budget (PDB) are discussed. PDB is the upper bound of the allowed packet delay time between the terminal device 10 and the UPF. In addition, Reference 1 also describes the introduction of the following new QoS parameters. PDU-Set Delay Budget (PSDB): is the upper bound of the allowed delay time of the PDU set between the terminal device 10 and the UPF. PDU-Set Error Rate (PSER): is the upper bound of the error rate calculated between the PDU set processed by the sender and the PDU set of the higher layer that was not successfully delivered to the corresponding receiver.

[0113] 1.6. Delay Information Reporting 1.6.1. Basic Configuration As described above, in the BSRs recorded in Non-Patent Documents 2 and 3, the terminal device can only send one message (i.e., information related to the buffer size) for predetermined data (i.e., uplink data corresponding to one LCG). Due to the small amount of information reported to the base station device, there is a possibility that the base station device may not be able to properly allocate radio resources to the terminal device.

[0114] In view of the above, this embodiment provides a process for a terminal device 10 to send delay-related information. Hereinafter, "delay-related information" is referred to as "delay information". The terminal device 10 sends a report to the base station device 20 including delay information for predetermined data. Hereinafter, "the report including delay information" is referred to as "delay information report". The delay information report may also be referred to as "Delay Status Report (DSR)".

[0115] The aforementioned predetermined data refers to the unit of data that is the subject of the delay information report. Hereinafter, the predetermined data will sometimes be referred to as "data to be reported" or "unit of data to be reported." According to this configuration, terminal device 10 can send delay information regarding the data to be reported to base station device 20.

[0116] The unit of data for a reporting object can be data corresponding to an LCG. An LCG can include one or more LCHs (i.e., data corresponding to one or more LCHs). In this configuration, the unit of data for a reporting object can be a portion or the entirety of the data available for an LCG. Furthermore, the unit of data for a reporting object can be data corresponding to an LCH. The unit of data for a reporting object can be a portion or the entirety of the data available for an LCH.

[0117] The unit of data for a reporting object can be data corresponding to a single PDU. In this configuration, the unit of data for a reporting object can be a portion or the entirety of the data available for a single PDU. Alternatively, the unit of data for a reporting object can be data corresponding to a set of PDUs. In this configuration, the unit of data for a reporting object can be a portion or the entirety of the data available for a set of PDUs. Furthermore, the unit of data for a reporting object can be data corresponding to multiple sets of PDUs. For example, the unit of data for a reporting object can be data (or a portion of data) available in one or more or all PDUs (or a set of PDUs) belonging to a PDU set.

[0118] The unit of data for a reporting object can be data corresponding to a single data burst. In this configuration, the unit of data for a reporting object can be a portion or the entirety of the data available for a single data burst. Furthermore, the unit of data for a reporting object can be data corresponding to multiple data bursts. For example, the unit of data for a reporting object can be data (or a portion of data) available within one or more or all data (or data bursts) belonging to a single data burst.

[0119] Delay information can be information that explicitly indicates a delay. For example, delay information can be the delay time. Delay information can also be an index representing the delay time.

[0120] Delay information can be information related to other times. For example, delay information can be information associated with the time limit of data transmission. The transmission deadline can be referred to as the "transmission deadline" or the "upper bound of delay."

[0121] The delay information can be the remaining time until a predetermined first deadline is reached. The first deadline can be the deadline for completing the transmission of a portion or all of the data of the reporting object. For example, the first deadline can be the earliest of several deadlines for completing the transmission of a portion of the data of the reporting object. The first deadline can be a deadline determined based on PDB or PSDB. PDB or PSDB can be determined based on the corresponding QoS flow. PDB or PSDB can be provided to terminal device 10 by core network 30. The first deadline related to a PDU set can be a value obtained by adding the PDB or PSDB of the corresponding QoS flow to the time when the data corresponding to the PDU in the PDU set was first cached in terminal device 10 or first arrived at the MAC entity. The first deadline related to a data burst can be a value obtained by adding the PDB or PSDB of the corresponding QoS flow to the time when the data corresponding to the PDU constituting the data burst was first cached in terminal device 10 or first arrived at the MAC entity.

[0122] The aforementioned remaining time can be a value obtained by subtracting the period during which the predetermined data (i.e., the data of the reporting object) is cached in the terminal device 10 from the PDB or PSDB of the corresponding QoS stream.

[0123] The aforementioned remaining time can be a period from a predetermined first moment to the first deadline. The first moment can be the current moment. The first moment can be the moment when the uplink grant for sending the delay information report is allocated. The first moment can be the moment when the aforementioned predetermined data (i.e., the data of the reporting object) is cached in terminal device 10. The first moment can be the moment when the data of the reporting object arrives at the MAC entity in terminal device 10. In such a configuration, the first deadline can be obtained by adding the first moment to the PDB or PSDB.

[0124] Delay information can be information that implicitly indicates a delay. For example, delay information can be information related to data within the data of the report object that imposes a time limit or requirement. Hereinafter, the entire data of the report object is referred to as "first data," and the data within the data within the report object that imposes a time limit or requirement is referred to as "second data." Delay information can be information related to the size of the second data. For example, delay information can be an index indicating the number of bytes in the second data.

[0125] The second data is the data that should be sent with priority. The second data can be referred to as urgent data. The second data can be data that meets delay-related conditions. For example, the second data can be data configured with the aforementioned first deadline. The second data can be data with a remaining time below a predetermined first threshold Th1. Base station device 20 can send an RRC message to terminal device 10 including information indicating the first threshold Th1. The first threshold Th1 can be configured for LCH. For example, the first threshold Th1 can be configured as a new element of LogicalChannelConfig IE. The first threshold Th1 can be configured for LCG. For example, the first threshold Th1 can be configured as a new element of LogicalChannelGroup IE. The first threshold Th1 can be configured for PDU or PDU set. The first threshold Th1 can be configured in an IE associated with the PDU or PDU set included in the RRC message. The first threshold Th1 can be configured for data burst. The first threshold Th1 can be configured in an IE associated with the data burst included in the RRC message. Furthermore, the base station device 20 may send system information (SI, e.g., SIB 1 and / or SIBs other than SIB 1) including information indicating the first threshold Th1 to the terminal device 10. The base station device 20 may also send DCI including information indicating the first threshold Th1 to the terminal device 10.

[0126] In another example, the second data could be data that imposes limitations or requirements related to time variations in delays such as jitter. In yet another example, the second data could be data that imposes limitations or requirements on the transmission rate.

[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 greater than a predetermined size, the base station device 20 can determine that a delay has occurred in the transmission of the terminal device 10. If the size of the second data is less than or equal to the predetermined size, the base station device 20 can determine that no delay has occurred in the transmission of the terminal device 10.

[0128] 1.6.2. Configuration of Delay Information Reporting Terminal device 10 can send a MAC CE including delay information as a delay information report. For example, terminal device 10 can send a BSR including a delay information report. In this configuration, terminal device 10 can send a BSR including a delay information report according to the following procedure.

[0129] like Figure 11As shown, the communication unit 220 of the base station device 20 sends an RRC message to the terminal device 10 (S1101). The RRC message includes parameters associated with the BSR. The RRC message may be an RRC reconfiguration message. The control unit 110 of the terminal device 10 generates the BSR based on the parameters included in the RRC message. The BSR includes cache size information and latency information related to the cache size. The communication unit 120 of the terminal device 10 sends the BSR (S1102).

[0130] Terminal device 10 can send Figure 12 The long BSR 1200 is shown. The long BSR 1200 includes a first field 1210 and a second field 1220.

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

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

[0133] Field 1221 is the field related to LCG 1. Field 1221 includes a first part 1221a and a second part 1221b. In this example, the first part 1221a includes 6 bits and the second part 1221b includes 2 bits. Furthermore, not limited to this configuration, each of the first part 1221a and the second part 1221b may include a different number of bits than in this example.

[0134] The first part 1221a represents the cache size related to the data corresponding to LCG 1. For example, the first part 1221a can be an index indicating the number of bytes. In order to configure the index in the first part 1221a, the control unit 110 can refer to a first cache size table for 6 bits. The first cache size table is a table that defines the correspondence between cache size and index.

[0135] The second part 1221b represents delay information related to the data corresponding to LCG 1. The second part 1221b may be an index representing the delay information. In order to configure the index in the second part 1221b, the control unit 110 may refer to a delay information table for 2 bits. The delay information table is a table that defines the correspondence between delay information and indexes.

[0136] Field 1222 is a field related to LCG 2. Field 1222 includes a first part 1222a and a second part 1222b. The configuration of the first part 1222a and the second part 1222b is the same as the configuration of the first part 1221a and the second part 1221b described above.

[0137] Field 1223 is a field related to LCG 3. Field 1223 represents the cache size related to the data corresponding to LCG 3. Assume that for the data corresponding to LCG 3, the remaining time is greater than the first threshold Th1. That is, there is no latency for the data corresponding to LCG 3. In this case, field 1223 may include information related to the cache size but not latency information. To configure an index in field 1223, the control unit 110 may refer to a second cache size table for 8 bits. The second cache size table is a table that defines the correspondence between cache size and index. Thus, the control unit 110 can switch between the first cache size table and the second cache size table to configure an index corresponding to information related to the cache size.

[0138] Furthermore, in the example above, 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 can be variable. Additionally, in another example, the order of the fields included in the second field 1220 can be determined based on priority.

[0139] like Figure 13 As shown, each of fields 1221 to 1223 in the second field 1220 may include a first part corresponding to information related to the cache size and a second part corresponding to latency information. In the following, only those related to... Figure 12 The different configurations will be explained, regarding the differences between them. Figure 12 The parts with the same configuration are omitted from the description.

[0140] Field 1223 is a field related to LCG 3. Field 1223 includes a first part 1223a and a second part 1223b. In this example, the first part 1223a includes 6 bits, and the second part 1223b includes 2 bits. For example, the first part 1223a may be an index indicating the number of bytes. To configure the index in the first part 1223a, the control unit 110 may refer to the first cache size table described above. As mentioned above, assuming that for data corresponding to LCG 3, the remaining time is greater than the first threshold Th1, the second part 1223b may be blank. In another example, the second part 1223b may be a value (or index) indicating that delay information has not been reported.

[0141] Furthermore, the configuration of the second field 1220 is not limited to the examples above. For example... Figure 14 As shown, the second field 1220 may include an 8-bit field 1410 corresponding to information related to the cache size and an 8-bit field 1420 corresponding to latency information. For example, field 1410 represents information related to the cache size of the data corresponding to LCG 1, and field 1420 represents latency information related to the data corresponding to LCG 1. Thus, the cache size information and latency information related to an LCG can be represented by two different fields.

[0142] While the above example illustrates the configuration of a long BSR, it is not limited to this example. The above configuration can also be applied to short BSRs. For example, terminal device 10 can send a short BSR that includes delay information (e.g., the buffer size of the second data).

[0143] Furthermore, while the configuration of a BSR including a delay information report has been described, it is not limited to this configuration. A new MAC CE for sending delay information can be defined. For example, terminal device 10 can send a MAC CE including delay information as a delay information report. Therefore, "sending a BSR including delay information" as described in this specification can be replaced with "sending a MAC CE including delay information".

[0144] Terminal device 10 can receive first configuration information associated with a delay information report from base station device 20. Base station device 20 can send an RRC message including the first configuration information to terminal device 10. Base station device 20 can send system information (SI, e.g., SIB 1 and / or SIBs other than SIB 1) including the first configuration information to terminal device 10. Base station device 20 can send a DCI including the first configuration information to terminal device 10.

[0145] The first configuration information can be "information indicating whether to send delay information". The first configuration information can indicate "send delay information" or "do not send delay information". The first configuration information can be a flag indicating "send delay information" or "do not send delay information". For example, when the first configuration information is included in an RRC message, terminal device 10 can send delay information. Conversely, when the first configuration information is not included in an RRC message, terminal device 10 can not send delay information. The first configuration information can be configured for an LCH. Terminal device 10 can determine whether to include delay information related to that LCH in the BSR based on the first configuration information configured for the LCH. For example, if the first configuration information indicates that delay information is sent to a specific LCH, terminal device 10 can include the delay information related to that LCH in the BSR. For example, the first configuration information can be configured as a new element of the LogicalChannelConfig IE. The first configuration information can be configured for an LCG. Terminal device 10 can determine whether to include delay information related to that LCG in the BSR based on the first configuration information configured for the LCG. For example, if the first configuration information indicates that delay information is to be sent to a specific LCG, the terminal device 10 can include the delay information related to that LCG in the BSR. For example, the first configuration information can be configured as a new element of the Logical Channel Group IE. The first configuration information can be configured for a PDU or a PDU set. The terminal device 10 can determine whether to include delay information related to that PDU or PDU set in the BSR based on the first configuration information configured for the PDU or PDU set. For example, if the first configuration information indicates that delay information is to be sent to a specific PDU or PDU set, the terminal device 10 can include the delay information related to that PDU or PDU set in the BSR. The first configuration information can be configured in an IE associated with the PDU or PDU set included in the RRC message. The first configuration information can be configured for a data burst. The terminal device 10 can determine whether to include delay information related to that data burst in the BSR based on the first configuration information configured for the data burst. For example, if the first configuration information indicates that delay information is to be sent to a specific data burst, the terminal device 10 can include the delay information related to that data burst in the BSR. The first configuration information can be configured in the IE associated with the data burst included in the RRC message.

[0146] Terminal device 10 can receive second configuration information associated with a delay information report from base station device 20. Base station device 20 can send an RRC message including the second configuration information to terminal device 10. Base station device 20 can send system information (SI, e.g., SIB 1 and / or SIBs other than SIB 1) including the second configuration information to terminal device 10. Base station device 20 can send a DCI including the second configuration information to terminal device 10.

[0147] The second configuration information can indicate the type of data for the reporting object. In this configuration, the terminal device 10 selects the type of data for the reporting object based on the second configuration information. The terminal device 10 can then send a delay information report for the selected data.

[0148] The second configuration information can be explicit information indicating the type of data for the reporting object, or it can be implicit information indicating the type of data for the reporting object. Examples of explicit and implicit information will be given below.

[0149] - Explicit information The second configuration information can be information indicating any of the LCH, LCG, PDU, PDU set, and data burst.

[0150] - Implicit information The second configuration information can be the first configuration information mentioned above. In this configuration, the terminal device 10 can select the type of data for the reporting object according to the IE configured with the first configuration information.

[0151] When first configuration information is configured for a MAC cell group, this indicates that the unit of data for the reporting object corresponds to the data of an LCG. For example, the first configuration information can be configured in an IE associated with the MAC cell group included in the RRC message. An example of such an IE is the BSR-config IE. Similarly, when first configuration information is configured for an LCG, this indicates that the unit of data for the reporting object corresponds to the data of an LCG. For example, the first configuration information can be configured in an IE associated with the LCG. An example of such an IE is the logicalChannelGroup IE.

[0152] When configuring first configuration information for a PDU or PDU set, this can indicate that the unit of data for the reporting object is data corresponding to a PDU or more than one PDU set. For example, the first configuration information can be configured in the IE associated with the PDU or PDU set included in the RRC message.

[0153] When a first configuration message is configured for a data burst, this indicates that the unit of data for the reporting object corresponds to more than one data burst. For example, the first configuration message can be configured in the IE associated with the data burst included in the RRC message.

[0154] For example, when the RRC message includes information indicating a first threshold Th1, the terminal device 10 can control the triggering (and / or sending) of a delay information report. That is, when the RRC message includes information indicating the first threshold Th1, the terminal device 10 can include the delay information report in the BSR based on the first threshold Th1. Conversely, when the RRC message does not include information indicating the first threshold Th1, the terminal device 10 can control the not to trigger (and / or not to send) a delay information report. That is, when the RRC message does not include information indicating the first threshold Th1, the terminal device 10 can choose not to include the delay information report in the BSR.

[0155] A MAC PDU may include identification information to determine whether it is a delayed information report. For example, the MAC subheader includes LCID or eLCID values ​​(i.e., code points). LCID or eLCID values ​​indicating a delayed information report can be defined. These LCID or eLCID values ​​can be defined based on the type of data being reported. • MAC CE includes delay information reporting, and the data unit of the reported object is the data corresponding to one LCH. MAC CE includes delay information reports, and the data for the reported objects is in units corresponding to one LCG. MAC CE includes delay information reports, and the data for the reported objects is in units corresponding to one PDU. • MAC CE includes delay information reporting, and the data unit of the reported object corresponds to more than one PDU set. • MAC CE includes delay information reporting, and the data unit of the reported object corresponds to more than one data burst.

[0156] When BSR includes delay information reporting, the following LCID or eLCID values ​​can be defined based on the type of data of the reporting object. • BSR includes delay information reports, and the data unit of the reported object is the data corresponding to one LCH. • BSR includes delay information reports, and the data unit of the reported object is data corresponding to one LCG. • BSR includes delay information reports, and the data unit of the reported object is data corresponding to one PDU. • BSR includes delay information reports, and the data unit of the reported object corresponds to more than one PDU set. • BSR includes delayed information reports, and the data unit of the reported object corresponds to more than one data burst.

[0157] Furthermore, a value for LCID or eLCID can be defined, indicating that the BSR includes a delay information report and that the BSR is in any of the following formats. Short BSR Long BSR Short truncated BSR Long truncated BSR • Extended Short Truncated BSR · Extended Long Truncation BSR Preemptive BSR • Expanded preemptive BSR

[0158] In another example, the MAC CE that includes a delay information report may include the aforementioned identification information. For instance, the BSR may also include a field that includes identification information indicating that delay information is included.

[0159] 1.6.3. Conditions for triggering delay information reporting Terminal device 10 can trigger a delay information report according to predetermined conditions. Hereinafter, such conditions are referred to as "trigger conditions". Trigger conditions may include at least one of the conditions (a1) to (a4) above.

[0160] Furthermore, the triggering condition may include at least one of the following conditions (d1) to (d4). (d1) There are data whose remaining time is below the first threshold Th1. (d2) On-duration of the start of Discontinuous Reception (DRX). (d3) There is a PDU set or data burst that should be sent, or the PDU set or data burst is cached. (d4) The PDU set is discarded.

[0161] For example, suppose terminal device 10 triggers a delay information report based on condition (d1). Here, the unit of data for the reported object is data corresponding to LCG. Additionally, the first threshold Th1 is 5ms. Figure 15As shown, at time t1, the data corresponding to LCG 1 satisfies condition (d1). Terminal device 10 triggers a delay information report. The delay information report, for each LCG, includes information related to the remaining time as delay information. Base station device 20 receives the delay information report and identifies the remaining time for the data corresponding to LCG 1 as 5ms and the remaining time for the data corresponding to LCG 2 as 8ms. At time t4, 3ms after time t1, the data corresponding to LCG 1 and the data corresponding to LCG 2 satisfy condition (d1). Therefore, terminal device 10 triggers a delay information report again. However, the remaining times included in the delay information report only advance by 3ms. Therefore, the information is more likely to be known to base station device 20. Figure 15 In the example, the communication load (i.e., overhead) may increase because delay information reports are triggered unnecessarily. Furthermore, this problem may occur under conditions other than condition (d1), such as any of conditions (a1) to (a4) and (d2) to (d4). Therefore, it is necessary to prevent the frequent triggering of unnecessary delay information reports.

[0162] In view of the above, terminal device 10 uses predetermined conditions that restrict the transmission of delay information reports to determine whether to trigger (or transmit) a delay information report. Hereinafter, these conditions are referred to as "restriction conditions". Restriction conditions include at least one of the following conditions (e1) and (e2). (e1) The first timer runs. (e2) A delay information report for the scheduled data, which was triggered at the current time, has been sent.

[0163] When the limiting condition is met under the condition that the triggering condition is met, the terminal device 10 does not trigger or send a delay information report. When the limiting condition is not met under the condition that the triggering condition is met, the terminal device 10 triggers or sends a delay information report. The details of each of the usage conditions (e1) aspect 1-1 and usage conditions (e2) aspect 1-2 are described below.

[0164] - Aspect 1-1 The aforementioned first timer is a timer used to configure a period during which delay information reports are not triggered or sent. In other words, the first timer is a disable timer used to prevent the triggering or sending of delay information reports. The first timer expires at a predetermined period. The period of the first timer can be selected from multiple values. While the first timer is running, the terminal device 10 does not trigger or send delay information reports. When the first timer is not running, the terminal device 10 triggers or sends delay information reports. For example, when the RRC message includes information indicating the first timer, the terminal device 10 can control itself to trigger (and / or send) delay information reports. That is, when the RRC message includes information indicating the first timer and the first timer is running, the terminal device 10 can choose not to trigger or send delay information reports. Alternatively, when the RRC message includes information indicating the first timer and the first timer is not running, the terminal device 10 can trigger or send delay information reports. Furthermore, when the RRC message does not include information indicating the first timer, the terminal device 10 can control itself to not trigger or send delay information reports.

[0165] When it begins Figure 16 During the illustrated process, the control unit 110 determines whether the triggering condition is met (S1601). The triggering condition may include at least one of conditions (a1) to (a4) and (d1) to (d4). If the triggering condition is not met, the communication unit 120 does not send a delay information report.

[0166] On the other hand, if the triggering condition is met, the control unit 110 determines whether condition (e1) is met (S1602). If condition (e1) is met, the communication unit 120 does not send a delay information report. Conversely, if condition (e1) is not met, the communication unit 120 sends a delay information report (S1603).

[0167] Based on delay information reports, the control unit 210 of the base station device 20 allocates radio resources to the terminal device 10. The control unit 210 can prioritize the allocation of radio resources to data that experiences delays.

[0168] Furthermore, condition (e1) can be applied to specific conditions among the triggering conditions. For example, condition (e1) can be applied to condition (d1). For example, if both condition (d1) and condition (e1) are met, the communication unit 120 does not send a delay information report. If condition (d1) is met but condition (e1) is not met, the communication unit 120 sends a delay information report. If at least one of conditions (a1) to (a4) and (d2) to (d4) is met, the communication unit 120 can send a delay information report without determining condition (e1). In another example, if condition (d1) is met, the terminal device 10 can start or restart the first timer. If at least one of conditions (a1) to (a4) and (d2) to (d4) is met, the terminal device 10 can not start or restart the first timer. For condition (d1), delay information reports are more likely to be sent more frequently compared to other conditions. This configuration effectively prevents the frequent triggering of unnecessary delay information reports.

[0169] Furthermore, restrictive conditions can be used to limit the transmission of BSRs that include delay information reports only. That is, condition (e1) can be applied to BSRs that include delay information reports, but condition (e1) cannot be applied to BSRs that do not include delay information reports (i.e., Figure 9 or Figure 10 (as shown in the BSR). Therefore, even if condition (e1) is met, the communication unit 120 can send a BSR that does not include a delay information report.

[0170] The first timer can be started or restarted at the time when a delay information report is triggered or sent. In a configuration where the BSR includes a delay information report, the first timer can be started or restarted at the time when the BSR is triggered or sent. In another example, the first timer can be started or restarted at the time when a BSR including a delay information report is triggered or sent. That is, the first timer can be neither started nor restarted at the time when a BSR not including a delay information report is triggered or sent.

[0171] Additionally, in the configuration of BSR including delay information reporting, the first timer can be used as a period during which the SR is not triggered or sent. That is, during the period when the first timer is running, the terminal device 10 does not trigger or send the SR.

[0172] Terminal device 10 may pre-store information related to the first timer within itself. Terminal device 10 may receive information related to the first timer from base station device 20. Base station device 20 may select a value from a plurality of values ​​associated with the first timer and send the selected value to terminal device 10. Base station device 20 may send an RRC message including information related to the first timer to terminal device 10. Base station device 20 may send system information (SI, e.g., SIB 1 and / or SIBs other than SIB 1) including information related to the first timer to terminal device 10. Base station device 20 may send a DCI including information related to the first timer to terminal device 10.

[0173] Information related to the first timer can be included in the parameters associated with the BSR. For example, information related to the first timer can be included in the BSR-config IE.

[0174] A first timer can be configured for an LCH or LCG. Information related to the first timer can be configured in the IE associated with the LCH or LCG. Examples of such IEs include the LogicalChannelConfig IE and the LogicalChannelGroup IE. In this configuration, the first timer is started or restarted when a delay information report for the LCH or LCG with the first timer configured is triggered or sent. Therefore, while the first timer is running, delay information reports for the LCH or LCG with the first timer configured are not triggered or sent.

[0175] A first timer can be configured for a PDU or PDU set. Information related to the first timer can be configured in the IE associated with the PDU or PDU set. For example, information related to the first timer can be configured in the IE associated with the PDU or PDU set included in an RRC message. In this configuration, the first timer is started or restarted when a delay information report for a PDU or PDU set configured with the first timer is triggered or sent. Therefore, while the first timer is running, delay information reports for PDUs or PDU sets configured with the first timer are not triggered or sent.

[0176] A first timer can be configured for a data burst. Information related to the first timer can be configured in the IE associated with the data burst. For example, information related to the first timer can be configured in the IE associated with the data burst included in an RRC message. In this configuration, the first timer is started or restarted when a delay information report for a data burst configured with the first timer is triggered or sent. Therefore, while the first timer is running, delay information reports for data bursts configured with the first timer are not triggered or sent.

[0177] Terminal device 10 can receive third configuration information associated with a delay information report from base station device 20. Base station device 20 can send an RRC message including the third configuration information to terminal device 10. Base station device 20 can send system information (SI, e.g., SIB 1 and / or SIBs other than SIB 1) including the third configuration information to terminal device 10. Base station device 20 can send a DCI including the third configuration information to terminal device 10.

[0178] The third configuration information can be "information indicating whether to apply the first timer". The third configuration information can indicate "apply the first timer" or "do not apply the first timer". The third configuration information can be a flag indicating "apply the first timer" or "do not apply the first timer". Third configuration information can be configured for the LCH. For example, the third configuration information can be configured as a new element in the LogicalChannelConfig IE. Third configuration information can be configured for the LCG. For example, the third configuration information can be configured as a new element in the LogicalChannelGroup IE. Third configuration information can be configured for a PDU or PDU set. The third configuration information can be configured in the IE associated with the PDU or PDU set included in the RRC message. Third configuration information can be configured for a data burst. The third configuration information can be configured in the IE associated with the data burst included in the RRC message.

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

[0180] - Aspect 1-2 Condition (e2) is satisfied if a delay information report for the scheduled data triggered at the current time was sent in the past. Condition (e2) being satisfied can also mean that the delay information report for the scheduled data triggered at the current time is included in previously sent delay information reports. If condition (e2) is not satisfied, it means that a delay information report for the scheduled data triggered at the current time has not yet been sent; that is, a delay information report for new data has been triggered.

[0181] exist Figure 15 In the example, at time t4, delay information reports related to data corresponding to LCG 1 and data corresponding to LCG 2 are triggered. However, delay information reports related to these data have already been sent at time t1. In this case, since condition (e2) is met, terminal device 10 does not send a delay information report at time t4. For example, later, if a delay information report for new data (e.g., data corresponding to LCG 3) is triggered, condition (e2) is not met. Therefore, terminal device 10 sends a delay information report for the data corresponding to LCG 3.

[0182] Furthermore, if condition (e2) is not met, the sent delay information report may include both previously sent delay information reports and delay information reports for new data. If condition (e2) is not met, the sent delay information report may include only delay information reports for new data.

[0183] When it begins Figure 17 During the illustrated process, the control unit 110 determines whether the triggering condition is met (S1701). The triggering condition may include at least one of conditions (a1) to (a4) and (d1) to (d4). If the triggering condition is not met, the communication unit 120 does not send a delay information report.

[0184] On the other hand, if the triggering condition is met, the control unit 110 determines whether condition (e2) is met (S1702). If condition (e2) is met, the communication unit 120 does not send a delay information report. Conversely, if condition (e2) is not met, the communication unit 120 sends a delay information report (S1703).

[0185] Furthermore, condition (e2) can be applied to specific conditions among the triggering conditions. For example, condition (e2) can be applied to condition (d1). For example, if both condition (d1) and condition (e2) are met, the communication unit 120 does not send a delay information report. If condition (d1) is met but condition (e2) is not met, the communication unit 120 sends a delay information report. If at least one of conditions (a1) to (a4) and (d2) to (d4) is met, the communication unit 120 can send a delay information report without determining condition (e2). For condition (d1), delay information reports are more likely to be sent more frequently than for other conditions. With this configuration, it is possible to effectively prevent the frequent triggering of unnecessary delay information reports.

[0186] When the unit of data for the reporting object corresponds to more than one PDU set, the terminal device 10 may operate as follows. Assume that for a specific PDU, a triggering condition (e.g., condition (d1)) is met, and a delay information report for the PDU set to which that PDU belongs is sent. Even if the triggering condition is subsequently met for other PDUs included in the PDU set to which that PDU belongs, the terminal device 10 will not trigger or send a delay information report for that PDU set.

[0187] Based on the above configuration, by applying at least one of the conditions (e1) and (e2), it is possible to prevent the frequent triggering of unnecessary delay information reports. Therefore, the possibility of increased communication load can be reduced.

[0188] Furthermore, aspects 1-1 and 1-2 can be combined. That is, the terminal device 10 can use conditions (e1) and (e2) to trigger or send a delay information report. For example, if the triggering condition is met but conditions (e1) and (e2) are not met, the communication unit 120 can send a delay information report.

[0189] In another example, one of the conditions (e1) and (e2) can take precedence. For example, when starting... Figure 18 During the process, the control unit 110 determines whether the triggering condition is met (S1801). The triggering condition may include at least one of conditions (a1) to (a4) and (d1) to (d4). If the triggering condition is not met, the communication unit 120 does not send a delay information report.

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

[0191] Conversely, if condition (e1) in step S1802 is not met, the communication unit 120 sends a delay information report (S1804). Additionally, if condition (e2) in step S1803 is not met, the communication unit 120 sends a delay information report (S1804).

[0192] Thus, if condition (e1) is met and condition (e2) is not met, the communication unit 120 can send a delay information report. That is, even if the first timer is running, the communication unit 120 can send a delay information report if a delay information report for new data is triggered.

[0193] 2. Second Implementation Method Next, the configuration of the second embodiment will be described. Hereinafter, only the parts that differ from the first embodiment will be described; the parts that are the same as the first embodiment will be omitted. Therefore, as long as there is no contradiction, the configuration of the first embodiment and its variations can be applied to the configuration described in this embodiment.

[0194] The delay information report includes delay information for uplink data with low latency requirements. Therefore, when the transmission of the delay information report is delayed, this delay information report may become unnecessary information for the base station equipment 20. For example, in... Figure 15 In the example, suppose the delay information report that should be sent at time t1 is delayed by more than 5ms. In this case, information related to the remaining time corresponding to LCG 1 may become unnecessary information for the base station device 20. In addition, when unnecessary delay information reports are sent, the communication load (i.e., overhead) may increase.

[0195] Considering the above, when a delay information report is triggered by the aforementioned triggering conditions, the terminal device 10 determines whether the available uplink resources can accommodate the delay information report. Based on this determination, the terminal device 10 performs predetermined processing associated with the transmission of the delay information report. The predetermined processing includes, for example, sending a scheduling request (SR) and canceling the transmission of the delay information report, at least one of these. Hereinafter, aspects 2-1 and 2-2 will be described.

[0196] - Aspect 2-1 When a delay information report is triggered, the terminal device 10 determines whether the following condition (f1) is met. (f1) Uplink resources are capable of accommodating delay information reports. That is, uplink resources can be used for new transmissions of delay information reports, and uplink resources are capable of accommodating delay information reports.

[0197] If condition (f1) is met, terminal device 10 sends a delay information report. Conversely, if condition (f1) is not met, i.e., if it is determined that uplink resources cannot accommodate the delay information report, terminal device 10 performs processing for sending the SR, as described above. The processing for sending the SR may include one or more processes associated with the SR. Therefore, when a delay information report is triggered, terminal device 10 can perform processing for sending the SR based on the inability of uplink resources to accommodate the delay information report. Base station device 20 allocates uplink resources to terminal device 10 according to the SR. Terminal device 10 can use the allocated uplink resources to send the delay information report.

[0198] When it begins Figure 19 During the illustrated process, the control unit 110 determines whether the triggering condition is met (S1901). The triggering condition may include at least one of conditions (a1) to (a4) and (d1) to (d4). If the triggering condition is not met, the communication unit 120 does not send a delay information report.

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

[0200] Furthermore, if condition (f1) is not met, the control unit 110 can determine whether the second timer used to delay the transmission of the SR is running. For example, the second timer could 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 can send the SR even when the second timer is running. That is, the communication unit 120 can send the SR regardless of whether the second timer is running. Since the delay information report includes delay information of uplink data with low latency requirements, it is preferable to send it to the base station device 20 as soon as possible. According to this configuration, uplink resources used for sending the delay information report can be allocated to the terminal device 10 more quickly.

[0202] Furthermore, a condition (f1) can be applied to a specific condition among the triggering conditions. For example, condition (f1) can be applied to condition (d1). For example, if condition (d1) is met and condition (f1) is not met, the communication unit 120 sends an SR. When a delay information report is triggered by condition (d1), this means that the remaining time until the delay information report is sent is relatively short. By applying condition (f1) to condition (d1), uplink resources used for sending delay information reports can be allocated to the terminal device 10 more quickly.

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

[0204] Based on the above configuration, uplink resources can be allocated to terminal device 10 by sending SR. For example, when a delay information report is triggered by condition (d1), base station device 20 can receive the delay information report before the first deadline of the data corresponding to the delay information included in the delay information report has elapsed. Base station device 20 can then appropriately allocate uplink resources to terminal device 10.

[0205] - Aspect 2-2 When a delay information report is triggered, the terminal device 10 determines whether the following condition (g1) is met. (g1) Uplink resources are sufficient to accommodate delay information reports until the predetermined second deadline. That is, uplink resources are available for new transmissions of delay information reports, and uplink resources are sufficient to accommodate delay information reports until the second deadline.

[0206] Terminal device 10 can determine a second time limit for condition (g1) based on the aforementioned remaining time. That is, the second time limit can be the same as the first time limit. More specifically, the second time limit can be the time limit for completing the transmission of a portion or all of the data of the reporting object. The second time limit can be a time limit determined based on PDB or PSDB. The second time limit can be a time limit determined based on the PDB or PSDB configured for a portion or all of the data of the reporting object. The second time limit can be a value obtained by adding the PDB or PSDB to the first time point. The second time limit can be an earlier value than the value obtained by adding the PDB or PSDB to the first time point.

[0207] If condition (g1) is met, terminal device 10 sends a delay information report. Conversely, if condition (g1) is not met, terminal device 10 cancels the sending or triggering of the delay information report, as per the predetermined processing described above. That is, if a delay information report is triggered, the sending or triggering of the delay information report is canceled because uplink resources cannot accommodate the delay information report before the second deadline. In other words, if condition (g1) is not met, terminal device 10 cancels the triggering of the delay information report (i.e., the triggering caused by the meeting of the triggering condition).

[0208] Condition (g1) can also be replaced by the following condition: the triggering of the delay information report has not been cancelled before the second deadline. Therefore, terminal device 102 can cancel the sending or triggering of the delay information report based on the fact that the triggering of the delay information report has not been cancelled before the second deadline.

[0209] Additionally, if uplink resources available for new transmissions and capable of accommodating delay information reports do not exist before the second deadline, 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 cannot be transmitted before the delay information included in the report expires, terminal device 10 may cancel the transmission or triggering of the delay information report.

[0210] When it begins Figure 20 During the process shown, the control unit 110 determines whether the triggering condition is met (S2001). The triggering condition may include at least one of conditions (a1) to (a4) and (d1) to (d4). If the triggering condition is not met, the communication unit 120 does not send a delay information report.

[0211] On the other hand, if the triggering condition is met, the control unit 110 determines whether condition (g1) is met (S2002). If condition (g1) is met, the communication unit 120 sends a delay information report (S2003). Conversely, if condition (g1) is not met, the communication unit 120 cancels the sending or triggering of the delay information report (S2004). Furthermore, the control unit 110 may cancel the sending or triggering of the delay information report and send a cancellation instruction to the communication unit 120.

[0212] Furthermore, if the above conditions (c1) or (c2) are met, the communication unit 120 may cancel the transmission or triggering of the delay information report.

[0213] A condition (g1) can be applied to a specific condition among the triggering conditions. For example, condition (g1) can be applied to condition (d1). For example, if condition (d1) is met and condition (g1) is not met, the communication unit 120 cancels the transmission or triggering of the delay information report. When the delay information report is triggered by condition (d1), this means that the remaining time until the transmission of the delay information report is completed is small. In such a case, even if the delay information report is sent to the base station device 20, the data corresponding to the delay information included in the delay information report may exceed the first time limit. That is, the delay information included in the delay information report may not be useful information for the base station device 20, and may be unnecessary information. When unnecessary delay information reports are sent, the communication load may increase. According to this configuration, the transmission of unnecessary delay information reports can be prevented.

[0214] Terminal device 10 can start a third timer at the time when the delay information report is triggered (i.e., the triggering condition is met), and determine a second timeout based on the third timer. The third timer expires within a predetermined period. The period of the third timer can be selected from multiple values. For example, terminal device 10 can determine that the condition (g1) is not met at the time when the third timer expires. Terminal device 10 can receive an RRC message from base station device 20 that includes information related to the third timer.

[0215] In the configuration of a BSR that includes delay information reporting, information related to the third timer can be included in the IE associated with the BSR (e.g., the BSR-Config IE).

[0216] A third timer can be configured for an LCH or LCG. Information related to the third timer can be configured in the IE associated with the LCH or LCG. Examples of such IEs include the LogicalChannelConfig IE and the LogicalChannelGroup IE. In this configuration, the third timer is started at the time when a delay information report for an LCH or LCG with a third timer configured is triggered. Therefore, when the third timer expires, the sending or triggering of a delay information report for an LCH or LCG with a third timer configured is canceled. Furthermore, delay information reports can be sent for LCHs or LCGs without a third timer configured. In other words, the triggering of delay information reports for LCHs or LCGs without a third timer configured can be continued.

[0217] A third timer can be configured for a PDU or PDU set. Information related to the third timer can be configured in the IE associated with the PDU or PDU set. For example, information related to the third timer can be configured in the IE associated with the PDU or PDU set included in an RRC message. In this configuration, the third timer is started at the time when a delay information report for a PDU or PDU set with a third timer configured is triggered. Therefore, when the third timer expires, the sending or triggering of a delay information report for a PDU or PDU set with a third timer configured is cancelled. Furthermore, delay information reports can be sent for PDUs or PDU sets without a third timer configured. In other words, the triggering of delay information reports for PDUs or PDU sets without a third timer configured can be continued.

[0218] A third timer can be configured for data bursts. Information related to the third timer can be configured in the IE associated with the data burst. For example, information related to the third timer can be configured in the IE associated with the data burst included in the RRC message. In this configuration, the third timer is started at the time when a delay information report for a data burst configured with the third timer is triggered. Therefore, when the third timer expires, the sending or triggering of a delay information report for a data burst configured with the third timer is cancelled. Furthermore, delay information reports can be sent for data bursts without a configured third timer. In other words, the triggering of delay information reports for data bursts without a configured third timer can be continued.

[0219] The above configuration prevents the transmission of unnecessary delay information reports. Since uplink resources are not used for unnecessary delay information reports, the likelihood of increased communication load is reduced.

[0220] Aspects 2-1 and 2-2 can be combined. That is, terminal device 10 can use conditions (f1) and (g1) to perform predetermined processing associated with the transmission of delay information reports. For example, control unit 110 can perform... Figure 19 After step S1904 of the process, it is determined whether condition (g1) is met. If condition (g1) is not met, the communication unit 120 may cancel the transmission or triggering of the delay information report. Thus, if there are no uplink resources available to accommodate the delay information report before the second deadline after the terminal device 10 sends the SR, the terminal device 10 may cancel the transmission or triggering of the delay information report.

[0221] 3. Variation Example It should be understood that although this disclosure has been described according to the above embodiments, this disclosure is not limited to these embodiments or constructions. This disclosure also includes various variations and equivalent modifications. Other combinations including one or more elements included in the above embodiments also fall within the scope or concept of this disclosure.

[0222] exist Figures 16-18 In this implementation, after determining the trigger condition, the constraint conditions (conditions (e1) and / or (e2)) are determined, but this configuration is not limited to this. For example, the determination of the constraint conditions may precede the determination of the trigger condition. The terminal device 10 may determine whether to determine the trigger condition based on whether the constraint conditions are met. For example, if the constraint conditions are met, the terminal device 10 does not determine the trigger condition. That is, the delay information report is not triggered. If the constraint conditions are not met, the terminal device 10 determines the trigger condition. Therefore, the first implementation may include "the aspect where the terminal device 10 uses the constraint conditions to cancel the triggering of the delay information report after the trigger condition is met" and "the aspect where the terminal device 10 does not determine the trigger condition for the delay information report based on the constraint conditions being met".

[0223] exist Figure 19In this configuration, after determining the trigger condition, the condition (f1) is determined, but this is not limited to this configuration. For example, the determination of condition (f1) may precede the determination of the trigger condition. The terminal device 10 may determine whether to determine the trigger condition based on whether condition (f1) is met. If condition (f1) is met, the terminal device 10 determines the trigger condition. If condition (f1) is not met, the terminal device 10 performs the processing for sending the SR. Therefore, aspect 2-1 of the second embodiment may include "the aspect of the terminal device 10 performing the processing for sending the SR when the trigger condition is met and condition (f1) is not met", and "the aspect of the terminal device 10 performing the processing for sending the SR without determining the trigger condition when condition (f1) is not met".

[0224] exist Figure 20 In this configuration, after determining the trigger condition, the condition (g1) is determined, but this is not limited to this configuration. For example, the determination of condition (g1) can be performed before the determination of the trigger condition. The terminal device 10 can determine whether to determine the trigger condition based on whether condition (g1) is met. If condition (g1) is met, the terminal device 10 determines the trigger condition. If condition (g1) is not met, 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 "the aspect of canceling the triggering of the delay information report (i.e., the triggering caused by the meeting of the trigger condition) when condition (g1) is not met" and "the aspect of not determining the trigger condition of the delay information report when condition (g1) is not met".

[0225] The words, phrases, etc., used in the above embodiments are merely exemplary and can be replaced with substantially the same or similar expressions. In particular, since the technologies involved in the above embodiments are related to technical specifications, the expressions in the above embodiments can be replaced with substantially the same or similar expressions in technical specifications (e.g., the technical specifications cited in this application specification).

[0226] In the above embodiments, the information sent and received may include the same or different messages or elements already described in the technical specifications, or it may include newly defined messages or elements. In the above embodiments, the information sent and received may use different layers and / or different channels than those described in the above embodiments.

[0227] The manner and / or functions provided by the device described in the above embodiments can be provided by software recorded in a physical memory device and a computer executing the software, by software alone, by hardware alone, or by a combination thereof. For example, in the case where any of the above-described devices is provided by electronic circuitry as hardware, it can be provided by digital circuitry or analog circuitry including multiple logic circuits.

[0228] The device described in the above embodiments executes a program stored in a non-transitory tangible storage medium. By executing this program, a method corresponding to the program is performed.

[0229] 4. Postscript The above-described embodiments and variations may be described in whole or in part as in the following notes, but are not limited to the content of the following notes. Hereinafter, the relationship of a note belonging to a note belonging to a note belonging to a note belonging to a note belonging to a note is described. All the subordinate relationships of the notes described below are included in the above-described embodiments.

[0230] (Note 1) A terminal device (10) includes: The control unit (110) is configured to determine whether to trigger the aforementioned delay information report using predetermined limiting conditions that restrict the transmission of the delay information report, the aforementioned delay information report including delay-related delay information for predetermined data; and The communications unit (120) is configured to send the aforementioned delay information report to the base station equipment (20).

[0231] (Note 2) According to the terminal device described in Appendix 1, the aforementioned limiting conditions include at least one of the following conditions: Conditions relating to the timer used to prevent the transmission of the aforementioned delay information report; and Conditions relating to whether the aforementioned delay information report for the aforementioned predetermined data has been sent.

[0232] (Note 3) According to the terminal device described in Appendix 2, the aforementioned limiting conditions include the aforementioned conditions related to the aforementioned timer. The aforementioned control unit is configured as follows: When the aforementioned timer is running, the aforementioned delay information report will not be triggered. If the aforementioned timer is not running, the aforementioned delay information report will be triggered.

[0233] (Note 4) According to the terminal device described in Appendix 2, the aforementioned limiting conditions include the aforementioned conditions related to the aforementioned timer. The aforementioned control unit is configured to start the aforementioned timer at the time point when the aforementioned delay information report is triggered or when the aforementioned delay information report is sent.

[0234] (Note 5) According to the terminal device described in Appendix 2, the aforementioned limiting conditions include the aforementioned conditions related to the aforementioned timer. The aforementioned communication unit is configured to receive information related to the aforementioned timer from the aforementioned base station equipment.

[0235] (Note 6) According to the terminal device described in Appendix 2, the aforementioned limiting conditions include the aforementioned conditions related to the aforementioned timer. The aforementioned communication unit is configured to receive information from the aforementioned base station equipment indicating whether to apply the aforementioned timer.

[0236] (Note 7) According to the terminal device described in Appendix 2, the aforementioned limiting conditions include those relating to whether the aforementioned delay information report for the aforementioned predetermined data has been sent. The aforementioned control unit is configured as follows: If the aforementioned delay information report for the predetermined data has already been sent, the aforementioned delay information report will not be triggered. The aforementioned delay information report is triggered before the aforementioned delay information report for the predetermined data has been sent.

[0237] (Note 8) According to the terminal device described in Appendix 1, the aforementioned control unit is configured to trigger the aforementioned delay information report using predetermined triggering conditions. The aforementioned control unit is configured as follows: If the aforementioned triggering conditions and the aforementioned limiting conditions are met, the aforementioned delay information report will not be triggered. If the aforementioned triggering conditions are met and the aforementioned limiting conditions are not met, the aforementioned delay information report will be triggered.

[0238] (Note 9) According to the terminal device described in Appendix 8, the aforementioned triggering conditions include conditions related to the remaining time before the predetermined data transmission period expires. The aforementioned restrictions include conditions relating to the timer used to prohibit the sending of the aforementioned delay information reports. The aforementioned control unit is configured as follows: If the remaining time is below a predetermined threshold and the aforementioned timer is running, The aforementioned delay information report will not be triggered.

[0239] (Postscript 10) According to the terminal device described in Appendix 9, the aforementioned control unit is configured as follows: If the remaining time is below the aforementioned threshold and the aforementioned timer is not running, This triggers the aforementioned delay information report.

[0240] (Postscript 11) According to the terminal device described in Appendix 9, the aforementioned control unit is configured to determine the aforementioned remaining time based on the Packet Delay Budget (PDB) or Protocol Data Unit-Set Delay Budget (PSDB).

[0241] (Postscript 12) According to the terminal device described in Appendix 8, the aforementioned triggering conditions include conditions related to the remaining time before the predetermined data transmission period expires. The aforementioned limitations include conditions relating to whether the aforementioned delay information report for the predetermined data has been sent. The aforementioned control unit is configured as follows: If the remaining time is below a predetermined threshold, and the aforementioned delay information report for the predetermined data has already been sent, The aforementioned delay information report will not be triggered.

[0242] (Postscript 13) According to the terminal device described in Appendix 12, the aforementioned control unit is configured as follows: If the remaining time is below the aforementioned threshold, and the aforementioned delay information report for the predetermined data has not yet been sent, This triggers the aforementioned delay information report.

[0243] (Postscript 14) According to the terminal device described in Appendix 12, the aforementioned control unit is configured to determine the aforementioned remaining time based on the Packet Delay Budget (PDB) or Protocol Data Unit-Set Delay Budget (PSDB).

[0244] (Postscript 15) According to the terminal device described in Appendix 1, the aforementioned latency information report is a buffer status report (BSR) that includes the aforementioned latency information and buffer size information related to the buffer size.

[0245] (Postscript 16) According to the terminal device described in Appendix 15, the aforementioned BSR includes: Fields including the aforementioned latency information and cache size information; and Fields that include the aforementioned cache size information but exclude the aforementioned delay information.

[0246] (Postscript 17) According to any one of the appendices 1 to 16, the aforementioned communication unit is configured to transmit a MAC PDU (Medium Access Control Protocol Data Unit) including the aforementioned delay information report. The identification information used to identify the aforementioned delay information report is included in the MAC CE or header, and the aforementioned MAC CE is included in the MAC PDU.

[0247] (Postscript 18) According to any one of Appendices 1 to 17, the aforementioned delay information is: Information related to delay time, or Information related to data subject to time constraints or requirements.

[0248] (Postscript 19) According to any one of Appendices 1 to 18, the aforementioned predetermined data is: Data corresponding to a logical channel; Data corresponding to a Logical Channel Group (LCG); Data corresponding to one or more Protocol Data Unit Sets (PDU sets); or Data corresponding to more than one data burst.

[0249] (Postscript 20) A method for a terminal device (10) includes: The determination of whether to trigger the aforementioned delay information report is made using predetermined limiting conditions that restrict the transmission of the delay information report; the aforementioned delay information report includes delay information related to the delay of predetermined data; and Send the aforementioned delay information report to the base station equipment (20).

[0250] (Postscript 21) A program that causes the processor (101) in the terminal device (10) to execute: The determination of whether to trigger the aforementioned delay information report is made using predetermined limiting conditions that restrict the transmission of the delay information report; the aforementioned delay information report includes delay information related to the delay of predetermined data; and Send the aforementioned delay information report to the base station equipment (20).

[0251] (Postscript 22) A non-transient tangible recording medium containing a program that causes a processor (101) in a terminal device (10) to execute: The determination of whether to trigger the aforementioned delay information report is made using predetermined limiting conditions that restrict the transmission of the delay information report; the aforementioned delay information report includes delay information related to the delay of predetermined data; and Send the aforementioned delay information report to the base station equipment (20).

[0252] (Postscript 23) A base station device (20) includes: The communication unit (220) is configured to receive a delay information report from the terminal device (10), the delay information report including delay information related to a predetermined data delay; and The control unit (210) is configured to allocate radio resources to the aforementioned terminal device based on the aforementioned delay information report. The aforementioned communication unit is configured to send configuration information to the aforementioned terminal device, and the aforementioned configuration information is associated with predetermined limiting conditions that restrict the transmission of the aforementioned delay information report.

[0253] (Postscript 24) According to the base station equipment described in Appendix 23, the aforementioned configuration information includes conditions related to a timer used to prohibit the transmission of the aforementioned delay information report.

[0254] (Postscript 25) According to the base station equipment described in Appendix 23 or 24, the aforementioned configuration information includes information indicating whether the aforementioned timer is applied.

[0255] (Postscript 26) A method for a base station device (20) includes: Receive a delay information report from the terminal device (10), the delay information report including delay information related to the delay of the predetermined data; Based on the aforementioned delay information report, wireless resources are allocated to the aforementioned terminal devices; and Configuration information is sent to the aforementioned terminal device, and the configuration information is associated with predetermined restrictions that limit the transmission of the aforementioned delay information report.

[0256] (Postscript 27) A program that causes the processor (201) in the base station equipment (20) to execute: Receive a delay information report from the terminal device (10), the delay information report including delay information related to the delay of the predetermined data; Based on the aforementioned delay information report, wireless resources are allocated to the aforementioned terminal devices; and Configuration information is sent to the aforementioned terminal device, and the configuration information is associated with predetermined restrictions that limit the transmission of the aforementioned delay information report.

[0257] (Postscript 28) A non-transient tangible recording medium storing a program that causes a processor (201) in a base station device (20) to execute: Receive a delay information report from the terminal device (10), the delay information report including delay information related to the delay of the predetermined data; Based on the aforementioned delay information report, wireless resources are allocated to the aforementioned terminal devices; and Configuration information is sent to the aforementioned terminal device, and the configuration information is associated with predetermined restrictions that limit the transmission of the aforementioned delay information report.

[0258] (Postscript 29) A terminal device (10) includes: The receiving unit (122) receives a Radio Resource Control (RRC) message from the base station equipment (20). The aforementioned RRC message includes information for configuring the identifier (ID) of the logical channel group (LCG) to which the logical channel (LCH) belongs, and information for indicating the threshold of the data for the aforementioned LCG for controlling the triggering of the Delay Status Report (DSR). The control unit (110) controls the triggering of the aforementioned DSR based on the remaining time of the earliest deadline for the data of the aforementioned LCG being less than the aforementioned threshold and the aforementioned DSR for the data of the aforementioned LCG not being sent; and The transmitting unit (121) transmits the aforementioned DSR and scheduling request (SR). When the aforementioned DSR is triggered, the aforementioned transmitting unit transmits the aforementioned DSR based on having uplink resources capable of accommodating the aforementioned DSR, and transmits the aforementioned SR based on not having uplink resources capable of accommodating the aforementioned DSR.

[0259] (Note 30) According to the terminal device described in Appendix 29, the aforementioned DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; A field indicating the remaining time for the earliest deadline of the data for the aforementioned LCG; and A field indicating the cache size related to the aforementioned LCG.

[0260] (Postscript 31) According to the terminal device described in Appendix 30, the aforementioned control unit switches between a first table and a second table different from the aforementioned first table to configure the aforementioned field indicating the aforementioned cache size.

[0261] (Note 32) According to the terminal device described in Appendix 29, the aforementioned DSR includes: Each bit in each bit indicates whether the cache size field for each LCG exists; and Fields including information related to the data of the aforementioned LCG when the remaining time is below the aforementioned threshold.

[0262] (Postscript 33) According to any one of the appendices 29 to 32, the aforementioned DSR is a MAC CE (Medium Access Control Control Element), the aforementioned MAC CE includes a sub-header, the aforementioned sub-header includes an extended Logical Channel Identifier (eLCID) for identifying the aforementioned DSR.

[0263] (Postscript 34) A method for a terminal device (10) includes: The base station device (20) receives a Radio Resource Control (RRC) message, which includes information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information for the threshold of data for the aforementioned LCG that indicates the triggering of the Delay Status Report (DSR). The triggering of the aforementioned DSR is controlled based on the remaining time of the earliest deadline for the aforementioned LCG data being less than the aforementioned threshold, and the aforementioned DSR for the aforementioned LCG data not being sent; and Send the aforementioned DSR and scheduling request (SR). The aforementioned transmission includes: when the aforementioned DSR is triggered, Based on uplink resources capable of accommodating the aforementioned DSR, the aforementioned DSR is transmitted; and The aforementioned SR is sent because there are no uplink resources available to accommodate the aforementioned DSR.

[0264] (Postscript 35) According to the terminal device method described in Appendix 34, the aforementioned DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; A field indicating the remaining time for the earliest deadline of the data for the aforementioned LCG; and A field indicating the cache size related to the aforementioned LCG.

[0265] (Postscript 36) The method for the terminal device according to Appendix 35 further includes: switching between a first table and a second table different from the aforementioned first table to configure the aforementioned field indicating the aforementioned cache size.

[0266] (Postscript 37) According to the terminal device method described in Appendix 34, the aforementioned DSR includes: Each bit in each bit indicates whether the cache size field for each LCG exists; and Fields including information related to the data of the aforementioned LCG when the remaining time is below the aforementioned threshold.

[0267] (Postscript 38) According to any one of the appendices 34 to 37, the aforementioned DSR is a MAC CE (Medium Access Control Control Element), the aforementioned MAC CE includes a sub-header, the aforementioned sub-header includes an extended Logical Channel Identifier (eLCID) for identifying the aforementioned DSR.

[0268] (Postscript 39) A program that causes the processor (101) in the terminal device (10) to execute: The base station device (20) receives a Radio Resource Control (RRC) message, which includes information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information for the threshold of data for the aforementioned LCG that indicates the triggering of the Delay Status Report (DSR). The triggering of the aforementioned DSR is controlled based on the remaining time of the earliest deadline for the aforementioned LCG data being less than the aforementioned threshold, and the aforementioned DSR for the aforementioned LCG data not being sent; and Send the aforementioned DSR and scheduling request (SR). The aforementioned transmission includes: when the aforementioned DSR is triggered, Based on uplink resources capable of accommodating the aforementioned DSR, the aforementioned DSR is transmitted; and The aforementioned SR is sent because there are no uplink resources available to accommodate the aforementioned DSR.

[0269] (Postscript 40) A non-transient tangible recording medium containing a program that causes a processor (101) in a terminal device (10) to execute: The base station device (20) receives a Radio Resource Control (RRC) message, which includes information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information for the threshold of data for the aforementioned LCG that indicates the triggering of the Delay Status Report (DSR). The triggering of the aforementioned DSR is controlled based on the remaining time of the earliest deadline for the aforementioned LCG data being less than the aforementioned threshold, and the aforementioned DSR for the aforementioned LCG data not being sent; and Send the aforementioned DSR and scheduling request (SR). The aforementioned transmission includes: when the aforementioned DSR is triggered, Based on uplink resources capable of accommodating the aforementioned DSR, the aforementioned DSR is transmitted; and The aforementioned SR is sent because there are no uplink resources available to accommodate the aforementioned DSR.

[0270] Furthermore, the disclosures in the aforementioned prior art documents and references are incorporated herein by reference.

Claims

1. A terminal device (10), comprising: The receiving unit (122) receives a Radio Resource Control (RRC) message from the base station device (20). The RRC message includes information for configuring the identifier (ID) of the logical channel group (LCG) to which the logical channel (LCH) belongs, and information for indicating the threshold of data for the LCG for controlling the triggering of delay status report (DSR). The control unit (110) controls the triggering of the DSR based on the remaining time of the earliest deadline of the data relative to the LCG being lower than the threshold and the DSR of the data about the LCG not being sent; and The transmitting unit (121) transmits the DSR and the scheduling request (SR). When the DSR is triggered, Based on uplink resources capable of accommodating the DSR, the transmitting unit transmits the DSR. The transmitting unit transmits the SR because it does not have uplink resources capable of accommodating the DSR.

2. The terminal device according to claim 1, The DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; A field indicating the remaining time of the earliest deadline for the data relative to the LCG; as well as A field indicating the cache size associated with the LCG.

3. The terminal device according to claim 2, The control unit switches between a first table and a second table different from the first table to configure the field indicating the cache size.

4. The terminal device according to claim 1, The DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; as well as Fields including information relating to the data of the LCG when the remaining time is below the threshold.

5. The terminal device according to any one of claims 1 to 4, The DSR is a MAC CE (Media Access Control Unit), which includes a sub-header that includes an Extended Logical Channel Identifier (eLCID) for identifying the DSR.

6. A method for a terminal device (10), comprising: The base station device (20) receives a Radio Resource Control (RRC) message, the RRC message including information for configuring the identifier (ID) of the Logical Channel Group (LCG) to which the Logical Channel (LCH) belongs, and information indicating the threshold for data of the LCG for controlling the triggering of Delay Status Report (DSR); The triggering of the DSR is controlled based on the remaining time of the earliest deadline of the data relative to the LCG being lower than the threshold and the DSR of the data about the LCG not being sent. as well as Send the DSR and the scheduling request (SR). The transmission includes: when the DSR is triggered. The DSR is transmitted based on uplink resources that can accommodate the DSR; as well as The SR is sent because there are no uplink resources available to accommodate the DSR.

7. The method of the terminal device according to claim 6, The DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; A field indicating the remaining time of the earliest deadline for the data relative to the LCG; as well as A field indicating the cache size associated with the LCG.

8. The method of the terminal device according to claim 7, Also includes: Switch between a first table and a second table different from the first table to configure the field indicating the cache size.

9. The method of the terminal device according to claim 6, The DSR includes: Each bit in the set indicates whether the cache size field for each LCG exists; as well as Fields including information relating to the data of the LCG when the remaining time is below the threshold.

10. The method of the terminal device according to any one of claims 6 to 9, The DSR is a MAC CE (Media Access Control Unit), which includes a sub-header that includes an Extended Logical Channel Identifier (eLCID) for identifying the DSR.

Images