Terminal device and terminal device method

Abstract

A terminal device (10) comprises: a control unit (110) configured so that, when an uplink grant corresponding to an uplink transmission including a delay information report is considered as a non-priority uplink grant on the basis of a priority process, the control unit (110) determines that autonomous uplink transmission is to be performed on a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generates information for the autonomous uplink transmission; and a communication unit (120) configured to perform the autonomous uplink transmission to a base station device (20).

Description

Terminal device and terminal device method CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

[0003] In recent years, technological development related to extended reality (XR) has progressed. XR is a concept that includes multimedia integration technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and substitutional reality (SR). In XR, three-dimensional time-series image data in real space and / or virtual space, audio data of multiple channels (stereo, 5.1ch, etc.), other data presented to the user, control data, etc. are transmitted and received in parallel. XR requires low latency and high reliability to maintain and improve the quality of the user's experience.

[0004] In Non-Patent Document 1, implementation of XR in 5G NR (Fifth Generation New Radio), which is a wireless specification defined by the Third Generation Partnership Project (3GPP (registered trademark)), is being considered.

[0005] 3GPP TR 38.838 V17.0.0 (2021-12)3GPP TS 38.321 V17.2.0 (2022-09)

[0006] XR is expected to be operated under various requirements, including a requirement for low latency. Accordingly, with regard to uplink communication from a terminal device, a base station device is required to allocate radio resources taking into consideration the above requirements. In order to allocate such radio resources, it is being considered that the terminal device makes a predetermined report (e.g., a report of information related to delay) to the base station device. Hereinafter, "information related to delay" will be referred to as "delay information." Furthermore, a "report including delay information" will be referred to as a "delay information report."

[0007] On the other hand, Non-Patent Document 2 describes intra-UE priority processing. However, Non-Patent Document 2 does not describe a procedure for transmitting a delay information report when the above priority processing is performed. In this regard, the inventor has discovered a problem that when the above priority processing is performed, the terminal device may transmit a delay information report containing inappropriate information. Note that the above problem also occurs in ordinary terminal devices and base station devices other than those implementing XR.

[0008] The present disclosure provides a technique that can prevent a terminal device from transmitting a delay information report that includes inappropriate information.

[0009] The terminal device of the present disclosure includes a control unit configured to, when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, determine to perform autonomous uplink transmission using a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generate information for the autonomous uplink transmission, and a communication unit configured to perform the autonomous uplink transmission to a base station device.

[0010] Furthermore, the method of the terminal device in the present disclosure includes, when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, determining to perform autonomous uplink transmission on a second resource scheduled after a first resource on which the uplink transmission is scheduled, generating information for the autonomous uplink transmission, and performing the autonomous uplink transmission to a base station device.

[0011] According to the above configuration, it is possible to prevent the terminal device from transmitting a delay information report including inappropriate information. Note that the above configuration may achieve other effects instead of or in addition to the above effect.

[0012] The above and other objects, features, and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which Fig. 1 is a diagram illustrating a communication system S according to a first embodiment, Fig. 2 is a diagram illustrating a U-plane protocol stack according to the first embodiment, Fig. 3 is a diagram illustrating a C-plane protocol stack according to the first embodiment, Fig. 4 is a block diagram illustrating a schematic hardware configuration of a terminal device 10 according to the first embodiment, Fig. 5 is a block diagram illustrating a schematic functional configuration of the terminal device 10 according to the first embodiment, Fig. 6 is a block diagram illustrating a schematic hardware configuration of a base station device 20 according to the first embodiment, Fig. 7 is a block diagram illustrating a schematic functional configuration of the base station device 20 according to the first embodiment, Fig. 8 is a diagram illustrating a radio frame configuration according to the first embodiment, Fig. 9 is a diagram illustrating a configuration of a short BSR, Fig. 10 is a diagram illustrating a configuration of a long BSR, and Fig. 11 is a diagram illustrating a MAC (Medium Access Control) frame. FIG. 12 is a diagram for explaining priority processing in the MAC layer, FIG. 13 is a sequence diagram showing the flow of processing of the terminal device 10 and the base station device 20 according to the first embodiment, FIG. 14 is a diagram showing an example of the configuration of a long BSR including delay information, FIG. 15 is a diagram showing another example of the configuration of a long BSR including delay information, FIG. 16 is a diagram showing another example of the configuration of a long BSR including delay information, and FIG. 17 is a diagram for explaining autonomous transmission processing of the terminal device 10. 18 is a diagram showing the processing flow for transmitting a delay information report according to the first embodiment, FIG. 19 is a sequence diagram showing the processing flow of the terminal device 10 and the base station device 20 according to the second embodiment, FIG. 20 is a diagram for explaining the situation for transmitting a delay information report according to the third embodiment, FIG. 21 is a flowchart showing the processing flow for transmitting a delay information report according to the third embodiment, FIG. 22 is a flowchart showing another aspect of the processing flow for transmitting a delay information report according to the third embodiment, and FIG. 23 is a diagram for explaining another aspect of the processing flow for transmitting a delay information report according to the third embodiment.

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

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

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

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

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

[0018] The terminal device 10 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a laptop PC, a communication module, a communication card, or an IoT device such as a surveillance camera or a robot. The terminal device 10 may be a vehicle (e.g., a car, a train, etc.) or a device provided therein. The terminal device 10 may be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device provided therein. The terminal device 10 may be a sensor or a device provided therein. Note that the terminal device 10 may be called by other names such as a terminal, a mobile station, a mobile terminal, a mobile device, a mobile unit, a subscriber station, a subscriber terminal, a subscriber device, a subscriber unit, a wireless station, a wireless terminal, a wireless device, a wireless unit, a remote station, a remote terminal, a remote device, or a remote unit. The terminal device 10 may be a device adapted to one or more of enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC).

[0019] The base station device 20 manages at least one cell. A cell constitutes the smallest unit of a communication area. For example, one cell belongs to one frequency (e.g., carrier frequency) and is composed of one component carrier. The term "cell" can refer to wireless communication resources and can also refer to a communication target of the terminal device 10. The base station device 20 wirelessly communicates with the terminal device 10 located in its own cell in the U-plane and C-plane. In other words, the base station device 20 terminates the U-plane protocol and C-plane protocol for the terminal device 10.

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

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

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

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

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

[0025] Each base station device 20 is connected to the core network 30 via a predetermined interface (for example, an NG interface). More specifically, for example, each base station device 20 is connected to the UPF of the core network 30 via an NG-U interface in the U-plane, and is connected to the AMF of the core network 30 via an NG-C interface in the C-plane. Note that each base station device 20 may be connected to the core network 30 via another interface with a different function or name.

[0026] The radio protocol architecture between the terminal device 10 and the base station device 20 will be described with reference to Fig. 2. The radio protocol architecture between the terminal device 10 and the base station device 20 and between the terminal device 10 and the core network 30 will be described with reference to Fig. 3.

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

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

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

[0030] The processor 101 is a computing element that realizes various functions of the terminal device 10. The processor 101 may be a system-on-a-chip (SoC) that includes elements such as a central processing unit (CPU), a graphics processing unit (GPU), and a memory controller.

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

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

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

[0034] 5, the terminal device 10 has, as functional blocks, a control unit 110 and a communication unit 120. The communication unit 120 has at least one transmission unit 121 and at least one reception unit 122.

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

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

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

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

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

[0040] The memory 202 is configured by at least one storage medium such as a read-only memory (ROM), a RAM, a hard disk drive (HDD), or a solid state drive (SSD). The memory 202 is an element that temporarily or permanently stores programs and data used to execute various processes in the base station device 20. The programs include one or more instructions for operating the base station device 20. The processor 201 implements the functions of the base station device 20 by expanding and executing the programs stored in the memory 202 in the memory 202 and / or a system memory (not shown).

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

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

[0043] 7, the base station device 20 has, as functional blocks, a control unit 210, a communication unit 220, and a network communication unit 230. The communication unit 220 has at least one transmission unit 221 and at least one reception unit 222.

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

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

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

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

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

[0049] The transmission method for downlink communication from the base station device 20 to the terminal device 10 is, for example, Orthogonal Frequency Division Multiplexing (OFDM) using a cyclic prefix (CP), i.e., CP-OFDM. The transmission method for uplink communication from the terminal device 10 to the base station device 20 is, for example, the above-mentioned CP-OFDM or DFTS-OFDM in which CP-OFDM is applied after transform precoding that performs discrete Fourier transform (DFT) spreading.

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

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

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

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

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

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

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

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

