Terminal device, method, and integrated circuit

Abstract

To provide a method for a UE to determine the configuration validity of a target cell during conditional handover and / or conditional PSCell addition and / or PSCell change.SOLUTION: In a communication system, a UE receives first information and / or second information from a base-station device. The first information includes information elements relating to one or more cells. The information elements relating the cells each include information to be identified by a first identifier and allowing the terminal device to determine the validity of the information element relating to the cells. The second information includes an RRC reconfigure information element including parameters for synchronization reconfigure. The UE determines whether the second information includes the first identifier, and configures a PDCP layer, an RLC layer, a MAC layer and / or a PHY layer in accordance with the information element relating to cells indicated by the held first identifier on the basis of the determination that the information elements relating to a valid cell indicated by the first identifier is held.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present invention relates to a terminal device, a method, and an integrated circuit. [Background technology]

[0002] The 3G Partnership Project, a standardization project for cellular mobile communication systems In the 3rd Generation Partnership Project (3GPP), Technical studies and standardization of cellular mobile communication systems, including services, are currently underway.

[0003] For example, technical studies and standardization of E-UTRA (Evolved Universal Terrestrial Radio Access) have begun in 3GPP as a radio access technology (Radio Access Technology: RAT) for 3.9G and 4G cellular mobile communication systems. Currently, 3GPP is also conducting technical studies and standardization of E-UTRA extension technologies. E-UTRA is a Long Term It is also called LTE Evolution (registered trademark), and the extended technology is sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

[0004] In addition, 3GPP has begun technical discussions and standardization of NR (New Radio, or NR Radio access) as a radio access technology (Radio Access Technology: RAT) for cellular mobile communication systems for the 5th Generation (5G). Technical studies and standardization are currently underway. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.331 v17.0.0,"Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specifications" pp70-116,pp218-223,pp316-1107 Summary of the Invention [Problem to be solved by the invention]

[0006] In 3GPP, as an extension technology of NR, a base station device is considering broadcasting common settings to multiple terminal devices in a cell and using those settings during handover in order to reduce signaling overhead across the entire cell, but the details of the settings have not been considered.

[0007] One aspect of the present invention has been made in consideration of the above-mentioned circumstances, and an object of the present invention 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] In order to achieve the above object, one aspect of the present invention provides the following means. That is, one aspect of the present invention provides a terminal device, which transmits first information and / or second information to a base station. A receiving unit that receives information from a station device and a processing unit that performs processing of an RRC layer, includes one or more information elements regarding a cell, each of the information elements regarding the cell being identified by a first identifier, each of the information elements regarding the cell including information for the terminal device to determine validity of the information element regarding the cell, and the second information includes RRC reconfiguration including some or all of the parameters for synchronous reconfiguration. The second information includes an information element, and the processing unit determines whether the second information includes the first identifier. and, if the second information includes the first identifier, determines whether or not an information element related to the valid cell indicated by the first identifier is held, and based on the determination that an information element related to the valid cell indicated by the first identifier is held, configures a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer in accordance with the held information element related to the cell indicated by the first identifier.

[0009] Another aspect of the present invention is a method applied to a terminal device, comprising: the step of receiving, from a base station device, either one or two pieces of information related to the cell; determining whether the second information includes the first identifier; if the second information includes the first identifier, determining whether the terminal device holds an information element related to the valid cell indicated by the first identifier; and, based on the determination that the terminal device holds an information element related to the valid cell indicated by the first identifier, configuring a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer in accordance with the held information element related to the cell indicated by the first identifier, wherein the first information includes one or more information elements related to a cell, each of the information elements related to the cell being identified by a first identifier, each of the information elements related to the cell including information for the terminal device to determine validity of the information element related to the cell, and the second information includes an RRC reconfiguration information element including some or all of parameters for synchronization reconfiguration.

[0010] Another aspect of the present invention is an integrated circuit implemented in a terminal device, the integrated circuit having a function of receiving first information and / or second information from a base station device, and a function of adding the first identification number to the second information. the terminal device to perform the following functions: determining whether the second information includes a child of the cell indicated by the first identifier; determining whether, when the second information includes the first identifier, it holds information elements related to a valid cell indicated by the first identifier; and, based on determining that the second information includes information elements related to the valid cell indicated by the first identifier, configuring a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer in accordance with the information elements related to the cell indicated by the first identifier that it holds, wherein the first information includes one or more information elements related to a cell, each of the information elements related to the cell being identified by a first identifier, each of the information elements related to the cell including information for the terminal device to determine validity of the information element related to the cell, and the second information includes an RRC reconfiguration information element including some or all of the parameters for synchronous reconfiguration.

[0011] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. Effect of the Invention

[0012] According to one aspect of the present invention, a terminal device, a method, and an integrated circuit can realize efficient communication control processing. [Brief description of the drawings]

[0013] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of an E-UTRA protocol configuration according to the present embodiment. [Diagram 3] FIG. 1 is a diagram showing an example of an NR protocol configuration according to the present embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a procedure flow for various settings in the RRC according to the present embodiment. [Diagram 5]FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment. [Figure 6] FIG. 2 is a block diagram showing the configuration of a base station device in the present embodiment. [Figure 7] An example of an ASN.1 description of a message regarding reconfiguration of an RRC connection in NR in this embodiment. [Figure 8] An example of an ASN.1 description of a message regarding reconfiguration of an RRC connection in NR in this embodiment. [Figure 9] 4 is an example of an RRC reconfiguration process in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, the present 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 (RATs). In addition, LTE that can be connected to NR via Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. In addition, LTE that uses 5GC in the core network (Core Network: CN) may be distinguished from conventional LTE that uses EPC in the core network. Conventional LTE may refer to LTE that does not implement technologies 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 are used, but this embodiment may also apply to technologies using other terms. , and / or other radio access technologies. The terms LTE and LTE may be used interchangeably.

[0016] In this embodiment, the names of the nodes and entities and the processes in the nodes and entities when the radio access technology is E-UTRA or NR will be described, but this embodiment may be applied to other radio access technologies. The names of the nodes and entities and the names of the parameters and messages in this embodiment may be different from those described in this embodiment.

[0017] Fig. 1 is a schematic diagram of a communication system according to this embodiment. Note that the functions of each node, radio access technology, core network, interface, etc. described using Fig. 1 are only some of the functions closely related to this embodiment, and the system may have other functions.

[0018] The E-UTRA 100 may be a radio access technology. The air interface between the UE 122 and the eNB 102 may be referred to as a Uu interface. The eNB (E-UTRAN Node B) 102 is the basis of the E-UTRA 100. The eNB 102 may be a base station device. The eNB 102 may have an E-UTRA protocol, which will be described later. The E-UTRA protocol includes an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA The eNB 102 may be configured with a control plane (CP) protocol. In contrast, the eNB may terminate an E-UTRA User Plane (UP) protocol and an E-UTRA Control Plane (CP) protocol. A radio access network configured with the eNB may be referred to as an E-UTRAN.

[0019] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104, and may be referred to as an S1 interface. The interface 112 may include a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may terminate at a Mobility Management Entity (MME; not shown) in the EPC 104. The user plane interface of the interface 112 may terminate at a Serving Gateway (S-GW; not shown) in the EPC 104. The control plane interface of the interface 112 may be referred to as an S1-MME interface. The interface may be called the S1-U interface.

[0020] Note that one or more eNBs 102 may be connected to the EPC 104 via an interface 112. There may be an interface (not shown) between multiple eNBs 102 that connect to the EPC 104. The interface between multiple eNBs 102 connected to 04 may be referred to as the X2 interface.

[0021] NR 106 may be a radio access technology. NR 106 may also be an air interface between UE 122 and gNB 108. The air interface between the UE 122 and the gNB 108 may be called a Uu interface. The gNB (g Node B) 108 may be a base station device of the NR 106. The gNB 108 may have the NR protocol described below. The NR protocol includes the NR User Plane (UP) protocol described below and the NR Control Plane (CP) protocol described below. The gNB 108 may terminate NR user plane (UP) protocols and NR control plane (CP) protocols for the UE 122.

[0022] The 5GC 110 may be a core network. The interface 116 is an interface between the gNB 108 and the 5GC 110. The interface 116 may be a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. There may be a control plane interface for the interface 116. The access point should be terminated by the Access and Mobility Management Function (AMF: not shown) in the 5GC110. The user plane interface of the interface 116 may terminate in a User Plane Function (UPF: not shown) in the 5GC 110. The control plane interface of the interface 116 may be referred to as an NG-C interface. The user plane interface of the interface 116 may be referred to as an NG-U interface.

[0023] Note that one or more gNBs 108 may be connected to the 5GC 110 via an interface 116. There may be an interface (not shown) between multiple gNBs 108 connected to the 5GC 110. The interface between multiple gNBs 108 connected to the 5GC 110 may be referred to as an Xn interface.

[0024] The eNB 102 may have a function to connect to the 5GC 110. The eNB 102 having a function to connect to the 5GC 110 may be called an ng-eNB. The interface 114 is an interface between the eNB 102 and the 5GC 110, and is an NG The interface 114 may be referred to as a control plane through which control signals pass. There exists a user plane interface through which user data passes. The control plane interface of interface 114 may terminate at an AMF in 5GC 110. The user plane interface of interface 114 may terminate at a UPF in 5GC 110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of the interface 114 is called the NG-U interface. A radio access network consisting of ng-eNB or gNB may be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may be simply called networks. , eNB, ng-eNB and gNB, etc.

[0025] Note that one or more eNBs 102 may be connected to the 5GC 110 via an interface 114. An interface may exist between the multiple eNBs 102 connected to the 5GC 110 (not shown). The interface between the multiple eNBs 102 connected to the 5GC 110 may be called an Xn interface. The eNBs 102 connected to the 5GC 110 and the gNBs 108 connected to the 5GC 110 are connected to each other via an interface 120. The interface 120 between the eNB 102 that connects to the 5GC 110 and the gNB 108 that connects to the 5GC 110 may be referred to as an Xn interface.

