WO2024058073A1 - Terminal device, method, and integrated circuit - Google Patents

Abstract

This terminal device communicates with a base station device. The terminal device comprises: a reception unit that receives, from the base station device, a first configuration indicating information about one or a plurality of candidate cells; and an RRC processing unit. The RRC processing unit determines whether the terminal device is configured to provide information regarding whether a measurement gap for a target frequency band of NR is required. If it is determined that the terminal device is configured to provide the requirement information, the RRC processing unit determines whether the first configuration includes a second configuration for reporting whether a measurement gap is required in NR. If it is determined that the first configuration includes the second configuration, the RRC processing unit includes, in signaling indicating completion with respect to the first configuration, third information indicating whether a measurement gap is required in NR. If it is determined that the terminal device is not configured to provide the requirement information, or if it is determined that the first configuration does not include the second configuration, the RRC processing unit does not include the third information in the signaling indicating completion with respect to the first configuration.　

Description

Terminal device, method, and integrated circuit

The present invention relates to a terminal device, a method, and an integrated circuit.
This application claims priority to Japanese Patent Application No. 2022-146782 filed in Japan on September 15, 2022, the contents of which are incorporated herein.

The 3rd Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, is conducting technical studies and standardization for cellular mobile communication systems, including wireless access, core networks, services, etc. There is.

For example, E-UTRA (Evolved Universal Terrestrial Radio Access) is a radio access technology (Radio Access Technology: RAT) for 3.9th and 4th generation cellular mobile communication systems that has been studied and developed as a standard in 3GPP. Ta. Currently, 3GPP is still conducting technical studies and standardization for E-UTRA expansion technology. Note that E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and the extended technology is also referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

In addition, NR (New Radio, or NR Radio access) is being studied and standardized as a radio access technology (RAT) for 5th Generation (5G) cellular mobile communication systems in 3GPP. started. Currently, 3GPP is still conducting technical studies and standardization for NR expansion technology.

As an extended technology for NR, there is a serving cell change technology that allows a terminal device to move from the coverage area of one cell to the coverage area of another cell. This serving cell change is triggered by layer 3 (also referred to as RRC) measurements, and synchronized reconfiguration for serving cell change is triggered by RRC signaling. Compared to RRC signaling, layer 1 or layer 2 signaling has the advantage of low delay and low overhead. Therefore, studies have begun on techniques for changing serving cells triggered by layer 1 or layer 2 signaling (layer 1/layer 2 mobility enhancement techniques).

The details of measurements in Layer 1/Layer 2 mobility optimization technology are one of the considerations mentioned above. However, it remains unclear how the measurement specifications described in Non-Patent Document 7 are reflected in layer 1/layer 2 mobility optimization technology.

One aspect of the present invention has been made in view of the above circumstances, and one of the objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently control communication. .

In order to achieve the above object, one embodiment of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device that communicates with a base station device, which includes a receiving unit that receives a first setting indicating information about one or more candidate cells from the base station device, and an RRC processing unit. and, the RRC processing unit determines whether or not it is set to provide the terminal device with information on whether or not a measurement gap of a target frequency band of NR is provided, and provides the terminal device with the If it is determined that provision of necessity information is set, the RRC processing unit includes, in the first setting, a second setting for reporting whether or not a measurement gap is necessary in NR. If it is determined that the second setting is included in the first setting, the RRC processing unit includes a measurement gap in NR in the signaling indicating completion of the first setting. If it is determined that the terminal device is not set to provide the necessity information, including the third information indicating whether it is necessary, or if the second information is included in the first setting, If it is determined that the setting is not included, the RRC processing unit does not include the third information in the signaling indicating completion of the first setting.

Further, one aspect of the present invention is a terminal device that communicates with a base station device, and includes an RRC processing unit, and the RRC processing unit is configured to transmit a signal from a lower layer (layer 1/layer 2) to a serving cell to a candidate cell. When a change is instructed, it is determined whether the terminal device is set to be provided with information on the necessity of measurement gaps for the target frequency band of NR, and the terminal device is provided with the necessity information on the measurement gap of the NR target frequency band. If the RRC processing unit determines that the serving cell change is set to be provided, after the serving cell change, the RRC processing unit adds a third measurement gap indicating whether or not a measurement gap is required in the NR to the signaling indicating completion of the serving cell change. If it is determined that the provision of the necessity information to the terminal device is not set, including the information of The third information is not included.

Another aspect of the present invention is a method of a terminal device communicating with a base station device, wherein an RRC entity of the terminal device receives a first setting indicating information about one or more candidate cells from the base station device. a step in which the RRC entity determines whether or not it is configured to provide measurement gap information for a target frequency band of NR to the terminal device; , if the RRC entity determines that it is configured to provide the necessity information, the RRC entity configures a second configuration that causes the first configuration to report whether or not a measurement gap is required in the NR. a step of determining whether the second configuration is included in the first configuration; and if it is determined that the second configuration is included in the first configuration, the RRC entity includes a measurement in NR in signaling indicating completion for the first configuration; including a step of including third information indicating whether or not a gap is necessary; and if it is determined that the terminal device is not set to provide the necessity information, or in the first setting; If it is determined that the second configuration is not included, the RRC entity does not include the third information in signaling indicating completion of the first configuration.

Another aspect of the present invention is a method for a terminal device to communicate with a base station device, wherein an RRC entity of the terminal device receives an instruction from a lower layer (layer 1/layer 2) to change a serving cell to a candidate cell. a step of determining whether provision of necessity information of a measurement gap of a target frequency band of NR is set to the terminal device, and providing the necessity information to the terminal device; If the RRC entity determines that a measurement gap is required in the NR after the serving cell change, the RRC entity includes third information indicating whether a measurement gap is required in the NR in signaling indicating completion for the serving cell change. If the RRC entity determines that provision of the necessity information to the terminal device is not configured, the RRC entity includes the provision of the necessity information to the terminal device in the signaling indicating completion of the serving cell change after the serving cell change. and a step of not including the information of No. 3.

Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, wherein an RRC entity of the terminal device indicates information about one or more candidate cells from the base station device. a function of receiving a first configuration, and a function of determining whether the RRC entity is configured to provide the terminal device with information on whether or not a measurement gap of a target frequency band of NR is required; When determining that the terminal device is configured to provide the necessity information, the RRC entity causes the first configuration to report whether or not a measurement gap is required in NR. and a function for determining whether or not the second configuration is included in the first configuration, and when it is determined that the second configuration is included in the first configuration, the RRC entity sends signaling indicating completion of the first configuration. , if it is determined that the function to include the third information indicating whether or not a measurement gap is necessary in the NR and the provision of the necessity information to the terminal device is not set, or If it is determined that the second configuration is not included in the first configuration, the RRC entity performs a function of not including the third information in signaling indicating completion of the first configuration.

Further, one aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, wherein an RRC entity of the terminal device transmits information from a lower layer (layer 1/layer 2) to a serving cell to a candidate cell. When a change is instructed, a function is provided to determine whether the terminal device is set to provide measurement gap information for the target frequency band of NR, If the RRC entity determines that providing information is configured, after the serving cell change, the RRC entity may include a measurement gap in the NR indicating whether a measurement gap is required in the signaling indicating completion for the serving cell change. If the RRC entity determines that the function of including the information in step 3 and providing the necessity information to the terminal device is not set, after the serving cell change, the RRC entity sends signaling indicating completion of the serving cell change. and a function of not including the third information.

Note that these comprehensive or specific aspects may be realized by a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium. It may be realized by any combination of the following.

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

FIG. 1 is a schematic diagram of a communication system according to the present embodiment. FIG. 2 is a diagram illustrating an example of the E-UTRA protocol configuration according to the present embodiment. FIG. 3 is a diagram illustrating an example of the NR protocol configuration according to the present embodiment. FIG. 3 is a diagram illustrating an example of a flow of procedures for various settings in RRC according to the present embodiment. FIG. 2 is a block diagram showing the configuration of a terminal device in this embodiment. FIG. 2 is a block diagram showing the configuration of a base station device in this embodiment. An example of an ASN.1 description included in a message regarding resetting an RRC connection in NR in this embodiment. An example of an ASN.1 description included in a message regarding resetting an RRC connection in E-UTRA in this embodiment. An example of ASN.1 description included in the serving cell common settings in this embodiment. An example of an ASN.1 description included in a message regarding reconfiguration of an RRC connection in NR and an RRC reconfiguration completion message in the present embodiment. An example of processing of the terminal device in this embodiment. An example of ASN.1 description of candidate target settings in this embodiment. An example of ASN.1 description of candidate target settings in this embodiment. An example of ASN.1 description of candidate target settings in this embodiment.

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

LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RAT). Further, NR may be defined as a technology included in LTE. Furthermore, LTE may be defined as a technology included in NR. Furthermore, LTE, which can be connected to NR using Multi-Radio Dual Connectivity (MR-DC), may be distinguished from conventional LTE. Furthermore, LTE that uses 5GC in the core network (Core Network: CN) may be distinguished from conventional LTE that uses EPC in the core network. Note that conventional LTE may be LTE that does not implement the technology standardized after Release 15 in 3GPP. This embodiment may be applied to NR, LTE and other RATs. Although the following description uses terms related to LTE and NR, the present embodiment may be applied to other technologies using other terms. Further, the term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

In addition, in this embodiment, the names of each node and entity and the processing in each node and entity will be explained when the radio access technology is E-UTRA or NR. However, this embodiment is applicable to other radio access technologies. May be used. The names of each node and entity in this embodiment may be different names.

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

E-UTRA100 may be a radio access technology. Further, the E-UTRA 100 may be an air interface between the UE 122 and the eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device of the E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA Control Plane (CP) protocol, which will be described later. The eNB 102 may terminate the E-UTRA user plane (UP) protocol and the E-UTRA control plane (CP) protocol for the UE 122. A radio access network composed of eNBs may be called E-UTRAN.

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

Note that one or more eNBs 102 may be connected to the EPC 104 via the interface 112. An interface may exist between multiple eNBs 102 connected to the EPC 104 (not shown). The interface between the plurality of eNBs 102 connected to the EPC 104 may be referred to as an X2 interface.

NR106 may be a radio access technology. NR106 may also be an air interface between UE122 and gNB108. The air interface between UE 122 and gNB 108 may be referred to as a Uu interface. gNB (g Node B) 108 may be a base station device of NR106. gNB 108 may have the NR protocol described below. The NR protocol may include an NR user plane (UP) protocol, which will be described later, and an NR control plane (CP) protocol, which will be described later. The gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.

5GC110 may be a core network. Interface 116 is an interface between gNB 108 and 5GC 110, and may be called an NG interface. The interface 116 may include a control plane interface through which control signals pass and/or a user plane interface through which user data passes. The control plane interface of interface 116 may terminate in an Access and Mobility Management Function (AMF: not shown) within 5GC 110. The user plane interface of interface 116 may terminate at a User Plane Function (UPF: not shown) within 5GC 110. The control plane interface of interface 116 may be referred to as an NG-C interface. The user plane interface of interface 116 may be referred to as an NG-U interface.

Note that one or more gNBs 108 may be connected to the 5GC 110 via the interface 116. An interface may exist between multiple gNBs 108 connected to 5GC 110 (not shown). The interface between multiple gNBs 108 connected to 5GC 110 may be called an Xn interface.