[0058] Each radio frame is assigned a system frame number (SFN), which counts up by one from 0 to 1023. SFN "0" corresponds to the initial value of the SFN, and SFN "1023" corresponds to the maximum value of the SFN. Therefore, the radio frame following a radio frame assigned SFN 1023 is assigned SFN 0. Since the time length of a radio frame is 10 ms, the time length of one cycle of the system frame number is 10,240 ms (= 10.24 seconds).

[0059] Here, the base station device 20 may configure one or more serving cells for the terminal device 10. The serving cell may correspond to a component carrier in the downlink and / or a component carrier in the uplink. The technology in which one or more serving cells are configured and the base station device 20 and the terminal device 10 perform wireless communication may also be referred to as carrier aggregation.

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

[0061] 1.3 Channels and Control Information The terminal device 10 and the base station device 20 transmit and receive user data and control information to and from each other. The transmission and reception of control information in the downlink and uplink will be exemplified below.

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

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

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

[0065] The base station device 20 transmits downlink control information (DCI) to the terminal device 10 using the PDCCH, which is a physical channel. The DCI includes information on downlink and uplink resource allocation for the terminal device 10, and control information for the terminal device 10. The DCI is mapped to the PDCCH and corresponds to Layer 1 signaling.

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

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

[0068] Here, a Cyclic Redundancy Check (CRC) scrambled with a Radio Network Temporary Identifier (RNTI) may be added to the DCI (or DCI format) transmitted on the PDCCH. The CRC may also be referred to as a CRC parity bit. Multiple types of RNTI are defined. For example, the base station device 20 may set each RNTI by transmitting an RRC message including at least one of information indicating a C-RNTI (Cell-RNTI), information indicating a Modulation and Coding Scheme Cell-RNTI (MCS-C-RNTI), and information indicating a Configured Scheduling-RNTI (CS-RNTI). That is, a CRC scrambled with at least one of the C-RNTI, MCS-C-RNTI, and CS-RNTI may be added to the DCI (or DCI format) transmitted on the PDCCH.

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

[0070] The terminal device 10 transmits uplink control information (UCI) to the base station device 20 using the PUCCH, which is a physical channel. The UCI includes control information such as a scheduling request (SR), a hybrid automatic repeat reQuest (HARQ) ACK / NACK, and channel state information (CSI). The UCI is mapped to the PUCCH or PUSCH and corresponds to layer 1 signaling.

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

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

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

[0074] The base station device 20 transmits control information in the RRC layer to the terminal device 10 using a signaling radio bearer (SRB) established between the terminal device 10 and the base station device 20 in the RRC layer. Hereinafter, messages exchanged between the base station device 20 and the terminal device 10 in the RRC layer may be referred to as RRC messages. There are multiple types of SRBs (e.g., SRB0, SRB1, SRB2, SRB3, SRB4). The SRBs are used to transmit and receive RRC messages as well as NAS messages containing control information in the NAS layer. The CCCH or DCCH is used to transmit RRC messages from the base station device 20 to the terminal device 10. The CCCH and DCCH are each mapped to the PDSCH via the DL-SCH. The RRC message corresponds to Layer 3 signaling.

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

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

[0077] As an example of an uplink RRC message, a user equipment capability information (UECapabilityInformation) message will be described. The user equipment capability information message is an RRC message transmitted from the terminal device 10 to the base station device 20 using SRB1. The DCCH is used to transmit the user equipment capability information message. The user equipment capability information message is used to notify the base station device 20 of information related to the radio access capability of the terminal device 10.

[0078] As an example of an uplink RRC message, a user equipment assistance information (UE Assistance Information) message will be described. The user equipment assistance information message is an RRC message transmitted from the terminal device 10 to the base station device 20 using SRB1 or SRB3. The DCCH is used to transmit the user equipment assistance information message. The user equipment assistance information message is used to notify the base station device 20 of various information related to the terminal device 10 (UE assistance information).

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

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

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

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

[0083] 1.5 Hybrid Automatic Repeat Request (HARQ) HARQ is a mechanism for controlling error correction and retransmission requests. When a receiver detects an error in data received from a sender, it requests the sender to retransmit the data. The receiver then combines the previously received data with the retransmitted data to obtain the data.

[0084] HARQ is a SAW (Stop-And-Wait) protocol. When the receiving side correctly receives data, the receiving side sends an acknowledgement (Ack) to the transmitting side. When the transmitting side receives the Ack, it sends the next data. In this way, with HARQ, the transmitting side cannot send the next data until the receiving side has completed receiving the data.

[0085] The following describes the case where a transmission opportunity for PUSCH is set by the CG.

[0086] The base station device 20 may transmit an RRC message including parameters related to the PUSCH to the terminal device 10. The parameters related to the PUSCH are included in a PUSCH-ServingCellConfig IE, which is an example of an RRC information element (IE).

[0087] The HARQ entity in the terminal device 10 can have one or more HARQ processes. For uplink transmission, the terminal device 10 supports up to 16 or 32 HARQ processes per cell. The number of HARQ processes is configured by nrofHARQ-ProcessesForPUSCH included in the parameters for PUSCH (i.e., PUSCH-ServingCellConfig IE). If nrofHARQ-ProcessesForPUSCH is not present in the PUSCH-ServingCellConfig IE, the number of HARQ processes is set to 16 by default.

[0088] For uplink transmission, each HARQ process supports one Transport Block (TB), i.e., one TB is transmitted in one transmission opportunity. Also, one HARQ process identifier is associated with (or assigned to) one HARQ process. Hereinafter, the HARQ process identifier will be referred to as "HPI."

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

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

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

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

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

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

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

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

[0097] The first part 910 is made up of three bits. The first part 910 is information for identifying the LCG for which the buffer status is reported. The first part 910 is sometimes referred to as an "LCG ID field."

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

[0099] The short BSR may include a Truncated format, which is a format for a logical channel with a high priority (i.e., LCH priority, which will be described later), and an Extended format, which is a format that can transmit a larger amount of information.

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

[0101] The LCG field 1010 is composed of 8 bits. In the LCG field 1010, the 8 bits correspond to 8 LCGi, respectively. Here, i is an integer from 0 to 7. The definition of i will remain the same in the following description. The LCG field 1010 may indicate whether a buffer size field for LCGi exists. For example, if the value of LCGi in the LCG field 1010 is 1, this indicates that a buffer size field corresponding to LCGi exists. If the value of LCGi is 0, this indicates that a buffer size field corresponding to LCGi does not exist.

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

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

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

[0105] The BSR may also include a Pre-emptive BSR format and an Extended Pre-emptive BSR format, which are used in the IAB-MT.

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

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

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

[0109] 1.7 LCP (Logical Channel Prioritization) Procedure The terminal device 10 generates a MAC PDU for uplink transmission in accordance with an uplink grant from the base station device 20. The terminal device 10 multiplexes data from different LCHs to generate a MAC PDU. At this time, the terminal device 10 generates a MAC PDU in accordance with the LCP procedure. The LCP procedure is a process for multiplexing data from different LCHs. The LCP procedure may be the procedure described in Section 5.4.3.1 of Non-Patent Document 2.

[0110] For example, the base station device 20 may transmit an RRC message including a LogicalChannelConfig IE. Furthermore, the terminal device 10 may generate a MAC PDU based on the LogicalChannelConfig IE included in the RRC message. The LogicalChannelConfig IE may include the following parameters: priority: a value ranging from 1 to 16, representing the priority. The smaller the value, the higher the priority. Hereinafter, this priority will be referred to as "LCH priority" to distinguish it from other priorities (e.g., PHY priority). prioritizedBitRate (PBR): represents the minimum guaranteed bit rate. bucketSizeDuration (BSD): represents the bucket size duration. The bucket size is determined by PBR x BSD.

[0111] For example, the terminal device 10 may perform the LCP procedure as follows to generate a MAC PDU. The terminal device 10 allocates the amount of data guaranteed by the PBR of each LCH to resources in the MAC PDU in order of LCH priority. If there are still available resources in the MAC PDU after the data guaranteed by the PBR for all LCHs has been allocated, the terminal device 10 allocates the available resources in the MAC PDU to the data of the LCHs in order of LCH priority. The terminal device 10 performs the above procedure until all LCH data is exhausted or the available resources in the MAC PDU are exhausted.