[0026] The gNB 108 may have a function to connect to the EPC 104. The gNB 108 having a function to connect to the EPC 104 may be called an en-gNB. The interface 118 is an interface between the gNB 108 and the EPC 104, and is an S1 The interface 118 may be referred to as a user program interface through which user data passes. There may be a lane interface. The user plane interface of the interface 118 may terminate at an S-GW (not shown) in the EPC 104. The interface may be referred to as an S1-U interface. The eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be connected to each other via an interface 120. The interface 120 between the UE 102 and the gNB 108 that connects to the EPC 104 may be referred to as the X2 interface.

[0027] The interface 124 is an interface between the EPC 104 and the 5GC 110, and can be used with either the CP only or the UP only. In addition, some or all of the interfaces such as the interface 114, the interface 116, the interface 118, the interface 120, and the interface 124 may be interfaces that are provided by a communication carrier or the like. It may not be present depending on the system.

[0028] The UE 122 may be a terminal device capable of receiving system information and paging messages transmitted from the eNB 102 and / or the gNB 108. The UE 122 may be a terminal device capable of wireless connection with the eNB 102 and / or the gNB 108. The UE 122 may be a terminal device capable of wireless connection with the eNB 102. The UE 122 may be a terminal device capable of simultaneously performing a radio connection with the gNB 108 and a radio connection with the gNB 108. The UE 122 may have an E-UTRA protocol and / or an NR protocol. The radio connection may be a Radio Resource Control (RRC) connection.

[0029] The UE 122 also communicates with the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108. When the eNB 102 and / or gNB 108 with which the UE 122 communicates is connected to the EPC 104, each Data Radio Bearer (DRB) (described later) established between the UE 122 and the eNB 102 and / or gNB 108 is further routed through the EPC 104. Each EPS bearer may be uniquely associated with an Evolved Packet System (EPS) bearer. Each EPS bearer may be identified by an EPS bearer identity (ID). The same QoS may be guaranteed for data such as packets and Ethernet frames. .

[0030] In addition, when the core network to which the eNB 102 and / or the gNB 108 with which the UE 122 communicates is connected is the 5GC 110, each DRB established between the UE 122 and the eNB 102 and / or the gNB 108 is further Each DRB may be associated with one of the PDU (Packet Data Unit) sessions established within the DRB. Each PDU session may have one or more QoS flows. Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flow. Each PDU session may be identified by a PDU session identifier (Identity, or ID). Also, each QoS flow may be identified by a QoS flow identifier (Identity, or ID). Also, the same QoS may be guaranteed to data such as IP packets and Ethernet frames passing through the same QoS flow.

[0031] There may be no PDU sessions and / or QoS flows in the EPC 104. When the UE 122 is connected to the EPC 104, the UE 122 has knowledge of the EPS bearers, but may not have knowledge of the PDU sessions and / or QoS flows. In addition, when the UE 122 is connected to the 5GC 110, the UE 122 may It has information about the EPS bearer, but does not need to have information about the EPS bearer.

[0032] In the following description, eNB 102 and / or gNB 108 are also simply referred to as base station devices, and UE 122 are also simply referred to as terminal devices or UEs.

[0033] FIG. 2 is a diagram showing an example of an E-UTRA protocol architecture according to this embodiment. FIG. 3 is a diagram showing an example of an NR protocol architecture according to this embodiment. The functions of each protocol described with reference to FIG. 3 are some of the functions closely related to this embodiment. In this embodiment, the uplink (UL) may be a link from a terminal device to a base station device. The link (downlink: DL) may be a link from a base station device to a terminal device. In this configuration, sidelink (SL) refers to a base station device from a terminal device to a terminal device. It may be a link that does not involve a

[0034] FIG. 2(A) is a diagram of an E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRA UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRA UP protocol may be a protocol that terminates at the eNB 102 on the network side. 1, the E-UTRA user plane protocol stack may be composed of a PHY (Physical layer) 200 which is a radio physical layer, a MAC (Medium Access Control) 202 which is a medium access control layer, a 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) shows the NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR The UP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol On the network side, the NR user plane protocol stack may be a protocol that terminates at the gNB 108. As shown in FIG. 3A, the NR user plane protocol stack may be composed of a radio physical layer PHY 300, a medium access control layer MAC 302, a radio link control layer RLC 304, a packet data convergence protocol layer PDCP 306, and a service data adaptation protocol layer SDAP (Service Data Adaptation Protocol) 310.

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

[0037] Figure 3(B) shows the NR control plane (CP) protocol configuration. As shown in Figure 3(B), the NR CP protocol In the protocol, the radio resource control layer RRC 308 controls the protocol between the UE 122 and the gNB 108. That is, the RRC 308 may be a protocol that terminates at the gNB 108 on the network side. In the NR CP protocol, the NAS 312, which is a non-AS layer, is a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates at the AMF on the network side. That's fine.

[0038] The AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and / or the gNB 108. In other words, the AS layer may be one of the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208. layers including some or all of the PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and and RRC 308.

[0039] In the present embodiment, the E-UTRA protocol and the NR protocol may not be distinguished from each other, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. The SDAP (SDAP layer) may also be the SDAP (SDAP layer) of the NR protocol.

[0040] In addition, in this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are referred to as PHY for E-UTRA and PHY for LTE, respectively. HY, MAC for E-UTRA or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or LTE The PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are also referred to as the E-UTRA PHY or LTE PHY, the E-UTRA MAC, or the LTE MAC, respectively. It may also be written as MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC. Also, a distinction is made between E-UTRA protocols and NR protocols. In this case, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. Also, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to 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. An entity that has some or all of the functions of the MAC layer may be called a MAC entity. An entity that has some or all of the functions of the RLC layer may be called an RLC entity. An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity. An entity having some or all of the functions of the SDAP layer may be called an SDAP entity. An entity having some or all of the functions of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0042] Note that data provided to lower layers from MAC, RLC, PDCP, and SDAP, and / or MAC, RLC The data provided to MAC, RLC, PDCP, and SDAP from lower layers may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided to MAC, RLC, PDCP, and SDAP from higher layers and / or the data provided to higher layers by MAC, RLC, PDCP, and SDAP may be called SDAP PDU. The data is called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may be referred to as an RLC SDU segment.

[0043] Here, the base station device and the terminal device transmit signals in a higher layer. The higher layer may be called the upper layer, and they are interchangeable. For example, the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC signaling) in a Radio Resource Control (RRC) layer. The base station apparatus and the terminal apparatus may transmit and receive MAC control elements in a Medium Access Control (MAC) layer. The RRC layer of the terminal apparatus acquires system information broadcast from the base station apparatus. Here, the RRC message, the system information, and and / or the MAC control element receives higher layer signaling A parameter included in a higher layer signaling received by a terminal device may be referred to as a higher layer parameter. For example, in PHY layer processing, a higher layer means a higher layer seen from the PHY layer, and may mean one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, a higher layer may mean one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer, etc.

[0044] In the following, "A is given (provided) by a higher layer" or "A is given (provided) by a higher layer" means that a higher layer (mainly an RRC layer or a MAC layer) of the terminal device receives A from a base station device, and the received A is transmitted from the higher layer of the terminal device to a lower layer of the terminal device (mainly a MAC layer or a physical layer). For example, in a terminal device, The phrase "upper layer parameters are provided" may mean that an upper layer signal is received from a base station apparatus, and the upper layer parameters included in the received upper layer signal are provided from an upper layer of the terminal apparatus to a lower layer of the terminal apparatus. The phrase "upper layer parameters are set in the terminal apparatus" may mean that the upper layer parameters are given (provided) to the terminal apparatus. For example, the phrase "upper layer parameters are set in the terminal apparatus" may mean that the terminal apparatus It may mean receiving a higher layer signal from the base station device and setting the received higher layer parameters in the higher layer. However, setting higher layer parameters in the terminal device may also include setting default parameters that are given in advance in the higher layer of the terminal device. Then, the RRC entity of the terminal device sends a message to the lower layer. In the terminal device, the RRC entity In the terminal device, "submitting a message to a lower layer" from the RRC layer may mean submitting a message to the PDCP layer. This is because RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). This means submitting messages to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from a lower layer, The layer may refer to one or more of a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and the like.

[0045] An example of the function of the PHY will be described. The PHY of the terminal device receives the downlink from the PHY of the base station device. Receives data transmitted via a Downlink (DL) physical channel. The PHY of the terminal device may have an uplink (UL) object with respect to the PHY of the base station device. The PHY may have a function of transmitting data via a physical channel. The PHY may be connected to a higher MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also pass data from the MAC via the transport channel. In the PHY, a Radio Network Temporary Identifier (RNTI) may be used to identify various control information.

[0046] Here, the physical channels will be described. The physical channels used for wireless communication between a terminal device and a base station device may include the following physical channels.

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

[0048] The PBCH may be used to broadcast system information required by a terminal device.

[0049] In addition, in NR, the PBCH may be used to broadcast a time index (SSB-Index) within a period of a synchronization signal block (SSB).

[0050] The PDCCH is a downlink radio communication channel (radio communication from a base station device to a terminal device). The UE may be used to transmit (or carry) Downlink Control Information (DCI), where one or more DCIs (DCI In other words, a format for the downlink control information may be defined. The fields corresponding to the PDCCH candidates may be defined as DCI and mapped to information bits. The PDCCH may be transmitted in a search space. 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. In addition, the terminal device may The PDCCH candidate may be monitored at configured monitoring occasions in one or more configured control resource sets (CORESETs) configured by the service configuration. The DCI format may be used for scheduling the PUSCH in the serving cell. The PUSCH may be used for transmitting user data, transmitting an RRC message (to be described later), and the like.

[0051] The PUCCH is used in uplink wireless communication (wireless communication from a terminal device to a base station device). The uplink control information may be used to transmit uplink control information (UCI). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. The uplink control information may include a Scheduling Request (SR) used to request an Uplink Shared CHannel (UL-SCH) resource. The link control information includes HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement). It is okay to be swallowed.

