Terminal apparatus, and terminal apparatus method

Description

/ 82 Terminal and base station apparatus, and method of terminal apparatus. Cross-reference to related request.

[001] This application is based on and claims the benefit of priority of Japanese Patent Application No. 2023-62921, filed on April 7, 2023, the content of which is incorporated herein by reference in its entirety. Technical Field

[002] The present description refers to a terminal apparatus and a method of a terminal apparatus. Fundamentals

[003] In recent years, an extended reality (XR) technology has been developed. XR is a concept that includes multimedia integration technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and substitutional reality (SR). In XR, three-dimensional image data in a time series in a real and / or virtual space, audio data from a plurality of channels (stereo, 5.1ch or similar), other data presented to a user, control data, and the like are transmitted and received in parallel. XR requires low latency and high reliability in order to maintain and enhance the quality of the user experience.

[004] In NPL 1, the implementation of XR in Fifth Generation New Radio (5G NR) is studied, with radio specifications defined by the Third Generation Partnership Project (3GPP, Third Generation Partnership Project (registered trademark)). List of Citations Non-Patented Literature

[005] [NPL 1] 3GPP TR 38.838 V17.0.0 (2021-12) Petition 870250087336, dated 09 / 26 / 2025, page 107 / 195 / 82 [NPL 2] 3GPP TS 38.321 V17.2.0 (2022-09) [NPL 3] 3GPP TS 38.331 V17.2.0 (2022-09) SUMMARY

[006] Meanwhile, NPL 2 describes a Buffer Status Reporting (BSR) procedure. Additionally, NPL 3 describes parameters that are transmitted from a base station device and used for the BSR. The BSR indicates, for specific data, an uplink data buffer size. The specific data corresponds to a logical channel group (LCG). A terminal device calculates a buffer size for each LCG and transmits the BSR including the calculated buffer size to a base station device. Based on the BSR, the base station device allocates a radio resource to the terminal device.

[007] It is assumed that XR is implemented under several requirements, including a low latency requirement. Thus, uplink communication from a terminal device requires radio resource allocation taking these requirements into account. However, in the BSR described in NPLs 2 and 3, the terminal device can only transmit one piece of information (i.e., information related to a buffer size) for certain data. This small amount of information reported to a base station device may prevent the base station device from adequately allocating a radio resource to the terminal device. Therefore, reporting certain information (e.g., delay-related information) in addition to the buffer size in the BSR is being studied. Furthermore, reporting this information to the base station device using a reporting method different from the BSR is also being studied.

[008] The inventor found a problem in that a procedure is needed to properly determine whether to trigger or transmit a report of certain information. Meanwhile, in Petition 870250087336, dated 09 / 26 / 2025, page 108 / 195 / 82 In NPLs 2 and 3, this procedure is not described. It should be noted that the problem is also present in a typical terminal device and in a base station device, in addition to one implemented with XR.

[009] The present description provides a technique that can properly determine whether to trigger or transmit a report of certain information.

[0010] A terminal device in the present description includes: a receiver configured to receive, from a base station device, a radio resource control (RRC) message including information to configure an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for controlling the triggering of a delay status report (DSR) for LCG data; and a controller configured to control the triggering of the DSR based on the fact that the remaining time relative to a nearest deadline for the LCG data becomes less than the threshold and the DSR is not transmitted for the LCG data. The controller is configured to cancel, in the event that a deadline for the LCG data associated with the DSR expires, the DSR that was triggered and not canceled.

[0011] A method of a terminal device in the present description includes receiving, from a base station device, a radio resource control (RRC) message including information to set up an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for controlling the triggering of a delay state report (DSR) for LCG data, controlling the triggering of the DSR based on the fact that the remaining time relative to a nearest deadline for the LCG data becomes less than the threshold and the DSR is not transmitted for the LCG data, and canceling, in the event that a deadline for the LCG data associated with the DSR expires, the DSR that Petition 870250087336, dated 09 / 26 / 2025, p. 109 / 195 / 82 was filed and not cancelled.

[0012] The configuration described above makes it possible to properly determine whether to trigger or transmit the delay information report. It should be noted that the configuration described above may provide, instead of or in addition to this effect, another effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The objects, features and advantages described above and others in this description will become more apparent in the following detailed description with reference to the accompanying drawings, in which: Figure 1 is a diagram illustrating a communication system S according to a first modality; Figure 2 is a diagram illustrating a protocol stack in the U-plane according to the first modality; Figure 3 is a diagram illustrating a protocol stack in the C-plane according to the first modality; Figure 4 is a block diagram schematically illustrating a hardware configuration of a terminal device 10 according to the first embodiment; Figure 5 is a block diagram schematically illustrating a functional configuration of terminal device 10 according to the first embodiment; Figure 6 is a block diagram schematically illustrating a hardware configuration of a base station device 20 according to the first modality; Figure 7 is a block diagram schematically illustrating a functional configuration of the base station 20 device according to the first modality; Figure 8 is a diagram illustrating a radio frame configuration according to a first mode; Petition 870250087336, dated 09 / 26 / 2025, page 110 / 195 / 82 Figure 9 is a diagram illustrating a Short BSR configuration; Figure 10 is a diagram illustrating a Long BSR configuration; Figure 11 is a sequence diagram illustrating a process flow of the terminal device 10 and the base station device 20 according to the first embodiment; Figure 12 is a diagram illustrating an example of a Long BSR configuration including delay information; Figure 13 is a diagram illustrating another example of the Long BSR configuration including delay information; Figure 14 is a diagram illustrating another example of the Long BSR configuration including delay information; Figure 15 is a diagram illustrating an example in which a delay information report is transmitted; Figure 16 is a sequence diagram illustrating a process flow of terminal device 10 according to Aspect 1-1 of the first embodiment; Figure 17 is a sequence diagram illustrating a process flow of terminal device 10 according to Aspect 1-2 of the first embodiment; Figure 18 is a sequence diagram illustrating a process flow of terminal device 10 according to a change from the first mode; Figure 19 is a sequence diagram illustrating a process flow of terminal device 10 according to Aspect 2-1 of the second embodiment; and Figure 20 is a sequence diagram illustrating a process flow of terminal device 10 according to Aspect 2-2 of the second embodiment. Petition 870250087336, dated 09 / 26 / 2025, page 111 / 195 / 82 modality. DETAILED DESCRIPTION

[0014] Hereafter, embodiments of the present description will be described in detail with reference to the attached drawings. It should be noted that, in the Descriptive Report and in the drawings, elements to which similar descriptions apply are indicated by the same reference signs, and repetitive descriptions may therefore be omitted.

[0015] Each embodiment described below is merely an example of a configuration that may implement the present description. Each embodiment described below may be suitably modified or altered according to the configuration of an apparatus to which the present description is applied and various conditions. Not all combinations of elements included in each embodiment described below are necessarily required to implement the present description, and some elements may suitably be omitted. Therefore, the scope of the present description is not limited by the configuration described in each embodiment described below. Configurations in which a plurality of configurations described in the embodiments below are combined may also be employed provided that the configurations are not inconsistent with each other. 1. First Modality 1.1. Communication System

[0016] As illustrated in Figure 1, a communication system S according to a first embodiment includes one or more terminal devices 10, one or more base station devices 20 and a central network 30. The communication system S is configured in accordance with certain technical specifications (TS). For example, the communication system S may conform to technical specifications defined by 3GPP (e.g., 5G, advanced 5G, 6G or similar). Petition 870250087336, dated 09 / 26 / 2025, page 112 / 195 / 82

[0017] In the S communication system, a user plane, in which user data is transmitted and received, and a control plane, in which control data is transmitted and received, are configured separately. In other words, the S communication system provides support for the C / U split. The user plane is abbreviated to U-plane, and the control plane is abbreviated to C-plane.

[0018] Terminal device 10 may be a device that performs radio communication with base station device 20, and may be, for example, user equipment (UE) that operates in accordance with 3GPP 5G NR specifications. Terminal device 10 may 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 notebook PC, a communication module, a communication card, or an IoT device such as a surveillance camera and a robot. Terminal device 10 may be a vehicle (e.g., a car, a train, or similar), or a device mounted on the vehicle. Terminal device 10 may be a transport machine body other than a vehicle (e.g., a ship, an airplane, or similar), or a device mounted on the transport machine body. Terminal device 10 may be a sensor, or a device provided with a sensor.It should be noted that the terminal device 10 may be referred to by other names, such as terminal, mobile station, mobile terminal, mobile device, mobile unit, subscriber station, subscriber terminal, subscriber device, subscriber unit, wireless station, wireless terminal, wireless device, wireless unit, remote station, remote terminal, remote device and remote unit. The terminal device 10 is preferably a device adapted to one or more enhanced mobile broadband (eMBB), ultra-reliable and low-cost communications. Petition 870250087336, dated 09 / 26 / 2025, page 113 / 195 / 82 latency (URLLC, ultra-reliable and low-latency communications) and massive machine-type communications (mMTC, massive machine-type communications).

[0020] Base station 20 manages at least one cell. A cell constitutes a minimal unit of a communication area. For example, a cell belongs to a frequency (e.g., carrier frequency), and is configured with a component carrier. The term “cell” can represent radio communication resources, and can represent a communication target of terminal 10. Base station 20 performs radio communication with terminal 10 located in the cell of base station 20 in the U-plane and C-plane. In other words, base station 20 terminates a U-plane protocol and a C-plane protocol to terminal 10.

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

[0022] Base station device 20 may be a gNB that provides terminal device 10 with the U-plane and C-plane compliant with the 3GPP 5G New Radio (NR) specifications and connects to a 3GPP 5G core network (5GC), for example. Base station device 20 may be a device compliant with other older or newer 3GPP specifications.

[0023] The base station 20 device can be configured with a plurality of unitary devices. For example, the base station 20 device can include a central unit (CU), a distributed unit (DU), and a radio unit (RU). Petition 870250087336, dated 09 / 26 / 2025, page 114 / 195 / 82

[0024] With a configuration in which a plurality of base station 20 devices are connected to each other, a radio access network (RAN) is formed. The radio access network formed by the base station 20 device being a gNB can be referred to as an NGRAN. The base station 20 device being a gNB can be referred to as an NG-RAN node.

[0025] The plurality of base station 20 devices are connected to each other by a predetermined interface (for example, an Xn interface). More specifically, for example, the plurality of base station 20 devices are connected to each other by an Xn-U interface in the U-plane, and are connected to each other by an Xn-C interface in the C-plane. It should be noted that the plurality of base station 20 devices may be connected to each other by another interface with a different function and name.

[0026] Each base station device 20 is connected to the central network 30 by a predetermined interface (e.g., an NG interface). More specifically, for example, each base station device 20 is connected to the UPF of the central network 30 by an NG-U interface in the U-plane, and is connected to the AMF of the central network 30 by an NG-C interface in the C-plane. It should be noted that each base station device 20 may be connected to the central network 30 by another interface with a different function and name.

[0027] With reference to Figure 2, a radio protocol architecture will be described between terminal unit 10 and base station unit 20. With reference to Figure 3, radio protocol architectures will be described between terminal unit 10 and base station unit 20 and between terminal unit 10 and central network 30.

[0028] As illustrated in Figure 2, a protocol stack in the U-plane is provided with, in order from the lowest layer, a Physical layer (PHY), a Media Access Control (MAC) layer, and a Radio Link Control (RLC) layer. Petition 870250087336, dated 09 / 26 / 2025, page 115 / 195 / 82 Radio Link Control), a Packet Data Convergence Protocol (PDCP) layer, and a Service Data Adaptation Protocol (SDAP) layer. Each layer is terminated at the base station device 20 on the network side.

[0029] As illustrated in Figure 3, a protocol stack in the C-plane is provided with, in order from the lowest layer, a Physical layer (PHY), a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Non-Access Stratum (NAS). Each of the layers, except the Non-Access Stratum, is terminated at the base station appliance 20 on the network side. The Non-Access Stratum is terminated at the central network AMF 30 on the network side.

[0030] As illustrated in Figure 4, terminal device 10 includes, as hardware elements, a processor 101, a memory 102, an input / output interface 103, a radio interface 104, and an antenna 105. The above elements provided in terminal device 10 are connected to each other by means of an internal bus. It should be noted that terminal device 10 may include a hardware element different from the elements illustrated in Figure 4.

[0031] Processor 101 is an arithmetic element that implements various functions of terminal device 10. Processor 101 can be a central processing unit (CPU), a graphics processing unit (GPU), and a system-on-a-chip (SoC) including an element such as a memory controller.

[0032] Memory 102 includes at least one storage medium, such as random access memory (RAM) and a Petition 870250087336, dated 09 / 26 / 2025, page 116 / 195 / 82 embedded multimedia card (eMMC). Memory 102 is an element that temporarily or permanently stores a program and data used to perform various types of processing on the terminal device 10. The program includes one or more instructions for operations of the terminal device 10. The processor 101 loads the program stored in memory 102 into memory 102 itself and / or into system memory (not shown), and executes the program to implement the functions of the terminal device 10.

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

[0034] Radio interface 104 is a circuit that performs various types of signal processing to implement radio communication, and includes a baseband processor and an RF circuit. Radio interface 104 transmits and receives a radio signal to and from base station 20 via antenna 105.

[0035] As illustrated in Figure 5, the terminal device 10 includes, as functional blocks, a controller 110 and a communicator 120. The communicator 120 includes at least one transmitter 121 and at least one receiver 122.

[0036] Controller 110 may include at least one processor 101 and at least one memory 102. In other words, controller 110 may be implemented by processor 101 and memory 102. Controller 110 performs various types of control processing on the terminal device 10. For example, controller 110 controls radio communication with the base station device 20 via communicator 120. In other words, controller 110 performs, via communicator 120, transmission / reception of data / information / messages. Petition 870250087336, dated 09 / 26 / 2025, page 117 / 195 / 82