[0112] In the LCP procedure, a MAC CE basically has priority over data from an LCH. Therefore, the terminal device 10 may allocate a MAC CE to a resource in a MAC PDU before allocating data from an LCH. However, a certain type of MAC CE may not have priority over data from an LCH. For example, the priority of a padding BSR may be lower than the priority of data from an LCH.

[0113] Furthermore, in the LCP procedure, the base station apparatus 20 can set a mapping restriction for the terminal apparatus 10. The mapping restriction may be the restriction described in section 5.4.3.1 of Non-Patent Document 2. The MAC entity of the terminal apparatus 10 may select LCH data to be allocated to resources in the MAC PDU in accordance with the mapping restriction.

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

[0115] For example, when the allowedCG-List is set for a certain LCH, the terminal device 10 can map data of the LCH only to MAC PDUs corresponding to CGs included in the allowedCG-List.

[0116] 1.8 Intra-UE Prioritization Processing When multiple uplink transmissions with different delay and / or reliability requirements overlap on time resources, the terminal device 10 may transmit uplink transmissions with higher priority and stop (or cancel) uplink transmissions with lower priority. Such processing is referred to as intra-UE prioritization processing. The intra-UE priority processing may include processing at the MAC layer and processing at the PHY layer. Hereinafter, processing at the MAC layer is referred to as "MAC layer prioritization processing" or "first priority processing," and processing at the PHY layer is referred to as "PHY layer prioritization processing" or "second priority processing."

[0117] 1.8.1 MAC Layer Priority Processing The base station device 20 may transmit a setting for enabling MAC layer priority processing (i.e., first priority processing) to the terminal device 10. For example, the setting may be set for a MAC cell group. The setting may be set in an IE related to the MAC cell group included in an RRC message. An example of such an IE is the MAC-CellGroupConfig IE. The setting may be lch-BasedPrioritization included in the MAC-CellGroupConfig IE. The lch-BasedPrioritization indicates that first priority processing based on LCH priority is performed.

[0118] If LCH-BasedPrioritization is present in the MAC-CellGroupConfig IE, the MAC entity of the terminal device 10 may perform a first priority process among multiple uplink transmissions that overlap on time resources. The terminal device 10 may determine a final priority for each uplink transmission based on the LCH priority. Hereinafter, the final priority is referred to as "transmission priority."

[0119] For example, when the MAC PDU to be transmitted is already stored in the HARQ buffer, the terminal device 10 determines the transmission priority based on the highest LCH priority among the LCH priorities corresponding to the LCH data multiplexed in the MAC PDU, according to the mapping restriction. When the MAC PDU to be transmitted is not yet stored in the HARQ buffer, the terminal device 10 determines the transmission priority based on the highest LCH priority among the LCH priorities corresponding to the LCH data that can be multiplexed in the MAC PDU, according to the mapping restriction. Furthermore, the transmission priority of the SR is the LCH priority of the LCH that triggered the SR.

[0120] As shown in Figure 11, when data 1 corresponding to LCH1 and data 2 corresponding to LCH2 are multiplexed, the transmission priority of MAC PDU 1101 including data 1 and data 2 is 3. Furthermore, the transmission priority of MAC PDU 1102 including data 3 corresponding to LCH3 is 1. In the example of Figure 11, MAC PDU 1101 corresponds to DG-based uplink transmission (i.e., DG PUSCH). DG PUSCH is, for example, PUSCH and / or PUSCH transmission scheduled using DCI (DCI format) to which CRC (CRC parity bits) scrambled by C-RNTI and / or MCS-C-RNTI is added. MAC PDU 1102 corresponds to CG-based uplink transmission (i.e., CG PUSCH). The CG PUSCH is, for example, a PUSCH and / or PUSCH transmission configured and / or indicated based on an information element (e.g., a ConfiguredGrantConfig IE) included in an RRC message. Also, for example, the CG PUSCH may be activated and / or deactivated using a DCI to which a CRC scrambled by the CS-RNTI is attached.

[0121] The terminal device 10 compares the transmission priority of the MAC PDU 1101 with the transmission priority of the MAC PDU 1102. The transmission priority (=1) of the MAC PDU 1102 is higher than the transmission priority (=3) of the MAC PDU 1101. Therefore, the terminal device 10 may prioritize the CG PUSCH and cancel the DG PUSCH.

[0122] Hereinafter, an uplink grant prioritized based on the transmission priority as described above is referred to as a "prioritized uplink grant." Also, an uplink grant not prioritized based on the transmission priority as described above is referred to as a "de-prioritized uplink grant."

[0123] Here, "priority / non-priority of transmission" may be determined based on "priority / non-priority of uplink grant". For example, "priority of transmission" may be determined based on "prioritized uplink grant". Also, "non-priority of transmission" may be determined based on "non-prioritized uplink grant". For example, "priority / non-priority of MAC PDU transmission" may be determined based on "priority / non-priority of uplink grant".

[0124] Although the case where CG-based uplink transmission and DG-based uplink transmission overlap on time resources has been described above, the terminal device 10 may also perform the same processing as above when multiple CG-based uplink transmissions overlap on time resources.Furthermore, the terminal device 10 may also perform the same processing as above when PUCCH transmission for SR and UL-SCH transmission overlap on time resources.

[0125] Note that the transmission priority of an uplink grant-based uplink transmission corresponding to a MAC PDU in which data from an LCH is not multiplexed may be lower than the transmission priority of an uplink grant-based uplink transmission corresponding to a MAC PDU in which data from an LCH is multiplexed or an SR triggered by an LCH.

[0126] On the other hand, if the transmission priorities are the same or if lch-BasedPrioritization is not present in the MAC-CellGroupConfig IE, the terminal device 10 may perform a first priority process between uplink transmissions that overlap on time resources as follows: If a CG-based uplink transmission and a DG-based uplink transmission overlap on time resources, the terminal device 10 may prioritize the DG-based uplink transmission. If multiple CG-based uplink transmissions overlap on time resources, the terminal device 10 may determine a prioritized uplink transmission according to the implementation of the terminal device 10. If a PUCCH transmission for SR and a UL-SCH transmission overlap on time resources, the terminal device 10 may prioritize the UL-SCH transmission.

[0127] The terminal device 10 may perform the first priority process in accordance with the contents described in Section 5.4.1 of Non-Patent Document 2. For example, the terminal device 10 may perform the first priority process for a CG as follows. When lch-BasedPrioritization is present in the MAC-CellGroupConfig IE, the MAC entity of the terminal device 10 may determine whether all of the following conditions (b1) to (b3) are satisfied for an uplink grant that is delivered to a HARQ entity and for which an associated PUSCH can be transmitted by a lower layer: (b1) There is no overlap with the PUSCH duration of another CG that has not yet been de-prioritized and has a higher LCH priority in the same BWP. (b2) In the same BWP, there is no overlap with the PUSCH duration of an uplink grant scrambled with a C-RNTI or a CS-RNTI with NDI = 1 that has not yet been made non-prioritized and has a higher or equal LCH priority. (b3) There is no overlap with the PUSCH duration with an SR transmission triggered by an LCH with a higher LCH priority that has not yet been made non-prioritized and where simultaneous transmission of SR and uplink grant is not allowed.

[0128] The terminal device 10 may regard a CG that satisfies the above conditions (b1) to (b3) as a “prioritized uplink grant.” The terminal device 10 may regard an uplink grant that overlaps with the CG as a “non-prioritized uplink grant.”

[0129] In another example, when Cell-Based Prioritization is present in the MAC-CellGroupConfig IE and a PUSCH transmission corresponding to a CG is canceled by a CI-RNTI (Cancellation Indication RNTI) or canceled by a PUCSH transmission with a high PHY priority, the terminal device 10 may regard the CG as a "non-priority uplink grant." Cancellation of uplink transmission using a CI-RNTI will be described later.

[0130] 1.8.2 PHY Layer Priority Processing The terminal device 10 may perform PHY layer priority processing (i.e., second priority processing) between uplink transmissions that overlap on time resources based on the PHY priority.

[0131] The PHY priority may be expressed by either a value of p0 or p1. In this configuration, the priority of p1 is higher than the priority of p0. The base station device 20 transmits information related to the PHY priority to the terminal device 10.