eNB102 may have the ability to connect to 5GC110. The eNB 102 that has the function of connecting to the 5GC 110 may be called an ng-eNB. Interface 114 is an interface between eNB 102 and 5GC 110, and may be called an NG interface. The interface 114 may include a control plane interface through which control signals pass and/or a user plane interface through which user data passes. The control plane interface of interface 114 may terminate at an AMF within 5GC 110. The user plane interface of interface 114 may terminate at a UPF within 5GC 110. The control plane interface of interface 114 may be referred to as an NG-C interface. The user plane interface of interface 114 may be referred to as an NG-U interface. A radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may also be simply referred to as networks. Further, the network may include eNB, ng-eNB, gNB, and the like.

Note that one or more eNB102 may be connected to 5GC110 via interface 114. An interface may exist between multiple eNB102 connected to 5GC110 (not shown). The interface between multiple eNB102 connected to 5GC110 may be called an Xn interface. Furthermore, an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be connected by interface 120. The interface 120 between an eNB102 connected to 5GC110 and a gNB108 connected to 5GC110 may be called an Xn interface.

gNB108 may have the function of connecting to EPC104. gNB 108 having the function of connecting to EPC 104 may be called en-gNB. Interface 118 is an interface between gNB 108 and EPC 104, and may be called an S1 interface. Interface 118 may include a user plane interface through which user data passes. The user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104. The user plane interface of interface 118 may be referred to as the S1-U interface. Further, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected through an interface 120. The interface 120 between the eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be called an X2 interface.

The interface 124 is an interface between the EPC 104 and the 5GC 110, and may be an interface that passes only CP, only UP, or both CP and UP. Furthermore, some or all of the interfaces 114, 116, 118, 120, 124, etc. may not exist depending on the communication system provided by the communication carrier or the like.

The UE 122 may be a terminal device that can receive system information and paging messages transmitted from the eNB 102 and/or gNB 108. Further, the UE 122 may be a terminal device that can be wirelessly connected to the eNB 102 and/or the gNB 108. Further, the UE 122 may be a terminal device that can simultaneously perform a wireless connection with the eNB 102 and a wireless connection with the gNB 108. UE 122 may have an E-UTRA protocol and/or an NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.

UE122 may also be a terminal device capable of connecting to EPC104 and/or 5GC110 via eNB102 and/or gNB108. When the core network to which eNB102 and/or gNB108, with which UE122 communicates, is connected is EPC104, each Data Radio Bearer (DRB: Data Radio Bearer) described below established between UE122 and eNB102 and/or gNB108 may further be uniquely linked to each EPS (Evolved Packet System) bearer passing through EPC104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.

Furthermore, if the core network connected to eNB102 and/or gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and eNB102 and/or gNB108 is further established within 5GC110. It may be linked to one of the PDU (Packet Data Unit) sessions. There may be one or more QoS flows in each PDU session. Each DRB may be mapped to one or more QoS flows, or may not be mapped to any QoS flows. Each PDU session may be identified by a PDU session identifier (Identity, or ID). Further, each QoS flow may be identified by a QoS flow identifier (Identity or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.

There may be no PDU sessions and/or QoS flows in the EPC 104. Also, 5GC110 does not need to have an EPS bearer. When the UE 122 is connected to the EPC 104, the UE 122 has information on the EPS bearer, but may not have information on the PDU session and/or QoS flow. Further, when the UE 122 is connected to the 5GC 110, the UE 122 has information on the PDU session and/or QoS flow, but does not need to have information on the EPS bearer.

Note that in the following description, the eNB 102 and/or gNB 108 will also be simply referred to as a base station device, and the UE 122 will also be simply referred to as a terminal device or UE.

FIG. 2 is a diagram of an example of the E-UTRA protocol architecture according to the present embodiment. Further, FIG. 3 is a diagram of an example of the NR protocol configuration according to the present embodiment. Note that the functions of each protocol explained using FIG. 2 and/or FIG. 3 are some functions closely related to this embodiment, and may have other functions. Note that in this embodiment, the uplink (UL) may be a link from a terminal device to a base station device. Furthermore, in this embodiment, the downlink (DL) may be a link from a base station device to a terminal device.

Figure 2(A) is a diagram of the 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. As shown in Figure 2(A), the E-UTRA user plane protocol stack consists of a wireless physical layer (PHY) 200, a medium access control layer (MAC) 200, and a medium access control layer (MAC). RLC (Radio Link Control) 204, which is a radio link control layer, and PDCP (Packet Data Convergence Protocol) 206, which is a packet data convergence protocol layer. It's okay to be.

Figure 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in FIG. 3(A), the NRUP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side. As shown in Figure 3(A), the NR user plane protocol stack includes a radio physical layer PHY300, a medium access control layer MAC302, a radio link control layer RLC304, a packet data convergence protocol layer PDCP306, and It may be configured from SDAP (Service Data Adaptation Protocol) 310, which is a service data adaptation protocol layer.

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

Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in FIG. 3(B), in the NR CP protocol, RRC 308, which is a radio resource control layer, may be a protocol between UE 122 and gNB 108. That is, RRC308 may be a protocol that terminates at gNB108 on the network side. Further, in the NR CP protocol, the NAS 312, which is a non-AS layer, may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates with AMF on the network side.

Note that the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and/or gNB 108. That is, the AS layer is a layer that includes some or all of PHY200, MAC202, RLC204, PDCP206, and RRC208, and/or a layer that includes some or all of PHY300, MAC302, RLC304, PDCP306, SDAP310, and RRC308. It's fine.

In this embodiment, the following does not distinguish between the E-UTRA protocol and the NR protocol, and uses PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), and RRC (RRC layer). , the term NAS (NAS layer) is sometimes used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are the PHY (PHY layer) of the E-UTRA protocol. ), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer). layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer). Further, the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

In this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively defined as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA, or It is also called MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. In addition, PHY200, MAC202, RLC204, PDCP206, and RRC208 are respectively E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA It may also be written as RRC or LTE RRC. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There are some things. In addition, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes written as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

Entities in the AS layer of E-UTRA and/or NR will be explained. An entity that has some or all of the functions of the MAC layer may be called a MAC entity. An entity that has some or all of the functions of the RLC layer may be called an RLC entity. An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity. An entity that has some or all of the functions of the SDAP layer may be called an SDAP entity. An entity that has some or all of the functions of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

Note that data provided from MAC, RLC, PDCP, and SDAP to lower layers and/or data provided from lower layers to MAC, RLC, PDCP, and SDAP are referred to as MAC PDU (Protocol Data Unit) and RLC, respectively. It can be called PDU, PDCP PDU, SDAP PDU. In addition, data provided from the upper layer to MAC, RLC, PDCP, and SDAP, and/or data provided from MAC, RLC, PDCP, and SDAP to the upper layer are MAC SDU (Service Data Unit) and RLC SDU, respectively. , PDCP SDU, SDAP SDU. Furthermore, a segmented RLC SDU may be referred to as an RLC SDU segment.

Here, the base station device and the terminal device exchange (transmit and receive) signals in a higher layer. For example, the base station device and the terminal device may transmit and receive RRC messages (also referred to as RRC messages, RRC information, and RRC signaling) in a radio resource control (RRC) layer. Further, the base station device and the terminal device may transmit and receive MAC control elements in the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, the RRC message, system information, and/or MAC control element is also referred to as a higher layer signal (higher layer signal) or a higher layer parameter (higher layer parameter). Each of the parameters included in the upper layer signal received by the terminal device may be referred to as an upper layer parameter. In PHY layer processing, upper layer refers to the upper layer seen from the PHY layer, so it refers to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. Good too. For example, in the processing of the MAC layer, the upper layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like. Hereinafter, "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" mean the upper layers of the terminal device (mainly the RRC layer and MAC layer). etc.) may mean that A is received from the base station device, and the received A is given (provided) from an upper layer of the terminal device to the physical layer of the terminal device. For example, in a terminal device, being “provided with upper layer parameters” means that the upper layer parameter included in the received upper layer signal is received from the base station device, and the upper layer parameter included in the received upper layer signal is transmitted from the upper layer of the terminal device to the terminal device. It may also mean provided in layers. Setting upper layer parameters to a terminal device may mean that upper layer parameters are given (provided) to the terminal device. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from a base station device and sets the received upper layer parameters in the upper layer. However, setting upper layer parameters to the terminal device may include setting default parameters given in advance to the upper layer of the terminal device. When explaining sending an RRC message from a terminal device to a base station device, the expression "submit" a message from the RRC entity of the terminal device to a lower layer may be used. . In a terminal device, "submitting a message to a lower layer" from an RRC entity may mean submitting a message to a PDCP layer. In a terminal device, "submitting a message from the RRC layer to a lower layer" means that RRC messages are sent using SRBs (SRB0, SRB1, SRB2, SRB3, etc.), so It may also mean submitting to the corresponding PDCP entity. When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may refer to one or more of a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and the like.

An example of the PHY function will be explained. The PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink (UL) physical channel. The PHY may be connected to the upper MAC via a transport channel. The PHY may pass data to the MAC via a transport channel. The PHY may also be provided with data from the MAC via a transport channel. In the PHY, RNTI (Radio Network Temporary Identifier) may be used to identify various control information.

Here, the physical channel will be explained. The physical channels used for wireless communication between the terminal device and the base station device may include the following physical channels.

PBCH (Physical Broadcast CHannel)
PDCCH (Physical Downlink Control CHannel)
PDSCH (Physical Downlink Shared CHannel)
PUCCH (Physical Uplink Control CHannel)
PUSCH (Physical Uplink Shared CHannel)
PRACH (Physical Random Access CHannel)

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

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

The PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for transmission of downlink control information. That is, a field for downlink control information may be defined as DCI and mapped to information bits. PDCCH may be transmitted on PDCCH candidates. A terminal device may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode a PDCCH according to a certain DCI format. Furthermore, the terminal device may use CORESET (Control Resource Set) to monitor the set of PDCCH candidates. The DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmitting user data, transmitting an RRC message, which will be described later, and the like.

The PUCCH may be used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device). 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 also include a scheduling request (SR) used to request UL-SCH (Uplink Shared CHannel) resources. Further, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement).

The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Further, in the case of the downlink, the PDSCH may be used to transmit system information (SI), random access response (RAR), and the like.

PUSCH may be used to transmit HARQ-ACK and/or CSI along with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. Further, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH may be used to transmit only UCI. Additionally, the PDSCH or PUSCH may be used to transmit RRC signaling (also referred to as RRC message) and MAC CE. Here, in the PDSCH, the RRC signaling transmitted from the base station device may be common signaling to multiple terminal devices within the cell. Further, the RRC signaling transmitted from the base station device may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device. That is, terminal device-specific (UE-specific) information may be transmitted to a certain terminal device using dedicated signaling. Further, PUSCH may be used to transmit UE Capability in the uplink.

PRACH may be used to transmit a random access preamble. PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmission, and requests for UL-SCH resources. You can.

An example of the MAC function will be explained. MAC may be called a MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. A logical channel may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID). The MAC may be connected to the upper RLC through a logical channel. Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information, depending on the type of information to be transmitted. Further, logical channels may be divided into uplink logical channels and downlink logical channels. The MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing the same to the PHY. The MAC may also have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer via the logical channel to which each MAC SDU belongs. The MAC may also have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have the ability to report scheduling information. The MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Further, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have a function to prioritize resources that overlap within one terminal device. E-UTRA MAC may have the function of identifying Multimedia Broadcast Multicast Services (MBMS). The NR MAC may also have a function of identifying multicast/broadcast service (MBS). The MAC may have the ability to select the transport format. MAC is a power head that has the function of performing discontinuous reception (DRX) and/or discontinuous transmission (DTX), the function of executing random access (RA) procedure, and the function of notifying information on transmittable power. It may have a room report (Power Headroom Report: PHR) function, a buffer status report (Buffer Status Report: BSR) function that notifies information on the amount of data in the transmission buffer, etc. NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. The MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for controlling the MAC.

