WO2025022773A1 - 端末装置及び端末装置の方法 - Google Patents

端末装置及び端末装置の方法 Download PDF

Info

Publication number
WO2025022773A1
WO2025022773A1 PCT/JP2024/018456 JP2024018456W WO2025022773A1 WO 2025022773 A1 WO2025022773 A1 WO 2025022773A1 JP 2024018456 W JP2024018456 W JP 2024018456W WO 2025022773 A1 WO2025022773 A1 WO 2025022773A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
delay information
uplink transmission
data
uplink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/018456
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
樹 長野
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Original Assignee
Denso Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Denso Corp filed Critical Denso Corp
Priority to JP2025535587A priority Critical patent/JPWO2025022773A1/ja
Publication of WO2025022773A1 publication Critical patent/WO2025022773A1/ja
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/115—Grant-free or autonomous transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient

Definitions

  • This disclosure relates to a terminal device and a method for a terminal device.
  • XR extended reality
  • XR is a concept that includes multimedia integration technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and substitutional reality (SR).
  • VR virtual reality
  • AR augmented reality
  • MR mixed reality
  • SR substitutional reality
  • three-dimensional time-series image data in real 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.
  • Non-patent document 1 discusses the implementation of XR in 5G NR (Fifth Generation New Radio), a wireless specification defined by the Third Generation Partnership Project (3GPP (registered trademark)).
  • 5G NR Full Generation New Radio
  • 3GPP Third Generation Partnership Project
  • XR is expected to be operated under various requirements, including the requirement of low latency. Accordingly, with regard to uplink communication from terminal devices, base station devices are required to allocate radio resources taking into account the above requirements. In order to allocate such radio resources, it is being considered that terminal devices will make a specified report (e.g., a report of information related to delays) to base station devices.
  • a specified report e.g., a report of information related to delays
  • terminal devices will make a specified report (e.g., a report of information related to delays) to base station devices.
  • delay information information
  • a “report including delay information” will be referred to as a "delay information report.”
  • Non-Patent Document 2 describes priority processing within the terminal (Intra-UE Prioritization 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 relation to this, the inventor has found a problem that when the above priority processing is performed, the terminal device may not be able to transmit a delay information report at an appropriate time. Note that the above problem also occurs in normal terminal devices and base station devices other than those implementing XR.
  • This disclosure provides technology that enables a terminal device to transmit delay information reports at appropriate times.
  • the terminal device of the present disclosure includes a control unit configured to include a delay information report including delay information in a second uplink transmission corresponding to a second uplink grant different from the first uplink grant when the first uplink grant corresponding to the first uplink transmission including the delay information report is deemed to be a non-priority uplink grant based on priority processing, and a communication unit configured to perform the second uplink transmission to a base station device.
  • the method of the terminal device disclosed herein includes, when a first uplink grant corresponding to a first uplink transmission including a delay information report including delay information is deemed to be a non-priority uplink grant based on priority processing, including the delay information report in a second uplink transmission corresponding to a second uplink grant different from the first uplink grant, and performing the second uplink transmission to a base station device.
  • the above configuration allows the terminal device to transmit delay information reports at appropriate times. Note that the above configuration may provide other effects instead of or in addition to the above effect.
  • FIG. 1 is a diagram showing a communication system S according to a first embodiment.
  • FIG. 2 is a diagram showing a protocol stack of a U-plane according to the first embodiment;
  • FIG. 3 is a diagram showing a protocol stack of a C-plane according to the first embodiment;
  • FIG. 4 is a block diagram showing a schematic hardware configuration of the terminal device 10 according to the first embodiment.
  • FIG. 5 is a block diagram showing a schematic functional configuration of a terminal device 10 according to the first embodiment.
  • FIG. 6 is a block diagram showing a schematic hardware configuration of the base station device 20 according to the first embodiment.
  • FIG. 7 is a block diagram showing a schematic functional configuration of a base station device 20 according to the first embodiment.
  • FIG. 8 is a diagram showing a radio frame configuration according to the first embodiment;
  • FIG. 9 is a diagram showing the configuration of a short BSR.
  • FIG. 10 is a diagram showing the configuration of a long BSR;
  • FIG. 11 is a diagram for explaining priority processing in a MAC (Medium Access Control) layer.
  • FIG. 12 is a diagram for explaining a process when an uplink grant is deemed to be non-priority by priority process in the MAC layer;
  • FIG. 13 is a sequence diagram showing a process flow 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
  • FIG. 17 is a diagram for explaining an autonomous transmission process of the terminal device 10.
  • FIG. 18 is a diagram showing a process flow for transmitting a delay information report according to the first embodiment
  • FIG. 19 is a sequence diagram showing a process flow of the terminal device 10 and the base station device 20 according to the second embodiment.
  • FIG. 20 is a diagram for explaining a situation in which a delay information report is transmitted according to the third embodiment;
  • FIG. 21 is a flowchart showing a process flow for transmitting a delay information report according to the third embodiment
  • FIG. 22 is a flowchart showing another aspect of the process flow for transmitting a delay information report according to the third embodiment
  • FIG. 23 is a diagram for explaining another aspect of the flow of the process of transmitting a delay information report according to the third embodiment.
  • each of the embodiments described below is merely an example of a configuration capable of realizing 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 to realizing the present disclosure, and some of the elements can be omitted as appropriate. Therefore, the scope of the present disclosure is not limited by the configurations described in each of the following embodiments. As long as there are no mutual contradictions, a configuration that combines multiple configurations described in the following embodiments can also be adopted.
  • 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 according to predetermined technical specifications (Technical Specifications, TS).
  • TS Technical Specifications
  • the communication system S may comply with technical specifications (e.g., 5G, 5G Advanced, 6G, etc.) defined by 3GPP.
  • communication system S the user plane, where user data is transmitted and received, and the control plane, where control data is transmitted and received, are configured separately.
  • communication system S supports C/U separation.
  • the user plane is abbreviated as the U plane
  • the control plane is abbreviated as the C plane.
  • 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 specifications.
  • the terminal device 10 may also be a device that complies with other older or newer 3GPP specifications.
  • the terminal device 10 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a notebook PC, a communication module, a communication card, or an IoT device such as a surveillance camera or a robot.
  • the terminal device 10 may be a vehicle (e.g., a car, a train, etc.) or a device 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.
  • 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, a remote unit, etc.
  • 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).
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra-Reliable and Low Latency Communications
  • mMTC massive Machine Type Communications
  • the base station device 20 manages at least one cell.
  • a cell constitutes the smallest unit of a communication area.
  • 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 the 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 the C-plane protocol for the terminal device 10.
  • the base station device 20 communicates with the core network 30 in the U-plane and C-plane. More specifically, the core network 30 includes multiple logical nodes including an Access and Mobility Management Function (AMF) and a User Plane Function (UPF). The base station device 20 connects to the AMF in the C-plane and connects to the UPF in the U-plane.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • the base station device 20 may be, for example, a gNB that provides the terminal device 10 with a U-plane and a C-plane conforming to the 3GPP 5G NR specifications 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.
  • the base station device 20 may be composed of multiple unit devices.
  • the base station device 20 may be composed of a centralized unit (CU), a distributed unit (DU), and a radio unit (RU).
  • CU centralized unit
  • DU distributed unit
  • RU radio unit
  • a radio access network is formed by interconnecting multiple base station devices 20.
  • the radio access network formed by base station devices 20 that are gNBs may be referred to as an NG-RAN.
  • a base station device 20 that is a gNB may be referred to as an NG-RAN node.
  • the multiple base station devices 20 are connected to each other by a specific interface (e.g., an Xn interface). More specifically, for example, the multiple base station devices 20 are connected to each other by an Xn-U interface in the U-plane, and are connected to each other by an Xn-C interface in the C-plane. Note that the multiple base station devices 20 may also be connected to each other by other interfaces with different functions or names.
  • a specific interface e.g., an Xn interface
  • the multiple base station devices 20 are connected to each other by an Xn-U interface in the U-plane, and are connected to each other by an Xn-C interface in the C-plane.
  • the multiple base station devices 20 may also be connected to each other by other interfaces with different functions or names.
  • Each base station device 20 is connected to the core network 30 via a specific interface (e.g., an NG interface). More specifically, for example, each base station device 20 is connected to the UPF of the core network 30 via an NG-U interface in the U-plane, and is connected to the AMF of the core network 30 via an NG-C interface in the C-plane. Note that each base station device 20 may also be connected to the core network 30 via another interface with a different function or name.
  • a specific interface e.g., an NG interface
  • 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.
  • 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.
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • 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).
  • PHY physical
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • NAS non-access stratum
  • 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.
  • the terminal device 10 may have hardware elements other than the elements shown in FIG. 4.
  • the processor 101 is a computing element that realizes various functions of the terminal device 10.
  • the processor 101 may be a SoC (System-on-a-Chip) that includes elements such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a memory controller.
  • SoC System-on-a-Chip
  • 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 the operation of the terminal device 10.
  • the processor 101 realizes 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).
  • the input/output interface 103 is an interface that accepts operations on the terminal device 10 and supplies them to the processor 101, as well as presenting various information to the user.
  • the input/output interface 103 is, for example, a touch panel.
  • the wireless interface 104 is a circuit that performs various signal processing to realize wireless communication, and includes a baseband processor and an RF circuit.
  • the wireless interface 104 transmits and receives wireless signals to and from the base station device 20 via the antenna 105.
  • 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.
  • 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.
  • 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.
  • the control unit 110 operates to execute various processes of the terminal device 10 of this embodiment.
  • 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.
  • the base station device 20 may have hardware elements other than the elements shown in FIG. 6.
  • 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.
  • Memory 202 is composed of at least one storage medium such as ROM (Read Only Memory), RAM, HDD (Hard Disk Drive), SSD (Solid State Drive), etc.
  • Memory 202 is an element that temporarily or permanently stores programs and data used to execute various processes in base station device 20.
  • the programs include one or more instructions for the operation of base station device 20.
  • Processor 201 realizes the functions of base station device 20 by expanding and executing the programs stored in memory 202 in memory 202 and/or a system memory (not shown).
  • the network interface 203 is an interface used to send and receive signals to and from other base station devices 20 and the core network 30.
  • 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 the antenna 205.
  • 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.
  • 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. Also, 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.
  • other nodes e.g., other base station devices 20, nodes of the core network 30
  • the communication unit 220 includes a wireless interface 204 and an antenna 205.
  • 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.
  • the network communication unit 230 includes the network interface 203.
  • 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).
  • the control unit 210 operates to execute various processes of the base station device 20 of this embodiment.
  • the terminal device 10 and the base station device 20 wirelessly communicate with each other using radio resources in the frequency domain and the time domain.
  • the radio resources are described below.
  • 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.
  • SCS subcarrier spacing
  • multiple subcarrier spacings ⁇ f may be applied.
  • ⁇ is an integer equal to or greater than 0, and can take on at least one of the following values: 0, 1, 2, 3, 4, 5, or 6. Therefore, the subcarrier spacing ⁇ f [kHz] can take on at least one of the following values: 15, 30, 60, 120, 240, 480, or 960. Note that ⁇ may take on a value of 7 or greater.
  • a hierarchical radio frame structure is used as shown in Figure 8.
  • One radio frame contains 10 subframes. Subframes are assigned subframe numbers that count up from 0 to 9.
  • 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 are independent of the subcarrier spacing ⁇ f.
  • One subframe includes one or more slots (slot(s)).
  • the number Ns of slots included in one subframe depends on the above-mentioned value of ⁇ , and further on the subcarrier interval ⁇ f.
  • a slot contains multiple symbols.
  • the number of symbols a slot contains depends on the type of cyclic prefix. For example, if a normal cyclic prefix is used, a slot contains 14 symbols. For example, if an extended cyclic prefix is used, a slot contains 12 symbols.
  • the number of slots and the number of symbols included in each of the radio frames, half frames, and subframes, which have fixed time lengths, are variable. Therefore, the time length of the slots and the time length of the symbols are also variable.
  • Radio frames are assigned a system frame number (SFN) that counts up from 0 to 1023 in increments of 1.
  • SFN system frame number
  • SFN "0" corresponds to the initial SFN value
  • SFN "1023” corresponds to the maximum SFN value. Therefore, the radio frame following a radio frame assigned SFN 1023 is assigned SFN 0.
  • the time length of a radio frame is 10 ms
  • the base station device 20 may set 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 set and the base station device 20 and the terminal device 10 perform wireless communication may also be referred to as carrier aggregation.
  • the base station device 20 may also set one or more bandwidth parts (Bandwidth Part, BWP) for the terminal device 10 for each of one or more serving cells.
  • BWP bandwidth parts
  • a downlink bandwidth part DownLink Bandwidth Part, DL-BWP
  • an uplink bandwidth part UpLink Bandwidth Part, UL-BWP
  • the DL-BWP may include an initial DL-BWP (Initial DL-BWP) and/or a dedicated DL-BWP (Dedicated DL-BWP).
  • the UL-BWP may include an initial UL-BWP (Initial UL-BWP) and/or a dedicated UL-BWP (Dedicated UL-BWP).
  • BWP may include DL-BWP and/or UL-BWP.
  • 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.
  • the terminal device 10 and the base station device 20 transmit and receive user data and control information using multiple hierarchical channels.
  • a physical channel is a channel used for physical communication between the terminal device 10 and the base station device 20. Examples of physical channels include the physical downlink control channel (Physical Downlink Control CHannel, PDCCH), the physical broadcast channel (Physical Broadcast CHannel, PBCH), and the physical uplink control channel (Physical Uplink Control CHannel, PUCCH).
  • PDCCH Physical Downlink Control CHannel
  • PBCH Physical Broadcast CHannel
  • PUCCH Physical Uplink Control CHannel
  • a transport channel is a channel that is located above a physical channel, and is mapped to a physical channel at 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).
  • DL-SCH downlink shared channel
  • UL-SCH uplink shared channel
  • data in the downlink may also be referred to as DL-SCH data.
  • data in the uplink may also be referred to as UL-SCH data.
  • DL-SCH data includes user data in the downlink.
  • UL-SCH data includes user data in the uplink.
  • a logical channel is a channel that is located above a transport channel and is mapped to a transport channel at 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 the Broadcast Control Channel (BCCH), the Common Control Channel (CCCH), and the Dedicated Control Channel (DCCH).
  • BCCH Broadcast Control Channel
  • CCCH Common Control Channel
  • DCCH Dedicated Control Channel
  • 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 regarding 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.
  • one or more formats may be specified for the transmission of DCI in the PDCCH.
  • the format specified for the transmission of DCI in the PDCCH may be referred to as a DCI format.
  • the DCI format may include a DCI format used for scheduling the 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).
  • the DCI format may also include a DCI format used for scheduling the 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).
  • PUSCH Physical Uplink Shared CHannel
  • the DCI format may also include a DCI format not used for scheduling the PDSCH and/or PUSCH.
  • a DCI format used for scheduling the PDSCH and/or PUSCH may be referred to as a scheduling DCI format.
  • a DCI format not used for scheduling the PDSCH and/or PUSCH may be referred to as a non-scheduling DCI format.
  • a "DCI format” may be simply referred to as a "PDCCH”.
  • a "DCI generated according to a DCI format” may be simply referred to as a "DCI format".
  • the base station device 20 may configure frequency domain resources and/or time domain resources for the terminal device 10 to monitor (i.e., monitor) the PDCCH candidate set.
  • the frequency domain resources for the terminal device 10 to monitor the PDCCH candidate set may be referred to as a control resource set (COntrol REsource SET, CORESET).
  • the time domain resources for the terminal device 10 to monitor 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 the serving cell in which PDCCH monitoring is configured according to the corresponding search space set.
  • monitoring may imply attempting to decode each of the PDCCH candidates according to the monitored DCI format.
  • the above configuration may be referred to as blind decoding.
  • a CRC Cyclic Redundancy Check
  • RNTI Radio Network Temporary Identifier
  • the CRC may also be referred to as a CRC parity bit.
  • Multiple types of RNTI are defined.
  • 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 an MCS-C-RNTI (Modulation and Coding Scheme Cell-RNTI), and information indicating a CS-RNTI (Configured Scheduling-RNTI). That is, a CRC scrambled by at least one of the C-RNTI, MCS-C-RNTI, and CS-RNTI may be added to the DCI (or DCI format) transmitted on the PDCCH.
  • Cell-RNTI C-RNTI
  • MCS-C-RNTI Modulation and Coding Scheme Cell-RNTI
  • CS-RNTI Configured Scheduling-RNTI
  • the terminal device 10 may monitor (and/or receive) the PDCCH and detect (and/or receive) the DCI format.
  • 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).
  • SR Scheduling Request
  • HARQ Hybrid Automatic Repeat reQuest
  • CSI Channel State Information
  • the UCI is mapped to the PUCCH or PUSCH and corresponds to Layer 1 signaling.
  • the base station device 20 transmits MAC layer control elements (CEs) to the terminal device 10 using the DL-SCH, which is a transport channel.
  • CEs MAC layer control elements
  • the downlink MAC CEs are mapped to the PDSCH via the DL-SCH, and correspond to Layer 2 signaling.
  • the terminal device 10 transmits a MAC layer control element (CE) 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).
  • BSR buffer status report
  • the uplink MAC CE is mapped to the PUSCH via the UL-SCH and corresponds to Layer 2 signaling.
  • the base station device 20 transmits (or notifies) system information (SI) to the terminal device 10 using the logical channel BCCH.
  • SI includes minimum system information (MSI) and other system information (OSI).
  • MSI includes master information block (MIB) and system information block 1 (SIB1).
  • SIB1 may be referred to as remaining minimum system information (RMSI).
  • OSI includes system information blocks other than SIB1 (SIB2 onwards).
  • the MIB is mapped to the PBCH via the BCH (Broadcast CHannel), and the SIB is mapped to the PDSCH via the DL-SCH.
  • 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.
  • SRB signaling radio bearer
  • 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 that include control information in the NAS layer.
  • CCCH or DCCH is used to transmit RRC messages from the base station device 20 to the terminal device 10.
  • the CCCH and DCCH are each mapped to the PDSCH via the DL-SCH.
  • the RRC message corresponds to Layer 3 signaling.
  • 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 perform reconfiguration or modification of the connection between the base station device 20 and the terminal device 10.
  • 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.
  • the user equipment capability information message is an RRC message transmitted from the terminal device 10 to the base station device 20 using SRB1.
  • DCCH is used to transmit the user equipment capability information message.
  • the user equipment capability information message is used to notify the base station device 20 of information regarding the radio access capability of the terminal device 10.
  • the user equipment assistance information message is an RRC message transmitted from the terminal device 10 to the base station device 20 using SRB1 or SRB3.
  • DCCH is used to transmit the user equipment assistance information message.
  • the user equipment assistance information message is used to notify the base station device 20 of various information (UE assistance information) related to the terminal device 10.
  • SR Scheduling Request
  • the SR is used by the terminal device 10 to request radio resource allocation of the PUSCH from the base station device 20.
  • the SR may 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 parameters of the SR to the terminal device 10.
  • the parameters of the SR are included in a SchedulingRequestResourceConfig IE, which is an example of an information element (IE) of RRC.
  • the terminal device 10 transmits UCI including SR to the base station device 20 using the configured PUCCH resources.
  • 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.
  • Dynamic Grant (DG) DG is a scheduling method for allocating radio resources for PUSCH according to the procedure of uplink grant.
  • the base station device 20 transmits an uplink grant to the terminal device 10 on the PDCCH.
  • the terminal device 10 transmits PUSCH according to the uplink grant.
  • the base station device 20 may allocate radio resources for PUSCH using a DCI format with a CRC scrambled by C-RNTI and/or MCS-C-RNTI (i.e., a DCI format used for scheduling PUSCH), and the terminal device 10 may perform uplink transmission using the allocated radio resources for PUSCH.
  • a new data indicator (New Data Indicator) included in the DCI format to which the CRC scrambled by C-RNTI and/or MCS-C-RNTI is added may be set to 0 or 1.
  • 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.
  • a new data indicator included in the DCI format with a CRC scrambled by the CS-RNTI may be set to 1.
  • CG is a scheduling method for allocating radio resources for PUSCH without the above-mentioned dynamic uplink grant procedure.
  • CG includes two types, type 1 and type 2.
  • the base station device 20 transmits an RRC message including CG parameters to the terminal device 10.
  • the CG parameters are included in ConfiguredGrantConfig IE, which is an example of an RRC information element (IE).
  • the ConfiguredGrantConfig IE includes a parameter periodicity related to the period of transmission using PUSCH.
  • 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).
  • PFS frames per second
  • the terminal device 10 starts transmitting a signal at the set period without being triggered by DCI.
  • 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.
  • the terminal device 10 starts transmission using the PUSCH at a set period.
  • Hybrid Automatic Repeat Request is a mechanism for controlling error correction and retransmission requests.
  • a receiver detects an error in data received from a sender, it requests the sender to retransmit the data.
  • the receiver combines the previously received data with the retransmitted data to obtain the data.
  • HARQ is a SAW (Stop-And-Wait) protocol.
  • the receiving side correctly receives the data, it sends an acknowledgement (Ack) to the transmitting side.
  • Ack acknowledgement
  • 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 finished receiving the data.
  • 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 the PUSCH-ServingCellConfig IE, which is an example of an RRC information element (IE).
  • each HARQ process For uplink transmission, each HARQ process supports one Transport Block (TB). That is, one TB is transmitted at one transmission opportunity. Also, one HARQ process identifier is associated with (or assigned to) one HARQ process. Hereinafter, the HARQ process identifier is denoted as "HPI”.
  • the terminal device 10 transmits the BSR by MAC signaling using the allocated PUSCH radio resource.
  • the BSR is composed of a MAC CE included in a MAC PDU (Medium Access Control Protocol Data Unit).
  • the BSR indicates information on the buffer status of the uplink data of the MAC entity.
  • the base station device 20 allocates radio resources for the uplink to the terminal device 10 based on the BSR.
  • the base station device 20 transmits an RRC message including the BSR parameters to the terminal device 10.
  • the BSR parameters are included in the BSR-Config IE, which is an example of an RRC information element (IE).
  • the BSR-Config IE includes three timers: periodicBSR-Timer, retxBSR-Timer, and logicalChannelSR-DelayTimer.
  • the LogicalChannelConfig IE 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 channel and/or the LCG based on the LogicalChannelConfig IE included in the RRC message.
  • the LogicalChannelConfig IE includes a logicalChannelGroup IE.
  • the logicalChannelGroup IE assigns the logical channel to the LCG. For example, an LCG index (ID) may be set for each of one or more logical channels, and an LCG to which the one or more logical channels belong may be set.
  • 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.
  • the terminal device 10 may trigger the BSR according to a predetermined condition.
  • the terminal device 10 may trigger the BSR when any of the following conditions (a1) to (a4) is satisfied for an activated cell group.
  • the following conditions may be referred to as "events.”
  • (a1) For a logical channel belonging to a certain LCG, uplink data becomes available in the MAC entity and one of the following two conditions is met: The uplink data belongs to a logical channel that has a higher priority than a logical channel that contains available uplink data belonging to any LCG. There are no logical channels with available uplink data belonging to any LCG.
  • 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.
  • 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.
  • 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.
  • the BSR includes multiple formats.
  • the multiple formats include at least a short BSR and a long BSR.
  • the MAC PDU that includes the BSR includes a MAC subheader.
  • the MAC subheader includes a Logical Channel Identifier (LCID) or an extended Logical Channel Identifier (eLCID).
  • LCID Logical Channel Identifier
  • eLCID extended Logical Channel Identifier
  • 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.
  • the Short BSR is a format for reporting the buffer status (i.e., buffer size) of one LCG.
  • the Short BSR includes one field 900 having a fixed size of 8 bits.
  • the field 900 includes a first part 910 and a second part 920.
  • the first part 910 consists of 3 bits.
  • the first part 910 is information for identifying the LCG for which the buffer status is reported.
  • the first part 910 is sometimes referred to as the "LCG ID field.”
  • 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 referred to simply 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.
  • the short BSR may include a Truncated format, which is a format for logical channels with high priority (i.e., LCH priority, described below), and an Extended format, which is a format capable of transmitting a larger amount of information.
  • Truncated format which is a format for logical channels with high priority (i.e., LCH priority, described below)
  • Extended format which is a format capable of transmitting a larger amount of information.
  • the Long BSR is a format for reporting the buffer status (i.e., buffer size) of multiple LCGs. As shown in FIG. 10, the Long BSR has a variable size.
  • the Long BSR includes an LCG field 1010 and a buffer size field 1020.
  • the LCG field 1010 is composed of 8 bits. In the LCG field 1010, the 8 bits correspond to 8 LCGi, respectively.
  • i is an integer from 0 to 7.
  • the definition of i will be the same in the following explanations.
  • the LCG field 1010 may indicate whether a buffer size field for LCGi exists. For example, in the LCG field 1010, if the value of LCGi 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.
  • 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 in the LCG field 1010 is 1, and the bit corresponding to LCG2 is 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.
  • Each field included in the buffer size field 1020 consists of 8 bits. Each field indicates an index that indicates the number of bytes. For example, each field indicates one of the values from 0 to 254.
  • Long BSRs may include truncated and extended formats.
  • the BSR may also include a Pre-emptive BSR format and an Extended Pre-emptive BSR format. These formats are used in the IAB-MT.
  • 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: If two or more LCGs have available data for transmission when a MAC PDU containing a BSR is built, the terminal device 10 transmits a long BSR for all LCGs that have available data. Otherwise, the terminal device 10 transmits a short BSR.
  • 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 the LCG ID among the configured LCGs is less than or equal to 7, the terminal device 10 transmits a long BSR for all LCGs that have available data. If two or more LCGs have available data for transmission and the maximum value of the LCG ID among the configured LCGs is greater than 7, the terminal device 10 transmits an Extended long BSR for all LCGs that have available data. If one or more LCGs have available data for transmission, the terminal device 10 transmits an Extended short BSR.
  • the terminal device 10 may transmit any of the following BSR formats according to the conditions that are met: ⁇ Short BSR ⁇ Long BSR ⁇ Short Truncated BSR ⁇ Long Truncated BSR ⁇ Extended Short Truncated BSR ⁇ Extended Long Truncated BSR
  • 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.
  • 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.
  • the base station device 20 may transmit an RRC message including a LogicalChannelConfig IE.
  • the terminal device 10 may generate a MAC PDU based on the LogicalChannelConfig IE included in the RRC message.
  • the LogicalChannelConfig IE may include the following parameters. priority: a value ranging from 1 to 16, which indicates 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).
  • bucketSizeDuration (BSD) represents the bucket size duration. The bucket size is determined by PBR x BSD.
  • the terminal device 10 may execute 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 executes the above procedure until all LCH data is exhausted or the available resources in the MAC PDU are exhausted.
  • the MAC CE is basically prioritized over data from the LCH. Therefore, the terminal device 10 may allocate the MAC CE to resources in the MAC PDU before allocating the data from the LCH. However, a certain type of MAC CE may not be prioritized over data from the LCH. For example, the priority of the padding BSR may be lower than the priority of data from the LCH.
  • the base station device 20 can set a mapping restriction for the terminal device 10.
  • the above mapping restriction may be the restriction described in section 5.4.3.1 of Non-Patent Document 2.
  • the MAC entity of the terminal device 10 may select the LCH data to be assigned to the resources in the MAC PDU according to the mapping restriction.
  • the terminal device 10 may execute 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 indicates whether CG type 1 can be used for transmission.
  • allowedServingCells represents the cells that are allowed for transmission.
  • allowedCG-List represents the CGs that are allowed for transmission.
  • allowedPHY-PriorityIndex represents the index of the allowed PHY priority of the DG for transmission. Note that the details of PHY priority will be described later.
  • allowedHARQ-mode represents the allowed uplink HARQ modes for transmission.
  • the terminal device 10 can map the data of that LCH only to the MAC PDU that corresponds to the CG included in the allowedCG-List.
  • the terminal device 10 may transmit uplink transmissions with a higher priority and stop (or cancel) uplink transmissions with a lower priority. Such processing is referred to as priority processing in the terminal.
  • Priority processing in the terminal may include processing in the MAC layer and processing in the PHY layer.
  • processing in the MAC layer is referred to as “MAC layer priority processing” or “first priority processing”
  • processing in the PHY layer is referred to as “PHY layer priority processing” or "second 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.
  • the above setting may be set for a MAC cell group.
  • the above setting may be set in an IE related to a MAC cell group included in an RRC message.
  • An example of such an IE is a MAC-CellGroupConfig IE.
  • the above setting may be lch-BasedPrioritization included in the MAC-CellGroupConfig IE.
  • the lch-BasedPrioritization indicates that a first priority processing based on an LCH priority is performed.
  • the MAC entity of the terminal device 10 may perform a first priority process between multiple uplink transmissions that overlap on a time resource.
  • the terminal device 10 may determine a final priority for each uplink transmission based on the LCH priority.
  • the above final priority is referred to as "transmission priority”.
  • 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, in accordance with the mapping restriction.
  • 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, in accordance with the mapping restriction.
  • the transmission priority of an SR is the LCH priority of the LCH that triggered the SR.
  • MAC PDU 1101 corresponds to a DG-based uplink transmission (i.e., DG PUSCH).
  • DG PUSCH is, for example, a PUSCH and/or PUSCH transmission scheduled using DCI (DCI format) to which a CRC (CRC parity bit) scrambled by C-RNTI and/or MCS-C-RNTI is added.
  • DCI DCI format
  • CRC CRC parity bit
  • MAC PDU 1102 corresponds to a 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.
  • the CG PUSCH may be activated and/or deactivated using a DCI to which a CRC scrambled by the CS-RNTI is added.
  • the terminal device 10 compares the transmission priority of MAC PDU 1101 with the transmission priority of MAC PDU 1102.
  • an uplink grant that is prioritized based on the transmission priority as described above is referred to as a "prioritized uplink grant.”
  • an uplink grant that is not prioritized based on the transmission priority as described above is referred to as a “de-prioritized uplink grant.”
  • 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”.
  • the terminal device 10 may also execute the same processing as above when multiple CG-based uplink transmissions overlap on time resources. Furthermore, the terminal device 10 may also execute the same processing as above when PUCCH transmission for SR and UL-SCH transmission overlap on time resources.
  • 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.
  • 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 the 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.
  • the terminal device 10 may execute the first priority process according to the contents described in Section 5.4.1 of Non-Patent Document 2.
  • the terminal device 10 may execute the first priority process for a CG as follows.
  • the MAC entity of the terminal device 10 may determine whether all of the following conditions (b1) to (b3) are satisfied. (b1) There is no overlap with the PUSCH duration of another CG in the same BWP that has not yet been de-prioritized and has a higher LCH priority.
  • the terminal device 10 may consider a CG that satisfies the above conditions (b1) to (b3) as a "prioritized uplink grant.”
  • the terminal device 10 may consider an uplink grant that overlaps with the CG as a "non-prioritized uplink grant.”
  • the terminal device 10 may regard the CG as a "non-prioritized uplink grant.” Cancellation of uplink transmissions using a CI-RNTI will be described later.
  • 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.
  • PHY layer priority processing i.e., second priority processing
  • the PHY priority may be expressed by either the value p0 or p1. In this configuration, the priority of p1 is higher than the priority of p0.
  • the base station device 20 transmits information regarding the PHY priority to the terminal device 10.
  • 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 related to the CG included in the RRC message (e.g., a ConfiguredGrantConfig IE).
  • 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 related to SR included in the RRC message (e.g., a SchedulingRequestResourceConfig IE).
  • the base station device 20 may transmit a DCI format including the PHY priority to the terminal device 10.
  • the PHY priority may be included in the DCI format that schedules the uplink transmission.
  • 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).
  • a higher PHY priority i.e., p1
  • P0 PHY priority
  • the terminal device 10 may execute a second priority process as follows. For example, when 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. When a PUCCH transmission and a PUSCH transmission overlap on time resources, the terminal device 10 may multiplex the PUCCH into the PUSCH.
  • the base station device 20 may stop (or cancel) the uplink transmission by the terminal device 10 having a lower priority. Such processing is called priority processing between terminals.
  • 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.
  • the terminal device 10 may perform autonomous uplink transmission processing.
  • the base station device 20 may transmit to the terminal device 10 a configuration for enabling the above-mentioned autonomous uplink transmission process.
  • the above-mentioned configuration may be included in an IE related to the CG included in the RRC message.
  • the above-mentioned configuration may be autonomousTx included in the ConfiguredGrantConfig IE.
  • 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 in the terminal is a CG for which autonomousTx is set, the terminal device 10 executes an autonomous uplink transmission process.
  • multiple resources i.e., multiple transmission opportunities
  • 1201-1, 1201-2, ..., 1201-n are scheduled for CG-based uplink transmission (i.e., CG PUSCH).
  • resource 1202 is scheduled for DG-based uplink transmission (i.e., DG PUSCH).
  • the terminal device 10 regards the uplink grant corresponding to the CG PUSCH using 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 set. Note that the HPI associated with the CG PUSCH using resource 1201-1 is #0.
  • 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 executes an autonomous transmission process of the MAC PDU corresponding to the canceled CG PUSCH.
  • the configuredGrantTimer and cg-RetransmissionTimer associated with the HARQ process of the uplink grant considered to be non-priority are stopped if they are running.
  • Extended Reality The characteristics of traffic generated in XR will be described.
  • multiple types of data video data, audio data, user data, control data, etc.
  • Multiple data streams corresponding to the above data have different traffic characteristics and quality of service (QoS) requirements.
  • QoS quality of service
  • 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.
  • Reference 1 states that the following definitions can be introduced regarding transmission and reception in XR: [Reference 1] 3GPP TR 23.700-60 V1.1.0 (2022-09)
  • PDU set A set of one or more PDUs that carry the payload of one unit of information generated at the application level, which corresponds for example to a frame or a video slice in the XR service.
  • Data Burst A set of datamultiple PDUs generated and transmitted by an application in a short period of time.
  • PDB packet delay budget
  • PDU-Set Delay Budget PSDB
  • PSER PDU-Set Error Rate
  • Basic Configuration of Delay Information Report XR is expected to be operated under various requirements including a requirement of low delay. Accordingly, for 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, the terminal device 10 transmits a delay information report including delay information about predetermined data to the base station device 20.
  • the delay information report may be referred to as a "delay status report.”
  • the above-mentioned specified data means the unit of data to be reported in the delay information report.
  • the above-mentioned specified data may be referred to as "data to be reported” or "unit of data to be reported.”
  • the terminal device 10 can transmit delay information about the data to be reported to the base station device 20.
  • 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).
  • the unit of data to be reported may be a part or all of the data available for one LCG.
  • the unit of data to be reported may be data corresponding to one LCH.
  • the unit of data to be reported may be a part or all of the data available for one LCH.
  • the unit of data to be reported may be data corresponding to one PDU.
  • the unit of data to be reported may be a part or all of the data available for one PDU.
  • the unit of data to be reported may be data corresponding to one PDU set.
  • the unit of data to be reported may be a part or all of the data available for one PDU set.
  • the unit of data to be reported may be data corresponding to multiple PDU sets.
  • the unit of data to be reported may be data (or a part of data) available for one, multiple, or all PDUs (or PDU sets) belonging to one PDU set.
  • the unit of data to be reported may be data corresponding to one data burst.
  • the unit of data to be reported may be a part or all of the data available for one data burst.
  • the unit of data to be reported may be data corresponding to multiple data bursts.
  • the unit of data to be reported may be data (or a part of data) available in one, multiple, or all data (or data bursts) belonging to one data burst.
  • the delay information may include one or both of information that explicitly indicates a delay and information that implicitly indicates a delay.
  • the delay information may be a delay time or an index representing a delay time.
  • the delay information may be a remaining time until a predetermined first deadline is reached.
  • the above remaining time may be a deadline calculated based on a predetermined timer.
  • the predetermined timer may be a PDCP discard timer.
  • the delay information may be a remaining time calculated based on the PDCP discard timer.
  • the terminal device 10 may calculate the above remaining time based on the PDCP discard timer, with the time of initial transmission of the delay information report as a reference.
  • the delay information may include information regarding a plurality of remaining times.
  • the delay information may be information regarding the shortest remaining time among a plurality of remaining times.
  • the delay information may include information regarding data to which a time constraint or requirement is imposed among the data to be reported.
  • first data the entire data to be reported
  • second data the data to which a time constraint or requirement is imposed among the data to be reported
  • the delay information may be information regarding the size of the second data.
  • the delay information may be an index indicating the number of bytes of the second data.
  • 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.
  • 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.
  • 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.
  • 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 the data burst.
  • the first threshold Th1 may be set for an IE related to the data burst included in the RRC message.
  • the base station device 20 may transmit system information (SI, for example, SIB1 and/or SIBs other than SIB1) including information indicating the first threshold Th1 to the terminal device 10.
  • SIB1 and/or SIBs other than SIB1 system information
  • the second data may be data that is subject to a constraint or requirement regarding time-varying delay, such as jitter.
  • the second data may be data that is subject to a transmission rate constraint or requirement.
  • 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.
  • 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 the 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.
  • the terminal device 10 may transmit a long BSR 1400 as shown in FIG. 14.
  • the long BSR 1400 includes a first field 1410 and a second field 1420.
  • 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.
  • the second field 1420 includes three fields 1421-1423.
  • Field 1421 is a field related to LCG1.
  • Field 1421 includes a first portion 1421a and a second portion 1421b.
  • first portion 1421a is composed of 6 bits
  • second portion 1421b is composed of 2 bits.
  • first portion 1421a and second portion 1421b may each be composed of a different number of bits from this example.
  • the first portion 1421a represents the buffer size for the data corresponding to LCG1.
  • the first portion 1421a may be an index indicating the number of bytes.
  • the control unit 110 may refer to a first buffer size table for 6 bits 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.
  • the second part 1421b represents delay information (e.g., the remaining time described above) related to the data corresponding to LCG1.
  • the second part 1421b may be an index representing the delay information.
  • the control unit 110 may refer to a 2-bit delay information table to set an index in the second part 1421b.
  • the delay information table is a table that defines the correspondence between delay information and an index.
  • 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.
  • 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.
  • the order of the fields included in the second field 1420 may be determined based on the LCH priority.
  • the long BSR 1400 may include a third field indicating whether delay information is included 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.
  • 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.
  • first portion corresponding to information related to buffer size
  • second portion corresponding to delay information.
  • Field 1423 is a field related to LCG3.
  • Field 1423 includes a first portion 1423a and a second portion 1423b.
  • first portion 1423a is composed of 6 bits
  • second portion 1423b is composed of 2 bits.
  • first portion 1423a may be an index indicating the number of bytes.
  • Control unit 110 may refer to the first buffer size table described above to set the index in first portion 1423a. As described above, it is assumed that the remaining time described above is greater than first threshold value Th1 for data corresponding to LCG3.
  • second portion 1423b may be blank.
  • second portion 1423b may be a value (or index) indicating that delay information is not reported.
  • the configuration of the second field 1420 is not limited to the above example.
  • the second field 1420 may include an 8-bit field 1610 corresponding to information related to the buffer size, and an 8-bit field 1620 corresponding to delay information.
  • field 1610 represents information related to the buffer size of data corresponding to LCG1
  • field 1620 represents delay information related to the data corresponding to LCG1.
  • buffer size information and delay information related to one LCG may be represented by two different fields.
  • the above example describes the configuration of a long BSR, but is not limited to this example.
  • the above configuration may also be applied to a short BSR.
  • the terminal device 10 may transmit a short BSR that includes delay information.
  • a BSR including a delay information report has been described, this configuration is not limiting.
  • a new MAC CE that transmits delay information may be defined.
  • 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.”
  • 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.
  • SI system information
  • SIB1 system information
  • SIB1 SIB1 and/or an SIB other than SIB1
  • DCI including the first setting information to the terminal device 10.
  • 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.”
  • the first setting information may be "information indicating whether or not to transmit the remaining time.”
  • the first setting information may be "information indicating whether or not to transmit information regarding the size of the second data.”
  • the terminal device 10 may transmit a delay information report if the RRC message includes the first setting information. Also, the terminal device 10 may not transmit a delay information report if the RRC message does not include the first setting information.
  • the first configuration information may be set for an LCH.
  • the terminal device 10 may determine whether or not to include delay information related to the LCH in the BSR based on the first configuration information set for the LCH. For example, when the first configuration information indicates that delay information is to be transmitted to a certain LCH, the terminal device 10 may include the delay information related to the LCH in the BSR.
  • the first configuration information may be set as a new element of the LogicalChannelConfig IE.
  • the first configuration information may be set for an LCG.
  • the terminal device 10 may determine whether or not to include delay information related to the LCG in the BSR based on the first configuration information set for an LCG.
  • 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.
  • SI system information
  • SIB1 system information
  • SIB1 SIB1 and/or an SIB other than SIB1
  • DCI including the second setting information to the terminal device 10.
  • the second setting information may indicate the type of data to be reported.
  • the terminal device 10 selects the 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.
  • the second setting information may be explicit information indicating the type of data to be reported, or it may be implicit information indicating the type of data to be reported. Examples of explicit information and implicit information are described below.
  • the second configuration information may be information indicating any one of an LCH, an LCG, a PDU, a PDU set, and a data burst.
  • the second setting information may be the above-mentioned first setting information.
  • the terminal device 10 may select the type of data to be reported according to the IE in which the first setting information is set.
  • the first configuration information When the first configuration information is configured for a MAC cell group, this may indicate that the unit of data to be reported is data corresponding to one LCG.
  • the first configuration information may be configured in an IE related to the MAC cell group included in the RRC message.
  • An example of such an IE is the BSR-config IE.
  • the first configuration information when the first configuration information is configured for an LCG, this may indicate that the unit of data to be reported is data corresponding to one LCG.
  • the first configuration information may be configured in an IE related to the LCG.
  • An example of such an IE is the logicalChannelGroup IE.
  • the first configuration information is set for a PDU or a PDU set, this may indicate that the unit of data to be reported is data corresponding to a PDU or one or more PDU sets.
  • the first configuration information may be set in an IE related to a PDU or a PDU set included in the RRC message.
  • the first configuration information may indicate that the unit of data to be reported is data corresponding to one or more data bursts.
  • the first configuration information may be set in an IE related to a data burst included in an RRC message.
  • the terminal device 10 may control to trigger (and/or transmit) a delay information report when the RRC message includes information indicating the first threshold Th1. That is, the terminal device 10 may include a delay information report in the BSR based on the first threshold Th1 when the RRC message includes information indicating the first threshold Th1. Furthermore, the terminal device 10 may control not to trigger (and/or transmit) a delay information report when the RRC message does not include information indicating the first threshold Th1. That is, the terminal device 10 may not include a delay information report in the BSR when the RRC message does not include information indicating the first threshold Th1.
  • the MAC PDU may include identification information for identifying whether it is a delay information report.
  • the MAC subheader includes an LCID or eLCID value (i.e., a code point).
  • An LCID or eLCID value indicating a delay information report may be defined.
  • the following LCID or eLCID values may be defined based on the type of data to be reported.
  • the MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one LCH.
  • the MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one LCG.
  • the MAC CE includes a delay information report, and the unit of data to be reported is data corresponding to one PDU.
  • the MAC CE includes a delay information report, and the unit of data to be reported corresponds to one or more PDU sets.
  • the MAC CE includes a delay information report, and the unit of data to be reported corresponds to one or more data bursts
  • the BSR includes a delay information report, the following LCID or eLCID values may be defined based on the type of data being reported.
  • the BSR includes a delay information report, and the unit of data to be reported is data corresponding to one LCH.
  • the BSR includes a delay information report, and the unit of data to be reported is data corresponding to one LCG.
  • the BSR includes a delay information report, and the unit of data to be reported is data corresponding to one PDU.
  • the BSR includes a delay information report, and the unit of data to be reported corresponds to one or more PDU sets.
  • the BSR includes a delay information report, and the unit of data to be reported is data corresponding to one or more data bursts.
  • a value of LCID or eLCID may be defined that indicates whether the BSR includes a delay information report and is in one of the following formats: ⁇ Short BSR ⁇ Long BSR ⁇ Short Truncated BSR ⁇ Long Truncated BSR ⁇ Extended Short Truncated BSR ⁇ Extended Long Truncated BSR ⁇ Pre-emptive BSR ⁇ Extended Pre-emptive BSR
  • the MAC CE including the delay information report may include the above-mentioned identification information.
  • the BSR may further include a field including identification information indicating that the BSR includes delay information.
  • the terminal device 10 may trigger a delay information report according to a predetermined condition.
  • the condition is referred to as a "trigger condition.”
  • the trigger condition may include at least one of the above conditions (a1) to (a4).
  • 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 value 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.
  • FIG. 17 shows a situation similar to that of Figure 12.
  • the MAC PDU corresponding to the CG PUSCH using the resource 1201-1 includes a delay information report.
  • the delay information included in the delay information report is the above-mentioned remaining time.
  • the terminal device 10 calculates the remaining time 1701 based on the time t1 of the initial transmission.
  • the terminal device 10 regards the uplink grant corresponding to the CG PUSCH using resource 1201-1 as a "non-priority uplink grant" due to priority processing within the terminal.
  • the terminal device 10 cancels the CG PUSCH using 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 actual remaining time 1702 at time t2 when the base station device 20 receives the above-mentioned new uplink transmission differs from the remaining time 1701 calculated at time t1. This may result in the base station device 20 being unable to recognize the accurate remaining time.
  • the terminal device 10 may execute the following processing.
  • 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).
  • the terminal device 10 determines to perform the autonomous uplink transmission using a second resource that is scheduled after the first resource in which the above-mentioned uplink transmission is scheduled.
  • the first resource may be referred to as a "first CG resource”
  • 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 above-mentioned autonomous uplink transmission.
  • At least a portion 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 modify at least a portion of the MAC PDU that was not transmitted using the first resource to generate a MAC PDU for autonomous uplink transmission.
  • the above information generated for autonomous uplink transmission may be a part or the whole of the MAC CE.
  • the terminal device 10 may generate a MAC CE for autonomous uplink transmission by modifying at least a part of the MAC CE that was not transmitted using the first resource.
  • the time (or period) of the first resource i.e., the first CG resource
  • the time (or period) of the first 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.
  • the time (or period) of the second resource may be referred to as the "autonomously retransmitted time (or period)."
  • the time (or period) 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, as described above.
  • the control unit 110 of the terminal device 10 regenerates the delay information report as information for the above-mentioned autonomous uplink transmission.
  • FIG. 18 shows a similar situation to FIG. 17.
  • resource 1201-1 is referred to as “first resource 1201-1”
  • resource 1201-n is referred to as “second resource 1201-n.”
  • the control unit 110 of the terminal device 10 calculates the remaining time based on the time t1 (i.e., the time of initial transmission) of the first resource 1201-1.
  • the remaining time may be a value calculated based on a predetermined timer (e.g., a PDCP discard timer) based on the time t1 as described above.
  • the control unit 110 generates a delay information report including the remaining time.
  • the control unit 110 executes priority processing within the terminal (1801).
  • 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" through the priority processing within the terminal.
  • the control unit 110 decides to perform autonomous uplink transmission using the second resource 1201-n associated with the same HPI as the first resource 1201-1.
  • control unit 110 generates information for autonomous uplink transmission. Specifically, the control unit 110 recalculates the remaining time described above 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 in the CG PUSCH using the second resource 1201-n (1802).
  • the above configuration makes it possible to prevent the terminal device 10 from sending 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 send a delay information report that includes accurate information.
  • a delay information report that includes inappropriate information (e.g., the remaining time).
  • 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). In other words, 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.
  • the above configuration can prevent the terminal device 10 from sending a delay information report that includes inappropriate information (e.g., remaining time).
  • 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 in the CG PUSCH using the second resource 1201-n (1802).
  • the above configuration can prevent the terminal device 10 from sending a delay information report that includes inappropriate information (e.g., remaining time).
  • 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 in the CG PUSCH using the second resource 1201-n (1802). Note that the size of the BSR generated here may be the same as the size of the delay information report.
  • the above configuration can 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 the buffer status to the base station device 20.
  • the base station device 20 can allocate radio resources using the BSR.
  • 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.
  • 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 setting information related to a mapping restriction for the delay information report.
  • the third setting 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 setting 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).
  • the third setting information may include information (e.g., index) of a CG for which mapping is permitted.
  • the information of the CG may be a list or sequence of CGs for which mapping is permitted. If the third setting information exists, the delay information report may be mapped only to the indicated CG. Also, if the size of the sequence is zero, the delay information report may not be mapped to any CG. If the third setting information does not exist, the delay information report may be mapped to any CG.
  • 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.
  • the uplink grant corresponding to the CG PUSCH for transmitting the delay information report is less likely to be regarded as a "non-priority uplink grant". That is, the possibility of autonomous uplink transmission processing being performed is reduced. It is possible to prevent the terminal device 10 from transmitting a delay information report including inappropriate information (e.g., remaining time).
  • 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 set (i.e., a CG in which autonomousTx is not set). With this configuration, autonomous uplink transmission processing including a 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).
  • the CG information may be information indicating that the delay information report is mapped to CG type 1.
  • the third setting information may include information of a DG for which mapping is permitted (e.g., PHY priority).
  • the information of the DG may be information indicating that the delay information report is mapped to a DG having a specific PHY priority. If the third setting information exists and the DG has a PHY priority, the delay information report may be mapped only to a DG that indicates a PHY priority equal to the set value. If the third setting information exists 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 setting information does not exist, the delay information report may be mapped to any DG.
  • the information of the DG may be information indicating that the delay information report is mapped to a DG having a PHY priority that is a value p1.
  • the uplink grant corresponding to the DG PUSCH for transmitting the delay information report is less likely to be regarded as a "non-priority uplink grant".
  • the terminal device 10 can transmit the delay information report on the DG PUSCH.
  • the third setting information may include information on a PUSCH duration for which mapping is permitted.
  • the information on the PUSCH duration 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.
  • the delay information report is mapped to a resource of an uplink grant having a PUSCH duration equal to or less than a value set as the maximum PUSCH duration. For example, when the maximum PUSCH duration is smaller, the possibility that multiple uplink transmissions overlap on time resources is reduced. In this case, the priority process itself in the terminal is not performed, and therefore, an autonomous uplink transmission process including the delay information report is not performed.
  • the terminal device 10 can transmit a delay information report in a resource corresponding to the uplink grant without performing priority process in the terminal.
  • 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.
  • 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 the "first uplink transmission”.
  • the uplink grant corresponding to the first uplink transmission is referred to as the "first uplink grant”.
  • the first uplink transmission is scheduled in the first resource 2001.
  • 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.
  • the uplink transmission that transmits the uplink data is called the "second uplink transmission.”
  • the uplink grant corresponding to the second uplink transmission is called the “second uplink grant.”
  • the second uplink transmission is scheduled in the second resource 2002.
  • the control unit 110 executes priority processing within the terminal (S2102). Through 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 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.”
  • the control unit 110 generates a MAC PDU corresponding to the second uplink transmission.
  • 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 a second uplink transmission including the delay information report to the base station device 20.
  • 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.
  • the control unit 110 may cancel the trigger of the delay information report.
  • the control unit 110 may cancel the trigger of the delay information report when a MAC PDU including a delay information report is generated and/or transmitted.
  • 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 in S2102 is regarded as a non-priority uplink grant.
  • the control unit 110 includes the delay information report in the MAC PDU corresponding to the second uplink transmission (S2103).
  • the control unit 110 may calculate the delay information (e.g., remaining time) included in the delay information report based on the time of initial transmission of each uplink grant.
  • the remaining time may be a value calculated based on a predetermined timer (e.g., PDCP discard timer) with the time of initial transmission as a reference, as described above.
  • the control unit 110 may calculate the 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 the 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.
  • the delay information e.g., remaining time
  • the control unit 110 includes a delay information report in the 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.
  • This embodiment is not limited to this example.
  • the control unit 110 may perform processing in a flow as shown in FIG. 22.
  • the control unit 110 generates a MAC PDU corresponding to the first uplink transmission.
  • the control unit 110 includes a delay information report in the MAC PDU (S2201).
  • the control unit 110 generates a MAC PDU corresponding to the second uplink transmission.
  • the control unit 110 includes a delay information report in the MAC PDU (S2202).
  • the control unit 110 executes priority processing in the terminal (S2203).
  • 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.
  • the control unit 110 includes the delay information report in the second link transmission that overlaps with the first uplink transmission in terms of time resources.
  • 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 is later than the first resource 2001.
  • the third resource 2003 may be the next resource associated with the same HPI as the first resource 2001.
  • the third resource 2003 may be the next resource associated with a different HPI than the first resource 2001.
  • Information transmitted and received in the above embodiment may be contained and transmitted in the same or a different message or the same or a different element already described in the technical specifications, or may be contained and transmitted in a newly defined message or element.
  • Information transmitted and received in the above embodiment may be transmitted and received using a layer and/or a different channel different from those in the above embodiment.
  • the means and/or functions provided by the devices described in the above embodiments can be provided by software recorded in a physical memory device and a computer that executes the software, by software alone, by hardware alone, or by a combination of these.
  • any of the above devices is provided by electronic circuits that are hardware, it can be provided by digital circuits including a large number of logic circuits, or by analog circuits.
  • the device described in the above embodiment executes a program stored on a non-transitory tangible storage medium. Execution of this program results in the execution of a method corresponding to the program.
  • a terminal device comprising:
  • the second uplink grant is an uplink grant that is considered to be a prioritized uplink grant based on the priority processing.
  • the control unit is Calculating the delay information of the delay information report included in the first uplink transmission based on a time of the first resource; and calculating the delay information of the delay information report included in the second uplink transmission based on a time of the second resource.
  • the control unit is The delay information report included in the first uplink transmission is configured to be included in the second uplink transmission. 3. A terminal device as described in claim 2.
  • the control unit is and including the delay information report in a Medium Access Control Protocol Data Unit (MAC PDU) corresponding to the second uplink transmission after the first uplink grant is deemed to be the non-prioritized uplink grant based on the priority processing.
  • MAC PDU Medium Access Control Protocol Data Unit
  • the control unit is and including the delay information report in a Medium Access Control Protocol Data Unit (MAC PDU) corresponding to the second uplink transmission before the priority processing.
  • MAC PDU Medium Access Control Protocol Data Unit
  • the second uplink transmission comprises: the first uplink transmission is an uplink transmission occurring on a second resource that does not overlap with a first scheduled resource and is scheduled after the first resource. 2.
  • the control unit is and canceling the trigger of the delay information report when it is determined that the second uplink transmission is transmittable at a physical (PHY) layer.
  • PHY physical
  • the delay information includes information regarding a remaining time calculated based on a predetermined timer. 9.
  • a terminal device according to any one of appendix 1 to 8.
  • the delay information report is a Buffer Status Report (BSR) including the delay information and buffer size information regarding a buffer size. 10.
  • BSR Buffer Status Report
  • the BSR is a field containing the delay information and the buffer size information; a field containing said buffer size information and not containing said delay information; Including, 11.
  • the control unit is configured to generate a Medium Access Control Protocol Data Unit (MAC PDU) including the delay information report, Identification information for identifying the delay information report is included in a MAC CE or a header included in the MAC PDU, 12.
  • MAC PDU Medium Access Control Protocol Data Unit
  • Identification information for identifying the delay information report is included in a MAC CE or a header included in the MAC PDU, 12.
  • a terminal device according to any one of appendix 1 to 11.
  • the delay information is delay information for predetermined data
  • 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. 13.
  • a terminal device according to any one of appendix 1 to 12.
  • a method for a terminal device comprising:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2024/018456 2023-07-26 2024-05-20 端末装置及び端末装置の方法 Pending WO2025022773A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2025535587A JPWO2025022773A1 (https=) 2023-07-26 2024-05-20

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023121582 2023-07-26
JP2023-121582 2023-07-26