[0037] Communicator 120 includes radio interface 104 and antenna 105. In other words, communicator 120 is implemented by radio interface 104 and antenna 105. Communicator 120 transmits and receives a radio signal to and from base station 20 and thus performs radio communication with base station 20. Communicator 120 may include two or more radio interfaces 104 and two or more antennas 105.

[0038] When controller 110 operates, the various types of processing of terminal device 10 according to the present embodiment are performed.

[0039] As illustrated in Figure 6, the base station device 20 includes, as hardware elements, a processor 201, a memory 202, a network interface 203, a radio interface 204, and an antenna 205. The above elements provided in the base station device 20 are connected to each other by means of an internal bus. It should be noted that the base station device 20 may include a hardware element different from the elements illustrated in Figure 6.

[0040] Processor 201 is an arithmetic element that implements various functions of base station 20. Processor 201 can be a CPU, and may additionally include another processor such as a GPU.

[0041] Memory 202 includes at least one storage medium, such as read-only memory (ROM), RAM, a hard disk drive (HDD), and a solid-state drive (SSD). Memory 202 is an element that temporarily or permanently stores a program and data used to perform various types of processing on the base station 20 device. The program includes one or more instructions for base station 20 device operations. Processor 201 loads the program stored in memory 202 into memory 202 itself and / or into a memory Petition 870250087336, dated 09 / 26 / 2025, page 118 / 195 / 82 of the system (not illustrated), and executes the program to thus implement the functions of the base station device 20.

[0042] Network interface 203 is an interface used to transmit and receive a signal to and from another base station device 20 and the central network 30.

[0043] Radio interface 204 is a circuit that performs various types of signal processing to implement radio communication, and includes a baseband processor and an RF circuit. Radio interface 204 transmits and receives a radio signal to and from terminal device 10 via antenna 205.

[0044] As illustrated in Figure 7, the base station device 20 includes, as functional blocks, a controller 210, a communicator 220 and a network communicator 230. The communicator 220 includes at least one transmitter 221 and at least one receiver 222.

[0045] Controller 210 may include at least one processor 201 and at least one memory 202. In other words, controller 210 may be implemented by processor 201 and memory 202. Controller 210 performs various types of control processing on base station 20. For example, controller 210 controls radio communication with terminal 10 via communicator 220. In other words, controller 210 performs data / information / message transmission / reception via communicator 220. For example, controller 210 controls communication with another node (e.g., another base station 20, a core network node 30) via network communicator 230.

[0046] Communicator 220 includes radio interface 204 and antenna 205. In other words, communicator 220 is implemented by radio interface 204 and antenna 205. Communicator 220 transmits and receives a radio signal to and from terminal device 10 and thus performs Petition 870250087336, dated 09 / 26 / 2025, page 119 / 195 / 82 radio communication with terminal device 10. The communicator 220 may include two or more radio interfaces 204 and two or more antennas 205.

[0047] Network communicator 230 includes network interface 203. In other words, network communicator 230 is implemented by network interface 203. Network interface 203 transmits and receives a signal to and from the network (ultimately, another node described above).

[0048] When controller 210 operates, the various types of processing of base station device 20 according to the present embodiment are executed. 1.2. Radio Resources

[0049] Terminal unit 10 and base station unit 20 communicate with each other using radio capabilities in the frequency domain and time domain. The radio capabilities will be described below.

[0050] One method of transmitting downlink communication 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. One method of transmitting uplink communication from terminal device 10 to base station device 20 is, for example, the CP-OFDM described above, or DFTS-OFDM in which the CP-OFDM is subsequently applied to a transform pre-encoder to perform discrete Fourier transform (DFT) spreading.

[0051] The cyclic prefix is ​​a redundant signal that functions as a guard period (GP) to prevent intersymbol interference and intercarrier interference, being inserted at the beginning of an OFDM symbol. Types of cyclic prefix include a normal cyclic prefix and an extended cyclic prefix. Petition 870250087336, dated 09 / 26 / 2025, page 120 / 195 / 82

[0052] As radio resources in the frequency domain of OFDM, a plurality of orthogonal subcarriers is used. The plurality of subcarriers is allocated with a predetermined subcarrier spacing (SCS, sub-carrier spacing) Δf in the frequency domain. In the S communication system, a plurality of subcarrier spacings Δf can be applied. The subcarrier spacing Δf is expressed by the following expression (1), for example. Af = 2μ· 15 [kHz] (1)

[0053] Here, μ is an integer equal to or greater than 0, and can be any of the values ​​0, 1, 2, 3, 4, 5, and 6. Thus, the subcarrier spacing Af [kHz] can be any of the values ​​15, 30, 60, 120, 240, 480, and 960. Note that μ can be a value equal to or greater than 7.

[0054] In the OFDM time domain, as illustrated in Figure 8, a hierarchical radio frame configuration is used. A radio frame includes 10 subframes. The subframes are numbered with subframe numbers, counted from 0 to 9 in ascending order of one. A radio frame is divided into two half-frames. A radio frame time length is 10 ms, a half-frame time length is 5 ms, and a subframe time length is 1 ms. The above time lengths do not depend on the subcarrier spacing Af.

[0055] A subframe includes one or more slots. The number Ns of slots included in a subframe depends on the value of μ described above, ultimately on the subcarrier spacing Af. The number Ns of slots is expressed by the following expression (2), for example. Ns = 2μ(2)

[0056] A slot includes a plurality of symbols. The number of symbols included in a slot depends on the type of cyclic prefix. For example, in a configuration where the normal cyclic prefix is ​​used, a Petition 870250087336, dated 09 / 26 / 2025, page 121 / 195 / 82 slot includes 14 symbols. For example, in a configuration where the extended cyclic prefix is ​​used, a slot includes 12 symbols.

[0057] As described above, the number of slots and the number of symbols included in each of the radio frame, half-frame and sub-frame with a fixed time length are variable. Thus, the slot time length and the symbol time length are also variable.

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

[0059] Radio frames are assigned to system frame numbers (SFNs) numbered from 0 to 1023 in increments of 1. SFN “0” corresponds to an initial SFN value, and SFN “1023” corresponds to the highest SFN value. Thus, SFN 0 is assigned to a radio frame that follows a radio frame assigned to SFN 1023. The time length of a radio frame is 10 ms, and thus the time length of a system frame number cycle is 10240 ms (= 10.24 seconds).

[0060] Here, base station device 20 can configure one or a plurality of service cells for terminal device 10. The service cell can correspond to a downlink component carrier and / or an uplink component carrier. A technology in which one or a plurality of service cells are configured and base station device 20 and terminal device 10 perform radio communication can also be referred to as carrier aggregation.

[0061] Base station device 20 can configure one or one Petition 870250087336, dated 09 / 26 / 2025, p. 122 / 195 / 82 plurality of bandwidth parts (BWPs) for terminal device 10 for each of one or a plurality of service cells. For example, on the downlink of a service cell, a downlink bandwidth part (DLBWP). On the uplink of a service cell, an uplink bandwidth part (UL-BWP). Here, the DL-BWP may include an initial DL-BWP and / or a dedicated DL-BWP. The UL-BWP may include an initial UL-BWP and / or a dedicated UL-BWP. In what follows, the BWP may include the DL-BWP and / or the UL-BWP. 1.3. Control Channels and Information

[0062] Terminal unit 10 and base station unit 20 transmit and receive user data and control information between themselves. The transmission and reception of downlink and uplink control information will be illustrated below.

[0063] Terminal unit 10 and base station unit 20 transmit and receive user data and control information using a plurality of hierarchical channels. A physical channel is a channel used for physical communication between terminal unit 10 and base station unit 20. Examples of physical channels include a physical downlink control channel (PDCCH), a physical broadcast channel (PBCH), and a physical uplink control channel (PUCCH).

[0064] A transport channel is a channel located above the physical channel and is mapped to the physical channel in the PHY layer. A plurality of transport channels can be mapped to a physical channel. Examples of transport channels include a downlink shared channel (DL-SCH) and an uplink shared channel (UL-SCH). For example, data in Petition 870250087336, dated 09 / 26 / 2025, p. 123 / 195 / 82. Downlink data is also referred to as DL-SCH data. For example, uplink data is also referred to as UL-SCH data. Here, DL-SCH data includes downlink user data. UL-SCH data includes uplink user data.

[0065] A logical channel is a channel located above the transport channel and is mapped to the transport channel in the MAC layer. A plurality of logical channels can be mapped to a transport channel, and a logical channel can be mapped to a plurality of transport channels. Logical channels are classified by the characteristics of the information to be transmitted. Examples of logical channels include a broadcast control channel (BCCH), a common control channel (CCCH), and a dedicated control channel (DCCH).

[0066] Base station device 20 transmits downlink control information (DCI) to terminal device 10, using the PDCCH as a physical channel. The DCI includes information related to downlink and uplink resource allocations for terminal device 10 and other control information for terminal device 10. The DCI is mapped to the PDCCH and corresponds to Layer 1 signaling.

[0067] Here, with respect to DCI transmission in PDCCH, one or a plurality of formats may be defined. A format defined with respect to DCI transmission in PDCCH may be referred to as a DCI format. For example, the DCI format may include a DCI format (e.g., a format referred to as DCI format 1_0, DCI format 1_1, and / or DCI format 1_2) used for scheduling a physical downlink shared channel (PDSCH). For example, the DCI format may include a DCI format Petition 870250087336, dated 09 / 26 / 2025, pp. 124 / 195 / 82 (for example, a format referred to as DCI format 0_0, DCI format 0_1, and / or DCI format 0_2) used for scheduling a physical uplink shared channel (PUSCH). The DCI format may include a DCI format not used for PDSCH and / or PUSCH scheduling. The DCI format used for PDSCH and / or PUSCH scheduling may be referred to as a scheduling DCI format. The DCI format not used for PDSCH and / or PUSCH scheduling may be referred to as a non-scheduling DCI format. In this embodiment, for simplicity of description, the “DCI format” may simply be referred to as “PDCCH”. "DCI generated according to the DCI format" can simply be referred to as the "DCI format".

[0068] For example, base station device 20 can configure frequency domain and / or time domain resources for terminal device 10 to monitor a candidate set of PDCCH. For example, the frequency domain resources on which terminal device 10 monitors the candidate set of PDCCH can be referred to as the control resource set (CORESET). The time domain resources on which terminal device 10 monitors the candidate set of PDCCH can be referred to as the search space set (SSS). Terminal device 10 can monitor the candidate set of PDCCH on one or a plurality of CORESETs in the DL-BWP of the service cell configured with PDCCH monitoring according to a corresponding search space set. Here, monitoring can connote attempting to decode each of the PDCCH candidates according to the monitored DCI format.The configuration described above can be referred to as blind decoding.

[0069] Here, a cyclic redundancy check (CRC) is scrambled using a temporary network identifier. Petition 870250087336, dated 09 / 26 / 2025, page 125 / 195 / 82. A radio network temporary identifier (RNTI) can be added to the DCI (or DCI format) to be transmitted in the PDCCH. The CRC can also be referred to as a CRC parity bit. A plurality of RNTI types is defined. For example, base station 20 can transmit an RRC message including at least one piece of information indicating a Cell RNTI (C-RNTI, iCell-RNTI), information indicating a Cell RNTI Modulation and Coding Scheme (MCS-C-RNTI, Modulation and Coding Scheme Cell-RNTI), and information indicating a Configured Scheduling RNTI (CS-RNTI, Configured SchedulingRNTI) to configure each RNTI. In other words, a scrambled CRC using at least one of the C-RNTI, MCS-C-RNTI, and CSRNTI can be added to the DCI (or DCI format) to be transmitted in PDCCH.

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

[0071] Terminal unit 10 transmits uplink control information (UCI) to base station unit 20 using a PUCCH as the physical channel. The UCI includes control information such as a scheduling request (SR), an Ack / Nack hybrid automatic repeat request (HARQ), and channel state information (CSI). The UCI is mapped to the PUCCH or PUSCH and corresponds to Layer 1 signaling.

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

[0073] Terminal unit 10 transmits to station unit Petition 870250087336, dated 09 / 26 / 2025, p. 126 / 195 / 82 base 20, a control element (CE, control element) of a MAC layer using a UL-SCH as a transport channel. The uplink MAC CE includes control information such as buffer status reports (BSR). The uplink MAC CE is mapped to a PUSCH via the UL-SCH and corresponds to Layer 2 signaling.

[0074] Base station device 20 transmits (or broadcasts) system information (SI) to terminal device 10, using the BCCH as the logical channel. The SI includes minimum system information (MSI) and other system information (OSI). The MSI includes a master information block (MIB) and a system information block 1 (SIB1). SIB1 may be referred to as remaining minimum system information (RMSI). The OSI includes system information blocks (from SIB2 onwards), except for SIB1. From the BCCH, the MIB is mapped to the PBCH via the broadcast channel (BCH), and the SIB is mapped to the PDSCH via the DL-SCH.

[0075] Base station 20 transmits control information at the RRC layer to terminal 10 using a signaling radio bearer (SRB) established between terminal 10 and base station 20 at the RRC layer. A message exchanged between base station 20 and terminal 10 at the RRC layer may henceforth be referred to as an RRC message. A plurality of SRB types (e.g., SRB0, SRB1, SRB2, SRB3, and SRB4) are present. The SRB is used to transmit and receive a NAS message including control information in the No-Access Stratum, in addition to the RRC message. To transmit the RRC message from base station 20 to terminal 10, CCCH or DCCH is used. CCCH and DCCH are each mapped to PDSCH via DL-SCH. Petition 870250087336, dated 09 / 26 / 2025, page 127 / 195 / 82 RRC message corresponds to layer 3 signaling.

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