The logical channels for uplink (UL) and/or downlink (DL) used in E-UTRA and/or NR will be explained.

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

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

CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device. CCCH may be used when the terminal device does not have an RRC connection. Further, CCCH may be used between a base station device and multiple terminal devices.

DCCH (Dedicated Control Channel) 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. It's good to be there. The dedicated control information may be control information dedicated to each terminal device. DCCH may be used when the terminal device has an RRC connection.

DTCH (Dedicated Traffic Channel) may be a logical channel for transmitting user data on a one-to-one (point-to-point) basis between a terminal device and a base station device. DTCH may be a logical channel for transmitting dedicated user data. The dedicated user data may be user data dedicated to each terminal device. DTCH may exist on both uplink and downlink.

The mapping of uplink logical channels and transport channels in E-UTRA and/or NR will be explained.

CCCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

The DCCH may be mapped to a UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

DTCH may be mapped to UL-SCH (Uplink Shared Channel), which is an uplink transport channel.

The mapping of downlink logical channels and transport channels in E-UTRA and/or NR will be explained.

The BCCH may be mapped to a BCH (Broadcast Channel), which is a downlink transport channel, and/or a DL-SCH (Downlink Shared Channel).

The PCCH may be mapped to a PCH (Paging Channel), which is a downlink transport channel.

CCCH may be mapped to DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

The DCCH may be mapped to a DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

DTCH may be mapped to the downlink transport channel, DL-SCH (Downlink Shared Channel).

An example of the RLC function will be explained. RLC may be referred to as an RLC sublayer. The E-UTRA RLC may have a function of segmenting and/or concatenating data provided from the upper layer PDCP and providing it to the lower layer. The E-UTRA RLC may have a function of reassembling and re-ordering data provided from lower layers and providing the data to upper layers. NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to data provided from the upper layer PDCP. Furthermore, NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers. Further, the NR RLC may have a function of reassembling data provided from lower layers and providing the data to upper layers. RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Additionally, RLC may have a function of performing error correction using ARQ. Control information indicating data that needs to be retransmitted, which is sent from the RLC receiving side to the transmitting side in order to perform ARQ, can be called a status report. Also, the status report transmission instruction sent from the RLC transmitting side to the receiving side can be referred to as a poll. The RLC may also have a function to detect data duplication. RLC may also have a data discard function. RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The TM does not divide data received from the upper layer and does not need to add an RLC header. A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. In UM, data received from the upper layer is divided and/or combined, RLC headers are added, etc., but there is no need to control data retransmission. A UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or as a receiving UMRLC entity. If the UM RLC entity is a bidirectional entity, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, division and/or combination of data received from the upper layer, addition of an RLC header, data retransmission control, etc. may be performed. 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. Note that data provided to a lower layer by a TM and/or data provided from a lower layer may be referred to as a TMD PDU. Furthermore, data provided to lower layers in UM and/or data provided from lower layers may be referred to as UMD PDU. Additionally, data provided to lower layers in AM or data provided from lower layers may be referred to as AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Further, the RLC PDU may include a data RLC PDU and a control RLC PDU. The RLC PDU for data may be called RLC DATA PDU (RLC Data PDU, RLC data PDU). Further, the control RLC PDU may be referred to as RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).

An example of the PDCP function will be explained. PDCP may be called a PDCP sublayer. PDCP may have a function to perform sequence number maintenance. Furthermore, PDCP may have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section. The protocol used to compress and decompress the header of IP packets can be called the ROHC (Robust Header Compression) protocol. Furthermore, the protocol used for compressing and decompressing Ethernet frame headers may be referred to as the EHC (Ethernet (registered trademark) Header Compression) protocol. Furthermore, PDCP may have data encryption/decryption functions. Furthermore, PDCP may have data integrity protection/integrity verification functions. PDCP may also have a re-ordering function. PDCP may also have a PDCP SDU retransmission function. Furthermore, PDCP may have a function of discarding data using a discard timer. Furthermore, PDCP may have a multiplexing (Duplication) function. Furthermore, PDCP may have a function of discarding data that has been received repeatedly. The PDCP entity is a bidirectional entity and may include a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Further, the PDCP PDU may include a data PDCP PDU and a control PDCP PDU. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). Further, the control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).

An example of SDAP functionality will be explained. SDAP is a service data adaptation protocol layer. SDAP maps the downlink QoS flow sent from 5GC110 to the terminal device via the base station device and the data radio bearer (DRB), and/or the mapping from the terminal device to the terminal device via the base station device. It may have a function to map uplink QoS flows sent to 5GC110 and DRB. SDAP may also have a function of storing mapping rule information. SDAP may also have a function of marking a QoS flow identifier (QoS Flow ID: QFI). Note that the SDAP PDU may include a data SDAP PDU and a control SDAP PDU. SDAP PDU for data may be called SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). Furthermore, the control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that one SDAP entity of the terminal device may exist for a PDU session.

An example of the RRC function will be explained. RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and/or 5GC 110. The RRC may have a paging function from the eNB 102 that connects to the gNB 108 or 5GC 110. RRC may also have RRC connection management functionality. RRC may also have radio bearer control functionality. The RRC may also have a cell group control function. The RRC may also have mobility control functionality. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions. RRC may also have QoS management functionality. RRC may also have radio link failure detection and recovery functionality. RRC uses RRC messages to perform broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, etc. You may do so. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.

The RRC message may be sent using the BCCH of a logical channel, the PCCH of a logical channel, the CCCH of a logical channel, or the DCCH of a logical channel. May be sent. Furthermore, the RRC message sent using the DCCH may be referred to as dedicated RRC signaling or RRC signaling.

The RRC message sent using the BCCH may include, for example, a master information block (MIB), each type of system information block (SIB), and other RRC messages may be included. RRC messages sent using the PCCH may include, for example, paging messages or other RRC messages.

RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request message, RRC Resume Request message, RRC Reestablishment Request message, It may include an RRC system information request message (RRC System Info Request), etc. Further, for example, an RRC Connection Request message, an RRC Connection Resume Request message, an RRC Connection Reestablishment Request message, and the like may be included. Other RRC messages may also be included.

RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject message, RRC Connection Setup message, RRC Connection Reestablishment message, It may include an RRC Connection Reestablishment Reject message, etc. Further, for example, an RRC rejection message (RRC Reject), an RRC Setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.

RRC signaling sent in the uplink (UL) direction using DCCH includes, for example, measurement report messages, RRC Connection Reconfiguration Complete messages, and RRC Connection Setup Complete messages. ), an RRC Connection Reestablishment Complete message, a Security Mode Complete message, a UE Capability Information message, and the like. Also, for example, measurement report message (Measurement Report), RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message. ), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. may be included. Other RRC signaling may also be included.

RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, RRC Connection Reconfiguration message, RRC Connection Release message, Security Mode Command message, It may include a UE Capability Inquiry message, etc. Also, for example, RRC Reconfiguration message, RRC Resume message, RRC Release message, RRC Reestablishment message, Security Mode Command message, UE capability inquiry message. (UE Capability Inquiry) etc. may be included. Other RRC signaling may also be included.

An example of a NAS function will be explained. The NAS may have an authentication function. The NAS may also have the ability to perform mobility management. The NAS may also have security control functions.

The functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS described above are just examples, and some or all of the functions do not have to be implemented. Furthermore, part or all of the functions of each layer may be included in another layer.

Next, the state transition of the UE 122 in LTE and NR will be explained. The UE 122 connecting to the EPC or 5GC may be in the RRC_CONNECTED state when the RRC connection has been established. The state in which the RRC connection is established may include a state in which the UE 122 holds some or all of the UE context described below. Furthermore, the state in which the RRC connection is established may include a state in which the UE 122 can transmit and/or receive unicast data. Furthermore, when the RRC connection is suspended, the UE 122 may be in the RRC_INACTIVE state. Further, the UE 122 may enter the RRC_INACTIVE state when the UE 122 is connected to the 5GC and the RRC connection is suspended. When the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state, the UE 122 may be in the RRC_IDLE state.

Note that when the UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the E-UTRAN may start suspending the RRC connection. When the UE 122 is connected to the EPC and the RRC connection is suspended, the UE 122 may transition to the RRC_IDLE state while retaining the UE's AS context and an identifier (resumeIdentity) used for resuming. The layer above the RRC layer of the UE 122 (for example, the NAS layer) is configured such that the UE 122 maintains the UE's AS context, the E-UTRAN permits the return of the RRC connection, and the UE 122 leaves the RRC_IDLE state. When it is necessary to transition to the RRC_CONNECTED state, recovery of the suspended RRC connection may be initiated.

The definition of pause may be different between the UE 122 connecting to the EPC 104 and the UE 122 connecting to the 5GC 110. Also, when the UE122 is connected to the EPC (when the UE122 is inactive in the RRC_IDLE state) and when the UE122 is connected to the 5GC (when the UE122 is inactive in the RRC_INACTIVE state), the UE122 All or part of the procedure for returning from hibernation may be different.

Note that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be respectively called connected state (connected mode), inactive state (inactive mode), and idle state (idle mode), and RRC connected state (RRC connected mode). , RRC inactive mode, and RRC idle mode.

The AS context of the UE held by the UE122 includes the current RRC settings, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, and the C-RNTI (Cell Radio) used in the PCell of the connection source (Source). The information may include all or part of the Network Temporary Identifier, cell identifier (cellIdentity), and physical cell identifier of the connection source PCell. Note that the UE AS context held by any or all of eNB 102 and gNB 108 may include the same information as the UE AS context held by UE 122, or the information contained in the UE AS context held by UE 122. may contain information different from that.

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

Next, the serving cell will be explained. In a terminal device in an RRC connected state in which CA and/or DC, which will be described later, are not configured, the serving cell may be configured from one primary cell (PCell). In addition, in a terminal device in an RRC connected state in which CA and/or DC, which will be described later, are configured, multiple serving cells include one or more special cells (Special Cell: SpCell) and one or more all secondary cells. It may mean a set of cells (set of cells) consisting of cells (Secondary Cell: SCell). The SpCell may support PUCCH transmission and contention-based Random Access (CBRA), and the SpCell may be activated at all times. The PCell may be a cell used in an RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. Further, the PCell may be a cell used in an RRC connection re-establishment procedure in which a terminal device re-establishes an RRC connection. Further, the PCell may be a cell used in a random access procedure during handover. The PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. Further, SpCell may be a cell used for purposes other than those described above.

If the serving cell group configured for the terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. . Furthermore, a cell that provides additional radio resources to SpCell for a terminal device in which CA is configured may mean SCell.

A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for the cells in which the uplink is configured. It can be called a timing advance group (TAG). Further, the TAG including SpCell of the MAC entity may mean a primary timing advance group (PTAG). Further, TAGs other than the above-mentioned PTAG may mean secondary timing advance group (STAG). Note that one or more TAGs may be configured for each cell group, which will be described later.

A cell group that is set from a base station device to a terminal device will be explained. A cell group may be composed of one SpCell. Further, a cell group may be composed of one SpCell and one or more SCells. That is, a cell group may be composed of one SpCell and optionally one or more SCells. Further, a cell group may be expressed as a set of cells.

Dual Connectivity (DC) means that a first base station device (first node) and a second base station device (second node) perform data communication by using the radio resources of the cell groups they respectively configure. It can be technology. When DC or MR-DC, which will be described later, is performed, a cell group may be added to the terminal device from the 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 (Master Node: MN). Further, a cell group constituted by a master node may be referred to as a master cell group (MCG). The second base station device may be referred to as a secondary node (SN). Further, a cell group configured by a secondary node may be referred to as a secondary cell group (SCG). Note that the master node and the secondary node may be configured within the same base station device.

