Terminal equipment, base station equipment, and method

Abstract

This invention provides a terminal device, base station device, and method for achieving efficient communication control with respect to conditional L1 / L2 mobility enhancement technology, which is a technology for adding further robustness to serving cell change technology (Layer 1 / Layer 2 mobility optimization (L1 / L2 mobility enhancement) technology) triggered by Layer 1 or Layer 2 signaling. [Solution] A terminal device UE communicating with a base station device receives RRC signaling from the base station device and, based on the determination that one of the conditions has been met, expires one or more timers, with the exception of one timer associated with one LTM candidate information element.

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device, and a method.

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP (registered trademark)), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems including radio access, core network, services, etc. are being carried out. In 3GPP, for example, as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th generation and 4th generation, technical studies and standardization of E-UTRA (Evolved Universal Terrestrial Radio Access) were started. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being carried out. Note that E-UTRA is also referred to as Long Term Evolution (LTE (registered trademark)), and extended technologies may also be referred to as LTE-Advanced (LTE-A), LTE-Advanced Pro (LTE-A Pro).

[0003]

[0004] [[ID=

[21] ] Also, in 3GPP, as a radio access technology (RAT) for cellular mobile communication systems for the 5th generation (5G), technical studies and standardization of NR (New Radio, or NR Radio access) were started. Even now, in 3GPP, technical studies and standardization of extended technologies of NR are being carried out.

Prior Art Documents

Non-Patent Documents

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v18.1.0,"NR;NR and NG-RAN Overall description; Stage 2" pp98-101 [Non-Patent Document 2] 3GPP TS 38.331 v18.1.0,"NR;Radio Resource Control (RRC);Protocol specifications" p35 pp159-163 pp794-800 p1502 [Non-Patent Document 3] 3GPP TS 38.321 v18.1.0, "NR;Medium Access Control (MAC) protocol specification" p135 pp284-285 [Non-Patent Document 4] 3GPP TS 38.213 v18.3.0, "NR;Physical layer procedures for control" pp12-14 [Overview of the project] [Problems that the invention aims to solve]

[0006] As an extension of NR, there is a serving cell change technology that allows terminal devices to move from the coverage area of ​​one cell to the coverage area of ​​another cell. This serving cell change is triggered by a measurement at Layer 3 (also called RRC), and serving Synchronized reconfiguration for cell changes is triggered by RRC signaling. Compared to RRC signaling, Layer 1 or Layer 2 signaling has the advantage of lower latency and less overhead. Therefore, a serving cell change technique (Layer 1 / Layer 2 mobility optimization (L1 / L2 mobility enhancement) technique) triggered by Layer 1 or Layer 2 signaling has been specified. To further enhance the robustness of this technique, conditional The study of L1 / L2 mobility enhancement technology has begun.

[0007] One aspect of the present invention has been made in view of the above circumstances, and one of its objectives is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently perform communication control. [Means for solving the problem]

[0008] To achieve the above objective, one aspect of the present invention employs the following means. That is, one aspect of the present invention is a terminal device that communicates with a base station device, comprising a receiving unit that receives RRC (Radio Resource Control) signaling from the base station device, and a processing unit, wherein the RRC signaling comprises one or more LTM (L1 / L2 Triggered Mobility) candidate information elements and This includes settings related to conditions associated with one or more LTM candidate information elements. Furthermore, based on the determination that one of the above conditions has been met, the processing unit determines one LTM The timers are stopped, except for one timer associated with a candidate information element, and the one LTM candidate information element is associated with one condition.

[0009] Another aspect of the present invention is a base station device that communicates with a terminal device, wherein RRC (Radio Resource) The system includes a transmission unit that transmits a control signal to the terminal device, and a processing unit, and the processing unit The RRC signaling includes one or more LTM (L1 / L2 Triggered Mobility) candidate information elements and conditions associated with each of the one or more LTM candidate information elements. By applying the RRC signaling to the terminal device, including the settings, the terminal Based on the device's determination that one of the above conditions is met, one LTM candidate information element Stop the one or more timers except for one associated with the one LTM candidate information element, and the one LTM candidate information element is associated with the one condition.

[0010] Furthermore, one aspect of the present invention is a method for a terminal device to communicate with a base station device, comprising the steps of receiving RRC (Radio Resource Control) signaling from the base station device, and the RRC signaling comprising one or more LTM (L1 / L2 Triggered Mobility) candidate information elements, and the one or include settings related to conditions associated with each of multiple LTM candidate information elements, Based on the determination that one of the conditions is met, an LTM candidate information element is associated with it. The method comprises the step of stopping one or more timers except for one timer that has been turned off, wherein one LTM candidate information element is associated with one of the conditions.

[0011] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media. [Effects of the Invention]

[0012] According to one aspect of the present invention, terminal equipment, base station equipment, and methods can achieve efficient communication control processing. [Brief explanation of the drawing]

[0013] [Figure 1] A schematic diagram of the communication system according to this embodiment. [Figure 2] A diagram showing an example of the E-UTRA protocol configuration according to this embodiment. [Figure 3] A diagram illustrating an example of the NR protocol configuration according to this embodiment. [Figure 4]A diagram showing an example of the flow of procedures for various settings in RRC according to this embodiment. [Figure 5] A block diagram showing the configuration of the terminal device in this embodiment. [Figure 6] A block diagram showing the configuration of the base station device in this embodiment. [Figure 7] An example of the ASN.1 description included in the message regarding the reconfiguration of the RRC connection in NR in this embodiment. [Figure 8] An example of the ASN.1 description representing the fields and / or information elements regarding the ServingCellConfigCommon information element in this embodiment. [Figure 9] An example of the processing of the terminal device in this embodiment.

Mode for Carrying Out the Invention

[0014] Hereinafter, this embodiment will be described in detail with reference to the drawings.

[0015] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RAT). Also, NR may be defined as a technology included in LTE. Moreover, LTE may be defined as a technology included in NR. Also, LTE that can be connected with NR and Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Also, LTE using 5GC in the core network (core network, Core Network: CN) may be distinguished from conventional LTE using EPC in the core network. Note that 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. In the following description, terms related to LTE and NR will be used for the description, but this embodiment is applicable to NR, LTE, and other RATs. In the following description, terms related to LTE and NR will be used for the description, but this embodiment will be described using terms related to LTE and NR. However, this embodiment The terminology may be applied to other technologies using other terms. Furthermore, the term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

[0016] In this embodiment, the names of each node and entity, and the processing at each node and entity, will be described when the wireless access technology is E-UTRA or NR. However, this embodiment may be used with other wireless access technologies. The names of each node and entity in this embodiment may be different.

[0017] Figure 1 is a schematic diagram of the communication system according to this embodiment. The functions of each node, wireless access technology, core network, interface, etc., described using Figure 1 are only some of the functions closely related to this embodiment, and other functions may also be present.

[0018] E-UTRA100 may be a wireless access technology. Also, E-UTRA100 is between UE122 and eNB102. It may be an air interface. The air interface between UE122 and eNB102 may be called the Uu interface. eNB (E-UTRAN Node B)102 may be a base station device. eNB102 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of the E-UTRA User Plane (UP) protocol described below and the E-UTRA Control Plane (CP) protocol described below. eNB102 communicates the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol to UE122. The rotocol may be terminated. A wireless access network composed of eNBs may be called E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be the core network. Interface 112 is the interface between eNB 102 and EPC 104, and may be called the S1 interface. Interface 112 may have a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface may terminate at the Mobility Management Entity (MME: not shown) within EPC104. The user plane interface of interface 112 is within the service within EPC104. The interface may be terminated at a junction gateway (S-GW: not shown). The control plane interface of interface 112 may be called the S1-MME interface. User plane of interface 112 The interface can be called the S1-U interface.

[0020] One or more eNB102s may be connected to the EPC104 via interface 112. Interfaces may exist between multiple eNB102s connected to the EPC104 (not shown). Interfaces between multiple eNB102s connected to the EPC104 may be called X2 interfaces.

[0021] NR106 may be a wireless access technology. Also, NR106 is an air connection between UE122 and gNB108. It may be an air interface. The air interface between UE122 and gNB108 may be called the Uu interface. gNB (g Node B)108 may be a base station device. gNB108 may have the NR protocol described below. The NR protocol consists of the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol described below. The configuration may be configured such that the gNB108 terminates the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol to the UE122.

[0022] 5GC110 may be the core network. Interface 116 is the interface between gNB108 and 5GC110. It is an interface and may be called an NG interface. Interface 116 has a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. A control plane interface may exist. Interface 116 control plane interface This may be terminated in the Access and Mobility Management Function (AMF: not shown) within 5GC110. The user plane interface of interface 116 may be terminated by a User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 116 is NG-C It can be called an interface. The user plane interface of interface 116 is NG-U It can be called an interface.

[0023] One or more gNB108s may be connected to the 5GC110 via interface 116. Interfaces may exist between multiple gNB108s connected to the 5GC110 (not shown). The interfaces between multiple gNB108s connected to the 5GC110 may be called Xn interfaces.

[0024] eNB102 may have the function to connect to 5GC110. An eNB102 that has the function to connect to 5GC110 may be called ng-eNB. Interface 114 is the interface between eNB102 and 5GC110, NG It can be called an interface. The control plane through which control signals pass is the interface 114. There exists an interface, and / or a user plane interface through which user data passes. The control plane interface of interface 114 may be terminated at the AMF in 5GC110. The user plane interface of interface 114 may be terminated at the UPF in 5GC110. The control plane interface of interface 114 may be called the NG-C interface. Let's call the user plane interface of interface 114 the NG-U interface. A wireless access network consisting of ng-eNB or gNB may be called NG-RAN. NG-RAN, E-UTRAN, etc., may simply be called a network. Furthermore, the network may include eNB. This may include ng-eNB and gNB, among others.

[0025] One or more eNB102s may be connected to the 5GC110 via interface 114. Interfaces may exist between multiple eNB102s connected to the 5GC110 (not shown). Interfaces between multiple eNB102s connected to the 5GC110 may be called Xn interfaces. Also, the eNB102 connected to the 5GC110 and the gNB108 connected to the 5GC110 are connected via interface 120. Good. The interface 120 between eNB102 connected to 5GC110 and gNB108 connected to 5GC110 is It can be called the Xn interface.

[0026] gNB108 may have the function to connect to EPC104. A gNB108 that has the function to connect to EPC104 may be called an en-gNB. Interface 118 is the interface between gNB108 and EPC104, S1 It can be called an interface. Interface 118 is a user interface through which user data passes. A lane interface may exist. User plane interface of interface 118 The line may be terminated at the S-GW (not shown) in EPC104. User plane of interface 118 The interface may be called the S1-U interface. Furthermore, the eNB102 connected to EPC104 and the gNB108 connected to EPC104 may be connected via interface 120. eNB102 connected to EPC104 And the interface 120 between the EPC104 and the gNB108 is called the X2 interface. stomach.

[0027] Interface 124 is the interface between EPC104 and 5GC110, and is either CP only or UP only. or it may be an interface that passes through both CP and UP. Also, interface 114, Some or all of the interfaces, such as interface 116, interface 118, interface 120, and interface 124, may not exist depending on the communication system provided by the telecommunications carrier.

[0028] UE122 may be a terminal device capable of receiving system information and paging messages transmitted from eNB102 and / or gNB108. UE122 may also be a terminal device capable of wireless connection with eNB102 and / or gNB108. Furthermore, UE122 may be a terminal device capable of simultaneously establishing wireless connections with eNB102 and gNB108. UE122 may have the E-UTRA protocol and / or the NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.

[0029] Furthermore, UE122 is connected to EPC104 and / or 5GC110 via eNB102 and / or gNB108. Any capable terminal device may be used. If the core network to which the eNB102 and / or gNB108 communicates with the UE122 is connected is the EPC104, then each Data Radio Bearer (DRB) established between the UE122 and the eNB102 and / or gNB108, as described below, may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet® frames passing through the same EPS bearer.

[0030] Furthermore, if the core network to which UE122 communicates with eNB102 and / or gNB108 is connected is 5GC110, then each DRB established between UE122 and eNB102 and / or gNB108 will be further established within 5GC110. It may be associated with one of the Packet Data Unit (PDU) sessions. Each PDU session may have one or more QoS flows. Each DRB may be associated with one or more QoS flows. Each PDU session may be mapped, or it may not be mapped to any QoS flow. Each QoS flow may be identified by a PDU session identifier (Identity, or ID). Each QoS flow may also 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.

[0031] EPC104 does not need to have a PDU session and / or QoS flow. Also, 5GC110 does not need to have an EPS bearer. When UE122 is connected to EPC104, UE122 does not have information about the EPS bearer. It will have information, but it does not need to have information within the PDU session and / or QoS flow. Also, when UE122 is connected to 5GC110, UE122 will have information within the PDU session and / or QoS flow, but it does not need to have information about the EPS bearer.

[0032] In the following description, eNB102 and / or gNB108 will also be simply referred to as base station equipment, and UE122 will also be simply referred to as terminal equipment or UE.

[0033] Figure 2 is a diagram of an example of the E-UTRA protocol architecture according to this embodiment. Figure 3 is a diagram of an example of the NR protocol architecture according to this embodiment. Note that Figure 2 and / or The functions of each protocol described using Figure 3 are some of the functions closely related to this embodiment. It may also have other functions. In this embodiment, the uplink (UL) and This may be a link from a terminal device to a base station device. In this embodiment, the downlink (DL) may be a link from a base station device to a terminal device.

[0034] Figure 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in Figure 2(A), the E-UTRA UP protocol may be a protocol between UE122 and eNB102. That is, the E-UTRA UP protocol may be a protocol that terminates on the network side at eNB102. Figure 2(A) As shown, the E-UTRA user plane protocol stack is the radio physical layer. It may consist of a PHY (Physical Layer) 200, a MAC (Medium Access Control) 202 which is a media access control layer, an RLC (Radio Link Control) 204 which is a radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206 which is a packet data convergence protocol layer.

[0035] Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in Figure 3(A), NR The UP protocol may be the protocol between UE122 and gNB108. That is, the NR UP protocol. This protocol may terminate at gNB108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack may consist of the wireless physical layer PHY300, the media access control layer MAC302, the wireless link control layer RLC304, the packet data convergence protocol layer PDCP306, and the service data adaptation protocol layer (service data adaptation protocol layer) SDAP (Service Data Adaptation Protocol)310.

[0036] Figure 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in Figure 2(B), in the E-UTRA CP protocol, the Radio Resource Control (RRC) 208, which is the radio resource control layer, may be a protocol between the UE122 and the eNB102. That is, the RRC 208 may be a protocol that terminates at the eNB102 on the network side. In Tokol, the NAS (Non-Access Stratum) 210, which is a non-AS (Access Stratum) layer, may be a protocol between UE122 and MME. That is, NAS210 may be a protocol that terminates at MME on the network side.

[0037] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), the NR CP In Rotokol, the RRC308, which is the wireless resource control layer, is the protocol between UE122 and gNB108. It may be a protocol that terminates with gNB108 on the network side. Also, in the NR CP protocol, the non-AS layer NAS312 is a protocol that connects UE122 and AMF. It can be a protocol. That is, the NAS312 is a protocol that terminates with AMF on the network side. It's okay to have it.

