[go: up one dir, main page]

WO2025205431A1 - Dispositif terminal, procédé et circuit intégré - Google Patents

Dispositif terminal, procédé et circuit intégré

Info

Publication number
WO2025205431A1
WO2025205431A1 PCT/JP2025/011038 JP2025011038W WO2025205431A1 WO 2025205431 A1 WO2025205431 A1 WO 2025205431A1 JP 2025011038 W JP2025011038 W JP 2025011038W WO 2025205431 A1 WO2025205431 A1 WO 2025205431A1
Authority
WO
WIPO (PCT)
Prior art keywords
ltm
terminal device
configuration
information element
rrc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2025/011038
Other languages
English (en)
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.)
Sharp Corp
Original Assignee
Sharp 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 Sharp Corp filed Critical Sharp Corp
Publication of WO2025205431A1 publication Critical patent/WO2025205431A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • 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
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality

Definitions

  • 3GPP registered trademark
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • RAT Radio Access Technology
  • 3GPP is currently conducting technical studies and standardization of E-UTRA extension technologies.
  • E-UTRA is also known as Long Term Evolution (LTE: registered trademark), and the extension technologies are sometimes referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
  • conditional handover CHO
  • Layer 1/Layer 2 triggered mobility LTM
  • Conditional LTM conditional Layer 1/Layer 2 triggered mobility
  • One aspect of the present invention was made in consideration of the above circumstances, and one of its objectives is to provide a terminal device, base station device, communication method, and integrated circuit that can efficiently control communications.
  • Another aspect of the present invention is a method for a terminal device to communicate with a base station device, comprising the step of receiving RRC signaling from the base station device, the RRC signaling including a first entry list, wherein each of one or more entries included in the first entry list links one LTM CSI resource configuration with one conditional LTM event configuration.
  • a terminal device, a base station device, a method, and an integrated circuit can achieve efficient communication control processing.
  • LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (Radio Access Technologies: RATs).
  • NR may also be defined as a technology included in LTE.
  • LTE may also be defined as a technology included in NR.
  • LTE that can connect to NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE.
  • LTE that uses 5GC for the core network (Core Network: CN) may be distinguished from conventional LTE that uses EPC for the core network.
  • Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later.
  • This embodiment may be applied to NR, LTE, and other RATs.
  • the following explanation uses terms related to LTE and NR, but this embodiment may also be applied to other technologies that use other terminology.
  • E-UTRA in this embodiment may be replaced with LTE, and the term LTE may be replaced with E-UTRA.
  • Figure 1 is a schematic diagram of a communications system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. described using Figure 1 are only some of the functions closely related to this embodiment, and other functions may also be included.
  • E-UTRA 100 may be a radio access technology.
  • E-UTRA 100 may also be the air interface between UE 122 and eNB 102.
  • the air interface between UE 122 and eNB 102 may be referred to as the Uu interface.
  • eNB (E-UTRAN Node B) 102 may be a base station device.
  • eNB 102 may have the E-UTRA protocol described below.
  • the E-UTRA protocol may be composed of the E-UTRA user plane (User Plane: UP) protocol described below and the E-UTRA control plane (Control Plane: CP) protocol described below.
  • EPC (Evolved Packet Core) 104 may be a core network.
  • Interface 112 is an interface between eNB 102 and EPC 104, and may be referred to as an S1 interface.
  • Interface 112 may have a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of interface 112 may terminate at a Mobility Management Entity (MME: not shown) in EPC 104.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the control plane interface of interface 112 may be referred to as an S1-MME interface.
  • the user plane interface of interface 112 may be referred to as an S1-U interface.
  • one or more eNBs 102 may be connected to the EPC 104 via an interface 112.
  • An interface (not shown) may exist between multiple eNBs 102 connected to the EPC 104.
  • the interface between multiple eNBs 102 connected to the EPC 104 may be referred to as an X2 interface.
  • NR106 may be a radio access technology.
  • NR106 may also be the air interface between UE122 and gNB108.
  • the air interface between UE122 and gNB108 may be referred to as the Uu interface.
  • gNB (g Node B) 108 may be a base station device.
  • gNB108 may have the NR protocol described below.
  • the NR protocol may consist of the NR user plane (User Plane: UP) protocol described below and the NR control plane (Control Plane: CP) protocol described below.
  • gNB108 may terminate the NR user plane (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol for UE122.
  • 5GC110 may be a core network.
  • Interface 116 is an interface between gNB108 and 5GC110, and may be referred to as an NG interface.
  • Interface 116 may have a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of interface 116 may terminate at an Access and Mobility Management Function (AMF: not shown) within 5GC110.
  • AMF Access and Mobility Management Function
  • the user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC110.
  • the control plane interface of interface 116 may be referred to as an NG-C interface.
  • the user plane interface of interface 116 may be referred to as an NG-U interface.
  • one or more gNBs 108 may be connected to the 5GC 110 via an interface 116.
  • An interface may exist between multiple gNBs 108 connected to the 5GC 110 (not shown).
  • the interface between multiple gNBs 108 connected to the 5GC 110 may be referred to as an Xn interface.
  • the eNB102 may have the ability to connect to the 5GC110.
  • the eNB102 with the ability to connect to the 5GC110 may be referred to as an ng-eNB.
  • the interface 114 is an interface between the eNB102 and the 5GC110 and may be referred to as an NG interface.
  • the interface 114 may have a control plane interface through which control signals pass, and/or a user plane interface through which user data passes.
  • the control plane interface of the interface 114 may terminate at the AMF within the 5GC110.
  • the user plane interface of the interface 114 may terminate at the UPF within the 5GC110.
  • the control plane interface of the interface 114 may be referred to as an NG-C interface.
  • the user plane interface of the interface 114 may be referred to as an NG-U interface.
  • a radio access network consisting of an ng-eNB or a gNB may be referred to as an NG-RAN.
  • the NG-RAN, E-UTRAN, etc. may simply be referred to as a network.
  • the network may include an eNB, ng-eNB, gNB, etc.
  • one or more eNB102 may be connected to 5GC110 via interface 114.
  • An interface may exist between multiple eNB102 connected to 5GC110 (not shown).
  • the interface between multiple eNB102 connected to 5GC110 may be called an Xn interface.
  • an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be connected via interface 120.
  • the interface 120 between an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be called an Xn interface.
  • the gNB108 may have the ability to connect to the EPC104.
  • a gNB108 with the ability to connect to the EPC104 may be referred to as an en-gNB.
  • Interface 118 is an interface between the gNB108 and the EPC104 and may be referred to as an S1 interface.
  • Interface 118 may have a user plane interface through which user data passes.
  • the user plane interface of interface 118 may terminate at an S-GW (not shown) within the EPC104.
  • the user plane interface of interface 118 may be referred to as an S1-U interface.
  • the eNB102 connecting to the EPC104 and the gNB108 connecting to the EPC104 may be connected by interface 120.
  • Interface 120 between the eNB102 connecting to the EPC104 and the gNB108 connecting to the EPC104 may be referred to as an X2 interface.
  • Interface 124 is an interface between EPC 104 and 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of interfaces such as interface 114, interface 116, interface 118, interface 120, and interface 124 may not exist depending on the communication system provided by the telecommunications carrier, etc.
  • UE122 may be a terminal device capable of receiving system information and paging messages transmitted from eNB102 and/or gNB108. UE122 may also be a terminal device capable of wireless connection with eNB102 and/or gNB108. UE122 may also be a terminal device capable of wireless connection with eNB102 and wireless connection with gNB108 simultaneously. UE122 may have the E-UTRA protocol and/or the NR protocol. The wireless connection may be a Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • UE122 may be a terminal device capable of connecting to EPC104 and/or 5GC110 via eNB102 and/or gNB108. If the core network to which eNB102 and/or gNB108, with which UE122 communicates, is connected is EPC104, each Data Radio Bearer (DRB) described below established between UE122 and eNB102 and/or gNB108 may further be uniquely linked to each EPS (Evolved Packet System) bearer passing through EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.
  • EPS bearer Evolved Packet System
  • eNB102 and/or gNB108 will also be referred to simply as base station devices, and UE122 will also be referred to simply as terminal device or UE.
  • FIG. 2 is a diagram showing an example of the E-UTRA protocol architecture according to this embodiment.
  • FIG. 3 is a diagram showing an example of the NR protocol architecture according to this embodiment. Note that the functions of each protocol described using FIG. 2 and/or FIG. 3 are only some of the functions closely related to this embodiment, and other functions may also be included.
  • the uplink (UL) may be a link from the terminal device to the base station device.
  • the downlink (DL) may be a link from the base station device to the terminal device.
  • the E-UTRA user plane protocol stack may be composed of a PHY (Physical layer) 200, which is the radio physical layer, a MAC (Medium Access Control) 202, which is the medium access control layer, a RLC (Radio Link Control) 204, which is the radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206, which is the packet data convergence protocol layer.
  • PHY Physical layer
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • Figure 3(A) is a diagram of the NR user plane (UP) protocol stack.
  • the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side.
  • the NR user plane protocol stack may be composed of a radio physical layer, PHY 300, a medium access control layer, MAC 302, a radio link control layer, RLC 304, a packet data convergence protocol layer, PDCP 306, and a service data adaptation protocol layer, SDAP (Service Data Adaptation Protocol) 310.
  • PHY 300 a radio physical layer
  • MAC 302 medium access control layer
  • RLC 304 radio link control layer
  • PDCP 306 Packet Control Protocol
  • SDAP Service Data Adaptation Protocol
  • FIG. 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration.
  • RRC Radio Resource Control
  • NAS Non Access Stratum
  • NAS 210 which is the non-AS (Access Stratum) layer
  • NAS 210 may be a protocol that terminates at MME on the network side.
  • Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration.
  • RRC308 which is the radio resource control layer
  • RRC308 may be a protocol that terminates at gNB108 on the network side.
  • NAS312 which is the non-AS layer
  • NAS312 may be a protocol that terminates at AMF on the network side.
  • the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and/or the gNB 108.
  • the AS layer may be a layer that includes some or all of the PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208, and/or a layer that includes some or all of the PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308.
  • PHY PHY layer
  • MAC MAC layer
  • RLC RLC layer
  • PDCP PDCP layer
  • RRC RRC layer
  • NAS NAS layer
  • the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, respectively, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol.
  • the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.
  • An entity that has some or all of the functions of the MAC layer may be called a MAC entity.
  • An entity that has some or all of the functions of the RLC layer may be called an RLC entity.
  • An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity.
  • An entity that has some or all of the functions of the SDAP layer may be called an SDAP entity.
  • An entity that has some or all of the functions of the RRC layer may be called an RRC entity.
  • the MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.
  • the base station device and the terminal device exchange (transmit and receive) signals at a higher layer.
  • the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC messages, RRC information, or RRC signaling) at the Radio Resource Control (RRC) layer.
  • RRC Radio Resource Control
  • the base station device and the terminal device may also transmit and receive MAC control elements at the MAC (Medium Access Control) layer.
  • the RRC layer of the terminal device acquires system information broadcast from the base station device.
  • the RRC messages, system information, and/or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters).
  • Each of the parameters included in the higher layer signals received by the terminal device may be referred to as a higher layer parameter.
  • the upper layer refers to the upper layer seen from the PHY layer, and may therefore refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc.
  • the upper layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc.
  • “A is given (provided) by the upper layer” or “A is given (provided) by the upper layer” may mean that the upper layer of the terminal device (mainly the RRC layer or MAC layer) receives A from the base station device, and the received A is given (provided) to the physical layer of the terminal device from the upper layer of the terminal device.
  • upper layer parameters are provided may mean that the upper layer signal is received from the base station device, and the upper layer parameters included in the received upper layer signal are provided to the physical layer of the terminal device from the upper layer of the terminal device.
  • Setting upper layer parameters in the terminal device may mean that the upper layer parameters are given (provided) to the terminal device.
  • setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device and sets the received upper layer parameters in the upper layer.
  • setting upper layer parameters in a terminal device may also include setting default parameters that are pre-assigned to the upper layer of the terminal device.
  • the PHY of the terminal device may have the function of receiving data transmitted from the PHY of the base station device via the downlink (DL) physical channel.
  • the PHY of the terminal device may have the function of transmitting data to the PHY of the base station device via the uplink (UL) physical channel.
  • the PHY may be connected to the upper MAC via a transport channel.
  • the PHY may pass data to the MAC via the transport channel.
  • the PHY may also be provided with data from the MAC via the transport channel.
  • an RNTI Radio Network Temporary Identifier
  • the physical channels used for wireless communication between terminal devices and base station devices may include the following physical channels:
  • PBCH Physical Broadcast CHannel
  • PDCCH Physical Downlink Control CHannel
  • PDSCH Physical Downlink Shared CHannel
  • PUCCH Physical Uplink Control CHannel
  • PUSCH Physical Uplink Shared CHannel
  • PRACH Physical Random Access CHannel
  • PBCH may be used to broadcast system information required by terminal devices.
  • the PBCH may be used to broadcast the time index (SSB-Index) within the period of a synchronization signal block (SSB).
  • SSB-Index time index within the period of a synchronization signal block
  • the PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device).
  • DCI downlink control information
  • one or more DCIs (which may also be referred to as DCI formats) may be defined for transmitting the downlink control information. That is, a field for the downlink control information may be defined as DCI and mapped to information bits.
  • the PDCCH may be transmitted in PDCCH candidates.
  • the terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. Furthermore, the terminal device may use a CORESET (Control Resource Set) to monitor the set of PDCCH candidates.
  • the DCI format may be used for scheduling the PUSCH in the serving cell.
  • the PUSCH may be used for transmitting user data, RRC messages (described later), etc.
  • the PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device).
  • the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
  • CSI Channel State Information
  • the uplink control information may also include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources.
  • SR Scheduling Request
  • UL-SCH Uplink Shared CHannel
  • the uplink control information may also include a HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
  • PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer.
  • DL-SCH Downlink Shared CHannel
  • PDSCH may also be used to transmit system information (SI: System Information) and random access response (RAR: Random Access Response).
  • SI System Information
  • RAR Random Access Response
  • PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and/or CSI together with uplink data. PUSCH may also be used to transmit only CSI, or only HARQ-ACK and CSI. In other words, PUSCH may be used to transmit only UCI. PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as RRC messages) and MAC CE.
  • RRC signaling also referred to as RRC messages
  • the RRC signaling transmitted from the base station device may be signaling common to multiple terminal devices within a cell.
  • RRC signaling transmitted from the base station device may also be signaling dedicated to a certain terminal device (also referred to as dedicated signaling). In other words, terminal device-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal device.
  • the PUSCH may also be used to transmit UE capabilities in the uplink.
  • the PRACH may be used to transmit a random access preamble.
  • the PRACH may also be used for initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmissions, and to indicate requests for UL-SCH resources.
  • the MAC may be called the MAC sublayer.
  • the MAC may have the function of mapping various logical channels to corresponding transport channels.
  • Logical channels may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID).
  • the MAC may be connected to the higher-level RLC via a logical channel.
  • logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information.
  • Logical channels may also be divided into uplink logical channels and downlink logical channels.
  • the MAC may have the function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY.
  • the MAC may have the ability to select the transport format.
  • the MAC may have functions such as discontinuous reception (DRX) and/or discontinuous transmission (DTX), a function to execute random access (RA) procedures, a power headroom report (PHR) function to notify information on the available transmit power, and a buffer status report (BSR) function to notify information on the amount of data in the transmit buffer.
  • the NR MAC may have a bandwidth adaptation (BA) function.
  • the MAC PDU format used in the E-UTRA MAC may differ from the MAC PDU format used in the NR MAC.
  • the MAC PDU may also include a MAC control element (MAC CE), which is an element for performing control in the MAC.
  • MAC CE MAC control element
  • This section explains the uplink (UL) and/or downlink (DL) logical channels used in E-UTRA and/or NR.
  • the BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI).
  • SI system information
  • the CCCH may be a logical channel for transmitting control information between a terminal device and a base station device.
  • the CCCH may be used when the terminal device does not have an RRC connection.
  • the CCCH may also be used between a base station device and multiple terminal devices.
  • the DCCH (Dedicated Control Channel) may be a logical channel for transmitting dedicated control information bidirectionally, point-to-point, between a terminal device and a base station device.
  • the dedicated control information may be control information dedicated to each terminal device.
  • the DCCH may be used when the terminal device has an RRC connection.
  • This section explains the mapping of logical channels and transport channels for the uplink in E-UTRA and/or NR.
  • the CCCH may be mapped to the uplink transport channel, UL-SCH (Uplink Shared Channel).
  • UL-SCH Uplink Shared Channel
  • DTCH may be mapped to the uplink transport channel, UL-SCH (Uplink Shared Channel).
  • UL-SCH Uplink Shared Channel
  • the BCCH may be mapped to the downlink transport channel BCH (Broadcast Channel) and/or DL-SCH (Downlink Shared Channel).
  • BCH Broadcast Channel
  • DL-SCH Downlink Shared Channel
  • the PCCH may be mapped to the PCH (Paging Channel), which is a downlink transport channel.
  • PCH Packet Control Channel
  • the CCCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • the DCCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • DTCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).
  • DL-SCH Downlink Shared Channel
  • PDCP may also have a PDCP SDU retransmission function.
  • PDCP may also have a data discard function using a discard timer.
  • PDCP may also have a duplication function.
  • PDCP may also have a function to discard duplicated received data.
  • a PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity.
  • the PDCP PDU format used in E-UTRA PDCP may differ from the PDCP PDU format used in NR PDCP.
  • PDCP PDUs may include data PDCP PDUs and control PDCP PDUs.
  • Data PDCP PDUs may be called PDCP DATA PDUs (PDCP Data PDUs).
  • Control PDCP PDUs may be called PDCP CONTROL PDUs (PDCP Control PDUs).
  • RRC may have a broadcast function.
  • RRC may have a paging function from EPC104 and/or 5GC110.
  • RRC may have a paging function from eNB102 connected to gNB108 or 5GC110.
  • RRC may also have an RRC connection management function.
  • RRC may also have a radio bearer control function.
  • RRC may also have a cell group control function.
  • RRC may also have a mobility control function.
  • RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions.
  • RRC may also have a QoS management function.
  • RRC may also have a radio link failure detection and recovery function.
  • RRC messages may be sent using the logical channel BCCH, the logical channel PCCH, the logical channel CCCH, or the logical channel DCCH.
  • RRC messages sent using the DCCH may also be referred to as dedicated RRC signaling or RRC signaling.
  • RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIB), or other RRC messages.
  • RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.
  • RRC messages sent in the uplink (UL) direction using CCCH may include, for example, an RRC setup request message (RRC Setup Request), an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request message (RRC System Info Request), etc. They may also include, for example, an RRC connection request message (RRC Connection Request), an RRC connection resume request message (RRC Connection Resume Request), an RRC connection reestablishment request message (RRC Connection Reestablishment Request), etc. They may also include other RRC messages.
  • RRC messages sent in the downlink (DL) direction using CCCH may include, for example, an RRC connection reject message (RRC Connection Reject), an RRC connection setup message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment Reject), an RRC connection reestablishment rejection message (RRC Connection Reestablishment Reject), etc. They may also include, for example, an RRC reject message (RRC Reject), an RRC setup message (RRC Setup), etc. They may also include other RRC messages.
  • It may also include, for example, a measurement report message (Measurement Report), an RRC reconfiguration complete message (RRC Reconfiguration Complete), an RRC setup complete message (RRC Setup Complete), an RRC reestablishment complete message (RRC Reestablishment Complete), an RRC resumption complete message (RRCResume Complete), a security mode complete message (Security Mode Complete), and a UE capability information message (UE Capability Information). It may also include other RRC signaling.
  • the NAS may have authentication functionality.
  • the NAS may also have mobility management functionality.
  • the NAS may also have security control functionality.
  • UE122 connected to EPC or 5GC may be in the RRC_CONNECTED state when an RRC connection has been established.
  • the state in which an RRC connection is established may include a state in which UE122 holds some or all of the UE context described below.
  • the state in which an RRC connection is established may also include a state in which UE122 is able to send and/or receive unicast data.
  • UE122 may be in the RRC_INACTIVE state when the RRC connection is suspended.
  • UE122 may be in the RRC_INACTIVE state when UE122 is connected to 5GC and the RRC connection is suspended.
  • UE122 may be in the RRC_IDLE state when UE122 is neither in the RRC_CONNECTED state nor the RRC_INACTIVE state.
  • UE122 when UE122 is connected to the EPC, it does not have the RRC_INACTIVE state, but E-UTRAN may initiate suspension of the RRC connection.
  • UE122 When UE122 is connected to the EPC and the RRC connection is suspended, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resumption.
  • a layer above the RRC layer of UE122 e.g., the NAS layer
  • dormancy may differ between UE122 connected to EPC104 and UE122 connected to 5GC110. Furthermore, all or part of the procedure for UE122 to return from dormancy may differ between when UE122 is connected to EPC (when UE122 is dormant in RRC_IDLE state) and when UE122 is connected to 5GC (when UE122 is dormant in RRC_INACTIVE state).
  • RRC_CONNECTED state may be referred to as the connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), respectively, or as the RRC connected state (RRC connected mode), RRC inactive state (RRC inactive mode), and RRC idle state (RRC idle mode).
  • the UE context held by UE122 may be information including all or part of the PDU session context, security key, UE radio capability information (UE Radio Capability), and UE security capability information (UE Security Capabilities).
  • the UE context held by either or all of eNB102 and gNB108 may include the same information as the UE context held by UE122, or may include information different from the information included in the UE context held by UE122.
  • the UE context may also include all or part of the UE AS context described below.
  • the security context may be information that includes all or part of the following: an AS-level encryption key, a Next Hop parameter (NH), a Next Hop Chaining Counter parameter (NCC) used to derive the next-hop access key, an identifier for the selected AS-level encryption algorithm, and a counter used for replay protection.
  • an AS-level encryption key a Next Hop parameter (NH), a Next Hop Chaining Counter parameter (NCC) used to derive the next-hop access key, an identifier for the selected AS-level encryption algorithm, and a counter used for replay protection.
  • NH Next Hop parameter
  • NCC Next Hop Chaining Counter parameter
  • the serving cell may consist of one primary cell (PCell).
  • multiple serving cells may refer to a set of multiple cells (set of cell(s)) consisting of one or more special cells (SpCells) and all one or more secondary cells (SCells).
  • the SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated.
  • the PCell may be the cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state.
  • a group of serving cells configured by a terminal device is composed of an SpCell and one or more SCells, it may be considered that the terminal device is configuring carrier aggregation (CA). Furthermore, for a terminal device that configures CA, a cell that provides additional radio resources to the SpCell may refer to an SCell.
  • CA carrier aggregation
  • a cell group may consist of one SpCell.
  • a cell group may also consist of one SpCell and one or more SCells.
  • a cell group may consist of one SpCell and, optionally, one or more SCells.
  • a cell group may also be expressed as a set of cells (set of cell(s)).
  • Dual Connectivity may be a technology for performing data communication using the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node).
  • first base station device first node
  • second base station device second node
  • a cell group may be added from the base station device to the terminal device.
  • the first base station device may add a second base station device.
  • the first base station device may be called the master node (MN).
  • the cell group configured by the master node may be called the master cell group (MCG).
  • the second base station device may be called the secondary node (SN).
  • the cell group configured by the secondary node may be called the secondary cell group (SCG).
  • the master node and secondary node may be configured within the same base station device.
  • the cell group configured by the terminal device may be called an MCG.
  • the SpCell configured by the terminal device may be a PCell.
  • an NR in which a terminal device does not configure a DC may be called an NR standalone.
  • Multi-Radio Dual Connectivity may be a technology that performs DC using E-UTRA for the MCG and NR for the SCG.
  • MR-DC may also be a technology that performs DC using NR for the MCG and E-UTRA for the SCG.
  • MR-DC may also be a technology that performs DC using NR for both the MCG and SCG.
  • MR-DC may be a technology included in DC. Examples of MR-DC that use E-UTRA for the MCG and NR for the SCG include EN-DC (E-UTRA-NR Dual Connectivity), which uses EPC in the core network, and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity), which uses 5GC in the core network.
  • EN-DC E-UTRA-NR Dual Connectivity
  • NG-RAN E-UTRA-NR Dual Connectivity which uses 5GC in the core network.
  • MR-DC examples include NE-DC (NR-E-UTRA Dual Connectivity), which uses 5GC in the core network.
  • NR-DC NR-NR Dual Connectivity
  • NR-NR Dual Connectivity Another example of MR-DC that uses NR for both MCG and SCG.
  • a radio bearer may include an RLC bearer.
  • An RLC bearer may consist of one or two RLC entities and logical channels. If an RLC bearer has two RLC entities, the RLC entities may be a TM RLC entity, and/or a transmitting RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity.
  • SRB0 may consist of one RLC bearer.
  • the RLC bearer of SRB0 may consist of a TM RLC entity and a logical channel. SRB0 may always be established in a terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state).
  • Figure 4 is a diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment.
  • Figure 4 shows an example of the flow when RRC signaling is sent from a base station device (eNB102 and/or gNB108) to a terminal device (UE122).
  • eNB102 and/or gNB108 base station device
  • UE122 terminal device
  • Handover may be a process in which a terminal device in an RRC connected state changes the serving cell from a source SpCell to a target SpCell. Handover may be part of mobility control performed by RRC. In the terminal device, handover may be performed based on RRC signaling instructing a handover received from a base station device.
  • the RRC signaling instructing a handover may be a message related to reconfiguration of the RRC connection that includes an information element (e.g., a MobilityControlInfo information element or a ReconfigurationWithSync information element) that includes a parameter instructing a handover.
  • the MobilityControlInfo information element may be referred to as a mobility control setting information element, mobility control setting, or mobility control information.
  • the ReconfigurationWithSync information element may be referred to as a reconfiguration with synchronization information element.
  • the RRC signaling instructing a handover may be a message indicating movement to a cell of another RAT (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand).
  • the handover may be triggered by RRC.
  • the conditions under which the terminal device can perform a handover may include some or all of the following: AS security is activated; the terminal device has established an SRB2; and at least one DRB is established.
  • Figure 7 is an example of an ASN.1 description representing fields and/or information elements included in a message related to RRC connection reconfiguration in NR in Figure 4.
  • ⁇ omitted> indicates that other information has been omitted rather than being part of the ASN.1 notation. Note that information elements may be omitted even in places without the notation ⁇ omitted>.
  • the ASN.1 example represents an example of parameters of RRC signaling in this embodiment, and other names and notations may be used. Furthermore, to avoid complicating the explanation, only examples of main information closely related to this embodiment are shown in the ASN.1 example.
  • parameters described in ASN.1 may all be referred to as information elements, without distinguishing between fields, information elements, etc.
  • fields and/or information elements described in ASN.1 included in RRC signaling may be referred to as information, and in addition to or instead of information, may be referred to as parameters.
  • the message regarding the reconfiguration of the RRC connection may be an RRC reconfiguration message in NR.
  • the message regarding the reconfiguration of the RRC connection may be an RRC connection reconfiguration message in E-UTRA.
  • the message regarding the reconfiguration of the RRC connection may include an information element (MeasConfig information element) used to set, change, release, etc., measurements performed by the terminal device.
  • the MeasConfig information element may also be referred to as a measurement setting information element or measurement setting.
  • the MeasConfig information element includes a measurement object add/modify list (MeasObjectToAddModList information element), which is a list indicating one or more measurement objects to be added and/or modified; a measurement object remove list (MeasObjectToRemoveList information element), which is a list indicating one or more measurement objects to be deleted; a report configuration add/modify list (ReportConfigToAddModList information element), which is a list indicating one or more measurement reporting settings to be added and/or modified; a report configuration remove list (ReportConfigToRemoveList information element), which is a list indicating one or more measurement reporting settings to be deleted; and a list indicating one or more measurement identifiers to be added and/or modified.
  • the information element may include some or all of the following: a measurement identifier add/modify list (MeasIdToAddModList information element), which is a list indicating one or more measurement identifiers to be deleted; a measurement identifier removal list (MeasIdToRemoveList information element), which is a list indicating one or more measurement identifiers to be deleted; an S-measurement configuration (S-MeasureConfig information element), which sets a threshold for measuring the Reference Signal Received Power (RSRP) of an NR SpCell when the terminal device performs measurements in one or more cells other than the serving cell (non-serving cells); and a measurement gap configuration (MeasGapConfig information element), which is used to set up and/or release one or more measurement gaps in NR.
  • the measurement report may be interchangeably referred to as a measurement report, which will be described later.
  • the MeasObjectToAddModList information element may include one or more measurement target entries (MeasObjectToAddMod information elements). Each of these entries may include at least a measurement target identifier (MeasObjectId information element) and an information element indicating the measurement target (MeasObject information element). For example, if the MeasObject information element includes information applicable to intra-frequency/inter-frequency measurements of one or more SS/PBCH blocks (SSBs) and/or intra-frequency/inter-frequency measurements of one or more CSI-RSs, the MeasObject information element may be an information element indicating an NR measurement target (MeasObjectNR information element).
  • SSBs SS/PBCH blocks
  • CSI-RSs intra-frequency/inter-frequency measurements of one or more CSI-RSs
  • the ReportConfigToAddModList information element may include one or more measurement report configuration entries (ReportConfigToAddMod information elements). Each of the entries may include at least a measurement report configuration identifier (ReportConfigId information element) and an information element indicating the measurement report configuration (ReportConfig information element). For example, if the ReportConfig information element includes criteria for triggering an NR measurement report event or a CHO, CPA, or CPC event described below, the ReportConfig information element may be an information element indicating the NR measurement report configuration (ReportConfigNR information element).
  • the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, it performs the following (A).
  • A If any of the following conditions (A-1) to (A-4) are met, start or restart the BWP inactivity timer associated with the Active DL BWP.
  • A-1) The UE has configured a default downlink BWP identifier (defaultDownlinkBWP-Id) and the MAC entity switches to a downlink BWP that is not indicated in either the defaultDownlinkBWP-Id or the dormant BWP identifier (dormantBWP-Id).
  • the UE is not a performance-limited terminal (RedCap UE), the UE has not set a default downlink BWP identifier (defaultDownlinkBWP-Id), and the MAC entity switches to a downlink BWP that is not the initialDownlinkBWP and is not indicated by the dormant BWP identifier (dormantBWP-Id).
  • RedCap UE performance-limited terminal
  • defaultDownlinkBWP-Id default downlink BWP identifier
  • the MAC entity switches to a downlink BWP that is not the initialDownlinkBWP and is not indicated by the dormant BWP identifier (dormantBWP-Id).
  • the MAC entity shall perform some or all of the following (A) to (H) if the BWP is activated (Active BWP) and the Active DL BWP in that serving cell is not a dormant BWP: (A) Transmit UL-SCH with that BWP. (B) If the UE has configured a PRACH occasion, it transmits the RACH (PRACH) in that BWP. (C) Monitor the PDCCH with that BWP. (D) If the UE has configured a PUCCH, it transmits the PUCCH in that BWP. (E) Report the CSI in that BWP.
  • the MAC entity performs some or all of the following (A) to (L).
  • the two operation modes may be single-DCI and multi-DCI. Control of uplink and downlink operations for both modes may be performed at the PHY and MAC layers using parameters configured by the terminal device at the RRC layer.
  • single-DCI mode the terminal device may be scheduled for both TRPs using the same DCI.
  • multi-DCI mode the terminal device may be scheduled for each TRP using independent DCI.
  • Each TRP of the mTRP may be identified by TRP information.
  • the TRP information may be information for identifying one TRP among one or more TRPs.
  • the TRP information may be an index for identifying one TRP.
  • one TRP may be determined based on the TRP information.
  • the TRP information may be information for identifying one or more TRPs.
  • the TRP information may be used to select one TRP.
  • the TRP information may be a CORESET pool index.
  • One CORESET may be associated with one CORESET pool index and one CORESET resource set identifier.
  • the terminal device may transmit a PUSCH with the corresponding TRP based on the CORESET resource set identifier.
  • the TRP information may be associated with an index of the CORESET resource pool.
  • a first CORESET pool index may be associated with a first TRP
  • a second CORESET pool index may be associated with a second TRP.
  • the TRP information may be associated with a pool (or a pool index) of a TCI state.
  • a first TCI state pool (or pool index) may be associated with a first TRP
  • a second TCI state pool (or pool index) may be associated with a second TRP.
  • the two operation modes may be PDCCH repetition and single frequency network (SFN)-based PDCCH transmission.
  • the terminal device can receive each PDCCH transmission carrying the same DCI from each TRP.
  • PDCCH repetition mode the terminal device can receive two PDCCH transmissions carrying the same DCI from two linked search spaces, each associated with a different CORESET.
  • SFN-based PDCCH transmission mode the terminal device can receive two PDCCH transmissions carrying the same DCI from a single search space/CORESET using different TCI states.
  • Layer 1/Layer 2 triggered mobility may be a procedure in which a base station device transmits a MAC CE that causes a terminal device to identify one or more cells that are targets (destinations for changing) for the serving cell, and instructs the terminal device to switch (change) the serving cell or cells via the MAC CE. Additionally or alternatively, Layer 1/Layer 2 triggered mobility may be a procedure in which a terminal device receives a MAC CE from a base station device that identifies one or more cells that are targets for the serving cell, and switches (changes) the serving cell to one or more cells indicated by the MAC CE.
  • the base station device may determine the target serving cell based on a measurement report provided from the terminal device.
  • the measurement report may be a CSI report transmitted from the terminal device on a PUSCH. Additionally or alternatively, the measurement report may be a CSI report transmitted from the terminal device on a PUCCH. Additionally or alternatively, the measurement report may be a measurement report message transmitted from the terminal device as RRC signaling. Additionally or alternatively, the measurement report may be measurement report information transmitted from the terminal device as a MAC CE. The measurement report may also be other information.
  • Conditional L1/L2-triggered mobility in this embodiment may be a procedure in which a base station device transmits RRC signaling including the setting of one or more candidate serving cell targets and signaling including the setting of execution conditions to a terminal device, and through this signaling, the terminal device evaluates the state of one or more cells that it has set based on the received RRC signaling, and switches (changes) the serving cell to one or more cells that satisfy the execution conditions.
  • the terminal device does not need to receive a MAC CE that allows the terminal device to identify one or more cells that are targets (destinations) of the serving cell.
  • the terminal device performs measurements on one or more cells that are targets (change destinations) of the serving cell based on CSI resources (SS/PBCH block resource sets and/or CSI-RS resource sets), etc., to evaluate the one or more cells, but does not need to provide measurement reports such as CSI reports for the one or more cells to the base station device.
  • the execution conditions may be referred to as LTM execution conditions.
  • each LTM execution condition may set one or more events.
  • the LTM candidate target identifier may be an identifier that identifies one LTM candidate setting (LTM-Candidate information element) described below. Additionally or alternatively, the LTM candidate target identifier may be an identifier indicated by the ltm-CandidateId information element, or an identifier indicated by another information element.
  • a base station device may notify a terminal device of the configuration of one or more candidate serving cell targets.
  • the configuration of one or more candidate serving cell targets may be notified to the terminal device by RRC signaling. Additionally or alternatively, the configuration of one or more candidate serving cell targets may be notified to the terminal device by MAC CE.
  • part of the configuration of one or more candidate serving cell targets may be notified to the terminal device in advance by RRC signaling, and when changing the serving cell, another part of the configuration of the one or more candidate serving cell targets may be notified to the terminal device by MAC CE.
  • the configuration of one or more candidate serving cell targets is referred to as an LTM candidate target configuration, or simply as an LTM configuration.
  • LTM configuration the configuration of one or more candidate serving cell targets in Layer 1/Layer 2 triggered mobility and conditional Layer 1/Layer 2 triggered mobility will be referred to as LTM configuration.
  • the terminal device may store the LTM configuration notified by the base station device in the terminal device's variable (UE variable).
  • the mobility scenario (F) below may be a scenario in which the target PCell and/or one or more target SCells are not the current serving cells. Additionally or alternatively, the mobility scenario (F) below may be a scenario in which the current PCell and SCell are swapped, i.e., the target PCell and SCell become the current SCell and PCell, respectively. Additionally or alternatively, the mobility scenario (J) below may be a scenario in which, for example, conditional reconfiguration (CHO, CPA, or CPC) is applied to Layer 1/Layer 2 triggered mobility.
  • conditional reconfiguration CHO, CPA, or CPC
  • A Intra-gNB-DU (intra-gNB-DU) mobility
  • B Intra-gNB-CU and inter-gNB-DU (intra-gNB-CU and inter-gNB-DU) mobility
  • C Inter-frequency mobility (including mobility to an inter-frequency cell that is not the current serving cell)
  • D PCell change in a terminal device where CA is not configured.
  • E PCell change without change of one or more SCells in a terminal device where CA is configured.
  • F PCell change with change of one or more SCells in a terminal device where CA is configured.
  • G PSCell change without MN involvement in a terminal device where DC is configured.
  • Layer 1/Layer 2 triggered mobility the following principles (A) and/or (B) may be applied.
  • A) An LTM configuration may be provided as a delta configuration on top of a reference configuration, where the reference configuration is managed separately and the terminal device maintains the reference configuration as a separate configuration.
  • B) The user plane communicates continuously without resetting as much as possible to avoid data loss and additional delays for data recovery. For example, security information is not updated in Layer 1/Layer 2 triggered mobility. Additionally or alternatively, for example, successive Layer 1/Layer 2 triggered mobility may be performed between multiple candidates without RRC reconfiguration. Note that successive Layer 1/Layer 2 triggered mobility may refer to a procedure in which the terminal device does not release other LTM configurations after Layer 1/Layer 2 triggered mobility is performed.
  • the terminal device may store some or all of the following (A) to (J) used for LTM configuration notified from the base station device in its variables.
  • A Messages related to RRC connection reconfiguration
  • B Cell group configuration
  • C SpCell configuration and/or SCell configuration
  • D LTM reference configuration
  • E LTM candidate configuration
  • F LTM CSI resource configuration
  • G Measurement configuration
  • H CSI-MeasConfig information element
  • I Radio bearer configuration
  • conditional Layer 1/Layer 2 triggered mobility some or all of the above (A) to (J) and the following (K) to (M) may be used for LTM configuration.
  • the terminal device may store some or all of the above (A) to (J) and the following (K) to (M) used for LTM configuration notified from the base station device in variables of the terminal device. Additionally or alternatively, for example, in conditional Layer 1/Layer 2 triggered mobility, the terminal device may evaluate the status of one or more cells based on some or all of the above (A) to (J) and the following (K) to (M) used for LTM configuration notified from the base station device.
  • K) Settings related to LTM execution conditions L
  • Settings related to events set by LTM execution conditions M
  • the LTM configuration may be common between intra-distributed unit mobility and inter-distributed unit mobility within an aggregation unit, or some of the LTM configuration may be different.
  • the LTM configuration may include some or all of the system information (searchSpaceSIB1, searchSpaceOtherSystemInformation, etc.), paging messages (pagingSearchSpace, etc.), and common search spaces (commonSearchSpaceList, etc.).
  • security key updates may not be performed in Layer 1/Layer 2 triggered mobility.
  • the LTM configuration may be provided by an LTM-Config information element, or by an information element with another name.
  • the LTM configuration is a delta configuration that corresponds (with respect to) a reference configuration, it may be referred to as an LTM delta configuration, or an LTM candidate configuration, as described below.
  • the above-mentioned LTM-Config information element may include a set of configurations related to one or more LTM candidate cells. Additionally or alternatively, the above-mentioned LTM-Config information element may include reference configurations for one or more LTM candidate cells (LTM reference configurations, described below).
  • the LTM configuration (e.g., the LTM-Config information element described above) may be independent for the configuration associated with the MCG and the configuration associated with the SCG.
  • the terminal device may receive two independent LTM configurations, i.e., two independent LTM-Config information elements, for each cell group.
  • the LTM-Config information element associated with the MCG may be included in a message regarding RRC connection reconfiguration received using SRB1.
  • the LTM-Config information element associated with the SCG may be included in a message regarding RRC connection reconfiguration received using SRB3 or embedded in a message regarding RRC connection reconfiguration received using SRB1.
  • the above cell group configuration, SpCell configuration, SCell configuration, measurement configuration, and bearer configuration may use the same information elements as those included in the message regarding RRC connection reconfiguration, or may use information elements that have new parameters added and/or some or all of the parameters removed from those included in the message regarding RRC connection reconfiguration.
  • Each LTM configuration may be a message related to reconfiguration of an RRC connection.
  • the LTM configuration may include at least a cell group configuration related to an MCG.
  • the cell group configuration may include at least an SpCell configuration.
  • the cell group configuration may also include an SCell configuration.
  • the LTM configuration may include other information.
  • a cell group configuration related to an SCG may be included in the LTM configuration.
  • a measurement configuration may be included in the LTM configuration.
  • a radio bearer configuration may be included in the LTM configuration.
  • an LTM candidate target identifier for identifying each LTM configuration may be notified from the base station device to the terminal device.
  • the terminal device may receive a MAC CE from the base station device that identifies one or more cells that are targets of the serving cell, and, based on the LTM candidate target identifier indicated by the MAC CE, apply a message regarding reconfiguration of the RRC connection corresponding to the LTM candidate target identifier to the RRC configuration of the terminal device.
  • the LTM configuration may include an LTM reference configuration.
  • the LTM reference configuration may be a common configuration for all LTM candidate cells configured by the terminal device in the LTM configuration.
  • the LTM reference configuration may also include a message related to reconfiguration of the RRC connection. If the LTM configuration is notified by RRC signaling, the LTM reference configuration may be included in the LTM-Config information element.
  • the LTM reference configuration may include at least a cell group configuration related to the MCG.
  • the cell group configuration may include at least an SpCell configuration.
  • the cell group configuration may also include an SCell configuration.
  • the LTM reference configuration may include other information. For example, a cell group configuration related to the SCG may be included in the LTM reference configuration.
  • a measurement configuration may be included in the LTM reference configuration.
  • a radio bearer configuration may be included in the LTM reference configuration.
  • the LTM reference configuration may also be a reference configuration with another name.
  • the LTM reference configuration may be indicated by an ltm-referenceConfiguration information element, or by an information element with another name.
  • the LTM configuration may include an LTM candidate configuration.
  • the LTM candidate configuration may be a configuration for one of one or more candidate serving cell targets in Layer 1/Layer 2 triggered mobility and conditional Layer 1/Layer 2 triggered mobility.
  • An identifier identifying an LTM candidate configuration may be referred to as an LTM candidate target index.
  • the LTM candidate configuration may also include a message related to RRC connection reconfiguration.
  • the LTM candidate configuration may also be included in an LTM-Config information element.
  • the LTM candidate configuration may include at least a cell group configuration for an MCG.
  • the cell group configuration may include at least an SpCell configuration.
  • the cell group configuration may also include an SCell configuration.
  • the LTM candidate configuration may include other information.
  • a cell group configuration for an SCG may be included in the LTM candidate configuration.
  • a measurement configuration may be included in the LTM candidate configuration.
  • radio bearer configuration may be included in the LTM candidate configuration.
  • configuration related to LTM execution conditions may be included in the LTM candidate configuration.
  • the LTM candidate configuration may be a reference configuration with another name.
  • the LTM candidate configuration may be indicated by an LTM-Candidate information element or by an information element with another name.
  • a message related to RRC connection reconfiguration included in the LTM candidate configuration may be indicated by an LTM-CandidateConfig information element or by an information element with another name.
  • the message related to RRC connection reconfiguration included in the LTM candidate configuration may include information required to execute an LTM cell switch procedure or a conditional LTM cell switch procedure with the LTM candidate cell as a target serving cell.
  • Information required to perform the above-described LTM cell switch procedure or conditional LTM cell switch procedure may be indicated by a ReconfigurationWithSync information element, etc.
  • information required to perform the above-described LTM cell switch procedure or conditional LTM cell switch procedure may include at least information related to the parameter of timer T304 (e.g., the value of timer T304). Additionally or alternatively, information required to perform the above-described LTM cell switch procedure or conditional LTM cell switch procedure may include a ServingCellConfigCommon information element. Additionally or alternatively, the information required to perform the above-described LTM cell switching procedure or conditional LTM cell switching procedure may include a RACH-ConfigDedicated information element.
  • the terminal device may receive a MAC CE from the base station device that identifies one or more cells that are targets of the serving cell, and, based on the LTM candidate target identifier indicated by the MAC CE, apply a message regarding RRC connection reconfiguration that is stored in a terminal device variable (UE variable) and is included in the LTM candidate configuration corresponding to the LTM candidate target identifier. Additionally or alternatively, for example, the terminal device may apply a message regarding RRC connection reconfiguration that is stored in a terminal device variable and is included in the LTM candidate configuration corresponding to the LTM candidate target identifier, based on the LTM candidate target identifier that identifies the configuration of one or more cells that satisfy the LTM execution conditions.
  • UE variable terminal device variable
  • the terminal device may apply a message regarding RRC connection reconfiguration that is stored in a terminal device variable and is included in the LTM candidate configuration corresponding to the LTM candidate target identifier, based on the LTM candidate target identifier that identifies the configuration of one or more cells that
  • an LTM configuration may include an LTM CSI resource configuration (e.g., an LTM-CSI-ResourceConfig information element) that defines one or more groups of CSI resources for one or more LTM candidate configurations.
  • Each LTM CSI resource configuration may include at least an LTM CSI resource configuration identifier (e.g., an LTM-CSI-ResourceConfigId information element), which is a field used to identify an instance of the LTM-CSI-ResourceConfig information element.
  • each LTM CSI resource configuration may include at least a field (e.g., an LTM-CSI-SSB-ResourceSet information element) that defines a resource set of one SS/PBCH block from one or more LTM candidate cells, and/or a field (e.g., an LTM-CSI-RS-ResourceSet information element) that defines a resource set of one CSI-RS from one or more LTM candidate cells.
  • a field e.g., an LTM-CSI-SSB-ResourceSet information element
  • the field defining a resource set of one SS/PBCH block from one or more LTM candidate cells may include at least a list indicating resources of one or more SS/PBCH blocks (e.g., LTM-CSI-SSB-ResourceList) and a list of LTM candidate target identifiers (e.g., LTM-CandidateIdList information element) that identify each of the same number of LTM candidate cells as the number of resources of the SS/PBCH block.
  • LTM-CSI-SSB-ResourceList e.g., LTM-CSI-SSB-ResourceList
  • LTM candidate target identifiers e.g., LTM-CandidateIdList information element
  • the field defining a resource set of one CSI-RS from one or more LTM candidate cells may include at least a list indicating one or more CSI-RS resources (e.g., LTM-CSI-RS-ResourceList) and a list of LTM candidate target identifiers (e.g., LTM-CandidateIdList information element) that identify each of the same number of LTM candidate cells as the number of CSI-RS resources.
  • the field defining a resource set of one CSI-RS from one or more LTM candidate cells may be configured for each LTM candidate cell.
  • the field defining a CSI-RS resource set from one or more LTM candidate cells may be included in an LTM-Candidate information element.
  • the LTM configuration held by the terminal device in a variable may include one or more entries.
  • the entries may be referred to as "LTM candidate target entries” or “LTM entries”, etc.
  • Each LTM entry may include at least one entry identifier and one MCG cell group configuration.
  • the entry identifier may be referred to as "LTM candidate target entry identifier" or “LTM entry identifier”, etc.
  • the entry identifier may be an identifier indicated by the ltm-CandidateId information element or an identifier indicated by other information elements.
  • Each LTM entry may optionally include one or more SCG cell group configurations, one or more radio bearer configurations, and/or one or more measurement configurations, as needed.
  • a list including one or more LTM entries may be referred to as an "LTM candidate target entry list information element" or "LTM entry list", etc.
  • the LTM entry list may be included in the LTM configuration. If the LTM entry list held by the terminal device does not include any entries, the terminal device may hold an empty list.
  • the variable containing the LTM configuration held by the terminal device may be, for example, a variable named VarLTM-Config, or may be a variable with another name.
  • VarLTM-Config may consist of a variable indicating one LTM reference configuration (e.g., a variable indicated by an ltm-referenceConfiguration information element) and a list (LTM entry list) containing one or more entries (e.g., entries indicated by an LTM-Candidate information element), or other variables or lists may be included in the variable named VarLTM-Config.
  • the LTM entry list included in the variable named VarLTM-Config may be indicated by an ltm-CandidateList information element, or may be indicated by an information element with another name.
  • the terminal device may hold two independent variables named VarLTM-Config, each associated with one of the above LTM-Config information elements.
  • the LTM configuration notified to the terminal device may include a structure of add/modify (ToAddMod/ToRelease).
  • the LTM configuration notified to the terminal device may include a list of add/modify LTM entries. Specifically, when each entry identifier (e.g., LTM entry identifier) included in the list of add/modify LTM entries exists in an entry in the LTM entry list held by the terminal device, the terminal device may perform some or all of the following processes (A) to (F). Note that the list of add/modify LTM entries may be indicated by an ltm-CandidateToAddModList information element, or may be indicated by an information element with another name.
  • an entry included in the addition/modification list of an LTM entry includes a cell group setting of an MCG
  • the cell group setting of the MCG of an entry in the LTM entry list that matches the entry identifier (e.g., the ltm-CandidateId information element) associated with this entry is replaced with the cell group setting of the MCG included in the addition/modification list of that LTM entry.
  • an entry included in the addition/modification list of an LTM entry includes a cell group setting of an SCG
  • the cell group setting of the SCG of an entry in the LTM entry list that matches the entry identifier (e.g., the ltm-CandidateId information element) associated with this entry is replaced with the cell group setting of the SCG included in the addition/modification list of that LTM entry.
  • entry identifier e.g., an ltm-CandidateId information element
  • the LTM configuration notified to the terminal device may include an LTM entry deletion list.
  • the terminal device may delete (remove) entries containing identifiers specified in the LTM entry deletion list from variables held by the terminal device.
  • the LTM entry deletion list may be indicated by an ltm-CandidateToReleaseList information element, or may be indicated by an information element with another name.
  • Figure 5 is a block diagram showing the configuration of a terminal device (UE122) in this embodiment. Note that to avoid complicating the explanation, Figure 5 shows only the main components closely related to this embodiment.
  • the UE 122 shown in Figure 5 comprises a receiver 500 that receives control information (DCI, MAC CE, RRC signaling, etc.) from a base station device, a processor 502 that performs processing according to parameters included in the received control information, and a transmitter 504 that transmits control information (UCI, RRC signaling, etc.) to the base station device.
  • the base station device mentioned above may be an eNB 102 or a gNB 108.
  • the processor 502 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer).
  • the processor 502 may include some or all of the physical layer processor, MAC layer processor, RLC layer processor, PDCP layer processor, SDAP layer processor, RRC layer processor, and NAS layer processor.
  • the receiver 500 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the receiver 500 may include some or all of a physical layer receiver, a MAC layer receiver, an RLC layer receiver, a PDCP layer receiver, an SDAP layer receiver, an RRC layer receiver, and an NAS layer receiver.
  • Figure 6 is a block diagram showing the configuration of a base station device in this embodiment. Note that to avoid complicating the explanation, Figure 6 shows only the main components closely related to this embodiment.
  • the base station device mentioned above may be eNB102 or gNB108.
  • the base station device shown in FIG. 6 comprises a transmitter 600 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to UE 122, a processor 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to UE 122, causing processing unit 502 of UE 122 to process it, and a receiver 604 that receives control information (UCI, RRC signaling, etc.) from UE 122.
  • processing unit 602 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer).
  • processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit.
  • the transmitter 600 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the transmitter 600 may include some or all of a physical layer transmitter, a MAC layer transmitter, an RLC layer transmitter, a PDCP layer transmitter, an SDAP layer transmitter, an RRC layer transmitter, and an NAS layer transmitter.
  • FIG. 9 is a diagram showing an example of RRC signaling related to conditional LTM received by UE122 in this embodiment.
  • UE122 receives an entry list (e.g., LTM-MeasIdToAddModList) from a base station device (gNB108 and/or eNB102) that includes one or more entries (e.g., LTM-MeasIdToAddMod) that include at least an identifier (e.g., LTM-MeasId information element) that specifies the measurement configuration for an LTM candidate cell.
  • an entry list e.g., LTM-MeasIdToAddModList
  • entries e.g., LTM-MeasIdToAddMod
  • identifier e.g., LTM-MeasId information element
  • Each of the one or more entries included in the entry list is linked to both one LTM CSI resource configuration (e.g., LTM-CSI-ResourceConfig information element) and one conditional LTM event configuration (e.g., LTM-CondTriggerConfig information element).
  • LTM CSI resource configuration e.g., LTM-CSI-ResourceConfig information element
  • conditional LTM event configuration e.g., LTM-CondTriggerConfig information element
  • each of one or more entries included in the entry list may include one LTM CSI resource configuration identifier (e.g., an LTM-CSI-ResourceConfigId information element) and one identifier (e.g., an LTM-EventConfigId information element) that specifies an event configuration that must be met to trigger a conditional LTM cell switching process.
  • LTM CSI resource configuration identifier e.g., an LTM-CSI-ResourceConfigId information element
  • an LTM-EventConfigId information element e.g., an LTM-EventConfigId information element
  • the UE122 receives RRC signaling from a base station device (gNB108 and/or eNB102).
  • the RRC signaling may include one LTM configuration.
  • the RRC processing unit of UE122 may retain the one LTM configuration included in the RRC signaling in a terminal variable (VarLTM-Config).
  • the LTM configuration may include one LTM reference configuration and one or more LTM candidate configurations.
  • Each of the LTM candidate configurations may include at least one LTM candidate target identifier.
  • the LTM configuration may include either a cell group configuration for an MCG or a cell group configuration for an SCG. That is, each of the LTM candidate configurations in the terminal variables retained by the RRC processing unit of UE122 may include one SpCell configuration.
  • each of the LTM candidate configurations in the terminal variables retained by the RRC processing unit of UE122 may include one or more SCell configurations. Additionally or alternatively, the LTM configuration may include one or more LTM CSI resource configurations. Each of the LTM CSI resource configurations may include at least one LTM CSI resource configuration identifier. Alternatively, each of the LTM CSI resource configurations may include at least a field (e.g., an LTM-CSI-SSB-ResourceSet information element) defining a resource set of one SS/PBCH block from one or more LTM candidate cells and/or a field (e.g., an LTM-CSI-RS-ResourceSet information element) defining a resource set of one CSI-RS from one or more LTM candidate cells.
  • a field e.g., an LTM-CSI-SSB-ResourceSet information element
  • the field defining a resource set of one SS/PBCH block from one or more LTM candidate cells may include at least a list (e.g., an LTM-CSI-SSB-ResourceList) indicating resources of one or more SS/PBCH blocks, and a list (e.g., an LTM-CandidateIdList information element) of LTM candidate target identifiers identifying each of the same number of LTM candidate cells as the resources of the SS/PBCH block.
  • a list e.g., an LTM-CSI-SSB-ResourceList
  • LTM-CandidateIdList information element e.g., an LTM-CandidateIdList information element
  • the field defining one CSI-RS resource set from one or more LTM candidate cells may include at least a list indicating one or more CSI-RS resources (e.g., LTM-CSI-RS-ResourceList) and a list of LTM candidate target identifiers (e.g., LTM-CandidateIdList information elements) identifying each of the same number of LTM candidate cells as the CSI-RS resources.
  • each of the LTM CSI resource configurations may be configured for each LTM candidate cell. For example, if the LTM CSI resource configuration includes a field defining one CSI-RS resource set from one or more LTM candidate cells, the LTM CSI resource configuration may be included in an LTM-Candidate information element. Note that in this embodiment, the LTM CSI resource configuration may be configured using an information element named LTM-CSI-ResourceConfig, or may be configured using an information element with another name.
  • the RRC signaling may include some or all of the following entry lists (A-1) to (A-4).
  • A-1) An entry list including one or more entries including at least an identifier (for example, an LTM-MeasId information element) that specifies the measurement configuration for an LTM candidate cell to be evaluated in order to trigger a conditional LTM cell switching process.
  • an identifier for example, an LTM-MeasId information element
  • an identifier for example, an LTM-EventConfigId information element
  • an information element for example, an LTM-CondTriggerConfig information element
  • the entry described in (A-1) above may be linked to both the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process. Additionally or alternatively, the entry described in (A-1) above may link the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process.
  • each of the one or more entries described in (A-1) above may include an LTM CSI resource configuration identifier and an identifier that identifies the configuration of an event that must be met to trigger a conditional LTM cell switching process.
  • the entry described in (A-2) above may link both the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process. Additionally or alternatively, the entry described in (A-2) above may link the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process.
  • each of the one or more entries described in (A-2) above may include one LTM CSI resource configuration identifier.
  • the entry described in (A-3) above may link both the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process. Additionally or alternatively, the entry described in (A-3) above may link the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching process.
  • each of the one or more entries described in (A-3) above may include one LTM CSI resource configuration identifier.
  • the entry described in (A-4) above may be linked to both the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching procedure. Additionally or alternatively, the entry described in (A-4) above may link the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching procedure.
  • each of the one or more entries described in (A-4) above may include an identifier that identifies the configuration of an event that must be met to trigger a conditional LTM cell switching procedure.
  • the entry described in (A-5) above may be linked to both the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching procedure. Additionally or alternatively, the entry described in (A-5) above may link the configuration of one CSI resource used in measurements on an LTM candidate cell and the configuration of one event that must be met to trigger a conditional LTM cell switching procedure.
  • each of the one or more entries described in (A-3) above may include an identifier that identifies the configuration of an event that must be met to trigger a conditional LTM cell switching procedure.
  • each of the LTM candidate configurations may include an LTM execution condition (e.g., an LTM-CondExecutionCond information element) that configures one or more events that must be met to trigger a conditional LTM cell switching process.
  • each of the events may correspond to an identifier that identifies a measurement configuration for an LTM candidate cell that is to be evaluated to trigger a conditional LTM cell switching process.
  • each of the events may correspond to an identifier that identifies a configuration of events that must be met to trigger a conditional LTM cell switching process.
  • each of the events may correspond to an LTM CSI resource configuration identifier.
  • UE122 may perform conditional LTM if it determines that an entry received from a base station device (gNB108 and/or eNB102) links one LTM CSI resource configuration and one conditional LTM event configuration.
  • a base station device gNB108 and/or eNB102
  • UE122 may evaluate one or more LTM candidate cells if it determines that an entry included in the RRC signaling received from a base station device (gNB108 and/or eNB102) includes one LTM CSI resource configuration identifier and one identifier that identifies the event configuration that must be met to trigger the conditional LTM cell switching process, and that the RRC signaling includes the LTM CSI resource configuration and the event configuration that must be met to trigger the conditional LTM cell switching process identified by each of the identifiers.
  • a base station device gNB108 and/or eNB102
  • UE122 may perform measurements on one or more LTM candidate cells based on one or more CSI resources (SS/PBCH block resource sets and/or CSI-RS resource sets) specified in the LTM CSI resource configuration associated with each of the entries of (A-1).
  • CSI resources SS/PBCH block resource sets and/or CSI-RS resource sets
  • UE122 may evaluate one or more LTM candidate cells using a conditional LTM event configuration associated with the same entry as the LTM CSI resource configuration.
  • UE122 may not evaluate one or more LTM candidate cells if it determines that the entry included in the RRC signaling received from the base station device (gNB108 and/or eNB102) includes one LTM CSI resource configuration identifier and one identifier identifying an event configuration that must be satisfied to trigger a conditional LTM cell switching process, but that the RRC signaling does not include either the LTM CSI resource configuration identified by each of the identifiers or the event configuration that must be satisfied to trigger a conditional LTM cell switching process.
  • UE122 may not evaluate one or more LTM candidate cells.
  • UE122 may evaluate one or more LTM candidate cells when it determines that an entry included in the RRC signaling received from a base station device (gNB108 and/or eNB102) includes one LTM CSI resource configuration identifier and one conditional LTM event configuration, and that the LTM CSI resource configuration identified by the LTM CSI resource configuration identifier is included in the RRC signaling.
  • a base station device gNB108 and/or eNB102
  • the UE 122 may evaluate one or more LTM candidate cells using an information element included in the entry (A-4) above, which includes a setting of an event that must be met to trigger a conditional LTM cell switch procedure.
  • the UE 122 may evaluate one or more LTM candidate cells using an information element included in the entry (A-5) above, which selects an event trigger criterion for the conditional LTM cell switch procedure.
  • UE122 may switch the serving cell to an LTM candidate cell that satisfies the LTM execution conditions based on the results of evaluation of one or more LTM candidate cells. Additionally or alternatively, in each of the above-described operations of UE122, UE122 may switch the serving cell to an LTM candidate cell that satisfies all events based on the results of evaluation of one or more LTM candidate cells.
  • UE122 may evaluate one or more LTM candidate cells using an information element included in the entry (A-4) above, including the configuration of events that must be satisfied to trigger a conditional LTM cell switch procedure, and if it determines based on the evaluation results that all events associated with a certain entry and configured in the configuration of events that must be satisfied to trigger a conditional LTM cell switch procedure are satisfied, apply a message related to reconfiguration of an RRC connection corresponding to an LTM candidate target identifier that identifies the LTM candidate cell associated with this entry to the RRC configuration of UE122.
  • the LTM candidate cells to be measured and evaluated to trigger the conditional LTM cell switching process may be some or all of one or more LTM candidate cells configured in one LTM candidate configuration.
  • the UE 122 may perform at least one of the following operations (C-1) to (C-3).
  • C-1) Before evaluating the LTM execution conditions, downlink synchronization is performed with one or more LTM candidate cells.
  • C-2 Before determining whether one or more conditions or events for triggering an LTM cell switching process are satisfied, downlink synchronization is performed with one or more LTM candidate cells.
  • C-3) Before determining an LTM candidate cell for which the LTM execution condition is to be evaluated, downlink synchronization with one or more LTM candidate cells is performed.
  • timer once a timer is started, it continues to run until it is stopped or expires. Once a timer expires, it may be considered to be no longer running (stopped). A timer always starts (if the timer is stopped) or restarts (if the timer is running) from its initial value. The period from when a timer is started or restarted to when it expires is not updated until the timer is stopped or expires.
  • the MAC entity of the terminal device may use the period from when a timer is started or restarted to when it expires as a value notified by a higher layer (e.g., the RRC layer).
  • terminal device variables such as “terminal device variables,” “terminal variables,” and “variables” may be used interchangeably.
  • part of the device in the above-described embodiments may be implemented by a computer.
  • the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read and executed by a computer system.
  • the term "computer system” here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices.
  • the term "computer-readable recording medium” may be any of a semiconductor recording medium, optical recording medium, magnetic recording medium, etc.
  • “computer-readable recording medium” may include something that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or something that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such cases.
  • the above program may be one that realizes some of the functions described above, or one that can realize the functions described above in combination with a program already recorded in the computer system.
  • each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, typically an integrated circuit or multiple integrated circuits.
  • the electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
  • the general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology result in the emergence of integrated circuit technology that can replace current integrated circuits, integrated circuits based on that technology may also be used.
  • this embodiment is not limited to the above-described embodiment. While one example of a device has been described in the embodiment, this embodiment is not limited to this and can be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
  • terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
  • One aspect of the present invention can be used, for example, in communication systems, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.
  • communication devices e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices
  • integrated circuits e.g., communication chips
  • E-UTRA 102 eNB 104 EPC 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interfaces 122UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 Processing section 504, 600 Transmitter

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Le présent dispositif terminal qui communique avec un dispositif de station de base comprend une unité de réception qui reçoit une signalisation RRC comprenant une première liste d'entrées provenant du dispositif de station de base. Une ou plusieurs entrées, qui sont incluses dans la première liste d'entrées, relient chacune une configuration de ressource CSI LTM et une configuration d'événement LTM conditionnelle.
PCT/JP2025/011038 2024-03-25 2025-03-21 Dispositif terminal, procédé et circuit intégré Pending WO2025205431A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2024047411 2024-03-25
JP2024-047411 2024-03-25