[0077] Terminal device 10 transmits the RRC message to base station device 20, using the SRB described above. To transmit the RRC message from terminal device 10 to base station device 20, CCCH or DCCH is used. CCCH and DCCH are each mapped to PUSCH via UL-SCH. The RRC message corresponds to layer 3 signaling.

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

[0079] As an example of an uplink RRC message, a User Equipment Assistance Information (UEAssistanceInformation) message will be described. The User Equipment Assistance Information message is an RRC message transmitted from Petition 870250087336, dated 09 / 26 / 2025, page 128 / 195 / 82 terminal device 10 to base station device 20 using SRB1 or SRB3. DCCH is used to transmit the user equipment assistance information message. The user equipment assistance information message is used to notify base station device 20 about various information (UE assistance information) related to terminal device 10. 1.4. Scheduling of Uplink 1.4.1. Scheduling Request (SR)

[0080] An SR is used for terminal unit 10 to request allocation of PUSCH radio resources from base station unit 20. An SR can be used to request a UL-SCH resource for initial transmission. Base station unit 20 allocates a PUCCH resource to terminal unit 10 for SR transmission. Base station unit 20 transmits an RRC message to terminal unit 10 including a parameter for the SR. The parameter for the SR is included in an information element (IE) “SchedulingRequestResourceConfig”, an example of an IE for RRC being.

[0081] Terminal unit 10 transmits UCI including SR to base station unit 20 using the configured PUCCH feature. Terminal unit 10 can transmit UCI on demand. Terminal unit 10 can transmit UCI with a configured periodicity. For example, terminal unit 10 can transmit SR set to “0” (negative SR) and / or SR set to “1” (positive SR). According to the SR, base station unit 20 allocates a PUSCH radio resource to terminal unit 10. 1.4.2. Dynamic Concession (DG)

[0082] A DG is a method of scheduling the allocation of a PUSCH radio resource according to an uplink allocation procedure. Base station 20 transmits to the device Petition 870250087336, dated 09 / 26 / 2025, page 129 / 195 / 82 terminal 10, an uplink grant in a PDCCH. Terminal 10 performs the transmission of a PUSCH according to the uplink grant. For example, base station 20 may allocate a PUSCH radio resource using a C-RNTI and / or a DCI format with a CRC scrambled with an MCS-C-RNTI (i.e., DCI format used for PUSCH scheduling), and terminal 10 may perform the uplink transmission using the allocated PUSCH radio resource. Here, an indicator of new data to be included in the C-RNTI and / or DCI format with the CRC scrambled with the MCS-C-RNTI may be set to 0 or 1.Base station device 20 can allocate a PUSCH radio resource using a DCI format with a CRC scrambled with a CSRNTI (i.e., DCI format used for PUSCH scheduling), and terminal device 10 can perform uplink transmission using the allocated PUSCH radio resource. A new data indicator to be included in the DCI format with the CRC scrambled with the CSRNTI can be set to 1. 1.4.3. Configured Grant (CG)

[0083] A CG is a method of scheduling the allocation of a PUSCH radio resource without the dynamic uplink granting procedure. CG includes two types, type 1 and type 2. Base station 20 transmits an RRC message to terminal 10, including a parameter for the CG. The parameter for the CG is included in an information element (IE) “ConfiguredGrantConfig”, an example of an IE for RRC. The “ConfiguredGrantConfig” IE includes a “periodicity” parameter related to a transmission periodicity using a PUSCH. Note that the “periodicity” parameter is configured in units of number of slots or number of symbols. Alternatively, the “periodicity” parameter can be configured in units of Frames Per Second (FPS). For type 1, the Petition 870250087336, dated 09 / 26 / 2025, page 130 / 195 / 82 terminal unit 10 initiates the transmission of a signal with a configured periodicity, without any DCI triggering. On the other hand, for type 2, base station unit 20 transmits, to terminal unit 10, DCI scrambled with a CS-RNTI. The CS-RNTI is used to activate the periodic transmission. According to such activation by the DCI scrambled with the CS-RNTI, terminal unit 10 initiates transmission using a PUSCH with a configured periodicity. 1.4.4. Buffer Status Reporting (BSR)

[0084] Terminal device 10 transmits, using an allocated PUSCH radio resource, a BSR via MAC signaling. The BSR is configured with a CE MAC included in a Media Access Control Protocol Data Unit (MAC PDU). The BSR indicates information related to an uplink data buffer state of a MAC entity. Based on the BSR, base station device 20 performs uplink radio resource allocation relative to terminal device 10.

[0085] In BSR, a logical channel (LCH) is allocated to a group of logical channels (LCG). Each LCG includes one or more logical channels. Terminal device 10 calculates, for each LCG, an uplink data buffer size. Terminal device 10 transmits, to base station device 20, the buffer size corresponding to each LCG as BSR.

[0086] Base station device 20 transmits an RRC message to terminal device 10, including a parameter for the BSR. The parameter for the BSR is included in an information element (IE) “BSR-Config”, which is an example of an IE for RRC. For example, the IE “BSRConfig” includes three timers, “periodicBSR-Timer”, “retxBSR-Timer”, and “logicalChannelSR-DelayTimer”.

[0087] A parameter associated with an LCG is included in a Petition 870250087336, dated 09 / 26 / 2025, page 131 / 195 / 82 information element (IE) “LogicalChannelConfig”, being an example of an IE for RRC. In other words, base station device 20 can transmit an RRC message including the IE “LogicalChannelConfig”. Based on the IE “LogicalChannelConfig” included in the RRC message, terminal device 10 can identify a configuration related to a logical channel and / or an LCG. For example, the IE “LogicalChannelConfig” includes an IE “logicalChannelGroup”. With the IE “logicalChannelGroup”, a logical channel is allocated to an LCG. For example, for each one or a plurality of logical channels, an LCG index (ID, index) can be configured, and an LCG to which such one or a plurality of logical channels belongs can be configured. Note that the IE “LogicalChannelConfig” can include an IE “logicalChannelGroupIAB-Ext”.The IE “logicalChannelGroupIAB-Ext” is applied only to an Integrated Access Backhaul-Mobile Termination (IAB-MT). If IE “logicalChannelGroupIAB-Ext” is configured, IE “LogicalChannelConfig” is ignored.

[0088] Terminal device 10 can trigger the BSR according to a given condition. For example, for a group of activated cells, terminal device 10 can trigger the BSR when any of the following conditions (a1) to (a4) are met. It should be noted that the following conditions can be referred to as “events”.

[0089] (al) For a logical channel belonging to a given LCG, uplink data becomes available to a MAC entity, and one of the following two conditions is met: - Uplink data belongs to a logical channel with a higher priority than the priorities of any available logical channels including uplink data belonging to any LCG; or - none of the logical channels belonging to an LCG includes Petition 870250087336, dated 09 / 26 / 2025, p. 132 / 195 / 82 any available uplink data.

[0090] (a2) Uplink resources are allocated and the number of padding bits is equal to or greater than the size of a BSR CE MAC plus its subheader.

[0091] (a3) ​​The “retxBSR-Timer” expires and at least one of the logical channels belonging to an LCG includes uplink data.

[0092] (a4) The “periodicBSR-Timer” expires.

[0093] The BSR includes at least Regular BSR, Filling BSR, and Periodic BSR. The Regular BSR, Filling BSR, and Periodic BSR can each be triggered based on a different condition. For example, terminal device 10 triggers the Regular BSR if condition (a1) or (a3) ​​is met. Terminal device 10 triggers the Filling BSR if condition (a2) is met. Terminal device 10 triggers the Periodic BSR if condition (a4) is met.

[0094] The BSR includes a plurality of formats. The plurality of formats includes at least Short BSR and Long BSR. A MAC PDU including the BSR includes a MAC subheader. The MAC subheader includes a Logical Channel Identifier (LCID) or an Extended Logical Channel Identifier (eLCID). The LCID or eLCID value may be referred to as a codepoint. The Short BSR and Long BSR are each identified by a codepoint value.

[0095] The Short BSR is a format for reporting the buffer state (i.e., buffer size) of an LCG. As illustrated in Figure 9, the Short BSR includes a field 900 with a fixed size of 8 bits. The field 900 includes a first part 910 and a second part 920.

[0096] The first part 910 consists of 3 bits. The first part 910 is information for identifying an LCG whose buffer status must be reported. The first part 910 can be referred to as the “ID field of Petition 870250087336, dated 09 / 26 / 2025, p. 133 / 195 / 82 LCG

[0097] The second part 920 consists of 5 bits. The second part 920 is information for identifying the total amount of data available for all logical channels included in the LCG indicated by the first part 910. The second part 920 can be simply referred to as the “buffer size”. The second part 920 indicates an index representing the number of bytes. For example, the second part 920 indicates any of the values ​​from 0 to 31.

[0098] It should be noted that the Short BSR may include Truncated format and Extended format, with the Truncated format being a format for a high-priority logical channel and the Extended format being a format that allows transmitting a greater amount of information.

[0099] Long BSR is a format for reporting buffer states (i.e., buffer sizes) of a plurality of LCGs. As illustrated in Figure 10, the Long BSR has variable size. The Long BSR includes an LCG field of 1010 and a buffer size field of 1020.

[00100] The LCG 1010 field consists of 8 bits. In the LCG 1010 field, the 8 bits correspond, respectively, to the eight LCGi. Here, i is an integer from 0 to 7. The same definition of i applies to the description from here on. The LCG 1010 field can indicate whether a buffer size field for LCGi is present. For example, if the value of LCGi in the LCG 1010 field is 1, this indicates the presence of the buffer size field corresponding to LCGi. If the value of LCGi is 0, this indicates the absence of the buffer size field corresponding to LCGi.

[00101] The number of fields included in the buffer size field 1020 varies depending on the value of the LCG field 1010. In the example in Figure 10, in the LCG field 1010, it is assumed that a bit corresponding to LCG 1 is 1 and a bit corresponding to LCG 2 is 1. Thus, the buffer size field 1020 includes a field 1021 Petition 870250087336, dated 09 / 26 / 2025, p. 134 / 195 / 82 corresponding to LCG 1 and a field 1022 corresponding to LCG 2. It should be noted that, as a bit corresponding to LCG 0 is assumed to be 0 in Figure 10, no field corresponding to LCG 0 is included in the buffer size field 1020.

[00102] Each field included in the 1020 buffer size field consists of 8 bits. Each field indicates an index representing the number of bytes. For example, each field indicates any of the values ​​from 0 to 254.

[00103] It should be noted that, similarly to the Short BSR, the Long BSR may include both Truncated and Extended formats.

[00104] The BSR may include Preemptive BSR format and Extended Preemptive BSR format. These formats are used for an IAB-MT.

[00105] Terminal device 10 can select Short BSR or Long BSR, according to a given method. For example, in the case of Regular BSR and Periodic BSR, terminal device 10 can select Short BSR or Long BSR as below. In the case where two or more LCGs have data (available data) available for transmission when a MAC PDU including a BSR is built, terminal device 10 transmits Long BSR to all LCGs that have the available data. Otherwise, terminal device 10 transmits Short BSR.

[00106] In the case of Regular BSR and Periodic BSR, with respect to a MAC entity configured with an IE “logicalChannelGroup-IABExt” by a higher layer, terminal device 10 can select Short BSR or Long BSR as below. In the case where two or more LCGs have data available for transmission and the maximum LCG ID value among the configured LCGs is 7 or less, terminal device 10 transmits Long BSR to all LCGs that have data available. In the case where two or more LCGs have data available for transmission and the maximum LCG ID value among the configured LCGs is greater than 7, terminal device 10 transmits Extended Long BSR to all LCGs that have data available. Petition 870250087336, dated 09 / 26 / 2025, p. 135 / 195 / 82 available. In the event that one or more LCGs have data available for transmission, terminal device 10 transmits Extended Short BSR.

[00107] In the case of Fill-in BSR, the terminal device 10 can transmit, according to a condition to be met, any of the following BSR formats: - Short BSR BSR Long - BSR Short Truncated BSR Long Truncated - BSR Short Truncated Extended BSR Long Truncated Extended

[00108] It should be noted that, in the case where at least one BSR has been triggered according to any of the conditions (a1) to (a4) and not canceled, terminal device 10 may perform the processing as described below. For example, in the case where UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a BSR MAC CE plus its subheader as a result of logical channel prioritization (LCP), terminal device 10 may generate a BSR MAC CE and transmit the BSR MAC CE.

[00109] In the case where a Regular BSR has been triggered and the “logicalChannelSR-DelayTimer” is not running, when the following condition (b1) or (b2) is met, terminal device 10 may trigger an SR.

[00110] (b1) No UL-SCH resource available for a new transmission.

[00111] (b2) The UL-SCH resource available for a new transmission does not satisfy an LCP mapping constraint configured for a logical channel that has triggered the BSR.

[00112] The LCP mapping constraint can be a constraint Petition 870250087336, dated 09 / 26 / 2025, p. 136 / 195 / 82 described in clause 5.4.3.1 of NPL 2. The restriction may be a restriction configured by RRC.The restriction may include, for example, at least one of: a restriction related to a subcarrier spacing allowed for transmission (e.g., allowedSCS-List), a restriction related to the maximum PUSCH duration allowed for transmission (e.g., maxPUSCH-Duration), a restriction related to whether a Type 1 CG can be used for transmission (e.g., configuredGrantTypelAllowed), a restriction related to a cell allowed for transmission (e.g., allowedServingCells), a restriction related to a CG allowed for transmission (e.g., allowedCG-List), a restriction related to a PHY priority index allowed for a dynamic grant (DG, dynamic grant) for transmission (e.g., allowedPHY-PriorityIndex), or a restriction related to an uplink HARQ mode allowed for transmission (e.g., allowedHARQ-mode).