[0038] The AS (Access Stratum) layer may be a layer that terminates between UE122 and eNB102 and / or gNB108. That is, the AS layer is a part of PHY200, MAC202, RLC204, PDCP206, and RRC208 or The layer containing all of them, and / or one of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308 It may be a layer that includes part or all of it.

[0039] In this embodiment, the following terms may be used without distinguishing between the E-UTRA protocol and the NR protocol, and may include PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer). In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS The layers may be PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, or PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. Also, SDAP (SDAP layer) is NR It can be the SDAP (SDAP layer) of the protocol.

[0040] Furthermore, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 are referred to as the PHY for E-UTRA or the PHY for LTE, the MAC for E-UTRA or the MAC for LTE, the RLC for E-UTRA or the RLC for LTE, the PDCP for E-UTRA or the PDCP for LTE, and It is also sometimes referred to as the RRC for E-UTRA or the RRC for LTE. Furthermore, PHY200, MAC202, RLC204, PDCP206, and RRC208 may be described as 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 RRC or LTE RRC, respectively. Yes. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RR, respectively. It is sometimes referred to as C. Additionally, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be written as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0041] This section describes entities in the AS layer of E-UTRA and / or NR. Entities possessing some or all of the functions of the MAC layer may be called MAC entities. Entities possessing some or all of the functions of the RLC layer may be called RLC entities. The functions of the PDCP layer are also described. An entity possessing some or all of the functions of the SDAP layer may be called a PDCP entity. An entity possessing some or all of the functions of the SDAP layer may be called an SDAP entity. Functions of the RRC layer An entity that possesses some or all of the characteristics may be called an RRC entity. MAC entities, RLC entities, PDCP entities, SDAP entities, and RRC entities may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0042] Furthermore, the data provided from MAC, RLC, PDCP, and SDAP to lower layers, and / or the data provided to MAC, RLC, PDCP, and SDAP from lower layers, may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. This refers to the data provided, and / or the data provided to higher layers from MAC, RLC, PDCP, and SDAP. These can be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Furthermore, a segmented RLC SDU can be referred to as an RLC SDU segment.

[0043] Here, the base station equipment and the terminal equipment exchange signals (send and receive) at the higher layer. For example, the base station equipment and the terminal equipment communicate via Radio Resource Control (RRC). At the Radio Resource Control (RRC) layer, RRC messages (also called RRC messages, RRC information, or RRC signalling) may be sent and received. Furthermore, the base station equipment and terminal equipment may send and receive MAC control elements at the MAC (Medium Access Control) layer. Good. Also, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, RRC messages, system information, and / or MAC control elements are higher layer signals (higher layer signaling) or higher layer parameters Also called a higher layer parameter. Each parameter included in the higher layer signal received by the terminal device may also be called a higher layer parameter. In PHY layer processing, the higher layer refers to the layer above the PHY layer, and therefore may refer to one or more layers such as the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non-Access Stratum) layer, etc. For example, in MAC layer processing, the upper layers include one of the following: RRC layer, RLC layer, PDCP layer, NAS layer, etc. It may also mean plural. Below, the meaning of "A is given (provided) at the upper layer" or "A is given (provided) by the upper layer" refers to the upper layer of the terminal device (mainly RRC). The layers (such as the MAC layer) receive A from the base station equipment, and the received A is then sent from the upper layers of the terminal equipment. It may also mean that the upper layer parameters are provided to the physical layer of the terminal device. For example, "being provided with upper layer parameters" in a terminal device may mean that the terminal device receives an upper layer signal from the base station device, and the upper layer parameters contained in the received upper layer signal are provided from the upper layer of the terminal device to the physical layer of the terminal device. Setting upper layer parameters in a terminal device may also mean that the upper layer parameters are provided to the terminal device. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from the base station device and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters in a terminal device may also include setting default parameters that are pre-provided in the upper layer of the terminal device. Sending an RRC message from a terminal device to a base station device When explaining this, the expression "submitting a message from the RRC entity of the terminal device to the lower layer" is sometimes used. "Submitting a message to a lower layer" from an entity may also mean submitting a message to the PDCP layer. In a terminal device, "submitting a message to a lower layer" from the RRC layer means that the RRC message is sent using an SRB (SRB0, SRB1, SRB2, SRB3, etc.). Therefore, it can also be said that this means submitting to the PDCP entity corresponding to each SRB. i. When the RRC entity of a terminal device receives an indication from a lower layer, that lower layer This may mean one or more layers such as the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0044] An example of PHY functionality is described below. The PHY of the terminal device receives downlink from the PHY of the base station device. Downlink (DL) receives data transmitted via the Physical Channel. It may have the function. The PHY of the terminal device is related to the PHY of the base station device, and is an uplink (UL) device. The PHY may have the function of transmitting data via a transport channel. The PHY may be connected to the higher-level MAC via a transport channel. The PHY may transfer data to the MAC via the transport channel. The PHY may also transfer data from the MAC via the transport channel. Data may be provided. In the PHY, RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0045] Now, let's explain physical channels. The following physical channels may be included in the physical channels used for wireless communication between terminal equipment and base station equipment.

[0046] 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)

[0047] PBCH may be used to broadcast system information required by terminal devices.

[0048] Furthermore, in NR, the PBCH may be used to announce the time index (SSB-Index) within the period of the Synchronization Signal Block (SSB).

[0049] PDCCH is used in downlink wireless communication (wireless communication from base station equipment to terminal equipment). It may be used to transmit (or carry) Downlink Control Information (DCI). Here, for the transmission of Downlink Control Information, one or more DCIs (DCI A format (which may also be called a format) may be defined. That is, for downlink control information The field may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate. It may be transmitted in the candidate. The terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The terminal device may also use a CORESET (Control Resource Set) to monitor a set of PDCCH candidates. The DCI format may be used for scheduling PUSCH in the serving cell. PUSCH may be used for sending user data or sending RRC messages, as described later. stomach.

[0050] PUCCH is used in uplink wireless communication (wireless communication from terminal equipment to base station equipment), It may be used to transmit Uplink Control Information (UCI). Here, the Uplink Control Information may include Channel State Information (CSI), which is used to indicate the state of the Downlink channel. The control information may include scheduling requests (SRs) used to request UL-SCH (UL-SCH: Uplink Shared Channel) resources. The link control information includes HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement). It's okay to be born.

[0051] PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the MAC layer. In the case of downlinks, PDSCH may also be used to transmit system information (SI) and random access responses (RAR).

[0052] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or to transmit HARQ-ACK and / or CSI along with uplink data. Alternatively, PUSCH may be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, PUSCH may be used to transmit only UCI. Also, PDSCH or PUSCH may be used to transmit RRC signaling (also called RRC messages) and MAC CE. Here, in PDSCH, the RRC signaling transmitted from the base station equipment may be a common signaling for multiple terminal devices within a cell. Furthermore, the RRC signaling transmitted from the base station equipment may be a dedicated signaling for a particular terminal device (also called dedicated signaling). That is, terminal device-specific information may be transmitted using a dedicated signaling for a particular terminal device. Furthermore, PUSCH may be used to transmit UE Capability on the uplink.

[0053] PRACH may be used to send a random access preamble. PRACH is used in the initial connection establishment procedure, handover procedure, connection re-establishment procedure, etc. It may be used to indicate synchronization (timing adjustment) for relink transmissions and requests for UL-SCH resources.

[0054] An example of MAC functionality is described below. MAC may be called a MAC sublayer. MAC may have the function of mapping various logical channels to corresponding transport channels. Logical channels may be identified by a Logical Channel Identity (Logical Channel ID). MAC may be connected to the higher-level RLC via logical channels. Logical channels may be divided into control channels that transmit control information and traffic channels that transmit user information, depending on the type of information being transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. MAC may have one or more different logical channels. MAC may have the function of multiplexing MAC SDUs belonging to a logical channel and providing them to the PHY. MAC may also have the function of demultiplexing MAC PDUs provided by the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs. MAC may also have the function of performing error correction through HARQ (Hybrid Automatic Repeat request). MAC may also have the function of reporting scheduling information. MAC has the function of prioritizing processing between terminal devices using dynamic scheduling. Good. Also, MAC has the function of prioritizing between logical channels within a single terminal device. MAC has the ability to prioritize the processing of overlapping resources within a single terminal device. That's fine. E-UTRA MAC is a device that identifies Multimedia Broadcast Multicast Services (MBMS). It may have the ability to identify a Multicast Broadcast Service (MBS). The MAC is a transport format. MAC may have a function to select a set. MAC has the function to perform intermittent reception (DRX) and / or intermittent transmission (DTX), and random access (Random Access:RA) Function to execute procedures, notify information on transmittable power, power headroom The Power Headroom Report (PHR) function notifies users of data volume information for the transmission buffer. It may have a Buffer Status Report (BSR) function, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also used in E-UTRA MAC The MAC PDU format used by [unspecified] and the MAC PDU format used by NR MAC may be different. Furthermore, a MAC PDU may contain MAC control elements (MAC control elements), which are elements used for control within the MAC. The element (MAC CE) may be included.

[0055] This section describes the logical channels used for uplink (UL) and / or downlink (DL) in E-UTRA and / or NR.

[0056] BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information, such as system information (SI).

[0057] A PCCH (Paging Control Channel) may be a downlink logical channel for carrying paging messages.

[0058] CCCH (Common Control Channel) may be a logical channel for transmitting control information between terminal equipment and base station equipment. CCCH is used when terminal equipment does not have RRC connection. It may be used. Furthermore, CCCH may be used between a base station device and multiple terminal devices.

[0059] DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information bidirectionally (point-to-point) between terminal equipment and base station equipment. That is fine. Dedicated control information may be control information specific to each terminal device. DCCH may be used when the terminal device has an RRC connection.

[0060] A DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data one-to-one (point-to-point) between a terminal device and a base station device. It may be a logical channel for transmitting data. Dedicated user data may be user data specific to each terminal device. DTCH may exist on both the uplink and downlink.

[0061] Logical channel and transport channel of the uplink in E-UTRA and / or NR Let's explain mapping.

[0062] CCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0063] DCCH is an uplink transport channel, also known as UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0064] DTCH is an uplink transport channel, UL-SCH (Uplink Shared Channel). It can be mapped to this.

[0065] Logical channel and transport channel of the downlink in E-UTRA and / or NR Let's explain mapping.

[0066] BCCH is a downlink transport channel, also known as BCH (Broadcast Channel), and / or This may be mapped to DL-SCH (Downlink Shared Channel).

[0067] PCCH is mapped to PCH (Paging Channel), which is a downlink transport channel. That's fine.

[0068] CCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0069] DCCH is a Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0070] DTCH stands for Downlink Shared Channel (DL-SCH), which is a downlink transport channel. It can be mapped to this.

[0071] An example of RLC functionality is described below. RLC may be called an RLC sublayer. E-UTRA RLC may have the function of segmenting and / or concatenating data provided from the upper layer PDCP and providing it to the lower layer. E-UTRA RLC The NR RLC may have the function of reassembling and reordering the data provided from the lower layer and providing it to the upper layer. The NR RLC provides the data from the PDCP of the upper layer with a sequence number independent of the sequence number added by the PDCP. It may have a function to add numbers. Furthermore, the NR RLC may have a function to segment the data provided by the PDCP and provide it to lower layers. The NR RLC may also have a function to reassemble the data provided by lower layers and provide it to higher layers. The RLC may also have a data retransmission function and / or retransmission request function (Automatic Repeat Request: ARQ). Furthermore, the RLC may have a function to perform error correction using ARQ. To perform this, control information indicating the data that needs to be retransmitted is sent from the RLC receiver to the transmitter. This can be called a status report. Also, the status is sent from the RLC transmitter to the receiver. The instruction to send a task report can be called a "poll." RLC also detects data duplication. It may have a function to perform the following. RLC may also have a data discard function. RLC has Transparent Mode (TM), Unacknowledged Mode (UM), and There can be three response modes (AM: Acknowledged Mode). In TM, it receives from the upper layer. The data will not be split, and the RLC header does not need to be added. TM RLC entities are single A unidirectional entity, and the terminal device uses the TM RLC entity. As a transmitting™ RLC entity, or as a receiving™ RLC entity It may be set as such. UM performs splitting and / or joining of data received from higher layers, adds RLC headers, etc., but does not need to perform data retransmission control. UM RLC entities may be unidirectional or bidirectional entities. If a UM RLC entity is unidirectional, the terminal device may set it as a transmitting UM RLC entity or a receiving UM RLC entity. If a UM RLC entity is bidirectional, the terminal device may set the UM RLC entity as a UM RLC entity consisting of a transmitting side and a receiving side. It can be set as an entity. AM splits and / or combines the data received from the upper layer. In addition, RLC headers may be added, and data retransmission control may be performed. AM RLC entities are bidirectional. The entity is such that the terminal device may configure the AM RLC entity as an AM RLC consisting of a transmitting side and a receiving side. The data provided to lower layers, and / or provided by lower layers, may be called TMD PDU. Similarly, the data provided to lower layers, and / or provided by lower layers, in UM, may be called UMD. It may be called a PDU. Furthermore, data provided to lower layers in AM, or data provided by lower layers, may be called an AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Also, RLC PDUs include data RLC PDUs and... It is acceptable to have RLC PDUs for specific purposes. A data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). Similarly, a control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU). It can be called a troll PDU (or RLC-controlled PDU).

[0072] This section describes an example of PDCP functionality. PDCP may be referred to as the PDCP sublayer. PDCP may have the function of maintaining sequence numbers. Furthermore, PDCP efficiently transmits user data such as IP packets and Ethernet frames over the wireless section. It may have a header compression / decompression function for this purpose. The protocol used for compressing and decompressing IP packet headers may be called the ROHC (Robust Header Compression) protocol. The protocol used for compressing and decompressing Ethernet frame headers is EHC (Ethernet(registered trademark)). This can be called a Header Compression protocol. PDCP may also have data encryption / decryption capabilities. PDCP may also have data integrity protection / verification capabilities. PDCP may also have reordering capabilities. PDCP may also have PDCP SDU retransmission capabilities. PDCP may also have data discarding capabilities using a discard timer. PDCP may also have duplication capabilities. Furthermore, PDCP may have a function to discard duplicate received data. A PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Furthermore, a PDCP PDU may include: There may be both 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).