[0132] For example, in the case of a CG, the base station device 20 may transmit an RRC message including a PHY priority to the terminal device 10. The PHY priority may be included in an IE (e.g., a ConfiguredGrantConfig IE) related to the CG included in the RRC message.

[0133] In the case of SR, the base station device 20 may transmit an RRC message including PHY priority to the terminal device 10. The PHY priority may be included in an IE (for example, a SchedulingRequestResourceConfig IE) related to SR included in the RRC message.

[0134] Furthermore, in order to determine between the uplink transmission and the UCI for the downlink transmission, the base station device 20 may transmit a DCI format including a PHY priority to the terminal device 10. Specifically, the PHY priority may be included in the DCI format that schedules the uplink transmission.

[0135] When multiple overlapping uplink transmissions are scheduled on a time resource, the terminal device 10 may prioritize uplink transmissions with a higher PHY priority (i.e., p1) and cancel uplink transmissions with a lower PHY priority (i.e., P0).

[0136] When uplink transmissions having the same PHY priority overlap on time resources, the terminal device 10 may perform a second priority process as follows. For example, when CG-based uplink transmission and DG-based uplink transmission overlap on time resources, the terminal device 10 may prioritize the DG-based uplink transmission. When PUCCH transmission and PUSCH transmission overlap on time resources, the terminal device 10 may multiplex the PUCCH into the PUSCH.

[0137] 1.9 Inter-UE Prioritization Processing When multiple uplink transmissions by different terminal devices 10 overlap in time resources, the base station device 20 may stop (or cancel) the uplink transmission by the terminal device 10 with a lower priority. Such processing is called inter-UE priority processing.

[0138] The base station device 20 transmits DCI format 2_4 scrambled with the CI-RNTI to the terminal device 10. This enables the base station device 20 to instruct the terminal device 10, which has a low priority, to cancel uplink transmission.

[0139] 1.10. Autonomous Uplink Transmission Processing When the uplink grant is a CG and the uplink grant is deemed to be non-priority by the priority processing within the terminal, the terminal device 10 may perform autonomous uplink transmission processing.

[0140] The base station device 20 may transmit a configuration for enabling the autonomous uplink transmission process to the terminal device 10. For example, the configuration may be included in an IE related to a CG included in an RRC message. The configuration may also be autonomousTx included in a ConfiguredGrantConfig IE.

[0141] For example, the base station device 20 transmits an RRC message including autonomousTx to the terminal device 10. If the uplink grant that is deemed non-prioritized by the priority processing within the terminal is a CG for which autonomousTx is set, the terminal device 10 performs autonomous uplink transmission processing.

[0142] 12, multiple resources (i.e., multiple transmission opportunities) 1201-1, 1201-2, ..., 1201-n are scheduled for CG-based uplink transmissions (i.e., CG PUSCH). Additionally, a resource 1202 is scheduled for DG-based uplink transmissions (i.e., DG PUSCH).

[0143] Here, it is assumed that the resource 1201-1 for the CG PUSCH and the resource 1202 for the DG PUSCH overlap in terms of time resources. The terminal device 10 regards the uplink grant corresponding to the CG PUSCH using the resource 1201-1 as a "non-priority uplink grant" through priority processing within the terminal. Furthermore, the uplink grant is a CG for which autonomousTx is configured. The HPI associated with the CG PUSCH using the resource 1201-1 is #0.

[0144] The terminal device 10 prioritizes the DG PUSCH using resource 1202 and cancels the CG PUSCH using resource 1201-1. Then, the terminal device 10 performs autonomous transmission processing of the MAC PDU corresponding to the canceled CG PUSCH. The terminal device 10 transmits the MAC PDU corresponding to the canceled CG PUSCH as a new uplink transmission using the next resource (i.e., CG resource) 1201-n associated with the same HPI (=#0) as the HPI associated with the canceled CG PUSCH. That is, in a CG for which autonomousTx is configured, the HARQ entity may consider that the MAC PDU has been acquired if the previous CG of the HARQ process was not prioritized and PUSCH transmission of the acquired MAC PDU was not performed.

[0145] It should be noted that in the above case, the configuredGrantTimer and cg-RetransmissionTimer associated with the HARQ process of the uplink grant considered as non-priority are stopped if they are running.

[0146] 1.11. Extended Reality (XR) This section describes the characteristics of traffic generated in XR. In XR, multiple types of data (video data, audio data, user data, control data, etc.) are transmitted and received in parallel. The multiple data streams corresponding to the above data each have different traffic characteristics and quality of service (QoS) requirements.

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

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

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

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

[0151] 1.12. Delay Information Report 1.12.1. Basic Configuration of Delay Information Report XR is expected to be operated under various requirements, including a requirement for low latency. Accordingly, with regard to uplink communication from a terminal device, a base station device is required to allocate radio resources taking into consideration the above requirements. To allocate such radio resources, the terminal device 10 transmits a delay information report including delay information for predetermined data to the base station device 20. Note that the delay information report may also be referred to as a "delay status report."

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

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

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

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

[0156] The delay information may include one or both of information that explicitly indicates a delay and information that implicitly indicates a delay.

[0157] - Information explicitly indicating a delay For example, the delay information may be a delay time or an index representing a delay time. The delay information may be the remaining time until a predetermined first deadline is reached. The remaining time may be a deadline calculated based on a predetermined timer. For example, the predetermined timer may be a PDCP discard timer. In this configuration, the delay information may be the remaining time calculated based on the PDCP discard timer. The terminal device 10 may calculate the remaining time based on the PDCP discard timer, taking the time of initial transmission of the delay information report as the reference. The delay information may include information about multiple remaining times. In another example, the delay information may be information about the shortest remaining time among multiple remaining times.

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

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

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

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

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

[0163] As shown in FIG. 13 , the communication unit 220 of the base station device 20 transmits an RRC message to the terminal device 10 (S1301). The RRC message includes parameters related to a BSR. The RRC message may be an RRC Reconfiguration message. The control unit 110 of the terminal device 10 generates a BSR based on the parameters included in the RRC message. The BSR includes buffer size information related to the buffer size and delay information. The communication unit 120 of the terminal device 10 transmits a BSR including a delay information report (S1302). The control unit 210 of the base station device 20 allocates radio resources to the terminal device 10 based on the delay information report.

[0164] The terminal device 10 may transmit a long BSR 1400 shown in FIG. 14. The long BSR 1400 includes a first field 1410 and a second field 1420.

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

[0166] In this example, the second field 1420 includes three fields 1421-1423.

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

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

[0169] The second portion 1421b represents delay information (e.g., the remaining time) related to the data corresponding to LCG1. The second portion 1421b may be an index representing the delay information. The control unit 110 may refer to a 2-bit delay information table to set the index in the second portion 1421b. The delay information table defines the correspondence between the delay information and the index.

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

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

[0172] In the above example, the second field 1420 includes three fields 1421 to 1423, but is not limited to this configuration. The number of fields included in the second field 1420 may be variable. In another example, the order of the fields included in the second field 1420 may be determined based on the LCH priority.

[0173] In another example, the Long BSR 1400 may include a third field indicating whether to include delay information for each LCG. For example, in the third field, if the value of LCGi is 1, this may indicate that delay information for LCGi is included. If the value of LCGi is 0, this may indicate that delay information for LCGi is not included.

[0174] In yet another example, the first portion 1421a of field 1421 and the first portion 1422a of field 1422 may each contain information regarding the size of the second data. The second data may be data whose remaining time is equal to or less than the first threshold value Th1. For example, the first portion 1421a of field 1421 may contain information regarding the size of the second data corresponding to LCG1. Similarly, the first portion 1422a of field 1422 may contain information regarding the size of the second data corresponding to LCG2.

[0175] As shown in Fig. 15, each of fields 1421 to 1423 included in second field 1420 may include a first portion corresponding to information related to buffer size and a second portion corresponding to delay information. In the following, only the portions different from the configuration in Fig. 14 will be described, and a description of the portions that are the same as the configuration in Fig. 14 will be omitted.

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

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

[0178] Although the configuration of the long BSR has been described in the above example, the present invention is not limited to this example. The above configuration may also be applied to a short BSR. For example, the terminal device 10 may transmit a short BSR including delay information.

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

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

[0181] The first setting information may be "information indicating whether or not to transmit delay information." The first setting information may indicate "to transmit delay information" or "not to transmit delay information." The first setting information may be a flag indicating "to transmit delay information" or "not to transmit delay information." Note that the first setting information may be "information indicating whether or not to transmit remaining time." Furthermore, the first setting information may be "information indicating whether or not to transmit information regarding the size of the second data."

[0182] For example, the terminal device 10 may transmit a delay information report when the RRC message includes the first setting information, or may not transmit a delay information report when the RRC message does not include the first setting information.

[0183] The first configuration information may be configured for an LCH. The terminal device 10 may determine whether or not to include delay information for the LCH in the BSR based on the first configuration information configured for the LCH. For example, if the first configuration information indicates that delay information is to be transmitted for a certain LCH, the terminal device 10 may include the delay information for the LCH in the BSR. For example, the first configuration information may be configured as a new element of the LogicalChannelConfig IE. The first configuration information may be configured for an LCG. The terminal device 10 may determine whether or not to include delay information for the LCG in the BSR based on the first configuration information configured for the LCG. For example, if the first configuration information indicates that delay information is to be transmitted for a certain LCG, the terminal device 10 may include the delay information for the LCG in the BSR. For example, the first configuration information may be configured as a new element of the LogicalChannelGroup IE. The first configuration information may be configured for a PDU or a PDU set. The terminal device 10 may determine whether or not to include delay information for the PDU or PDU set in the BSR based on the first configuration information configured for the PDU or PDU set. For example, when the first configuration information indicates that delay information is to be transmitted for a certain PDU or PDU set, the terminal device 10 may include the delay information for the PDU or PDU set in the BSR. The first configuration information may be set in an IE associated with a PDU or PDU set included in the RRC message. The first configuration information may be set for a data burst. The terminal device 10 may determine whether to include the delay information for the data burst in the BSR based on the first configuration information set for the data burst. For example, when the first configuration information indicates that delay information is to be transmitted for a certain data burst, the terminal device 10 may include the delay information for the data burst in the BSR. The first configuration information may be set in an IE associated with a data burst included in the RRC message.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0197] 1.12.3. Conditions for Triggering Delay Information Reporting The terminal device 10 may trigger a delay information report according to a predetermined condition. Hereinafter, the condition is referred to as a "trigger condition." The trigger condition may include at least one of the above conditions (a1) to (a4).

