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

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

Info

Publication number
WO2024029478A1
WO2024029478A1 PCT/JP2023/027917 JP2023027917W WO2024029478A1 WO 2024029478 A1 WO2024029478 A1 WO 2024029478A1 JP 2023027917 W JP2023027917 W JP 2023027917W WO 2024029478 A1 WO2024029478 A1 WO 2024029478A1
Authority
WO
WIPO (PCT)
Prior art keywords
rrc
terminal device
mac
reconfiguration procedure
layer
Prior art date
Application number
PCT/JP2023/027917
Other languages
English (en)
Japanese (ja)
Inventor
恭輔 井上
昇平 山田
秀和 坪井
拓真 河野
Original Assignee
シャープ株式会社
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 シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2024029478A1 publication Critical patent/WO2024029478A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • 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
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present invention relates to a terminal device, a method, and an integrated circuit.
  • This application claims priority to Japanese Patent Application No. 2022-124608 filed in Japan on August 4, 2022, the contents of which are incorporated herein.
  • 3GPP 3rd Generation Partnership Project
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • RAT Radio Access Technology
  • 3GPP 3GPP is still conducting technical studies and standardization for E-UTRA expansion technology.
  • E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and the extended technology is also referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • NR New Radio, or NR Radio access
  • 5G 5th Generation
  • a serving cell change technology that allows a terminal device to move from the coverage area of one cell to the coverage area of another cell.
  • This serving cell change is triggered by layer 3 (also referred to as RRC) measurements, and synchronized reconfiguration for serving cell change is triggered by RRC signaling.
  • layer 1 or layer 2 signaling has the advantage of low latency and low overhead. Therefore, studies have begun on techniques for changing serving cells triggered by layer 1 or layer 2 signaling (layer 1/layer 2 mobility enhancement techniques).
  • Non-Patent Document 7 is the RRC specification before the study of layer 1/layer 2 mobility optimization technology was started. However, when triggering a serving cell change using Layer 1 or Layer 2 signaling, the problem remains that certain processes may cause unnecessary delays.
  • One aspect of the present invention has been made in view of the above circumstances, and one of the objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently control communication. .
  • one embodiment of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with a base station device, which includes a receiving unit that receives radio resource control (RRC) signaling from the base station device, and a receiving unit that triggers and performs an RRC reconfiguration procedure. and a MAC processing unit that triggers the RRC reconfiguration procedure.
  • RRC radio resource control
  • the RRC processing unit submits signaling indicating completion of the RRC reconfiguration procedure;
  • the RRC processing unit notifies the MAC processing unit of the completion of the RRC reconfiguration procedure after executing the RRC reconfiguration procedure, and
  • the MAC processing unit transmits a MAC CE indicating completion of the RRC reconfiguration procedure based on being notified of the completion of the RRC reconfiguration procedure from the RRC processing unit.
  • one aspect of the present invention is a method for a terminal device to communicate with a base station device, the method comprising: receiving radio resource control (RRC) signaling from the base station device; performing an RRC reconfiguration procedure based on receiving RRC signaling or based on performing conditional reconfiguration; and if the RRC reconfiguration procedure is triggered by RRC of the terminal device; RRC of the terminal device submits signaling indicating completion of an RRC reconfiguration procedure; and if the RRC reconfiguration procedure is triggered by a MAC of the terminal device, the RRC of the terminal device: After executing the RRC reconfiguration procedure, the MAC of the terminal device is notified of the completion of the RRC reconfiguration procedure, and the MAC of the terminal device is notified of the completion of the RRC reconfiguration procedure by the RRC of the terminal device. and transmitting a MAC CE indicating completion of the RRC reconfiguration procedure.
  • RRC radio resource control
  • Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the integrated circuit having a function of receiving radio resource control (RRC) signaling from the base station device, and a function of receiving radio resource control (RRC) signaling from the base station device; a function in which the RRC of the device executes an RRC reconfiguration procedure based on receiving the RRC signaling or based on execution of conditional reconfiguration; a function for the RRC of the terminal device to submit signaling indicating completion of the RRC reconfiguration procedure if triggered by the MAC of the terminal device; After the RRC of the terminal device executes the RRC reconfiguration procedure, the RRC of the terminal device notifies the MAC of the terminal device of the completion of the RRC reconfiguration procedure, and the MAC of the terminal device receives the RRC reconfiguration from the RRC of the terminal device. Based on being notified of the completion of the procedure, exhibit the ability to send a MAC CE indicating completion of the RRC reconfiguration procedure.
  • RRC radio
  • a terminal device, a method, and an integrated circuit can realize efficient communication control processing.
  • FIG. 1 is a schematic diagram of a communication system according to the present embodiment.
  • FIG. 2 is a diagram illustrating an example of the E-UTRA protocol configuration according to the present embodiment.
  • FIG. 3 is a diagram illustrating an example of the NR protocol configuration according to the present embodiment.
  • FIG. 3 is a diagram illustrating an example of a flow of procedures for various settings in RRC according to the present embodiment.
  • FIG. 2 is a block diagram showing the configuration of a terminal device in this embodiment.
  • FIG. 2 is a block diagram showing the configuration of a base station device in this embodiment.
  • An example of ASN.1 description included in the serving cell common settings in this embodiment.
  • LTE and LTE-A, LTE-A Pro
  • NR may be defined as different radio access technologies (RAT).
  • RAT radio access technologies
  • LTE may be defined as a technology included in LTE.
  • LTE may be defined as a technology included in NR.
  • LTE which can be connected to NR using Multi-Radio Dual Connectivity (MR-DC)
  • MR-DC Multi-Radio Dual Connectivity
  • LTE that uses 5GC in the core network Core Network: CN
  • CN Core Network
  • conventional LTE may be LTE that does not implement the technology standardized after Release 15 in 3GPP.
  • This embodiment may be applied to NR, LTE and other RATs.
  • E-UTRA in this embodiment may be replaced with the term LTE
  • LTE may be replaced with the term E-UTRA.
  • each node and entity and the processing in each node and entity will be explained when the radio access technology is E-UTRA or NR. However, this embodiment is applicable to other radio access technologies. May be used. The names of each node and entity in this embodiment may be different names.
  • FIG. 1 is a schematic diagram of a communication system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. explained using FIG. 1 are some functions closely related to this embodiment, and may have other functions.
  • E-UTRA100 may be a radio access technology. Further, the E-UTRA 100 may be an air interface between the UE 122 and the eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface.
  • the eNB (E-UTRAN Node B) 102 may be a base station device of the E-UTRA 100.
  • the eNB 102 may have the E-UTRA protocol described below.
  • the E-UTRA protocol may be composed of an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA Control Plane (CP) protocol, which will be described later.
  • the eNB 102 may terminate the E-UTRA user plane (UP) protocol and the E-UTRA control plane (CP) protocol for the UE 122.
  • a radio access network composed of eNBs may be called E-UTRAN.
  • the EPC (Evolved Packet Core) 104 may be a core network.
  • Interface 112 is an interface between eNB 102 and EPC 104, and may be called an S1 interface.
  • the interface 112 may include 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) within EPC 104 .
  • MME Mobility Management Entity
  • S-GW serving gateway
  • the control plane interface of interface 112 may be referred to as the S1-MME interface.
  • the user plane interface of interface 112 may be referred to as the S1-U interface.
  • one or more eNBs 102 may be connected to the EPC 104 via the interface 112.
  • An interface may exist between multiple eNBs 102 connected to the EPC 104 (not shown).
  • the interface between the plurality of 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 an air interface between UE122 and gNB108.
  • the air interface between UE 122 and gNB 108 may be referred to as a Uu interface.
  • gNB (g Node B) 108 may be a base station device of NR106.
  • gNB 108 may have the NR protocol described below.
  • the NR protocol may include an NR user plane (UP) protocol, which will be described later, and an NR control plane (CP) protocol, which will be described later.
  • the gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.
  • UP NR user plane
  • CP NR control plane
  • 5GC110 may be a core network.
  • Interface 116 is an interface between gNB 108 and 5GC 110, and may be called an NG interface.
  • the interface 116 may include 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 in an Access and Mobility Management Function (AMF: not shown) within 5GC 110.
  • AMF Access and Mobility Management Function
  • the user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110.
  • 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 the interface 116.
  • An interface may exist between multiple gNBs 108 connected to 5GC 110 (not shown).
  • the interface between multiple gNBs 108 connected to 5GC 110 may be called an Xn interface.
  • eNB102 may have the ability to connect to 5GC110.
  • the eNB 102 that has the function of connecting to the 5GC 110 may be called an ng-eNB.
  • Interface 114 is an interface between eNB 102 and 5GC 110, and may be called an NG interface.
  • the interface 114 may include 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 114 may terminate at an AMF within 5GC 110.
  • the user plane interface of interface 114 may terminate at a UPF within 5GC 110.
  • the control plane interface of interface 114 may be referred to as an NG-C interface.
  • the user plane interface of interface 114 may be referred to as an NG-U interface.
  • a radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN.
  • NG-RAN, E-UTRAN, etc. may also be simply referred to as networks.
  • the network may include eNB, ng-eNB, gNB, and the like.
  • one or more eNBs 102 may be connected to the 5GC 110 via the interface 114.
  • An interface may exist between multiple eNBs 102 connected to 5GC 110 (not shown).
  • the interface between the plurality of eNBs 102 connected to the 5GC 110 may be referred to as an Xn interface.
  • the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be connected through an interface 120.
  • the interface 120 between the eNB 102 that connects to the 5GC 110 and the gNB 108 that connects to the 5GC 110 may be called an Xn interface.
  • gNB108 may have the function of connecting to EPC104.
  • gNB 108 having the function of connecting to EPC 104 may be called en-gNB.
  • Interface 118 is an interface between gNB 108 and EPC 104, and may be called an S1 interface.
  • Interface 118 may include 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 EPC 104.
  • the user plane interface of interface 118 may be referred to as the S1-U interface.
  • the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected through an interface 120.
  • the interface 120 between the eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be called an X2 interface.
  • the interface 124 is an interface between the EPC 104 and the 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of the interfaces 114, 116, 118, 120, 124, etc. may not exist depending on the communication system provided by the communication carrier or the like.
  • the UE 122 may be a terminal device that can receive system information and paging messages transmitted from the eNB 102 and/or gNB 108. Further, the UE 122 may be a terminal device that can be wirelessly connected to the eNB 102 and/or the gNB 108. Further, the UE 122 may be a terminal device that can simultaneously perform a wireless connection with the eNB 102 and a wireless connection with the gNB 108. UE 122 may have an E-UTRA protocol and/or an NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.
  • RRC Radio Resource Control
  • the UE 122 may be a terminal device that can be connected to the EPC 104 and/or 5GC 110 via the eNB 102 and/or gNB 108.
  • each data radio bearer (DRB) established between UE122 and eNB102 and/or gNB108 (to be described later) ) may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104.
  • EPS Evolved Packet System
  • Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID).
  • the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames that pass through the same EPS bearer.
  • each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110. It may be linked to one of the PDU (Packet Data Unit) sessions. There may be one or more QoS flows in each PDU session. Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flows.
  • Each PDU session may be identified by a PDU session identifier (Identity, or ID). Further, each QoS flow may be identified by a QoS flow identifier (Identity or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.
  • the EPC 104 There may be no PDU sessions and/or QoS flows in the EPC 104. Also, 5GC110 does not need to have an EPS bearer. When the UE 122 is connected to the EPC 104, the UE 122 has information on the EPS bearer, but may not have information on the PDU session and/or QoS flow. Further, when the UE 122 is connected to the 5GC 110, the UE 122 has information on the PDU session and/or QoS flow, but does not need to have information on the EPS bearer.
  • the eNB 102 and/or gNB 108 will also be simply referred to as a base station device, and the UE 122 will also be simply referred to as a terminal device or UE.
  • FIG. 2 is a diagram of an example of the E-UTRA protocol architecture according to the present embodiment.
  • FIG. 3 is a diagram of an example of the NR protocol configuration according to the present embodiment. Note that the functions of each protocol explained using FIG. 2 and/or FIG. 3 are some functions closely related to this embodiment, and may have other functions.
  • the uplink (UL) may be a link from a terminal device to a base station device.
  • the downlink (DL) may be a link from a base station device to a terminal device.
  • FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack.
  • the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side.
  • the E-UTRA user plane protocol stack consists of a wireless physical layer (PHY) 200, a medium access control layer (MAC) 200, and a medium access control layer (MAC).
  • 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 includes a radio physical layer PHY300, a medium access control layer MAC302, a radio link control layer RLC304, a packet data convergence protocol layer PDCP306, and It may be configured from SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.
  • 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
  • the NAS 210 may be a protocol that terminates with the MME on the network side.
  • Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration.
  • RRC 308 which is a radio resource control layer
  • RRC308 may be a protocol that terminates at gNB108 on the network side.
  • the NAS 312, which is a non-AS layer may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates with 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 gNB 108. That is, the AS layer is a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, and RRC208, and/or a layer that includes some or all of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308. It's fine.
  • the following does not distinguish between the E-UTRA protocol and the NR protocol, and uses PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer).
  • NAS NAS layer
  • PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are the PHY (PHY layer) of the E-UTRA protocol.
  • the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively defined as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA, or It is also called MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE.
  • PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA It may also be written as RRC or LTE RRC.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There are some things.
  • PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes written as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.
  • Entities in the AS layer of E-UTRA and/or NR will be explained.
  • 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 replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.
  • MAC PDU Protocol Data Unit
  • RLC Network Data Unit
  • RLC Physical Location
  • SDAP Secure Protocol
  • data provided from the upper layer to MAC, RLC, PDCP, and SDAP, and/or data provided from MAC, RLC, PDCP, and SDAP to the upper layer are MAC SDU (Service Data Unit) and RLC SDU, respectively.
  • MAC SDU Service Data Unit
  • RLC SDU Service Data Unit
  • PDCP SDU Secure Data Unit
  • SDAP SDU Secure Data Unit
  • a segmented RLC SDU may be referred to as an RLC SDU segment.
  • the base station device and the terminal device exchange (transmit and receive) signals in 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, and RRC signaling) in a radio resource control (RRC) layer.
  • RRC radio resource control
  • the base station device and the terminal device may transmit and receive MAC control elements in the MAC (Medium Access Control) layer.
  • the RRC layer of the terminal device acquires system information broadcast from the base station device.
  • the RRC message, system information, and/or MAC control element is also referred to as a higher layer signal (higher layer signal) or a higher layer parameter (higher layer parameter).
  • upper layer refers to the upper layer seen from the PHY layer, so it refers to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. Good too.
  • the upper layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like.
  • A is given (provided) by the upper layer” and “A is given (provided) by the upper layer” mean the upper layers of the terminal device (mainly the RRC layer and MAC layer).
  • A is received from the base station device, and the received A is given (provided) from an upper layer of the terminal device to the physical layer of the terminal device.
  • being “provided with upper layer parameters” means that the upper layer parameter included in the received upper layer signal is received from the base station device, and the upper layer parameter included in the received upper layer signal is transmitted from the upper layer of the terminal device to the terminal device.
  • Setting upper layer parameters to a terminal device may mean that 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 to the terminal device may include setting default parameters given in advance to the upper layer of the terminal device.
  • the expression "submit" a message from the RRC entity of the terminal device to a lower layer may be used.
  • "submitting a message to a lower layer” from an RRC entity may mean submitting a message to a PDCP layer.
  • "submitting a message from the RRC layer to a lower layer” means that RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), so It may also mean submitting to the corresponding PDCP entity.
  • the lower layer may refer to one or more of a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and the like.
  • the PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel.
  • the PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an 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 a transport channel.
  • the PHY may also be provided with data from the MAC via a transport channel.
  • RNTI Radio Network Temporary Identifier
  • the physical channels used for wireless communication between the terminal device and the base station device 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 a 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 may be defined for transmission of downlink control information. That is, a field for downlink control information may be defined as DCI and mapped to information bits.
  • PDCCH may be transmitted on PDCCH candidates.
  • a terminal device may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode a PDCCH according to a certain DCI format.
  • the terminal device may use CORESET (Control Resource Set) to monitor the set of PDCCH candidates.
  • the DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmitting user data, transmitting an RRC message, which will be described later, and the like.
  • 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) used to indicate the state of a downlink channel.
  • the uplink control information may also include a scheduling request (SR) used to request UL-SCH (Uplink Shared CHannel) resources.
  • SR scheduling request
  • the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).
  • the PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Further, in the case of the downlink, the PDSCH may be used to transmit system information (SI), random access response (RAR), and the like.
  • SI system information
  • RAR random access response
  • PUSCH may be used to transmit HARQ-ACK and/or CSI along with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. Further, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH may be used to transmit only UCI. Additionally, the PDSCH or PUSCH may be used to transmit RRC signaling (also referred to as RRC message) and MAC CE.
  • RRC signaling also referred to as RRC message
  • the RRC signaling transmitted from the base station device may be common signaling to multiple terminal devices within the cell. Further, the RRC signaling transmitted from the base station device may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device. That is, terminal device-specific (UE-specific) information may be transmitted to a certain terminal device using dedicated signaling. Further, PUSCH may be used to transmit UE Capability in the uplink.
  • PRACH may be used to transmit a random access preamble.
  • PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmission, and requests for UL-SCH resources. You can.
  • MAC may be called a MAC sublayer.
  • the MAC may have a function of mapping various logical channels to corresponding transport channels.
  • a logical channel may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID).
  • Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information to be transmitted. Further, logical channels may be divided into uplink logical channels and downlink logical channels.
  • the MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing the same to the PHY.
  • the MAC may also have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer via the logical channel to which each MAC SDU belongs.
  • the MAC may also have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest).
  • HARQ Hybrid Automatic Repeat reQuest
  • the MAC may also have the ability to report scheduling information.
  • the MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Further, the MAC may have a function of performing priority processing between logical channels within one terminal device.
  • the MAC may have a function to prioritize resources that overlap within one terminal device.
  • E-UTRA MAC may have the function of identifying Multimedia Broadcast Multicast Services (MBMS).
  • MBMS Multimedia Broadcast Multicast Services
  • the NR MAC may also have a function of identifying multicast/broadcast service (MBS).
  • MBS multicast/broadcast service
  • the MAC may have the ability to select the transport format.
  • MAC is a power head that has the function of performing discontinuous reception (DRX) and/or discontinuous transmission (DTX), the function of executing random access (RA) procedure, and the function of notifying information on transmittable power. It may have a room report (Power Headroom Report: PHR) function, a buffer status report (Buffer Status Report: BSR) function that notifies information on the amount of data in the transmission buffer, etc.
  • NR MAC may have a Bandwidth Adaptation (BA) function.
  • BA Bandwidth Adaptation
  • the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different.
  • the MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for controlling the MAC.
  • MAC control element MAC CE
  • the BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI).
  • SI system information
  • PCCH Packet Control Channel
  • PCCH Packet Control Channel
  • CCCH Common Control Channel
  • CCCH may be a logical channel for transmitting control information between a terminal device and a base station device.
  • CCCH may be used when the terminal device does not have an RRC connection. Further, CCCH may be used between a base station device and multiple terminal devices.
  • DCCH Dedicated Control Channel
  • the dedicated control information may be control information dedicated to each terminal device.
  • DCCH may be used when the terminal device has an RRC connection.
  • DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device.
  • DTCH may be a logical channel for transmitting dedicated user data.
  • the dedicated user data may be user data dedicated to each terminal device.
  • DTCH may exist on both uplink and downlink.
  • CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • the DCCH may be mapped to a UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.
  • UL-SCH Uplink Shared Channel
  • the BCCH may be mapped to a BCH (Broadcast Channel), which is a downlink transport channel, and/or a DL-SCH (Downlink Shared Channel).
  • BCH Broadcast Channel
  • DL-SCH Downlink Shared Channel
  • the PCCH may be mapped to a PCH (Paging Channel), which is a downlink transport channel.
  • PCH Packet Control Channel
  • CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • the DCCH may be mapped to a DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • DTCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.
  • DL-SCH Downlink Shared Channel
  • RLC may be referred to as an RLC sublayer.
  • the E-UTRA RLC may have a function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer.
  • the E-UTRA RLC may have a function of reassembling and re-ordering data provided from lower layers and providing the data to upper layers.
  • NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to data provided from the upper layer PDCP.
  • NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers.
  • the NR RLC may have a function of reassembling data provided from lower layers and providing the data to upper layers.
  • RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Additionally, RLC may have a function of performing error correction using ARQ. Control information indicating data that needs to be retransmitted, which is sent from the RLC receiving side to the transmitting side in order to perform ARQ, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be referred to as a poll. The RLC may also have a function to detect data duplication. RLC may also have a data discard function. RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM).
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledged mode
  • the TM does not divide data received from the upper layer and does not need to add an RLC header.
  • a TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity.
  • data received from the upper layer is divided and/or combined, RLC headers are added, etc., but there is no need to control data retransmission.
  • a UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UMRLC entity.
  • the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.
  • the AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.
  • data provided to a lower layer by a TM and/or data provided from a lower layer may be referred to as a TMD PDU.
  • data provided to lower layers in UM and/or data provided from lower layers may be referred to as UMD PDU.
  • data provided to lower layers in AM or data provided from lower layers may be referred to as AMD PDU.
  • the RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different.
  • the RLC PDU may include a data RLC PDU and a control RLC PDU.
  • the RLC PDU for data may be called RLC DATA PDU (RLC Data PDU, RLC data PDU).
  • the control RLC PDU may be referred to as RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).
  • PDCP may be called a PDCP sublayer.
  • PDCP may have a function to perform sequence number maintenance.
  • PDCP may have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section.
  • the protocol used to compress and decompress the header of IP packets can be called the ROHC (Robust Header Compression) protocol.
  • the protocol used for compressing and decompressing Ethernet frame headers may be referred to as the EHC (Ethernet (registered trademark) Header Compression) protocol.
  • EHC Errnet (registered trademark) Header Compression
  • PDCP may have data encryption/decryption functions.
  • PDCP may have data integrity protection/integrity verification functions.
  • PDCP may also have a re-ordering function.
  • PDCP may also have a PDCP SDU retransmission function.
  • PDCP may have a function of discarding data using a discard timer.
  • PDCP may have a multiplexing (Duplication) function.
  • PDCP may have a function of discarding data that has been received repeatedly.
  • the PDCP entity is a bidirectional entity and may include a transmitting PDCP entity and a receiving PDCP entity.
  • the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different.
  • the PDCP PDU may include a data PDCP PDU and a control PDCP PDU.
  • the data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU).
  • the control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).
  • SDAP is a service data adaptation protocol layer.
  • SDAP maps the downlink QoS flow sent from 5GC110 to the terminal device via the base station device and the data radio bearer (DRB), and/or the mapping from the terminal device to the terminal device via the base station device. It may have a function to map uplink QoS flows sent to 5GC110 and DRB.
  • SDAP may also have a function of storing mapping rule information.
  • SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI).
  • QFI QoS flow ID
  • the SDAP PDU may include a data SDAP PDU and a control SDAP PDU.
  • SDAP PDU for data may be called SDAP DATA PDU (SDAP Data PDU, SDAP data PDU).
  • control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that one SDAP entity of the terminal device may exist for a PDU session.
  • RRC may have a broadcast function.
  • the RRC may have a paging function from the EPC 104 and/or 5GC 110.
  • the RRC may have a paging function from the eNB 102 that connects to the gNB 108 or 5GC 110.
  • RRC may also have RRC connection management functionality.
  • RRC may also have radio bearer control functionality.
  • the RRC may also have a cell group control function.
  • the RRC may also have mobility control functionality.
  • the RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions.
  • RRC may also have QoS management functionality.
  • RRC may also have radio link failure detection and recovery functionality.
  • RRC uses RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. You may do so. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.
  • the RRC message may be sent using the BCCH of a logical channel, the PCCH of a logical channel, the CCCH of a logical channel, or the DCCH of a logical channel. May be sent. Furthermore, the RRC message sent using the DCCH may be referred to as dedicated RRC signaling or RRC signaling.
  • the RRC message sent using the BCCH may include, for example, a master information block (MIB), each type of system information block (SIB), and other RRC messages may be included.
  • 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 include, for example, RRC Setup Request message, RRC Resume Request message, RRC Reestablishment Request message, It may include an RRC system information request message (RRC System Info Request), etc. Further, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. may be included. Other RRC messages may also be included.
  • RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject message, RRC Connection Setup message, RRC Connection Reestablishment message, It may include an RRC Connection Reestablishment Reject message, etc. Further, for example, an RRC rejection message (RRC Reject), an RRC Setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.
  • RRC signaling sent in the uplink (UL) direction using DCCH includes, for example, measurement report messages, RRC Connection Reconfiguration Complete messages, and RRC Connection Setup Complete messages. ), an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, and the like. Also, for example, measurement report message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message. ), a security mode complete message (Security Mode Complete), a UE Capability Information message, and the like may be included. Other RRC signaling may also be included.
  • RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration message, RRC Connection Release message, Security Mode Command message, It may include a UE Capability Inquiry message, etc. Also, for example, RRC Reconfiguration message, RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE capability inquiry message. (UE Capability Inquiry) etc. may be included. Other RRC signaling may also be included.
  • the NAS may have an authentication function.
  • the NAS may also have the ability to perform mobility management.
  • the NAS may also have security control functions.
  • the UE 122 connecting to the EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established.
  • the state in which the RRC connection is established may include a state in which the UE 122 holds some or all of the UE context described below.
  • the state in which the RRC connection is established may include a state in which the UE 122 can transmit and/or receive unicast data.
  • the UE 122 when the RRC connection is suspended, the UE 122 may be in the RRC_INACTIVE state. Further, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is suspended.
  • the UE 122 may be in the RRC_IDLE state.
  • the E-UTRAN may start suspending the RRC connection.
  • the UE 122 may transition to the RRC_IDLE state while retaining the UE's AS context and an identifier (resumeIdentity) used for resuming.
  • the layer above the RRC layer of the UE 122 (for example, the NAS layer) is configured such that the UE 122 maintains the UE's AS context, the E-UTRAN permits the return of the RRC connection, and the UE 122 leaves the RRC_IDLE state.
  • recovery of the suspended RRC connection may be initiated.
  • the definition of pause may be different between the UE 122 connecting to the EPC 104 and the UE 122 connecting to the 5GC 110. Also, when the UE122 is connected to the EPC (when the UE122 is inactive in the RRC_IDLE state) and when the UE122 is connected to the 5GC (when the UE122 is inactive in the RRC_INACTIVE state), the UE122 All or part of the procedure for returning from hibernation may be different.
  • RRC_CONNECTED state may be respectively called connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), and RRC connected state (RRC connected mode). , RRC inactive mode, and RRC idle mode.
  • the AS context of the UE held by the UE122 includes the current RRC settings, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, and the C-RNTI (Cell Radio) used in the PCell of the connection source (Source).
  • the information may include all or part of the Network Temporary Identifier, cell identifier (cellIdentity), and physical cell identifier of the connection source PCell.
  • the UE AS context held by any or all of eNB 102 and gNB 108 may include the same information as the UE AS context held by UE 122, or the information contained in the UE AS context held by UE 122. may contain information different from that.
  • the security context includes the encryption key at the AS level, the NH (Next Hop parameter), the NCC (Next Hop Chaining Counter parameter) used to derive the next hop access key, the identifier of the selected AS-level encryption algorithm, and replay protection.
  • the information may include all or part of the counter used for
  • the serving cell In a terminal device in an RRC connected state in which CA and/or DC, which will be described later, are not configured, the serving cell may be configured from one primary cell (PCell).
  • multiple serving cells include one or more special cells (Special Cell: SpCell) and one or more all secondary cells. It may mean a set of cells (set of cells) consisting of cells (Secondary Cell: SCell).
  • the SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and the SpCell may be activated at all times.
  • CBRA contention-based Random Access
  • the PCell may be a cell used in an RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. Further, the PCell may be a cell used in an RRC connection re-establishment procedure in which a terminal device re-establishes an RRC connection. Further, the PCell may be a cell used in a random access procedure during handover. The PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. Further, SpCell may be a cell used for purposes other than those described above.
  • the serving cell group configured for the terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device.
  • CA carrier aggregation
  • a cell that provides additional radio resources to SpCell for a terminal device in which CA is configured may mean SCell.
  • TAG timing advance group
  • the TAG including SpCell of the MAC entity may mean a primary timing advance group (PTAG).
  • TAGs other than the above-mentioned PTAG may mean secondary timing advance group (STAG). Note that one or more TAGs may be configured for each cell group, which will be described later.
  • a cell group that is set from a base station device to a terminal device will be explained.
  • a cell group may be composed of one SpCell.
  • a cell group may be composed of one SpCell and one or more SCells. That is, a cell group may be composed of one SpCell and optionally one or more SCells. Further, a cell group may be expressed as a set of cells.
  • Dual Connectivity means that a first base station device (first node) and a second base station device (second node) perform data communication by using the radio resources of the cell groups they respectively configure. It can be technology.
  • a cell group may be added to the terminal device from the base station device.
  • the first base station device may add a second base station device.
  • the first base station device may be called a master node (Master Node: MN).
  • MN master node
  • MCG master cell group
  • the second base station device may be referred to as a secondary node (SN).
  • a cell group configured by a secondary node may be referred to as a secondary cell group (SCG).
  • the master node and the secondary node may be configured within the same base station device.
  • a cell group configured in a terminal device may be referred to as an MCG.
  • the SpCell set in the terminal device may be a PCell.
  • an NR without a DC configured may be called an NR standalone.
  • Multi-Radio Dual Connectivity may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Further, MR-DC may be a technique for performing DC using NR for MCG and E-UTRA for SCG. Further, MR-DC may be a technology that performs DC using NR on both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC that uses E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC for the core network, and NGEN-DC that uses 5GC for the core network. There may be DC (NG-RAN E-UTRA-NR Dual Connectivity).
  • NR-DC that uses NR for MCG and E-UTRA for SCG
  • NE-DC NR-E-UTRA Dual Connectivity
  • NR-DC NR-NR Dual Connectivity
  • one MAC entity may exist for each cell group.
  • a DC or MR-DC when configured in a terminal device, there may be one MAC entity for MCG and one MAC entity for SCG.
  • a MAC entity for MCG in a terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.).
  • the MAC entity for the SCG in the terminal device may be created by the terminal device when the SCG is configured in the terminal device.
  • the MAC entity for each cell group of the terminal device may be configured by the terminal device receiving RRC signaling from the base station device.
  • SpCell When a MAC entity is associated with an MCG, SpCell may refer to PCell.
  • SpCell may mean a primary SCG cell (Primary SCG Cell: PSCell). Also, if the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells.
  • the MAC entity for MCG may be an E-UTRA MAC entity
  • the MAC entity for SCG may be an NR MAC entity.
  • the MAC entity for MCG may be an NR MAC entity
  • the MAC entity for SCG may be an E-UTRA MAC entity.
  • both the MAC entities for MCG and SCG may be NR MAC entities. Note that the existence of one MAC entity for each cell group can be translated into the existence of one MAC entity for each SpCell. Furthermore, one MAC entity for each cell group may be translated as one MAC entity for each SpCell.
  • a wireless connection may be established by establishing a radio bearer (RB) between the terminal device and the base station device.
  • the radio bearer used for CP may be called a signaling radio bearer (SRB).
  • the radio bearer used for UP may be called a data radio bearer (DRB).
  • Each radio bearer may be assigned a radio bearer identity (ID).
  • the radio bearer identifier for SRB may be called an SRB identity (SRB ID).
  • the radio bearer identifier for DRB may be called a DRB identity (DRB ID).
  • SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined.
  • SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined.
  • SRB0 may be an SRB for an RRC message that is transmitted and/or received using the CCCH of the logical channel.
  • SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2.
  • RRC signaling transmitted and/or received using SRB1 may include piggybacked NAS signaling.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB1.
  • SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB2.
  • SRB2 may have a lower priority than SRB1.
  • SRB3 may be an SRB for transmitting and/or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device.
  • the logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB3. Also, other SRBs may be prepared for other uses.
  • DRB may be a radio bearer for user data.
  • the logical channel DTCH may be used for RRC signaling that is transmitted and/or received using the DRB.
  • Radio bearers may include RLC bearers.
  • An RLC bearer may consist of one or two RLC entities and a logical channel. When there are two RLC entities in an RLC bearer, the RLC entities may be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in an RLC entity in unidirectional UM mode.
  • 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 the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.).
  • One SRB1 may be established and/or configured in the terminal device by RRC signaling received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state.
  • SRB1 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB1 RLC bearer may consist of an AM RLC entity and a logical channel.
  • One SRB2 may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling received from the base station device.
  • SRB2 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB2 RLC bearer may consist of an AM RLC entity and a logical channel.
  • the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node.
  • SRB3 when a secondary node in EN-DC, NGEN-DC, or NR-DC is added or changed, a terminal device in an RRC connection state with AS security activated connects to the base station. One may be established and/or configured in the terminal device by RRC signaling received from the device.
  • SRB3 may be a direct SRB between the terminal device and the secondary node.
  • SRB3 may consist of one PDCP entity and one or more RLC bearers.
  • the SRB3 RLC bearer may consist of an AM RLC entity and a logical channel.
  • PDCP on the base station device side of SRB3 may be placed in a secondary node.
  • One or more DRBs may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling that the terminal device receives from the base station device.
  • a DRB may consist of one PDCP entity and one or more RLC bearers.
  • a DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.
  • the radio bearer in which PDCP is placed in the master node may be referred to as an MN terminated bearer.
  • a radio bearer in which PDCP is placed in a secondary node may be referred to as an SN terminated bearer.
  • a radio bearer in which the RLC bearer exists only in the MCG may be referred to as an MCG bearer.
  • a radio bearer in which the RLC bearer exists only in the SCG may be referred to as an SCG bearer.
  • a radio bearer in which the RLC bearer exists in both the MCG and the SCG may be referred to as a split bearer.
  • the bearer types of SRB1 and SRB2 established/and/or configured in the terminal device may be MN-terminated MCG bearer and/or MN-terminated split bearer.
  • the bearer type of SRB3 established/and/or configured in the terminal device may be an SN termination SCG bearer.
  • the bearer type of the DRB established/and/or configured in the terminal device may be any one of all bearer types.
  • the RLC entity to be established and/or configured may be E-UTRA RLC.
  • the RLC entity to be established and/or configured may be NR RLC.
  • EN-DC is configured in the terminal device
  • the PDCP entity established and/or configured for the MN terminating MCG bearer may be either E-UTRA PDCP or NR PDCP.
  • the PDCP established and/or configured may be NR PDCP.
  • the PDCP entity established and/or configured for the radio bearer in all bearer types may be NR PDCP.
  • a DRB established and/or configured in a terminal device may be linked to one PDU session.
  • One SDAP entity may be established and/or configured for one PDU session at the terminal device.
  • Establishment and/or configuration of the SDAP entity, PDCP entity, RLC entity, and logical channel in the terminal device may be established and/or configured by RRC signaling that the terminal device receives from the base station device.
  • a network configuration in which the master node is eNB 102 and EPC 104 is the core network may be referred to as E-UTRA/EPC.
  • a network configuration in which the master node is the eNB 102 and the 5GC 110 is the core network may be called E-UTRA/5GC.
  • a network configuration in which the master node is gNB 108 and 5GC 110 is the core network may be called NR or NR/5GC.
  • the above-mentioned master node may refer to a base station device that communicates with the terminal device.
  • Handover may be a process in which the UE 122 in the RRC connected state changes the serving cell from the source SpCell to the target SpCell.
  • Handover may be part of mobility control performed by RRC.
  • Handover may be performed when UE 122 receives RRC signaling from eNB 102 and/or gNB 108 instructing handover.
  • RRC signaling that instructs handover may be a message regarding reconfiguration of an RRC connection that includes a parameter that instructs handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync).
  • a parameter that instructs handover for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync.
  • MobilityControlInfo may be referred to as a mobility control setting information element, mobility control setting, or mobility control information.
  • RRC signaling instructing handover may be a message (eg, MobilityFromEUTRACommand or MobilityFromNRCommand) indicating movement to a cell of another RAT.
  • Handover can also be referred to as reconfiguration with sync.
  • Reconfiguration with synchronization may be triggered by RRC, or by layer 1 or layer 2, which will be described later.
  • the conditions under which the UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and when at least one DRB is established. good.
  • FIG. 4 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment.
  • FIG. 4 is an example of a flow when RRC signaling is sent from the base station device (eNB 102 and/or gNB 108) to the terminal device (UE 122).
  • the base station device creates an RRC message (step S400).
  • the RRC message may be created in the base station device so that the base station device can distribute system information (SI) and paging messages. Further, the creation of the RRC message in the base station device may be performed so that the base station device can transmit RRC signaling to cause a specific terminal device to perform processing.
  • the processing to be performed on a specific terminal device may include, for example, processing related to security, reconfiguration of an RRC connection, handover to a different RAT, suspension of an RRC connection, release of an RRC connection, and the like.
  • Resetting an RRC connection involves processing such as radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. May be included.
  • the creation of an RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device.
  • the response to RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC restart request, and the like.
  • the RRC message includes information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements, and may be described using a description method called ASN.1 (Abstract Syntax Notation One).
  • the base station device then transmits the created RRC signaling to the terminal device (step S402).
  • the terminal device performs processing such as setting, if necessary, according to the above-mentioned received RRC signaling (step S404).
  • the terminal device that has performed the processing may transmit RRC signaling for response to the base station device (not shown).
  • RRC signaling is not limited to the above example and may be used for other purposes.
  • RRC on the master node side is used to transfer RRC signaling for settings on the SCG side (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal device. good.
  • NR RRC signaling may be included in the form of a container in E-UTRA RRC signaling transmitted and received between eNB 102 and UE 122.
  • E-UTRA RRC signaling may be included in the form of a container in the NR RRC signaling transmitted and received between the gNB 108 and the UE 122.
  • RRC signaling for SCG side configuration may be transmitted and received between the master node and the secondary nodes.
  • NR RRC signaling may be included in E-UTRA RRC signaling transmitted from eNB 102 to UE 122, and NR RRC signaling transmitted from gNB 108 to UE 122.
  • the signaling may include RRC signaling for E-UTRA.
  • FIG. 7 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in NR in FIG. 4.
  • FIG. 8 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in E-UTRA in FIG. 4.
  • ⁇ omitted> and ⁇ omitted> are not part of the notation of ASN.1, and indicate that other information is omitted. shows.
  • the example of ASN.1 does not correctly follow the ASN.1 notation method.
  • the example ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names and other representations may be used.
  • the parameters described in ASN.1 are sometimes referred to as information elements, without distinguishing them into fields, information elements, etc.
  • fields, information elements, etc. described in ASN.1 and included in RRC signaling may be translated into information or parameters.
  • the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.
  • the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc. a cell group of MCG or SCG in NR.
  • the information element named CellGroupConfig may be referred to as a cell group configuration information element or cell group configuration.
  • An information element named SpCellConfig included in an information element named CellGroupConfig may be an information element used for configuring a special cell (SpCell).
  • the information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration.
  • An information element named SCellConfig included in an information element named CellGroupConfig may be an information element used to configure a secondary cell (SCell).
  • the information element named SCellConfig may be rephrased as SCell configuration information element or SCell configuration.
  • the information element named ReconfigurationWithSync included in the information element named SpCellConfig may be the above-mentioned reconfiguration with synchronization information element or reconfiguration with synchronization.
  • the information element named ReconfigurationWithSync may include a new UE identifier named newUE-Identity.
  • the information element named spCellConfigCommon included in the information element named ReconfigurationWithSync may be an information element indicating common settings configured in SpCell.
  • the information element named spCellConfigCommon can be rephrased as SpCell common settings.
  • An information element named sCellConfigCommon included in an information element named SCellConfig may be an information element indicating common settings configured in SCell.
  • the information element named sCellConfigCommon can be rephrased as SCell common settings.
  • FIG. 9 is an example of an information element named ServingCellConfigCommon included in the SpCell configuration or SCell configuration in FIG. 7, that is, an example of an ASN.1 description representing a field and/or information element related to the serving cell common configuration.
  • the information element named DownlinkConfigCommon included in the information element named ServingCellConfigCommon may be an information element indicating common settings configured in the downlink.
  • the information element named DownlinkConfigCommon may be rephrased as downlink common settings.
  • the information element named BWP-DownlinkCommon included in the information element named DownlinkConfigCommon may be an information element indicating common settings configured in the downlink BWP.
  • the information element named BWP-DownlinkCommon may be rephrased as downlink BWP common settings.
  • the information element named PDCCH-ConfigCommon included in the information element named BWP-DownlinkCommon may be an information element indicating common settings configured on the PDCCH.
  • the information element named PDCCH-ConfigCommon may be rephrased as PDCCH common settings.
  • the information element named PDCCH-ConfigCommon may include an information element named commonSearchSpaceList, an information element named searchSpaceSIB1, an information element named searchSpaceOtherSystemInformation, and/or an information element named pagingSearchSpace.
  • the information element named commonSearchSpaceList may refer to a list of common search spaces (CSS).
  • searchSpaceSIB1 may be information on a search space for receiving system information (SIB1).
  • searchSpaceOtherSystemInformation may include information on a search space for receiving system information (SIB2 and later).
  • pagingSearchSpace may be information on a search space for receiving paging messages.
  • the RRC reconfiguration procedure may be a procedure for reconfiguring parameters, information elements, etc. set in RRC. Further, the purpose of the RRC reconfiguration procedure may be some or all of the following (A) to (F).
  • A) Modifying an RRC connection B) Performing a reconfiguration with synchronization
  • E Adding, modifying, and/or releasing conditional handover (CHO) settings
  • F Conditional PSCell changes Adding, modifying, and/or releasing settings for (conditional PSCell change: CPC) or conditional PSCell addition (CPA)
  • the base station device may initiate an RRC reconfiguration procedure for the terminal device in the RRC_CONNECTED state.
  • the base station apparatus may apply some or all of the following (A) to (F) to the RRC reconfiguration procedure.
  • the base station device starts an RRC reconfiguration procedure for the terminal device may be paraphrased as "the base station device transmits a message regarding reconfiguring the RRC connection to the terminal device", etc. .
  • A Establishment of radio bearers other than SRB1
  • B Addition of SCG and one or more SCells
  • C Reconfiguration with synchronization included in SCG cell group configuration
  • D Synchronization included in MCG cell group configuration
  • Conditional reconfiguration E
  • Conditional reconfiguration for conditional PSCell change F
  • a synchronized reconfiguration with security key update included in a message regarding RRC connection reconfiguration may include some or all of (A) to (E) below, which is triggered by an explicit layer 2 indicator. may be included.
  • (A) Random access to PCell and/or PSCell (B) MAC reset (C) Security update (D) Re-establishment of RLC (E) Re-establishment of PDCP
  • a synchronized reconfiguration without security key update included in a message regarding RRC connection reconfiguration is triggered by an explicit layer 2 indicator, and some or all of (A) to (D) below are triggered by an explicit layer 2 indicator.
  • (A) Random access to PCell and/or PSCell (B) MAC reset (C) RLC re-establishment (D) PDCP data recovery
  • the layer 2 indicators described above may include, for example, layer 2 signaling such as MAC, RLC, and PDCP.
  • the terminal device When the terminal device receives a message regarding RRC connection reconfiguration or executes conditional reconfiguration (CHO, CPA, or CPC), the terminal device performs some or all of the following (A) to (E). You may (perform). (Processing RRP) (A) If the message regarding RRC connection reconfiguration is applied by performing a conditional reconfiguration when performing cell selection while timer T311 is running, which starts at the beginning of the RRC reestablishment procedure, then Remove all entries from the entry list. (B) If the message regarding RRC connection reconfiguration includes MCG cell group configuration, perform cell group configuration for the received MCG cell group configuration, and the cell group configuration is reconfigured with synchronization. If SpCell settings with information elements are included, perform reconfiguration with synchronization.
  • RRC connection reconfiguration includes cell group configuration for the SCG, perform cell group configuration for the SCG, and said cell group configuration includes SpCell configuration with synchronized reconfiguration information element; If included, perform reconfiguration with synchronization.
  • D If the message regarding RRC connection reconfiguration includes conditional reconfiguration, perform conditional reconfiguration.
  • E Submit an RRC reconfiguration completion message to the lower layer (PHY, MAC, etc.) for transmission using the new configuration.
  • the terminal device may perform some or all of (A) to (E) below in order to execute reconfiguration with synchronization.
  • "Performing reconfiguration with synchronization” may be rephrased as “performing reconfiguration with synchronization” or "triggering reconfiguration with synchronization”.
  • (Processing RWS) (A) If timer T310 for the corresponding SpCell is running, stop it. (B) If timer T312 for the corresponding SpCell is running, stop it. (C) Reset the MAC entity of the corresponding cell group. (D) Apply the value of the new UE identifier (newUE-Identity) included in the reconfiguration information element with synchronization as the C-RNTI for the corresponding cell group.
  • Conditional reconfiguration may refer to conditional handover, conditional PSCell addition, and/or conditional PSCell change.
  • the network sets one or more target candidate cells for conditional reconfiguration for the terminal device.
  • the terminal device evaluates the state of the configured candidate cell.
  • the terminal device performs the evaluation and applies conditional reconfiguration information elements associated with candidate cells that satisfy the execution conditions.
  • the terminal device may maintain a list of entries (VarConditionalReconfig), which will be described later, for conditional reconfiguration.
  • the terminal device Based on receiving the information regarding conditional reconfiguration, the terminal device deletes a target candidate cell for conditional reconfiguration if the information regarding conditional reconfiguration includes an entry deletion list (condReconfigToRemoveList). If the information regarding the conditional reconfiguration includes an addition/modification list of entries (condReconfigToAddModList), the conditional reconfiguration target candidate cell may be added or modified.
  • the operation of deleting the conditional reconfiguration target candidate cell means that if the entry identifier (condReconfigId) included in the entry deletion list is included in the list of entries held by the terminal device, the terminal device
  • the method may be to delete an entry corresponding to the identifier of the entry from a list of entries held by the terminal device.
  • the list of entries held by the terminal device is also simply referred to as an entry list. That is, the "entry list” in the following description refers to a list of entries held by the terminal device, unless otherwise specified.
  • the entry list may also be a variable named VarConditionalReconfig.
  • the entry identifier is also simply referred to as an entry identifier.
  • the operation of adding or modifying a target candidate cell for conditional reconfiguration means that when each entry identifier included in the entry addition/modification list exists in an entry in the entry list, the terminal device performs the following process (A). ) and/or (B).
  • the terminal device may add a new entry corresponding to the entry identifier not included in the entry list to the entry list.
  • the entry deletion list may be a list related to the settings of one or more candidate SpCells to be deleted.
  • the addition/modification list of entries may be a list regarding the settings of one or more candidate SpCells to be added and modified for CHO, CPC, and CPA.
  • Each entry included in the addition/modification list of entries includes an entry identifier and may additionally include execution conditions and/or conditional reconfiguration information elements.
  • Each entry may be associated with one candidate SpCell of one or more candidate SpCells.
  • the entry identifier is an identifier used to identify each entry of CHO, CPA, and CPC.
  • the entry list may include one or more entries. Each entry may include one entry identifier, one or more execution conditions, and one conditional reconfiguration information element.
  • the terminal device may hold an empty list.
  • the execution condition may be a condition that needs to be met to trigger execution of the conditional reconfiguration.
  • the conditional reconfiguration information element may be a message related to RRC connection reconfiguration that is applied when the execution condition is satisfied.
  • the message regarding resetting the RRC connection may be a message used to connect to a candidate SpCell.
  • the terminal device may evaluate the execution conditions of the entries included in the entry list held by the terminal device. If the entry list held by the terminal device is empty or if the terminal device does not hold an entry list, it is not necessary to evaluate the execution condition.
  • Executing conditional reconfiguration means that when one or more execution conditions are met, the conditional reconfiguration information element included in the same entry as the one or more execution conditions is applied, and conditional reconfiguration is performed. It may be to perform an RRC reconfiguration procedure based on the configuration information element.
  • the terminal device selects one cell from among the multiple candidate cells that meet the execution conditions, and executes the conditional replay associated with the selected candidate cell.
  • Configuration information elements may be applied.
  • the MAC entity of the terminal device may implement some or all of (A) to (O) below.
  • the resetting of the MAC entity may be referred to as a MAC reset.
  • (Processing MR) (A) Initialize the parameter Bj set for each logical channel to 0. (B) If all timers are running, stop them. (C) Set the New Data Indicator (NDI) value of all uplink HARQ processes to 0. (D) Stop any ongoing random access procedures, if any. (E) Discard explicitly signaled 4-step and 2-step RA type contention-free random access (CFRA) resources, if any.
  • CFRA contention-free random access
  • the multiple Transmit/Receive Point (also referred to as multi-TRP or mTRP) operation is explained.
  • a serving cell receives terminal equipment from multiple TRPs (Transmit/Receive Points) to provide better coverage, reliability, and/or data rate for PDSCH, PDCCH, PUSCH, and PUCCH. Good to be able to schedule.
  • TRPs Transmit/Receive Points
  • 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 with settings configured by the RRC layer.
  • single-DCI mode a terminal device may be scheduled for both TRPs by the same DCI.
  • multi-DCI mode a terminal device may be scheduled for each TRP by an independent DCI.
  • Each TRP of mTRPs may be specified 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 TRP information.
  • the TRP information may be information for identifying one or more TRPs.
  • TRP information may be used to select one TRP.
  • the TRP information may be a CORESET pool index.
  • One CORESET pool index and one CORESET resource set identifier may be associated with one CORESET.
  • the terminal device may transmit the PUSCH with the corresponding TRP based on the CORESET resource set identifier.
  • TRP information may be associated with an index of a 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.
  • TRP information may be associated with a TCI state pool (or a TCI state pool index).
  • 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 modes of operation may be PDCCH repetition and single frequency network (SFN) based PDCCH transmission.
  • the terminal device may receive each of the PDCCH transmissions carrying the same DCI from each TRP.
  • PDCCH repetition mode the terminal device may receive two PDCCH transmissions carrying the same DCI from two linked search spaces, each associated with a different CORESET.
  • SFN-based PDCCH transmission mode a terminal device can receive two PDCCH transmissions carrying the same DCI from a single search space/CORESET with different TCI states.
  • the terminal equipment is associated with different spatial relations corresponding to the two TRPs by the indication by the configured uplink grant provided by the single DCI or RRC signaling.
  • PUSCH transmission of the same content may be performed in the same beam direction.
  • one or more TCI states in multi-DCI PDSCH transmission may be associated with a different PCI SSB than the serving cell's Physical Cell Identity (PCI). Further, at most one TCI state associated with a PCI different from the serving cell may be activated at a time.
  • PCI Physical Cell Identity
  • Layer 1/layer 2 mobility may mean that layer 1 or layer 2 has a mobility control function.
  • Layer 1/Layer 2 mobility refers to the process of changing a serving cell from a source cell to a target cell by Layer 1 or Layer 2, in addition to or in place of Layer 1 or Layer 2 signaling. Mobility control with modification processing may be triggered.
  • Layer 1/layer 2 mobility may be rephrased as layer 1/layer 2 centric mobility (L1/L2 centric mobility).
  • layer 1 may be a PHY layer
  • layer 2 may be one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer.
  • the information necessary for the serving cell change process may be notified in advance by RRC signaling, and the information may include system information (searchSpaceSIB1, searchSpaceOtherSystemInformation, etc.), paging messages (such as pagingSearchSpace), a part or all of a common search space (such as commonSearchSpaceList).
  • system information searchSpaceSIB1, searchSpaceOtherSystemInformation, etc.
  • paging messages such as pagingSearchSpace
  • a part or all of a common search space such as commonSearchSpaceList.
  • the information may be different between the PCI of the serving cell and a PCI different from the serving cell, and in the serving cell change process, when a serving cell with a PCI different from the serving cell becomes a target cell, the terminal equipment may switch settings such as a search space for receiving system information and paging messages from the information of the serving cell to the information of the serving cell having a PCI different from that of the serving cell.
  • the information is set for a PCI different from the serving cell, and in the serving cell change process, if the serving cell with the PCI different from the serving cell becomes the target cell, the terminal device: Based on the fact that the serving cell change process is triggered by layer 1 or layer 2 signaling, system information and paging messages are received using the search space included in the information configured for a PCI different from the serving cell. good. Furthermore, security key updating does not need to be performed in mobility control triggered by layer 1 or layer 2 signaling.
  • the source cell and the target cell may be SpCell or SCell.
  • FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) in this embodiment. Note that in order to avoid complicating the explanation, FIG. 5 shows only the main components closely related to this embodiment.
  • the UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, RRC signaling, etc.) from a base station device, a processing unit 502 that performs processing according to parameters included in the received control information, and a base station device. It consists of a transmitter 504 that transmits control information (UCI, RRC signaling, etc.).
  • the above-mentioned base station device may be eNB102 or gNB108.
  • the processing unit 502 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. It's fine.
  • FIG. 6 is a block diagram showing the configuration of the base station device in this embodiment. Note that in order to avoid complicating the explanation, FIG. 6 shows only the main components closely related to this embodiment.
  • the above-mentioned base station device may be eNB102 or gNB108.
  • the base station device shown in FIG. a processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a reception unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122.
  • the processing unit 602 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing section 602 includes some or all of the physical layer processing section, MAC layer processing section, RLC layer processing section, PDCP layer processing section, SDAP processing section, RRC layer processing section, and NAS layer processing section. It's fine.
  • FIG. 10 is a diagram showing an example of the processing of the terminal device in this embodiment.
  • the processing unit 502 of the UE 122 determines the conditions (step S1000), and operates based on the determination (step S1002).
  • step S1000 the processing unit 502 of the UE 122 may determine whether one or both of the following conditions (a) and (b) are satisfied. (a) Reception of RRC signaling from transmitter 600 of gNB 108. (b) Execution of conditional reset.
  • the processing unit 502 of the UE 122 may execute the RRC reconfiguration procedure in step S1002. . That is, the processing unit 502 of the UE 122 may perform part or all of the processing shown in the above processing (RRP) in step S1002. Furthermore, if the processing unit 502 of the UE 122 determines in step S1000 that neither of the conditions (a) and (b) is satisfied, it does not need to execute the RRC reconfiguration procedure in step S1002.
  • step S1002 the processing unit 502 of the UE 122 determines in step S1000 that neither of the conditions (a) and (b) is satisfied, in step S1002, the processing unit 502
  • the RRC reconfiguration procedure may be performed based on the following factors: "Do not perform the RRC reconfiguration procedure” may be rephrased as "do not perform part or all of the process shown in the above process (RRP)."
  • the RRC signaling described in condition (a) above may be, for example, a message regarding reconfiguration of an RRC connection.
  • the processing unit 502 of the UE 122 which has received the RRC signaling from the transmission unit 600 of the gNB 108, determines the conditions (step S1000) and operates based on the determination (step S1002).
  • step S1000 the processing unit 502 of the UE 122 may determine whether one or both of the following conditions (a) and (b) are satisfied.
  • the RRC signaling received from the transmitter 600 of the gNB 108 includes a reconfiguration information element with synchronization.
  • the RRC signaling received from the transmitter 600 of the gNB 108 includes SpCell settings, and the SpCell settings include a reconfiguration information element with synchronization.
  • the processing unit 502 of the UE 122 may execute reconfiguration with synchronization in step S1002. . That is, the processing unit 502 of the UE 122 may perform part or all of the processing shown in the above processing (RWS) in step S1002. Furthermore, if the processing unit 502 of the UE 122 determines in step S1000 that neither of the conditions (a) and (b) is satisfied, it does not need to perform reconfiguration with synchronization in step S1002. In other words, the processing unit 502 of the UE 122 does not need to perform part or all of the processing shown in the above processing (RWS) in step S1002.
  • the processing unit 502 of the UE 122 may determine that neither of the conditions (a) and (b) is satisfied.
  • the RRC signaling described in conditions (a) and (b) above may be, for example, a message regarding reconfiguration of an RRC connection.
  • the processing unit 502 of the UE 122 that executes reconfiguration with synchronization determines the conditions (step S1000), and operates based on the determination (step S1002).
  • the processing unit 502 of the UE 122 that executes reconfiguration with synchronization may determine in step S1000 whether any or any combination of the following (a) to (d) is satisfied.
  • (a) Reconfiguration with synchronization was triggered in RRC.
  • (b) Reconfiguration with synchronization was triggered in layer 1.
  • (c) Reconfiguration with synchronization was triggered in layer 2.
  • (d) The PCI of the target cell matches a different PCI than the serving cell, which is associated with an activated TCI state.
  • the processing unit 502 of the UE 122 may trigger a MAC reset in step S1002. That is, the processing unit 502 of the UE 122 may perform part or all of the processing shown in the above processing (MR) in step S1002. Further, if the processing unit 502 of the UE 122 determines in step S1000 that any one or any combination of conditions (b), (c), and (d) is satisfied, in step S1002, No need to trigger MAC reset. In other words, the processing unit 502 of the UE 122 does not need to perform part or all of the processing shown in the above processing (MR) in step S1002. Further, if the processing unit 502 of the UE 122 determines that none of the conditions (a) to (d) are satisfied when executing reconfiguration with synchronization in step S1000, , may or may not trigger a MAC reset.
  • the RRC 308 of the processing unit 502 of the UE 122 that executes the RRC reconfiguration procedure determines the conditions (step S1000), and operates based on the determination (step S1002).
  • step S1000 the RRC 308 of the processing unit 502 of the UE 122 that executes the RRC reconfiguration procedure determines whether any or any combination of the following (a) to (d) is satisfied. good.
  • (a) Triggered the RRC reconfiguration procedure in RRC.
  • (b) Triggered the RRC reconfiguration procedure at layer 1 (PHY).
  • (c) Triggered the RRC reconfiguration procedure at layer 2 (MAC).
  • the RRC 308 of the processing unit 502 of the UE 122 may submit signaling indicating completion of the RRC reconfiguration procedure in step S1002.
  • the signaling indicating the completion of the RRC reconfiguration procedure may be, for example, an RRC reconfiguration complete message.
  • the processing unit 508 of the UE 122 PHY300 may be notified of the completion of the RRC reconfiguration procedure.
  • step S1002 may instruct the PHY 300 of the processing unit 502 of the UE 122 to submit signaling indicating completion of the RRC reconfiguration procedure.
  • the PHY 300 of the processing unit 502 of the UE 122 is notified of the completion of the RRC reconfiguration procedure by the RRC 308 of the processing unit 502 of the UE 122, and/or submits signaling indicating the completion of the RRC reconfiguration procedure.
  • the signaling may be transmitted on PUCCH or may be other signaling.
  • the processing unit 508 of the processing unit 502 of the UE 122 may notify the MAC 302 of the completion of the RRC reconfiguration procedure.
  • the RRC 308 of the processing unit 502 of the UE 122 may instruct the MAC 302 of the processing unit 502 of the UE 122 to submit signaling indicating completion of the RRC reconfiguration procedure.
  • the MAC 302 of the processing unit 502 of the UE 122 is notified of the completion of the RRC reconfiguration procedure by the RRC 308 of the processing unit 502 of the UE 122, and/or submits signaling indicating the completion of the RRC reconfiguration procedure.
  • the signaling may be transmitted by MAC CE or may be other signaling.
  • the RRC 308 of the processing unit 502 of the UE 122 determines that none of the conditions (a) to (d) are satisfied in step S1000 when executing the RRC reconfiguration procedure
  • the RRC 308 of the processing unit 502 of the UE 122 performs In S1002, signaling indicating completion of the RRC reconfiguration procedure may be submitted, and lower layers (PHY, MAC, etc.) may be notified of the completion of the RRC reconfiguration procedure; It may be instructed to submit signaling indicating completion of the configuration procedure.
  • lower layers PHY, MAC, etc.
  • RRC signaling may be received to perform synchronized reconfiguration, and to add, modify, and/or release the configuration of conditional handover or conditional PSCell change. may be notified. If RRC signaling is notified in advance to add, modify and/or release the configuration of conditional handover or conditional PSCell change, said RRC signaling may include system information (searchSpaceSIB1, searchSpaceOtherSystemInformation, etc.), paging messages ( pagingSearchSpace, etc.) and/or common search spaces (such as commonSearchSpaceList). Additionally, in each embodiment, RRC signaling may be received or notified for other purposes.
  • Non-Patent Document 7 a UE that receives RRC signaling including a reconfiguration with synchronization information element triggers reconfiguration with synchronization. Furthermore, regardless of whether the reconfiguration with synchronization is triggered by RRC, layer 1 or layer 2, the MAC entity is reset based on Non-Patent Document 8. At this time, the settings in the MAC necessary for Layer 1/Layer 2 mobility are deleted, and when a serving cell change is triggered, the UE may need to acquire the settings in the MAC again. According to each of the embodiments described above, the settings in the MAC are not erased by reconfiguration with synchronization, and the UE can use the settings as they are when triggering a serving cell change.
  • the radio bearer in the above description may be a DRB, an SRB, or a DRB and an SRB, unless otherwise specified.
  • condition "A” and the condition “B” are contradictory conditions, the condition “B” may be expressed as an “other” condition of the condition "A”. good.
  • the program that runs on the device related to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of this embodiment.
  • Programs or information handled by programs are temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and are stored as needed.
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • the program for realizing this control function may be realized by recording it on a computer-readable recording medium and causing the computer system to read and execute the program recorded on this recording medium.
  • the "computer system” herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” may be any of semiconductor recording media, optical recording media, magnetic recording media, and the like.
  • a "computer-readable recording medium” refers to a medium 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. In that case, it may also include something that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. .
  • each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, typically an integrated circuit or multiple integrated circuits.
  • An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof.
  • a general purpose processor may be a microprocessor, or in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine.
  • the general-purpose processor or each of the circuits described above may be configured with a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.
  • this embodiment is not limited to the above-described embodiment.
  • the present embodiment is not limited to this, and can be applied to stationary or non-movable electronic equipment installed indoors or outdoors, such as AV equipment, kitchen equipment, etc. It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
  • One embodiment of the present invention is used in, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), a program, or the like. be able to.
  • a communication device e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device
  • an integrated circuit e.g., a communication chip
  • a program e.g., a program, or the like.
  • E-UTRA 102eNB 104EPC 106NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 interface 122 U.E. 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiving section 502, 602 processing section 504, 600 transmitter