Furthermore, when a DC is not configured, a cell group configured in a terminal device may be referred to as an MCG. Furthermore, when a DC is not set, the SpCell set in the terminal device may be a PCell. Furthermore, an NR without a DC configured may be called an NR standalone.

Note that Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Further, MR-DC may be a technique for performing DC using NR for MCG and E-UTRA for SCG. Further, MR-DC may be a technology that performs DC using NR on both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC that uses E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC for the core network, and NGEN-DC that uses 5GC for the core network. DC (NG-RAN E-UTRA-NR Dual Connectivity) is fine. Also, as an example of an MR-DC that uses NR for MCG and E-UTRA for SCG, there may be NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC for the core network. Further, as an example of MR-DC that uses NR for both MCG and SCG, there may be NR-DC (NR-NR Dual Connectivity) that uses 5GC for the core network.

Note that in the terminal device, one MAC entity may exist for each cell group. For example, when a DC or MR-DC is configured in a terminal device, there may be one MAC entity for MCG and one MAC entity for SCG. A MAC entity for MCG in a terminal device may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). Further, the MAC entity for the SCG in the terminal device may be created by the terminal device when the SCG is configured in the terminal device. Further, the MAC entity for each cell group of the terminal device may be configured by the terminal device receiving RRC signaling from the base station device. When a MAC entity is associated with an MCG, SpCell may refer to PCell. Furthermore, when the MAC entity is associated with an SCG, SpCell may mean a primary SCG cell (Primary SCG Cell: PSCell). Also, if the MAC entity is not associated with a cell group, SpCell may mean PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. Further, in the NE-DC, the MAC entity for MCG may be an NR MAC entity, and the MAC entity for SCG may be an E-UTRA MAC entity. Further, in NR-DC, both the MAC entities for MCG and SCG may be NR MAC entities. Note that the existence of one MAC entity for each cell group can be translated into the existence of one MAC entity for each SpCell. Furthermore, one MAC entity for each cell group may be translated as one MAC entity for each SpCell.

Let's explain the radio bearer. When a terminal device communicates with a base station device, a wireless connection may be established by establishing a radio bearer (RB) between the terminal device and the base station device. The radio bearer used for CP may be called a signaling radio bearer (SRB). Furthermore, the radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identity (ID). The radio bearer identifier for SRB may be called an SRB identity (SRB ID). The radio bearer identifier for DRB may be called a DRB identity (DRB ID). SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined. SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined. SRB0 may be an SRB for an RRC message that is transmitted and/or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2. RRC signaling transmitted and/or received using SRB1 may include piggybacked NAS signaling. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB1. SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB2. Further, SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and/or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and/or received using SRB3. Further, other SRBs may be prepared for other uses. DRB may be a radio bearer for user data. The logical channel DTCH may be used for RRC signaling that is transmitted and/or received using the DRB.

The radio bearer in the terminal device will be explained. Radio bearers may include RLC bearers. An RLC bearer may consist of one or two RLC entities and a logical channel. When there are two RLC entities in an RLC bearer, the RLC entities may be a TM RLC entity and/or a transmitting RLC entity and a receiving RLC entity in an RLC entity in unidirectional UM mode. SRB0 may consist of one RLC bearer. The RLC bearer of SRB0 may consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). One SRB1 may be established and/or configured in the terminal device by RRC signaling received from the base station device when the terminal device transitions from the RRC idle state to the RRC connected state. SRB1 may consist of one PDCP entity and one or more RLC bearers. The SRB1 RLC bearer may consist of an AM RLC entity and a logical channel. One SRB2 may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling received from the base station device. SRB2 may consist of one PDCP entity and one or more RLC bearers. The SRB2 RLC bearer may consist of an AM RLC entity and a logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node. In SRB3, when a secondary node in EN-DC, NGEN-DC, or NR-DC is added or changed, a terminal device in an RRC connection state with AS security activated connects to the base station. One may be established and/or configured in the terminal device by RRC signaling received from the device. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. The SRB3 RLC bearer may consist of an AM RLC entity and a logical channel. PDCP on the base station device side of SRB3 may be placed in a secondary node. One or more DRBs may be established and/or configured in a terminal device in an RRC connected state with AS security activated by RRC signaling that the terminal device receives from the base station device. A DRB may consist of one PDCP entity and one or more RLC bearers. A DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.

Note that in MR-DC, the radio bearer in which PDCP is placed in the master node may be referred to as an MN terminated bearer. Furthermore, in MR-DC, a radio bearer in which PDCP is placed in a secondary node may be referred to as an SN terminated bearer. Note that in MR-DC, a radio bearer in which the RLC bearer exists only in the MCG may be referred to as an MCG bearer. Furthermore, in MR-DC, a radio bearer in which the RLC bearer exists only in the SCG may be referred to as an SCG bearer. Furthermore, in the DC, a radio bearer in which the RLC bearer exists in both the MCG and the SCG may be referred to as a split bearer.

When MR-DC is configured in the terminal device, the bearer types of SRB1 and SRB2 established/and/or configured in the terminal device may be MN-terminated MCG bearer and/or MN-terminated split bearer. Further, when MR-DC is configured in the terminal device, the bearer type of SRB3 established/and/or configured in the terminal device may be an SN termination SCG bearer. Further, when MR-DC is configured in the terminal device, the bearer type of the DRB established/and/or configured in the terminal device may be any one of all bearer types.

For an RLC bearer to be established and/or configured in a cell group configured with E-UTRA, the RLC entity to be established and/or configured may be E-UTRA RLC. Furthermore, the RLC entity to be established and/or configured for an RLC bearer established and/or configured in a cell group configured with NR may be NR RLC. When EN-DC is configured in the terminal device, the PDCP entity established and/or configured for the MN terminating MCG bearer may be either E-UTRA PDCP or NR PDCP. In addition, when EN-DC is configured in the terminal device, other bearer types of radio bearers, namely MN-terminated split bearer, MN-terminated SCG bearer, SN-terminated MCG bearer, SN-terminated split bearer, and SN-terminated SCG bearer, are The PDCP established and/or configured may be NR PDCP. Additionally, if NGEN-DC, NE-DC, or NR-DC is configured in the terminal device, the PDCP entity established and/or configured for the radio bearer in all bearer types may be NR PDCP. .

Note that in NR, a DRB established and/or configured in a terminal device may be linked to one PDU session. One SDAP entity may be established and/or configured for one PDU session at the terminal device. Establishment and/or configuration of the SDAP entity, PDCP entity, RLC entity, and logical channel in the terminal device may be established and/or configured by RRC signaling that the terminal device receives from the base station device.

Note that regardless of whether MR-DC is configured, a network configuration in which the master node is eNB102 and EPC104 is the core network may be called E-UTRA/EPC. A network configuration in which the master node is eNB102 and 5GC110 is the core network may be called E-UTRA/5GC. A network configuration in which the master node is gNB108 and 5GC110 is the core network may be called NR or NR/5GC. When MR-DC is not configured, the above-mentioned master node may refer to a base station device that communicates with a terminal device.

Next, handover in LTE and NR will be explained. Handover may be a process in which the UE 122 in the RRC connected state changes the serving cell from the source SpCell to the target SpCell. Handover may be part of mobility control performed by RRC. Handover may be performed when UE 122 receives RRC signaling from eNB 102 and/or gNB 108 instructing handover. RRC signaling that instructs handover may be a message regarding reconfiguration of an RRC connection that includes a parameter that instructs handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). Note that the above-mentioned information element named MobilityControlInfo may be referred to as a mobility control setting information element, mobility control setting, or mobility control information. Note that the above-mentioned information element named ReconfigurationWithSync may be referred to as a reconfiguration with synchronization information element or a reconfiguration with synchronization. Furthermore, RRC signaling instructing handover may be a message (eg, MobilityFromEUTRACommand or MobilityFromNRCommand) indicating movement to a cell of another RAT. Handover can also be referred to as reconfiguration with sync. Reconfiguration with synchronization may be triggered by RRC, or by DCI or MAC control elements. In addition, the conditions under which the UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and when at least one DRB is established. good. The above-mentioned handover may be rephrased as layer 3 handover or the like.

The flow of RRC signaling transmitted and received between the terminal device and the base station device will be explained. FIG. 4 is a diagram showing an example of a flow of procedures for various settings in RRC according to the present embodiment. FIG. 4 is an example of a flow when RRC signaling is sent from the base station device (eNB 102 and/or gNB 108) to the terminal device (UE 122).

In FIG. 4, the base station device creates an RRC message (step S400). The RRC message may be created in the base station device so that the base station device can distribute system information (SI) and paging messages. Further, the creation of the RRC message in the base station device may be performed so that the base station device can transmit RRC signaling to cause a specific terminal device to perform processing. The processing to be performed on a specific terminal device may include, for example, processing related to security, reconfiguration of an RRC connection, handover to a different RAT, suspension of an RRC connection, release of an RRC connection, and the like. Resetting an RRC connection involves processing such as radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. May be included. Further, the creation of an RRC message in the base station device may be performed in response to RRC signaling transmitted from the terminal device. The response to RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC restart request, and the like. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements, and may be described using a description method called ASN.1 (Abstract Syntax Notation One).

In FIG. 4, the base station device then transmits the created RRC signaling to the terminal device (step S402). Next, the terminal device performs processing such as setting, if necessary, according to the above-mentioned received RRC signaling (step S404). The terminal device that has performed the processing may transmit RRC signaling for response to the base station device (not shown).

RRC signaling is not limited to the above example and may be used for other purposes.

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

Note that, not only when using MR-DC, NR RRC signaling may be included in E-UTRA RRC signaling transmitted from eNB 102 to UE 122, and NR RRC signaling transmitted from gNB 108 to UE 122. The signaling may include RRC signaling for E-UTRA.

An example of parameters included in a message regarding resetting an RRC connection will be explained. FIG. 7 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in NR in FIG. 4. Further, FIG. 8 is an example of an ASN.1 description representing fields and/or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in E-UTRA in FIG. 4. Not limited to FIGS. 7 and 8, in the examples of ASN.1 in this embodiment, <omitted> and <omitted> are not part of the notation of ASN.1, and indicate that other information is omitted. shows. Note that information elements may be omitted even in places where there is no description of <omitted> or <omitted>. Note that in this embodiment, the example of ASN.1 does not correctly follow the ASN.1 notation method. In this embodiment, the example ASN.1 represents an example of the RRC signaling parameters in this embodiment, and other names and other representations may be used. Further, in the example of ASN.1, in order to avoid complicating the explanation, only an example related to main information closely related to this embodiment will be shown. Note that the parameters described in ASN.1 are sometimes referred to as information elements, without distinguishing them into fields, information elements, etc. Further, in this embodiment, fields, information elements, etc. described in ASN.1 and included in RRC signaling may be translated into information or parameters. Note that the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

In FIG. 7, the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc. a cell group of MCG or SCG in NR. The information element named CellGroupConfig may be referred to as a cell group configuration information element or cell group configuration. An information element named SpCellConfig included in an information element named CellGroupConfig may be an information element used for configuring a special cell (SpCell). The information element named SpCellConfig may be rephrased as SpCell configuration information element or SpCell configuration. An information element named SCellConfig included in an information element named CellGroupConfig may be an information element used to configure a secondary cell (SCell). The information element named SCellConfig may be rephrased as SCell configuration information element or SCell configuration. The information element named ReconfigurationWithSync included in the information element named SpCellConfig may be the above-mentioned reconfiguration with synchronization information element or reconfiguration with synchronization. The information element named ReconfigurationWithSync may include a new UE identifier named newUE-Identity. The information element named spCellConfigCommon included in the information element named ReconfigurationWithSync may be an information element indicating common settings configured in SpCell. The information element named spCellConfigCommon can be rephrased as SpCell common settings. An information element named sCellConfigCommon included in an information element named SCellConfig may be an information element indicating common settings configured in SCell. The information element named sCellConfigCommon can be rephrased as SCell common settings.