[0198] Furthermore, the trigger condition may include at least one of the following conditions (c1) to (c4): (c1) There is data whose remaining time is equal to or less than a first threshold Th1; (c2) An on-duration of discontinuous reception (DRX) has started; (c3) There is a PDU set or a data burst to be transmitted, or a PDU set or a data burst has been buffered; or (c4) A PDU set has been discarded.

[0199] 1.13. Autonomous Transmission Process of Delay Information Report Figure 17 shows a situation similar to that of Figure 12. In Figure 17, it is assumed that the MAC PDU corresponding to the CG PUSCH using resource 1201-1 includes a delay information report. For example, the delay information included in the delay information report is the remaining time described above. The terminal device 10 calculates the remaining time 1701 based on the initial transmission time t1.

[0200] The terminal device 10 regards the uplink grant corresponding to the CG PUSCH using the resource 1201-1 as a "non-priority uplink grant" through priority processing within the terminal. The terminal device 10 cancels the CG PUSCH using the resource 1201-1. The above uplink grant is a CG for which autonomousTx is set. Therefore, the terminal device 10 executes autonomous transmission processing in the same manner as in FIG. 12. The terminal device 10 transmits the MAC PDU corresponding to the above canceled CG PUSCH as a new uplink transmission using the next resource 1201-n associated with the same HPI (=#0) as the resource 1201-1.

[0201] However, the actual remaining time 1702 at time t2 when the base station device 20 receives the new uplink transmission is different from the remaining time 1701 calculated at time t1, which may cause the base station device 20 to be unable to accurately recognize the remaining time.

[0202] In order to solve the above problem, when an uplink grant corresponding to an uplink transmission including a delay information report is deemed to be a "non-priority uplink grant" based on priority processing within the terminal, the terminal device 10 may execute the following processing. Here, the uplink grant deemed to be non-priority is a CG for which autonomous transmission processing is set (i.e., a CG for which autonomousTx is set).

[0203] The terminal device 10 determines to perform autonomous uplink transmission using a second resource scheduled after the first resource for which the uplink transmission is scheduled. The first resource may be referred to as a "first CG resource," and the second resource may be referred to as a "second CG resource." The second resource may be a next resource associated with the same HPI as the first resource. Then, the terminal device 10 generates information (or data) for the autonomous uplink transmission.

[0204] At least a part of the MAC PDU for the autonomous uplink transmission is different from the MAC PDU that was not transmitted using the first resource. The terminal device 10 may generate the MAC PDU for the autonomous uplink transmission by modifying at least a part of the MAC PDU that was not transmitted using the first resource.

[0205] For example, the information generated for the autonomous uplink transmission may be a part or the whole of the MAC CE. The terminal device 10 may generate the MAC CE for the autonomous uplink transmission by changing at least a part of the MAC CE that was not transmitted using the first resource.

[0206] Note that the time (or duration) of the first resource (i.e., the first CG resource) may be represented by one or a combination of two or more of the SFN, subframe, slot, and symbol (e.g., the first symbol position and / or the last symbol position) of the uplink transmission (i.e., the PUSCH transmission) corresponding to the uplink grant. Furthermore, the time (or duration) of the second resource (i.e., the second CG resource) may be referred to as the "autonomously retransmitted time (or duration)." Similarly to the above, the time (or duration) of the second resource may be represented by one or a combination of two or more of the SFN, subframe, slot, and symbol (e.g., the first symbol position and / or the last symbol position) of the uplink transmission (i.e., the PUSCH transmission) corresponding to the uplink grant.

[0207] Hereinafter, details of each of aspects 1-1 to 1-3 for generating information for autonomous uplink transmission will be described.

[0208] - Aspect 1-1 The control unit 110 of the terminal device 10 regenerates the delay information report as information for the autonomous uplink transmission described above.

[0209] Figure 18 shows a similar situation to Figure 17. In the example of Figure 18, resource 1201-1 is referred to as "first resource 1201-1" and resource 1201-n is referred to as "second resource 1201-n."

[0210] The control unit 110 of the terminal device 10 calculates the remaining time using time t1 (i.e., the time of initial transmission) of the first resource 1201-1 as a reference. For example, as described above, the remaining time may be a value calculated based on a predetermined timer (e.g., a PDCP discard timer) using time t1 as a reference. The control unit 110 generates a delay information report including the remaining time. Furthermore, the control unit 110 performs priority processing within the terminal (1801). Through the priority processing within the terminal, the control unit 110 regards the uplink grant corresponding to the CG PUSCH using the first resource 1201-1 as a "non-priority uplink grant." The control unit 110 determines to perform autonomous uplink transmission using the second resource 1201-n associated with the same HPI as the first resource 1201-1.

[0211] Next, the control unit 110 generates information for autonomous uplink transmission. Specifically, the control unit 110 recalculates the remaining time based on time t2 of the second resource 1201-n. The control unit 110 generates a delay information report including the recalculated remaining time. The communication unit 120 transmits the delay information report via the CG PUSCH using the second resource 1201-n (1802).

[0212] The above configuration can prevent the terminal device 10 from transmitting a delay information report that includes inappropriate information (e.g., the remaining time). Specifically, the terminal device 10 recalculates the remaining time based on the time t2 of the second resource 1201-n. Therefore, the terminal device 10 can transmit a delay information report that includes accurate information.

[0213] 18 in this embodiment is the same as that in embodiment 1-1. In the following, only the process in 1802 that differs from embodiment 1-1 will be described.

[0214] The control unit 110 generates information including padding bits of the same size as the delay information report as information for autonomous uplink transmission. The communication unit 120 transmits the generated information in the CG PUSCH using the second resource 1201-n (1802). That is, the terminal device 10 does not transmit information including the delay information report in the CG PUSCH using the second resource 1201-n, but transmits information including padding bits of the same size as the delay information report.

[0215] According to the above configuration, it is possible to prevent the terminal device 10 from transmitting a delay information report that includes inappropriate information (for example, the remaining time).

[0216] 18 in this embodiment is the same as that in embodiment 1-1. In the following, only the process in 1802 that differs from embodiment 1-1 will be described.

[0217] The control unit 110 generates information for autonomous uplink transmission by replacing the remaining time included in the delay information report with padding bits. The communication unit 120 transmits the generated information via the CG PUSCH using the second resource 1201-n (1802).

[0218] According to the above configuration, it is possible to prevent the terminal device 10 from transmitting a delay information report that includes inappropriate information (for example, the remaining time).

[0219] In another example, the control unit 110 may generate a BSR as information for autonomous uplink transmission. That is, the control unit 110 may generate a BSR instead of a delay information report. The communication unit 120 transmits the generated BSR on the CG PUSCH using the second resource 1201-n (1802). Note that the size of the generated BSR may be the same as the size of the delay information report.

[0220] According to the above configuration, it is possible to prevent the terminal device 10 from transmitting a delay information report that includes inappropriate information (e.g., remaining time). The terminal device 10 transmits a BSR instead of a delay information report. The terminal device 10 can report a buffer status to the base station device 20. The base station device 20 can allocate radio resources using the BSR.

[0221] 2. Second Embodiment Next, the configuration of the second embodiment will be described. Only the differences from the first embodiment will be described below, and the same parts as the first embodiment will not be described. Therefore, the configuration of the first embodiment and its variations can be applied to the configuration described in this embodiment, as long as there is no mutual contradiction.

[0222] The terminal device 10 applies a mapping restriction to the delay information report. The terminal device 10 may transmit the delay information report according to the following procedure.

[0223] As shown in FIG. 19 , the communication unit 220 of the base station device 20 transmits an RRC message to the terminal device 10 (S1901). The RRC message includes third configuration information related to a mapping restriction for a delay information report. For example, the third configuration information may be set in an IE related to a MAC cell group included in the RRC message. An example of such an IE is the MAC-CellGroupConfig IE. The control unit 110 of the terminal device 10 generates a delay information report based on the third configuration information included in the RRC message. Specifically, the control unit 110 generates a MAC PDU including the delay information report in accordance with the mapping restriction. The communication unit 120 of the terminal device 10 transmits the delay information report (S1902).

[0224] The following describes the details of each of the third setting information aspects 2-1 to 2-3.

[0225] - Aspect 2-1 The third configuration information may include information (e.g., an index) of a CG for which mapping is permitted. The CG information may be a list or sequence of CGs for which mapping is permitted. When the third configuration information is present, the delay information report may be mapped only to the indicated CG. Furthermore, when the sequence size is zero, the delay information report may not be mapped to any CG. When the third configuration information is absent, the delay information report may be mapped to any CG. For example, the CG information may be information indicating that the delay information report is mapped to a CG with a higher transmission priority than other uplink grants. This configuration reduces the likelihood that an uplink grant corresponding to a CG PUSCH for transmitting the delay information report will be considered a "non-priority uplink grant." In other words, the likelihood of autonomous uplink transmission processing being performed is reduced. It is possible to prevent the terminal device 10 from transmitting a delay information report that includes inappropriate information (e.g., remaining time).

[0226] In another example, the CG information may be information indicating that the delay information report is mapped to a CG in which autonomous uplink transmission processing is not configured (i.e., a CG in which autonomousTx is not configured). According to this configuration, autonomous uplink transmission processing including the delay information report is not performed. It is possible to prevent the terminal device 10 from transmitting a delay information report including inappropriate information (e.g., remaining time). In another example, the CG information may be information indicating that the delay information report is mapped to CG type 1.

[0227] - Aspect 2-2 The third configuration information may include information on DGs for which mapping is permitted (e.g., PHY priority). The DG information may be information indicating that the delay information report is mapped to a DG having a specific PHY priority. If the third configuration information is present and the DG has a PHY priority, the delay information report may be mapped only to a DG that indicates the same PHY priority as the set value. If the third configuration information is present and the DG does not have a PHY priority, the delay information report may be mapped to the DG if the value p0 is set. If the third configuration information is not present, the delay information report may be mapped to any DG. For example, the DG information may be information indicating that the delay information report is mapped to a DG having a PHY priority of value p1. This configuration reduces the possibility that an uplink grant corresponding to a DG PUSCH for transmitting a delay information report will be regarded as a "non-priority uplink grant." The terminal device 10 can transmit the delay information report via the DG PUSCH.

[0228] - Aspect 2-3 The third configuration information may include information on a PUSCH duration for which mapping is permitted. The PUSCH duration information may be information on a maximum PUSCH duration to which the delay information report is mapped. The maximum PUSCH duration may be a value selected from a plurality of values. In this configuration, the delay information report is mapped to a resource of an uplink grant having a PUSCH duration equal to or less than the value set as the maximum PUSCH duration. For example, a shorter maximum PUSCH duration reduces the likelihood that multiple uplink transmissions will overlap on time resources. In this case, priority processing within the terminal is not performed, and therefore autonomous uplink transmission processing including the delay information report is not performed either. In this respect, it is possible to prevent the terminal device 10 from transmitting a delay information report including inappropriate information (e.g., remaining time). The terminal device 10 can transmit the delay information report in a resource corresponding to the uplink grant without performing priority processing within the terminal. In another example, the third configuration information may be a subcarrier spacing in which mapping is allowed, a cell in which mapping is allowed, and / or an uplink HARQ mode in which mapping is allowed.

[0229] 3. Third Embodiment Next, the configuration of the third embodiment will be described. Only the differences from the first and second embodiments will be described below, and the same parts as the first and second embodiments will not be described. Therefore, as long as there is no mutual contradiction, the configurations of the first and second embodiments and their modified examples can be applied to the configuration described in this embodiment.

[0230] As shown in FIG. 20 , the control unit 110 of the terminal device 10 triggers a delay information report at time t11 in accordance with the above trigger condition. The uplink transmission including the delay information report is referred to as a "first uplink transmission." The uplink grant corresponding to the first uplink transmission is referred to as a "first uplink grant." The first uplink transmission is scheduled in a first resource 2001. As shown in FIG. 21 , the control unit 110 generates a MAC PDU corresponding to the first uplink transmission (S2101). The MAC PDU corresponding to the first uplink transmission includes a delay information report.

[0231] As shown in Fig. 20 , at time t12, which is later than time t11, another uplink data occurs. The uplink transmission transmitting the uplink data is referred to as a "second uplink transmission." The uplink grant corresponding to the second uplink transmission is referred to as a "second uplink grant." The second uplink transmission is scheduled in a second resource 2002.

[0232] The first resource 2001 and the second resource 2002 overlap in terms of time resources. As shown in FIG. 21 , the control unit 110 executes priority processing within the terminal (S2102). Through the priority processing within the terminal, the control unit 110 regards the first uplink grant corresponding to the first uplink transmission as a "non-prioritized uplink grant." Through the priority processing within the terminal, the control unit 110 regards the second uplink grant corresponding to the second uplink transmission as a "prioritized uplink grant."

[0233] 21 , the control unit 110 generates a MAC PDU corresponding to the second uplink transmission. In this case, the control unit 110 includes a delay information report in the MAC PDU corresponding to the second uplink transmission (S2103). The communication unit 120 performs the second uplink transmission including the delay information report to the base station apparatus 20.

[0234] Note that, at the time of S2103 in Fig. 21 , the control unit 110 may not yet cancel the trigger for the delay information report. The control unit 110 may cancel the trigger for the delay information report when the second uplink transmission can be transmitted at the PHY layer. In other words, the control unit 110 may cancel the trigger for the delay information report at the time when it is determined that the uplink transmission including the delay information report can be transmitted at the PHY layer.

[0235] Alternatively, at the time of S2101 in Fig. 21 , the control unit 110 may cancel the trigger for the delay information report. For example, the control unit 110 may cancel the trigger for the delay information report when a MAC PDU including the delay information report is generated and / or transmitted. In this case, the control unit 110 may trigger the delay information report based on the fact that the first uplink grant corresponding to the uplink transmission including the delay information report is deemed to be a non-priority uplink grant in S2102. Based on the trigger for the delay information report, the control unit 110 includes the delay information report in the MAC PDU corresponding to the second uplink transmission (S2103).

[0236] Conventionally, in the situation shown in FIG. 20 , the terminal device 10 cannot transmit a delay information report to the base station device 20. In the present embodiment, even when the first uplink transmission and the second uplink transmission overlap on the time resource and the first uplink grant corresponding to the first uplink transmission is considered a "non-priority uplink grant," the terminal device 10 can include the delay information report in the second uplink transmission. According to the above configuration, the terminal device 10 can transmit the delay information report to the base station device 20 earlier. In other words, even when the first uplink transmission and the second uplink transmission overlap on the time resource as in the situation shown in FIG. 20 , the delay in transmitting the delay information report can be minimized.

[0237] The control unit 110 may calculate delay information (e.g., remaining time) included in the delay information report based on the time of the initial transmission of each uplink grant. For example, the remaining time may be a value calculated based on a predetermined timer (e.g., a PDCP discard timer) using the time of the initial transmission as a reference, as described above. The control unit 110 may calculate delay information (e.g., remaining time) included in the MAC PDU corresponding to the first uplink transmission based on time t14 of the first resource 2001 in which the first uplink transmission is scheduled. The control unit 110 may calculate delay information (e.g., remaining time) included in the MAC PDU corresponding to the second uplink transmission based on time t13 of the second resource 2002 in which the second uplink transmission is scheduled. Time t13 and time t14 are different. Therefore, the delay information (e.g., remaining time) included in the MAC PDU corresponding to the first uplink transmission may be different from the delay information (e.g., remaining time) included in the MAC PDU corresponding to the second uplink transmission.

[0238] In another example, the control unit 110 may include a delay information report included in a MAC PDU corresponding to a first uplink transmission in a MAC PDU corresponding to a second uplink transmission. In this manner, the control unit 110 may include the delay information report generated for the first uplink transmission in the second uplink transmission. In this configuration, the delay information (e.g., remaining time) included in the MAC PDU corresponding to the first uplink transmission is the same as the delay information (e.g., remaining time) included in the MAC PDU corresponding to the second uplink transmission. For example, if time t13 and time t14 are substantially the same, there is substantially no difference in the delay information, and the control unit 110 may perform this processing.

[0239] In the example of Fig. 21 , the control unit 110 includes a delay information report in a MAC PDU corresponding to the second uplink transmission after the first uplink grant is deemed a "non-priority uplink grant" based on priority processing in the terminal. The present embodiment is not limited to this example. In a situation where a delay information report is triggered, if the first uplink transmission and the second uplink transmission overlap in time resources, the control unit 110 may perform processing according to the flow shown in Fig. 22 .

[0240] As shown in Fig. 22, the control unit 110 generates a MAC PDU corresponding to a first uplink transmission. The control unit 110 includes a delay information report in the MAC PDU (S2201). Next, the control unit 110 generates a MAC PDU corresponding to a second uplink transmission. The control unit 110 includes a delay information report in the MAC PDU (S2202). Thereafter, the control unit 110 executes priority processing within the terminal (S2203).

[0241] According to the above configuration, the control unit 110 includes the delay information report in both the MAC PDU corresponding to the first uplink transmission and the MAC PDU corresponding to the second uplink transmission before priority processing in the terminal. Regardless of whether the first uplink grant or the second uplink grant is considered to be the "prioritized uplink grant," the terminal device 10 can transmit the delay information report to the base station device 20.

[0242] In the above example, the control unit 110 includes the delay information report in the second uplink transmission that overlaps with the first uplink transmission in terms of time resources. However, the present embodiment is not limited to this example. As shown in FIG. 23 , the control unit 110 may include the delay information report in the uplink transmission performed in the third resource 2003. The third resource 2003 is a resource that does not overlap with the first resource 2001 in terms of time resources and that is later than the first resource 2001. The third resource 2003 may be a next resource associated with the same HPI as the first resource 2001. The third resource 2003 may be a next resource associated with a different HPI from the first resource 2001.

[0243] The terminal device 10 may be configured to perform the above-described processing described in FIGS. 20 to 23 when transmitting a MAC CE including a delay information report, and not to perform the above-described processing when transmitting a MAC CE not including a delay information report.

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

[0245] The words, phrases, and other expressions used in the above embodiments are merely examples and may be replaced with substantially identical or similar expressions. In particular, since the technology according to the above embodiments relates to technical specifications, the expressions in the above embodiments may be replaced with substantially identical or similar expressions in technical specifications (e.g., technical specifications cited in this specification).

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

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

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

[0249] 5. Supplementary Notes Some or all of the above embodiments and modified examples may also be described as in the following supplementary notes, but are not limited to the contents of the supplementary notes. Below, a relationship is expressed in which a supplementary note that is dependent on multiple supplementary notes is dependent on another supplementary note that is dependent on multiple supplementary notes. All of the dependency relationships of the supplementary notes expressed below are included in the above embodiments.

[0250] (Supplementary Note 1) A terminal device (10) comprising: a control unit (110) configured to, when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed a non-priority uplink grant based on priority processing, determine to perform autonomous uplink transmission on a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generate information for the autonomous uplink transmission; and a communication unit (120) configured to perform the autonomous uplink transmission to a base station device (20).

[0251] (Supplementary Note 2) The terminal device according to Supplementary Note 1, wherein the control unit is configured to generate the delay information report as the information for the autonomous uplink transmission.

[0252] (Supplementary Note 3) The terminal device according to Supplementary Note 2, wherein the control unit is configured to calculate the delay information based on a time (t2) of the second resource as a reference, and generate the delay information report including the calculated delay information as the information for the autonomous uplink transmission.

[0253] (Supplementary Note 4) The terminal device according to Supplementary Note 1, wherein the control unit is configured to generate, as the information for the autonomous uplink transmission, information including padding bits having the same size as the delay information report.

[0254] (Supplementary Note 5) The terminal device according to Supplementary Note 1, wherein the control unit is configured to generate, as the information for the autonomous uplink transmission, information in which the delay information included in the delay information report is replaced with padding bits.

[0255] (Supplementary Note 6) The terminal device according to Supplementary Note 1, wherein the control unit is configured to generate a Buffer Status Report (BSR) as the information for the autonomous uplink transmission.

[0256] (Supplementary Note 7) The terminal device according to Supplementary Note 6, wherein the size of the BSR is the same as the size of the delay information report.

[0257] (Supplementary Note 8) The terminal device according to any one of Supplementary Notes 1 to 7, wherein the delay information includes information about a remaining time calculated based on a predetermined timer.

[0258] (Supplementary Note 9) The terminal device according to any one of Supplementary Notes 1 to 8, wherein the delay information report is a Buffer Status Report (BSR) including the delay information and buffer size information related to a buffer size.

[0259] (Supplementary Note 10) The terminal device according to Supplementary Note 9, wherein the BSR includes: a field including the delay information and the buffer size information; and a field including the buffer size information but not including the delay information.

[0260] (Supplementary Note 11) The terminal device according to any one of Supplementary Notes 1 to 10, wherein the control unit is configured to generate a Medium Access Control Protocol Data Unit (MAC PDU) including the delay information report, and identification information for identifying the delay information report is included in a MAC CE or a header included in the MAC PDU.

[0261] (Supplementary Note 12) The terminal device according to any one of Supplementary Notes 1 to 11, wherein the delay information is delay information for predetermined data, and the predetermined data is data corresponding to one logical channel, data corresponding to one logical channel group (LCG), data corresponding to one or more protocol data unit sets (PDU sets), or data corresponding to one or more data bursts.

[0262] (Supplementary Note 13) A method for a terminal device (10), comprising: when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed a non-priority uplink grant based on priority processing, determining to perform autonomous uplink transmission on a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generating information for the autonomous uplink transmission; and performing the autonomous uplink transmission to a base station device (20).

[0263] (Supplementary Note 14) A program that causes a processor (101) in a terminal device (10) to execute the following: when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed a non-priority uplink grant based on priority processing, determining to perform autonomous uplink transmission using a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generating information for the autonomous uplink transmission; and performing the autonomous uplink transmission to a base station device (20).

[0264] (Supplementary Note 15) A non-transient tangible recording medium having recorded thereon a program that causes a processor (101) in a terminal device (10) to execute the following: when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, determining to perform autonomous uplink transmission on a second resource scheduled after a first resource on which the uplink transmission is scheduled, and generating information for the autonomous uplink transmission; and performing the autonomous uplink transmission to a base station device (20).

[0265] (Supplementary Note 16) A terminal device (10) comprising: a communication unit (120) that receives setting information related to a mapping restriction for a delay information report including delay information from a base station device (20); and a control unit (110) that generates the delay information report according to the setting information.

[0266] (Supplementary Note 17) The terminal device according to Supplementary Note 16, wherein the configuration information includes information on a configured grant (CG) to which the delay information report is mapped.

[0267] (Supplementary Note 18) The terminal device according to Supplementary Note 17, wherein the configuration information is information indicating that the delay information report is mapped to a CG having a higher priority than other uplink grants.

[0268] (Supplementary Note 19) The terminal device according to Supplementary Note 17, wherein the configuration information is information indicating that the delay information report is mapped to a CG for which an autonomous uplink transmission process is not configured.

[0269] (Supplementary Note 20) The terminal device according to Supplementary Note 16, wherein the configuration information includes information on a dynamic grant (DG) to which the delay information report is mapped.

[0270] (Supplementary Note 21) The terminal device according to Supplementary Note 20, wherein the configuration information is information indicating that the delay information report is mapped to a DG having a specific PHY priority.

[0271] (Supplementary Note 22) The terminal device according to Supplementary Note 16, wherein the configuration information includes information on a maximum PUSCH duration to which the delay information report is mapped.

[0272] (Supplementary Note 23) The terminal device according to Supplementary Note 22, wherein the maximum PUSCH duration is a value selected from a plurality of values.

[0273] (Supplementary Note 24) The terminal device according to Supplementary Note 22, wherein the control unit is configured to map the delay information report to a resource of an uplink grant having a PUSCH duration equal to or less than the maximum PUSCH duration.

[0274] (Supplementary Note 25) The terminal device according to any one of Supplementary Notes 16 to 24, wherein the delay information includes information about a remaining time calculated based on a predetermined timer.

[0275] (Supplementary Note 26) The terminal device according to any one of Supplementary Notes 16 to 25, wherein the delay information report is a Buffer Status Report (BSR) including the delay information and buffer size information related to a buffer size.

[0276] (Supplementary Note 27) The terminal device according to Supplementary Note 26, wherein the BSR includes: a field including the delay information and the buffer size information; and a field including the buffer size information but not including the delay information.

[0277] (Supplementary Note 28) The terminal device according to any one of Supplementary Notes 16 to 27, wherein the control unit is configured to generate a Medium Access Control Protocol Data Unit (MAC PDU) including the delay information report, and identification information for identifying the delay information report is included in a MAC CE or a header included in the MAC PDU.

[0278] (Supplementary Note 29) The terminal device according to any one of Supplementary Notes 16 to 28, wherein the delay information is delay information for predetermined data, and the predetermined data is data corresponding to one logical channel, data corresponding to one logical channel group (LCG), data corresponding to one or more protocol data unit sets (PDU sets), or data corresponding to one or more data bursts.

[0279] (Supplementary Note 30) A method for a terminal device (10) comprising: receiving, from a base station device (20), configuration information relating to a mapping restriction for a delay information report including delay information; and generating the delay information report according to the configuration information.

[0280] (Supplementary Note 31) A program that causes a processor (101) in a terminal device (10) to execute the following: receiving, from a base station device (20), configuration information regarding mapping restrictions for delay information reports that include delay information; and generating the delay information report according to the configuration information.

[0281] (Supplementary Note 32) A non-transient tangible recording medium having recorded thereon a program that causes a processor (101) in a terminal device (10) to execute the following: receiving, from a base station device (20), configuration information regarding mapping restrictions for delay information reports including delay information; and generating the delay information reports according to the configuration information.

[0282] (Supplementary Note 33) A base station device (20) comprising: a communication unit (220) configured to transmit setting information regarding a mapping restriction for a delay information report including delay information to a terminal device (10) and receive the delay information report from the terminal device; and a control unit (210) configured to allocate radio resources to the terminal device based on the delay information report.

[0283] (Supplementary Note 34) The base station device according to Supplementary Note 33, wherein the configuration information includes information on a configured grant (CG) to which the delay information report is mapped.

[0284] (Supplementary Note 35) The base station device according to Supplementary Note 34, wherein the configuration information is information indicating that the delay information report is mapped to a CG having a higher priority than other uplink grants.

[0285] (Supplementary Note 36) The base station device according to Supplementary Note 34, wherein the configuration information is information indicating that the delay information report is mapped to a CG for which autonomous uplink transmission processing is not configured.

[0286] (Supplementary Note 37) The base station device according to Supplementary Note 33, wherein the configuration information includes information on a dynamic grant (DG) to which the delay information report is mapped.

[0287] (Supplementary Note 38) The base station device according to Supplementary Note 37, wherein the configuration information is information indicating that the delay information report is mapped to a DG having a specific PHY priority.

[0288] (Supplementary Note 39) The base station apparatus according to Supplementary Note 33, wherein the configuration information includes information on a maximum PUSCH duration to which the delay information report is mapped.

[0289] (Supplementary Note 40) The base station apparatus according to Supplementary Note 39, wherein the maximum PUSCH duration is a value selected from a plurality of values.

[0290] (Supplementary Note 41) A method for a base station device (20) comprising: transmitting configuration information regarding mapping restrictions for delay information reports including delay information to a terminal device (10); receiving the delay information reports from the terminal device; and allocating radio resources to the terminal device based on the delay information reports.

[0291] (Supplementary Note 42) A method for a base station device (20) comprising: transmitting configuration information regarding mapping restrictions for delay information reports including delay information to a terminal device (10); receiving the delay information reports from the terminal device; and allocating radio resources to the terminal device based on the delay information reports.

[0292] (Supplementary Note 43) A program that causes a processor (201) in a base station device (20) to execute the following: transmitting configuration information regarding mapping restrictions for delay information reports including delay information to a terminal device (10); receiving the delay information reports from the terminal device; and allocating radio resources to the terminal device based on the delay information reports.

[0293] (Supplementary Note 44) A non-transient tangible recording medium having recorded thereon a program that causes a processor (201) in a base station device (20) to execute the following: transmitting configuration information regarding mapping restrictions for delay information reports including delay information to a terminal device (10); receiving the delay information reports from the terminal device; and allocating radio resources to the terminal device based on the delay information reports.

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

Claims

1. A terminal device (10) comprising: a control unit (110) configured to determine, when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, to perform autonomous uplink transmission using a second resource scheduled after a first resource in which the uplink transmission is scheduled, and to generate information for the autonomous uplink transmission; and a communication unit (120) configured to perform the autonomous uplink transmission to a base station device (20).

2. The terminal device according to claim 1, wherein the control unit is configured to generate the delay information report as the information for the autonomous uplink transmission.

3. The terminal device according to claim 2, wherein the control unit is configured to calculate the delay information based on a time (t2) of the second resource, and to generate the delay information report including the calculated delay information as the information for the autonomous uplink transmission.

4. The terminal device according to claim 1, wherein the control unit is configured to generate information including padding bits of the same size as the delay information report as the information for the autonomous uplink transmission.

5. The terminal device according to claim 1, wherein the control unit is configured to generate information in which the delay information included in the delay information report is replaced with padding bits as the information for the autonomous uplink transmission.

6. The terminal device according to claim 1, wherein the control unit is configured to generate a Buffer Status Report (BSR) as the information for the autonomous uplink transmission.

7. The terminal device according to claim 6, wherein the size of the BSR is the same as the size of the delay information report.

8. The terminal device according to any one of claims 1 to 7, wherein the delay information includes information regarding a remaining time calculated based on a predetermined timer.

9. The terminal device according to claim 1, wherein the delay information report is a Buffer Status Report (BSR) including the delay information and buffer size information regarding a buffer size.

10. The terminal device according to claim 9, wherein the BSR includes: a field including the delay information and the buffer size information; and a field including the buffer size information but not the delay information.

11. The terminal device according to claim 1, wherein the control unit is configured to generate a MAC PDU (Medium Access Control Protocol Data Unit) including the delay information report, and identification information for identifying the delay information report is included in a MAC CE or a header included in the MAC PDU.

12. The terminal device of claim 1, wherein the delay information is delay information for specified data, and the specified data is data corresponding to one logical channel, data corresponding to one logical channel group (LCG), data corresponding to one or more protocol data unit sets (PDU sets), or data corresponding to one or more data bursts.

13. A method for a terminal device (10), comprising: when an uplink grant corresponding to an uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, determining to perform an autonomous uplink transmission on a second resource scheduled after a first resource on which the uplink transmission is scheduled, generating information for the autonomous uplink transmission; and performing the autonomous uplink transmission to a base station device (20).

Images