[00113] If the following condition (c1) is met, terminal device 10 can cancel all fired BSRs. Furthermore, if the following condition (c2) is met, terminal device 10 can cancel all fired BSRs before mounting the MAC PDU.

[00114] (c1) An uplink lease may accommodate all pending data available for transmission, but is not sufficient to additionally accommodate a BSR CE MAC plus its subheader.

[00115] (c2) A MAC PDU is transmitted and the MAC PDU includes a MAC CE of BSR Long, Long Extended, Short or Short Extended, the MAC CE of BSR including a buffer state up to (and including) the last event that triggered a BSR before mounting the MAC PDU. 1.5. Extended Reality (XR, eXtended Reality)

[00116] Characteristics of the traffic generated in XR will be described. In XR, a plurality of data types (video data, voice data, user data, control data, and the like) are transmitted and received in Petition 870250087336, dated 09 / 26 / 2025, page 137 / 195 / 82 parallel. A plurality of data streams corresponding to the data segments have different traffic characteristics and quality of service (QoS) requirements.

[00117] During data transmission and reception, temporal shifts may occur, expressed as jitter, variability, and fluctuation due to factors such as video and audio encoding and network latency.

[00118] Reference Literature 1 describes that the following definitions can be introduced for transmission and reception in XR.

[00119] [Reference Literature 1] 3GPP TR 23.700-60 V1.1.0 (2022-09)

[00120] PDU set: a set of PDUs including one or more PDUs that carry a payload of a unit of information generated at an application level. The application level corresponds, for example, to a frame or a video segment in an XR service.

[00121] Data burst: a set of multiple PDUs generated and sent by an application in a short period of time.

[00122] In addition, for XR, requirements for a packet delay budget (PDB, packet delay budget) as QoS requirements were studied. The PDB is an upper limit on the allowed packet delay time between the terminal device 10 and the UPF. It should be noted that Reference Literature 1 also describes that the following new QoS parameters can be introduced.

[00123] PDU-set delay budget (PSDB): an upper limit on the allowed PDU-set delay time between terminal device 10 and the UPF.

[00124] PDU-set error rate (PSER): an upper bound of a calculated error rate among a set of PDUs. Petition 870250087336, dated 09 / 26 / 2025, p. 138 / 195 / 82 processed by a transmitter and all PDUs in a set of PDUs that were not successfully delivered to a higher layer of a corresponding receiver. 1.6. Delay Information Report 1.6.1. Basic Configuration

[00125] As described above, in the BSR described in NPLs 2 and 3, the terminal device can only transmit information (i.e., information related to a buffer size) for certain data (i.e., uplink data corresponding to an LCG). This small amount of information reported to the base station device may prevent the base station device from properly allocating a radio resource to the terminal device.

[00126] In view of this, the present embodiment provides a procedure for terminal device 10 to transmit delay-related information. Hereinafter, “delay-related information” is referred to as “delay information”. Terminal device 10 transmits to base station device 20 a report including delay information relating to certain data. Hereinafter, “report including delay information” is referred to as “delay information report”. The delay information report may be referred to as “Delay Status Report (DSR)”.

[00127] The specified data means a data unit to be reported in the delay information report. Hereafter, the specified data may be referred to as “data to be reported” or “data unit to be reported”. This configuration allows terminal device 10 to transmit delay information relating to data to be reported to base station device 20.

[00128] The data unit to be reported may be data corresponding to an LCG. Such an LCG may include one or a plurality of Petition 870250087336, dated 09 / 26 / 2025, p. 139 / 195 / 82 LCHs (i.e., data corresponding to one or a plurality of LCHs). In this configuration, the data unit to be reported may be a portion or all of the data available for an LCG. Note that the data unit to be reported may be data corresponding to an LCH. The data unit to be reported may be a portion or all of the data available for an LCH.

[00129] The data unit to be reported can be data corresponding to a PDU. In this configuration, the data unit to be reported can be part or all of the data available for a PDU. The data unit to be reported can be data corresponding to a set of PDUs. In this configuration, the data unit to be reported can be part or all of the data available for a set of PDUs. Additionally, the data unit to be reported can be data corresponding to a plurality of sets of PDUs. For example, the data unit to be reported can be data (or part of the data) available for one, a plurality of, or all of the PDUs (or sets of PDUs) belonging to a set of PDUs.

[00130] The data unit to be reported can be data corresponding to a data burst. In this configuration, the data unit to be reported can be a portion or all of the data available for a data burst. It should be noted that the data unit to be reported can be data corresponding to a plurality of data bursts. For example, the data unit to be reported can be data (or a portion of the data) available for one, a plurality of, or all of the data segments (or data bursts) belonging to a data burst.

[00131] Delay information can be information explicitly indicating a delay. For example, delay information can be a delay time. Delay information can be an index indicating a delay time. Petition 870250087336, dated 09 / 26 / 2025, p. 140 / 195 / 82

[00132] Delay information can be information related to another time. For example, delay information can be information related to a data transmission time limit. The transmission time limit may be referred to as a “transmission deadline” or “upper delay limit”.

[00133] Delay information may be the remaining time until a given first time limit is reached. The first time limit may be a time limit until which the transmission of some or all of the data to be reported must be completed. For example, the first time limit may be the nearest time limit among a plurality of time limits until which the transmission of some of the data to be reported must be completed. The first time limit may be a time limit determined based on a PDB or PSDB. The PDB or PSDB may be determined based on a corresponding QoS flow. The PDB or PSDB may be provided to the terminal device 10 by the central network 30.The first time limit related to a set of PDUs can be a value obtained by adding a PDB or PSDB from a QoS stream corresponding to a moment when data corresponding to a PDU in the set of PDUs is first buffered for terminal device 10 or to a moment when the data first arrives at a MAC entity. The first time limit related to a data burst can be a value obtained by adding a PDB or PSDB from a QoS stream corresponding to a moment when data corresponding to a PDU included in the data burst is first buffered for terminal device 10 or to a moment when the data first arrives at a MAC entity.

[00134] The remaining time can be a value obtained by subtracting a period of time during the corresponding QoS stream's PDB or PSDB. Petition 870250087336, dated 09 / 26 / 2025, page 141 / 195 / 82 which certain data (i.e., data to be reported) are stored in a buffer on terminal device 10.

[00135] The remaining time can be a period of time from a given first instant to the first time limit. The first instant can be the current time. The first instant can be a moment when an uplink grant for transmitting the delayed information report is allocated. The first instant can be a moment when the specified data (i.e., data to be reported) is buffered for terminal device 10. The first instant can be a moment when the data to be reported arrives at a MAC entity on terminal device 10. In this configuration, the first time limit can be obtained by adding a PDB or PSDB to the first instant.

[00136] Delay information can be information that implicitly indicates a delay. For example, delay information can be information related to data provided with a temporal constraint or requirement among the data to be reported. Hereafter, all data to be reported is referred to as “first data” and the data provided with the temporal constraint or requirement among the data to be reported 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 of the second data.

[00137] Second data may be data to be transmitted with priority. Second data may be referred to as urgent data. Second data may be data that satisfies a delay-related condition. For example, second data may be data configured with the first time limit. Second data may be data whose remaining time is equal to or less than a given first threshold Th1. Base station device 20 may transmit, to terminal device 10, a Petition 870250087336, dated 09 / 26 / 2025, page 142 / 195 / 82 RRC message including information indicating the first Th1 threshold. The first Th1 threshold can be configured for an LCH. For example, the first Th1 threshold can be configured as a new element of the IE “LogicalChannelConfig”. The first Th1 threshold can be configured for an LCG. For example, the first Th1 threshold can be configured as a new element of the IE “logicalChannelGroup”. The first Th1 threshold can be configured for a PDU or set of PDUs. The first Th1 threshold can be configured for an IE related to the PDU or set of PDUs included in the RRC message. The first Th1 threshold can be configured for a data burst. The first Th1 threshold can be configured for an IE related to the data burst included in the RRC message.It should be noted that base station 20 can transmit system information (SI, for example, SIB1 and / or SIB other than SIB1) to terminal 10, including information indicating the first threshold Th1. Base station 20 can transmit DCI information to terminal 10, including information indicating the first threshold Th1.

[00138] In another example, the second data may be data provided with a constraint or requirement related to a time delay shift, such as ripple. In yet another example, the second data may be data provided with a constraint or requirement for a transmission rate.

[00139] Based on the size of the given seconds, base station 20 can determine a degree of delay. If the given seconds are larger than a certain size, base station 20 can determine that there is a delay in transmission by terminal 10. If the given seconds are equal to or smaller than the determined size, base station 20 can determine that there is no delay in transmission by terminal 10. Petition 870250087336, dated 09 / 26 / 2025, page 143 / 195 / 82 1.6.2. Delay Information Report Configuration

[00140] Terminal device 10 can transmit, as a delay information report, a MAC CE including delay information. For example, terminal device 10 can transmit a BSR including the delay information report. In this configuration, terminal device 10 can transmit the BSR including the delay information report according to the following procedure.

[00141] As illustrated in Figure 11, communicator 220 on base station 20 transmits an RRC message (S1101) to terminal 10. The RRC message includes a parameter related to a BSR. The RRC message may be an RRC reconfiguration message (RRCReconfiguration). Based on the parameter included in the RRC message, controller 110 on terminal 10 generates a BSR. The BSR includes buffer size information related to a buffer size and delay information. Communicator 120 on terminal 10 transmits the BSR (S1102).

[00142] Terminal device 10 can transmit the Long BSR 1200 illustrated in Figure 12. The Long BSR 1200 includes a first field 1210 and a second field 1220.

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

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

[00145] Field 1221 is a field related to LCG 1. Field 1221 includes a first part 1221a and a second part 1221b. In Petition 870250087336, dated 09 / 26 / 2025, page 144 / 195 / 82 In this example, the first part 1221a has 6 bits and the second part 1221b has 2 bits. It should be noted that, not limited to this configuration, the first part 1221a and the second part 1221b may each include a different number of bits than in this example.

[00146] The first part 1221a indicates a buffer size related to data corresponding to LCG 1. For example, the first part 1221a could be an index indicating the number of bytes. Controller 110 could reference a first buffer size table for 6 bits in order to set an index for the first part 1221a. The first buffer size table is a table that defines a correspondence relationship between buffer sizes and indices.

[00147] The second part 1221b indicates the delay information related to data corresponding to LCG 1. The second part 1221b can be an index indicating the delay information. Controller 110 can reference a 2-bit delay information table in order to set an index for the second part 1221b. The delay information table is a table that defines a correspondence relationship between delay information and indexes.

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

[00149] Field 1223 is a field related to LCG 3. Field 1223 indicates a buffer size related to data corresponding to LCG 3. With respect to data corresponding to LCG 3, it is assumed that the remaining time is greater than the first threshold Th1. In other words, data corresponding to LCG 3 has no delay. In this case, field 1223 may include information related to buffer size and not include delay information. Controller 110 may reference a Petition 870250087336, dated 09 / 26 / 2025, page 145 / 195 / 82 second buffer size table for 8 bits, in order to configure an index for field 1223. The second buffer size table is a table that defines a correspondence relationship between buffer sizes and indices. As described above, in order to configure an index corresponding to the buffer size-related information, controller 110 can switch the table to be used between the first buffer size table and the second buffer size table.

[00150] It should be noted that, in the example described above, although the second field 1220 includes the three fields 1221 to 1223, the configuration is not limited to this. The number of fields included in the second field 1220 can be variable. In another example, the order of the fields included in the second field 1220 can be determined based on their priorities.

[00151] As illustrated in Figure 13, each of the fields 1221 to 1223 included in the second field 1220 may include a first part corresponding to buffer size information and a second part corresponding to delay information. Hereafter, only the details different from the configuration in Figure 12 are described, and the description of the details identical to the configuration in Figure 12 is omitted.

[00152] Field 1223 is a field related to LCG 3. Field 1223 includes a first part 1223a and a second part 1223b. In the present example, the first part 1223a has 6 bits and the second part 1223b has 2 bits. For example, the first part 1223a can be an index indicating the number of bytes. Controller 110 can reference the first buffer size table in order to set an index for the first part 1223a. As described above, with respect to the data corresponding to LCG 3, it is assumed that the remaining time is greater than the first threshold Th1. In this case, the second part 1223b can be blank. In another example, the second part 1223b can be a value (or index) indicating that no delay information is reported. Petition 870250087336, dated 09 / 26 / 2025, page 146 / 195 / 82

[00153] Furthermore, the configuration of the second 1220 field is not limited to the examples described above. As illustrated in Figure 14, the second 1220 field may include an 8-bit 1410 field corresponding to buffer size information and an 8-bit 1420 field corresponding to delay information. For example, the 1410 field indicates buffer size information for the data corresponding to LCG 1, and the 1420 field indicates delay information for the data corresponding to LCG 1. As described above, such buffer size information and delay information for an LCG may be indicated with two different fields.

[00154] In the examples described above, although a Long BSR configuration is presented, the configuration is not limited to these examples. The configuration described above can be applied to Short BSR. For example, terminal device 10 can transmit a Short BSR including delay information (e.g., the buffer size of the data seconds).

[00155] It should be noted that although a BSR configuration including delay information reporting is described, the configuration is not limited to this. A new MAC CE for transmitting delay information can be defined. For example, terminal device 10 can transmit, as a delay information report, a MAC CE including delay information. Thus, the “transmission of a BSR including delay information” described in the Descriptive Report can be replaced by “transmission of a MAC CE including delay information”.

[00156] Terminal unit 10 can receive initial configuration information related to the delay information report from base station unit 20. Base station unit 20 can transmit an RRC message including the initial configuration information to terminal unit 10. Base station unit 20 can transmit system information (SI, for example, SIB1 and / or) to terminal unit 10. Petition 870250087336, dated 09 / 26 / 2025, page 147 / 195 / 82 (SIB different from SIB1) including the initial configuration information. Base station device 20 can transmit a DCI including the initial configuration information to terminal device 10.