Landscapes

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

Abstract

L'invention concerne un dispositif terminal qui communique avec un dispositif de station de base, le dispositif terminal comprenant : une unité de réception qui reçoit une signalisation de commande de ressources radio (RRC) en provenance du dispositif de station de base ; une unité de traitement RRC qui déclenche et exécute une procédure de reconfiguration RRC ; et une unité de traitement MAC qui déclenche la procédure de reconfiguration RRC. L'unité de traitement RRC : exécute la procédure de reconfiguration RRC sur la base de la réception de la signalisation RRC ou de l'exécution d'une reconfiguration conditionnelle ; si la procédure de reconfiguration RRC est déclenchée par l'unité de traitement RRC, soumet une signalisation indiquant l'achèvement de la procédure de reconfiguration RRC ; et si la procédure de reconfiguration RRC est déclenchée par l'unité de traitement MAC, exécute la procédure de reconfiguration RRC et notifie ensuite l'unité de traitement MAC de l'achèvement de la procédure de reconfiguration RRC. Sur la base de la notification, à partir de l'unité de traitement RRC, de l'achèvement de la procédure de reconfiguration RRC, l'unité de traitement MAC transmet un CE MAC indiquant l'achèvement de la procédure de reconfiguration RRC.
PCT/JP2023/027917 2022-08-04 2023-07-31 Dispositif terminal, procédé et circuit intégré WO2024029478A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022-124608 2022-08-04
JP2022124608 2022-08-04