FIG. 9 is an example of an information element named ServingCellConfigCommon included in the SpCell configuration or SCell configuration in FIG. 7, that is, an example of an ASN.1 description representing a field and/or information element related to the serving cell common configuration. The information element named DownlinkConfigCommon included in the information element named ServingCellConfigCommon may be an information element indicating common settings configured in the downlink. The information element named DownlinkConfigCommon may be rephrased as downlink common settings. The information element named BWP-DownlinkCommon included in the information element named DownlinkConfigCommon may be an information element indicating common settings configured in the downlink BWP. The information element named BWP-DownlinkCommon may be rephrased as downlink BWP common settings. The information element named PDCCH-ConfigCommon included in the information element named BWP-DownlinkCommon may be an information element indicating common settings configured on the PDCCH. The information element named PDCCH-ConfigCommon may be rephrased as PDCCH common settings. The information element named PDCCH-ConfigCommon may include an information element named commonSearchSpaceList, an information element named searchSpaceSIB1, an information element named searchSpaceOtherSystemInformation, and/or an information element named pagingSearchSpace. The information element named commonSearchSpaceList may refer to a list of common search spaces (CSS). Further, the information element named searchSpaceSIB1 may be information on a search space for receiving system information (SIB1). Furthermore, searchSpaceOtherSystemInformation may include information on a search space for receiving system information (SIB2 and later). Further, the information element named pagingSearchSpace may be information on a search space for receiving paging messages.

　Explain the measurement gap. The measurement gap is a period during which it can be considered that uplink transmission from the terminal device to the base station device and downlink transmission from the base station device to the terminal device are not scheduled. A terminal device with a measurement gap set may perform measurements during the measurement gap period. Moreover, the measurement gap may be rephrased as a measurement gap or the like.

FIG. 10 is an example of an ASN.1 description representing fields and/or information elements related to measurement gap settings included in a message related to RRC connection reconfiguration in NR and an RRC reconfiguration completion message in FIG. 4. be. In FIG. 10, the information element named NeedForGapsConfigNR may be an information element including settings related to reporting of measurement gap requirement information in NR. The information element named NeedForGapsConfigNR may be rephrased as an information element of a setting that causes NR to report whether or not a measurement gap is required, or a setting that causes NR to report whether or not a measurement gap is required. In addition, the information element named NeedForGapsInfoNR in Figure 10 indicates that if NR-DC or NE-DC is not configured, the measurement gap is required for the terminal device to perform SSB-based measurement on the target frequency band of NR. It may be an information element indicating whether or not it is necessary. The information element named NeedForGapsInfoNR may be rephrased as an information element indicating whether a measurement gap is required in NR, or information indicating whether a measurement gap is necessary in NR. The information element named requestedTargetBandFilterNR included in the information element named NeedForGapsConfigNR is an information element indicating the target NR frequency band for which the terminal device needs to report gap requirement information. good. "Gap necessity information" can be translated as "information indicating whether a gap is necessary", "measurement gap necessity information", or "information indicating whether a measurement gap is necessary", etc. It's okay to be rejected. An information element named intraFreq-needForGap included in an information element named NeedForGapsInfoNR may be an information element that indicates whether or not a measurement gap is necessary for NR intra-frequency measurement. The information element named intraFreq-needForGap includes the information element named servCellId, which indicates the identifier of the serving cell on which the measurement is performed, and the information element named intraFreq-needForGap, and the information element named intraFreq-needForGap, which indicates the identifier of the serving cell where the measurement is performed, and the information element named intraFreq-needForGap. It may include, for example, an information element named gapIndicationIntra indicating whether a measurement gap is required to perform the based intra-frequency measurements. The information element named gapIndicationIntra indicates that a measurement gap is required when none of the one or more BWPs configured in the terminal device contains the SSB frequency domain resource associated with the initial DL BWP. may indicate the value "gap" indicating that no measurement gap is required to perform measurements of the SSB associated with the initial DL BWP for all BWPs configured on the terminal device. May indicate a value of "no-gap". The information element named interFreq-needForGap, which is included in the information element named NeedForGapsInfoNR, may be an information element that indicates whether or not a measurement gap is necessary for NR inter-frequency measurement. The information element named interFreq-needForGap is similar to the information element named bandNR which indicates the target frequency band of the NR in which the measurement is performed, or if NR-DC or NE-DC is not configured, the terminal equipment A value named gapIndication that indicates whether a measurement gap is required to perform SSB-based measurements on the NR's target frequency band (the NR's target frequency band indicated by the information element named bandNR). It may include information elements, etc. The information element named gapIndication may indicate a value of "gap" indicating that a measurement gap is required, or a value of "no-gap" indicating that a measurement gap is not required.

The RRC reconfiguration procedure will be explained. The RRC reconfiguration procedure may be a procedure for reconfiguring parameters, information elements, etc. set in RRC. Further, the purpose of the RRC reconfiguration procedure may be some or all of the following (A) to (F).
(A) Modifying an RRC connection (B) Performing a reconfiguration with synchronization (C) Setting, modifying, and/or releasing a measurement (D) One or more Adding, modifying, and/or releasing SCells and cell groups (E) Adding, modifying, and/or releasing conditional handover (CHO) settings (F) Conditional PSCell changes Adding, modifying, and/or releasing settings for (conditional PSCell change: CPC) or conditional PSCell addition (CPA)

The base station device (network) may initiate an RRC reconfiguration procedure for the terminal device in the RRC_CONNECTED state. At this time, the base station apparatus may apply some or all of the following (A) to (F) to the RRC reconfiguration procedure. Note that "the base station device starts an RRC reconfiguration procedure for the terminal device" may be paraphrased as "the base station device transmits a message regarding reconfiguring the RRC connection to the terminal device", etc. .
(A) Establishment of radio bearers other than SRB1 (B) Addition of SCG and one or more SCells (C) Reconfiguration with synchronization included in SCG cell group configuration (D) Synchronization included in MCG cell group configuration Conditional reconfiguration (E) Conditional reconfiguration for conditional PSCell change
(F) Conditional reconfiguration for conditional handover or conditional PSCell addition

A synchronized reconfiguration with security key update included in a message regarding RRC connection reconfiguration may include some or all of (A) to (E) below, which is triggered by an explicit layer 2 indicator. may be included.
(A) Random access to PCell and/or PSCell (B) MAC reset (C) Security update (D) Re-establishment of RLC (E) Re-establishment of PDCP

A synchronized reconfiguration without security key update included in a message regarding RRC connection reconfiguration is triggered by an explicit layer 2 indicator, and some or all of (A) to (D) below are triggered by an explicit layer 2 indicator. may include.
(A) Random access to PCell and/or PSCell (B) MAC reset (C) RLC re-establishment (D) PDCP data recovery

Note that the layer 2 indicators described above may include, for example, layer 2 signaling such as MAC, RLC, and PDCP.

When the terminal device receives a message regarding RRC connection reconfiguration or executes conditional reconfiguration (CHO, CPA, or CPC), the terminal device performs some or all of the following (A) to (H). You may (perform).
(Processing RRP)
(A) If the message regarding RRC connection reconfiguration is applied by performing a conditional reconfiguration when performing cell selection while timer T311 is running, which starts at the beginning of the RRC reestablishment procedure, then Remove all entries from the entry list.
(B) If the message regarding RRC connection reconfiguration includes MCG cell group configuration, perform cell group configuration for the received MCG cell group configuration, and the cell group configuration is reconfigured with synchronization. If SpCell settings with information elements are included, perform reconfiguration with synchronization.
(C) If the message regarding RRC connection reconfiguration includes cell group configuration for the SCG, perform cell group configuration for the SCG, and said cell group configuration includes SpCell configuration with synchronized reconfiguration information element; If included, perform reconfiguration with synchronization.
(D) If the message regarding RRC connection reconfiguration includes conditional reconfiguration, perform conditional reconfiguration.
(E) If the message regarding the reconfiguration of an RRC connection includes a setting that causes the NR to report whether a measurement gap is required, and the setting that causes the NR to report whether a measurement gap is required is set up If it is set to , it is considered that it is set to provide information on whether or not a measurement gap is required for the target frequency band of NR.
(F) If the message regarding RRC connection reconfiguration includes a setting to report whether a measurement gap is required in the NR, and the setting to report whether a measurement gap is required in the NR is set up If it is not set to , it is considered that it is not set to provide information on whether or not the measurement gap of the target frequency band of NR is required.
(G) Set the contents of the RRC reconfiguration completion message according to (G-1) to (G-3) below.
(H) Submit an RRC reconfiguration completion message to lower layers (PHY, MAC, etc.) via SRB1 for transmission using the new configuration.

(Processing NFG)
(G-1) If a message regarding RRC connection reconfiguration is received via SRB1, an SCG configuration in MR-DC named mrdc-SecondaryCellGroup (not shown), an RRC connection reconfiguration message in E-UTRA (RRCConnectionReconfiguration) or in the RRC Connection Resume message (RRCConnectionResume) in E-UTRA, perform the following process (G-2).
(G-2) If the terminal device is set to be provided with information on whether or not a measurement gap for the target frequency band of NR is provided, the following process (G-3) is performed.
(G-3) If the message regarding the reconfiguration of the RRC connection contains a setting that causes the NR to report whether a measurement gap is required, or if there is no information indicating whether a measurement gap is required in the NR. , if there has been a change since the last time the terminal device reported, include information indicating whether a measurement gap is required in the NR in the RRC reconfiguration completion message, and from (G-3-1) below ( G-3-3), set the contents of information indicating whether a measurement gap is necessary in NR.
(G-3-1) Include an information element named intraFreq-needForGap in the information indicating whether a measurement gap is required in the NR, and include information on the necessity or necessity of an intra-frequency measurement gap for the serving cell of each NR. set.
(G-3-2) If the information element named requestedTargetBandFilterNR is set, the name interFreq-needForGap is assigned to each NR frequency band supported by the terminal device, which is also included in the information element named requestedTargetBandFilterNR. includes an entry in the information element of , and sets gap necessity information for the frequency band.
(G-3-3) If the information element named requestedTargetBandFilterNR is not configured, include an entry in the information element named interFreq-needForGap with a corresponding entry for each NR frequency band supported by the terminal device. Set gap necessity information.

The terminal device may perform some or all of (A) to (E) below in order to execute reconfiguration with synchronization. "Performing reconfiguration with synchronization" may be rephrased as "performing reconfiguration with synchronization" or "triggering reconfiguration with synchronization".
(Processing RWS)
(A) If timer T310 for the corresponding SpCell is running, stop it.
(B) If timer T312 for the corresponding SpCell is running, stop it.
(C) Reset the MAC entity of the corresponding cell group.
(D) Apply the value of the new UE identifier (newUE-Identity) included in the reconfiguration information element with synchronization as the C-RNTI for the corresponding cell group.
(E) Configure lower layers (PHY, etc.) according to the received SpCell common settings.

Next, conditional resetting will be explained. Conditional reconfiguration may refer to conditional handover, conditional PSCell addition, and/or conditional PSCell change. The network sets one or more target candidate cells for conditional reconfiguration for the terminal device. The terminal device evaluates the state of the configured candidate cell. The terminal device performs the evaluation and applies conditional reconfiguration information elements associated with candidate cells that satisfy the execution conditions. Furthermore, the terminal device may maintain a list of entries (VarConditionalReconfig), which will be described later, for conditional reconfiguration.

Based on receiving the information regarding conditional reconfiguration, the terminal device deletes a target candidate cell for conditional reconfiguration if the information regarding conditional reconfiguration includes an entry deletion list (condReconfigToRemoveList). If the information regarding the conditional reconfiguration includes an addition/modification list of entries (condReconfigToAddModList), the conditional reconfiguration target candidate cell may be added or modified.

The operation of deleting the conditional reconfiguration target candidate cell means that if the entry identifier (condReconfigId) included in the entry deletion list is included in the list of entries held by the terminal device, the terminal device The method may be to delete an entry corresponding to the identifier of the entry from a list of entries held by the terminal device. Note that in the following description, the list of entries held by the terminal device is also simply referred to as an entry list. That is, the "entry list" in the following description refers to a list of entries held by the terminal device, unless otherwise specified. The entry list may also be a variable named VarConditionalReconfig. Further, the entry identifier is also simply referred to as an entry identifier.

The operation of adding or modifying a target candidate cell for conditional reconfiguration means that when each entry identifier included in the entry addition/modification list exists in an entry in the entry list, the terminal device performs the following process (A). ) and/or (B).
(A) If an entry included in the addition/modification list of an entry includes an execution condition (condExecutionCond), the execution condition of the entry in the entry list that matches the entry identifier of this entry is included in the list of addition/modification of that entry. Replace with the execution condition.
(B) If an entry included in the entry addition/modification list includes a conditional reconfiguration information element (condRRCReconfig), the conditional reconfiguration information element in the entry list that matches the entry identifier of this entry is added to that entry. Replace with the conditional reconfiguration information element included in the additional modification list.

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