[0073] This section describes an example of SDAP functionality. SDAP is a Service Data Adaptive Protocol Layer (SAP). SDAP is a bis-data adaptive protocol layer. SDAP transmits data from the 5GC110 to the terminal via the base station equipment. Mapping the downlink QoS flow sent to the device with the data radio bearer (DRB) (map SDAP may have the function of mapping (mapping) and / or mapping the uplink QoS flow sent from the terminal device to the 5GC110 via the base station device to the DRB. SDAP may also have the function of storing mapping rule information. SDAP may also have the function of marking QoS flow identifiers (QoS Flow ID: QFI). Note that there may be data SDAP PDUs and control SDAP PDUs. Data SDAP PDUs may be called SDAP DATA PDUs (SDAP Data PDUs). Control SDAP PDUs may be called SDAP CONTROL PDUs (SDAP Control PDUs). Note that there may be one SDAP entity for each PDU session of the terminal device.

[0074] An example of RRC functionality is described below. RRC may have broadcast functionality. RRC may have paging functionality from EPC104 and / or 5GC110. It may have. The RRC may have a paging function from the eNB102 connected to the gNB108 or 5GC110. The RRC may also have an RRC connection management function. The RRC may also have a wireless base It may have an error control function. The RRC may also have a cell group control function. Furthermore, the RRC may have a mobility control function. The RRC may also have terminal device measurement reporting. The RRC may also have a terminal device measurement reporting control function. Furthermore, the RRC may have a QoS management function. The RRC may also have a wireless link failure detection and recovery function. The RRC may also have an RRC Me Using messages, broadcasting, paging, RRC connection management, wireless bearer control, and cell group management are performed. You may perform mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, wireless link failure detection and recovery, etc. Note that E-UTRA RRC may use The RRC messages and parameters used may differ from those used in NR RRC.

[0075] RRC messages may be sent using the logical channel BCCH, or the logical channel PCCH. It may be sent using the logical channel CCCH, or it may be sent using the logical channel DCCH. Furthermore, RRC messages sent using DCCH may be referred to as dedicated RRC signaling or RRC signaling.

[0076] RRC messages sent using BCCH may include, for example, a Master Information Block (MIB), a System Information Block (SIB) of each type, or other RRC messages. RRC messages sent using PCCH may include, for example, a paging message or other RRC messages.

[0077] RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request messages, RRC Resume Request messages, RRC Reestablishment Request messages, and RRC System Information Request messages. This may include messages such as Sage (RRC System Info Request). It may also include messages such as RRC Connection Request, RRC Connection Resume Request, and RRC Connection Reestablishment Request. Other RRC messages may also be included.

[0078] RRC messages sent in the downlink (DL) direction using CCCH may include, for example, RRC Connection Reject messages, RRC Connection Setup messages, RRC Connection Reestablishment messages, and RRC Connection Reestablishment Reject messages. Messages such as "RRC Setup" may be included. Other RRC messages may also be included.

[0079] RRC signaling transmitted in the uplink (UL) direction using DCCH includes, for example, measurement reports. Messages such as Measurement Report, RRC Connection Reconfiguration Complete, RRC Connection Setup Complete, RRC Connection Reestablishment Complete, Security Mode Complete, and UE Capability Information may be included. Regular reporting message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Re-establishment Complete message This may include messages such as RRC Reestablishment Complete, RRC Resume Complete, Security Mode Complete, and UE Capability Information. Other RRC signaling may also be included.

[0080] RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration messages and RRC Connection Release messages. This may include messages such as RRC Connection Release, Security Mode Command, and UE Capability Enquiry. It may also include, for example, RRC Reconfiguration, RRC Resume, RRC Release, RRC Reestablishment, and security messages. This may include Security Mode Command messages, UE Capability Enquiry messages, and other RRC signaling.

[0081] Let's explain an example of NAS functionality. A NAS may have authentication functionality. Also, a NAS can be mobile It may have a mobility management function. Furthermore, the NAS may have security control functions. You may have it.

[0082] The aforementioned functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS are just examples, and some of each function may be present. Not all of these features need to be implemented. Also, some or all of the functionality of each layer may be included in other layers.

[0083] Next, we will explain the state transitions of UE122 in LTE and NR. When a UE122 connected to an EPC or 5GC has an RRC connection, the UE122 may be in the RRC_CONNECTED state. The state in which an RRC connection has been established may include the state in which the UE122 holds some or all of the UE context described below. The state in which UE122 is able to send and / or receive unicast data may include the state in which UE122 is able to send and / or receive unicast data. Also, UE122 may be in the RRC_INACTIVE state when the RRC connection is suspended. Furthermore, UE122 may be in the RRC_INACTIVE state when UE122 is connected to 5GC and the RRC connection is suspended. When neither in the RRC_INACTIVE state nor the RRC_INACTIVE state, UE122 may be in the RRC_IDLE state.

[0084] Note that when UE122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN The RRC connection may be put into a pause state. If UE122 is connected to EPC, when the RRC connection is put into a pause state, UE122 may transition to the RRC_IDLE state, retaining the UE's AS context and the identifier (resumeIdentity) used for resuming. The upper layer of the UE122's RRC layer (e.g., the NAS layer) will, when UE122 retains the UE's AS context, E-UTRAN has permitted the resumption of the RRC connection, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, then the paused RRC connection You may begin your recovery.

[0085] The definition of hibernation may differ between UE122 connected to EPC104 and UE122 connected to 5GC110. Also, the definition of hibernation may differ depending on whether UE122 is connected to EPC (when UE122 is hibernating in the RRC_IDLE state) or UE122 is connected to 5GC (when UE122 is hibernating in the RRC_INACTIVE state). The procedure for resuming from hibernation may be entirely or partially different.

[0086] Note that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state are referred to as the connection state. These can be called connected mode, inactive mode, or idle mode, or RRC connected mode, RRC inactive mode, or RRC idle mode.

[0087] The UE context held by UE122 may include all or part of the following: PDU session context, security key, UE radio capability information, and UE security capability information. Any or all of the UE contexts held are the same as the UE contexts held by UE122. It may include the same information, or it may contain information different from the information contained in the UE context held by UE122. This may include information. Furthermore, the UE context may include all or part of the AS context of the UE, as described below.

[0088] The AS context of the UE held by UE122 may include all or part of the following information: the current RRC settings, the current security context, the PDCP status including the ROHC (RObust Header Compression) status, the C-RNTI (Cell Radio Network Temporary Identifier) ​​used by the source PCell, the cell identifier, and the physical cell identifier of the source PCell. The AS context of the UE held by any or all of eNB102 and gNB108 may include the same information as the AS context of the UE held by UE122, or it may include information different from the information included in the AS context of the UE held by UE122.

[0089] The security context may include all or part of the following at the AS level: the encryption key, 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 the counter used for replay protection.

[0090] Next, we will explain the Serving Cell. The CA and / or DC described later... In terminal devices with an unconfigured RRC connection, the serving cell may consist of one primary cell (PCell). Furthermore, the CA and / or DC described later may be configured. In terminal devices with RRC connectivity, multiple serving cells are one or more special A Special Cell (SpCell) may refer to a set of cells (a set of cells) consisting of one or more Secondary Cells (SCells). A SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and may always be activated. A PCell may be a cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. A PCell may also be used in the RRC connection re-establishment procedure when a terminal device re-establishes an RRC connection. It may be a cell. Also, PCell is used in the random access procedure during handover. It may be a cell used for purposes other than those mentioned above. PSCell may be a cell used in the random access procedure when adding a secondary node, as described later. SpCell may be a cell used for purposes other than those mentioned above.

[0091] If a group of serving cells configured by a terminal device consists of a SpCell and one or more SCells, it may be considered that the terminal device is configuring carrier aggregation (CA). Furthermore, for a terminal device configuring CA, a cell providing additional radio resources to a SpCell may be considered an SCell.

[0092] A group of serving cells configured by a terminal device in RRC, where the terminal device is the uplink For the cell where the link is set, the same timing reference cell and the same A group of serving cells that use Timing Advance values ​​may be called a Timing Advance Group (TAG). A TAG containing a MAC entity SpCell may represent a Primary Timing Advance Group (PTAG). A TAG other than a PTAG may represent a Secondary Timing Advance Group (STAG). One or more of the aforementioned TAGs may be configured for each cell group, as described later.

[0093] This section explains cell groups, which are configured by terminal devices at higher layers (such as RRC). A cell group may consist of one SpCell. Alternatively, a cell group may consist of one SpCell and one or more SCells. That is, a cell group may consist of one SpCell and, if necessary... A cell group may optionally consist of one or more SCells. A cell group may also be described as a set of cell(s).

[0094] Dual Connectivity (DC) is a technology that enables data communication using the radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). It may be a technique. When DC or MR-DC (described later) is performed, the base station equipment can communicate with the terminal equipment. Cell groups may be added. To perform DC (Data Center) operations, the first base station device may add a second base station device. The first base station device is called the Master Node (MN). Furthermore, the cell group formed by the master node may be called the Master Cell Group (MCG). The second base station device is called the Secondary Node (SN). It is acceptable to refer to it as such. Furthermore, the cell group formed by the secondary node may be called a Secondary Cell Group (SCG). Note that the master node and secondary node may be configured within the same base station equipment.

[0095] Furthermore, when a terminal device does not set a DC, the cell group that the terminal device sets may be called an MCG. The SpCell set by can be a PCell. Also, the terminal device can set an NR that does not have a DC set. It can be called a standalone device.

[0096] Furthermore, Multi-Radio Dual Connectivity (MR-DC) may be defined as a technology that performs DC using E-UTRA for MCG and NR for SCG. It is acceptable. Furthermore, MR-DC is a technology that performs DC using NR in both MCG and SCG. Good. MR-DC can be a technology included in DC. An example of MR-DC using E-UTRA in the MCG and NR in the SCG is EN-DC (E-UTRA-NR Dual Connectivity) which uses EPC in the core network, and An NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC in the A network is acceptable. Furthermore, as an example of an MR-DC using NR in the MCG and E-UTRA in the SCG, an NE-DC (NR-E-UTRA Dual Connectivity) using 5GC in the core network is acceptable. Also, as an example of an MR-DC using NR in both the MCG and SCG, It is acceptable to have NR-DC (NR-NR Dual Connectivity) using 5GC in the core network.

[0097] In a terminal device, there may be one MAC entity for each cell group. For example, when a terminal device sets up DC or MR-DC, there may be one MAC entity for MCG and one MAC entity for SCG. The MAC entity for MCG in the terminal device can represent all states (RRC idle state, RRC connected state, and RRC inactive state). In terminal devices such as the above, the MAC entity for the SCG in the terminal device may always be established. In addition, the MAC entity for each cell group in the terminal device may be created by the terminal device when the terminal device sets up the SCG. In addition, the MAC entity for each cell group in the terminal device may always be established by the terminal device Configuration may be performed by receiving RRC signaling from a local station. If the MAC entity is associated with MCG, SpCell may mean PCell. Also, MAC entity If associated with an SCG, SpCell may mean 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. In EN-DC and NGEN-DC, the MAC entity for MCG is the E-UTRA MAC entity. It is acceptable for the MAC entity for SCG to be an NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be an NR MAC entity, and the MAC entity for SCG may be an E-UTRA MAC entity. Also, in NR-DC, MCG The MAC entities for both and SCG may be NR MAC entities. The fact that there is one entity for each cell group can be rephrased as saying that there is one MAC entity for each SpCell. This can be rephrased as one MAC entity for each SpCell.