[0052] The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. In addition, the PDSCH may be used to transmit system information (SI: System Information) and random access response (RAR: Random Access Response) in the downlink.

[0053] The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or uplink data together with HARQ-ACK and / or CSI, or may be used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only the UCI, and the PDSCH or the PUSCH may be used to transmit an RRC message and a MAC CE, which will be described later. In the PDSCH, an RRC message transmitted from a base station apparatus may be common signaling for a plurality of terminal apparatuses in a cell. Also, an RRC message transmitted from a base station apparatus may be dedicated signaling for a certain terminal apparatus. In other words, the information specific to a terminal apparatus (UE specific information) may be dedicated to a certain terminal apparatus. The PUSCH may be transmitted using the same signaling as the UE's uplink capability. It may also be used to transmit UE Capability.

[0054] The PRACH may be used to transmit a random access preamble. The PRACH is used for initial connection establishment procedures, handover procedures, connection re-establishment procedures, and the above. It may be used for synchronization (timing alignment) for uplink transmissions and to indicate a request for UL-SCH resources.

[0055] An example of the functions of the MAC will be described. The MAC may be called a MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by a logical channel identity (or logical channel ID). The MAC may be connected to the higher RLC via a logical channel. Depending on the type of information to be transmitted, the logical channels may be divided into a control channel that transmits control information and a traffic channel that transmits user information. The logical channels may also be divided into an uplink logical channel and a downlink logical channel. The MAC may be configured to transmit one or more different The MAC may have a function of multiplexing MAC SDUs belonging to different logical channels and providing them to the PHY. The MAC may also have a function of demultiplexing MAC PDUs provided from the PHY and providing them to a higher layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function of performing error correction through Hybrid Automatic Repeat reQuest (HARQ). The MAC may also have a function of reporting scheduling information, i.e., a scheduling information reporting function. The MAC may have a scheduling and reporting function. MAC may have a function for performing priority processing between logical channels in one terminal device. The MAC may have a function for prioritizing overlapping packets within a single terminal device. The NR MAC may have the ability to prioritize resources. The MAC may have the ability to identify Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also The MAC may have the ability to identify the Multicast Broadcast Service (MBS). The MAC may have the ability to select the transport format. The MAC may perform Discontinuous Reception (DRX) and / or Discontinuous Transmission (DTX). Function, Random Access (RA) procedure execution function, Power Headroom Report (PHR) function to notify information on available transmission power, Transmission buffer The NR MAC may have a Buffer Status Report (BSR) function to report the amount of data in the NR channel. The NR MAC may have a Bandwidth Adaptation (BA) function. In addition, the MAC PDU format used in the E-UTRA MAC and the MAC PDU format used in the NR MAC may be different. In addition, the MAC PDU may include a MAC control element (MAC CE), which is an element for performing control in the MAC.

[0056] Uplink (UL) and / or downlink (DL) used in E-UTRA and / or NR Next, the logical channels for DL ​​(Downlink) will be described.

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

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

[0059] A Common Control Channel (CCCH) may be a logical channel for transmitting control information between a terminal device and a base station device. The CCCH is used when the terminal device does not have an RRC connection. In addition, the CCCH may be used between a base station device and multiple terminal devices.

[0060] A DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information in a point-to-point bidirectional manner between a terminal device and a base station device. The dedicated control information may be control information dedicated to each terminal device. The DCCH may be used when the terminal device has an RRC connection.

[0061] A Dedicated Traffic Channel (DTCH) may be a logical channel for transmitting user data point-to-point between a terminal device and a base station device. The DTCH may be a logical channel for transmitting user data. The dedicated user data may be user data dedicated to each terminal device. The DTCH may exist in both the uplink and the downlink.

[0062] Logical channels and transport channels for the uplink in E-UTRA and / or NR This section explains the mapping of rules.

[0063] CCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0064] DCCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0065] DTCH is an uplink transport channel, UL-SCH (Uplink Shared Channel) may be mapped to

[0066] Logical channels and transport channels for the downlink in E-UTRA and / or NR This section explains the mapping of rules.

[0067] BCCH is a downlink transport channel, BCH (Broadcast Channel), and / or Or it may be mapped to a DL-SCH (Downlink Shared Channel).

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

[0069] CCCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0070] DCCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0071] DTCH is a downlink transport channel, DL-SCH (Downlink Shared Channel) may be mapped to

[0072] An example of the function of the RLC will be described. The RLC may be called an RLC sublayer. The E-UTRA RLC may have a function of segmenting and / or concatenating data provided from the PDCP of the upper layer and providing it to a lower layer. The E-UTRA RLC may perform reassembly and reordering of data provided from the lower layer. The NR RLC may have the function of re-ordering and providing it to higher layers. The NR RLC may have a function to add a sequence number to data provided by the PDCP of the layer that is independent of the sequence number added by the PDCP. The NR RLC may also have a function to segment data provided by the PDCP and provide it to a lower layer. The NR RLC may also have a function to reassemble data provided by the lower layer and provide it to a higher layer. The RLC may also have a function to retransmit data and / or a function to request retransmission (Automatic The RLC may have a Repeat reQuest (ARQ) function. The RLC may also have a function for performing error correction by ARQ. The control information sent from the receiving side of the RLC to the transmitting side to indicate the data that needs to be retransmitted in order to perform ARQ may be called a status report. The status report transmission instruction sent by the RLC is called a poll. The RLC entity may have a function to detect data duplication. The RLC entity may also have a function to discard data. The RLC entity may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The TM entity does not divide data received from the upper layer, and does not need to add an RLC header. The TM RLC element is a uni-directional entity. The UM may be configured as a receiving TM RLC entity or as a receiving TM RLC entity. In UM, it is responsible for splitting and / or combining data received from higher layers, adding RLC headers, etc. In the AM, retransmission control of data is not required. The UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, it may be configured as a transmitting UM RLC entity or as a receiving UM RLC entity. If the UM RLC entity is a bi-directional entity, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In the AM The AM RLC entity may perform division and / or concatenation of data received from a higher layer, addition of an RLC header, data retransmission control, etc. The AM RLC entity is a bidirectional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side. In addition, the data provided to the lower layer by TM and / or the data provided by the lower layer The data provided to and / or from a lower layer in UM may be called a UMD PDU. The data provided to and / or from a lower layer in AM may be called a UMD PDU. The data provided by the RLC or a lower layer may be called AMD PDU. The RLC PDU format used in the NR RLC may be different from the RLC PDU format used in the NR RLC. The RLC PDU may be a data RLC PDU or a control RLC PDU. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU). The control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU).

[0073] An example of the function of PDCP will be described. PDCP may be called a PDCP sublayer. PDCP may have a function for maintaining sequence numbers. PDCP also provides a mechanism for efficiently transmitting user data such as IP packets and Ethernet frames over wireless sections. The protocol used for IP packet header compression and decompression may be called ROHC (Robust Header Compression) protocol. The protocol used for Ethernet frame header compression and decompression is EHC (Ethernet (registered trademark) PDCP may be called a Header Compression Protocol (PDCP). PDCP may also have a function for encrypting and decrypting data. PDCP may also have a function for protecting and verifying the integrity of data. PDCP may also have a function for re-ordering. PDCP may also have a function for retransmitting PDCP SDUs. PDCP may also have a function for discarding data using a discard timer. PDCP may also have a duplication function. PDCP may also have a function to discard duplicated received data. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from the PDCP PDU format used in NR PDCP. There may be a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). The PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0074] An example of the SDAP function is explained below. SDAP is a service data adaptation protocol layer (SDAP). SDAP is a data service adaptation protocol layer (SDAP). Mapping of downlink QoS flows sent to the device and data radio bearers (DRBs) The SDAP may have a function of mapping between the DRB and an uplink QoS flow sent from the terminal device to the 5GC110 via the base station device, and / or a function of mapping between the DRB and an uplink QoS flow sent from the terminal device to the 5GC110 via the base station device. The SDAP may also have a function of storing mapping rule information. The SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI). The SDAP PDU may include a data SDAP PDU and a control SDAP PDU. The data SDAP PDU is called an SDAP DATA PDU (SDAP Data PDU, SDAP Data PDU). The SDAP PDU for control may be called SDAP CONTROL PDU (SDAP Control PDU, SDAP The SDAP entity of the terminal device may be called a control PDU or an SDAP control PDU. One SDAP entity of the terminal device may exist for each PDU session.

[0075] An example of the function of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or the 5GC 110. The RRC may also have an RRC connection management function. The RRC may also have a The RRC may have a radio bearer control function. The RRC may also have a cell group control function. The RRC may have a mobility control function. The RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. The RRC may have a QoS management function. The RRC may have a radio link failure detection and recovery function. The RRC may use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. Note that the RRC messages and parameters used in E-UTRA RRC are the same as the RRC messages and parameters used in NR RRC. The parameter may be different.

[0076] RRC messages may be sent using the logical channel BCCH or the logical channel PCCH. RRC messages may be sent using the logical channel CCCH, or may be sent using the logical channel DCCH. In addition, RRC messages sent using the DCCH are referred to as Dedicated RRC signaling, or RRC signaling.

[0077] The RRC messages sent using the BCCH may include, for example, a Master Information Block (MIB), various types of System Information Blocks (SIBs), and other RRC messages. The RRC messages sent using the PCCH may include, for example, paging messages, and other RRC messages.

[0078] RRC messages sent in the uplink (UL) direction using CCCH include, for example, an RRC setup request message, an RRC resume request message, an RRC reestablishment request message, and an RRC system information request message. The RRC message may include an RRC System Info Request message, etc. Also, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, etc. Also, other RRC messages may be included.

[0079] RRC messages sent in the downlink (DL) direction using CCCH include, for example, an RRC connection reject message (RRC Connection Reject), an RRC connection setup message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment), and an RRC connection reestablishment reject message (RRC Connection Reestablishment Reject). Also, for example, an RRC reject message, an RRC setup message, etc. may be included. Also, other RRC messages may be included.