Note that the entry deletion list may be a list related to the settings of one or more candidate SpCells to be deleted. The addition/modification list of entries may be a list regarding the settings of one or more candidate SpCells to be added and modified for CHO, CPC, and CPA. Each entry included in the addition/modification list of entries includes an entry identifier and may additionally include execution conditions and/or conditional reconfiguration information elements. Each entry may be associated with one candidate SpCell of one or more candidate SpCells. The entry identifier is an identifier used to identify each entry of CHO, CPA, and CPC. The entry list may include one or more entries. Each entry may include one entry identifier, one or more execution conditions, and one conditional reconfiguration information element. If the entry list held by the terminal device does not include any entries, the terminal device may hold an empty list. The execution condition may be a condition that needs to be met to trigger execution of the conditional reconfiguration. The conditional reconfiguration information element may be a message related to RRC connection reconfiguration that is applied when the execution condition is satisfied. The message regarding resetting the RRC connection may be a message used to connect to a candidate SpCell.

The terminal device may evaluate the execution conditions of the entries included in the entry list held by the terminal device. If the entry list held by the terminal device is empty or if the terminal device does not hold an entry list, it is not necessary to evaluate the execution condition.

Executing conditional reconfiguration means that when one or more execution conditions are met, the conditional reconfiguration information element included in the same entry as the one or more execution conditions is applied, and conditional reconfiguration is performed. It may be to perform an RRC reconfiguration procedure based on the configuration information element.

If there are multiple candidate cells that meet the execution conditions, the terminal device selects one cell from among the multiple candidate cells that meet the execution conditions, and executes the conditional replay associated with the selected candidate cell. Configuration information elements may be applied.

When the MAC entity of the terminal device is requested to reset of the MAC entity from an upper layer (such as RRC), the MAC entity of the terminal device may implement some or all of (A) to (O) below. The resetting of the MAC entity may be referred to as a MAC reset. Furthermore, the process in which the MAC entity of the terminal device performs some of the following (A) to (O) may be called a partial MAC reset, or the process of partially resetting the MAC entity. It can be rephrased as "Partially resetting the MAC entity" may be rephrased as "instructing the MAC entity to perform a partial reset."
(Processing MR)
(A) Initialize the parameter Bj set for each logical channel to 0.
(B) If all timers are running, stop them.
(C) Set the New Data Indicator (NDI) value of all uplink HARQ processes to 0.
(D) Stop any ongoing random access procedures, if any.
(E) Discard explicitly signaled 4-step and 2-step RA type contention-free random access (CFRA) resources, if any.
(F) Flush Msg3's buffer.
(G) Flush the MSGA buffer.
(H) Cancel the triggered SR procedure, if any.
(I) Cancel the triggered BSR procedure, if any.
(J) Cancel the triggered PHR procedure, if any.
(K) Cancel the triggered configured uplink grant confirmation, if any.
(L) Flush the soft buffers of all downlink HARQ processes.
(M) In each downlink HARQ process, consider the next received transmission for a certain transport block (TB) to be the very first transmission.
(N) Release Temporary C-RNTI, if any.
(O)Reset all BFI_COUNTERs.

The multiple Transmit/Receive Point (also referred to as multi-TRP or mTRP) operation is explained.

In mTRP operation, a serving cell receives terminal equipment from multiple TRPs (Transmit/Receive Points) to provide better coverage, reliability, and/or data rate for PDSCH, PDCCH, PUSCH, and PUCCH. Good to be able to schedule.

There may be two different operation modes for the mTRP PDSCH transmission schedule. The two operation modes may be single-DCI and multi-DCI. Control of uplink and downlink operations for both modes may be performed at the PHY and MAC layers with settings configured by the RRC layer. In single-DCI mode, a terminal device may be scheduled for both TRPs by the same DCI. In multi-DCI mode, a terminal device may be scheduled for each TRP by an independent DCI.

Each TRP of mTRPs may be specified by TRP information. For example, the TRP information may be information for identifying one TRP among one or more TRPs. For example, the TRP information may be an index for identifying one TRP. For example, one TRP may be determined based on TRP information. For example, the TRP information may be information for identifying one or more TRPs. TRP information may be used to select one TRP. The TRP information may be a CORESET pool index. One CORESET pool index and one CORESET resource set identifier may be associated with one CORESET. The terminal device may transmit the PUSCH with the corresponding TRP based on the CORESET resource set identifier. TRP information may be associated with an index of a CORESET resource pool. For example, a first CORESET pool index may be associated with a first TRP, and a second CORESET pool index may be associated with a second TRP. TRP information may be associated with a TCI state pool (or a TCI state pool index). For example, a first TCI state pool (or pool index) may be associated with a first TRP, and a second TCI state pool (or pool index) may be associated with a second TRP.

There may be two different operation modes for the mTRP PDCCH transmission schedule. The two modes of operation may be PDCCH repetition and single frequency network (SFN) based PDCCH transmission. In both modes, the terminal device may receive each of the PDCCH transmissions carrying the same DCI from each TRP. In PDCCH repetition mode, the terminal device may receive two PDCCH transmissions carrying the same DCI from two linked search spaces, each associated with a different CORESET. In SFN-based PDCCH transmission mode, a terminal device can receive two PDCCH transmissions carrying the same DCI from a single search space/CORESET with different TCI states.

In the mTRP PUSCH repetition, the terminal equipment is associated with different spatial relations corresponding to the two TRPs by the indication by the configured uplink grant provided by the single DCI or RRC signaling. PUSCH transmission of the same content may be performed in the same beam direction.

In inter-cell mTRP operations, one or more TCI states in multi-DCI PDSCH transmission may be associated with a different PCI SSB than the serving cell's Physical Cell Identity (PCI). . Further, at most one TCI state associated with a PCI different from the serving cell may be activated at a time.

Next, the central unit (CU) and distributed unit (DU) will be explained. The aggregation unit may be a logical node that hosts the RRC layer, SDAP layer, and PDCP layer of the base station device. Furthermore, the distributed unit may be a logical node that hosts the RLC layer, MAC layer, and PHY layer of the base station device. An aggregation unit may control the operation of one or more distributed units. Also, one distribution unit may support one or more cells, and one cell may be supported by only one distribution unit. That is, one distributed unit may be associated with one or more cells.

Next, layer 1/layer 2 mobility (L1/L2 mobility) in this embodiment will be explained. Layer 1/Layer 2 mobility refers to a base station device that allows a terminal device to specify one or more serving cells through a DCI or MAC control element that allows the terminal device to identify one or more cells to which the serving cell is to be targeted (changed to). It may be a procedure for instructing changes to the process. Additionally or alternatively, Layer 1/Layer 2 mobility refers to a DCI or MAC control element received by a terminal device from a base station device that causes the terminal device to identify one or more target cells of the serving cell. It may refer to the procedure of changing the serving cell to one or more indicated cells. The DCI that causes the terminal device to specify one or more cells as the target of the serving cell may be a DCI that indicates one or more cells as the target of the serving cell of the terminal device that the base station device changes. Similarly, a MAC control element that causes a terminal device to specify one or more cells as the target of the serving cell is a MAC control element that indicates one or more cells as the target of the serving cell of the terminal device that the base station device changes. It's fine. The DCI and MAC control elements that cause the terminal device to identify one or more cells as a target of the serving cell may include other information indicating a change in the serving cell. In layer 1/layer 2 mobility, the base station device causes the terminal device to identify one or more target cells of the serving cell based on one or more measurement reports received from the terminal device. The terminal device may be instructed to change one or more serving cells through the DCI or MAC control element. Note that "Layer 1/Layer 2 mobility" refers to "Layer 1/Layer 2 based inter-cell mobility (L1/L2 based inter-cell mobility)" and "Layer 1/Layer 2 inter-cell mobility (L1/L2 inter-cell mobility)". cell mobility)," "layer 1/layer 2 serving cell change processing," "layer 1/layer 2 serving cell change," or "layer 1/layer 2 handover." ``DCI that causes the terminal device to identify one or more target cells of the serving cell'' is ``DCI that instructs the terminal device to change the serving cell to one or more target cells'' and ``DCI that causes the terminal device to identify one or more target cells of the serving cell.'' "DCI for changing the serving cell," etc., and "MAC control element that allows the terminal device to identify one or more target cells of the serving cell" can be translated as "DCI for changing the serving cell to one or more target cells." It may be rephrased as "MAC control element that instructs a change" or "MAC control element that changes one or more serving cells of a terminal device." Further, DCI may be translated into layer 1 signaling, etc., and MAC control element may be translated into layer 2 signaling, etc. Layer 1 may be a PHY layer, and layer 2 may be one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Further, the above-mentioned measurements may be performed by layer 1 and/or layer 3, that is, the RRC layer.

In layer 1/layer 2 mobility, one or more cell candidates for the serving cell target of the terminal device that the base station device changes may be called a candidate cell (candidate cell), or a candidate target cell (candidate target cell). ) and other names. In Layer 1/Layer 2 mobility, one or more candidate cells are configured in a terminal device by a base station device before the terminal device changes one or more serving cells to target one or more cells. It's fine. In layer 1/layer 2 mobility, a candidate cell may be an SpCell or an SCell. In layer 1/layer 2 mobility, a group (set of cells) of one or more cell candidates for the serving cell target of the terminal device that the base station device changes is called a candidate cell group (CCG). or may be called by other names such as candidate cell set or configured cell set. In layer 1/layer 2 mobility, a CCG may be a group of some or all cells included in the MCG or SCG. In Layer 1/Layer 2 mobility, one or more CCGs are configured on a terminal device by a base station device before the terminal device changes one or more serving cells to target one or more cells. good. In layer 1/layer 2 mobility, a candidate target may be the above-mentioned candidate cell or the above-mentioned CCG. Additionally or alternatively, in Layer 1/Layer 2 mobility, candidate targets may include both candidate cells and CCGs as described above. In Layer 1/Layer 2 mobility, the target cell or cells are one or more candidate cells configured on the terminal device and/or one or more CCGs configured on the terminal device. may be one or more cells identified by a DCI or MAC control element that causes the terminal equipment to identify one or more cells as a target of the serving cell.