[00157] The initial configuration information may be “information indicating whether delay information should be transmitted”. The initial configuration information may indicate “transmission of delay information” or “no transmission of delay information”. The initial configuration information may be a flag indicating “transmission of delay information” or “no transmission of delay information”. For example, in a case where the RRC message includes the initial configuration information, terminal device 10 may transmit the delay information. In a case where the RRC message does not include the initial configuration information, terminal device 10 may not transmit the delay information. The initial configuration information may be set for an LCH.Terminal device 10 can determine whether to include delay information related to an LCH in a BSR, based on the initial configuration information defined for the LCH. For example, in a case where the initial configuration information indicates the transmission of delay information for a given LCH, terminal device 10 can include the delay information related to the LCH in a BSR. For example, the initial configuration information can be defined as a new IE element “LogicalChannelConfig”. The initial configuration information can be defined for an LCG. Terminal device 10 can determine whether to include delay information related to an LCG in a BSR, based on the initial configuration information defined for the LCG.For example, in a case where the initial configuration information indicates the transmission of delay information to a specific LCG, terminal device 10 may include the delay information related to that. Petition 870250087336, dated 09 / 26 / 2025, page 148 / 195 / 82 LCG in a BSR. For example, the initial configuration information can be defined as a new element of the IE “logicalChannelGroup”. The initial configuration information can be defined for a PDU or set of PDUs. Terminal device 10 can determine whether to include delay information related to a PDU or set of PDUs in a BSR, based on the initial configuration information defined for the PDU or set of PDUs. For example, in a case where the initial configuration information indicates the transmission of delay information for a given PDU or set of PDUs, terminal device 10 can include the delay information related to the PDU or set of PDUs in a BSR. The initial configuration information can be configured for an IE related to the PDU or set of PDUs included in the RRC message. The initial configuration information can be configured for a burst of data.Terminal device 10 can determine whether to include delay information related to a data burst in a BSR, based on the initial configuration information defined for the data burst. For example, in a case where the initial configuration information indicates the transmission of delay information for a given data burst, terminal device 10 can include the delay information related to the data burst in a BSR. The initial configuration information can be configured for an IE related to the data burst included in the RRC message.

[00158] Terminal unit 10 can receive, from base station unit 20, secondary configuration information related to the delay information report. Base station unit 20 can transmit to terminal unit 10 an RRC message including the secondary configuration information. Base station unit 20 can transmit to terminal unit 10 system information (SI, for example, SIB1 and / or Petition 870250087336, dated 09 / 26 / 2025, page 149 / 195 / 82 SIB (different from SIB1) including the second configuration information. Base station device 20 can transmit a DCI including the second configuration information to terminal device 10.

[00159] The second configuration information may indicate the type of data to be reported. In this configuration, terminal unit 10 selects the type of data to be reported based on the second configuration information. With respect to the selected data, terminal unit 10 may transmit the delay information report.

[00160] The second configuration information can be explicit information indicating the type of data to be reported or implicit information indicating the type of data to be reported. An example of explicit information and an example of implicit information are described below. Explicit Information

[00161] The second configuration information can be information indicating any of the following: LCH, LCG, PDU, PDU set, and data burst. Implicit Information

[00162] The second configuration information may be the first configuration information. In this configuration, terminal device 10 may select the type of data to be reported according to an IE configured with the first configuration information.

[00163] If the initial configuration information is set for a MAC cell group, this may indicate that the data unit to be reported corresponds to an LCG. For example, the initial configuration information may be set for an IE related to the MAC cell group included in the RRC message. Examples of such an IE include the “BSR-config” IE. As another example, if the initial configuration information is set for an LCG, this Petition 870250087336, dated 09 / 26 / 2025, p. 150 / 195 / 82 may indicate that the data unit to be reported corresponds to an LCG. For example, the initial configuration information may be defined for an IE related to an LCG. Examples of such an IE include the “logicalChannelGroup” IE.

[00164] In the case where the initial configuration information is set for a PDU or set of PDUs, this may indicate that the data unit to be reported corresponds to a PDU or one or more sets of PDUs. For example, the initial configuration information may be set for an IE related to the PDU or set of PDUs included in the RRC message.

[00165] In the case where the initial configuration information is set to a data burst, this may indicate that the data unit to be reported corresponds to one or more data bursts. For example, the initial configuration information may be set to an IE related to the data burst included in the RRC message.

[00166] For example, if the RRC message includes information indicating the first Th1 threshold, terminal device 10 can perform the control to trigger (and / or transmit) the delay information report. In other words, if the RRC message includes information indicating the first Th1 threshold, terminal device 10 can include, in a BSR, the delay information report based on the first Th1 threshold. If the RRC message does not include information indicating the first Th1 threshold, terminal device 10 can perform the control to not trigger (and / or not transmit) the delay information report. In other words, if the RRC message does not include information indicating the first Th1 threshold, terminal device 10 may not include any delay information report in a BSR.

[00167] A MAC PDU may include identifying information for Petition 870250087336, dated 09 / 26 / 2025, p. 151 / 195 / 82 to identify whether delay information reporting is provided. For example, a MAC subheader includes an LCID or eLCID value (i.e., a codepoint). An LCID or eLCID value for indicating delay information reporting can be defined. Based on the type of data to be reported, the following LCID or eLCID value can be defined: - The MAC CE includes the delay information report, and the data unit to be reported corresponds to an LCH.

[00168] - The MAC CE includes the delay information report and the data unit to be reported corresponds to an LCG.

[00169] - The MAC CE includes the delay information report and the data unit to be reported corresponds to a PDU.

[00170] - The MAC CE includes the delay information report and the data unit to be reported corresponds to one or more sets of PDUs.

[00171] - The MAC CE includes the delay information report and the data unit to be reported corresponds to one or more data bursts.

[00172] In the case where a BSR includes delay information reporting, based on the type of data to be reported, the following LCID or eLCID value may be set: - The BSR includes the delay information report, and the data unit to be reported corresponds to an LCH.

[00173] - The BSR includes the delay information report and the data unit to be reported corresponds to an LCG.

[00174] - The BSR includes the delay information report and the data unit to be reported corresponds to a PDU.

[00175] - The BSR includes the delay information report and the data unit to be reported corresponds to one or more sets of PDUs. Petition 870250087336, dated 09 / 26 / 2025, p. 152 / 195 / 82

[00176] - The BSR includes the delay information report and the data unit to be reported corresponds to one or more data bursts.

[00177] In addition, an LCID or eLCID value can be set indicating that the BSR includes the delay information report and in which of the following formats the BSR is.

[00178] - Short BSR BSR Long - BSR Short Truncated BSR Long Truncated - BSR Short Truncated Extended BSR Long Truncated Extended Preemptive BSR Extended Preemptive BSR

[00179] In another example, the MAC CE that includes the delay information report may include identification information. For example, the BSR may also include a field containing identification information indicating that delay information is included. 1.6.3. Condition for Triggering the Delay Information Report

[00180] Terminal device 10 can trigger the delay information report according to a certain condition. Hereafter, this condition is called the “trigger condition”. The trigger condition can include at least one of the conditions (a1) to (a4).

[00181] In addition, the trigger condition may include at least one of the following conditions (d1) to (d4): (d1) There is data where the remaining time is equal to or less than the first threshold Th1.

[00182] (d2) The activation duration of discontinuous reception (XDR, discontinuous reception) is initiated. Petition 870250087336, dated 09 / 26 / 2025, p. 153 / 195 / 82

[00183] (d3) There is a set of PDUs or burst of data being transmitted, or the set of PDUs or burst of data is buffered.

[00184] (d4) A set of PDUs is discarded.

[00185] For example, suppose that terminal unit 10 triggers the delay information report according to condition (d1). Here, the data unit to be reported corresponds to an LCG. Furthermore, the first limit Th1 is 5 ms. As illustrated in Figure 15, at time t1, the data corresponding to LCG 1 satisfies condition (d1). Terminal unit 10 triggers the delay information report. This report includes, for each LCG, information related to the remaining time as delay information. Base station unit 20 receives the report and recognizes that the data corresponding to LCG 1 has a remaining time of 5 ms and the data corresponding to LCG 2 has a remaining time of 8 ms. At time t4, 3 ms after time t1, both the data corresponding to LCG 1 and the data corresponding to LCG 2 satisfy condition (d1). Thus, terminal unit 10 triggers the delay information report again.However, each remaining time included in this new report only indicates that 3 ms have elapsed. Therefore, this report contains information that is highly likely already known by base station 20. In the example in Figure 15, the delay information report is triggered unnecessarily, which can increase the communication load (i.e., overhead). It should be noted that such a problem can occur not only in condition (d1), but also in any of the conditions (a1) to (a4) and (d2) to (d4). It is desirable to avoid an unnecessary delay information report being triggered frequently.

[00186] Taking this into account, terminal device 10 determines whether to trigger (or transmit) the delay information report using a specific condition that restricts this transmission. Hereafter, this condition is referred to as the “restriction condition”. Petition 870250087336, dated 09 / 26 / 2025, pages 154 / 195 / 82 The restriction condition may include at least one of the following conditions (e1) or (e2): (e1) A first timer is running.

[00187] (e2) The delay information report relating to certain data triggered at the current moment has already been transmitted.

[00188] If the restriction condition is met while the trigger condition is also met, terminal device 10 does not trigger or transmit the delay information report. If the restriction condition is not met while the trigger condition is met, terminal device 10 triggers or transmits the delay information report. Hereafter, Aspect 1-1, which uses condition (e1), and Aspect 1-2, which uses condition (e2), are described in detail. Aspect 1-1

[00189] The first timer is a timer to set a period during which the delay information report is neither triggered nor transmitted. In other words, the first timer acts as a prohibition timer, preventing the triggering or transmission of the delay information report. The first timer expires after a specified period of time. The time period for the first timer can be selected from a plurality of values. While the first timer is running, terminal device 10 neither triggers nor transmits the delay information report. In the case where the first timer is not running, terminal device 10 triggers or transmits the delay information report. For example, if an RRC message includes information indicating the first timer, terminal device 10 can control whether to trigger (and / or transmit) the delay information report.In other words, if the RRC message includes information indicating the first timer and the first timer is running, the device... Petition 870250087336, dated 09 / 26 / 2025, page 155 / 195 / 82 Terminal 10 can trigger or transmit the delay information report. In the case where the RRC message includes information indicating the first timer and the first timer is not running, Terminal 10 can trigger or transmit the delay information report. In a case where the RRC message does not include information indicating the first timer, Terminal 10 can execute the control to not trigger or transmit the delay information report.

[00190] Having initiated the flow illustrated in Figure 16, controller 110 determines whether the trigger condition has been met (S1601). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). In a case where the trigger condition is not met, communicator 120 does not transmit the delay information report.

[00191] On the other hand, in a case where the trigger condition is met, controller 110 determines whether condition (e1) is met (S1602). In a case where condition (e1) is met, communicator 120 does not transmit the delay information report. On the other hand, in a case where condition (e1) is not met, communicator 120 transmits the delay information report (S1603).

[00192] Based on the delay information report, controller 210 of base station 20 performs radio resource allocation with respect to terminal 10. Controller 210 can allocate a radio resource to delayed data, with priority.

[00193] Note that condition (e1) can be applied to a specific condition in the trigger condition. For example, condition (e1) can be applied to condition (d1). For example, in a case where condition (d1) is met and condition (e1) is met, communicator 120 does not transmit the delay information report. In a case where condition (d1) is met and condition (e1) is not met, communicator 120 transmits the delay information report. In a case where at least one of the Petition 870250087336, dated 09 / 26 / 2025, p. 156 / 195 / 82 conditions (a1) to (a4) and (d2) to (d4) are met, communicator 120 can transmit the delay information report without performing the determination of condition (e1). In another example, in a case where condition (d1) is met, terminal device 10 can start or restart the first timer. In the case where at least one of the conditions (a1) to (a4) and (d2) to (d4) is met, terminal device 10 may not start or restart the first timer. With regard to condition (d1), compared to the other conditions, frequent transmission of the delay information report is more likely to occur. Such a configuration described above can effectively prevent an unnecessary delay information report from being triggered frequently.

[00194] Note that only transmission of a BSR including the delay information report can be restricted by using the restriction condition. In other words, condition (e1) can be applied to a BSR including the delay information report and condition (e1) can not be applied to a BSR including no delay information report (i.e., the BSR illustrated in Figure 9 or 10). Thus, even in a case where condition (e1) is satisfied, communicator 120 can transmit a BSR including no delay information report.

[00195] At a point in time when the delay information report is triggered or transmitted, the first timer may be started or reset. In a configuration where a BSR includes the delay information report, at a point in time when the BSR is triggered or transmitted, the first timer may be started or reset. In another example, at a point in time when the BSR including the delay information report is triggered or transmitted, the first timer may be started or reset. In other words, at a point in time when a BSR including no delay information report is triggered or transmitted, the first timer may not be started or Petition 870250087336, dated 09 / 26 / 2025, page 157 / 195 / 82 restarted.

[00196] In a configuration where a BSR includes delay information reporting, the first timer can be used as a time period during which no SR is triggered or transmitted. In other words, while the first timer is running, terminal device 10 does not trigger or transmit SR.

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

[00198] Information related to the first timer can be included in parameters related to a BSR. For example, information related to the first timer can be included in the IE “BSR-config”