[0080] RRC signaling sent in the uplink (UL) direction using the DCCH includes, for example, measurement reports. The message may include, for example, a measurement report message, an RRC connection reconfiguration complete message, an RRC connection setup complete message, an RRC connection reestablishment complete message, a security mode complete message, a UE capability information message, etc. RRC Setup Complete, RRC Reestablishment Complete, RRC Resume Complete, Security Mode Complete The RRC signaling may include a Security Mode Complete message, a UE Capability Information message, etc., and may also include other RRC signaling.

[0081] The RRC signaling sent in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message, an RRC connection release message, a security mode command message, a UE capability inquiry message, etc. Also, for example, an RRC reconfiguration message, an RRC resume message, an RRC release message, an RRC reestablishment message, a security mode command message, a UE capability inquiry message, etc. Also, other RRC signaling may be included.

[0082] An example of the function of the NAS will be described. The NAS may have an authentication function. The NAS may also have the functionality to perform security control. You may have it.

[0083] The above-mentioned PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are examples. In addition, some or all of the functions of each layer may be included in other layers.

[0084] Next, state transitions of the UE 122 in LTE and NR will be described. When the UE 122 connected to the EPC or 5GC has an RRC connection established, the UE 122 may be in an RRC_CONNECTED state. The state in which the RRC connection is established means that the UE 122 is in a state where it ... The RRC connection may include a state in which the UE holds some or all of the above-mentioned UE context. The established state may include a state in which the UE 122 can transmit and / or receive unicast data. The UE 122 may be in an RRC_INACTIVE state when the RRC connection is suspended. The UE 122 may be in an RRC_INACTIVE state when the UE 122 is connected to a 5GC and the RRC connection is suspended. When the UE 122 is neither in an RRC_CONNECTED state nor in an RRC_INACTIVE state, the UE 122 may be in an RRC_IDLE state.

[0085] Note that when the UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but is In the case where UE 122 is connected to EPC, when the RRC connection is suspended, UE 122 may transition to the RRC_IDLE state while retaining the UE AS context and an identifier (resumeIdentity) used for resume. An upper layer (e.g., NAS layer) of the RRC layer of UE 122 may transmit the suspended RRC connection to the RRC_IDLE state when UE 122 retains the UE AS context, the E-UTRAN has permitted the RRC connection to be resumed, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state. Recovery may be initiated.

[0086] The definition of dormancy may be different between the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110. In addition, when the UE 122 is connected to the EPC (when the UE 122 is dormant in the RRC_IDLE state) and when the UE 122 is connected to the 5GC (when the UE 122 is dormant in the RRC_INACTIVE state), However, some or all of the procedures for returning from hibernation may be different.

[0087] Note that the RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states are referred to as connected, The RRC state may be referred to as a connected mode, an inactive mode, or an idle mode, or may be referred to as an RRC connected mode, an RRC inactive mode, or an RRC idle mode.

[0088] The UE AS context held by the UE 122 may be information including all or a part of the following: a current RRC setting, a current security context, a PDCP state including a ROHC (RObust Header Compression) state, a C-RNTI (Cell Radio Network Temporary Identifier) ​​used in the source PCell, a cell identifier, and a physical cell identifier of the source PCell. Note that the UE AS context held by any or all of the eNB 102 and the gNB 108 may include the same information as the UE AS context held by the UE 122, or may include information different from the information included in the UE AS context held by the UE 122.

[0089] The security context may be information including all or part of the encryption key at the AS level, the Next Hop parameter (NH), the Next Hop Chaining Counter parameter (NCC) used to derive the next hop access key, an identifier for the selected AS level encryption algorithm, and a counter used for replay protection.

[0090] Next, the serving cell will be explained. CA and / or DC, which will be described later, In a terminal device in an unconfigured RRC connected state, the serving cell has one primary In addition, the CA and / or DC may be configured as In a terminal device in an established RRC connected state, the multiple serving cells are one or Multiple Special Cells (SpCells) and one or more of all secondary The term "PCell" may refer to a set of multiple cells (set of cell(s)) consisting of a secondary cell (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may be always activated. The 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. The PCell may also be a cell used in the RRC connection reestablishment procedure when a terminal device reestablishes an RRC connection. The PCell may be the cell used in the establishment procedure. The PCell may also be the cell used for random addressing during handover. The PSCell may be a cell used in a random access procedure when a secondary node is added, which will be described later. The SpCell may be a cell used for purposes other than those described above.

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

[0092] A cell group configured by a base station device for a terminal device will be described. A cell group may be composed of one SpCell. Also, a cell group may be composed of one SpCell and one or more SCells. and optionally one or more SCells. A loop may be expressed as a set of cell(s).

[0093] Dual Connectivity (DC) is a technology that performs data communication using the wireless resources of cell groups that are respectively configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC is performed, the base station device A cell group may be added from the first base station device. In order to perform DC, the first base station device may add a second base station device. The first base station device may be called a master node (MN). Also, a cell group configured by the master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). Also, a cell group configured by the secondary node may be called a secondary cell group (SCG). The master node and the secondary node may be configured in the same base station device.

[0094] In addition, when DC is not configured, the cell group configured in the terminal device may be called MCG. In addition, when DC is not configured, the SpCell configured in the terminal device may be PCell. In addition, NR in which DC is not configured may be called NR standalone (NR SA).

[0095] In addition, Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC is a technology that performs DC using NR for MCG and E-UTRA for SCG. MR-DC is a technique for performing DC using NR in both MCG and SCG. MR-DC may be a technology included in DC. An example of MR-DC using E-UTRA for MCG and NR for SCG is EN-DC (E-UTRA-NR Dual Connectivity) using EPC for the core network. An example of an MR-DC that uses NR for the MCG and E-UTRA for the SCG is NE-DC (NR-E-UTRA Dual Connectivity), which uses 5GC for the core network. An example of an MR-DC that uses NR for the MCG and E-UTRA for the SCG is NE-DC (NR-E-UTRA Dual Connectivity), which uses 5GC for the core network. Therefore, it would be good to have NR-DC (NR-NR Dual Connectivity) that uses 5GC in the core network.

[0096] In addition, in the terminal device, one MAC entity may exist for each cell group. For example, when a DC or MR-DC is set in a terminal device, one MAC address for the MCG is There may be one MAC entity for the MCG and one MAC entity for the SCG in the terminal device. The MAC entity for the MCG in the terminal device may be always established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). The MAC entity for the SCG is CLASSIFIED by the terminal device when the SCG is configured in the terminal device. Also, a MAC entity for each cell group of the terminal device may be created. The terminal device is configured by receiving RRC signaling from the base station device. If the MAC entity is associated with an MCG, the SpCell may refer to a PCell. Also, when the MAC entity is associated with an SCG, SpCell may mean a Primary SCG Cell (PSCell). If not specified, SpCell may mean PCell. PCell, PSCell and SCell are service In EN-DC and NGEN-DC, the MAC entity for the MCG is E-UTRA In the NE-DC, the MAC entity for the SCG may be an NR MAC entity, and the MAC entity for the MCG may be an NR MAC entity. and the MAC entity for the SCG may be an E-UTRA MAC entity. In addition, in NR-DC, the MAC entities for the MCG and the SCG may both be NR MAC entities. Note that the existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell. Also, one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

[0097] Explains the flow of RRC signaling transmitted and received between a terminal device and a base station device FIG. 4 is a flow chart of a procedure for various settings in the RRC according to this embodiment. 4 is a diagram illustrating an example of a flow when RRC signaling is transmitted from a base station device (eNB 102 and / or gNB 108) to a terminal device (UE 122).

[0098] In FIG. 4, the base station device creates an RRC message (step S400). The base station device may create an RRC message in order to deliver system information (SI) or a paging message. The base station device creates the message by sending RRC signaling to a specific terminal device to perform the process. The processing to be performed on a specific terminal device may be, for example, security-related settings, re-setting of an RRC connection, handover to a different RAT, or The RRC connection re-establishment process may include processes such as radio bearer control (establishment, modification, release, etc.), cell group control (establishment, modification, release, etc.), etc. ,addition, modification, release, etc.), measurement configuration, handover, security key update, etc. The base station device may generate an RRC message. The RRC message may be performed in response to the RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, etc. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be fields of the RRC message and / or information elements, or field values ​​(including information elements). RRC Message The structure of the object can be described using a notation method called ASN.1 (Abstract Syntax Notation One). stomach.