In Layer 1/Layer 2 mobility, settings indicating information on one or more candidate cells and/or one or more CCGs that the base station device provides to the terminal device can be configured between Layer 1/Layer 2 cells. It can also be called mobility candidate target configuration (L1/L2 inter-cell mobility candidate target configuration), and can also be referred to as candidate target configuration, candidate target configuration, candidate cell configuration, CCG configuration, etc. You can call me. Additionally or alternatively, in Layer 1/Layer 2 mobility, Layer 1/Layer 2 inter-cell mobility candidate target setting refers to information on one or more candidate targets that the base station device provides to the terminal device. It may refer to the settings shown. In Layer 1/Layer 2 mobility, the Layer 1/Layer 2 intercell mobility candidate targeting configuration may include the configuration of one or more candidate targets, and measurements and/or measurements applied to the one or more candidate targets. Alternatively, it may include radio bearer settings. In layer 1/layer 2 mobility, the base station device may prepare one or more candidate cells and provide the terminal device with a layer 1/layer 2 inter-cell mobility candidate target configuration including the configuration of the candidate cell. . At this time, upon receiving the Layer 1/Layer 2 inter-cell mobility candidate target setting, the terminal device may start measuring the candidate cell and reporting it to the base station device. In addition to or in place of that, in Layer 1/Layer 2 mobility, the base station device prepares one or more CCGs, and provides a Layer 1/Layer 2 inter-cell mobility candidate target that includes the configuration of the CCG in the terminal device. You may provide settings. At this time, when the terminal device receives the Layer 1/Layer 2 inter-cell mobility candidate target setting, it may start measuring each candidate cell of the CCG and reporting it to the base station device. For example, in Layer 1/Layer 2 mobility, the base station device notifies the terminal device of information indicating which candidate cell or which CCG it is using DCI to change one or more serving cells of the terminal device. Accordingly, the terminal device may change one or more serving cells. Also, for example, in layer 1/layer 2 mobility, the base station device transmits information indicating which candidate cell or which CCG to the terminal device in a MAC control element that changes one or more serving cells of the terminal device. A terminal device may change one or more serving cells by notifying the device.

In layer 1/layer 2 mobility, some or all of the mobility scenarios (A) to (C) below may be supported, or other mobility scenarios may be supported. In addition, in a terminal device where CA is not configured, the mobility scenario (A) below may be a scenario in which only the PCell is changed, and in a terminal device where CA is configured, the mobility scenario (A) below may be a scenario where only the PCell is changed. The mobility scenario may be a scenario in which a PCell and one or more SCells are changed.
(A) PCell change (B) Intra-DU mobility and intra-CU-inter-DU mobility (C) Inter-cell beam management

In layer 1/layer 2 mobility, the following principles (A) and/or (B) may be applied.
(A) The base station apparatus prepares layer 1/layer 2 inter-cell mobility candidate target settings so that dynamic switching can be performed without requiring full configuration.
(B) The user plane communicates continuously without resetting as much as possible to avoid data loss and additional delays for data recovery.

In Layer 1/Layer 2 mobility, Layer 1/Layer 2 inter-cell mobility candidate target settings are notified in advance by RRC signaling (A) to (C) below or other control information (RRC signaling, etc.). Optionally, the terminal device configures the Layer 1/Layer 2 inter-cell mobility candidate targeting by using a DCI or MAC control element that directs a change of serving cell from Layer 1 or Layer 2 to the target cell or cells. It may be stored until received. Further, the layer 1/layer 2 inter-cell mobility candidate target setting may be common for the intra-distributed unit mobility and the intra-aggregated unit inter-distributed unit mobility, and the layer 1/layer 2 inter-cell mobility candidate target setting may be the same. The parts may be different. Note that the Layer 1/Layer 2 inter-cell mobility candidate target setting may include part or all of system information (searchSpaceSIB1, searchSpaceOtherSystemInformation, etc.), paging messages (pagingSearchSpace, etc.), and common search spaces (commonSearchSpaceList, etc.). . Furthermore, in layer 1/layer 2 mobility, security key updates do not need to be performed.
(A) Messages regarding RRC connection reconfiguration for each candidate target (B) Cell group configuration for each candidate target (C) SpCell configuration and/or SCell configuration for each candidate target

Handover interruption time (HO interruption time) for Layer 1/Layer 2 mobility refers to the time when the terminal equipment uses DCI or MAC It may be the time from receiving a control element to performing the first downlink/uplink transmission/reception on the beam of the target cell or cells. Further, the handover interruption time for layer 1/layer 2 mobility may include time for processing some or all of (A) to (F) below. Note that "handover interruption time for layer 1/layer 2 mobility" may be rephrased as "delay for layer 1/layer 2 mobility" or the like.
(A) UE reconfiguration (B) Measurement at layer 1 and/or RRC
(C) Downlink synchronization (D) Uplink synchronization (E) TRS (Temporary RS) tracking (F) CSI-RS measurement

Based on the above description, various embodiments will be described. Note that each process explained above may be applied to each process omitted in the following description.

FIG. 5 is a block diagram showing the configuration of the terminal device (UE 122) in this embodiment. Note that in order to avoid complicating the explanation, FIG. 5 shows only the main components closely related to this embodiment.

The UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, RRC signaling, etc.) from a base station, a processing unit 502 that performs processing according to parameters included in the received control information, and a It consists of a transmitter 504 that transmits information (UCI, RRC signaling, etc.). The above-mentioned base station device may be eNB102 or gNB108. Further, the processing unit 502 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing section 502 includes some or all of the physical layer processing section, MAC layer processing section, RLC layer processing section, PDCP layer processing section, SDAP processing section, RRC layer processing section, and NAS layer processing section. It's fine.

FIG. 6 is a block diagram showing the configuration of the base station device in this embodiment. Note that in order to avoid complicating the explanation, FIG. 6 shows only the main components closely related to this embodiment. The above-mentioned base station device may be eNB102 or gNB108.

The base station device shown in FIG. , a processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a reception unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Further, the processing unit 602 may include some or all of the functions of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing section 602 includes some or all of the physical layer processing section, MAC layer processing section, RLC layer processing section, PDCP layer processing section, SDAP processing section, RRC layer processing section, and NAS layer processing section. It's fine.

An example of the processing of the terminal device in this embodiment will be explained using FIG. 11.

FIG. 11 is a diagram showing an example of the processing of the terminal device in this embodiment. The RRC 308 of the processing unit 502 of the UE 122, which has received the candidate target settings from the transmission unit 600 of the gNB 108, determines the conditions (step S1100) and operates based on the determination (step S1102).

In step S1100, the RRC 308 of the processing unit 502 of the UE 122 may determine whether any or any combination of the following (a) to (c) is satisfied.
(a) The candidate target settings include a setting to report whether or not a measurement gap is required in the NR set in setup.
(b) The previously received RRC signaling includes a setting to report whether or not a measurement gap is required in the NR set in setup.
(c) The RRC signaling including the setting of the candidate target includes a setting to report whether or not a measurement gap is required in the NR set in setup.

If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that the condition (a) is satisfied, the RRC 308 is set to provide the UE 122 with information on whether or not a measurement gap of the target frequency band of NR is required. If it is determined that the above condition (a) is not satisfied, it is not configured to provide the UE 122 with information on whether or not a measurement gap for the target frequency band of NR is required. You can judge that. If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that the condition (b) is satisfied, the RRC 308 is set to provide the UE 122 with information on whether or not a measurement gap of the target frequency band of NR is required. If it is determined that the above condition (b) is not satisfied, it is not configured to provide the UE 122 with information on whether or not a measurement gap for the target frequency band of NR is required. You can judge that. If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that the condition (c) is satisfied, the RRC 308 is set to provide the UE 122 with information on whether or not a measurement gap of the target frequency band of NR is required. If it is determined that the above condition (c) is not satisfied, it is not configured to provide the UE 122 with information on whether or not a measurement gap for the target frequency band of NR is required. You can judge that. For example, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that condition (a) or (c) is satisfied, if each candidate target set in the candidate target settings is applied. It may be determined that the UE 122 is set to be provided with information on whether or not a measurement gap of the target frequency band of NR is required. The frequency bands of the NR targets may include frequency bands for intra-frequency measurements on each candidate target set in the candidate target settings, and may include frequency bands for intra-frequency measurements on each candidate target set in the candidate target settings. may include frequency bands for inter-frequency measurements. Note that the RRC signaling described in condition (b) above may be a message regarding resetting an RRC connection, or may be other RRC signaling such as an RRC restart message.

If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that it is set to provide the UE 122 with information on whether or not the measurement gap of the target frequency band of NR is required, the RRC 308 performs the following (d) to ( It may be determined whether any or any combination of f) is satisfied.
(d) The candidate target settings include a setting to report whether or not a measurement gap is required in NR.
(e) The information indicating whether a measurement gap is required in NR has been changed compared to the last time the UE 122 reported it.
(f) Other conditions

If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that any of the conditions (d) to (f) is satisfied, in step S1102, the RRC 308 of the processing unit 502 determines the candidate target according to the above processing (NFG). Information indicating whether a measurement gap is required in NR may be included in the signaling indicating completion of the configuration. In addition to or in place of that, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that any of the conditions (d) to (f) is satisfied, the RRC 308 performs a measurement in the NR in step S1102. Signaling indicating completion of setting the candidate target, including information indicating whether a gap is required, may be submitted to lower layers (PHY 300, MAC 302, etc.) via SRB1.

If the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that it is not set to provide the UE 122 with information on whether or not the measurement gap of the target frequency band of NR is required, or (d) of the above condition If it is determined that none of the conditions from (f) to good. In addition to or in place of that, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that it is not set to provide the UE 122 with information on whether or not the measurement gap of the target frequency band of NR is required. , or if it is determined that none of the conditions (d) to (f) are satisfied, in step S1102, signaling indicating completion of setting the candidate target is sent to the lower layer (PHY300, MAC302, etc.) via SRB1. etc.).

Note that the signaling indicating the completion of setting the candidate target may be an RRC reconfiguration completion message, or may be other signaling. Additionally or alternatively, the information indicating whether measurement gaps are required in the NR includes intra-frequency measurement gaps for some or all of the candidate targets set in the candidate target settings. Necessity information may be set. In addition to or in place of that, the information indicating whether or not a measurement gap is required in the NR includes the information of the UE 122 when some or all of the candidate targets set in the candidate target settings are applied. Gap necessity information may be set for each supported NR frequency band. For example, if an information element named requestedTargetBandFilterNR is set in the candidate target settings, the UE 122 when each candidate target set in the candidate target settings is applied, which is also included in the information element named requestedTargetBandFilterNR. Gap necessity information may be set for each NR frequency band supported by the NR. Additionally or alternatively, the support of the UE 122 when each candidate target configured in the candidate target configuration is applied, for example, if an information element named requestedTargetBandFilterNR is not configured in the candidate target configuration. Corresponding gap necessity information for each NR frequency band may be set. In addition, whether or not the condition (e) is satisfied may be determined at the time when each candidate target set in the candidate target settings is applied to the UE 122. For example, if the RRC 308 of the processing unit 502 of the UE 122 determines that the condition (e) is satisfied in some of the candidate targets set in the candidate target setting, the RRC 308 determines that the condition (e) is satisfied in step S1102. may include information indicating whether a measurement gap is required in NR only for candidate targets for which May contain information. In the above explanation, "each candidate target set in the candidate target setting has been applied" means "the UE 122 has applied one or more cells included in each candidate target set in the candidate target setting". This may be rephrased as "set as a serving cell."