[00199] The first timer can be configured for an LCH or LCG. Information related to the first timer can be configured for an IE related to the LCH or LCG. Examples of such an IE include the “LogicalChannelConfig” IE and the “logicalChannelGroup” IE. In this configuration, in a case where the delay information report with Petition 870250087336, dated 09 / 26 / 2025, page 158 / 195 / 82, regarding an LCH or LCG configured with the first timer, is triggered or transmitted, the first timer is started or restarted. Thus, while the first timer is running, the delay information report regarding the LCH or LCG configured with the first timer is not triggered or transmitted.

[00200] The first timer can be configured for a PDU or set of PDUs. The information related to the first timer can be configured for an IE related to the PDU or set of PDUs. For example, the information related to the first timer can be configured for an IE related to the PDU or set of PDUs included in the RRC message. In this configuration, in a case where the delay information report regarding a PDU or set of PDUs configured with the first timer is triggered or transmitted, the first timer is started or restarted. Thus, while the first timer is running, the delay information report regarding the PDU or set of PDUs configured with the first timer is not triggered or transmitted.

[00201] The first timer can be configured for a data burst. The information related to the first timer can be configured for an IE related to the data burst. For example, the information related to the first timer can be configured for an IE related to the data burst included in the RRC message. In this configuration, in a case where the delay information report regarding a data burst configured with the first timer is triggered or transmitted, the first timer is started or restarted. Thus, while the first timer is running, the delay information report regarding the data burst configured with the first timer is not triggered or transmitted.

[00202] Terminal device 10 can receive from station device Petition 870250087336, dated 09 / 26 / 2025, page 159 / 195 / 82 base 20, third-party configuration information related to the delay information report. Base station 20 can transmit an RRC message including third-party configuration information to terminal 10. Base station 20 can transmit system information (SI, for example, SIB1 and / or SIB other than SIB1) including third-party configuration information to terminal 10. Base station 20 can transmit DCI including third-party configuration information to terminal 10.

[00203] The third configuration information can be “information indicating whether to apply the first timer”. The third configuration information can indicate “first timer application” or “no first timer application”. The third configuration information can be a flag indicating “first timer application” or “no first timer application”. The third configuration information can be configured for an LCH. For example, the third configuration information can be configured as a new IE element “LogicalChannelConfig”. The third configuration information can be configured for an LCG. For example, the third configuration information can be defined as a new IE element “logicalChannelGroup”. The third configuration information can be defined for a PDU or set of PDUs.The third configuration information can be set for an IE related to the PDU or set of PDUs included in the RRC message. The third configuration information can be set for a data burst. The third configuration information can be set for an IE related to the data burst included in the RRC message.

[00204] In a case where the third configuration information indicating no application of the first timer is configured to Petition 870250087336, dated 09 / 26 / 2025, page 160 / 195 / 82 If a LCH or LCG is triggered and the delay information report regarding the LCH or LCG is triggered, terminal device 10 may stop the first timer. In a case where the third configuration information indicating no application of the first timer is configured for a PDU or set of PDUs and the delay information report regarding the PDU or set of PDUs is triggered, terminal device 10 may stop the first timer. In a case where the third configuration information indicating no application of the first timer is configured for a data burst and the delay information report regarding the data burst is triggered, terminal device 10 may stop the first timer. Aspect 1-2

[00205] Satisfying condition (e2) means that the delayed information report with respect to certain data triggered at a current time point was transmitted in the past. Satisfying condition (e2) may mean that the delayed information report with respect to certain data triggered at a current time point is included in a previously transmitted delayed information report. In a case where condition (e2) is not satisfied, this means that the delayed information report with respect to certain data triggered at a current time point has not yet been transmitted; in other words, the delayed information report with respect to new data is triggered.

[00206] In the example in Figure 15, the delay information report related to the data corresponding to LCG 1 and the data corresponding to LCG 2 is triggered at time t4. However, the delay information report related to this data has already been transmitted at time t1. Condition (e2) is satisfied in such a case, and therefore, terminal device 10 does not transmit the delay information report at time t4. Subsequently, for example, in a case where the delay information report with respect to new Petition 870250087336, dated 09 / 26 / 2025, p. 161 / 195 / 82 data (e.g., data corresponding to LCG 3) is triggered, condition (e2) is not met. Thus, terminal device 10 transmits the delay information report with respect to the data corresponding to LCG 3.

[00207] Note that, in a case where condition (e2) is not met, the delayed information report to be transmitted may include the delayed information report already transmitted and the delayed information report with respect to new data. In the case where condition (e2) is not met, the delayed information report to be transmitted may include only the delayed information report with respect to new data.

[00208] Having initiated the flow illustrated in Figure 17, controller 110 determines whether the trigger condition has been met (S1701). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). In a case where the trigger condition is not met, communicator 120 does not transmit the delay information report.

[00209] On the other hand, in a case where the trigger condition is met, controller 110 determines whether condition (e2) is met (S1702). In a case where condition (e2) is met, communicator 120 does not transmit the delay information report. In contrast, in a case where condition (e2) is not met, communicator 120 transmits the delay information report (S1703).

[00210] Note that condition (e2) can be applied to a specific condition in the trigger condition. For example, condition (e2) can be applied to condition (d1). For example, in a case where condition (d1) is satisfied and condition (e2) is satisfied, communicator 120 does not transmit the delay information report. In a case where condition (d1) is satisfied and condition (e2) is not satisfied, communicator 120 transmits the delay information report. In a case where at least one of the conditions (a1) to (a4) and (d2) to (d4) is satisfied, communicator 120 can Petition 870250087336, dated 09 / 26 / 2025, page 162 / 195 / 82 transmit the delay information report without executing the determination of condition (e2). With respect to condition (d1), compared to the other conditions, frequent transmission of the delay information report is more likely to occur. The configuration described above can effectively prevent an unnecessary delay information report from being triggered frequently.

[00211] In a case where the data unit to be reported is data corresponding to one or more sets of PDUs, terminal unit 10 may operate as follows. It is assumed that the trigger condition (e.g., condition (d1)) is satisfied for a given PDU and the delay information report with respect to a set of PDUs to which the PDU belongs is transmitted. Subsequently, even if the trigger condition is satisfied for another PDU included in the set of PDUs to which the PDU belongs, terminal unit 10 does not trigger or transmit the delay information report with respect to the set of PDUs.

[00212] The configuration described above can prevent an unnecessary delay information report from being triggered frequently by applying at least one of the conditions (e1) or (e2). Thus, the possibility of increased communication load can be reduced.

[00213] Note that Aspect 1-1 and Aspect 1-2 can be combined. In other words, terminal device 10 can trigger or transmit the delay information report using conditions (e1) and (e2). For example, in a case where neither condition (e1) nor condition (e2) is satisfied with the trigger condition being satisfied, communicator 120 can transmit the delay information report.

[00214] In another example, either condition (e1) or condition (e2) can be prioritized. For example, having a flow illustrated in Figure 18 initiated, controller 110 determines whether the trigger condition is satisfied (S1801). The trigger condition can include at least one of the conditions (a1) to (a4) and Petition 870250087336, dated 09 / 26 / 2025, page 163 / 195 / 82 (dl) to (d4). In a case where the trigger condition is not met, communicator 120 does not transmit the delay information report.

[00215] On the other hand, in a case where the trigger condition is met, controller 110 determines whether condition (e1) is met (S1802). In a case where condition (e1) is met, controller 110 determines whether condition (e2) is met (S1803). In a case where condition (e2) is met, communicator 120 does not transmit the delay information report.

[00216] On the other hand, in a case where condition (e1) is not met in Step S1802, communicator 120 transmits the delay information report (S1804). In a case where condition (e2) is not met in Step S1803, communicator 120 transmits the delay information report (S1804).

[00217] As described above, in a case where condition (e1) is met and condition (e2) is not met, communicator 120 can transmit the delay information report. In other words, even if the first timer is running, in a case where the delay information report regarding new data is triggered, communicator 120 can transmit the delay information report. 2. Second Modality

[00218] Next, a configuration of a second embodiment will be described. Hereafter, only details different from those of the first embodiment are described, and the description of details identical to those of the first embodiment is omitted. Thus, the configuration of the first embodiment and any alteration thereof may be applied to the configuration described in the present embodiment, provided that the configurations are not inconsistent with each other.

[00219] The delay information report includes uplink data delay information with a low latency requirement. Petition 870250087336, dated 09 / 26 / 2025, pages 164 / 195 / 82 Therefore, a delay in transmitting the delay information report can render the delay information report unnecessary for base station 20. For example, in the example in Figure 15, it is assumed that the delay information report to be transmitted at time t1 has a delay of 5 ms or more. In this case, the remaining time information corresponding to LCG 1 may be unnecessary for base station 20. Furthermore, transmitting such an unnecessary delay information report can cause an increase in communication load (i.e., overhead).

[00220] Taking this into consideration, in a situation where the delay information report is triggered according to the trigger condition, terminal device 10 determines whether the available uplink resources can accommodate the delay information report. Based on this determination, terminal device 10 performs certain processing related to the transmission of the delay information report. This processing includes, for example, at least one transmission of a scheduling request (SR) or cancellation of the delay information report transmission. Aspect 2-1 and Aspect 2-2 are described herein. Aspect 2-1

[00221] Terminal device 10 determines, in a situation where the delay information report is triggered, whether the following condition (f1) is satisfied.

[00222] (f1) Uplink resources can accommodate delay information reporting. In other words, uplink resources are available for a new transmission of delay information reporting and uplink resources can accommodate delay information reporting.

[00223] In a case where condition (f1) is satisfied, the device Petition 870250087336, dated 09 / 26 / 2025, page 165 / 195 / 82 terminal 10 transmits the delay information report. On the other hand, in a case where condition (f1) is not met, in other words, a case where it is determined that the uplink resources cannot accommodate the delay information report, terminal 10 performs the processing for transmitting an SR as determined processing. The processing for transmitting the SR may include one or more processing steps related to the SR. The processing for transmitting the SR may include the transmission of the SR. Thus, based on the fact that the uplink resources cannot accommodate the delay information report in a situation where the delay information report is triggered, terminal 10 may perform the processing for transmitting the SR. According to the SR, base station 20 allocates uplink resources to terminal 10.Terminal device 10 can transmit the delay information report using the allocated uplink resources.

[00224] Having initiated the flow illustrated in Figure 19, controller 110 determines whether the trigger condition has been met (S1901). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). In a case where the trigger condition is not met, communicator 120 does not transmit the delay information report.

[00225] On the other hand, in a case where the trigger condition is met, controller 110 determines whether condition (f1) is met (S1902). In a case where condition (f1) is met, communicator 120 transmits the delay information report (S1903). Conversely, in a case where condition (f1) is not met, this means that there is no uplink resource available for the delay information report. Therefore, communicator 120 transmits an SR to base station handset 20 (S1904).

[00226] Note that, in the case where condition (f1) is not satisfied, the Petition 870250087336, dated 09 / 26 / 2025, page 166 / 195 / 82 controller 110 can determine if a second timer to delay the transmission of the SR is running. For example, the second timer could be the “logicalChannelSR-DelayTimer”. In a case where the second timer is running, communicator 120 may not transmit an SR. In a case where the second timer is not running, communicator 120 may transmit an SR.

[00227] In another example, even in a case where the second timer is running, communicator 120 can transmit an SR. In other words, regardless of whether the second timer is running, communicator 120 can transmit an SR. The delay information report includes uplink data delay information with the low latency requirement and, therefore, it is preferable that it be transmitted to base station handset 20 as quickly as possible. Such a configuration allows uplink resources for transmitting the delay information report to be allocated to terminal handset 10 more quickly.

[00228] Note that condition (f1) can be applied to a specific condition in the trigger condition. For example, condition (f1) can be applied to condition (d1). For example, in a case where condition (d1) is met and condition (f1) is not met, communicator 120 transmits an SR. In a case where the delay information report is triggered according to condition (d1), this means that the remaining time until the delay information report transmission is complete is short. Applying condition (f1) to condition (d1) allows uplink resources for delay information report transmission to be allocated to terminal device 10 more quickly.

[00229] In a case where condition (f1) is satisfied and a subject to be fired (i.e., data corresponding to an LCH, LCG, PDU, set of PDUs, or burst of data) does not meet the LCP mapping constraint, the Petition 870250087336, dated 09 / 26 / 2025, page 167 / 195 / 82 communicator 120 may not transmit an SR.

[00230] The configuration described above allows uplink resources to be allocated to terminal device 10 by transmitting an SR. For example, in a case where the delay information report is triggered according to condition (d1), base station device 20 can receive the delay information report before the first time limit for data corresponding to the delay information included in the delay information report has passed. Base station device 20 can then appropriately allocate uplink resources to terminal device 10. Aspect 2-2

[00231] Terminal device 10 determines, in a situation where the delay information report is triggered, whether the following condition (g1) is satisfied.

[00232] (g1) Uplink resources can accommodate delay information reporting for a given second time limit. In other words, uplink resources are available for a new transmission of delay information reporting and uplink resources can accommodate delay information reporting for the second time limit.

[00233] Terminal device 10 can determine, based on the remaining time, the second time limit for condition (g1). In other words, the second time limit can be the same as the first time limit described above. More specifically, the second time limit can be a time limit until which the transmission of part or all of the data to be reported must be completed. The second time limit can be a time limit determined based on a PDB or PSDB. The second time limit can be a time limit determined based on a PDB or PSDB configured for part or all of the data to be Petition 870250087336, dated 09 / 26 / 2025, pp. 168 / 195 / 82 reported. The second time limit may be a value obtained by adding a PDB or PSDB to the first time limit. The second time limit may be a value prior to a value obtained by adding a PDB or PSDB to the first time limit.