[0098] This section explains radio bearers. When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a wireless connection. Good. The radio bearer used in CP may be called a Signaling Radio Bearer (SRB). The radio bearer used in UP may be called a Data Radio Bearer (DRB). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRBs may be called an SRB identifier (SRB Identity, or SRB ID). The radio bearer identifier for DRBs may be called a DRB identifier (DRB Identity, or DRB ID). For E-UTRA, SRB0 to SRB2 may be defined, or other SRBs may be defined. For NR, SRB0 to SRB3 may be defined, or other SRBs may be defined. SRB0 may be an SRB for RRC messages transmitted and / or received using the logical channel CCCH. SRB1 is for RRC signaling and NAS before SRB2 is established. It may be an SRB for signaling. RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. All RRC signaling and NAS signaling transmitted and / or received using SRB1 have a logical channel. DCCH of the RU may be used. SRB2 is for NAS signaling and for recording measurement information (logged It may be an SRB for RRC signaling that includes measurement information. All RRC signaling and NAS signaling transmitted and / or received includes logical chips. The DCCH of the channel may be used. Also, SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and / or receiving specific RRC signaling when a terminal device sets EN-DC, NGEN-DC, NR-DC, etc. Transmitting and / or receiving using SRB3 All RRC signaling and NAS signaling may use the DCCH logical channel. Other SRBs may be provided for other purposes. The DRB is used for user data. It may be a wireless bearer. RRC signals transmitted and / or received using DRB. A logical channel (DTCH) may be used for the junction.

[0099] This section describes wireless bearers in terminal devices. Wireless bearers include RLC bearers. Good. An RLC bearer may consist of one or two RLC entities and a logical channel. When a bearer has two RLC entities, the RLC entity is the TM RLC entity. and / or in a unidirectional UM mode RLC entity, this may be a transmitting RLC entity and a receiving RLC entity. SRB0 may consist of one RLC bearer. RLC bearer of SRB0 SRB0 may consist of TM's RLC entities and logical channels. SRB0 may always be established in terminal devices in all states (RRC idle state, RRC connected state, and RRC inactive state, etc.). SRB1 may be established and / or configured by the terminal device in RRC when the terminal device transitions from the RRC idle state to the RRC connected state, based on RRC signaling received from the base station device. SRB1 consists of one PDCP entity and one or more RLC bearers. It may be. The RLC bearer of SRB1 may consist of AM's RLC entity and logical channel. SRB2 receives from base station equipment terminal devices in an RRC connection state with AS security activated. RRC signaling enables one connection to a terminal device and / or the terminal device to be configured with RRC. SRB2 may consist of one PDCP entity and one or more RLC bearers. The RLC bearers of SRB2 may consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be located on the master node. SRB3 is established when a secondary node is added or changed in EN-DC, NGEN-DC, or NR-DC, and terminal devices with AS security enabled and RRC connection status are connected from the base station device. The received RRC signaling may establish and / or configure one RRC on the terminal 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 array may consist of AM RLC entities and logical channels. SRB3 base station equipment The PDCP on the side may be located on the secondary node. The DRB may be established and / or configured on the terminal device by RRC signaling received from the base station device by the terminal device in an RRC connection state with AS security activated. The DRB is one PDCP entity and 1 It may consist of one or more RLC bearers. The RLC bearer of the DRB may consist of an AM or UM RLC entity and a logical channel.

[0100] In MR-DC, a wireless bearer on the master node where PDCP is located can be called an MN-terminated bearer. Also, in MR-DC, a secondary node A wireless bearer on which a PDCP is placed is called an SN-terminated bearer. That's fine. Furthermore, in MR-DC, a wireless bearer where the RLC bearer exists only in the MCG can be called an MCG bearer. Also, in MR-DC, if the RLC bearer exists only in the SCG... A wireless bearer that has both an MCG and an SCG can be called an SCG bearer. Also, in a DC, a wireless bearer that has both an RLC bearer and an SCG can be called a split bearer.

[0101] When a terminal device configures MR-DC, the bearer types of SRB1 and SRB2 established and / or configured by the terminal device may be MN-terminated MCG bearer and / or MN-terminated split bearer. Also, when a terminal device configures MR-DC, the bearer type of SRB3 established and / or configured by the terminal device may be SN-terminated SCG bearer. Also, when a terminal device configures MR-DC, the bearer type of DRB established and / or configured by the terminal device may be any of all bearer types.

[0102] For RLC bearers established and / or configured by a terminal device in a cell group composed of E-UTRA, the RLC entities established and / or configured by the terminal device may be E-UTRA RLC. Also, for RLC bearers established and / or configured by a terminal device in a cell group composed of NR, The RLC entities established and / or configured by the device may be NR RLCs. When a terminal device configures EN-DC, the PDCP entities established and / or configured by the terminal device for the MN termination MCG bearer The PT can be either E-UTRA PDCP or NR PDCP. Also, the terminal device sets EN-DC. In this case, the terminal device will use other bearer-type wireless bearers, namely MN-terminated split bearers, MN-terminated SCG bearers, SN-terminated MCG bearers, SN-terminated split bearers, and SN-terminated SCG bearers. The PDCP established and / or set for R may be an NR PDCP. Also, when the terminal device sets NGEN-DC, NE-DC, or NR-DC, the terminal device sets all bearer types The PDCP entity established and / or configured for the wireless bearer may be an NR PDCP.

[0103] In NR, the DRB established and / or configured by the terminal device may be associated with one PDU session. The terminal device establishes and / or configures one SDAP entity for one PDU session. The SDAP entities, PDCP entities, RLC entities, and logical channels established and / or configured by the terminal device may be established and / or configured by the terminal device through RRC signaling received from the base station device.

[0104] Note that regardless of whether the terminal device configures MR-DC or not, the master node is eNB102. A network configuration with EPC104 as the core network may be called E-UTRA / EPC. A network configuration with eNB102 as the master node and 5GC110 as the core network may be called E-UTRA / 5GC. A network configuration with gNB108 as the master node and 5GC110 as the core network may be called NR, or NR / 5GC. When terminal devices do not configure MR-DC, the above master nodes... This can refer to a base station device that communicates with terminal devices.

[0105] This section describes the RRC signaling flow transmitted and received between terminal equipment and base station equipment. Figure 4 shows the flowchart for the various settings in the RRC according to this embodiment. This is a diagram illustrating an example. Figure 4 shows an example of the flow when RRC signaling is sent from the base station equipment (eNB102, and / or gNB108) to the terminal equipment (UE122).

[0106] In Figure 4, the base station device creates an RRC message (step S400). The creation of an RRC message by the base station device may be performed in order for the base station device to distribute system information (SI) or paging messages. The creation of a data entry involves the base station sending RRC signaling to a specific terminal device to perform a specific action. This may be done for the purpose of trust. Processes performed on a specific terminal device include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, and RRC connection reconfiguration. This may include processes such as pausing the session and releasing the RRC connection. RRC connection reconfiguration may include, for example, control of wireless bearers (establish, change, release, etc.) and control of cell groups (establish, add (Addition, modification, release, etc.), measurement settings, handover, security key updates, etc. Processing may be included. Also, the creation of RRC messages in the base station equipment is done by sending from the terminal equipment. This may be done in response to transmitted RRC signaling. Responses to RRC signaling transmitted from a terminal device may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, and responses to RRC restart requests. RRC messages contain various informational and configuration information (parameters). These parameters are fields and / or information elements. You can call it that, and it is written using the ASN.1 (Abstract Syntax Notation One) notation method. You may do so.

[0107] In Figure 4, the base station device then transmits the created RRC signaling to the terminal device (S Step S402). Next, the terminal device performs any necessary processing, such as configuration, according to the RRC signaling it has received (Step S404). The terminal device that has performed the processing may send an RRC signaling response to the base station device (not shown).

[0108] RRC signaling may be used for purposes other than those mentioned above.

[0109] In MR-DC, the RRC signaling for SCG settings (cell group settings, wireless bearer settings, measurement settings, etc.) may be transmitted between the master node and the terminal device. For example, in EN-DC or NGEN-DC, the RRC signaling transmitted between eNB102 and UE122 is used. The RRC signaling for E-UTRA may include the RRC signaling for NR in the form of a container. Similarly, in NE-DC, the RRC signaling for NR transmitted and received between gNB108 and UE122 may include the RRC signaling for E-UTRA in the form of a container. RRC signaling for SCG-side configuration may be transmitted and received between the master node and the secondary node.

[0110] Note that the RRC signature for E-UTRA sent from eNB102 to UE122 is not limited to cases where MR-DC is used. The signaling may include RRC signaling for NR, and the RRC signaling for NR transmitted from gNB108 to UE122 may include RRC signaling for E-UTRA.

[0111] Next, we will explain handover in LTE and NR. Handover may be the process by which a terminal device in an RRC-connected state changes the serving cell from the source SpCell to the target SpCell. Handover may be part of the mobility control performed by the RRC. In this context, the handover is indicated by an RRC signal that receives a handover from the base station equipment. It may be done based on the signaling. RRC signaling that indicates a handover is, A message regarding the reconfiguration of an RRC connection, including an information element containing parameters that instruct the user (e.g., a MobilityControlInfo information element or a ReconfigurationWithSync information element). It may be so. Note that the MobilityControlInfo information element is a mobility control setting information element. This may be referred to as mobility control settings or mobility control information. The ReconfigurationWithSync information element may be referred to as a synchronized reconfiguration information element. In addition to that, or Instead, the RRC signaling that instructs a handover is a message indicating the movement of another RAT to a cell (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand). It is also acceptable for the handover to be triggered by RRC. The conditions for performing the operation include, among others, that AS security is activated, that the terminal device has established an SRB2, and that at least one DRB is established. Or all conditions may be included.

[0112] This section explains an example of parameters included in the message regarding the reconfiguration of the RRC connection. Figure 7 shows the message regarding the reconfiguration of the RRC connection in NR, as shown in Figure 4. This is an example of an ASN.1 description representing a field and / or information element. This is not limited to Figure 7. In the example of ASN.1 in the embodiment, <omitted> indicates that other information is omitted, not part of the ASN.1 notation. Information elements may also be omitted where <omitted> is not present. In this embodiment, the example of ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names or notations may be used. Furthermore, the example of ASN.1 is used in the description. To avoid complexity, only examples of key information closely related to this embodiment are shown. In each embodiment, the parameters described in ASN.1 are referred to as fields and information. In some cases, all information elements are referred to as "information elements" without distinction. Furthermore, in each embodiment, the fields and / or information elements included in the RRC signaling, as described in ASN.1, are: This can be rephrased as "information," or in addition to or instead of information, it can be rephrased as "parameters." The message regarding the resetting of the RRC connection may be the RRC resetting message in NR. Furthermore, the message regarding the resetting of the RRC connection may be the RRC connection resetting message in E-UTRA.

[0113] In Figure 7, the message regarding the reconfiguration of the RRC connection may include an information element used for security key updates (MasterKeyUpdate information element). The MasterKeyUpdate information element may include an information element indicating whether or not to derive a new security key (keySetChangeIndicator information element) and an information element indicating the NCC parameters (nextHopChainingCount information element). , information elements (nas-Container information elements) that indicate fields for transferring UE-specific NAS layer information between the network and terminal devices, some or all of It may include a section.

[0114] In Figure 7, the message regarding the reconfiguration of the RRC connection contains information elements (CellGroupConfig information elements) used for setting, changing, releasing, etc., of the NR's MCG or SCG cell group. It may be included. Messages regarding the reconfiguration of RRC connections may independently include CellGroupConfig information elements for MCG configuration and CellGroupConfig information elements for SCG configuration. It is acceptable to include it. The CellGroupConfig information element is a cell group setting information element, or cell group It may also be called a loop setting.

[0115] The CellGroupConfig information element contains identifier information to identify this cell group as follows: The cellGroupId information element may be included.

[0116] The CellGroupConfig information element may include the RLC-BearerConfig information element as information used to configure the RLC entity.

[0117] The CellGroupConfig information element may include the MAC-CellGroupConfig information element, which is used to set the MAC parameters for that cell group.

[0118] The CellGroupConfig information element may include the PhysicalCellGroupConfig information element, which is used to set the PHY(L1) parameters specific to that cell group.

[0119] The CellGroupConfig information element contains the parameter settings for the SpCell of that cell group. The information used may include SpCellConfig information elements. SpCellConfig information elements may also be called SpCell configuration information elements or SpCell configurations.

[0120] The CellGroupConfig information element may include a SCellConfig information element for each SCell, which is used to set parameters for one or more SCells in that cell group. The SCellConfig information element may also be called a SCell setting information element or SCell setting.

[0121] The MAC-CellGroupConfig information element may include a TAG-Config information element as information used to set parameters related to TAGs. The TAG-Config information element may include identifiers (TAG-Id) of one or more TAGs set by the terminal device and the value of the time adjustment timer corresponding to the identifier of that TAG.

[0122] The SpCellConfig information element contains terminal device-specific (UE-specific) parameters related to SpCell. The ServingCellConfig information element may be included as information used for setting the SCell. Furthermore, the SCellConfig information element may include this ServingCellConfig information element as information used for setting terminal device-specific (UE specific) parameters related to the SCell. The CellGroupConfig information element is used for setting terminal device-specific parameters related to the SpCell and each SCell. Each serving cell may contain a ServingCellConfig information element. Each ServingCellConfig information element may contain a TAG identifier (TAG-Id) indicating which TAG within the cell group the serving cell belongs to. In addition, the ServingCellConfig information element may contain terminal device-specific information. In addition to parameters, cell-specific parameters may also be included.

[0123] Each ServingCellConfig information element may include an initialDownlinkBWP, which indicates the BWP-DownlinkDedicated information element, as a terminal device-specific setting for the initial downlink BWP. The BWP-DownlinkDedicated information element is also referred to as a downlink BWP-specific setting. In addition to or instead of that, each ServingCellConfig information element includes the first active This may include some or all of the following: the firstActiveDownlinkBWP-Id, the BWP inactivity timer (bwp-InactivityTimer), and the default downlinkBWP-Id.

[0124] The ServingCellConfig information element, used for setting terminal device-specific parameters for each SCell, may include a DormantBWP-Config information element as a setting for a dormant BWP for the SCell. The DormantBWP-Config information element is also referred to as the dormant BWP setting. For example, the DormantBWP-Config information element may include a dormant BWP identifier (dormantBWP-Id).

[0125] The SCellConfig information element may include an RRC parameter (sCellState) that indicates whether SCell is activated or not during SCell configuration. sCellState is also referred to as the SCell state setting. Example For example, if the SCellConfig information element contains sCellState, or instead, The RRC entity of the terminal device sets the sCellState contained in the SCellConfig information element to activate. If configured, the MAC entity of the terminal device may activate the SCell, and in addition to or instead, the RRC layer of the terminal device may configure its lower layers (such as the MAC entity) to consider that the SCell is activated. Alternatively, for example, if the SCellConfig information element does not contain sCellState In addition, the MAC entity of the terminal device may deactivate the SCell, or, in addition to or instead of doing so, the RRC layer of the terminal device may configure its lower layers (such as the MAC entity) to consider that the SCell is deactivated.

[0126] The ServingCellConfig information element for setting terminal-specific parameters for each SCell that the terminal device has not set PUCCH may include an SCell inactivity timer.

[0127] Each ServingCellConfig information element has an UplinkConfig information element as an uplink setting. It may include the following. The UplinkConfig information element is also called the uplink setting. The UplinkConfig information element includes terminal device-specific settings for the initial uplink BWP (initial uplink BWP). The BWP-UplinkDedicated information element may include initialUplinkBWP. The BWP-UplinkDedicated information element is also referred to as the uplink BWP-only setting. In addition to or instead Furthermore, the UplinkConfig information element may include the first active uplink BWP identifier (firstActiveUplinkBWP-Id).

[0128] The SpCellConfig information element may include a ReconfigurationWithSync information element, which contains information necessary for the process of asynchronous reconfiguration from a source SpCell to a target SpCell. The ReconfigurationWithSync information element is as described above. This may be a synchronized reconfiguration information element. If the MCG's SpCellConfig information element includes a ReconfigurationWithSync information element, the synchronized reconfiguration process for the target SpCell may be a handover. If the SCG's SpCellConfig information element includes a ReconfigurationWithSync information element, the synchronized reconfiguration process for the target SpCell may be a PSCell addition or PSCell modification.

[0129] The ReconfigurationWithSync information element and the SCellConfig information element may include a ServingCellConfigCommon information element, which is used to set cell-specific parameters for a serving cell. The ServingCellConfigCommon information element may include parameters typically obtained from the cell's SSB, MIB, or one or more SIBs when a terminal device accesses the cell from an idle state.

[0130] The ReconfigurationWithSync information element includes, for example, the cell group of the target SpCell. The information element of ReconfigurationWithSync may include information about the C-RNTI value used. For example, it may include information regarding the parameters of timer T304, which will be described later. Reconfiguration nWithSync information elements include, for example, the contention criteria rancher in the target SpCell. Contention-based Random Access (CBRA) procedure or contention-free access The RACH-ConfigDedicated information element may be included as information necessary for executing the contention-free Random Access (CFRA) procedure. The RACH-ConfigDedicated information element is also referred to as the RACH-specific setting.

[0131] Figure 8 shows the SCellConfig information element and the ServingCellConfigCommon information element contained within the ReconfigurationWithSync information element within the SpCellConfig information element in Figure 7. This is an example of an ASN.1 description representing a world and / or information element.

[0132] The ServingCellConfigCommon information element includes the physical cell identifier (physCellId) of that cell. It's okay to be born.

[0133] The ServingCellConfigCommon information element contains cell-specific (cell-common) downlink parameters. The information provided may include the DownlinkConfigCommon information element. The DownlinkConfigCommon information element is also referred to as the common downlink settings.

[0134] The ServingCellConfigCommon information element contains cell-specific (cell-common) uplink parameters. The information provided may include the UplinkConfigCommon information element. The UplinkConfigCommon information element is also referred to as the common uplink settings.

[0135] The ServingCellConfigCommon information element contains information for all uplink transmissions in that cell. The value of N_{TA, offset} to which it is applied may be included.

[0136] The DownlinkConfigCommon information element may include the FrequencyInfoDL information element as basic information about the downlink carrier and transmissions on that downlink carrier. The FrequencyInfoDL information element may include SSB frequency information.

[0137] The DownlinkConfigCommon information element contains the initial downlink BWP (initial downlink) for that cell. The BWP setting includes initialDownlinkBWP, which indicates the BWP-DownlinkCommon information element. That's fine. In addition, or instead, the DownlinkConfigCommon information element may include initialDownlinkBWP-RedCap, which indicates the BWP-DownlinkCommon information element that one or more performance-limited terminals (RedCap UEs) use instead of initialDownlinkBWP. The BWP-DownlinkCommon information element is also referred to as the downlink BWP common setting.

[0138] The BWP-DownlinkCommon information element may include BWP information elements as information for the terminal device to set generic parameters of BWP.

[0139] The BWP-DownlinkCommon information element may include the PDCCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the PDCCH of this BWP. The PDCCH-ConfigCommon information element is also referred to as the PDCCH common settings.

[0140] The BWP-DownlinkCommon information element may include the PDSCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the PDSCH of this BWP. The PDSCH-ConfigCommon information element is also referred to as the PDSCH common settings.

[0141] The PDCCH-ConfigCommon information element may include a SearchSpaceZero information element as information for the terminal device to set the parameters of the common search space (CSS) #0. This SearchSpaceZero information element may be included in the PDCCH-ConfigCommon information element only if the BWP is the initial downlink BWP.

[0142] The PDCCH-ConfigCommon information element may include a ControlResourceSetZero information element as information for a terminal device to set the parameters of the common CORESET#0 used in one or more common search spaces and one or more UE-specific search spaces. This ControlResourceSetZero information element may be included in the PDCCH-ConfigCommon information element only if the BWP is the initial downlink BWP.

[0143] The PDCCH-ConfigCommon information element contains additional common CORESET parameters set by the terminal device. The ControlResourceSet information element may be included as information for determining the value.

[0144] The PDCCH-ConfigCommon information element may contain a list of information elements (SearchSpace information elements) (commonSearchSpaceList) that indicate one or more additional CSS settings.

[0145] The PDCCH-ConfigCommon information element contains information (searchSpaceSIB1) indicating which CSS setting in the commonSearchSpaceList corresponds to the search space setting for system information (SIB1). It may be included.

[0146] The PDCCH-ConfigCommon information element may include information (searchSpaceOtherSystemInformation) indicating which CSS setting in the commonSearchSpaceList corresponds to the search space setting for system information (SIB2 and later).

[0147] The PDCCH-ConfigCommon information element may include information (pagingSearchSpace) indicating which CSS setting in commonSearchSpaceList is responsible for setting the search space for paging messages.

[0148] The UplinkConfigCommon information element may include the FrequencyInfoUL information element, which sets the absolute uplink frequency and lists multiple virtual carriers specific to each subcarrier. For example, the FrequencyInfoUL information element may include the maximum transmission frequency. It may include information indicating power consumption.

[0149] The UplinkConfigCommon information element may include an initialUplinkBWP, which indicates the BWP-UplinkCommon information element, as the initial uplink BWP setting for that cell. In addition to or instead of the above, the UplinkConfigCommon information element may contain the BWP-UplinkCommon information that one or more performance-limited terminals (RedCap UEs) use instead of initialUplinkBWP. The initialUplinkBWP-RedCap element may be included to indicate the element. The BWP-UplinkCommon information element is above This is also called the BWP common settings for linking.

[0150] The BWP-UplinkCommon information element may include BWP information elements as information for the terminal device to set generic parameters of the BWP.

[0151] The BWP-UplinkCommon information element may include the PUCCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for PUCCH of this BWP. The PUCCH-ConfigCommon information element is also referred to as the PUCCH common settings.

[0152] The BWP-UplinkCommon information element may include the PUSCH-ConfigCommon information element, which provides information for the terminal device to set cell-specific parameters for the BWP's PUSCH function. The PUSCH-ConfigCommon information element is also referred to as the PUSCH common settings.

[0153] The BWP-UplinkCommon information element contains parameters for cell-specific random access that the terminal device uses. The RACH-ConfigCommon information element may be included as information for configuring the settings. The RACH-ConfigCommon information element is also referred to as the RACH common setting.

[0154] Note that each of the above information elements may include other information besides the information described.

[0155] This document describes the RRC reset procedure. The RRC reset procedure involves the terminal device resetting the RRC connection. Based on the message regarding the reconfiguration, modify the RRC connection. The procedure may be any of the following. Furthermore, the purpose of the RRC reset procedure may be some or all of (A) through (F) below. (A) Establish, modify, and / or release a wireless bearer. (B) Perform a reconfiguration with synchronization. (C) Set up, modify, and / or release the measurement. and (D) Adding, modifying, and / or releasing SCells and cell groups. (E) Add, modify, and / or release conditional handover (CHO) settings. (F) Adding, modifying, and / or releasing conditional PSCell change (CPC) or conditional PSCell addition (CPA) settings.

[0156] The base station equipment (Network) may initiate the RRC reset procedure for terminal devices in the RRC_CONNECTED state. "Initiating the process" means "the base station equipment will initiate the RRC connection reconfiguration process for the terminal equipment." This can be rephrased as "send a message."

[0157] When the terminal device receives a message regarding the reconfiguration of the RRC connection, When performing a conditional reset (CHO, CPA, or CPC), some or all of the following RRP processes (A) through (D) may be performed. (Processing RRP) (A) If the message regarding the reconfiguration of the RRC connection includes the MCG cell group settings If so, the cell group settings are used to configure the cell group. In addition, if the cell group settings include a SpCell setting that contains synchronized reconfiguration information elements, a synchronized reconfiguration is performed. (B) If the message regarding the reconfiguration of the RRC connection includes the SCG cell group settings If so, the cell group settings are used to configure the cell group. In addition, if the cell group settings include a SpCell setting with synchronized reconfiguration information elements, a synchronized reconfiguration is performed. (C) If the message regarding the reconfiguration of the RRC connection contains information about conditional reconfiguration, the conditional reconfiguration process will be performed using that information. (D) To transmit using the new settings, an RRC reconfiguration completion message is submitted to the lower layers of the terminal device (PHY, MAC, etc.).

[0158] The terminal device may perform some or all of the following RWS processes (A) through (G) in order to execute a synchronized reconfiguration. This can be rephrased as "perform the configuration" or "trigger a reconfiguration with synchronization." (Processing RWS) (A) If this procedure is performed for MCG, or if this procedure is performed for RRC Connect The message regarding the reset of the system includes an embedded E-UTRA or NR RRC signal. If performed for an SCG that has not been notified of deactivation within the ring, the synchronized reset information Set the value of timer T304, described later, included in the information element, and set the timer for the corresponding SpCell. Start T304. (B) If the synchronized reset information element contains a frequencyInfoDL information element, it is determined that the target SpCell is the cell indicated by the physical cell identifier contained in the synchronized reset information element, which is at the SSB frequency indicated by the frequencyInfoDL information element. If the synchronized reset information element does not contain a frequencyInfoDL information element, the target SpCell is determined to be the cell indicated by the physical cell identifier contained in the synchronized reset information element. This is indicated by the physical cell identifier included in the synchronized reset information element, which is on the same SSB frequency as the SpCell. It is determined that this is a cell that will be processed. (C) Start downlink synchronization to target SpCell. (D) If the timing information required for the random access procedure is not held, the target Retrieve the MIB of SpCell. (E) Reset the MAC entities of the cell groups that are subject to synchronized reconfiguration. (F) The value of the new UE identifier (newUE-Identity) included in the synchronized reset information element is synchronized Apply as C-RNTI for the cell group subject to reconfiguration. (G) Configure the lower layers of the RRC (PHY, etc.) according to the common settings of SpCell.

[0159] Conditional resetting is described below. The terminal device receives one or more conditional resetting information elements from the network, and therefore, the terminal device sets candidate target SpCells associated with each conditional resetting information element received from the network. The terminal device evaluates the state of the set candidate target SpCells. The terminal device performs the evaluation and applies one of the conditional RRC resetting information elements included in the conditional resetting information elements associated with one or more candidate target SpCells that satisfy the execution conditions. The final device may maintain a list of entries (VarConditionalReconfig) described later for conditional reconfiguration.

[0160] Conditional resetting may be called conditional handover when the candidate target SpCell is an MCG SpCell (i.e., a PCell). Also, conditional resetting may be called conditional handover when the candidate target SpCell is an SCG If it is a SpCell (i.e., a PSCell), then conditional PSCell addition, and / or conditional PSCell It can be called a change.

[0161] The terminal device processes information regarding conditional resetting (for example, conditions) as part of the conditional resetting setting process. Based on the receipt of the conditional reset information element, the conditional reset information is attempted to If the row condition reset information element (attemptCondReconfig) is included, then in the cell selection during the RRC connection re-establishment procedure described below, if the selected cell is a target candidate cell (e.g., candidate target SpCell) and the cell selection is the first cell selection after a conditional reset failure (e.g., expiration of timer T304), then a conditional reset may be performed.

[0162] As part of the conditional reset setting process, if the information regarding the conditional reset includes an entry deletion list (condReconfigToRemoveList), the terminal device may remove the conditional reset setting specified in the entry deletion list from the settings held by the terminal device. Specifically, if an entry identifier (condReconfigId) included in the entry deletion list is included in the list of entries held by the terminal device, the terminal device may delete the entry corresponding to the entry identifier from the list of entries held by the terminal device.

[0163] In the following explanation, the list of conditional reset entries held by the terminal device will also be simply referred to as the entry list. That is, unless otherwise specified, "entry list" in the following explanation refers to the list of conditional reset entries held by the terminal device. The conditional reset entry list may also be a variable named VarConditionalReconfig. The entry identifier will also be simply referred to as the entry identifier.

[0164] As a setting process for conditional reconfiguration, when the information regarding the conditional reconfiguration includes an entry addition / modification list (condReconfigToAddModList), the terminal device may add or modify the settings held by the terminal device with the settings of the conditional reconfiguration included in the entry addition / modification list. The entry addition / modification list may be a list of one or more conditional reconfiguration information elements. The terminal device may set each entry with a conditional reconfiguration information element. The conditional reconfiguration information element may include an entry identifier, an execution condition, and a conditional RRC reconfiguration information element. Yes.

[0165] Specifically, when each entry identifier included in the entry addition / modification list exists in the entry of the entry list, the terminal device may perform the following process (A) and / or (B). (A) When the entry included in the entry addition / modification list includes an execution condition (condExecutionCond), replace the execution condition of the entry in the entry list that matches the entry identifier of this entry with the execution condition included in the entry addition / modification list of that entry. (B) When the entry included in the entry addition / modification list includes a conditional RRC reconfiguration information element (condRRCReconfig), replace the conditional RRC reconfiguration information element of the entry list that matches the entry identifier of this entry with the conditional RRC reconfiguration information element included in the entry addition / modification list of that entry. Also, when the entry identifier included in the entry addition / modification list is not included in the entry list, the terminal device may add a new entry corresponding to the entry identifier not included in the entry list to the entry list.

[0166]

[0167] ​The entry deletion list may be a list of one or more entry identifiers to be deleted. Each entry included in the entry addition / modification list includes an entry identifier and may also include execution conditions and / or conditional RRC reset information elements. Each entry may be associated with one of one or more candidate target SpCells. The entry identifier is used to identify each CHO, CPA, and CPC entry. The identifier may be one or more entries. The entry list may contain one entry identifier, one or more execution conditions, and one conditional RRC reset information element. The entry list held by the terminal device is an entry If not included, the terminal device may maintain an empty list. Execution conditions may be any conditions that must be met to trigger the execution of conditional reset. Conditional RRC reset information required. The term "basic" refers to the mechanism for resetting the RRC connection that is applied when the aforementioned execution conditions are met. It may be a message. The message regarding the reconfiguration of the RRC connection is a candidate message. This message may be used to connect to GetSpCell.

[0168] A terminal device may evaluate the execution conditions of entries included in the entry list it holds. If the entry list held by the terminal device is empty or if it does not hold an entry list, it does not need to evaluate the execution conditions.

[0169] Conditional resetting is performed when a terminal device evaluates the execution conditions of an entry in the entry list it holds, and if one or more execution conditions are met, applies the conditional RRC resetting information element contained in the entry containing those execution conditions. Applying a conditional RRC reset information element means executing an RRC reset procedure using that conditional RRC reset information element.

[0170] If there are multiple entries that satisfy the execution conditions, the terminal device selects one entry from among the multiple entries that satisfy the execution conditions and performs a conditional RRC rerun of the selected entry. You may apply the configuration information elements.

[0171] The MAC entity of the terminal device is reset from a higher layer (e.g., RRC). When a MAC entity reset is requested, some or all of the following processes MR (A) through (N) may be performed. The MAC entity reset may simply be referred to as a MAC reset. When a partial reset of the MAC entity is requested from a higher layer (e.g., RRC), the MAC entity of a terminal device may perform some or all of the following processes MR (A) through (N). A partial reset of the terminal device may simply be called a partial MAC reset. The process performed in a partial MAC reset may be a process in which only a portion of the process performed in a MAC reset is performed. The process performed in a partial MAC reset may be a process in which some of the process performed in a MAC reset is not performed. The MAC entity of a terminal device may perform a MAC reset based on an instruction from T to the MAC entity of the terminal device. In addition to or instead of this, the MAC entity of a terminal device may perform a partial MAC reset based on an instruction from the RRC entity of the terminal device to the MAC entity of the terminal device.

[0172] (Processing MR) (A) Initialize the parameter Bj that the terminal device has set for each logical channel to 0. (B) All running timers except for some timers, including time adjustment timers Stop the timer. (C) Set the New Data Indicator (NDI) value to 0 for all uplink HARQ processes. ru. (D) If there is a random access procedure in progress, stop that random access procedure. do. (E) If explicitly signaled, 4 steps and 2 steps If there are any contention-free random access (CFRA) resources of type RA in the TEP, discard those resources. (F)Flush the buffer for Msg3. (G)Flush the MSGA buffer. (H) If there are any triggered Scheduling Request (SR) procedures, cancel those SR procedures. Do it. (I) If any Buffer Status Reporting (BSR) procedures have been triggered, cancel those BSR procedures. (J) If there is a triggered Power Headroom Reporting (PHR) procedure, that PHR procedure Cancel. (K) Flushes the soft buffers of all downlink HARQ processes. (L) If a Beam Failure Reporting (BFR) has been triggered, cancel that BFR. do. (M) If there is a temporary C-RNTI, then To lease (release). (N) Reset all BFI_COUNTERs.

[0173] The RRC connection re-establishment procedure will be described. The RRC connection re- establishment procedure may be a procedure for a terminal device to re-establish an RRC connection (RRC connection) based on an RRC re-establishment message. The RRC connection re-establishment procedure may also be referred to as an RRC re-establishment procedure. In the RRC connection re-establishment procedure, after the terminal device transmits an RRC re-establishment request message (RR CReestablishmentRequest) to the base station device (network: Network), based on receiving an RRC re-establishment message (RRCReestablishment) from the base station device, it may determine that the re-establishment of the RRC connection is successful and transmit an RRC re-establishment complete message (RRCReestablishmentComplete) to the base station device. The order of the terminal device determining that the re-establishment of the RRC connection is successful and transmitting an RRC re-establishment complete message to the base station device may be either way. Also, a terminal device in the RRC_CONNECTED state may start the procedure to continue the RRC connection. The re-establishment of the RRC connection is successful when the base station device finds a valid UE context and can verify (that it is the UE context held by the terminal device). Or, if the UE context cannot be obtained, the base station device may reply using an RRC setup message. When starting the RRC connection re-establishment procedure, the terminal device may perform some or all of the following processes (A) to (C) of RRI.

[0174] (Process RRI) (A) If running, stop timer T304. (B) If the terminal device has not set the attempt condition reset information element (attemptCondReconfig), perform some or all of the following processes (B-1) to (B-5). (C) Perform cell selection and if a suitable NR cell is selected, perform some or all of the following processes (C-1) to (C-2).

[0175] (B-1) Reset the MAC entity. (B-2) If the terminal device has configured it, release the SpCell configuration. (B-3) Suspend all radio bearers except SRB0. (B-4) If the terminal device has configured it, release one or more SCells of the MCG. (B-5) If the terminal device has MR-DC configured, perform an MR-DC release.

[0176] (C-1) Essential system information that is valid and up-to-date. To ensure that one possesses it. (C-2) If cell selection is triggered by detection of MCG radio link failure, MCG synchronization reset failure (i.e., expiration of timer T304), Furthermore, the terminal device has set the attempt condition reset information element (attemptCondReconfig), and The selected cell is included in the MCG conditional reset entry list (VarConditionalReconfig) If it is one of the candidate cells for the synchronized reconfiguration information element, the terminal device applies the conditional RRC reconfiguration information element (condRRCReconfig) associated with the selected cell and performs part or all of the above RRP process; otherwise, it performs part or all of the following processes (C-2-1) to (C-2-4); and if the terminal device has set an attempt conditional reconfiguration information element (attemptCondReconfig), it performs part or all of the following processes (C-2-5) to (C-2-7). The department will be implemented.

[0177] (C-2-1) Apply the values ​​of default L1 parameters other than those provided in SIB1 as the values ​​specified in the corresponding physical layer specification. (C-2-2) Apply the default MAC cell group configuration. (C-2-3) Apply the CCCH settings. (C-2-4) Start sending the RRC re-establishment request message.

[0178] (C-2-5) Reset the MAC entity. (C-2-6) If the terminal device has configured it, release the SpCell settings. . (C-2-7) If the terminal device is configured, release one or more SCells of the MCG To release.

[0179] The aforementioned timer T304 is triggered when the terminal device resets the RRC connection, which includes a synchronized reset information element. The process may start upon receiving a message regarding the settings and stop upon successful completion of the random access procedure on the SpCell corresponding to the synchronized reconfiguration information element. Furthermore, if the timer T304 described above expires, the terminal device may perform the RRC connection re-establishment procedure. It may be started. In addition to or instead of the above, the timer T304 shall notify that the LTM cell switching process described below has been triggered from a lower layer (such as the MAC layer), and / or It may start based on the execution (performance) of the LTM cell switching process after cell selection. In addition to or instead of this, the timer T304 described above may stop for the same HARQ process based on the reception of a PDCCH addressed to C-RNTI after the initial uplink transmission, in the case of an LTM cell switching that does not involve the execution of a random access procedure.

[0180] Next, we will explain the Central Unit (CU) and the Distributed Unit (DU). The Central Unit may be a logical node that hosts the RRC layer, SDAP layer, and PDCP layer of the base station equipment. The Distributed Unit is the RRC layer of the base station equipment. This may refer to a logical node that hosts the MAC layer and the PHY layer. The aggregation unit may control the operation of one or more distributed units. A unit may support one or more cells. A single cell may be supported by only one distributed unit. Furthermore, some of the functions of an aggregated unit may be implemented in a distributed unit. Also, some of the functions of a distributed unit may be implemented in an aggregated unit.

[0181] Next, Layer 1 / Layer 2 triggered mobility (L1 / L2-triggered mobility: LTM) in this embodiment will be described.

[0182] LTM refers to the base station equipment receiving one or more L1 measurement reports from the terminal equipment. The procedure may involve the base station device switching the serving cell of the terminal device by a cell switching command signaled via MAC CE. The cell switching command is prepared in advance by the base station device and provided to the terminal device via RRC signaling. Specify the LTM candidate setting. The terminal device targets according to the cell switching command. You may apply the default settings.

[0183] For example, the RRC layer of the terminal device includes an RRC signaling that includes one or more LTM candidate settings. The terminal device may receive a signal from the base station device. The RRC layer of the terminal device receives the signal. It may store multiple LTM candidate information elements. Also, the MAC layer of the terminal device may receive cell switching commands from the base station device via MAC CE. The RRC layer of the terminal device The target settings may be applied according to the cell switching command. The cell switching command may include a target setting identifier indicating the target settings. The MAC layer of the terminal device that receives the cell switching command may notify the RRC layer of the terminal device (a layer higher than the MAC layer) that the LTM cell switching procedure has been triggered and the target setting identifier. When the RRC layer receives a notification from the MAC layer (a layer lower than the RRC layer), it triggers a cell switching procedure. The target identifier may be used to identify one or more LTM candidate information elements One of the LTM candidate settings may be applied. The target setting identifier may be an identifier used to identify a certain LTM candidate setting. The target setting may be an LTM candidate setting indicated by the target setting identifier. The cell switching command is the terminal The command (MAC CE) may be a command that triggers the device to perform an LTM cell switching procedure. The NET identifier may be associated with the LTM candidate identifier described later.

[0184] In LTM, the base station equipment receives the measurement report provided by the terminal equipment. The target setting may be determined based on this. The measurement report is transmitted from the terminal device via PUSCH. The transmitted CSI report may be a CSI report transmitted via PUCCH from the terminal device. In addition to or instead of the CSI report, the measurement report may be a CSI report transmitted via PUCCH from the terminal device. It may be a measurement report message. In addition to or instead of the measurement report, the measurement report information transmitted as MAC CE from the terminal device may be measurement report information. The measurement report may also be other information.

[0185] Furthermore, MAC CE can be rephrased as Layer 2 signaling. Also, the above measurements are, Layer 1 (PHY layer), Layer 2 (MAC layer), and / or Layer 3 (RRC layer) This may be done. Furthermore, the above measurement report may be performed by Layer 1 (PHY layer), Layer 2 (MAC layer), and / or Layer 3 (RRC layer).

[0186] The aforementioned cell switching command may be signaled by MAC CE. The MAC CE is LTM It may also be called the cell switching command MAC CE, and can be used interchangeably with the term cell switching command. In other words, sending and receiving cell switching commands is equivalent to LTM cells. This can be rephrased as sending or receiving a MAC CE switching command. The cell switching command may include multiple fields, and these multiple fields may include the following information, as well as other information. (a) Target setting identifier corresponding to LTM candidate identifier (b) TA command (c) Identifier indicating the TCI state in the SpCell (target cell) of the target setting. (d) Identifying the uplink TCI state in the target cell (SpCell) for target setting. Besshi (e) Information indicating the existence of CFRA resources (f) Information indicating the uplink carrier that transmits the CFRA PRACH. (g) Preamble index of CFRA resources (h) Show the SSB used to determine the RACH occasion for CFRA PRACH transmission. information (i) Information indicating a RACH occasion related to the SSB indicated by the information indicating the SSB

[0187] One or more LTM candidate information elements may be included in the LTM setting, and the LTM setting may be included in the RRC reset message. The RRC reset message may be RRC signaling. The LTM candidate information elements include an LTM candidate identifier, an LTM candidate cell identifier, an LTM-SSB setting, and LTM Candidate setting, LTM full setting indicator, early UL synchronization setting, early SUL synchronization setting, LTM reset judgment indicator The LTM candidate identifier may include B, LTM-UE criterion TA measurement identifier B, and other information. The child is an identifier used to identify the LTM candidate setting and the LTM candidate information element, and may be an information element named ltm-CandidateId. The LTM candidate cell identifier is an identifier indicating the physical cell identifier (PCI) of the SpCell of the setting included in the LTM candidate setting, and may be an information element named ltm-CandidatePCI. The LTM-SSB setting indicates the setting of the SS / PBCH block used for L1 measurement and TCI status, and may be an information element named ltm-SSB-Config. It may be an element. The aforementioned LTM candidate setting is an RRC setting used to set LTM candidate cells. The setting includes a fixed value and may be an information element named ltm-CandidateConfig. The LTM complete setting indicator indicates whether the RRC reconfiguration included in the LTM candidate setting is a complete setting and may be an information element named ltm-ConfigComplete. The early UL synchronization setting is a setting used to execute the early UL synchronization procedure on the UL carrier and may be an information element named ltm-EarlyUL-SyncConfig. The early SUL synchronization setting is a setting used to execute the early UL synchronization procedure on the SUL carrier and may be an information element named ltm-EarlyUL-SyncConfigSUL It may be an information element. The LTM reset judgment identifier B is an identifier used to determine whether or not an L2 reset is performed when the LTM cell switching procedure is triggered for an LTM candidate cell, and may be an information element named ltm-NoResetID. The LTM-UE reference TA measurement Identifier B is an identifier used to determine whether or not to perform UE-based TA measurement on an LTM candidate cell, and may be an information element named ltm-UE-MeasuredTA-ID.

[0188] The LTM configuration may include LTM reference settings, an LTM candidate setting release list, an LTM candidate setting addition / modification list, an LTM reset decision identifier A, an LTM-UE criterion TA measurement identifier A, an LTM-CSI resource setting release list, an LTM-CSI resource setting addition / modification list, and other information. The LTM reference settings are settings used to configure reference settings for LTM, and may be an information element named ltm-ReferenceConfiguration. The LTM candidate setting release list is a list indicating LTM candidate settings to be released, and may be an information element named ltm-CandidateToReleaseList. It may exist. The LTM candidate setting release list contains the LTM candidate identification corresponding to the LTM candidate setting to be released. It may also be a list of children. The LTM candidate settings add / modify list is added and / or modified. The LTM CandidateToAddModList is a list of LTM candidate settings, which may be an information element named ltm-CandidateToAddModList. The LTM Reset Decision Identifier A is an identifier used to determine whether an L2 reset is performed when an LTM cell switching procedure is triggered for an LTM candidate cell, which may be an information element named ltm-ServingCellNoResetID. The LTM-UE Criteria TA Measurement Identifier A is an identifier used to determine whether or not to perform a UE criteria TA measurement for an LTM candidate cell, which may be an information element named ltm-ServingCellUE-MeasuredTA-ID. The LTM-CSI Resource Setting Release List is a list indicating the LTM CSI resource settings to be released, which may be an information element named ltm-CSI-ResourceConfigToReleaseList. The LTM-CSI Resource Setting Release List may be a list of LTM-CSI resource setting identifiers corresponding to the LTM-CSI resource settings to be released. The LTM-CSI Resource Setting Addition and Modification List is a list of additions and also This is a list of LTM-CSI resource settings to be modified, and may be an information element named ltm-CSI-ResourceConfigToAddModList. An LTM-CSI resource setting may be a setting that defines a group of one or more CSI resources for one or more LTM candidate settings. Each LTM-CSI resource setting may be identified by an LTM-CSI resource setting identifier.

[0189] When a terminal device receives an RRC reconfiguration message that includes the LTM setting, it uses the received LTM setting as a basis. The following actions may be performed: (A) If the received LTM setting includes LTM reset decision identifier A, and the current UE variable-LTM reset decision identifier includes LTM reset decision identifier A, the value of LTM reset decision identifier A included in the UE variable-LTM reset decision identifier may be replaced with the received LTM reset decision identifier A; and if the received LTM setting includes LTM reset decision identifier A, and the current UE variable-LTM reset decision identifier does not include LTM reset decision identifier A, the received LTM reset decision identifier A may be replaced with the UE variable-LTM reset (B) If the received LTM setting includes LTM-UE criterion TA measurement identifier A, and the current UE variable -LTM -UE criterion TA measurement identifier is LTM-UE criterion TA measurement identifier A If it includes, the value of LTM-UE reference TA measurement identifier A included in the UE variable-LTM-UE reference TA measurement identifier may be replaced with the received LTM-UE reference TA measurement identifier A, and the received LTM setting If the LTM-UE reference TA measurement identifier A is included, and the current UE variable-LTM-UE reference TA measurement identifier A is not included, the received LTM-UE reference TA measurement identifier A may be stored in the UE variable-LTM-UE reference TA measurement identifier. (C) If the received LTM setting includes an LTM candidate setting release list, the operation of the terminal device that received the LTM candidate setting release list described below shall be (D) If the received LTM setting includes an LTM candidate setting addition / modification list, the following steps are permitted. The terminal device that received the aforementioned LTM candidate setting addition / modification list may perform the operation. The variable -LTM reset determination identifier determines whether an L2 reset is required during the LTM cell switching procedure. It may be used to store the identifier of a serving cell that serves as a criterion for the terminal device to make a determination, and may be a UE variable named VarLTM-ServingCellNoResetID. The UE variable-LTM-UE criterion TA measurement identifier serves as a criterion for the terminal device to determine whether or not a UE criterion TA measurement is required. This variable may be used to store the identifier of a serving cell and may be a UE variable named VarLTM-ServingCellUE-MeasuredTA-ID. Note that a UE variable may be a variable stored internally within the terminal device.

[0190] When a terminal device receives the LTM candidate setting addition / modification list, it performs the following processing for each LTM candidate identifier included in the LTM candidate setting addition / modification list: (A) When it determines that the current terminal device setting includes an LTM candidate information element that contains an LTM candidate identifier with the same value as the LTM candidate identifier: In other words, the LTM candidate information element (included in the terminal device settings) may be reconfigured according to the received LTM candidate information element, and if not (i.e., if it is not determined that the current terminal device settings include an LTM candidate information element containing an LTM candidate identifier with the same value as the LTM candidate identifier), the received LTM candidate information element may be added to the terminal device settings. (B) The above The LTM candidate information element, which includes the received LTM candidate identifier, includes the LTM-UE reference TA measurement identifier B. If so, further, (C) if it is determined that the value of the LTM-UE standard TA measurement identifier B is equal to the value of the LTM-UE standard TA measurement identifier A included in the UE variable-LTM-UE standard TA measurement identifier, it is notified to the lower layer that a UE standard TA measurement has been set for this LTM candidate information element, and if not, ( That is, the value of the LTM-UE reference TA measurement identifier B and the UE variable included in the LTM-UE reference TA measurement identifier If the value of the LTM-UE standard TA measurement identifier A is not determined to be equal, this LTM candidate information element Therefore, it is possible to inform the lower layer that UE-based TA measurement is not set. Note that the LTM candidate information element including the received LTM candidate identifier does not include the LTM-UE-based TA measurement identifier B. If not, the lower layer will indicate that the UE criterion TA measurement is not set for this LTM candidate information element. It's okay to inform them.

[0191] Upon receiving the LTM candidate setting release list, the terminal device performs the following processing on each LTM candidate identifier included in the LTM candidate setting release list: (A) It may delete the LTM candidate information element corresponding to the LTM candidate identifier.

[0192] Furthermore, if NR-DC is configured on the terminal device, the terminal device can receive two independent LTM settings. That is, (1) the MCG is included in the RRC reset message received via SRB1. (2) The associated LTM settings and the RRC received via SRB3 or SRB1. The terminal device can receive two LTM settings associated with the SCG, which are included in the RRC reconfiguration message embedded in the configuration message. If the terminal device receives two independent LTM settings, the terminal device may maintain the two independent LTM settings, and the terminal device may receive two Independent UE variable-LTM-UE reference TA measurement identifiers may be maintained, and the terminal device may maintain two independent The UE variable-LTM reset decision identifier may be maintained, and the terminal device may perform all procedures independently for each LTM setting, UE variable-LTM-UE reference TA measurement identifier, and UE variable-LTM reset decision identifier unless otherwise explicitly instructed.

[0193] In LTM, some or all of the following mobility scenarios (A) through (J) are supported. It is acceptable to include other mobility scenarios, and other mobility scenarios may also be supported. (A) Mobility within base station distributed units (intra-gNB-DU) (B) Mobility between base station distribution units within a base station aggregation unit (intra-gNB-CU inter-gNB-DU) (C) Inter-frequency mobility (including mobility to inter-frequency cells that are not currently serving cells) (D) Intra-frequency mobility (E) PCell modification in terminal devices where CA and DC are not configured. (F) Changing PCell and one or more SCells in terminal devices where CA is configured. (G) Changes to PCell and MCG SCell(s) in terminal devices where DC is configured, changes to PSCell and SCG SCell(s) without MN involvement (H) Inter-cell beam management (Layer 1 / Layer 2 trigger mobilization) (This is not considered a prerequisite for using T.) (I) Mobility between base station aggregation units (inter-gNB-CU) (J) Conditional mobility

[0194] This section describes random access procedures initiated by a PDCCH order. A random access procedure initiated by a PDCCH order is a random access procedure initiated by a PDCCH order. The identifier of the random access preamble may be a random access procedure that includes a procedure explicitly provided by the PDCCH order (PDCCH). The identifier of the random access preamble may be, for example, a 6-bit identifier named ra-PreambleIndex. The identifier of the access preamble may be indicated by the RACH-ConfigDedicated information element described above. Furthermore, the PDCCH order is, for example, a single DCI format named 1_0. It is a PDCCH that sends a DCI to schedule a PDSCH within a downlink cell. i. In addition to or instead of the PDCCH order and / or the DCI order Mat1_0 is PRACH if the values ​​of all identifiers in the random access preamble are not 0. It may include an identifier for the SS / PBCH (SSB) used to determine the RACH occasion for transmission (PRACH occasion) (SS / PBCH block index field), and / or an identifier for the PRACH mask (PRACH mask index field) that indicates the RACH occasion associated with the SS / PBCH. Note that in the following description, "random access preamble" and "PRACH" and "PRACH" can be used interchangeably.

[0195] On a serving cell, a random access procedure was initiated in PDCCH order. In this case, the terminal device may send PRACH on this serving cell. For example, random When an access procedure is initiated on the PCell by a PDCCH order, the terminal device will enter this PCell You may send PRACH above. In addition to or instead of that, for example, random accessories If a procedure is initiated on a SCell by a PDCCH order, the terminal device may send a PRACH on that SCell. Note that if a random access procedure is initiated on a serving cell by a PDCCH order, The phrase "when initiated by an order" can be rephrased as "when a terminal device receives a PDCCH (PDCCH order) in a serving cell that explicitly provides an identifier for a random access preamble," etc.

[0196] In a random access procedure of type 4 steps, the MAC entity of the terminal device is defined as the identifier of the random access preamble if it is explicitly provided by the PDCCH. If the identifier values ​​of the random access preamble are not all zero, then (a) and / or (b) below may be performed. (a) The preamble identifier (PREAMBLE_INDEX) is signaled to the random array Set this value to the identifier in the access preamble. (b) Select the SSB signaled by the PDCCH.

[0197] In a random access procedure with RA type 4 steps, the MAC entity of the terminal device is associated with the PRACH occasion in which the random access preamble is sent. The random access identifier (RA-RNTI) is computed, and the selected PRACH occasion The terminal device may instruct the PHY layer to transmit a random access preamble using the corresponding random access identifier (RA-RNTI) and / or the preamble identifier. The PHY layer, when a request is made from a higher layer (such as a MAC entity) to send a random access preamble, sends a PRACH within the selected PRACH occasion. This may be done. In this case, the time between the last symbol that receives the PDCCH order and the first symbol that transmits the PRACH may be longer than N_{T,2} + Δ_BWPSwitching + Δ_Delay + T_switch milliseconds (msec), or equal to N_T,2 + Δ_BWPSwitching + Δ_Delay + T_switch milliseconds, where N_{T,2} may be the time interval of N_2 symbols corresponding to the PUSCH preparation time. In addition to or instead of Δ_BWPSwitching may be the delay that occurs during BWP switching, and Active UL BWP If it is not changed, the value of Δ_BWPSwitching may be 0. In addition to or instead of that, the value of Δ_Delay is for the frequency range 410 MHz - 7125 MHz (Frequency range 1: FR1) It may be 0.5 milliseconds (msec) in the frequency range 24250 MHz - 52600 MHz (Frequency range 2: FR2, or Frequency range 2-1: FR2-1). In addition to or instead of the above, T_switch may be the switching gap duration.

[0198] Once a random access preamble is sent, regardless of the potential occurrence of a measurement gap, the MAC entity of the terminal device will, in the first PDCCH occasion, start the random access response window (ra-ResponseWindow) set by the RRC entity of the terminal device in the RACH-ConfigCommon information element, and the random access response window will run... While doing so, one or more random access identifiers (RA-RNTIs) are identified. You may monitor the PDCCH of the SpCell for access responses (Random Access Response: RAR). The MAC entity of the terminal device, if a valid downlink assignment is randomly accessed If the PDCCH for the S identifier (RA-RNTI) is received, the received transport block (TB) is successfully decoded, and the received random access response contains a MAC subPDU with a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX, then the receipt of this random access response is successful. It can be considered a success.

[0199] The MAC entity of a terminal device that considers the receipt of a random access response to be successful is If the trusted random access response contains only MAC subPDUs with RAPID, this random The access procedure is considered to have been completed successfully, and an acknowledgment for the SI request is received, which is indicated to the higher layer (RRC layer, etc.). Otherwise (received) If the random access response includes a MAC subPDU and MAC RAR with RAPID, then run For a serving cell that has sent a dam access preamble, some or all of the following actions (a) through (c) may be applied. Note that the above MAC RAR is subject to the timing described below. Timing Advance Command (TAC), uplink grant, and / Alternatively, it may include some or all of the Temporary C-RNTI. (a) Process the timing advance command described below. (b) The base station equipment notifies lower layers (PHY layer, etc.) of the parameter (preambleReceivedTargetPower) for the received power (target power) of the random access preamble, and the amount of power ramping applied when the random access preamble was last transmitted. (c) Random access for SCell on an uplink carrier where the terminal device has not set terminal device-specific PUSCH parameters (UE-specific PUSCH parameter: PUSCH-Config) If the procedure is performed, the received uplink grant will be ignored. Otherwise, the received uplink grant value is processed, and that value is notified to the lower layer (PHY layer, etc.).

[0200] The terminal device may adjust the transmission timing of the uplink. For example, the terminal device may adjust the timing based on the receipt of a Timing Advance Command (TAC) MAC CE. The transmission timing of the uplink may be adjusted. The serving settings configured by the terminal device in RRC Within the group, the terminal device uses the same timing reference cell and the same timing advance value for the cell where it sets the uplink. A group of Bing Cells may be referred to as a Timing Advance Group (TAG). Furthermore, a TAG containing a MAC entity SpCell may be referred to as a Primary Timing Advance Group (PTAG). TAGs other than the PTAG may be referred to as Secondary Timing Advance Groups. It may be referenced as p:STAG). One or more of the aforementioned TAGs may be configured independently for each cell group.

[0201] For example, upon receiving a TAC MAC CE for a given TAG, the terminal device may adjust the uplink transmission timing for PUSCH, SRS, and / or PUCCH transmissions in some or all serving cells in that TAG. The terminal device may adjust the uplink transmission timing so that T_TA is earlier than the timing at the beginning of the downlink frame of the same frame number. The terminal device may calculate the timing advance value T_TA based on N_TA and TA offset (N_{TA, offset}). The terminal device may use N_TA to calculate the information contained in the TAC MAC CE. It may be set based on the report. The terminal device sets the TA offset (N_{TA,offset}) to serve The settings may be determined based on the RRC parameter (n-TimingAdvanceOffset) set by the terminal device for each cell. The terminal device sets N_{TA,offset} for each serving cell, but serving cells with the same TAG may have the same value for N_{TA,offset}.

[0202] Furthermore, in Dual Connectivity, cells in each cell group may belong to different TAGs. That is, the PTAG of the MCG and the PTAG of the SCG may be independent and different TAGs.

[0203] The RRC entity of a terminal device may set the value of the timeAlignmentTimer to MAC in order to maintain the time alignment of the uplink. The timeAlignmentTimer is the uplink of the serving cell belonging to the TAG associated with the timeAlignmentTimer. It is used to control the time at which MAC entities consider the timing to be adjusted. Good. The terminal device receives the value of the time adjustment timer from the base station device via RRC signaling. You may use this to set it.

[0204] The MAC entity of the terminal device has received a Timing Advance Command (TAC) MAC CE and maintains the N_TA of the TAG indicated by the TAC MAC CE. Based on this, TAC may be applied to the TAG specified by the TAC MAC CE. Also, based on the fact that the terminal device has received the Timing Advance Command (TAC) MAC CE and that the N_TA of the TAG specified by the TAC MAC CE is maintained, the MAC may start the timeAlignmentTimer associated with the TAG specified by the TAC MAC CE, or restart it if it is already running.

[0205] The MAC entity of a terminal device receives a Timing Advance Command (TAC) within a Random Access Response (RAR) message for a serving cell belonging to a certain TAG, and the random access preamble is selected from the contention-based random access preamble. Based on the fact that it was not selected by T (for example, the identifier for the random access preamble was explicitly provided by the PDCCH order), apply TAC to this TAG. In addition to or instead of the above, the MAC entity of a terminal device may start, or restart, the timeAlignmentTimer associated with a TAG, based on the fact that it has received a Timing Advance Command (TAC) in a Random Access Response (RAR) message for a serving cell belonging to a TAG, and that the random access preamble was not selected by the MAC entity from among the contention-based random access preambles.

[0206] When the MAC entity of the terminal device expires, the time adjustment timer associated with the PTAG will be deleted. You may perform some or all of the following processes (A) through (G). (A) Flux all HARQ buffers for all serving cells (within a cell group) To rush. (B) If the terminal device has set PUCCH, it notifies the RRC that it has released PUCCH for all serving cells. (C) If the terminal device has SRS configured, SRS for all serving cells Notify RRC that the release has been made. (D) Clear all configured downlink assignments and configured uplink grants. (E) Clear all pushes for semi-persistent CSI reporting. (F) All time adjustment timers, including STAG, are considered to have expired. (G) Maintain N_TA for all TAGs.

[0207] When the MAC entity of the terminal device expires, the time adjustment timer associated with STAG will be used. For all serving cells belonging to this STAG, some or all of the following processes (A) through (F) may be performed. (A) Flush all HARQ buffers. (B) If the terminal device has set PUCCH, it notifies the RRC that it has released PUCCH. (C) If the terminal device has SRS configured, it notifies RRC that it has released SRS. (D) Clear all configured downlink assignments and configured uplink grants. (E) Clear all pushes for semi-persistent CSI reporting. (F) Maintain the N_TA of this TAG.

[0208] The terminal device will not perform any uplink transmissions in serving cells other than the transmission of the random access preamble in the SpCell and the transmission of the MSGA (in 2-step RACH) based on the fact that one or more time adjustment timers associated with the PTAG are not running. It is acceptable to conclude that.

[0209] Based on the above description, various embodiments will be explained. Note that any processes omitted in the following description may be replaced by the processes described above.

[0210] Figure 5 is a block diagram showing the configuration of the terminal device (UE122) in this embodiment. Note that, to avoid making the explanation complicated, Figure 5 shows only the main components closely related to this embodiment. To show.

[0211] The UE122 shown in Figure 5 consists of a receiving unit 500 that receives control information (DCI, MAC CE, RRC signaling, etc.) from the base station equipment, and a processing unit that performs processing according to the parameters contained in the received control information. It consists of a unit 502 and a transmission unit 504 that transmits control information (UCI, RRC signaling, etc.) to a base station device. The above-mentioned base station device may be an eNB102 or a gNB108. Furthermore, the processing unit 502 has various layers (for example, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, etc.) The functions of the physical layer (and NAS layer) may be included in some or all of them. That is, the processing unit 502 includes physical layer processing The receiver 500 may include some or all of the processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. In addition to or instead of these, the receiver 500 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the receiver 500 may include some or all of the physical layer receiver, MAC layer receiver, RLC layer receiver, PDCP layer receiver, SDAP layer receiver, RRC layer receiver, and NAS layer receiver.

[0212] Figure 6 is a block diagram showing the configuration of the base station equipment in this embodiment. To avoid sloppiness, Figure 6 shows only the main components closely related to this embodiment. As shown above, the base station device may be eNB102 or gNB108.

[0213] The base station device shown in Figure 6 consists of a transmitting unit 600 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to the UE 122, a processing unit 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to the UE 122, causing the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Furthermore, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP layer processing unit, RRC layer processing unit, and NAS layer processing unit. It may include some or all of the above. In addition to or instead of the above, the transmitting unit 600 may include various The transmitter 600 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the transmitter 600 may include some of the functions of the physical layer transmitter, MAC layer transmitter, RLC layer transmitter, PDCP layer transmitter, SDAP layer transmitter, RRC layer transmitter, and NAS layer transmitter. Or it may include all of them.

[0214] Conditional LTM cell switching is described below. Conditional LTM cell switching may be performed on candidate target SpCells that meet certain execution conditions. UE122 receives one or more from the base station equipment. Upon receiving RRC signaling that includes conditional LTM candidate information elements, the UE122 These are candidates associated with the conditional LTM candidate information elements received from the base station device. Set the auxiliary target SpCell. The candidate target SpCell is a conditional LTM cell switch. It may also be a candidate for an LTM target cell in the LTM. The conditional LTM candidate information element is LTM The candidate identifier may be managed by an identifier such as a candidate identifier. The UE122 sets the candidate identifier - The state of the GetSpCell may be evaluated. The UE122 performs the evaluation and satisfies the execution conditions. Trigger the LTM cell switching procedure for one or more candidate target SpCells. Good. The UE122 relates to one or more candidate target SpCells that satisfy the execution conditions. One of the conditional LTM candidate setting information elements included in the linked conditional LTM candidate information elements may be applied. The conditional LTM candidate information elements and the conditional LTM candidate setting information elements may be information elements having the same information as the aforementioned LTM candidate information elements and LTM candidate setting information elements, or in addition to or instead of them, they may be the same information elements. The conditional LTM candidate information elements may be replaced with LTM candidate information elements, and the conditional LTM candidate setting information elements may be replaced with LTM candidate setting information elements. The execution condition may be associated with the candidate target SpCell, or the conditional LTM candidate It may be associated with an information element.

[0215] The UE122 may evaluate whether the execution conditions are met in the evaluation. Or multiple execution conditions are associated with one or more conditional LTM candidate information elements. The execution conditions may be set in the UE122 by RRC signaling, or by information elements included in the RRC signaling that includes one or more conditional LTM candidate information elements. The execution conditions may be, for example, one of the following conditions or Multiple conditions are acceptable. (C-1) The beam measurement parameters associated with the candidate target SpCell are currently being served. The value is greater than the value obtained by adding an offset to the measurement parameters of the beam that makes up the SpCell. (C-2) The measurement parameters of the beam associated with the candidate target SpCell are greater than the threshold. (C-3) The measurement parameters of the beams constituting the current serving cell (SpCell) are greater than the first threshold. The measurement parameters of the beam associated with the candidate target SpCell are small and greater than the second threshold. (C-4) The measurement items of the candidate target SpCell are the same as the measurement items of the current serving cell (SpCell). The value is greater than the value with the offset applied to the eye. (C-5) The measurement item of the candidate target SpCell is greater than the threshold. (C-6) The measurement parameters of the current serving cell (SpCell) are smaller than the first threshold, and the candidate The measurement value in getSpCell is greater than the second threshold.

[0216] In addition to the conditions mentioned above, other conditions may also be considered. For example, the execution condition may be that the condition (Cn) [n=1,2,…,6] is satisfied for a certain period of time. The setting may be included in the RRC signaling as an execution condition. The period may be set in the UE122 via an information element named TimeToTrigger, or other named information The UE122 may be set via the reporting element. In addition to or instead of that, for example, For example, the measurement items of the beam (Cn)[n=1,2,3] may be the measurement items of a single beam or multiple beams.

[0217] The aforementioned measurement items may be, for example, Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Interference-and-Noise Ratio (SINR), or other indicators. The UE122 is SSB, CSI-RS (Channel State The beam parameters may be measured using an Information-Reference Signal (I-S) or a signal with a different name. The beam constituting the current serving cell (SpCell) may also be referred to as the serving beam or the current beam. The UE122 is, Multiple instances of a single type of signal associated with a single cell may be used to measure the measurement parameters of that cell. The single type of signal may be SSB, CSI-RS, or any other signal. The network (base station equipment) sets which signal to use in the UE122. It may also be used.

[0218] An example of the processing of the terminal device (UE122) in this embodiment will be explained using Figure 9. In this embodiment, the processing unit 502 of UE122 is configured to perform RRC processing, PDCP processing, RLC processing, MAC processing, and PHY processing. It may include a PHY processing unit.

[0219] Figure 9 shows an example of the processing of UE122 in this embodiment. The processing unit 502 of UE122 makes a conditional judgment (step S900) and operates based on the judgment (step S902).

[0220] The UE122 may receive a Timing Advance Command (TA command) associated with an LTM candidate information element from the base station device via MAC CE. The LTM candidate information element is a candidate target It may be associated with a target identifier. The MAC CE may include the candidate target identifier and the TA command. The UE122 may store the received TA command. The candidate target identifier may be replaced with other information that can identify the candidate target SpCell to which the TA command applies. The TA command controls the amount of timing adjustment that the UE122 must apply when performing a conditional LTM cell switchover. An index value T_A used for this purpose may be shown. The index value T_A may be a value used for Timing Advance and may be used to calculate the value of N_TA.

[0221] Each of the aforementioned UE122s is associated one-to-one with one or more candidate target SpCells. It may manage one or more synchronization timers. The UE122 is located in front of the base station equipment. The UE122 may receive RRC signaling that includes settings for the synchronization timer. The UE122 may set the initial value of the synchronization timer according to the settings for the synchronization timer. In addition or alternatively, it may set a default value for the initial value of the synchronization timer. In addition or alternatively, it may set the initial value of the synchronization timer according to MAC CE received from the base station device. The settings for the synchronization timer may be one or more ( It may be associated with a conditional LTM candidate information element. The initial value of the synchronization timer is different depending on one or more associated (conditional) LTM candidate information elements. This may be a value or a common value. Furthermore, each of the one or more synchronization timers may be associated with one or more (conditional) LTM candidate information elements.

[0222] Based on the fact that UE122 has received the MAC CE including the TA command, the TA command The synchronization timer associated with the candidate target SpCell associated with the UE122 may be started or restarted. While the synchronization timer is running, the UE122 may determine that it is UL synchronized with the candidate target SpCell. The conditional LTM cell switching procedure is If triggered, the UE122 will, based on the fact that at least the synchronous timer is operating, It is acceptable to conclude that a RACH-less LTM cell switchover is ongoing. Based on the expiration of the synchronization timer, the UE122 will send the candidate target SpCell Alternatively, it may be determined that UL synchronization is not occurring. In addition or in lieu thereof, based on the expiration of the synchronization timer, the UE122 may be associated with the synchronization timer. The UE122 may determine that the TAC (or index value T_A) associated with the auxiliary target SpCell is invalid, or it may release the TAC. If the conditional LTM cell switching procedure is triggered, the UE122 may initiate a random access procedure to the LTM target cell based on at least the fact that the synchronization timer is not running. The LTM target cell is In the conditional LTM cell switching procedure, the LTM target cell may be a cell that is subject to LTM cell switching. The LTM target cell may also be a candidate target SpCell that satisfies the execution conditions. i. If multiple candidate target SpCells satisfy the execution conditions, one selected candidate target SpCell may be chosen from among the multiple candidate target SpCells. The LTM -Get cell may also be called selected cell. Also, the above execution clause Candidate target SpCells that satisfy the criteria may be referred to as triggered cells.

[0223] Furthermore, based on the triggering of the conditional LTM cell switching procedure, the UE122 operates one or more timers, excluding the synchronous timer associated with the LTM target cell. The synchronous timer may be stopped. In addition to or instead of the above, the UE may stop the synchronous timer associated with the LTM target cell based on the triggering of the conditional LTM cell switching procedure.

[0224] The UE122 may, in the conditional LTM cell switching procedure, apply the index value T_A indicated by the TA command to the PTAG of the LTM target cell. In addition, it may set the value of the synchronization timer associated with the LTM target cell to the TA timer (Timer Alignment Timer) associated with the PTAG and start the TA timer. In addition or alternatively, it may set the value of the TA timer associated with the PTAG based on the setting of the TAG included in the LTM candidate setting associated with the LTM target cell and start the TA timer. In addition or alternatively, it may compare the value of the synchronization timer associated with the LTM target cell with the value of the TA timer of the PTAG included in the setting of the TAG included in the LTM candidate setting associated with the LTM target cell, set the smaller value to the TA timer associated with the PTAG, and start the TA timer. In addition, or instead, the value of the synchronization timer associated with the LTM target cell. And, included in the TAG settings included in the LTM candidate settings associated with the LTM target cell The value of the TA timer associated with the PTAG may be compared with the value of the TA timer associated with the PTAG, and the larger value may be set to the TA timer associated with the PTAG, and the TA timer may be started.

[0225] The UE122 may perform a MAC reset in the LTM cell switching procedure. The MAC layer processing unit of the UE122 performs the MAC reset in accordance with a request from the upper layer (RRC layer processing unit). Alternatively, the UE122, in the MAC reset, one or more of the LTM targets You may stop one or more operating timers, excluding one or more synchronous timers associated with the t cell.

[0226] The UE122 performs an LTM cell switching procedure without RACH. Based on this, the RRC reset completion message includes information indicating the value of the synchronization timer associated with the LTM target cell and sends it to the base station equipment providing the LTM target cell. You may believe. In addition to or instead of the above, the UE122 is one or more candidates The RRC reset completion message contains information indicating the value of the synchronization timer associated with the target SpCell. The message may be included in the page and transmitted to the base station equipment providing the LTM target cell. The UE122 may also transmit the RRC reconfiguration completion message via SRB1 or SRB3.

[0227] The base station device may be the base station device that provides the source cell when the UE122 performs the conditional LTM cell switching. The base station device that provides the source cell may be called the source gNB. The base station device that provides the target cell may be called the target It may also be called a gNB. If the CU providing the source cell and the CU providing the target cell are the same, then the source gNB and the target gNB may both be the base station device. The source gNB is a unit held by the UE122 with respect to the target gNB. Information relating to one or more synchronous timers may be provided. The information relating to one or more synchronous timers may, for example, be information indicating the remaining time of an active synchronous timer, or in addition to or instead be information identifying a candidate target SpCell associated with an active synchronous timer, or in addition to or instead be information identifying the UE122.

[0228] The UE122 has set a UE-based TA (Timing Advance) measurement for the LTM target cell, and based on the fact that it has successfully measured the TA (Timing Advance) of the LTM target cell, it sets the value of the TA timer associated with the PTAG based on the setting of the TAG included in the LTM candidate setting associated with the LTM target cell. The TA timer may be started. In addition to or instead of the UE122, Based on the fact that the synchronization timer for the LTM target cell is operating, the synchronization The index value T_A indicated by the TA command associated with the timer may be applied to the PTAG of the LTM target cell. In addition to or instead of this, the UE122 may perform a UE-based TA (Timing Advance) measurement on the LTM target cell. Not determined, or the Timing Advance (TA) of the LTM target cell has been successfully measured. Based on the fact that it has not been done, the value of the synchronization timer associated with the LTM target cell The value of the TA timer associated with the PTAG may be set, and the TA timer may be started.

[0229] The embodiments described above may be combined with each other. Furthermore, although the operation in the conditional LTM cell switching procedure was described in the examples of the embodiments described above, the procedure is not limited to that, for example, This may also be an operation in the normal LTM cell switching procedure, that is, a procedure in which cell switching is performed based on the receipt of an LTM cell switching command (MAC CE) from the base station equipment. In other words, the conditional LTM cell switching procedure and the LTM cell switching procedure may be interchangeable. Furthermore, in each of the embodiments described above, applying the LTM candidate cell setting may mean executing the RRC reset procedure using the message regarding the reset of the RRC connection included in the LTM candidate cell setting. Furthermore, in each of the embodiments described above, the selected LTM candidate cell SpCell, one or more LTM candidate cells associated with the settings, is a terminal device This refers to a single SpCell configured using the cell group settings included in the aforementioned LTM candidate cell settings. This may be the case. Also, in each of the embodiments described above, “execute,” “start,” and “trigger” may be interchangeable with each other. In addition or instead, the RRC reset procedure in each of the embodiments described above may be performed independently in each cell group in the case of NR-DC. For example, the LTM candidate cell setting associated with the LTM target cell may be , included in the LTM candidate target settings associated with MCG (for example, the LTM-Config information element mentioned above) In this case, the RRC processing unit of UE122 executes the RRC reset procedure in the MCG, but does not need to execute the RRC reset procedure in the SCG. Also, in each of the above embodiments, "conditions A, B, C, ... If it is determined that all of the conditions A, B, C, ... are all met This can be rephrased as "in the case of," etc. Also, in each of the embodiments described above, "conditions A, B, C, If it is determined that any of the following conditions are not met, then "If any of the conditions A, B, C, ... If not met, or if it is determined that all conditions A, B, C, ... are met. This can be rephrased as "in the case that..." or similar.

[0230] Furthermore, unless otherwise specified, the term "wireless bearer" in the above description may refer to a DRB, an SRB, or both a DRB and an SRB.

[0231] Furthermore, in the above explanation, terms such as "user plane," "user plane protocol," and "user plane interface" may be used interchangeably.

[0232] Furthermore, in the above description, "receiving a DCI or MAC control element that instructs a change in the serving cell to one or more target cells" may be rephrased as "being instructed to change the serving cell to one or more target cells."

[0233] Furthermore, in the above explanation, expressions such as "terminal device variable," "terminal variable," and "variable" may be interchangeable.

[0234] Furthermore, unless otherwise specified, the serving cell change described above may refer to a change in a Layer 1 or Layer 2 serving cell.

[0235] Furthermore, in the above explanation, expressions such as "provided," "signaled," and "selected" may be interchangeable.

[0236] Furthermore, in the above explanation, expressions such as "LTM candidate target identifier" and "LTM candidate target entry identifier" may be interchangeable.

[0237] Furthermore, in the above explanation, expressions such as "to be notified" and "to be pointed out" may be used interchangeably.

[0238] Furthermore, in the above explanation, expressions such as "link," "correspond," and "associate" may be used interchangeably.

[0239] Furthermore, in the above explanation, expressions such as "included," "included," and "was included" may be interchangeable.

[0240] Furthermore, in the above explanation, "the aforementioned..." may be replaced with "the aforementioned...".

[0241] Also, in the above explanation, the phrases "~ has been confirmed," "~ is set," and "~ is included" are used. These expressions may be interchangeable.

[0242] Furthermore, in the examples of processes or process flows described above, some or all of the steps may not be executed. Also, in the examples of processes or process flows described above, the order of the steps may differ. Also, in the examples of processes or process flows described above, some or all of the processes within each step may not be executed. Also, in the examples of processes or process flows described above, the order of the processes within each step may differ. Also, in the above description, "Based on A, B "To perform" can be rephrased as "to perform B." In other words, "to perform B" is equivalent to "to be A." It may be executed independently.

[0243] Furthermore, in the above explanation, "A may be replaced with B" may include not only replacing A with B, but also replacing B with A. Also, in the above explanation, if it states "C may be D" and "C may be E", it may also include "D may be E". Also, in the above explanation, if it states "F may be G" and "G may be H", it may also include "F may be H".

[0244] Furthermore, in the above explanation, if condition "A" and condition "B" are contradictory conditions, condition "B" may be expressed as an "other" condition of condition "A".

[0245] The program running on the device according to this embodiment may be a program that controls the Central Processing Unit (CPU), etc., to make the computer function in order to realize the functions of this embodiment. The program or the information handled by the program may be temporarily loaded into volatile memory such as Random Access Memory (RAM) or flashed during processing. It is stored in non-volatile memory such as RAM or a Hard Disk Drive (HDD), and the CPU processes it as needed. This is how data is read, modified, and written.

[0246] Furthermore, some parts of the apparatus in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here refers to a computer system built into the apparatus, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of the following: a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0247] Furthermore, "computer-readable recording media" includes not only those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or communication lines like telephone lines, but also those that hold programs for a fixed period of time, such as the volatile memory inside computer systems that act as servers or clients in such cases. That's fine. Also, the above program may be for the purpose of implementing some of the functions mentioned above, and may also be a program that already has the aforementioned functions recorded in the computer system. It is also acceptable if it can be achieved in combination with the above.

[0248] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, typically an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), and field-programmable circuits. This may include a multi-gate array (FPGA), other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, a conventional processor, controller, microcontroller, or state machine. The general-purpose processor, or each of the aforementioned circuits, may consist of digital or analog circuits. Furthermore, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, integrated circuits using such technologies may also be used.

[0249] It should be noted that this embodiment is not limited to the embodiments described above. Although the embodiments describe an example of a device, this embodiment is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0250] Although this embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like that do not depart from the gist of this embodiment are also included. Furthermore, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in the above embodiment that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0251] 100 E-UTRA 102 eNB 104 EPC 106 NR 108 gNB 110 5GC 112, 114, 116, 118, 120, 124 Interfaces 122 UE 200, 300 PHY 202, 302 MAC 204, 304 RLC 206, 306 PDCP 208, 308 RRC 310 SDAP 210, 312 NAS 500, 604 Receiver 502, 602 processing unit 504, 600 Transmitter