[0099] In FIG. 4, the base station device then transmits the created RRC signaling to the terminal device (step (Step S402). Next, the terminal device performs processing such as setting according to the received RRC signaling if necessary (Step S404). After performing the processing, the terminal device may transmit RRC signaling for response to the base station device (not shown).

[0100] RRC signaling may be used for other purposes, not limited to the above examples.

[0101] In the MR-DC, the RRC on the master node side may be used to transfer RRC signaling for SCG side configuration (cell group configuration, radio bearer configuration, measurement configuration, etc.) between the terminal device. For example, in the EN-DC or NGEN-DC, the RRC signaling is transmitted and received between the eNB 102 and the UE 122. In the NE-DC, the RRC signaling of the E-UTRA may include the RRC signaling of the NR in the form of a container in the RRC signaling of the E-UTRA transmitted between the gNB 108 and the UE 122. The RRC signaling for the SCG side configuration may be transmitted between the master node and the secondary node.

[0102] In addition, the RRC signal for E-UTRA transmitted from the eNB 102 to the UE 122 may be transmitted in any case, regardless of whether the MR-DC is used or not. The RRC signaling for NR may be included in the gNB 108 RRC signaling transmitted to the UE 122, and the RRC signaling for NR may be included in the RRC signaling for E-UTRA transmitted from the gNB 108 to the UE 122.

[0103] An example of parameters included in the message regarding re-establishment of the RRC connection will be described with reference to FIGS. 7 and 8. FIG.

[0104] In Figures 7 and 8, the message related to the re-establishment of the RRC connection includes information elements (CellGroupConfig information) used for establishing, modifying, releasing, etc. the cell group of the NR MCG or SCG. The RRC connection re-establishment message may include the MCG configuration element. and a CellGroupConfig information element for the SCG configuration. The CellGroupConfig information element may be included separately from the Cell Group Configuration information element, or may be referred to as a cell group configuration.

[0105] The CellGroupConfig information element contains identifier information to identify this cell group. , a cellGroupId information element may be included.

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

[0107] The CellGroupConfig information element may include a MAC-CellGroupConfig information element as information used to configure MAC parameters in the cell group.

[0108] The CellGroupConfig information element may include a PhysicalCellGroupConfig information element as information used to configure PHY (L1) parameters specific to the cell group.

[0109] The CellGroupConfig information element contains the parameter settings for the SpCell of the cell group. The information used for may include an SpCellConfig information element. The SpCellConfig information element may be referred to as an SpCell configuration information element or an SpCell configuration.

[0110] The CellGroupConfig information element may include a SCellConfig information element for each SCell as information used to configure parameters for one or more SCells in the cell group. The SCellConfig information element may be referred to as a SCell configuration information element or a SCell configuration.

[0111] The SpCellConfig information element contains UE specific parameters related to the SpCell. The ServingCellConfig information element may be included as information used to configure the UE specific parameters for the SCell. The CellGroupConfig information element may include the following information to configure the UE specific parameters for the SpCell and each SCell: A ServingCellConfig information element may be included for each serving cell.

[0112] The SpCellConfig information element is an information element that contains parameters required for the process of synchronous reconfiguration from the source SpCell to the target SpCell. If the SpCellConfig information element of the MCG includes a Reconfiguration with Sync information element, the process of synchronous reconfiguration to the target SpCell may be a handover. If the SpCellConfig information element of the SCG includes a Reconfiguration with Sync information element, In this case, the process of synchronous reconfiguration to the target SpCell may be a PSCell addition or a PSCell modification.

[0113] The synchronized reconfiguration information element and the SCellConfig information element include the ServingCellConfigCommon information element as information used to configure cell specific parameters of the serving cell. The ServingCellConfigCommon information element may include parameters that are typically obtained from the SSB, MIB, or one or more SIBs of a cell when a terminal device accesses the cell from an idle state.

[0114] The reconfiguration information element with synchronization may include, for example, information on the value of C-RNTI used in the cell group of the target SpCell. The reconfiguration information element with synchronization may include, for example, information required for performing a non-contention random access procedure in the target SpCell.

[0115] The ServingCellConfigCommon information element contains the physical cell identifier (physCellId) of the cell. It's okay to be there.

[0116] The ServingCellConfigCommon information element contains cell-specific (cell-common) downlink parameters. The DownlinkConfigCommon information element may be included as information providing the downlink common configuration. The DownlinkConfigCommon information element is also referred to as downlink common configuration.

[0117] The ServingCellConfigCommon information element contains cell-specific (cell-common) uplink parameters. The UplinkConfigCommon information element may be included as information providing the uplink common configuration. The UplinkConfigCommon information element is also referred to as uplink common configuration.

[0118] The ServingCellConfigCommon information element specifies the configuration for all uplink transmissions in the cell. It may include the value of N_{TA,offset} to be applied to the

[0119] The ServingCellConfigCommon information element may include an NTN-Config information element as information required for connecting to a network via NTN access.

[0120] The NTN-Config information element may include cell ephemeris information, parameters used for timing adjustment of uplink transmissions, and / or uplink synchronization validity period information. The uplink synchronization validity period information is transmitted to the terminal device without the need to update the uplink synchronization assistance information included in the NTN-Config information element. The uplink synchronization validity period information may be a parameter named ntn-UlSyncValidityDuration. The uplink synchronization auxiliary information may include the ephemeris information and / or the timing of the uplink transmission. The parameters used for tuning may be included.

[0121] The DownlinkConfigCommon information element may include a FrequencyInfoDL information element as basic information regarding a downlink carrier and transmission on the downlink carrier. For example, , the FrequencyInfoDL information element may include frequency information of the SSB.

[0122] The DownlinkConfigCommon information element contains the initial downlink BWP of the cell. The BWP-DownlinkCommon information element may be included as part of the BWP configuration. The information element is also referred to as downlink BWP common configuration.

[0123] The BWP-DownlinkCommon information element may include a BWP information element as information for setting generic parameters of the BWP.

[0124] The BWP-DownlinkCommon information element may include a PDCCH-ConfigCommon information element as information for configuring cell-specific parameters for the PDCCH of this BWP. The PDCCH-ConfigCommon information element is also referred to as a PDCCH common configuration.

[0125] The BWP-DownlinkCommon information element may include a PDSCH-ConfigCommon information element as information for configuring cell-specific parameters for the PDSCH of this BWP. The PDSCH-ConfigCommon information element is also referred to as a PDSCH common configuration.

[0126] The PDCCH-ConfigCommon information element includes common search space (CSS) #0 As information for setting the parameters, a SearchSpaceZero information element may be included. This SearchSpaceZero information element may be included in the PDCCH-ConfigCommon information element only if the BWP is an initial downlink BWP.

[0127] The PDCCH-ConfigCommon information element may include a ControlResourceSetZero information element as information for setting parameters of a common CORESET#0 used in one or more common search spaces and one or more UE-specific search spaces. This ControlResourceSetZero information element is included when the BWP is initialized. It may be included in the PDCCH-ConfigCommon information element only in the case of downlink BWP.

[0128] The PDCCH-ConfigCommon information element is used to configure additional common CORESET parameters. The information may include a ControlResourceSet information element.

[0129] The PDCCH-ConfigCommon information element may include a list (commonSearchSpaceList) of information elements (SearchSpace information elements) indicating the configuration of one or more additional CSSs.

[0130] The PDCCH-ConfigCommon information element includes information (searchSpaceSIB1) indicating which CSS in the commonSearchSpaceList the search space setting for the system information (SIB1) is. may be included.

[0131] The PDCCH-ConfigCommon information element may include information (searchSpaceOtherSystemInformation) indicating which CSS in the commonSearchSpaceList the search space configuration for system information (SIB2 and subsequent information) is.

[0132] The PDCCH-ConfigCommon information element may include information (pagingSearchSpace) indicating which CSS in the commonSearchSpaceList is used as the search space setting for the paging message.

[0133] Each of the above information elements may include information other than the information described above.

[0134] In order to execute the synchronization reconfiguration, the terminal device may perform some or all of the following processes RWS (A) to (E). This may be restated as "implementing" or "triggering a synchronization reconfiguration." (Processing RWS) (A) If the frequencyInfoDL information element is included in the synchronized reconfiguration information element, The target SpCell is determined to be a cell identified by the physical cell identifier included in the synchronization reconfiguration information element at the SSB frequency indicated in the frequencyInfoDL information element. If the synchronization reconfiguration information element does not include the frequencyInfoDL information element, the target SpCell is determined to be a cell identified by the physical cell identifier included in the synchronization reconfiguration information element at the SSB frequency indicated in the frequencyInfoDL information element. The physical cell identifier included in the reconfiguration information element with synchronization is on the same SSB frequency as the SpCell. It is determined that the cell is the one to be processed. (B) Initiate downlink synchronization to the target SpCell. (C) If the target does not have the timing information required for the random access procedure, Get the MIB of the target SpCell. (C) Reset the MAC entity of the cell group that is to be resynchronized. (D) The value of the new UE identifier (newUE-Identity) included in the synchronized reconfiguration information element is It is applied as the C-RNTI for the cell group to be reconfigured. (E) The lower levels of the RRC layer are configured according to the SpCell common configuration (ServingCellConfigCommon information element). Set up the network interface (PHY, etc.).

[0135] Measurement will now be described. In the following description, the base station device may be read as a network. The base station device may configure the terminal device in an RRC connected state to perform measurements. The base station device may configure the terminal device to report measured results. The base station device may notify the terminal device of RRC signaling to perform synchronization reconfiguration based on the reported measurement results. In addition or instead, the base station device may The station device may configure the terminal device to perform conditional reconfiguration, which will be described later, based on the reported measurement result. The measurement configuration is transmitted to the base station device by RRC signaling (e.g., an RRCReconfiguration message or an RRCResume message). It may be provided from the station device to the terminal device.

[0136] The base station device may configure the terminal device to perform, for example, the following types of measurements: (a) NR measurement (b) Inter-Radio Access Technology (Inter-RAT) Measurements on E-UTRA Frequencies (c) Inter-RAT measurements for UTRA-FDD frequencies

[0137] The base station configures the terminal to report the following measurement information, for example based on SSB: That's fine. (a) Measurement results for each SSB (b) Cell-by-cell measurement results based on SSB (c) SSB Index

[0138] The base station device may configure the terminal device to report the following measurement information, for example based on CSI-RS: (a) Measurement results per CSI-RS resource (b) Measurement results per cell based on CSI-RS (c) CSI-RS Resource Measurement Identifier

[0139] The measurement configuration is sent to the terminal device via an information element (IE) of RRC signaling. The IE indicating the measurement configuration (measurement configuration IE) may include one or more measurement object IEs indicating measurement objects, one or more reporting configuration IEs indicating a reporting configuration, one or more measurement identities used to link the measurement objects and the reporting configuration, a quantity configuration IE indicating a quantity configuration, a measurement gap configuration IE indicating a measurement gap configuration, Serving cell quality threshold configuration (s-Measure configuration), including some or all of That's fine.

[0140] <Quantity Config> The quantityConfig specifies the L3 filtering coefficient when the measurement objects are NR and / or E-UTRA. The L3 filtering coefficient specifies the ratio between the latest measurement result and the past filtered measurement result. The filtering result is used for event evaluation in the terminal device. It is okay to do so.

[0141] <Measurement gap setting (measGapConfig)> The measurement gap configuration includes information on the length and period of the measurement gap. The measurement gap configuration may be set independently for each terminal device or for each predetermined frequency range.

[0142] <Measurement Identifier (measId)> The measurement identifier is used to associate (or associate or link) a measurement target with a reporting configuration. Specifically, it links a measurement target identifier (measObjectId) for uniquely identifying each measurement target with a reporting configuration identifier (reportConfigId) for uniquely identifying each reporting configuration. One measurement target identifier and one reporting configuration identifier are associated with each other in the measurement identifier. The measurement configuration is added by adding a measurement identifier, a measurement target, and / or a reporting configuration. It may be configured to be editable and deletable.

[0143] <Measurement objects> Measurement objects may be defined per RAT, frequency, and / or subcarrier spacing.

[0144] The measurement object IE includes a measurement object NR (measObjectNR) IE indicating information of a measurement object whose measurement object is NR associated with a measurement object identifier, and a measurement object NR (measObjectNR) IE indicating information of a measurement object whose measurement object is E-UTRA. The measurement object may include a measurement object EUTRA (measObjectEUTRA) IE indicating information of the measurement object when the measurement object is UTRA, and a measurement object UTRA (measObjectUTRA) IE indicating information of the measurement object when the measurement object is GERAN. The measurement object GERAN (measObjectGERAN) IE indicates the information of the measurement object to be measured. A part or whole of the measurement object CDMA2000 (measObjectCDMA2000) IE indicating the information of the measurement object to be It may include a part.

[0145] The NR IE to be measured includes the frequency information (ssbFrequency) of the block (SSB) containing the synchronization signal, The measurement result may include some or all of the following: subcarrier spacing (ssbSubcarrierSpacing), information on a list of cells to be measured, information on a blacklist to be excluded from measurement, and information on a whitelist to be measured.

[0146] The information on the list of cells to be measured includes information on the cells to be the subject of event evaluation and measurement reporting. The information on the list of cells to be measured includes physical cell ID, cell individual offset (cellIndividualOffset, neighbor cell ID, etc.). The measurement offset value to be applied to the measurement loop may be included.

[0147] <Reporting configurations> The reporting configuration IE may include a reporting configuration NR (reportConfigNR) IE and / or a reporting configuration InterRAT (reportConfigInterRAT) IE associated with a reporting configuration identifier (reportConfigId).

[0148] The report configuration identifier is an identifier used to identify a report configuration for measurements. The report configuration IE may include information for NR measurement reports, information for measurement reports for RATs other than NR (part or all of UTRA, GERAN, CDMA2000, E-UTRA), and information for NR sidelink measurement reports. The report configuration NR (reportConfigNR) IE, which is an information element used for NR measurement reports, may include information indicating a report type. The report type may include periodic (periodic), The report type may include event triggered, event notification, and so on. In the case of a trigger, the reporting configuration NR IE may include information such as triggering criteria.

[0149] In addition, the reporting configuration NR IE includes an event identifier (eventId), a trigger quantity (triggerQuantity), Hysteresis, trigger time, report quantity, maximum The report configuration NR IE may include some or all of the following: maxReportCells, report interval, and report amount. The trigger conditions for the events used in the process may be included.

[0150] <About event trigger conditions> There are multiple event trigger conditions defined for the measurement report, each of which may have an entering condition and a leaving condition. A terminal device that satisfies a joining condition for a specified event may transmit a measurement report to the base station device. Also, a terminal device that satisfies a leaving condition for an event specified by the base station device may transmit a measurement report to the base station device if the base station device has set a report to be triggered when the leaving condition is satisfied (if the report setting IE includes reportOnLeave). You may send it.

[0151] In addition, for reporting configurations for non-NR RATs, several triggering criteria for events used to report measurements for non-NR RATs are defined. For example, if the measurement result of the neighboring cell (other RAT) is better than the threshold b1_Threshold set for each RAT after applying each parameter, the event B1 occurs. Event B2 may occur if the measurement result of the neighboring cell (other RAT) is worse than the threshold b2_Threshold1 after application of the respective parameters and the measurement result of the neighboring cell (other RAT) is better than the threshold b2_Threshold2 configured per RAT after application of the respective parameters. Information about these events may be included in the report Config InterRAT IE.

[0152] Measurement reporting will now be described. The terminal device transfers the measurement result to the network based on the measurement configuration. For each measurement identifier for which the measurement report procedure is triggered, the terminal device sets the measurement result in a measurement report message. The measurement result may include information on the measurement identifier for which the measurement report is triggered. The measurement result may also include information on the RSRP, RSRQ, and / or average SINR of the serving cell derived based on the reference signal. The measurement result may include information of the identifier of the serving cell. The measurement result may also include information of the RSRP, RSRQ, and / or average SINR of the neighboring cell derived based on the reference signal. The measurement result may also include information of the identifier of the neighboring cell. The reference signal may be an SSB, a CSI-RS, or another signal. It's fine.

[0153] Explain conditional reconfiguration. The terminal device configures one or more conditional reconfiguration information elements for the terminal device, whereby the network configures candidate target SpCells, each associated with the conditional reconfiguration information element, for the terminal device. The terminal device evaluates the state of the configured candidate target SpCell. The terminal device performs the evaluation and selects conditional RRC reconfiguration information included in the conditional reconfiguration information element associated with one or more candidate target SpCells that satisfy an execution condition. The terminal device may also hold a list of entries (VarConditionalReconfig) for conditional reconfiguration, which will be described later.

[0154] A conditional reconfiguration may be referred to as a conditional handover when the candidate target SpCell is an SpCell (i.e., a PCell) of an MCG. A conditional reconfiguration may also be referred to as a conditional handover when the candidate target SpCell is an SpCell (i.e., a PCell) of an SCG. In the case of an SpCell (i.e., a PSCell), this may be referred to as a conditional PSCell addition and / or a conditional PSCell modification.

[0155] The terminal device, as a setting process for conditional resetting, receives information regarding conditional resetting (e.g., condition Based on the reception of the conditional reconfiguration information element, When the entry deletion list (condReconfigToRemoveList) is included, the terminal device may delete (remove) the conditional reconfiguration configuration specified in the entry deletion list from the configuration held by the terminal device. Specifically, when 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.

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

[0157] When the information regarding the conditional reconfiguration includes an entry add / modify list (condReconfigToAddModList) as a configuration process for conditional reconfiguration, the terminal device may add or modify the conditional reconfiguration configuration included in the entry add / modify list to the configuration held by the terminal device. The entry add / modify list may be a list of one or more conditional reconfiguration information elements. Each entry may be configured by the conditional reconfiguration information element. The conditional reconfiguration information element may include an entry identifier, an execution condition, and a conditional RRC reconfiguration information element. stomach.

[0158] Specifically, when each entry identifier included in the entry addition / modification list exists in an entry of the entry list, the terminal device may perform the following processing (A) and / or (B). (A) If an entry included in the addition / modification list of an entry includes an execution condition (condExecutionCond), the execution condition of an entry in the entry list that matches the entry identifier of this entry is replaced with the execution condition included in the addition / modification list of that entry. (B) If an entry included in the entry addition modification list includes a conditional RRC reconfiguration information element (condRRCReconfig), an entry that matches the entry identifier of this entry The conditional RRC reconfiguration information element in the list is added to the additional modification list of that entry. Replace it with the RRC reconfiguration information element with

[0159] Furthermore, if an entry identifier included in the entry addition / modification list is not included in the entry list, the terminal device may add to the entry list a new entry corresponding to the entry identifier not included in the entry list.

[0160] The deletion list of entries may be a list of one or more entry identifiers to be deleted. Each entry included in the addition / modification list of entries includes an entry identifier and may additionally include an execution condition and / or a conditional RRC reconfiguration information element. Each entry may be associated with one of one or more candidate target SpCells. The entry identifier is used to identify each entry of the CHO, CPA, and CPC. The entry list may include one or more entries. Each entry may include an entry identifier, one or more execution conditions, and one conditional RRC reconfiguration information element. If the terminal does not contain any birds, it may keep an empty list.

[0161] The execution condition may be a condition that needs to be satisfied to trigger execution of the conditional reconfiguration. For example, a measurement identifier may be specified as the execution condition. Furthermore, the conditional RRC reconfiguration information element of the measurement event may be a message related to reconfiguration of the RRC connection that is applied when the execution condition is satisfied. The message may be a message used to connect to a candidate target SpCell.

[0162] The terminal device may evaluate the execution conditions of the entries included in the entry list held by the terminal device. If the entry list held by the terminal device is empty or if the terminal device does not hold an entry list, the execution conditions do not need to be evaluated.

[0163] Execution of a conditional reconfiguration may mean, for example, that the terminal device evaluates whether a join condition or leave condition of a measurement event associated with a measurement identifier indicated by an execution condition of an entry included in an entry list held by the terminal device is satisfied, and when the join condition of one or more measurement events is satisfied, applies a conditional RRC reconfiguration information element included in an entry including the execution condition. Applying a conditional RRC reconfiguration information element may mean executing an RRC reconfiguration procedure using the conditional RRC reconfiguration information element.

[0164] The terminal device transmits conditional RRC reconfiguration information of each entry identified by the entry identifier. If the element includes a synchronous reconfiguration information element, a cell whose value matches the physical cell identifier indicated in the synchronous reconfiguration information element may be determined to be an applicable cell. .

[0165] The terminal device may determine that a measurement event associated with a measurement identifier indicated in a certain execution condition is satisfied when an entry condition of the measurement event associated with the applicable cell is satisfied. The terminal device may determine that a measurement event associated with the measurement identifier is not satisfied when a leave condition of the measurement event associated with the measurement identifier indicated in a certain execution condition is satisfied for the applicable cell. When the terminal device determines that all measurement events for a certain applicable cell are satisfied, it may consider the cell as a triggered cell and perform conditional reconfiguration.

[0166] If there are multiple entries that satisfy the execution condition, the terminal device selects one entry from the multiple entries and applies the conditional RRC reconfiguration information element of the selected entry. It may be used.

[0167] Various embodiments of the present invention will be described based on the above description. Note that the above-described processes may be applied to processes that are omitted in the following description.

[0168] Fig. 5 is a block diagram showing the configuration of a terminal device (UE 122) in this embodiment. In order to avoid a complicated explanation, Fig. 5 shows only main components closely related to this embodiment. Show only.

[0169] The UE 122 shown in FIG. 5 receives control information (DCI, MAC control elements, RRC signaling, etc.) from the base station device. A receiving unit 500 receives the control information, and performs processing according to parameters included in the received control information. The base station device may be the eNB 102 or the gNB 108. In addition, the processing unit 502 may include various layers (for example, a physical layer, a MAC layer, an RLC layer, a PDCP layer, an SDAP layer, etc.). In other words, the processing unit 502 may include some or all of the functions of a physical layer processing unit (PHY processing unit), a MAC layer processing unit (MAC processing unit), an RLC layer processing unit (RLC processing unit), a PDCP layer processing unit (PDCP processing unit), an SDAP processing unit (SDAP processing unit), an RRC layer processing unit (RRC processing unit), and a NAS layer processing unit (NAS processing unit).

[0170] FIG. 6 is a block diagram showing the configuration of a base station device in this embodiment. In order to avoid clutter, FIG. 6 shows only the main components closely related to this embodiment. This base station device may be an eNB 102 or a gNB 108.

[0171] The base station apparatus shown in Fig. 6 includes a transmitter 600 that transmits control information (DCI, RRC signaling, etc.) to the UE 122, a processor 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to the UE 122, thereby causing the processor 502 of the UE 122 to process it, and a receiver 604 that receives the control information (UCI, RRC signaling, etc.) from the UE 122. The processor 602 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processor 602 includes a physical layer processor, a MAC layer processor, an RLC It may include some or all of a layer processing unit, a PDCP layer processing unit, an SDAP processing unit, an RRC layer processing unit, and an NAS layer processing unit.

[0172] An example of the processing of the terminal device in this embodiment will be described with reference to FIG.

[0173] FIG. 9 is a diagram showing an example of processing of the terminal device (UE 122) in this embodiment. The processing unit 502 receives first information and / or second information from the base station device (step S900). The processing unit 502 of the UE 122 adds a first identifier to an RRC reconfiguration information element included in the received second information. It is determined whether or not a distinguishing character is included (step S902). The processing unit 502 of the UE 122 performs an operation based on the determination (step S904).

[0174] The first information may include one or more information elements about a cell, and each of the information elements about a cell may be identified by a first identifier. Furthermore, each of the information elements about a cell may be an information element including settings related to different cells. Furthermore, the information element about a cell may be an information element used to set cell-specific parameters. For example, the information element about a cell may include the SSB, MIB, and / or the cell's information when the terminal device accesses the cell from an idle state. The information element may include parameters typically obtained from one or more SIBs. For example, the information element for the cell may be an information element (ServingCellConfigCommon information element) used to configure cell-specific parameters of the cell in the terminal device. The information element for the cell is the synchronous reconfiguration to the cell. The reconfiguration with Sync information element is used for The first information may be one or more information elements included in the SIB. In addition, the first information may be information that is broadcast using a BCCH in the serving cell of the terminal device, information that is notified to the terminal device using a DCCH, or information that is notified to the terminal device using an MCCH. For example, the first information may be broadcast using SIB3 and / or SIB4, which are SIBs that broadcast information on neighboring cells, in the serving cell of the terminal device. Also, for example, the first information may be broadcast using other SIBs. In this case, For example, the SIB may include a list of neighboring cell information, Each may include one of the information elements relating to the cell.

[0175] In addition, the first information includes information indicating whether a part or all of the first information is valid. In addition, or instead, the information element regarding the cell may include information (first validity determination information) used by the terminal device to determine whether the cell is invalid. The terminal device determines whether some or all of the information elements for the cell are valid or invalid. In addition to or instead of that, when the first information is notified by the SIB, the information notified by the SIB1 may include information (second validity determination information) used to determine whether the first information is valid or not. When a value of a Value Tag for an SIB broadcasting the first information, among one or more Value Tags (Value Tag fields) that are stored in the terminal device, is different from a value of a Value Tag for an SIB broadcasting the first information that is stored in the terminal device, the terminal device reports the first information that is stored in the terminal device. The terminal may determine that the SIB information it receives is invalid. The terminal device may determine that the first information it holds is invalid. Furthermore, the terminal device may determine that it does not hold a valid information element regarding the cell based on the determination that the first information is invalid. Furthermore, the terminal device may determine that it holds a valid information element regarding the cell based on the determination that the first information is valid.

[0176] The first validity determination information may include first timer information. The entity may start or restart a timer (first validity determination timer) based on acquiring the first timer information from the first information. The terminal device may determine that the first validity determination timer has expired when the first validity determination timer has elapsed a period (time) set based on the first timer information. The terminal device may determine that a part or all of the first information held by the terminal device is invalid based on the expiration of the first validity determination timer. Also, the terminal device may determine that a part or all of the first information held by the terminal device is invalid based on the stopping of the first validity determination timer. The first validity determination timer may be stopped by the terminal device based on the expiration of the first validity determination timer. Also, the first validity determination timer may be stopped by the terminal device based on other conditions. In other words, the terminal device may determine that a part or all of the first information held by the terminal device is valid based on the first validity determination timer being running (not stopped). For example, the terminal device may determine that all information elements regarding cells contained in the first information and held by the terminal device are invalid based on the first validity determination timer being stopped.

[0177] The second validity determination information may include second timer information. The entity may start or restart a timer (second validity determination timer) based on acquiring the second timer information from the first information. The terminal device may determine that the second validity determination timer has expired when the second validity determination timer has elapsed a period (time) set based on the second timer information. The terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on the expiration of the second validity determination timer. Also, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on the stop of the second validity determination timer. The second validity determination timer may be stopped by the terminal device based on the expiration of the second validity determination timer. Also, the second validity determination timer may be stopped by the terminal device based on other conditions. In other words, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are valid based on the second validity determination timer being running (not stopped). Furthermore, the information element regarding the cell may not include the second validity determination timer. The terminal device may determine that the first information is valid based on the fact that the information element regarding the cell does not include the second validity determination timer. Furthermore, when the information element regarding the cell includes the second validity determination timer, the terminal device may ignore the second validity determination timer. In this way, the terminal device may determine that the first information is valid.

[0178] In addition, both the first validity determination timer and the second validity determination timer are installed in a terminal device. When the second validity determination timer is maintained, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are invalid based on the expiration or stopping of any of the timers. In other words, the terminal device may determine that some or all of the information elements related to the cell held by the terminal device are valid based on the fact that both timers are running (not stopped). In addition, the terminal device may discard the information elements related to the cell held by the terminal device based on the expiration or stopping of the second validity determination timer. In other words, the terminal device may consider that it does not hold the information elements related to the cell by discarding the information elements related to the cell held by the terminal device based on the expiration or stopping of the second validity determination timer.

[0179] In addition, if the terminal device has not acquired the first information in the current serving cell, it may determine that the first information held by the terminal device is invalid, and in addition or instead, it may determine that the terminal device does not hold valid first information.

[0180] In addition, if the terminal device has not acquired the first information in the current serving cell, it may determine that the information element regarding the cell held by the terminal device is invalid, and in addition or instead, it may determine that the terminal device does not hold a valid information element regarding the cell.

[0181] The information element about the cell may be, for example, a ServingCellConfigCommon information element. Alternatively, the information element regarding the cell may be, for example, a ServingCellConfigCommon information element. The information element about the cell may include information elements that include the The information element related to the cell may include information required for connecting to a network. For example, the information element related to the cell may include an NTN-Config information element. In this case, for example, the timer information included in the second validity determination information may be uplink synchronization validity period information, or may be other information different from the uplink synchronization validity period information. When the uplink synchronization validity period information is the timer information, the terminal device may start a second validity determination timer and determine that the second validity determination timer has expired based on the lapse of a period (time) indicated by the uplink synchronization validity period information.

[0182] The first identifier may be an identifier included in an information element about the cell. The first identifier may be an identifier that is not included in an information element about the cell, but is associated with an information element about the cell and is included in the first information and notified. The first identifier may be an identifier that is not included in the first information and indicates the number of one or more set information elements about the cell. For example, the first identifier may be a physical cell identifier. For example, the first identifier may be composed of any combination or all combinations of a physical cell identifier, a frequency, and a subcarrier interval. For example, the first identifier may be an identifier that is uniquely associated with any combination or all combinations of a physical cell identifier, a frequency, and a subcarrier interval. For example, when the maximum number of information elements about a cell included in the first information is two or less, the first identifier may be 1-bit information, and when the maximum number of information elements about a cell included in the first information is four or less, the first identifier may be 2-bit information.

[0183] The second information may be a message including an RRC reconfiguration information element, and The second information may be, for example, an RRC reconfiguration message. The second information may include a reconfiguration information element with synchronization. For example, the second information may be an RRC reconfiguration message. For example, the second information is a conditional RRC reconfiguration information element used in conditional reconfiguration. Also, for example, the second information may be transmitted to the terminal device by other RRC signaling. The RRC message may be an information element or an RRC message notified to the device.

[0184] An example of the operation of the UE 122 in step S904 will be described. When it is determined that the RRC reconfiguration information element included in the second information includes the first identifier, When the terminal device determines that the information element regarding the cell of the first information indicated by the first identifier held by the terminal device is valid, the terminal device determines that the information element regarding the cell of the first information indicated by the first identifier is valid, and performs the above-mentioned processing for the lower layer of the RRC layer (for example, the PDCP layer, the RLC layer, , a MAC layer, and / or a PHY layer). In addition, when the processing unit 502 of the UE 122 determines that the RRC reconfiguration information element included in the received second information does not include the first identifier, In this case, if the second information includes an information element about the cell, a lower layer (e.g., a PDCP layer, an RLC layer) of the RRC layer is determined according to the information element about the cell included in the second information. The processing unit 502 of the UE 122 may apply a value of a new UE identifier (newUE-Identity) included in a synchronized reconfiguration information element of the second information as a C-RNTI for a cell group to be subjected to synchronous reconfiguration, regardless of whether a first identifier is included in an RRC reconfiguration information element included in the received RRC signaling. The processing unit 502 of the UE 122 may apply a value of a new UE identifier (newUE-Identity) included in a synchronized reconfiguration information element of the second information as a C-RNTI for a cell group to be subjected to synchronous reconfiguration, regardless of whether a first identifier is included in an RRC reconfiguration information element included in the received second information. If it is determined that the first identifier is included in the cell, the terminal device does not hold an information element regarding the cell indicated by the first identifier, or if it is determined that the information element regarding the cell of the first information indicated by the first identifier held by the terminal device is invalid, the following process (A) is performed. (F) may be carried out in whole or in part. (A) All RRC reconfiguration information elements included in the second information are not applied (ignored). (B) Generate RRC signaling and transmit it to the base station device. (C) It is determined that a reconfiguration failure or a handover failure has occurred. (D) Initiate the RRC re-establishment procedure. (E) Reacquiring the first information in a serving cell. (F) an information element equivalent to the information element for the cell of the first information indicated by the first identifier; Information is obtained in a cell of the first information indicated by the first identifier.

[0185] In the above process (B), the RRC signaling is, for example, to inform the network of the completion of the RRC reconfiguration. In this case, the processing unit 502 of the UE 122 may include in the RRCReconfigurationComplete message information indicating that the UE does not hold an information element related to the cell indicated by the first identifier included in the second information. In addition, the RRC signaling may be, for example, a message used to notify the network of the auxiliary information of the UE. The UE Assistance Information message was used to notify the In this case, the processing unit 502 of the UE 122 may include the above-mentioned in the UEAssistanceInformation message. The second information may include information indicating that an information element related to a cell indicated by a first identifier included in the second information is not held. Also, the information indicating that an information element related to a cell indicated by a first identifier included in the second information is not held may be information indicating that an information element related to a cell indicated by a first identifier included in the second information is not acquired.

[0186] In step S904, the terminal device may set a period (time) applied to the timer T304, which is a timer used to determine failure of synchronization reconfiguration, based on a parameter (e.g., parameter t304) for setting the timer T304 included in the synchronization reconfiguration information element of the second information. The timer T304 is set when the terminal device receives an RRC message including the synchronization reconfiguration information element of the second information including a parameter for setting the timer T304. Based on this, the value of the period (time) indicated by the parameter for setting the timer T304 may be set and started or restarted by the terminal device. The terminal device may set the timer T304 based on the lapse of the period (time) set by the timer T304. The terminal device may determine that the synchronization reconfiguration has failed based on the expiration of the timer T304. Here, the processing unit 502 of the UE 122 determines that the RRC reconfiguration information element included in the received second information includes a first identifier, and Based on the determination that the terminal device does not hold an information element regarding the cell indicated by the first identifier or that the information element regarding the cell of the first information indicated by the first identifier held by the terminal device is invalid, a value obtained by adding a specific period (time) to the value of the period (time) indicated by the parameter for setting the timer T304 may be used as the value to be set in the timer T304. For example, the specific period (time) may be a default period (time) or may be a period (time) set by the base station device through RRC signaling. The device sets a timer T304 when executing the above process (E) and / or process (F). As the value, a value obtained by adding the specific period (time) to the value of the period (time) indicated by the parameter for setting the timer T304 may be used.

[0187] In the above description, the processing unit 502 of the UE 122 may be a processing unit that performs processing of the RRC layer. .

[0188] In addition, in the above description, "valid" and "not invalid" may be interchangeable. In addition, in the above description, "invalid" and "not valid" may be interchangeable.

[0189] Furthermore, unless otherwise specified, the radio bearer in the above description may be a DRB, an SRB, or a combination of a DRB and an SRB.

[0190] In the above explanation, "link to" and "correspond to" are used. The terms "associate with" and the like may be used interchangeably.

[0191] In the above explanation, "A is confirmed," "A is set," "A is included," etc. Expressions such as the above may be interchangeable.

[0192] In the above description, "transition from X to Y" may be rephrased as "X becomes Y." Also, in the above description, "cause a transition" may be rephrased as "determine a transition."

[0193] In addition, in each of the process examples or process flow examples described above, some or all of the steps may not be executed. In each of the process examples or process flow examples described above, the order of the steps may be different. In each of the process examples or process flow examples described above, some or all of the processing in each step may not be executed.

[0194] In the above explanation, "A may be replaced with B" may mean replacing A with B, as well as replacing B with A. In the above explanation, when it is written that "C may be D" and "C may be E", it may also mean that "D may be E". In the above explanation, when it is written that "F may be G" and "G may be H", it may also mean that "F may be H".

[0195] The program that runs on the device according to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or information handled by the program is temporarily loaded into a volatile memory such as a Random Access Memory (RAM) during processing, or is stored in a flash memory. The information is stored in non-volatile memory such as a memory or a hard disk drive (HDD) and is retrieved by the CPU as needed. Reading, modifying and writing are performed by this.

[0196] It should be noted that a part of the device in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the control function. The "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

[0197] Furthermore, the term "computer-readable recording medium" includes those that dynamically hold a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. The program may be for implementing part of the above-mentioned functions, or may be a program that already has the above-mentioned functions recorded in a computer system. It may be possible to realize this in combination with

[0198] Also, each functional block or feature of the device used in the above-described embodiment may be implemented or executed by an electric circuit, i.e., typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described herein may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable logic circuit (PLC), or a combination of such circuits. The general purpose processor may include a general purpose gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor, or each of the aforementioned circuits, may be composed of digital circuits or analog circuits. Also, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, an integrated circuit based on that technology may be used.

[0199] It should be noted that the present embodiment is not limited to the above-mentioned embodiment. In the embodiment, an example of the device is described, but the present 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 of AV devices, kitchen devices, cleaning / washing devices, air conditioners, office devices, vending machines, and other household appliances.

[0200] Although this embodiment has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes within the scope of the gist of this embodiment are also included. In addition, 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 are replaced with elements that have the same effect are also included. [Explanation of symbols]

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

Claims

1. A terminal device, a receiving unit that receives the first information and / or the second information from a base station device; A processing unit that performs RRC layer processing, the first information includes one or more information elements relating to a cell, each of the information elements relating to a cell being identified by a first identifier; Each of the information elements regarding the cell includes information for the terminal device to determine the validity of the information element regarding the cell, The second information includes an RRC reconfiguration parameter including some or all of the parameters for synchronization reconfiguration. Contains certain information elements, The processing unit includes: determining whether the second information includes the first identifier; When the second information includes the first identifier, determining whether a valid information element relating to the cell indicated by the first identifier is held; Based on the determination that the valid information element regarding the cell indicated by the first identifier is held, the PDCP layer, the RLC layer, the MAC layer, and / or the PHY layer are configured according to the held information element regarding the cell indicated by the first identifier. Terminal device.

2. A method applied to a terminal device, comprising: receiving first information and / or second information from a base station device; determining whether the second information includes the first identifier; When the second information includes the first identifier, determining whether a valid information element for the cell indicated by the first identifier is held; and configuring a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer in accordance with the information element related to the cell identified by the first identifier, based on the determination that the information element related to the valid cell identified by the first identifier is held; the first information includes one or more information elements relating to a cell, each of the information elements relating to a cell being identified by a first identifier; Each of the information elements regarding the cell includes information for the terminal device to determine the validity of the information element regarding the cell, The second information includes an RRC reconfiguration parameter including some or all of the parameters for synchronization reconfiguration. Contains certain information elements method.

3. An integrated circuit implemented in a terminal device, A function of receiving the first information and / or the second information from a base station device; determining whether the second information includes the first identifier; When the second information includes the first identifier, a function of determining whether a valid information element related to the cell indicated by the first identifier is held; Based on the determination that the terminal device holds a valid information element regarding the cell indicated by the first identifier, the terminal device is caused to perform a function of setting a PDCP layer, an RLC layer, a MAC layer, and / or a PHY layer in accordance with the information element regarding the cell indicated by the first identifier that is held; The first information includes one or more information elements relating to a cell, each of the associated information elements is identified by a first identifier; Each of the information elements regarding the cell includes information for the terminal device to determine the validity of the information element regarding the cell, The second information includes an RRC reconfiguration parameter including some or all of the parameters for synchronization reconfiguration. Contains certain information elements Integrated circuits.

Images