Publications (1)

Publication Number Publication Date
WO2024029478A1 true WO2024029478A1 (fr) 2024-02-08

Family

ID=89849040

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/027917 WO2024029478A1 (fr) 2022-08-04 2023-07-31 Dispositif terminal, procédé et circuit intégré

Country Status (1)

Country Link
WO (1) WO2024029478A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022086933A1 (fr) * 2020-10-22 2022-04-28 Google Llc Gestion d'informations d'ue après la préparation d'une procédure de mobilité conditionnelle
WO2022154706A1 (fr) * 2021-01-13 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Activation d'un groupe désactivé de cellules dans un réseau de communication sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022086933A1 (fr) * 2020-10-22 2022-04-28 Google Llc Gestion d'informations d'ue après la préparation d'une procédure de mobilité conditionnelle
WO2022154706A1 (fr) * 2021-01-13 2022-07-21 Telefonaktiebolaget Lm Ericsson (Publ) Activation d'un groupe désactivé de cellules dans un réseau de communication sans fil

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Conditional NR PSCell addition/change procedures", 3GPP DRAFT; R2-1912297, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, CN; 20191014 - 20191018, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051790344 *
SAMSUNG: "ReconfigurationWithSync and Random Access (offline discussion 20)", 3GPP DRAFT; R2-1815991 OFFLINE DISCUSSION 20, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chengdu, China; 20181008 - 20181012, 12 October 2018 (2018-10-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051525185 *

Similar Documents

Publication Publication Date Title
CN116158118A (zh) 终端装置、通信方法以及基站装置
JP2024024131A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2024029478A1 (fr) Dispositif terminal, procédé et circuit intégré
JP2023169449A (ja) 端末装置、基地局装置、方法、および、集積回路
WO2024057978A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024058073A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024142971A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024096097A1 (fr) Dispositif terminal, procédé, et circuit intégré
WO2024070379A1 (fr) Équipement terminal, procédé et circuit intégré
WO2024070447A1 (fr) Dispositif terminal, procédé et circuit intégré
EP4224936A1 (fr) Appareil terminal, procédé et circuit intégré permettant d'empecher l'evaluation d'une condition d'execution d'une cellule speciale candidate
US20230246906A1 (en) Terminal apparatus, base station apparatus, and method
WO2023189798A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023204307A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024005069A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2024005010A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023189963A1 (fr) Équipement terminal, procédé et circuit intégré
WO2024009884A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023243571A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023132370A1 (fr) Dispositif de terminal, procédé et circuit intégré
WO2023238820A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023136231A1 (fr) Dispositif terminal, procédé et circuit intégré
WO2023063342A1 (fr) Dispositif terminal, dispositif de station de base, et procédé
WO2023042747A1 (fr) Dispositif terminal, dispositif de station de base et procédé
WO2023013292A1 (fr) Dispositif terminal, dispositif de station de base et procédé

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

Country of ref document: EP

Kind code of ref document: A1