[00234] In a case where condition (g1) is satisfied, terminal device 10 transmits the delay information report. In contrast, in a case where condition (g1) is not satisfied, terminal device 10 cancels the transmission or firing of the delay information report, as determined by processing. Specifically, based on the fact that the uplink resources cannot accommodate the delay information report up to the second time limit in a situation where the delay information report is fired, the transmission or firing of the delay information report is canceled. In other words, in the case where condition (g1) is not satisfied, terminal device 10 cancels the firing (i.e., the firing based on the satisfaction of the firing condition) with respect to the delay information report.

[00235] Condition (g1) can be replaced by a condition in which the firing with respect to the delay information report is not cancelled until the second time limit. Thus, terminal device 10 can cancel the transmission or firing of the delay information report, based on the fact that the firing with respect to the delay information report is not cancelled until the second time limit.

[00236] In a case where, by the time the second time limit has passed, there are no uplink resources available for a new transmission and capable of accommodating the delay information report, terminal device 10 may cancel the transmission or trigger the delay information report. In another example, in a case where, even if the delay information report is triggered, the delay information report cannot be transmitted before the delay time limit. Petition 870250087336, dated 09 / 26 / 2025, page 169 / 195 / 82 included in the delay information report expires, terminal device 10 may cancel the transmission or triggering of the delay information report.

[00237] Having initiated the flow illustrated in Figure 20, controller 110 determines whether the trigger condition has been met (S2001). The trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). In a case where the trigger condition is not met, communicator 120 does not transmit the delay information report.

[00238] On the other hand, in a case where the triggering condition is met, controller 110 determines whether condition (g1) is met (S2002). In a case where condition (g1) is met, communicator 120 transmits the delay information report (S2003). Conversely, in a case where condition (g1) is not met, communicator 120 cancels the transmission or triggering of the delay information report (S2004). Note that controller 110 can cancel the transmission or triggering of the delay information report and transmit the cancellation indication to communicator 120.

[00239] Note that if condition (c1) or (c2) is met, communicator 120 may cancel transmission or triggering of the delay information report.

[00240] Condition (g1) can be applied to a specific condition in the trigger condition. For example, condition (g1) can be applied to condition (d1). For example, in a case where condition (d1) is satisfied and condition (g1) is satisfied, communicator 120 cancels the transmission or triggering of the delayed information report. In a case where the delayed information report is triggered according to condition (d1), this means that the remaining time until the completion of the delayed information report transmission is short. Even if the delayed information report is transmitted to base station 20 in such a case, the data Petition 870250087336, dated 09 / 26 / 2025, pp. 170 / 195 / 82, corresponding to the delay information included in the delay information report, may have already exceeded the first time limit. In other words, the delay information included in the delay information report may be unnecessary, not useful, for base station device 20. Transmitting such an unnecessary delay information report may cause an increase in communication load. This configuration may prevent an unnecessary delay information report from being transmitted.

[00241] Terminal unit 10 can start a third timer at a point in time when the delay information report is triggered (i.e., the trigger condition is met) and then determine, based on the third timer, the second time limit. The third timer expires at a certain time period. The time period for the third timer can be selected from a plurality of values. For example, at a point in time when the third timer expires, terminal unit 10 can determine that condition (g1) is not met. Terminal unit 10 can receive, from base station unit 20, an RRC message including information related to the third timer.

[00242] In a BSR configuration including delay information reporting, information related to the third timer may be included in an IE related to the BSR (for example, the IE “BSR-Conflg”).

[00243] The third timer can be configured for an LCH or LCG. Information related to the third timer can be configured for an IE related to the LCH or LCG. Examples of such an IE include the “LoglcalChannelConflg” IE and the “loglcalChannelGroup” IE. In this configuration, at a point in time when the delay information report relative to an LCH or LCG configured with the third timer is Petition 870250087336, dated 09 / 26 / 2025, pp. 171 / 195 / 82 triggered, the third timer is initiated. Thus, in a case where the third timer expires, the transmission or triggering of the delay information report related to the LCH or LCG configured with the third timer is canceled. Note that the delay information report related to an LCH or LCG not configured with the third timer can be transmitted. In other words, the triggering of the delay information report related to the LCH or LCG not configured with the third timer may not need to be canceled.

[00244] The third timer can be configured for a PDU or set of PDUs. The information related to the third timer can be configured for an IE relative to the PDU or set of PDUs. For example, the information related to the third timer can be configured for an IE relative to the PDU or set of PDUs included in the RRC message. In this configuration, at a point in time when the delay information report relative to a PDU or set of PDUs configured with the third timer is triggered, the third timer is started. Thus, in a case where the third timer expires, the transmission or triggering of the delay information report relative to the PDU or set of PDUs configured with the third timer is canceled. Note that the delay information report relative to a PDU or set of PDUs not configured with the third timer can be transmitted.In other words, the triggering of the delay information report related to the PDU or set of PDUs not configured with the third timer may not need to be canceled.

[00245] The third timer can be configured for a data burst. The information related to the third timer can be configured for an IE relative to the data burst. For example, the information related to the third timer can be configured for an IE relative to the data burst included in the RRC message. In this Petition 870250087336, dated 09 / 26 / 2025, page 172 / 195 / 82 configuration, at a point in time when the delayed information report related to a data surge configured with the third timer is triggered, the third timer is started. Thus, in a case where the third timer expires, the transmission or triggering of the delayed information report related to the data surge configured with the third timer is canceled. Note that the delayed information report related to a data surge not configured with the third timer can be transmitted. In other words, the triggering of the delayed information report related to the data surge not configured with the third timer may not need to be canceled.

[00246] The configuration described above can prevent unnecessary delay information reports from being transmitted. No uplink resources are used for such unnecessary delay information reports, and thus the possibility of increased communication load can be reduced.

[00247] Aspect 2-1 and Aspect 2-2 can be combined. In other words, using conditions (f1) and (g1), terminal device 10 can perform certain processing related to the transmission of the delay information report. For example, after executing Step S1904 in the flow of Figure 19, controller 110 can determine if condition (g1) is met. In a case where condition (g1) is not met, communicator 120 can cancel the transmission or triggering of the delay information report. As described above, in a case where, after the transmission of an SR by terminal device 10, there is no uplink resource capable of accommodating the delay information report up to the second time limit, terminal device 10 can cancel the transmission or triggering of the delay information report.

[00248] 3. Changes

[00249] Although the present description is made in accordance with Petition 870250087336, dated 09 / 26 / 2025, p. 173 / 195 / 82 modalities, it is understood that the present description is not limited to the modalities or structures. The present description includes various alterations and variations within the equivalent scope. Any other combination including one or more elements included in the modalities is included in the essence or spirit of the scope of this description.

[00250] In Figures 16 to 18, although the determination of the trigger condition is followed by the determination of the restriction condition (condition (e1) and / or (e2)), the present description is not limited to this configuration. For example, the determination of the restriction condition can be performed before the determination of the trigger condition. Based on whether the restriction condition is satisfied, terminal device 10 can determine whether to determine the trigger condition. For example, in a case where the restriction condition is satisfied, terminal device 10 does not determine the trigger condition. In other words, the delayed information report is not triggered. In a case where the restriction condition is not satisfied, terminal device 10 determines the trigger condition.Therefore, the first mode may include an “aspect in which terminal device 10 cancels the triggering with respect to the delay information report using the restriction condition after the triggering condition is met” and an “aspect in which terminal device 10 does not determine the triggering condition for the delay information report based on the fact that the restriction condition is met”.

[00251] In Figure 19, although the determination of the firing condition is followed by the determination of condition (f1), the present description is not limited to this configuration. For example, the determination of condition (f1) can be performed before the determination of the firing condition. Based on whether condition (f1) is satisfied, terminal device 10 can determine whether to determine the firing condition. In a case where condition (f1) is satisfied, terminal device 10 determines the firing condition. In a Petition 870250087336, dated 09 / 26 / 2025, p. 174 / 195 / 82 in which condition (f1) is not met, terminal device 10 performs processing for transmission of an SR. Therefore, Aspect 2-1 of the second embodiment may include an “aspect in which terminal device 10 performs processing for transmission of an SR in a case where the triggering condition is met and condition (f1) is not met” and an “aspect in which terminal device 10 performs processing for transmission of an SR, without determining the triggering condition, in a case where condition (f1) is not met”.

[00252] In Figure 20, although the determination of the trigger condition is followed by the determination of condition (g1), the present description is not limited to this configuration. For example, the determination of condition (g1) can be performed before the determination of the trigger condition. Based on whether condition (g1) is satisfied, terminal device 10 can determine whether to determine the trigger condition. In a case where condition (g1) is satisfied, terminal device 10 determines the trigger condition. In a case where condition (g1) is not satisfied, terminal device 10 does not determine the trigger condition. In other words, the delayed information report is not triggered.Therefore, Aspect 2-2 of the second embodiment may include an “aspect in which terminal device 10 cancels firing with respect to the delay information report (i.e., firing according to the satisfaction of the firing condition) in a case where condition (g1) is not satisfied” and an “aspect in which terminal device 10 does not determine the firing condition for the delay information report in a case where condition (g1) is not satisfied”.

[00253] Expressions such as words and phrases used in the embodiments are merely examples and may be replaced by substantially identical or similar expressions. In particular, since the technique according to the embodiments refers to technical specifications, the expressions in the embodiments may be replaced by expressions Petition 870250087336, dated 09 / 26 / 2025, pp. 175 / 195 / 82 substantially identical or similar in technical specifications (for example, the technical specifications cited in the descriptive report of this application).

[00254] The information transmitted / received in the modes may be transmitted / received in the same or a different message or in the same or a different element as or from that already described in the technical specifications, or may be transmitted / received in a new message or element to be defined. The information transmitted / received in the modes may be transmitted / received using a layer and / or a channel different from that of the modes.

[00255] The means and / or functions provided by the devices described in the embodiments may be provided by software stored in a tangible memory device and a computer that runs the software, by software alone, by hardware alone, or by a combination thereof. For example, when one of the devices is provided by an electronic circuit being hardware, it may be provided by a digital circuit including several logic circuits or an analog circuit.

[00256] The devices described in the embodiments execute a program stored in a non-transient tangible storage medium. The execution of the program causes the execution of a method corresponding to the program. 4. Supplementary Notes

[00257] All or part of the modalities and amendments may be described as in the following supplementary notes, but the description is not limited to the content of the following supplementary notes. The following text expresses relationships in which a supplementary note that depends on a plurality of supplementary notes depends on a supplementary note that depends on a plurality of supplementary notes. All dependency relationships of the supplementary notes expressed below are included in Petition 870250087336, dated 09 / 26 / 2025, pp. 176 / 195 / 82 modalities. (Supplementary Note 1)

[00258] A terminal apparatus (10), including: a controller (110) configured to perform, in a situation where a delay information report including delay-related information for certain data is triggered, the determination of whether an available uplink resource is capable of accommodating the delay information report; and a communicator (120) configured to perform, based on the determination, certain processing related to the transmission of the delay information report. (Supplementary Note 2)

[00259] The terminal device according to supplementary note 1, in which the communicator is configured to execute, based on the fact that the available uplink resource is not capable of accommodating the delay information report in the situation where the delay information report is triggered, a processing for transmitting a scheduling request (SR) as the determined processing. (Supplementary Note 3)

[00260] The terminal device according to supplementary note 2, wherein the communicator is configured not to perform processing for SR transmission in the event that the available uplink resource is not capable of accommodating the delay information report in the situation where the delay information report is triggered and where a timer to delay SR transmission is running, and the communicator is configured to perform processing Petition 870250087336, dated 09 / 26 / 2025, pp. 177 / 195 / 82 for transmission of the SR in the case where the available uplink resource is not capable of accommodating the delay information report in the situation where the delay information report is triggered and the timer is not running. (Supplementary Note 4)

[00261] The terminal device according to supplementary note 3, wherein the communicator is configured to receive, from a base station device (20), a radio resource control (RRC) message, and the timer is the “logicalChannelSR-DelayTimer” included in the RRC message. (Supplementary Note 5)

[00262] The terminal device in accordance with supplementary note 2, wherein the communicator is configured to perform processing for SR transmission even in the case where the available uplink resource is not capable of accommodating the delay information report in the situation where the delay information report is triggered and where a timer to delay SR transmission is running. (Supplementary Note 6)

[00263] The terminal device according to supplementary note 5, in which the communicator is configured to receive, from a base station device (20), a radio resource control (RRC) message, and the timer is the “logicalChannelSR-DelayTimer” included in the RRC message. (Supplementary Note 7) Petition 870250087336, dated 09 / 26 / 2025, pages 178 / 195 / 82

[00264] The terminal device in accordance with supplementary note 2, wherein the controller is configured to trigger the delay information report using a trigger condition related to a remaining time until a transmission deadline for the specified data is reached, and the communicator is configured to perform processing for SR transmission in the event that the remaining time is a certain threshold or less and the available uplink resource is not able to accommodate the delay information report. (Supplementary Note 8)

[00265] The terminal device according to supplementary note 1, where the communicator is configured to cancel, based on the fact that the available uplink resource is not capable of accommodating the delay information report up to a certain deadline in the situation where the delay information report is triggered, the transmission or triggering of the delay information report as the determined processing. (Supplementary Note 9)

[00266] The terminal device in accordance with supplementary note 8, wherein the controller is configured to trigger the delay information report using a trigger condition related to a remaining time until a transmission deadline for the specified data is reached, and the communicator is configured to cancel, in the event that the remaining time is a certain threshold or less and the available uplink resource is not able to accommodate the delay information report until the certain deadline, the transmission or the triggering of the delay information report. Petition 870250087336, dated 09 / 26 / 2025, pp. 179 / 195 / 82 (Supplementary Note 10)

[00267] The terminal device in accordance with supplementary note 9, in which the controller is configured to determine the specific time limit based on the remaining time. (Supplementary Note 11)