Publications (1)

Publication Number Publication Date
WO2025205431A1 true WO2025205431A1 (fr) 2025-10-02

Family

ID=97216702

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2025/011038 Pending WO2025205431A1 (fr) 2024-03-25 2025-03-21 Dispositif terminal, procédé et circuit intégré

Country Status (1)

Country Link
WO (1) WO2025205431A1 (fr)

Similar Documents

Publication Publication Date Title
JP2024102379A (ja) 端末装置、方法、および、集積回路
JP7766506B2 (ja) 端末装置、方法、および、集積回路
WO2025205431A1 (fr) Dispositif terminal, procédé et circuit intégré
US12273236B2 (en) Terminal apparatus, base station apparatus, and method
JP7785751B2 (ja) 端末装置、方法、および、集積回路
EP4590023A1 (fr) Dispositif terminal, procédé et circuit intégré
US20250056410A1 (en) Terminal apparatus, method, and integrated circuit
WO2024190124A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025142358A1 (fr) Équipement terminal, procédé et circuit intégré
WO2025033421A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024096097A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2025033418A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024058073A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025192703A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025057810A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024142971A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025028491A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024171852A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025028657A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024171638A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2024171627A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025070742A1 (fr) Dispositif terminal, procédé et circuit intégré
JP2024162582A (ja) 端末装置、方法、および集積回路
WO2025023297A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2025022679A1 (fr) Dispositif terminal, procédé et circuit intégré

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: 25778584

Country of ref document: EP

Kind code of ref document: A1