Claims

1. A terminal device that communicates with a base station device, A receiving unit that receives RRC (Radio Resource Control) signaling from the base station device, A processing unit, and The RRC signaling includes one or more LTM (L1 / L2 Triggered Mobility) candidate information elements and conditions associated with each of the one or more LTM candidate information elements. Includes fixed, Based on the determination that one of the above conditions has been met, the processing unit determines one LTM candidate Stop one or more timers except for one associated with the supplementary information element. The aforementioned one LTM candidate information element is associated with the aforementioned one condition, Terminal device.

2. A base station device that communicates with terminal devices, A transmitting unit that transmits RRC (Radio Resource Control) signaling to the terminal device, A processing unit, and The processing unit provides the RRC signaling with one or more LTM (L1 / L2 Triggered Mobility) candidate information elements and the one or more LTM candidate information elements associated with each of them. Including the settings related to the conditions, By applying the RRC signaling to the terminal device, the terminal device will receive the conditions Based on the determination that one of the conditions has been met, one LTM candidate information element is associated with Stop one or more timers except for one. The aforementioned one LTM candidate information element is associated with the aforementioned one condition, Base station equipment.

3. A method for a terminal device to communicate with a base station device, The steps include receiving RRC (Radio Resource Control) signaling from the base station device and 、 The RRC signaling includes one or more LTM (L1 / L2 Triggered Mobility) candidate information elements and conditions associated with each of the one or more LTM candidate information elements. Includes fixed, Based on the determination that one of the above conditions has been met, regarding one LTM candidate information element The step of stopping one or more timers except for one of the connected timers, The aforementioned one LTM candidate information element is associated with the aforementioned one condition, A method for terminal devices.

Images