[00268] The terminal device in accordance with supplementary note 8, wherein the controller is configured to determine the specific time limit based on a packet delay budget (PDB) or a protocol data unit set delay budget (PSDB). (Supplementary Note 12)

[00269] The terminal device in accordance with supplementary note 8, wherein the controller is configured to start a timer at a point in time when the delay information report is triggered and determine the specific time limit based on the timer. (Supplementary Note 13)

[00270] The terminal device according to supplementary note 12, in which the communicator is configured to receive, from a base station device (20), a radio resource control (RRC) message, and the timer is included in the RRC message. (Supplementary Note 14)

[00271] The terminal device in accordance with any of the supplementary notes 1 to 13, where Petition 870250087336, dated 09 / 26 / 2025, page 180 / 195 / 82 the delay information report is a buffer state report (BSR) including delay information and buffer size information related to a buffer size. (Supplementary Note 15)

[00272] The terminal device in accordance with any of supplementary notes 1 to 14, wherein delay information is information relating to a delay time, or information relating to data provided with a temporal restriction or requirement. (Supplementary Note 16)

[00273] The terminal device in accordance with any of supplementary notes 1 to 15, wherein the determined data are 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 one or more data bursts. (Supplementary Note 17)

[00274] A method of a terminal device (10), the method including: performing, in a situation where a delay information report including delay-related information for certain data is triggered, the determination of whether an available uplink resource is capable of accommodating the delay information report; and performing, based on the determination, certain processing related to the transmission of the delay information report. Petition 870250087336, dated 09 / 26 / 2025, pp. 181 / 195 / 82 (Supplementary Note 18)

[00275] A program that causes a processor (101) in a terminal device (10) to execute: The task involves, in a situation where a delay information report including delay-related information for specific data is triggered, determining whether an available uplink resource is capable of accommodating the delay information report; and performing, based on that determination, specific processing related to transmitting the delay information report. (Supplementary Note 19)

[00276] A non-transient tangible storage medium storing on it a program that causes a processor (101) in a terminal device (10) to execute: The task involves, in a situation where a delay information report including delay-related information for specific data is triggered, determining whether an available uplink resource is capable of accommodating the delay information report; and performing, based on that determination, specific processing related to transmitting the delay information report. (Supplementary Note 20)

[00277] A base station apparatus (20) including: a communicator (220) configured to receive, from a terminal device (10), a delay information report including delay-related information for certain data; and a controller (210) configured to perform, based on Petition 870250087336, dated 09 / 26 / 2025, page 182 / 195 / 82 delay information report, radio resource allocation with respect to the terminal device, where the communicator is configured to receive, from the terminal device, a scheduling request (SR) in the event that, on the terminal device, an available uplink resource is not able to accommodate the delay information report in a situation where the delay information report is triggered on the terminal device. (Supplementary Note 21)

[00278] The base station device according to supplementary note 20, where the controller is configured to allocate a radio resource to the terminal device, according to the SR. (Supplementary Note 22)

[00279] A method of a base station apparatus (20), the method including: the receipt, from a terminal device (10), of a delay information report including delay information related to delays for certain data; The realization, based on the delay information report, of the allocation of radio resources with respect to the terminal device, in which the receipt, from the terminal device, of a scheduling request (SR) in the case where, in the terminal device, an available uplink resource is not able to accommodate the delay information report in a situation in which the delay information report is triggered in the terminal device. (Supplementary Note 23)

[00280] A program that causes a processor (201) in a terminal device (20) to execute: the receipt, from a terminal device (10), of a Petition 870250087336, dated 09 / 26 / 2025, page 183 / 195 / 82 delay information report including delay information related to delays for certain data; The realization, based on the delay information report, of the allocation of radio resources with respect to the terminal device, in which the receipt, from the terminal device, of a scheduling request (SR) in the case where, in the terminal device, an available uplink resource is not able to accommodate the delay information report in a situation in which the delay information report is triggered in the terminal device. (Supplementary Note 24)

[00281] A non-transient tangible storage medium storing on it a program that causes a processor (201) in a base station device (20) to execute: the receipt, from a terminal device (10), of a delay information report including delay information related to delay for certain data; and the realization, based on the delay information report, of the allocation of radio resources with respect to the terminal device, wherein the receipt, from the terminal device, of a scheduling request (SR) in the event that, in the terminal device, an available uplink resource is not able to accommodate the delay information report in a situation in which the delay information report is triggered in the terminal device. (Supplementary Note 25)

[00282] A terminal apparatus (10), including: a receiver (122) configured to receive, from a base station device (20), a radio resource control (RRC) message including information to configure an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and Petition 870250087336, dated 09 / 26 / 2025, page 184 / 195 / 82 information to indicate a threshold for controlling the triggering of a Delay Status Report (DSR) for LCG data; and a controller (110) configured to control the triggering of the DSR based on the fact that the remaining time relative to a nearest deadline for the LCG data becomes less than the threshold and the DSR is not transmitted for the LCG data, where the controller is configured to cancel, in the event that a deadline for the LCG data associated with the DSR expires, the DSR that was triggered and was not canceled. (Supplementary Note 26)

[00283] The terminal device in accordance with supplementary note 25, wherein the DSR includes a field with bits, each indicating whether a buffer size field for each LCG is present, a field indicating the time remaining relative to the nearest deadline for the LCG data, and a field indicating a buffer size related to the LCG. (Supplementary Note 27)

[00284] The terminal device according to supplementary note 26, in which the controller is configured to switch between a first table and a second table different from the first table to establish the field that indicates the buffer size. (Supplementary Note 28)

[00285] The terminal device in accordance with supplementary note 25, in which the DSR includes Petition 870250087336, dated 09 / 26 / 2025, p. 185 / 195 / 82 a field with bits, each indicating whether a buffer size field for each LCG is present, and a field including information related to the LCG data with the remaining time being below the threshold. (Supplementary Note 29)

[00286] The terminal device in accordance with any of supplementary notes 25 to 28, wherein the DSR is a medium access control (MAC CE) element including a subheader that includes an extended logical channel identifier (eLCID) for identification of the DSR. (Supplementary Note 30)

[00287] A method of a terminal device (10), the method including: receiving, from a base station device (20), a radio resource control (RRC) message including information to set up an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for controlling the firing of a delay state report (DSR) for LCG data; To control the triggering of the DSR based on the fact that the remaining time relative to a closer deadline for the LCG data becomes less than the threshold and the DSR is not transmitted to the LCG data; and to cancel, in the case where a deadline for the LCG data associated with the DSR expires, the DSR that was triggered and was not canceled. (Supplementary Note 31)

[00288] The terminal device method according to supplementary note 30, wherein the DSR includes a field with bits, each indicating whether a buffer size field for each LCG is present, Petition 870250087336, dated 09 / 26 / 2025, page 186 / 195 / 82 a field indicating the remaining time in relation to the nearest deadline for the LCG data, and a field indicating a buffer size related to the LCG. (Supplementary Note 32)

[00289] The terminal apparatus method according to supplementary note 31, additionally comprising: Switching between a first table and a second table that is different from the first table will determine the field that indicates the buffer size. (Supplementary Note 33)

[00290] The terminal device method according to supplementary note 30, wherein the DSR includes a field with bits, each indicating whether a buffer size field for each LCG is present, and a field including information relating to the LCG data with the remaining time being below the threshold. (Supplementary Note 34)

[00291] The terminal device method according to any of supplementary notes 30 to 33, wherein the DSR is a medium access control (MAC CE) element including a subheader that includes an extended logical channel identifier (eLCID) for DSR identification. (Supplementary Note 35)

[00292] A program that causes a processor (101) in a terminal device (10) to execute: the receipt, from a base station device (20), of a radio resource control (RRC) message including information Petition 870250087336, dated 09 / 26 / 2025, pp. 187 / 195 / 82 to configure an identifier (ID) for a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information to indicate a threshold for controlling the triggering of a Delay State Report (DSR) for LCG data; The control of DSR triggering is based on the fact that the remaining time relative to a closer deadline for LCG data becomes less than the threshold, and the DSR is not transmitted to the LCG data; and the cancellation, in the event that a deadline for LCG data associated with the DSR expires, of the DSR that was triggered and not canceled. (Supplementary Note 36)

[00293] A non-transient tangible storage medium that stores in it a program that causes a processor (101) in a terminal device (10) to execute: the receipt, from a base station device (20), of a radio resource control (RRC) message including information to set up an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for controlling the firing of a delay state report (DSR) for LCG data; The control of DSR triggering is based on the fact that the remaining time relative to a closer deadline for LCG data becomes less than the threshold, and the DSR is not transmitted to the LCG data; and the cancellation, in the event that a deadline for LCG data associated with the DSR expires, of the DSR that was triggered and not canceled.

[00294] Note that the content of the descriptions of related technical documents and reference literature mentioned above is incorporated here by reference. Petition 870250087336, dated 09 / 26 / 2025, pages 188 / 195

Claims

1 / 6 CLAIMS 1. Terminal apparatus (10), characterized in that it comprises: a receiver (122) configured to receive, from a base station apparatus (20), a radio resource control (RRC) message including information to configure an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for triggering a delay status report (DSR) for the LCG; and a controller (110) configured to trigger the DSR in the event that the remaining time relative to a nearest deadline for certain data becomes less than the threshold and the DSR is not transmitted for certain data, wherein the controller is configured to cancel, in the event that a deadline for certain data associated with the DSR expires, the DSR that was triggered and was not canceled.

2. Terminal apparatus according to claim 1, characterized in that the specified data is given to the LCG, and the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, a remaining time field indicating the time remaining relative to the nearest deadline for the data to the LCG, and the buffer size field indicating a buffer size related to the data to the LCG.

3. Terminal device according to claim 2, characterized in that the controller is configured to use one of a first table and a second table to establish the buffer size field that indicates the buffer size.

4. Terminal device according to claim 1, characterized in that the specified data is given to the LCG, and the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, and a field including information relating to a data size for the LCG with the remaining time being below the threshold.

5. Terminal device according to claim 1, characterized in that certain data is given to the LCH, and the controller is configured to trigger the DSR in the event that the remaining time relative to a closer deadline for the data to the LCH becomes less than the threshold and the DSR is not transmitted for the data to the LCH.

6. Terminal device according to any one of claims 1 to 5, characterized in that the DSR is a medium access control (MAC CE) element that is identified by an extended logical channel identifier (eLCID) included in a MAC subheader.

7. Terminal device method (10), the method characterized in that it comprises: receiving, from a base station device (20), a radio resource control (RRC) message including information to set up an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for triggering a delay status report (DSR) for the LCG; Petition 870250087336, dated 26 / 09 / 2025, p. 190 / 195 3 / 6 triggering the DSR in the event that the remaining time relative to a nearest deadline for certain data becomes less than the threshold and the DSR is not transmitted for certain data; and cancelling, in the event that a deadline for certain data associated with the DSR expires, the DSR that was triggered and was not cancelled.

8. A terminal apparatus method according to claim 7, characterized in that certain data is given to the LCG, and the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, a remaining time field indicating the time remaining relative to the nearest deadline for the data to the LCG, and the buffer size field indicating a buffer size related to the data for the LCG.

9. A terminal apparatus method according to claim 8, characterized in that it further comprises: using one of a first table and a second table to establish the buffer size field that indicates the buffer size.

10. Terminal apparatus method according to claim 7, characterized in that certain data is given to the LCG, and the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, and a field including information relating to a data size for the LCG with the remaining time being below the threshold.

11. Terminal device method according to Petition 870250087336, dated 09 / 26 / 2025, p. 191 / 195 4 / 6 claim 7, characterized in that the specified data is given to the LCH, and the method further comprises triggering the DSR in the event that the remaining time relative to an nearest deadline for the data to the LCH becomes less than the threshold and the DSR is not transmitted for the data to the LCH.

12. Terminal device method according to any one of claims 7 to 11, characterized in that the DSR is a medium access control (MAC CE) element that is identified by an extended logical channel identifier (eLCID) included in a MAC subheader.

13. Base station apparatus (20), characterized in that it comprises: a transmitter (221) configured to transmit, to a terminal apparatus (10), a radio resource control (RRC) message, including information for configuring an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information to indicate a threshold for triggering a delay state report (DSR) for the LCG; and a receiver (222) configured to receive, from the terminal apparatus, the DSR triggered in the event that the remaining time relative to an nearest deadline for certain data becomes less than the threshold and the DSR is not transmitted for the certain data, in the event that a time limit for the certain data associated with the DSR expires, the DSR that was triggered and not canceled is canceled.

14. Base station apparatus according to claim 13, characterized in that the specified data is data for the LCG, and Petition 870250087336, dated 09 / 26 / 2025, pp. 192 / 195 5 / 6 the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, a remaining time field indicating the remaining time relative to the nearest deadline for the LCG data, and the buffer size field indicating a buffer size related to the data for the LCG.

15. Base station apparatus according to claim 14, characterized in that the buffer size field is defined using one of a first and a second table.

16. Base station apparatus according to claim 13, characterized in that the specified data is given to the LCG, and the DSR includes each of the LCG bit fields indicating whether a buffer size field for each LCG is present, and a field including information relating to the size of the data for the LCG with the remaining time below the threshold.

17. Base station apparatus according to claim 13, characterized in that certain data is given to the LCH, and the receiver is configured to receive, from the terminal apparatus, the triggered DSR in a case where the remaining time relative to an nearest deadline for the data to the LCH becomes less than the threshold and the DSR is not transmitted for the data to the LCH.

18. Base station apparatus according to any one of claims 13 to 17, characterized in that the DSR is a medium access control element (MAC Petition 870250087336, dated 09 / 26 / 2025, p. 193 / 195 6 / 6 CE) that is identified by an extended logical channel identifier (eLCID) included in a MAC subheader. Petition 870250087336, dated 09 / 26 / 2025, p. 194 / 195

Images