Another example of the processing of the terminal device in this embodiment will be explained using FIG. 11. The RRC 308 of the processing unit 502 of the UE 122, which has been instructed to change the serving cell to one or more target cells from the lower layer (layer 1 or layer 2), judges the conditions (step S1100) and (Step S1102).

In step S1100, the RRC 308 of the processing unit 502 of the UE 122 determines whether it is set to provide information on whether or not a measurement gap of the target frequency band of NR is provided, and determines whether the measurement gap of the target frequency band of NR is provided. If it is determined that provision of necessity information is set, in step S1102, according to the above-mentioned process (NFG), after the serving cell change, the NR is set to provide signaling indicating completion of the serving cell change. Information indicating whether a measurement gap is required may be included. In addition to or in place of that, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that it is set to provide information on the necessity of measurement gaps for the target frequency band of NR, the RRC 308 of the processing unit 502 of the UE 122 performs step S1102. , signaling indicating completion of the serving cell change, including information indicating whether a measurement gap is required in the NR, may be submitted to the lower layer (PHY 300, MAC 302, etc.) via SRB1. Further, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that provision of information on the necessity of measurement gap of the target frequency band of NR is not set, in step S1102, the RRC 308 of the processing unit 502 changes the serving cell. After , information indicating whether a measurement gap is required in NR may not be included in the signaling indicating completion of the serving cell change. In addition to or in place of that, if the RRC 308 of the processing unit 502 of the UE 122 determines in step S1100 that it is not set to provide information on the necessity of measurement gaps for the target frequency band of NR, the RRC 308 of the processing unit 502 of the UE 122 performs step S1102. In this case, there is no need to submit signaling indicating completion of the serving cell change to the lower layer (PHY 300, MAC 302, etc.) via SRB1. The frequency bands of the NR target may include frequency bands for intra-frequency measurements on one or more cells of the target and for inter-frequency measurements on one or more cells of the target. frequency bands. Note that the signaling indicating completion of the serving cell change may be an RRC reconfiguration completion message, or may be other signaling. Additionally or alternatively, the information indicating whether a measurement gap is required in the NR includes information on whether or not an intra-frequency measurement gap is required for the target one or more cells. It's fine. In addition to or in place of that, the information indicating whether a measurement gap is required in the NR includes information regarding the necessity of a gap for each NR frequency band supported by the UE 122 after the serving cell change. may be set. For example, if an information element named requestedTargetBandFilterNR is set in the candidate target settings, the information element for each NR frequency band supported by the UE 122 after the serving cell change is also included in the information element named requestedTargetBandFilterNR. Information on whether or not a gap is necessary may be set. Additionally or alternatively, for example, if an information element named requestedTargetBandFilterNR is not configured in the candidate target configuration, a corresponding NR frequency band for each supported NR frequency band of the UE 122 after the serving cell change. Information on whether or not a gap is necessary may be set.

Each embodiment may be combined with each other. In addition, in each embodiment, the setting to report whether or not a measurement gap is necessary in NR is the RRC signaling shown in (A) to (D) below in the candidate target setting, or other control information (RRC signaling). etc.) may be included.
(A) Messages regarding RRC connection reconfiguration for each candidate target (B) Cell group configuration for each candidate target (C) SpCell configuration and/or SCell configuration for each candidate target (D) Each candidate target Conditional reconfiguration for

Figures 12, 13, and 14 are ASN.1 descriptions representing fields and/or information elements related to candidate target configuration, respectively, as indicated by the signaling described in (A), (B), and (C) above. This is an example. In FIGS. 12, 13, and 14, the configuration of candidate targets may be represented by an information element named Candidates-L1L2-Config. In FIGS. 12 and 13, the information element named Candidates-L1L2Id may be an information element indicating the identifier of each candidate target set in the candidate target setting. Additionally or alternatively, in FIGS. 12 and 13, the information element named candidates-L1L2-CellsConfig contains the configuration of one or more candidate cells included in each candidate target identified by said identifier. May be an information element. In FIG. 14, the information element named sCell-L1L2-ToAddModList may be an addition/modification list with only SCell as an entry among the candidate cells included in the candidate target settings. Additionally or alternatively, in FIG. 14, the information element named spCell-L1L2-ToAddModList is an additional modification list with only SpCell as an entry among each candidate cell included in the candidate target setting. good.

In each embodiment, the number of candidate targets set in the candidate target setting may be one or more. Additionally or alternatively, the target cell or cells indicated by lower layers in the serving cell change may be one or more candidate cells and/or one or more CCGs. Additionally or alternatively, configuring a candidate target may include configuring one or more candidate cells and/or configuring one or more CCGs. In addition, the cell group settings described in (B) above may include SpCell settings and/or SCell settings, and the CCG settings instructed from the lower layer when changing the serving cell are applied to the cell group of the lower layer. May be applied to

According to each of the above embodiments, the RRC layer can submit to the lower layer information on whether or not a measurement gap is required for one or more target cells instructed by the lower layer when setting a candidate target or changing a serving cell. , in Layer 1/Layer 2 mobility, the UE can efficiently perform measurements.

The radio bearer in the above description may be a DRB, an SRB, or a DRB and an SRB, unless otherwise specified.

Furthermore, in the above description, expressions such as "user plane", "user plane protocol", "user plane interface", etc. may be used interchangeably.

Also, in the above explanation, "receiving a DCI or MAC control element instructing a change of serving cell to one or more target cells" is replaced with "receiving a DCI or MAC control element instructing a change of serving cell to one or more target cells." ” can be rephrased as “

Furthermore, in the above description, expressions such as "candidate target", "candidate cell", "CCG", etc. may be used interchangeably.

Furthermore, the serving cell change in the above description may be a layer 1/layer 2 serving cell change, unless otherwise specified.

Furthermore, in the above description, expressions such as "to be notified" and "to be pointed out" may be used interchangeably.

Furthermore, in the above description, expressions such as "link," "correspond," and "associate" may be used interchangeably.

Furthermore, in the above description, expressions such as "included", "included", "included", etc. may be used interchangeably.

Furthermore, in the above description, "the above ~" may be replaced with "the above ~".

Furthermore, in the above description, expressions such as "determined as ~", "~ is set", and "~ is included" may be used interchangeably.

Further, in the examples of each process or the example of the flow of each process in the above description, some or all of the steps may not be executed. Further, in the example of each process or the example of the flow of each process in the above description, the order of steps may be different. Further, in the example of each process or the example of the flow of each process in the above description, some or all of the processes in each step may not be executed. Further, in the example of each process or the example of the flow of each process in the above description, the order of the processes within each step may be different. Furthermore, in the above description, "doing B based on A" may be rephrased as "doing B." That is, "doing B" may be performed independently of "doing A".

Note that in the above description, "A may be replaced with B" may include the meaning of replacing A with B, as well as replacing B with A. Furthermore, in the above description, when "C may be D" and "C may be E" are stated, "D may be E" may also be included. Furthermore, in the above description, when "F may be G" and "G may be H" are stated, "F may be H" may also be included.

In addition, in the above explanation, if the condition "A" and the condition "B" are contradictory conditions, the condition "B" may be expressed as an "other" condition of the condition "A". good.

The program that runs on the device related to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make the computer function so as to realize the functions of this embodiment. Programs or information handled by programs are temporarily read into volatile memory such as Random Access Memory (RAM) during processing, or stored in non-volatile memory such as flash memory or Hard Disk Drive (HDD), and are stored as needed. The data is read, modified, and written by the CPU accordingly.

Note that a part of the apparatus in the embodiment described above may be realized by a computer. In that case, the program for realizing this control function may be realized by recording it on a computer-readable recording medium and causing the computer system to read and execute the program recorded on this recording medium. . The "computer system" herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of semiconductor recording media, optical recording media, magnetic recording media, and the like.

Furthermore, a "computer-readable recording medium" refers to a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In that case, it may also include something that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system. .

Additionally, each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, typically an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, or in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the circuits described above may be configured with a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

Note that this embodiment is not limited to the above-described embodiment. Although an example of the device has been described in the embodiment, the present embodiment is not limited to this, and can be applied to stationary or non-movable electronic equipment installed indoors or outdoors, such as AV equipment, kitchen equipment, etc. It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.

Although this embodiment has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and may include design changes without departing from the gist of this embodiment. Further, this embodiment can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments also fall within the technical scope of this embodiment. include. Also included are configurations in which the elements described in the above embodiments are replaced with each other and have similar effects.

One embodiment of the present invention is used in, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), a program, or the like. be able to.

100 E-UTRA
102eNB
104EPC
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interface
122 U.E.
200, 300 PHY
202, 302 MAC
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
210, 312 NAS
500, 604 Receiving section
502, 602 processing section
504, 600 transmitter

Claims (3)

1. A terminal device that communicates with a base station device,
   a receiving unit that receives a first setting indicating information about one or more candidate cells from the base station device;
   RRC processing section,
   Equipped with
   The RRC processing unit is
   Determining whether the terminal device is set to be provided with information on whether or not a measurement gap of a target frequency band of NR is provided;
   If it is determined that the terminal device is set to provide the necessity information,
   The RRC processing unit is
   determining whether the first setting includes a second setting for reporting whether a measurement gap is necessary in NR;
   If it is determined that the second setting is included in the first setting,
   The RRC processing unit is
   Signaling indicating completion of the first setting,
   including third information indicating whether a measurement gap is required in the NR;
   If it is determined that the terminal device is not set to provide the necessity information, or
   If it is determined that the second setting is not included in the first setting,
   The RRC processing unit is
   Signaling indicating completion of the first setting,
   not including the third information;
   Terminal device.
2. A method for a terminal device to communicate with a base station device, the method comprising:
   The RRC entity of the terminal device,
   receiving a first configuration indicating information on one or more candidate cells from the base station device;
   The RRC entity is
   determining whether or not the terminal device is set to be provided with information on whether or not a measurement gap of a target frequency band of NR is provided;
   If it is determined that the terminal device is set to provide the necessity information,
   The RRC entity is
   determining whether the first setting includes a second setting for reporting whether a measurement gap is required in NR;
   If it is determined that the second setting is included in the first setting,
   The RRC entity is
   Signaling indicating completion of the first setting,
   including third information indicating whether a measurement gap is required in the NR;
   If it is determined that the terminal device is not set to provide the necessity information, or
   If it is determined that the second setting is not included in the first setting,
   The RRC entity is
   Signaling indicating completion of the first setting,
   not including the third information;
   method including.
3. An integrated circuit implemented in a terminal device that communicates with a base station device,
   The RRC entity of the terminal device,
   a function of receiving a first configuration indicating information on one or more candidate cells from the base station device;
   The RRC entity is
   a function of determining whether the terminal device is set to be provided with information on whether or not a measurement gap of a target frequency band of NR is provided;
   If it is determined that the terminal device is set to provide the necessity information,
   The RRC entity is
   a function of determining whether the first setting includes a second setting for reporting whether a measurement gap is necessary in NR;
   If it is determined that the second setting is included in the first setting,
   The RRC entity is
   Signaling indicating completion of the first setting,
   a function of including third information indicating whether a measurement gap is necessary in NR;
   If it is determined that the terminal device is not set to provide the necessity information, or
   If it is determined that the second setting is not included in the first setting,
   The RRC entity is
   Signaling indicating completion of the first setting,
   a function of not including the third information;
   Integrated circuits that bring out the best in you.

Images