Publications (1)

Publication Number Publication Date
WO2025022773A1 true WO2025022773A1 (ja) 2025-01-30

Family

ID=94374759

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/018456 Pending WO2025022773A1 (ja) 2023-07-26 2024-05-20 端末装置及び端末装置の方法

Country Status (2)

Country Link
JP (1) JPWO2025022773A1 (https=)
WO (1) WO2025022773A1 (https=)

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
JUHA KORHONEN, NOKIA, QUALCOMM (RAPPORTEURS): "XR Enhancements", 3GPP DRAFT; R2-2306920; TYPE DRAFTCR; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 2 June 2023 (2023-06-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052383791 *
LI QIANG, HUAWEI, HISILICON: "Discussion on MAC enhancements for XR-specific capacity improvement", 3GPP DRAFT; R2-2306130; TYPE DISCUSSION; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052315345 *
NAVEEN PALLE, APPLE: "Views on BSR Enhancements for XR", 3GPP DRAFT; R2-2305073; TYPE DISCUSSION; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052314299 *
RICHARD TANO, ERICSSON: "Discussion on BSR enhancements for XR", 3GPP DRAFT; R2-2305828; TYPE DISCUSSION; NR_XR_ENH, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 11 May 2023 (2023-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052315047 *
SUDEEP PALAT, INTEL CORPORATION: "BSR Enhancements for XR Traffic", 3GPP DRAFT; R2-2305495; TYPE DISCUSSION; NR_XR_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Incheon, KR; 20230522 - 20230526, 12 May 2023 (2023-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052314717 *

Also Published As

Publication number Publication date
JPWO2025022773A1 (https=) 2025-01-30

Similar Documents

Publication Publication Date Title
RU2754679C2 (ru) Система, устройство и способ передачи данных
WO2018103702A1 (zh) 一种上行信息处理的方法及装置
CN102595600A (zh) 半静态调度方法、用户设备及网络设备
US20250358814A1 (en) Terminal apparatus, method of terminal apparatus and base station apparatus
WO2019213953A1 (zh) 一种通信方法和通信装置
US20250234416A1 (en) Terminal apparatus, method of terminal apparatus and base station apparatus
CN112753272B (zh) 无线通信系统中发送和接收信号的方法及支持该方法的装置
JP7827146B2 (ja) 端末装置、基地局装置、及び方法
JP7798236B2 (ja) 端末装置及び端末装置の方法
JP7782756B2 (ja) 端末装置及び端末装置の方法
WO2025022773A1 (ja) 端末装置及び端末装置の方法
WO2025022772A1 (ja) 端末装置及び端末装置の方法
WO2023248667A1 (ja) 端末装置、基地局装置、及び端末装置における方法
JP7758232B2 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025070068A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025070067A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2024154462A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025234285A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2024095792A1 (ja) 端末装置及び基地局装置
WO2025234286A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2025094646A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025164131A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2026009628A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2026009629A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2024209828A1 (ja) 端末装置、端末装置の方法、及び、基地局装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24845157

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025535587

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025535587

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE