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

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

Info

Publication number
WO2024209893A1
WO2024209893A1 PCT/JP2024/009669 JP2024009669W WO2024209893A1 WO 2024209893 A1 WO2024209893 A1 WO 2024209893A1 JP 2024009669 W JP2024009669 W JP 2024009669W WO 2024209893 A1 WO2024209893 A1 WO 2024209893A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
data
lcg
delay information
dsr
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.)
Ceased
Application number
PCT/JP2024/009669
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 JP2025512464A priority Critical patent/JP7798236B2/ja
Priority to CN202480023526.3A priority patent/CN120898497A/zh
Priority to EP24784688.4A priority patent/EP4694475A1/en
Publication of WO2024209893A1 publication Critical patent/WO2024209893A1/ja
Priority to US19/347,247 priority patent/US20260032661A1/en
Anticipated expiration legal-status Critical
Ceased 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/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1221—Wireless traffic scheduling based on age of data to be sent
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

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
  • Non-Patent Document 2 describes the procedure for buffer status reporting (BSR).
  • Non-Patent Document 3 describes parameters for the BSR, which are transmitted from the base station device.
  • the BSR indicates the buffer size of uplink data for specific data.
  • the above specific data is data corresponding to one Logical Channel Group (LCG).
  • the terminal device calculates the buffer size for each LCG, and transmits a BSR including the calculated buffer size to the base station device.
  • the base station device allocates radio resources to the terminal device based on the BSR.
  • XR is expected to be operated under various requirements, including the requirement of low latency. Accordingly, for uplink communication from a terminal device, it is required to allocate radio resources taking the above requirements into consideration.
  • the terminal device can only transmit one piece of information for specific data (i.e., information on buffer size). Since the amount of information reported to the base station device is small, there is a possibility that the base station device will not be able to appropriately allocate radio resources to the terminal device. Therefore, it is being considered to report specific information (e.g., information on delay) in addition to the buffer size in the BSR. Furthermore, it is also being considered to report the above specific information to the base station device using a reporting method other than the BSR.
  • Non-Patent Documents 2 and 3 do not describe such a procedure. Note that the above-mentioned problem also occurs in ordinary terminal devices and base station devices other than those that implement XR.
  • the present disclosure provides technology that can appropriately determine whether to trigger or send a report of specified information.
  • the terminal device of the present disclosure includes a receiving unit that receives a Radio Resource Control (RRC) message from a base station device, the RRC message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs, and information indicating a threshold value for the LCG data for controlling the triggering of a Delay Status Report (DSR), and a control unit that controls the triggering of the DSR based on the remaining time for the earliest expiration of the LCG data being below the threshold value and the DSR for the LCG data not being transmitted.
  • the control unit cancels the DSR that has been triggered and has not been canceled when the expiration date of the LCG data associated with the DSR has expired.
  • the method of the terminal device disclosed herein includes receiving a Radio Resource Control (RRC) message from a base station device, the Radio Resource Control (RRC) message including information for setting an identifier (ID) of a Logical Channel Group (LCG) to which a Logical Channel (LCH) belongs and information indicating a threshold value for the LCG data for controlling triggering of a Delay Status Report (DSR), controlling triggering of the DSR based on the remaining time for the earliest expiration of the LCG data being below the threshold value and the DSR for the LCG data not being transmitted, and canceling the DSR that has been triggered and not canceled when the expiration of the LCG data associated with the DSR has expired.
  • RRC Radio Resource Control
  • the above configuration allows an appropriate decision to be made as to whether or not to trigger or transmit a delay information report. 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 sequence diagram showing a process flow of the terminal device 10 and the base station device 20 according to the first embodiment.
  • FIG. 12 is a diagram showing an example of the configuration of a long BSR including delay information;
  • FIG. 13 is a diagram showing another example of the configuration of a long BSR including delay information;
  • FIG. 14 is a diagram showing another example of the configuration of a long BSR including delay information;
  • FIG. 15 is a diagram showing an example in which a delay information report is transmitted;
  • FIG. 16 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 1-1 of the first embodiment.
  • FIG. 17 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 1-2 of the first embodiment.
  • FIG. 18 is a sequence diagram showing a processing flow of the terminal device 10 according to a modification of the first embodiment.
  • FIG. 19 is a sequence diagram showing a processing flow of the terminal device 10 according to aspect 2-1 of the second embodiment.
  • FIG. 20 is a sequence diagram showing the flow of processing of the terminal device 10 according to aspect 2-2 of the second 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 other interfaces with different functions and names.
  • 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. Also, 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 a wireless interface 104 and an 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.
  • the transmission method for downlink communication from the base station device 20 to the terminal device 10 is, for example, Orthogonal Frequency Division Multiplexing (OFDM) using a Cyclic Prefix (CP), i.e., CP-OFDM.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix
  • the transmission method for uplink communication from the terminal device 10 to the base station device 20 is, for example, the above-mentioned CP-OFDM, or DFTS-OFDM in which CP-OFDM is applied after Transform Precoding that performs Discrete Fourier Transform (DFT) spreading.
  • DFT Discrete Fourier Transform
  • the cyclic prefix is a redundant signal that functions as a guard period (GP) to prevent inter-symbol interference and inter-carrier interference, and is inserted at the beginning of an OFDM symbol.
  • GP guard period
  • 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 contained 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.
  • a resource element (RE) is a radio resource unit in the time-frequency domain consisting of one subcarrier and one symbol.
  • a resource block (RB) is a radio resource unit in the time-frequency domain consisting of 12 subcarriers and multiple symbols.
  • 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 with 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 set one or more bandwidth parts (Bandwidth Part, BWP) for the terminal device 10 with respect to 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.
  • DCI downlink control information
  • the DCI includes information regarding the allocation of downlink and uplink resources to 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 transport channel DL-SCH.
  • 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 parameters of CG to the terminal device 10.
  • the parameters of CG are included in ConfiguredGrantConfig IE, which is an example of an information element (IE) of RRC.
  • 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).
  • FPS 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.
  • the terminal device 10 transmits the BSR by MAC signaling using the allocated radio resources of the PUSCH.
  • 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.
  • logical channels are assigned to logical channel groups (LCGs).
  • LCGs logical channel groups
  • Each LCG includes one or more logical channels.
  • the terminal device 10 calculates the buffer size of the uplink data for each LCG.
  • the terminal device 10 transmits the buffer size corresponding to each LCG as a BSR to the base station device 20.
  • 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 a logical channel to an 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 the logical channel containing 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 high-priority logical channels, and an 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 is 1 and the bit corresponding to LCG2 is 1 in the LCG field 1010. Therefore, the buffer size field 1020 includes a field 1021 corresponding to LCG1 and a field 1022 corresponding to LCG2. Note that, since it is assumed that the bit corresponding to LCG0 is 0 in FIG. 10, the buffer size field 1020 does not include a field corresponding to LCG0.
  • 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 may execute the following processing. For example, if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate a BSR MAC CE and its subheader as a result of LCP (Logical Channel Prioritization), the terminal device 10 may generate a BSR MAC CE and transmit the BSR MAC CE.
  • LCP Logical Channel Prioritization
  • the terminal device 10 may trigger an SR when the following condition (b1) or (b2) is satisfied.
  • (b1) There are no UL-SCH resources available for a new transmission.
  • (b2) The UL-SCH resources available for the new transmission do not satisfy the LCP mapping restriction configured for the logical channel that triggered the BSR.
  • the above LCP mapping restriction may be the restriction described in section 5.4.3.1 of Non-Patent Document 2.
  • the above restriction may be a restriction set by the RRC.
  • the above restriction may include, for example, at least one of a restriction on the allowed subcarrier spacing for transmission (e.g., allowedSCS-List), a restriction on the maximum PUSCH duration allowed for transmission (e.g., maxPUSCH-Duration), a restriction on whether CG type 1 can be used for transmission (e.g., configuredGrantType1Allowed), a restriction on the cells allowed for transmission (e.g., allowedServingCells), a restriction on the CGs allowed for transmission (e.g., allowedCG-List), a restriction on the allowed PHY priority index of the dynamic grant (DG) for transmission (e.g., allowedPHY-PriorityIndex), and a restriction on the allowed uplink HARQ mode for transmission (e.g., allowedHARQ-mode).
  • a restriction on the allowed subcarrier spacing for transmission
  • the terminal device 10 may cancel all the triggered BSRs. Furthermore, when the following condition (c2) is satisfied, the terminal device 10 may cancel all the BSRs triggered before the MAC PDU assembly.
  • the uplink grant can accommodate all pending data available for transmission, but is insufficient to additionally accommodate the BSR MAC CE and its subheader.
  • a MAC PDU is transmitted, the MAC PDU containing a long, extended long, short, or extended short BSR MAC CE, the BSR MAC CE containing the buffer status up to (and including) the last event that triggered a BSR prior to MAC PDU assembly.
  • 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
  • the terminal device can transmit only one piece of information (i.e., information on the buffer size) for a given piece of data (i.e., uplink data corresponding to one LCG). Since the amount of information reported to the base station device is small, there is a possibility that the base station device cannot appropriately allocate radio resources to the terminal device.
  • this embodiment provides a procedure for transmitting information regarding delay by the terminal device 10.
  • the "information regarding delay” is referred to as “delay information”.
  • the terminal device 10 transmits a report including delay information about specified data to the base station device 20.
  • the "report including delay information” is referred to as a “delay information report”.
  • the delay information report may also be referred to as a "Delay Status Report (DSR)".
  • 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 be information that explicitly indicates a delay.
  • the delay information may be a delay time.
  • the delay information may be an index that represents the delay time.
  • the delay information may also be other time-related information.
  • the delay information may be information related to a time limit of transmission of data.
  • the transmission limit may be referred to as a "transmission deadline" or an "upper bound of delay.”
  • the delay information may be the remaining time until a predetermined first deadline is reached.
  • the first deadline may be a deadline by which the transmission of a part or the whole of the data to be reported must be completed.
  • the first deadline may be the earliest deadline among a plurality of deadlines by which the transmission of a part of the data to be reported must be completed.
  • the first deadline may be a deadline determined based on the PDB or PSDB.
  • the PDB or PSDB may be determined based on the corresponding QoS flow.
  • the PDB or PSDB may be provided to the terminal device 10 by the core network 30.
  • the first deadline for a PDU set may be a value obtained by adding the PDB or PSDB of the corresponding QoS flow to the time when data corresponding to a PDU in the PDU set is first buffered in the terminal device 10 or first arrives at the MAC entity.
  • the first deadline for a data burst may be a value obtained by adding the PDB or PSDB of the corresponding QoS flow to the time when data corresponding to a PDU constituting the data burst is first buffered in the terminal device 10 or first arrives at the MAC entity.
  • the remaining time may be a value obtained by subtracting the period during which the specified data (i.e., the data to be reported) is buffered in the terminal device 10 from the PDB or PSDB of the corresponding QoS flow.
  • the remaining time may be the period from a predetermined first time to the first deadline.
  • the first time may be the current time.
  • the first time may be the time when an uplink grant for transmitting a delay information report is assigned.
  • the first time may be the time when the predetermined data (i.e., the data to be reported) is buffered in the terminal device 10.
  • the first time may be the time when the data to be reported arrives at the MAC entity in the terminal device 10.
  • the first deadline may be obtained by adding the PDB or PSDB to the first time.
  • the delay information may be information that implicitly indicates a delay.
  • the delay information may be information about 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 about 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-dependent changes in 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 terminal device 10 may transmit a MAC CE including delay information as a delay information report.
  • the terminal device 10 may transmit a BSR including a delay information report.
  • the terminal device 10 may transmit a BSR including a 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 (S1101).
  • the RRC message includes parameters related to the BSR.
  • the RRC message may be an RRCReconfiguration message.
  • the control unit 110 of the terminal device 10 generates a BSR based on the parameters included in the RRC message.
  • the BSR includes buffer size information related to the buffer size and delay information.
  • the communication unit 120 of the terminal device 10 transmits the BSR (S1102).
  • the terminal device 10 may transmit a long BSR 1200 as shown in FIG. 12.
  • the long BSR 1200 includes a first field 1210 and a second field 1220.
  • the first field 1210 may have the same configuration as the LCG field 1010 in FIG. 10.
  • the first field 1210 may also be a field indicating whether the LCGi has available data. For example, if the value of LCGi in the first field 1210 is 1, this may indicate that the LCGi has available data. If the value of LCGi is 0, this may indicate that the LCGi does not have available data.
  • the second field 1220 includes three fields 1221 to 1223.
  • Field 1221 is a field related to LCG1.
  • Field 1221 includes a first portion 1221a and a second portion 1221b.
  • first portion 1221a is composed of 6 bits
  • second portion 1221b is composed of 2 bits.
  • first portion 1221a and second portion 1221b may each be composed of a different number of bits from this example.
  • the first portion 1221a represents the buffer size for the data corresponding to LCG1.
  • the first portion 1221a 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 1221a.
  • the first buffer size table is a table that defines the correspondence between the buffer size and the index.
  • the second part 1221b represents delay information related to the data corresponding to LCG1.
  • the second part 1221b 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 1221b.
  • the delay information table is a table that defines the correspondence between delay information and an index.
  • Field 1222 is a field related to LCG2.
  • Field 1222 includes a first portion 1222a and a second portion 1222b.
  • the configurations of first portion 1222a and second portion 1222b are the same as those of first portion 1221a and second portion 1221b described above.
  • Field 1223 is a field related to LCG3.
  • Field 1223 indicates the buffer size related to the data corresponding to LCG3. It is assumed that the remaining time for the data corresponding to LCG3 is greater than the first threshold Th1. That is, the data corresponding to LCG3 is not delayed.
  • field 1223 includes information related to the buffer size and does not need to include delay information.
  • the control unit 110 may refer to a second buffer size table for 8 bits to set an index in field 1223.
  • the second buffer size table is a table that defines the correspondence between the buffer size and the index. In this way, the control unit 110 may switch between the first buffer size table and the second buffer size table to set an index corresponding to the information related to the buffer size.
  • the second field 1220 includes three fields 1221 to 1223, but is not limited to this configuration.
  • the number of fields included in the second field 1220 may be variable.
  • the order of the fields included in the second field 1220 may be determined based on priority.
  • each of fields 1221 to 1223 included in second field 1220 may include a first portion corresponding to information related to buffer size and a second portion corresponding to delay information.
  • first portion corresponding to information related to buffer size
  • second portion corresponding to delay information.
  • Field 1223 is a field related to LCG3.
  • Field 1223 includes a first portion 1223a and a second portion 1223b.
  • first portion 1223a is composed of 6 bits
  • second portion 1223b is composed of 2 bits.
  • first portion 1223a 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 1223a. 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 1223b may be blank.
  • second portion 1223b may be a value (or index) indicating that delay information is not reported.
  • the configuration of the second field 1220 is not limited to the above example.
  • the second field 1220 may include an 8-bit field 1410 corresponding to information related to the buffer size, and an 8-bit field 1420 corresponding to delay information.
  • field 1410 represents information related to the buffer size of data corresponding to LCG1
  • field 1420 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 present invention is not limited to this example.
  • the above configuration may be applied to a short BSR.
  • the terminal device 10 may transmit a short BSR including delay information (e.g., the buffer size of the second data).
  • a BSR including a delay information report has been described, this configuration is not limiting.
  • a new MAC CE for transmitting delay information may be defined.
  • the terminal device 10 may transmit a MAC CE including delay information as a delay information report. Therefore, the "transmission of a BSR including delay information" described in this specification may be replaced with "transmission of 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 terminal device 10 may transmit delay information when the RRC message includes the first setting information.
  • the terminal device 10 may not transmit delay information when the RRC message does not include the first setting information.
  • the first setting 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 setting information set for the LCH.
  • the terminal device 10 may include delay information related to the LCH in the BSR.
  • the first setting information may be set as a new element of the LogicalChannelConfig IE.
  • the first setting information may be set for an LCG.
  • the terminal device 10 may determine whether or not to include delay information related to an LCG in the BSR based on the first setting information set for the LCG.
  • the terminal device 10 may include delay information related to the LCG in the BSR.
  • the first setting information may be set as a new element of the logicalChannelGroup IE.
  • the first setting information may be set for a PDU or a PDU set.
  • the terminal device 10 may determine whether or not to include delay information related to the PDU or the PDU set in the BSR based on the first setting information set for the PDU or the PDU set. For example, when the first setting information indicates that delay information is to be transmitted for a certain PDU or a PDU set, the terminal device 10 may include delay information related to the PDU or the PDU set in the BSR.
  • the first setting information may be set in an IE related to a PDU or a PDU set included in the RRC message.
  • the first setting information may be set for a data burst.
  • the terminal device 10 may determine whether or not to include delay information related to the data burst in the BSR based on the first setting information set for the data burst. For example, if the first setting information indicates that delay information is to be transmitted for a certain data burst, the terminal device 10 may include the delay information for the data burst in the BSR.
  • the first setting information may be set in an IE related to the data burst included in the RRC message.
  • 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 corresponds 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 (d1) to (d4).
  • (d1) There is data whose remaining time is equal to or less than a first threshold value Th1.
  • (d2) The on-duration of discontinuous reception (DRX) has started.
  • (d3) There is a PDU set or a data burst to be transmitted, or a PDU set or a data burst has been buffered.
  • (d4) The PDU set is discarded.
  • the terminal device 10 triggers a delay information report due to condition (d1).
  • the unit of data to be reported is data corresponding to an LCG.
  • the first threshold Th1 is 5 ms.
  • the terminal device 10 triggers a delay information report.
  • the delay information report includes information on the remaining time as delay information for each LCG.
  • the base station device 20 receives the delay information report and recognizes that the remaining time of the data corresponding to LCG1 is 5 ms and that the remaining time of the data corresponding to LCG2 is 8 ms.
  • delay information reports are unnecessarily triggered, which may increase the communication load (i.e., overhead). Note that such a problem may occur under conditions other than condition (d1), for example, conditions (a1) to (a4) and (d2) to (d4). It is necessary to prevent unnecessary delay information reports from being frequently triggered.
  • the terminal device 10 determines whether to trigger (or transmit) a delay information report using a predetermined condition that restricts the transmission of the delay information report.
  • the condition is referred to as a "restriction condition.”
  • the restriction condition includes at least one of the following conditions (e1) and (e2): (e1) The first timer is running. (e2) A delay information report for the currently triggered given data has already been sent.
  • the terminal device 10 does not trigger or transmit a delay information report. If the restrictive condition is not satisfied in a situation where the trigger condition is satisfied, the terminal device 10 triggers or transmits a delay information report. Details of each of aspect 1-1 in which condition (e1) is used and aspect 1-2 in which condition (e2) is used are described below.
  • the above-mentioned first timer is a timer for setting a period during which a delay information report is not triggered or transmitted.
  • the first timer is a prohibition timer for prohibiting triggering or transmitting a delay information report.
  • the first timer expires at a predetermined period.
  • the period of the first timer may be selected from among a plurality of values.
  • the terminal device 10 does not trigger or transmit a delay information report while the first timer is running. When the first timer is not running, the terminal device 10 triggers or transmits a delay information report.
  • the terminal device 10 may control to trigger (and/or transmit) a delay information report when the RRC message includes information indicating the first timer.
  • the terminal device 10 may not trigger or transmit a delay information report while the RRC message includes information indicating the first timer and the first timer is running. Furthermore, the terminal device 10 may trigger or transmit a delay information report while the RRC message includes information indicating the first timer and the first timer is not running. Furthermore, the terminal device 10 may perform control so as not to trigger or transmit a delay information report when the RRC message does not include information indicating the first timer.
  • the control unit 110 determines whether the trigger condition is satisfied (S1601).
  • the trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not send a delay information report.
  • the control unit 110 determines whether the condition (e1) is met (S1602). If the condition (e1) is met, the communication unit 120 does not send a delay information report. On the other hand, if the condition (e1) is not met, the communication unit 120 sends a delay information report (S1603).
  • 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 control unit 210 may preferentially allocate radio resources to data that is experiencing a delay.
  • condition (e1) may be applied to a specific condition among the trigger conditions.
  • condition (e1) may be applied to condition (d1).
  • condition (d1) if condition (d1) is satisfied and condition (e1) is satisfied, the communication unit 120 does not transmit a delay information report. If condition (d1) is satisfied and condition (e1) is not satisfied, the communication unit 120 transmits a delay information report. If at least one of conditions (a1) to (a4) and (d2) to (d4) is satisfied, the communication unit 120 may transmit a delay information report without determining condition (e1). In another example, if condition (d1) is satisfied, the terminal device 10 may start or restart the first timer.
  • condition (a1) to (a4) and (d2) to (d4) are satisfied, the terminal device 10 may not start or restart the first timer.
  • Condition (d1) is more likely to result in the transmission of delay information reports more frequently than other conditions. This configuration can effectively prevent unnecessary delay information reports from being frequently triggered.
  • condition (e1) may be applied to a BSR that includes a delay information report, and condition (e1) may not be applied to a BSR that does not include a delay information report (i.e., the BSR shown in FIG. 9 or FIG. 10). Therefore, even if condition (e1) is satisfied, communication unit 120 may transmit a BSR that does not include a delay information report.
  • the first timer may be started or restarted upon triggering or transmitting a delay information report.
  • the first timer may be started or restarted upon triggering or transmitting the BSR.
  • the first timer may be started or restarted upon triggering or transmitting a BSR that includes a delay information report. That is, the first timer may not be started or restarted upon triggering or transmitting a BSR that does not include a delay information report.
  • the first timer may be used as a period during which the SR is not triggered or transmitted. That is, the terminal device 10 does not trigger or transmit an SR while the first timer is running.
  • the terminal device 10 may store information related to the first timer in advance in the terminal device 10 itself.
  • the terminal device 10 may receive information related to the first timer from the base station device 20.
  • the base station device 20 may select one value from among multiple values related to the first timer and transmit the selected value to the terminal device 10.
  • the base station device 20 may transmit an RRC message including information related to the first timer to the terminal device 10.
  • the base station device 20 may transmit system information (SI, for example, SIB1 and/or SIBs other than SIB1) including information related to the first timer to the terminal device 10.
  • SIB1 system information
  • Information regarding the first timer may be included in parameters related to the BSR.
  • information regarding the first timer may be included in a BSR-config IE.
  • the first timer may be set for an LCH or an LCG.
  • Information regarding the first timer may be set in an IE related to the LCH or the LCG. Examples of such IEs include the LogicalChannelConfig IE and the logicalChannelGroup IE.
  • the first timer is started or restarted when a delay information report is triggered or transmitted for the LCH or the LCG for which the first timer is set.
  • a delay information report is not triggered or transmitted for the LCH or the LCG for which the first timer is set.
  • the first timer may be set for a PDU or a PDU set.
  • Information about the first timer may be set in an IE related to the PDU or the PDU set.
  • information about the first timer may be set in an IE related to the PDU or the PDU set included in an RRC message.
  • the first timer is started or restarted when a delay information report is triggered or transmitted for the PDU or the PDU set for which the first timer is set.
  • a delay information report is not triggered or transmitted for the PDU or the PDU set for which the first timer is set.
  • the first timer may be set for the data burst.
  • Information about the first timer may be set in an IE related to the data burst.
  • information about the first timer may be set in an IE related to the data burst included in an RRC message.
  • the first timer is started or restarted when a delay information report is triggered or transmitted for the data burst for which the first timer is set.
  • a delay information report is not triggered or transmitted for the data burst for which the first timer is set.
  • the terminal device 10 may receive third setting information related to the delay information report from the base station device 20.
  • the base station device 20 may transmit an RRC message including the third setting information to the terminal device 10.
  • the base station device 20 may transmit system information (SI, for example, SIB1 and/or an SIB other than SIB1) including the third setting information to the terminal device 10.
  • SI system information
  • the third configuration information may be "information indicating whether or not to apply the first timer".
  • the third configuration information may indicate "to apply the first timer” or “not to apply the first timer”.
  • the third configuration information may be a flag indicating "to apply the first timer” or "not to apply the first timer”.
  • the third configuration information may be set for the LCH.
  • the third configuration information may be set as a new element of the LogicalChannelConfig IE.
  • the third configuration information may be set for the LCG.
  • the third configuration information may be set as a new element of the logicalChannelGroup IE.
  • the third configuration information may be set for a PDU or a PDU set.
  • the third configuration information may be set in an IE related to a PDU or a PDU set included in an RRC message.
  • the third configuration information may be set for a data burst.
  • the third configuration information may be set in an IE related to a data burst included in an RRC message.
  • the terminal device 10 may stop the first timer.
  • the terminal device 10 may stop the first timer.
  • the terminal device 10 may stop the first timer.
  • the terminal device 10 may stop the first timer.
  • the satisfaction of the condition (e2) means that the delay information report for the currently triggered predetermined data has been sent in the past.
  • the satisfaction of the condition (e2) may mean that the delay information report for the currently triggered predetermined data is included in the previously sent delay information report. If the condition (e2) is not satisfied, it means that the delay information report for the currently triggered predetermined data has not been sent yet, that is, a delay information report for new data has been triggered.
  • a delay information report is triggered at time t4 for data corresponding to LCG1 and data corresponding to LCG2.
  • delay information reports for these data have already been transmitted at time t1.
  • condition (e2) is satisfied, and therefore the terminal device 10 does not transmit a delay information report at time t4.
  • a delay information report for new data e.g., data corresponding to LCG3
  • condition (e2) is not satisfied. Therefore, the terminal device 10 transmits a delay information report for the data corresponding to LCG3.
  • the delay information report to be sent may include delay information reports that have already been sent and delay information reports for new data. If condition (e2) is not satisfied, the delay information report to be sent may include only delay information reports for new data.
  • the control unit 110 determines whether the trigger condition is satisfied (S1701).
  • the trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not send a delay information report.
  • the control unit 110 determines whether the condition (e2) is met (S1702). If the condition (e2) is met, the communication unit 120 does not send a delay information report. On the other hand, if the condition (e2) is not met, the communication unit 120 sends a delay information report (S1703).
  • condition (e2) may be applied to a specific condition among the trigger conditions.
  • condition (e2) may be applied to condition (d1).
  • condition (d1) if condition (d1) is satisfied and condition (e2) is satisfied, the communication unit 120 does not transmit a delay information report. If condition (d1) is satisfied and condition (e2) is not satisfied, the communication unit 120 transmits a delay information report. If at least one of conditions (a1) to (a4) and (d2) to (d4) is satisfied, the communication unit 120 may transmit a delay information report without determining whether condition (e2) is satisfied.
  • Condition (d1) is more likely to cause delay information reports to be transmitted more frequently than other conditions. With this configuration, it is possible to effectively prevent unnecessary delay information reports from being frequently triggered.
  • the terminal device 10 may operate as follows. Assume that a trigger condition (e.g., condition (d1)) is met for a certain PDU and a delay information report is sent for the PDU set to which that PDU belongs. Even if the trigger condition is subsequently met for other PDUs included in the PDU set to which that PDU belongs, the terminal device 10 does not trigger or send a delay information report for that PDU set.
  • a trigger condition e.g., condition (d1)
  • the terminal device 10 may trigger or transmit a delay information report using conditions (e1) and (e2). For example, when the trigger condition is satisfied but both conditions (e1) and (e2) are not satisfied, the communication unit 120 may transmit a delay information report.
  • one of the conditions (e1) and (e2) may take precedence.
  • the control unit 110 starts the flow of FIG. 18, it determines whether the trigger condition is satisfied (S1801).
  • the trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not send a delay information report.
  • condition (e1) is met (S1802). If condition (e1) is met, the control unit 110 determines whether condition (e2) is met (S1803). If condition (e2) is met, the communication unit 120 does not send a delay information report.
  • step S1802 the communication unit 120 transmits a delay information report (S1804). Also, if condition (e2) is not satisfied in step S1803, the communication unit 120 transmits a delay information report (S1804).
  • the communication unit 120 may transmit a delay information report. That is, even if the first timer is running, if a delay information report for new data is triggered, the communication unit 120 may transmit a delay information report.
  • the delay information report includes delay information of uplink data that has low delay requirements. Therefore, if the transmission of the delay information report is delayed, the delay information report may become unnecessary information for the base station device 20. For example, in the example of FIG. 15, assume that the delay information report that should be transmitted at time t1 is delayed by 5 ms or more. In this case, information regarding the remaining time corresponding to LCG1 may become unnecessary information for the base station device 20. Furthermore, if an unnecessary delay information report is transmitted, the communication load (i.e., overhead) may increase.
  • the terminal device 10 determines whether the available uplink resources can accommodate the delay information report. Based on the determination, the terminal device 10 executes a predetermined process related to the transmission of the delay information report.
  • the above predetermined process includes, for example, at least one of the transmission of a scheduling request (SR) and the cancellation of the transmission of the delay information report.
  • the terminal device 10 determines whether the following condition (f1) is satisfied in a situation in which a delay information report is triggered.
  • (f1) Uplink resources are available to accommodate the delay information report i.e., uplink resources are available for a new transmission of the delay information report, and uplink resources are available to accommodate the delay information report.
  • condition (f1) the terminal device 10 transmits a delay information report.
  • condition (f1) is not satisfied, that is, if it is determined that the uplink resource cannot accommodate the delay information report
  • the terminal device 10 executes a process for transmitting an SR as the above-mentioned predetermined process.
  • the process for transmitting the SR may include one or more processes related to the SR.
  • the process for transmitting the SR may include transmitting the SR. Therefore, the terminal device 10 may execute a process for transmitting an SR based on the fact that the uplink resource cannot accommodate the delay information report in the situation in which the delay information report is triggered.
  • the base station device 20 allocates an uplink resource to the terminal device 10 in accordance with the SR.
  • the terminal device 10 can transmit the delay information report using the allocated uplink resource.
  • the control unit 110 determines whether the trigger condition is satisfied (S1901).
  • the trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not send a delay information report.
  • the control unit 110 determines whether the condition (f1) is met (S1902). If the condition (f1) is met, the communication unit 120 transmits a delay information report (S1903). On the other hand, if the condition (f1) is not met, this means that there are no uplink resources available for the delay information report. Therefore, the communication unit 120 transmits an SR to the base station device 20 (S1904).
  • control unit 110 may determine whether a second timer for delaying the transmission of the SR is running.
  • the second timer may be logicalChannelSR-DelayTimer. If the second timer is running, the communication unit 120 may not need to send the SR. If the second timer is not running, the communication unit 120 may send the SR.
  • the communication unit 120 may transmit an SR even if the second timer is running. That is, the communication unit 120 may transmit an SR regardless of whether the second timer is running. Since the delay information report includes delay information of uplink data having a low delay requirement, it is preferable that the delay information report be transmitted to the base station device 20 as soon as possible. According to this configuration, uplink resources for transmitting the delay information report can be allocated to the terminal device 10 earlier.
  • condition (f1) may be applied to a specific condition among the trigger conditions.
  • condition (f1) may be applied to condition (d1).
  • condition (d1) For example, if condition (d1) is satisfied and condition (f1) is not satisfied, the communication unit 120 transmits an SR. If a delay information report is triggered by condition (d1), this means that there is little time remaining until the transmission of the delay information report is completed.
  • condition (f1) By applying condition (f1) to condition (d1), uplink resources for transmitting the delay information report can be allocated to the terminal device 10 more quickly.
  • condition (f1) If condition (f1) is met and the trigger target (i.e., the data corresponding to the LCH, LCG, PDU, PDU set, or data burst) does not satisfy the above LCP mapping restrictions, the communication unit 120 does not need to transmit an SR.
  • the trigger target i.e., the data corresponding to the LCH, LCG, PDU, PDU set, or data burst
  • the base station device 20 can receive the delay information report before the first deadline for the data corresponding to the delay information included in the delay information report expires.
  • the base station device 20 can appropriately allocate uplink resources to the terminal device 10.
  • the terminal device 10 determines whether the following condition (g1) is satisfied in a situation in which a delay information report is triggered.
  • (g1) Uplink resources can accommodate the delay information report by a predetermined second deadline, i.e., uplink resources are available for a new transmission of the delay information report, and uplink resources can accommodate the delay information report by the second deadline.
  • the terminal device 10 may determine the second deadline of the condition (g1) based on the remaining time. That is, the second deadline may be the same as the first deadline described above. More specifically, the second deadline may be a deadline for completing transmission of a part or all of the data to be reported. The second deadline may be a deadline determined based on the PDB or PSDB. The second deadline may be a deadline determined based on the PDB or PSDB set for a part or all of the data to be reported. The second deadline may be a value obtained by adding the PDB or PSDB to the first time. The second deadline may be a value that is earlier than the value obtained by adding the PDB or PSDB to the first time.
  • condition (g1) the terminal device 10 transmits a delay information report.
  • condition (g1) the terminal device 10 cancels the transmission or triggering of the delay information report as the above-mentioned predetermined processing. That is, the transmission or triggering of the delay information report is canceled based on the fact that the uplink resources cannot accommodate the delay information report by the second deadline in a situation in which the delay information report is triggered.
  • condition (g1) the terminal device 10 cancels the trigger for the delay information report (i.e., the trigger due to the trigger condition being satisfied).
  • Condition (g1) may be replaced with a condition that the trigger for the delay information report has not been canceled by the second deadline. Therefore, the terminal device 10 may cancel the transmission or trigger of the delay information report based on the fact that the trigger for the delay information report has not been canceled by the second deadline.
  • the terminal device 10 may cancel the transmission or triggering of the delay information report.
  • the terminal device 10 may cancel the transmission or triggering of the delay information report.
  • the control unit 110 determines whether the trigger condition is satisfied (S2001).
  • the trigger condition may include at least one of the conditions (a1) to (a4) and (d1) to (d4). If the trigger condition is not satisfied, the communication unit 120 does not send a delay information report.
  • the control unit 110 determines whether the condition (g1) is met (S2002). If the condition (g1) is met, the communication unit 120 transmits a delay information report (S2003). In contrast, if the condition (g1) is not met, the communication unit 120 cancels the transmission or trigger of the delay information report (S2004). Note that the control unit 110 may cancel the transmission or trigger of the delay information report and transmit an instruction to cancel to the communication unit 120.
  • the communication unit 120 may cancel the transmission or trigger of the delay information report.
  • Condition (g1) may be applied to a specific condition among the trigger conditions. For example, condition (g1) may be applied to condition (d1). For example, if condition (d1) is satisfied and condition (g1) is not satisfied, the communication unit 120 cancels the transmission or triggering of the delay information report. If the delay information report is triggered by condition (d1), this means that there is little time remaining until the transmission of the delay information report is completed. In such a case, even if the delay information report is transmitted to the base station device 20, the data corresponding to the delay information included in the delay information report may have passed the first deadline. In other words, the delay information included in the delay information report may not be useful information for the base station device 20, but may be unnecessary information. If an unnecessary delay information report is transmitted, the communication load may increase. With this configuration, it is possible to prevent the transmission of unnecessary delay information reports.
  • the terminal device 10 may start a third timer when the delay information report is triggered (i.e., the trigger condition is satisfied) and determine the second deadline based on the third timer.
  • the third timer expires at a predetermined period.
  • the period of the third timer may be selected from among a plurality of values.
  • the terminal device 10 may determine that the condition (g1) is not satisfied when the third timer expires.
  • the terminal device 10 may receive an RRC message including information regarding the third timer from the base station device 20.
  • information regarding the third timer may be included in an IE related to the BSR (e.g., the BSR-Config IE).
  • the third timer may be set for an LCH or an LCG.
  • Information regarding the third timer may be set in an IE related to an LCH or an LCG. Examples of such IEs include the LogicalChannelConfig IE and the logicalChannelGroup IE.
  • the third timer is started when a delay information report is triggered for an LCH or an LCG for which the third timer is set. Therefore, when the third timer expires, the transmission or triggering of a delay information report for an LCH or an LCG for which the third timer is set is canceled.
  • a delay information report for an LCH or an LCG for which the third timer is not set may be transmitted. In other words, the triggering of a delay information report for an LCH or an LCG for which the third timer is not set does not have to be canceled.
  • the third timer may be set for a PDU or a PDU set.
  • Information about the third timer may be set in an IE related to a PDU or a PDU set.
  • information about the third timer may be set in an IE related to a PDU or a PDU set included in an RRC message.
  • the third timer is started when a delay information report for a PDU or a PDU set for which the third timer is set is triggered. Therefore, when the third timer expires, the transmission or triggering of a delay information report for a PDU or a PDU set for which the third timer is set is canceled.
  • a delay information report for a PDU or a PDU set for which the third timer is not set may be transmitted.
  • the triggering of a delay information report for a PDU or a PDU set for which the third timer is not set may not be canceled.
  • the third timer may be set for the data burst.
  • Information about the third timer may be set in an IE related to the data burst.
  • information about the third timer may be set in an IE related to the data burst included in an RRC message.
  • the third timer is started when a delay information report for a data burst for which the third timer is set is triggered. Therefore, when the third timer expires, the transmission or triggering of the delay information report for the data burst for which the third timer is set is canceled.
  • a delay information report for a data burst for which the third timer is not set may be transmitted. In other words, the triggering of a delay information report for a data burst for which the third timer is not set may not be canceled.
  • the above configuration makes it possible to prevent unnecessary delay information reports from being sent. Since uplink resources are not used for unnecessary delay information reports, the possibility of an increase in communication load can be reduced.
  • the terminal device 10 may execute a predetermined process related to the transmission of a delay information report using conditions (f1) and (g1). For example, the control unit 110 may determine whether condition (g1) is satisfied after executing step S1904 of the flow in FIG. 19. If condition (g1) is not satisfied, the communication unit 120 may cancel the transmission or triggering of the delay information report. In this way, if there are no uplink resources that can accommodate the delay information report by the second deadline after the terminal device 10 transmits the SR, the terminal device 10 may cancel the transmission or triggering of the delay information report.
  • the determination of the trigger condition is followed by the determination of the restriction condition (condition (e1) and/or (e2)), but this configuration is not limiting.
  • the determination of the restriction condition may be made before the determination of the trigger condition.
  • the terminal device 10 may decide whether to determine the trigger condition based on whether the restriction condition is satisfied. For example, if the restriction condition is satisfied, the terminal device 10 does not determine the trigger condition. In other words, the delay information report is not triggered. If the restriction condition is not satisfied, the terminal device 10 determines the trigger condition.
  • the first embodiment may include "an aspect in which the terminal device 10 cancels the trigger for the delay information report using the restriction condition after the trigger condition is satisfied" and “an aspect in which the terminal device 10 does not determine the trigger condition for the delay information report based on the fact that the restriction condition is satisfied.”
  • the determination of the trigger condition is performed after the determination of the condition (f1), but this configuration is not limited to this.
  • the determination of the condition (f1) may be performed before the determination of the trigger condition.
  • the terminal device 10 may decide whether to determine the trigger condition based on whether the condition (f1) is satisfied. If the condition (f1) is satisfied, the terminal device 10 determines the trigger condition. If the condition (f1) is not satisfied, the terminal device 10 executes a process for transmitting an SR.
  • aspect 2-1 of the second embodiment may include "an aspect in which the terminal device 10 executes a process for transmitting an SR when the trigger condition is satisfied and the condition (f1) is not satisfied” and “an aspect in which the terminal device 10 executes a process for transmitting an SR without determining the trigger condition when the condition (f1) is not satisfied.”
  • the determination of the trigger condition is performed after the determination of the condition (g1), but this configuration is not limited to this.
  • the determination of the condition (g1) may be performed before the determination of the trigger condition.
  • the terminal device 10 may decide whether to determine the trigger condition based on whether the condition (g1) is satisfied. If the condition (g1) is satisfied, the terminal device 10 determines the trigger condition. If the condition (g1) is not satisfied, the terminal device 10 does not determine the trigger condition. In other words, the delay information report is not triggered.
  • aspect 2-2 of the second embodiment may include "an aspect in which the terminal device 10 cancels the trigger for the delay information report (i.e., the trigger due to the trigger condition being satisfied) when the condition (g1) is not satisfied” and “an aspect in which the terminal device 10 does not determine the trigger condition for the delay information report when the condition (g1) is not satisfied.”
  • 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 control unit (110) configured to determine whether available uplink resources can accommodate a delay information report in a situation where a delay information report including delay information regarding a delay for a given data is triggered; a communication unit (120) configured to execute a predetermined process related to the transmission of the delay information report based on the determination;
  • a terminal device (10) comprising:
  • the communication unit is Based on the available uplink resources being unable to accommodate the delay information report in a situation in which the delay information report is triggered,
  • the predetermined processing is configured to execute a process for transmitting a scheduling request (SR).
  • SR scheduling request
  • the communication unit is In a situation in which the delay information report is triggered, if the available uplink resources cannot accommodate the delay information report and a timer for delaying the transmission of the SR is running, not performing a process for transmitting the SR; and performing a process for transmitting the SR when the available uplink resources cannot accommodate the delay information report in a situation in which the delay information report is triggered and the timer is not running. 3.
  • a terminal device as described in claim 2.
  • the communication unit is configured to receive a Radio Resource Control (RRC) message from a base station device (20);
  • RRC Radio Resource Control
  • the timer is a logicalChannelSR-DelayTimer included in the RRC message. 4.
  • the communication unit is and performing a process for transmitting the SR even if the available uplink resources cannot accommodate the delay information report in a situation in which the delay information report is triggered and a timer for delaying the transmission of the SR is running. 3.
  • the communication unit is configured to receive a Radio Resource Control (RRC) message from a base station device (20);
  • RRC Radio Resource Control
  • the timer is a logicalChannelSR-DelayTimer included in the RRC message. 6.
  • a terminal device as described in claim 5.
  • the control unit is configured to trigger the delay information report using a trigger condition related to a remaining time until a deadline for transmitting the predetermined data is reached;
  • the communication unit is performing a process for transmitting the SR when the remaining time is equal to or less than a predetermined threshold and the available uplink resources cannot accommodate the delay information report.
  • the communication unit is Based on the available uplink resources being unable to accommodate the delay information report by a predetermined time limit in a situation in which the delay information report is triggered, The predetermined process is configured to cancel transmission or trigger of the delay information report.
  • the predetermined process is configured to cancel transmission or trigger of the delay information report.
  • the control unit is configured to trigger the delay information report using a trigger condition related to a remaining time until a deadline for transmitting the predetermined data is reached;
  • the communication unit is configured to cancel transmission or triggering of the delay information report if the remaining time is equal to or less than a predetermined threshold and the available uplink resources cannot accommodate the delay information report by the predetermined deadline.
  • the control unit is and determining the predetermined deadline based on the remaining time. 10.
  • the control unit is and determining the predetermined deadline based on a Packet Delay Budget (PDB) or a Protocol Data Unit-Set Delay Budget (PSDB). 9.
  • PDB Packet Delay Budget
  • PSDB Protocol Data Unit-Set Delay Budget
  • the control unit is starting a timer when the delay information report is triggered; configured to determine the predetermined deadline based on the timer.
  • the communication unit is configured to receive a Radio Resource Control (RRC) message from a base station device (20); The timer is included in the RRC message. 13.
  • RRC Radio Resource Control
  • the delay information report is a Buffer Status Report (BSR) including the delay information and buffer size information regarding a buffer size. 14.
  • BSR Buffer Status Report
  • a terminal device according to any one of appendix 1 to 13.
  • the delay information is Information about delay times, or Information about data that is subject to time constraints or requirements; 15. A terminal device according to any one of appendix 1 to 14.
  • 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. 16.
  • a terminal device according to any one of appendix 1 to 15.
  • the delay information report includes delay information regarding a delay for a given data, and determining whether the available uplink resources can accommodate the delay information report; executing a predetermined process related to transmitting the delay information report based on the determination;
  • a method for a terminal device (10) comprising:
  • the delay information report includes delay information regarding a delay for a given data, and determining whether the available uplink resources can accommodate the delay information report; executing a predetermined process related to transmitting the delay information report based on the determination;
  • the delay information report includes delay information regarding a delay for a given data, and determining whether the available uplink resources can accommodate the delay information report; executing a predetermined process related to transmitting the delay information report based on the determination;
  • a communication unit (220) configured to receive a delay information report from a terminal device (10) including delay information regarding a delay for a predetermined data;
  • a control unit (210) configured to allocate radio resources to the terminal device based on the delay information report; Equipped with In a situation where the delay information report is triggered in the terminal device, if the uplink resources available in the terminal device cannot accommodate the delay information report, the communication unit is configured to receive a scheduling request (SR) from the terminal device.
  • the control unit is configured to allocate radio resources to the terminal device in response to the SR. 21.
  • a base station apparatus as described in Supplementary Note 20.
  • (Appendix 22) receiving a delay information report from a terminal device (10), the delay information including delay information regarding a delay for a predetermined data; Allocating radio resources to the terminal device based on the delay information report; In a situation where the delay information report is triggered in the terminal device, if an uplink resource available in the terminal device cannot accommodate the delay information report, receiving a scheduling request (SR) from the terminal device; A method for a base station device (20).
  • SR scheduling request
  • SR scheduling request
  • a control unit (110) that controls triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; Equipped with The control unit cancels the DSR that has been triggered and has not been canceled when data of the LCG associated with the DSR expires.
  • the DSR is a field whose bits each indicate whether a buffer size field for each LCG is present; A field indicating the remaining time for the earliest deadline of the data of the LCG; A field indicating a buffer size for the LCG; Including, 26.
  • the control unit is switching between a first table and a second table different from the first table and setting the field indicating the buffer size; 27.
  • a terminal device as described in appendix 26.
  • the DSR is a field whose bits each indicate whether a buffer size field for each LCG is present; A field containing information about data of the LCG whose remaining time is below the threshold; Including, 26.
  • the DSR is a MAC CE (Medium Access Control Element) including a subheader including an extended logical channel identifier (eLCID) for identifying the DSR. 29.
  • eLCID extended logical channel identifier
  • Appendix 30 receiving, from a base station device (20), a radio resource control (RRC) message including information for setting an identifier (ID) of a logical channel group (LCG) to which a logical channel (LCH) belongs, and information indicating a threshold value for data of the LCG for controlling a trigger of a delay status report (DSR); Controlling the triggering of the DSR based on the remaining time for the earliest deadline of the data of the LCG being below the threshold and the DSR for the data of the LCG not being transmitted; canceling the DSR that has been triggered and has not been cancelled when the data of the LCG associated with the DSR expires; A method for a terminal device (10).
  • RRC radio resource control
  • the DSR is a field whose bits each indicate whether a buffer size field for each LCG is present; A field indicating the remaining time for the earliest deadline of the data of the LCG; A field indicating a buffer size for the LCG; Including, 31.
  • the DSR is a field whose bits each indicate whether a buffer size field for each LCG is present; A field containing information about data of the LCG whose remaining time is below the threshold; Including, 31. A method for a terminal device as described in claim 30.
  • the DSR is a MAC CE (Medium Access Control Element) including a subheader including an extended logical channel identifier (eLCID) for identifying the DSR.
  • eLCID extended logical channel identifier
  • RRC radio resource control
  • RRC Radio Resource Control

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2024/009669 2023-04-07 2024-03-13 端末装置及び端末装置の方法 Ceased WO2024209893A1 (ja)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2025512464A JP7798236B2 (ja) 2023-04-07 2024-03-13 端末装置及び端末装置の方法
CN202480023526.3A CN120898497A (zh) 2023-04-07 2024-03-13 终端设备以及终端设备的方法
EP24784688.4A EP4694475A1 (en) 2023-04-07 2024-03-13 Terminal device and method for terminal device
US19/347,247 US20260032661A1 (en) 2023-04-07 2025-10-01 Terminal apparatus, method of terminal apparatus and base station apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023062921 2023-04-07
JP2023-062921 2023-04-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/347,247 Continuation US20260032661A1 (en) 2023-04-07 2025-10-01 Terminal apparatus, method of terminal apparatus and base station apparatus

Publications (1)

Publication Number Publication Date
WO2024209893A1 true WO2024209893A1 (ja) 2024-10-10

Family

ID=92972026

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/009669 Ceased WO2024209893A1 (ja) 2023-04-07 2024-03-13 端末装置及び端末装置の方法

Country Status (5)

Country Link
US (1) US20260032661A1 (https=)
EP (1) EP4694475A1 (https=)
JP (1) JP7798236B2 (https=)
CN (1) CN120898497A (https=)
WO (1) WO2024209893A1 (https=)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012914A1 (ja) * 2021-08-03 2023-02-09 株式会社Ｎｔｔドコモ 端末および無線通信方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023012914A1 (ja) * 2021-08-03 2023-02-09 株式会社Ｎｔｔドコモ 端末および無線通信方法

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
3GPP TR 38.838, December 2021 (2021-12-01)
3GPP TS 38.321, September 2022 (2022-09-01)
3GPP TS 38.331, September 2022 (2022-09-01)
HANSEUL HONG, LG ELECTRONICS INC.: "Discussion on BSR enhancement and delay information report", 3GPP DRAFT; R2-2304008; 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. Online; 20230417 - 20230426, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052290400 *
NAVEEN PALLE, APPLE: "Views on BSR Enhancements for XR", 3GPP DRAFT; R2-2300727; 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. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052245370 *
See also references of EP4694475A1
TATSUKI NAGANO, DENSO CORPORATION: "Discussion on delay status reporting for XR", 3GPP DRAFT; R2-2307243; 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. Toulouse, FR; 20230821 - 20230825, 9 August 2023 (2023-08-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052442962 *
YANHUA LI, XIAOMI COMMUNICATIONS: "Discussing on UE feedback enhancements for XR capacity", 3GPP DRAFT; R2-2300422; TYPE DISCUSSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, GR; 20230227 - 20230303, 17 February 2023 (2023-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052245069 *

Also Published As

Publication number Publication date
JPWO2024209893A1 (https=) 2024-10-10
CN120898497A (zh) 2025-11-04
EP4694475A1 (en) 2026-02-11
JP7798236B2 (ja) 2026-01-14
US20260032661A1 (en) 2026-01-29

Similar Documents

Publication Publication Date Title
RU2754679C2 (ru) Система, устройство и способ передачи данных
CN110167172A (zh) 一种传输信息的方法和装置
US20250358814A1 (en) Terminal apparatus, method of terminal apparatus and base station apparatus
CN119316108A (zh) 数据处理方法及装置
US20250234416A1 (en) Terminal apparatus, method of terminal apparatus and base station apparatus
US20250126678A1 (en) Terminal apparatus, base station apparatus, and method
CN112753272B (zh) 无线通信系统中发送和接收信号的方法及支持该方法的装置
JP7798236B2 (ja) 端末装置及び端末装置の方法
JP7782756B2 (ja) 端末装置及び端末装置の方法
WO2023248667A1 (ja) 端末装置、基地局装置、及び端末装置における方法
WO2025022772A1 (ja) 端末装置及び端末装置の方法
WO2025022773A1 (ja) 端末装置及び端末装置の方法
WO2025070067A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
JP7758232B2 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025070068A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2024154462A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2024095792A1 (ja) 端末装置及び基地局装置
WO2025094646A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2025234285A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2025234286A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2025164131A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2026009628A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2024209828A1 (ja) 端末装置、端末装置の方法、及び、基地局装置
WO2026009629A1 (ja) 端末装置、端末装置の方法及び基地局装置
WO2025173430A1 (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: 24784688

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025512464

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025512464

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202480023526.3

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202480023526.3

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2024784688

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

ENP Entry into the national phase

Ref document number: 2024784688

Country of ref document: EP

Effective date: 20251107

WWP Wipo information: published in national office

Ref document number: 2024784688

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112025020693

Country of ref document: BR