Terminal device, base station device, and method

Abstract

According to the present invention, when a second cell group is deactivated, a terminal device, on the basis of whether a measurement identifier of a measurement that is configured is included in a reconfiguration execution condition field of a conditional PSCell modification setting information element, determines whether to delete the measurement of the measurement identifier.

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a base station device, and a method. This application claims priority to Japanese Patent Application No. 2020-219736, filed on December 29, 2020, the contents of which are incorporated herein by reference. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP), a standardization project for cellular mobile communication systems, is conducting technical studies and formulating standards for cellular mobile communication systems, including radio access, core networks, services, etc.

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

[0004] Additionally, 3GPP has begun technical studies and standardization of NR (New Radio, or NR Radio access) as a radio access technology (RAT) for 5th Generation (5G) cellular mobile communication systems. 3GPP is currently conducting technical studies and standardization of NR extension technologies. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v16.2.0,"NR;NR and NG-RAN Overall description; Stage 2" pp10-134 [Non-patent document 2] 3GPP TS 36.300 v16.2.0,"Evolved Universal Terrestrial Radio Access (E-UTRA)and Evolved Universal Terrestrial Radio Access Network (E-UTRAN);Overall description; Stage 2" pp19-361 [Non-patent document 3] 3GPP TS 38.331 v16.2.0,"NR;Radio Resource Control (RRC);Protocol specifications"pp21-861 [Non-patent document 4] 3GPP TS 36.331 v16.1.0,"Evolved Universal Terrestrial Radio Access (E-UTRA);Radio Resource Control (RRC);Protocol specifications" pp25-1012 [Non-Patent Document 5] 3GPP TS 37.340 v16.2.0,"EvolvedUniversal Terrestrial Radio Access (E-UTRA)and NR; Multi-Connectivity; Stage 2" pp6-67 [Non-patent document 6] 3GPP TS 38.321 v16.1.0, "NR;Medium Access Control (MAC) protocol specification" pp8-148 Summary of the Invention [Problem to be solved by the invention]

[0006] As an extension of NR, there is a dual connectivity (also called multi-connectivity) technology that enables communication between one or more base station devices and a terminal device using multiple cell groups to enable large-volume data communication. With this dual connectivity, in order to communicate in each cell group, the terminal device must monitor each cell group for messages addressed to it. To ensure low-latency communication when large-volume data communication occurs, the terminal device must constantly monitor multiple cell groups, which poses a problem of consuming a lot of power. For this reason, research is being conducted on a technology that reduces the frequency of monitoring some cell groups or stops monitoring them altogether (cell group deactivation technology).

[0007] In addition to the operation of a terminal device when a cell group is in an inactive state, the operation of a terminal device when it is activated (returned) from an inactive state is also being studied.

[0008] When a cell group is in an inactive state, the terminal device needs to perform the processing required to quickly start communication when the cell group becomes active.

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

[0010] In order to achieve the above object, one aspect of the present invention provides the following measures: That is, one aspect of the present invention provides a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, the terminal device comprising: a processing unit that processes an RRC message received from the base station device; and a measurement unit that performs measurement based on a measurement configuration included in the RRC message, wherein the measurement configuration includes information on measurement targets, reporting conditions, and a measurement identifier that links the measurement targets and the reporting conditions; when deactivating the second cell group, the terminal device determines whether to delete a measurement for the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element; and deletes the measurement for the measurement identifier based at least on the measurement identifier not being included in the reconfiguration execution condition field of the conditional PSCell modification configuration information element.

[0011] Another aspect of the present invention is a base station device that communicates with a terminal device, comprising: a transmitting unit that transmits an RRC message to the terminal device; and a processing unit that generates an RRC message to be transmitted to the terminal device, wherein the measurement configuration included in the RRC message includes information on a measurement target, a reporting configuration, and a measurement identifier that links the measurement target and the reporting configuration, and by instructing the terminal device to deactivate a secondary cell group, the base station device is caused to delete the measurement of the measurement identifier based at least on the fact that the measurement identifier is not included in a reconfiguration execution condition field of a conditional PSCell change configuration information element.

[0012] Another aspect of the present invention is a method applied to a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, the method comprising the steps of: processing an RRC message received from the base station device; and performing measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes information on measurement targets, reporting conditions, and a measurement identifier that links the measurement targets and the reporting conditions; when deactivating the second cell group, determining whether to delete the measurement for the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element; and deleting the measurement for the measurement identifier based at least on the measurement identifier not being included in the reconfiguration execution condition field of the conditional PSCell modification configuration information element.

[0013] Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and causes the terminal device to perform functions of processing RRC messages received from the base station devices and performing measurements based on measurement configurations included in the RRC messages, where the measurement configurations include information on measurement targets, reporting conditions, and measurement identifiers that link the measurement targets and reporting conditions, and when deactivating the second cell group, determines whether to delete (pause, disable) the measurement of the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element, and deletes the measurement of the measurement identifier based at least on the fact that the measurement identifier is not included in the reconfiguration execution condition field of the conditional PSCell modification configuration information element.

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

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

[0016] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram illustrating an example of an E-UTRA protocol configuration according to an embodiment of the present invention. [Figure 3] FIG. 1 is a diagram of an example of an NR protocol configuration according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram showing an example of a flow of procedures for various settings in an RRC according to an embodiment of the present invention. [Figure 5] FIG. 2 is a block diagram showing the configuration of a terminal device according to an embodiment of the present invention. [Figure 6] FIG. 1 is a block diagram showing a configuration of a base station device according to an embodiment of the present invention. [Figure 7] An example of an ASN.1 description included in a message regarding re-establishment of an RRC connection in NR in an embodiment of the present invention. [Figure 8] 10 is an example of an ASN.1 description included in a message regarding re-establishment of an RRC connection in E-UTRA according to an embodiment of the present invention. [Figure 9] 3 shows an example of ASN.1 description of an RRC reconfiguration message according to an embodiment of the present invention. [Figure 10] 10 shows an example of ASN.1 description of a cell group configuration information element in the embodiment of the present invention. [Figure 11] 10 shows an example of an ASN.1 description of SpCell settings in an embodiment of the present invention. [Figure 12] 10 is an example of ASN.1 description of a synchronization-attached reconfiguration information element according to an embodiment of the present invention. [Figure 13] 10 shows an example of an ASN.1 description of a ServingCellConfigCommon information element in the embodiment of the present invention. [Figure 14] 10 shows an example of ASN.1 description of an SCell configuration information element according to an embodiment of the present invention. [Figure 15] 10 shows an example of processing by a terminal device according to an embodiment of the present invention. [Figure 16] 10 shows an example of processing by a terminal device according to an embodiment of the present invention. [Figure 17] 10 shows an example of processing by a terminal device according to an embodiment of the present invention. [Figure 18] 10 is an example of an ASN.1 description representing fields and / or information elements related to the setting of a conditional PSCell change in an embodiment of the present invention. [Figure 19] FIG. 4 is a diagram showing an example of processing performed by a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0018] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different radio access technologies (RATs). NR may also be defined as a technology included in LTE. LTE may also be defined as a technology included in NR. LTE that can connect to NR via Multi Radio Dual connectivity (MR-DC) may be distinguished from conventional LTE. LTE that uses 5GC in the core network may be distinguished from conventional LTE that uses EPC in the core network. Conventional LTE may refer to LTE that does not implement technologies standardized in 3GPP Release 15 or later. Embodiments of the present invention may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR are used; however, embodiments of the present invention may be applied to other technologies that use other terminology. In the embodiments of the present invention, the term E-UTRA may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

[0019] In the embodiments of the present invention, the names of the nodes and entities and the processes performed by the nodes and entities are described when the radio access technology is E-UTRA or NR, but the embodiments of the present invention may be used for other radio access technologies. The names of the nodes and entities in the embodiments of the present invention may be different names.

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

[0021] E-UTRA 100 may be a radio access technology. E-UTRA 100 may also be an air interface between UE 122 and eNB 102. The air interface between UE 122 and eNB 102 may be referred to as a Uu interface. eNB (E-UTRAN Node B) 102 may be a base station device of E-UTRA 100. eNB 102 may have an E-UTRA protocol, which will be described later. The E-UTRA protocol may be configured from 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. eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol for UE 122. A radio access network configured by eNBs may be referred to as E-UTRAN.

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

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

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

[0025] 5GC110 may be a core network. Interface 116 is an interface between gNB108 and 5GC110 and may be referred to as an NG interface. Interface 116 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of interface 116 may terminate in an Access and Mobility Management Function (AMF: not shown) in 5GC110. The user plane interface of interface 116 may terminate in a User Plane Function (UPF: not shown) in 5GC110. The control plane interface of interface 116 may be referred to as an NG-C interface. The user plane interface of interface 116 may be referred to as an NG-U interface.

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

[0027] The eNB102 may have the function of connecting to the 5GC110. The eNB102 with the function of connecting to the 5GC110 may be referred to as an ng-eNB. The interface 114 is an interface between the eNB102 and the 5GC110 and may be referred to as an NG interface. The interface 114 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 114 may terminate in an Access and Mobility Management Function (AMF: not shown) in the 5GC110. The user plane interface of the interface 114 may terminate in a User Plane Function (UPF: not shown) in the 5GC110. The control plane interface of the interface 114 may be referred to as an NG-C interface. The user plane interface of the interface 114 may be referred to as an NG-U interface. A radio access network consisting of an ng-eNB or a gNB may be referred to as an NG-RAN. The NG-RAN, E-UTRAN, eNB, ng-eNB, gNB, etc. may be simply referred to as a network.

[0028] Note that one or more eNBs 102 may be connected to 5GC 110 via interface 114. An interface may exist between multiple eNBs 102 connected to 5GC 110 (not shown). The interface between multiple eNBs 102 connected to 5GC 110 may be referred to as an Xn interface. Furthermore, an eNB 102 connected to 5GC 110 and a gNB 108 connected to 5GC 110 may be connected by interface 120. The interface 120 between an eNB 102 connected to 5GC 110 and a gNB 108 connected to 5GC 110 may be referred to as an Xn interface.

[0029] The gNB 108 may have the function of connecting to the EPC 104. A gNB 108 with the function of connecting to the EPC 104 may be referred to as an en-gNB. Interface 118 is an interface between the gNB 108 and the EPC 104 and may be referred to as an S1 interface. A user plane interface through which user data passes may exist in interface 118. The user plane interface of interface 118 may terminate in an S-GW (not shown) in the EPC 104. The user plane interface of interface 118 may be referred to as an S1-U interface. Furthermore, the eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be connected by interface 120. The interface 120 between the eNB 102 connecting to the EPC 104 and the gNB 108 connecting to the EPC 104 may be referred to as an X2 interface.

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

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

[0032] When the UE 122 communicates with the eNB 102 and / or the gNB 108, a radio connection may be established by establishing a radio bearer (RB) between the UE 122 and the eNB 102 and / or the gNB 108. A radio bearer used for CP may be referred to as a signaling radio bearer (SRB). A radio bearer used for UP may be referred to as a data radio bearer (DRB Data Radio Bearer). Each radio bearer may be assigned a radio bearer identity (ID). A radio bearer identity for an SRB may be referred to as an SRB identity (SRB ID). A radio bearer identity for a DRB may be referred to as a DRB identity (DRB ID).

[0033] Furthermore, the UE 122 may be a terminal device capable of connecting to the EPC 104 and / or the 5GC 110 via the eNB 102 and / or the gNB 108. When the core network to which the eNB 102 and / or the gNB 108, with which the UE 122 communicates, is connected is the EPC 104, each DRB established between the UE 122 and the eNB 102 and / or the gNB 108 may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104. Each EPS bearer may be identified by an EPS bearer identifier (identity, or ID). Furthermore, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same EPS bearer.

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

[0035] There may be no PDU sessions and / or QoS flows in the EPC 104, and no EPS bearers in the 5GC 110. When the UE 122 is connected to the EPC 104, the UE 122 has information about the EPS bearers, but may not have information about the PDU sessions and / or QoS flows. When the UE 122 is connected to the 5GC 110, the UE 122 has information about the PDU sessions and / or QoS flows, but may not have information about the EPS bearers.

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

[0037] FIG. 2 is a diagram showing an example of an E-UTRA protocol architecture according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of an NR protocol architecture according to an embodiment of the present invention. Note that the functions of each protocol described using FIG. 2 and / or FIG. 3 are only some of the functions closely related to the embodiment of the present invention, and other functions may also be included. Note that in the embodiment of the present invention, an uplink (UL) may be a link from a terminal device to a base station device. Also, in each embodiment of the present invention, a downlink (DL) may be a link from a base station device to a terminal device.

[0038] 2A is a diagram of an E-UTRA user plane (UP) protocol stack. As shown in FIG. 2A, the E-UTRAN UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRAN UP protocol may be a protocol that terminates at the eNB 102 on the network side. As shown in FIG. 2A, the E-UTRA user plane protocol stack may be composed of a PHY (Physical layer) 200, which is a radio physical layer, a MAC (Medium Access Control) 202, which is a medium access control layer, a RLC (Radio Link Control) 204, which is a radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206, which is a packet data convergence protocol layer.

[0039] FIG. 3A is a diagram of an NR user plane (UP) protocol stack. As shown in FIG. 3A, 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 FIG. 3A, the E-UTRA user plane protocol stack may be composed of a radio physical layer PHY 300, a medium access control layer MAC 302, a radio link control layer RLC 304, a packet data convergence protocol layer PDCP 306, and a service data adaptation protocol layer SDAP (Service Data Adaptation Protocol) 310.

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

[0041] 3B is a diagram of the NR control plane (CP) protocol configuration. As shown in FIG. 3B, in the NR CP protocol, the radio resource control layer RRC 308 may be a protocol between the UE 122 and the gNB 108. That is, the RRC 308 may be a protocol that terminates at the gNB 108 on the network side. Also, in the E-UTRAN CP protocol, the non-AS layer NAS 312 may be a protocol between the UE 122 and the AMF. That is, the NAS 312 may be a protocol that terminates at the AMF on the network side.

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

[0043] In the embodiments of the present invention, the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used without distinguishing between the E-UTRA protocol and the NR protocol. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may respectively refer to the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, or the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the NR protocol. The SDAP (SDAP layer) may also be the SDAP (SDAP layer) of the NR protocol.

[0044] In the embodiments of the present invention, when distinguishing between E-UTRA protocols and NR protocols, the PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 may be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. The PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 may also be referred to as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. Furthermore, when distinguishing between E-UTRA protocols and NR protocols, PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Furthermore, PHY 200, MAC 302, RLC 304, PDCP 306, and RRC 308 may be referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

[0045] This section describes entities in the AS layer of E-UTRA and / or NR. An entity having some or all of the functions of the MAC layer may be referred to as a MAC entity. An entity having some or all of the functions of the RLC layer may be referred to as an RLC entity. An entity having some or all of the functions of the PDCP layer may be referred to as a PDCP entity. An entity having some or all of the functions of the SDAP layer may be referred to as an SDAP entity. An entity having some or all of the functions of the RRC layer may be referred to as an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0046] 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, may be referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Data provided from upper layers to MAC, RLC, PDCP, and SDAP, and / or data provided from MAC, RLC, PDCP, and SDAP to upper layers may be referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may be referred to as an RLC SDU segment. A layer may also be referred to as a layer.

[0047] An example of the functions of the PHY will be described. The PHY of the terminal device may have a function to receive 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 to transmit data to the PHY of the base station device via an uplink (UL) physical channel. The PHY may be connected to a higher MAC via a transport channel. The PHY may pass data to the MAC via the transport channel. The PHY may also be provided with data from the MAC via the transport channel. In the PHY, an RNTI (Radio Network Temporary Identifier) ​​may be used to identify various control information.

[0048] Here, the physical channels will be described.

[0049] The physical channels used for wireless communication between a terminal device and a base station device may include the following physical channels.

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

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

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

[0053] 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 transmitting the downlink control information. That is, a field for the downlink control information may be defined as DCI and mapped to information bits. The PDCCH may be transmitted in PDCCH candidates. The terminal device may monitor a set of PDCCH candidates in a serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The DCI format may be used for scheduling the PUSCH in the serving cell. The PUSCH may be used for transmitting user data, transmitting an RRC message (described later), and the like.

[0054] 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 an uplink shared channel (UL-SCH) resource. The uplink control information may also include a hybrid automatic repeat request ACKnowledgement (HARQ-ACK).

[0055] The PDSCH may be used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer, and may also be used to transmit system information (SI) and random access responses (RAR) in the downlink.

[0056] The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and / or CSI together with uplink data. The PUSCH may also be used to transmit only CSI, or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI. The PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as an RRC message) and MAC control elements. Here, in the PDSCH, the RRC signaling transmitted from the base station apparatus may be signaling common to multiple terminal apparatuses in a cell. The RRC signaling transmitted from the base station apparatus may also be signaling dedicated to a certain terminal apparatus (also referred to as dedicated signaling). That is, terminal apparatus-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal apparatus. The PUSCH may also be used to transmit UE capabilities in the uplink.

[0057] The PRACH may be used to transmit a random access preamble and may be used for initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustment) for uplink transmissions, and to indicate requests for PUSCH (UL-SCH) resources.

[0058] An example of the function of the MAC will be described below. The MAC may be called a MAC sublayer.

[0059] The MAC may have the function of mapping various logical channels to corresponding transport channels. A logical channel may be identified by a logical channel identity (or logical channel ID). The MAC may be connected to the higher-level RLC via a logical channel. Depending on the type of information to be transmitted, the logical channel may be divided into a control channel that transmits control information and a traffic channel that transmits user information. The logical channel may also be divided into an uplink logical channel and a downlink logical channel. The MAC may have the function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. The MAC may also have the function of demultiplexing MAC PDUs provided by the PHY and providing them to the higher layer via the logical channel to which each MAC SDU belongs.

[0060] The MAC may also have a function for performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a scheduling report (SR) function for reporting scheduling information. The MAC may also have a function for performing priority processing between terminal devices using dynamic scheduling. The MAC may also have a function for performing priority processing between logical channels within one terminal device. The MAC may also have a function for performing priority processing of overlapping resources within one terminal device.

[0061] The E-UTRA MAC may have the capability to identify Multimedia Broadcast Multicast Services (MBMS), and the NR MAC may have the capability to identify Multicast / Broadcast Services (MBS).

[0062] The MAC may have a function for selecting a transport format, a function for performing discontinuous reception (DRX) and / or discontinuous transmission (DTX), a function for executing a random access (RA) procedure, a power headroom report (PHR) function for reporting information on available transmission power, a buffer status report (BSR) function for reporting information on the amount of data in the transmission buffer, etc.

[0063] The NR MAC may have a bandwidth adaptation (BA) function. The MAC PDU format used in the E-UTRA MAC may differ from the MAC PDU format used in the NR MAC. The MAC PDU may also include a MAC control element (MAC CE), which is an element for controlling the MAC.

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

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

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

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

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

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

[0070] The MTCH (Multicast Traffic Channel) may be a point-to-multipoint downlink channel for transmitting data from a base station to a terminal. The MTCH may be a multicast logical channel. The MTCH may be used by a terminal only when the terminal receives MBMS.

[0071] The MCCH (Multicast Control Channel) may be a point-to-multipoint downlink channel for transmitting MBMS control information for one or more MTCHs from a base station device to a terminal device. The MCCH may be a multicast logical channel. The MCCH may be used by a terminal device only when the terminal device receives MBMS or is interested in receiving MBMS.

[0072] The SC-MTCH (Single Cell Multicast Traffic Channel) may be a point-to-multipoint downlink channel for transmitting data from a base station device to a terminal device using SC-PTM. The SC-MTCH may be a multicast logical channel. The SC-MTCH may be used by a terminal device only when the terminal device receives MBMS using SC-PTM (Single Cell Point-To-Multipoint).

[0073] The SC-MCCH (Single Cell Multicast Control Channel) may be a point-to-multipoint downlink channel for transmitting MBMS control information for one or more SC-MTCHs from a base station device to a terminal device. The SC-MCCH may be a multicast logical channel. The SC-MCCH may be used by a terminal device only when the terminal device receives MBMS using SC-PTM or is interested in receiving MBMS using SC-PTM.

[0074] This section describes the mapping of logical channels and transport channels for the uplink in E-UTRA and / or NR.

[0075] The CCCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0076] The DCCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0077] The DTCH may be mapped to an uplink shared channel (UL-SCH), which is an uplink transport channel.

[0078] This section describes the mapping of logical channels and transport channels for the downlink in E-UTRA and / or NR.

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

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

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

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

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

[0084] The MTCH may be mapped to a Multicast Channel (MCH), which is a downlink transport channel.

[0085] The MCCH may be mapped to a Multicast Channel (MCH), which is a downlink transport channel.

[0086] The SC-MTCH may be mapped to a DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0087] The SC-MTCH may be mapped to a DL-SCH (Downlink Shared Channel), which is a downlink transport channel.

[0088] An example of the function of the RLC will be described below: The RLC may be called an RLC sublayer.

[0089] The E-UTRA RLC may have a function to segment and / or concatenate data provided from the PDCP of the upper layer and provide it to the lower layer. The E-UTRA RLC may have a function to reassemble and reorder the data provided from the lower layer and provide it to the upper layer.

[0090] The NR RLC may have the function of adding a sequence number to data provided by the PDCP in the upper layer that is independent of the sequence number added by the PDCP. The NR RLC may also have the function of segmenting data provided by the PDCP and providing it to the lower layer. The NR RLC may also have the function of reassembling data provided by the lower layer and providing it to the upper layer. The RLC may also have the function of retransmitting data and / or requesting retransmission (Automatic Repeat reQuest: ARQ).

[0091] RLC may also have a function to perform error correction using ARQ. The control information sent from the receiving side of RLC to the transmitting side to indicate data that needs to be retransmitted in order to perform ARQ may be called a status report. The instruction to send a status report sent from the transmitting side of RLC to the receiving side may be called a poll. RLC may also have a function to detect data duplication. RLC may also have a function to discard data.

[0092] RLC may have three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). In TM, data received from a higher layer is not segmented and no RLC header is added. The TM RLC entity is a unidirectional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, data received from a higher layer is segmented and / or combined, and an RLC header is added, but data retransmission control is not performed. The UM RLC entity may be a unidirectional entity or a bidirectional entity. If the UM RLC entity is a unidirectional entity, it may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is a bidirectional entity, it may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, it may perform operations such as segmenting and / or combining data received from a higher layer, adding an RLC header, and controlling data retransmission. 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 in TM and / or data provided from a lower layer may be referred to as a TMD PDU. Also, data provided to a lower layer in UM and / or data provided from a lower layer may be referred to as a UMD PDU. Also, data provided to a lower layer in AM or data provided from a lower layer may be referred to as an AMD PDU.

[0093] The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. RLC PDUs may include data RLC PDUs and control RLC PDUs. Data RLC PDUs may be called RLC DATA PDUs (RLC Data PDUs). Control RLC PDUs may be called RLC CONTROL PDUs (RLC Control PDUs).

[0094] An example of the function of PDCP will be described below. PDCP may be called a PDCP sublayer.

[0095] PDCP may have a function for maintaining sequence numbers. PDCP may also have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over wireless interfaces. The protocol used for IP packet header compression / decompression may be called the ROHC (Robust Header Compression) protocol. The protocol used for Ethernet frame header compression / decompression may be called the EHC (Ethernet(R) Header Compression) protocol. PDCP may also have a data encryption / decryption function. PDCP may also have a data integrity protection / verification function. PDCP may also have a re-ordering function. PDCP may also have a PDCP SDU retransmission function. PDCP may also have a data discard function using a discard timer. PDCP may also have a duplication function. PDCP may also have a function for discarding duplicately received data.

[0096] The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from that used in NR PDCP. PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called a PDCP DATA PDU (PDCP Data PDU). The control PDCP PDU may be called a PDCP CONTROL PDU (PDCP Control PDU).

[0097] An example of the function of the SDAP will be described below: SDAP is a service data adaptation protocol layer.

[0098] The SDAP may have the function of mapping the downlink QoS flow sent from the 5GC 110 to the terminal device via the base station device to a data radio bearer (DRB), and / or the function of mapping the uplink QoS flow sent from the terminal device to the 5GC 110 via the base station device to a DRB. The SDAP may also have the function of storing mapping rule information. The SDAP may also have the function of marking a QoS flow identifier (QoS Flow ID: QFI). Note that SDAP PDUs may include data SDAP PDUs and control SDAP PDUs. The data SDAP PDU may be called an SDAP DATA PDU (SDAP Data PDU). The control SDAP PDU may be called an SDAP CONTROL PDU (SDAP Control PDU). Note that one SDAP entity in the terminal device may exist for each PDU session.

[0099] An example of the RRC function will be described.

[0100] The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. The RRC may have a paging function from the gNB 108 or the eNB 102 connected to the 5GC 100. The RRC may also have an RRC connection management function. The RRC may also have a radio bearer control function. The RRC may also have a cell group control function. The RRC may also have a mobility control function. The RRC may also have terminal device measurement reporting and terminal device measurement reporting control functions. The RRC may also have a QoS management function. The RRC may also have a radio link failure detection and recovery function. The RRC may use 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. 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.

[0101] The RRC message may be sent using the BCCH of the logical channel, may be sent using the PCCH of the logical channel, may be sent using the CCCH of the logical channel, may be sent using the DCCH of the logical channel, or may be sent using the MCCH of the logical channel.

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

[0103] RRC messages transmitted in the uplink (UL) direction using the CCCH may include, for example, an RRC setup request message (RRC Setup Request), an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request message (RRC System Info Request), etc. Also, for example, an RRC connection request message (RRC Connection Request), an RRC connection resume request message (RRC Connection Resume Request), an RRC connection reestablishment request message (RRC Connection Reestablishment Request), etc. Other RRC messages may also be included.

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

[0105] RRC messages transmitted in the uplink (UL) direction using the DCCH may include, for example, a Measurement Report message, an RRC connection reconfiguration complete message, an RRC connection setup complete message, an RRC connection reestablishment complete message, a security mode complete message, a UE capability information message, etc. Also, for example, a Measurement Report message, an RRC reconfiguration complete message, an RRC setup complete message, an RRC reestablishment complete message, an RRC resume complete message, a security mode complete message, a UE capability information message, etc. Other RRC messages may also be included.

[0106] RRC messages transmitted in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message, an RRC connection release message, a security mode command message, a UE capability inquiry message, etc. Also, for example, an RRC reconfiguration message, an RRC resume message, an RRC release message, an RRC reestablishment message, a security mode command message, a UE capability inquiry message, etc. Other RRC messages may also be included.

[0107] An example of the functions of the NAS will be described. The NAS may have an authentication function. The NAS may also have a function for performing mobility management. The NAS may also have a security control function.

[0108] The above-mentioned functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS are merely examples, and some or all of the functions may not be implemented. Also, some or all of the functions of each layer may be included in another layer.

[0109] Note that layers (not shown) above the AS layer of the terminal device may include an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and the like. Furthermore, an Ethernet layer may be present above the AS layer of the terminal device. The layer above the AS layer of the terminal device may be called a PDU layer (PDU layer). The PDU layer may include an IP layer, a TCP layer, a UDP layer, an Ethernet layer, and the like. An application layer may be present above the IP layer, the TCP layer, the UDP layer, the Ethernet layer, the PDU layer, and the like. The application layer may include SIP (Session Initiation Protocol) and SDP (Session Description Protocol) used in IMS (IP Multimedia Subsystem), which is one of the service networks standardized by 3GPP. Furthermore, the application layer may include RTP (Real-time Transport Protocol) used for media communication, and / or protocols such as RTCP (Real-time Transport Control Protocol) and HTTP (HyperText Transfer Protocol) for media communication control. Furthermore, the application layer may include codecs for various media. The RRC layer may also be a layer above the SDAP layer.

[0110] Next, the states and state transitions of the UE 122 in LTE and NR will be described.

[0111] When the UE 122 connected to the EPC or 5GC has an RRC connection established, the UE 122 may be in an RRC_CONNECTED state. The state in which the RRC connection is established may include a state in which the UE 122 holds some or all of the UE context described below. The state in which the RRC connection is established may also include a state in which the UE 122 can transmit and / or receive unicast data. The UE 122 may be in an RRC_INACTIVE state when the RRC connection is suspended. The UE 122 may be in the RRC_INACTIVE state when the UE 122 is connected to 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 an RRC_IDLE state.

[0112] Note that when UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the suspension of the RRC connection may be initiated by E-UTRAN. When UE 122 is connected to the EPC, when the RRC connection is suspended, UE 122 may transition to the RRC_IDLE state while retaining the UE AS context and an identifier (resumeIdentity) used for resuming. A layer above the RRC layer of UE 122 (e.g., the NAS layer) may initiate the resumption of the suspended RRC connection when UE 122 retains the UE AS context, the E-UTRAN has permitted resumption of the RRC connection, and UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0113] The definition of RRC connection suspension may be different for UE 122 connected to EPC 104 and UE 122 connected to 5GC 110. In addition, all or part of the procedure for UE 122 to recover from RRC connection suspension may be different when UE 122 is connected to EPC (when suspended in RRC_IDLE state) and when UE 122 is connected to 5GC (when suspended in RRC_INACTIVE state).

[0114] The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be referred to as the RRC connected mode, RRC inactive mode, and RRC idle mode, respectively, or may simply be referred to as the connected mode, inactive mode, and idle mode, if there is no risk of misunderstanding.

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

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

[0117] A cell group configured by a base station device for a terminal device will now be described. A cell group may consist of only one special cell (SpCell). Alternatively, a cell group may consist of one SpCell and one or more secondary cells (SCells). That is, a cell group may consist of one SpCell and, optionally, one or more SCells. Note that when a MAC entity is associated with a master cell group (MCG), the SpCell may refer to a primary cell (PCell). Also, when a MAC entity is associated with a secondary cell group (SCG), the SpCell may refer to a primary SCG cell (PSCell). Also, when a MAC entity is not associated with a cell group, the SpCell may refer to a PCell. The PCell, PSCell, and SCell are serving cells. The SpCell may support PUCCH transmission and contention-based random access. The SpCell may always be in an activated state. The PCell may be a cell used in the RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. The PCell may also be a cell used in the RRC connection re-establishment procedure when a terminal device re-establishes an RRC connection. The PCell may also be a cell used in the random access procedure during handover. The PSCell may be a cell used in the random access procedure when adding a secondary node (SN), which will be described later. The SpCell may also be a cell used for purposes other than those mentioned above. Note that when a cell group is composed of an SpCell and one or more SCells, it can be said that carrier aggregation (CA) is configured for this cell group.Furthermore, for a terminal device in which CA is configured, a cell that provides additional radio resources to an SpCell may refer to an SCell.

[0118] A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for the uplink configured cells may be called a Timing Advance Group (TAG). A TAG including an SpCell of a MAC entity may refer to a Primary Timing Advance Group (PTAG). A TAG other than the above PTAG may refer to a Secondary Timing Advance Group (STAG).

[0119] Furthermore, when Dual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC) is performed, a cell group may be added from a base station device to a terminal device. DC may be a technology for performing data communication using radio resources of cell groups configured by a first base station device (first node) and a second base station device (second node). MR-DC may be a technology included in DC. To perform DC, a first base station device may add a second base station device. The first base station device may be called a master node (MN). A cell group configured by the master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). A cell group configured by the secondary node may be called a secondary cell group (SCG). The master node and the secondary node may be configured within the same base station device.

[0120] Furthermore, when a DC is not configured, a cell group configured in a terminal device may be called an MCG. Furthermore, when a DC is not configured, an SpCell configured in a terminal device may be a PCell.

[0121] Note that MR-DC may be a technology that performs DC using E-UTRA for MCG and NR for SCG. MR-DC may also be a technology that performs DC using NR for MCG and E-UTRA for SCG. MR-DC may also be a technology that performs DC using NR for both MCG and SCG. Examples of MR-DC that use E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) that uses EPC for the core network, and NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) that uses 5GC for the core network. Examples of MR-DC that use NR for MCG and E-UTRA for SCG include NE-DC (NR-E-UTRA Dual Connectivity) that uses 5GC for the core network. Examples of MR-DC that use NR for both MCG and SCG include NR-DC (NR-NR Dual Connectivity) that uses 5GC for the core network.

[0122] In addition, in the terminal device, one MAC entity may exist for each cell group. For example, when DC or MR-DC is configured in the terminal device, there may be one MAC entity for the MCG and one MAC entity for the SCG. The MAC entity for the MCG in the terminal device may always be established in the terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state). The MAC entity for the SCG in the terminal device may be created by the terminal device when an SCG is configured in the terminal device. The MAC entity for each cell group in the terminal device may be configured by the terminal device receiving an RRC message from the base station device. In EN-DC and NGEN-DC, the MAC entity for the MCG may be an E-UTRA MAC entity, and the MAC entity for the SCG may be an NR MAC entity. In NE-DC, the MAC entity for the MCG may be an NR MAC entity, and the MAC entity for the SCG may be an E-UTRA MAC entity. In NR-DC, both the MAC entities for the MCG and the SCG may be NR MAC entities. The existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell, and one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

[0123] Radio bearers will now be described. SRB0 to SRB2 may be defined as SRBs for E-UTRA, or other SRBs may be defined. SRB0 to SRB3 may be defined as SRBs for NR, or other SRBs may be defined.

[0124] SRB0 may be an SRB for RRC messages that are transmitted and / or received using the logical channel CCCH.

[0125] SRB1 may be an SRB for RRC messages and for NAS messages before the establishment of SRB2. RRC messages transmitted and / or received using SRB1 may include piggybacked NAS messages. All RRC and NAS messages transmitted and / or received using SRB1 may use the logical channel DCCH.

[0126] SRB2 may be an SRB for NAS messages and RRC messages including logged measurement information. All RRC and NAS messages sent and / or received using SRB2 may use the logical channel DCCH. SRB2 may also have a lower priority than SRB1.

[0127] SRB3 may be an SRB for transmitting and / or receiving specific RRC messages when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. The logical channel DCCH may be used for all RRC messages and NAS messages transmitted and / or received using SRB3. Other SRBs may also be provided for other uses. DRB may be a radio bearer for user data. The logical channel DTCH may be used for RRC messages transmitted and / or received using DRB.

[0128] The following describes a radio bearer in a terminal device. The radio bearer may include an RLC bearer. The RLC bearer may consist of one or two RLC entities and logical channels. When an RLC bearer has two RLC entities, the RLC entities may be a TM RLC entity and / or a transmitting RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity.

[0129] 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 be always established in a terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state). SRB1 may be established and / or configured in a terminal device by an RRC message received from a base station device when the terminal device transitions from an RRC idle state to an RRC connected state. SRB1 may consist of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may consist of an AM RLC entity and a logical channel. SRB2 may be established and / or configured in a terminal device by an RRC message received from a base station device in an RRC connected state with AS security activated. SRB2 may consist of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB2 may consist of an AM RLC entity and a logical channel. The PDCPs of SRB1 and SRB2 on the base station device side may be placed in the master node. When a secondary node in EN-DC, NGEN-DC, or NR-DC is added or the secondary node is changed, one SRB3 may be established and / or configured in the terminal device by an RRC message received from the base station device by a terminal device in an RRC connected state with AS security activated. 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 RLC bearer of SRB3 may consist of an AM RLC entity and a logical channel. The PDCP of SRB3 on the base station device side may be placed in the secondary node.

[0130] One or more DRBs may be established and / or configured in a terminal device by an RRC message received from a base station device by a terminal device in an RRC connected state with AS security activated. A DRB may consist of one PDCP entity and one or more RLC bearers. An RLC bearer of a DRB may consist of an AM or UM RLC entity and a logical channel.

[0131] In MR-DC, a radio bearer in which a PDCP is placed in the master node may be called an MN terminated bearer. In MR-DC, a radio bearer in which a PDCP is placed in a secondary node may be called an SN terminated bearer. In MR-DC, a radio bearer in which an RLC bearer exists only in an MCG may be called an MCG bearer. In MR-DC, a radio bearer in which an RLC bearer exists only in an SCG may be called an SCG bearer. In DC, a radio bearer in which an RLC bearer exists in both an MCG and an SCG may be called a split bearer.

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

[0133] For an RLC bearer established and / or configured in a cell group configured with E-UTRA, the RLC entity established and / or configured may be an E-UTRA RLC. For an RLC bearer established and / or configured in a cell group configured with NR, the RLC entity established and / or configured may be an NR RLC. When an EN-DC is configured in the terminal device, the PDCP entity established and / or configured for an MN-terminated MCG bearer may be either an E-UTRA PDCP or an NR PDCP. When an EN-DC is configured in the terminal device, the PDCP entity established and / or configured for radio bearers of other bearer types, i.e., MN-terminated split bearers, MN-terminated SCG bearers, SN-terminated MCG bearers, SN-terminated split bearers, and SN-terminated SCG bearers, may be an NR PDCP. When an NGEN-DC, NE-DC, or NR-DC is configured in the terminal device, the PDCP entity established and / or configured for radio bearers of all bearer types may be an NR PDCP.

[0134] In NR, a DRB established and / or configured in a terminal device may be associated with one PDU session. One SDAP entity may be established and / or configured for one PDU session in the terminal device. The SDAP entity, PDCP entity, RLC entity, and logical channels established and / or configured in the terminal device may be established and / or configured by an RRC message received by the terminal device from the base station device.

[0135] 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. Also, a network configuration in which the master node is eNB102 and 5GC110 is the core network may be called E-UTRA / 5GC. Also, 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.

[0136] Next, handover in LTE and NR will be described. A handover may be a process in which a UE 122 in an RRC connected state changes its serving cell. A handover may be performed when the UE 122 receives an RRC message instructing a handover from the eNB 102 and / or the gNB 108. The RRC message instructing a handover may be a message related to reconfiguration of the RRC connection including a parameter instructing a handover (e.g., an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). 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. The above-mentioned information element named ReconfigurationWithSync may be referred to as a reconfiguration with synchronization information element, or reconfiguration with synchronization. The RRC message instructing a handover may be a message indicating movement to a cell of another RAT (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand). Alternatively, handover may be referred to as reconfiguration with sync. The conditions under which UE 122 can perform handover may include some or all of the following: AS security is activated, SRB2 is established, and at least one DRB is established.

[0137] The terminal device may execute a process in which the serving cell is not changed based on an RRC message instructing a handover. That is, the terminal device may execute a handover process in which the same cell as the current serving cell is set as the target cell.

[0138] The following describes uplink time alignment in the MAC entity of the terminal device.

[0139] The MAC entity of the terminal device may be configured by RRC with the following parameters for uplink time alignment maintenance: Time Alignment Timer per TAG: A timer used to control the time at which the MAC entity considers the uplink of the serving cells belonging to the TAG associated with this timer to be time aligned (i.e., the uplink is considered synchronized).

[0140] The MAC entity of the terminal device performs some or all of the following (A) to (D) to maintain uplink time alignment. (A) Receive a Timing Advance Command MAC Control Element, and if the parameter (N_TA) indicating the timing advance between the downlink and uplink is maintained for the indicated TAG, (1) apply the Timing Advance Command for this indicated TAG, and (2) start or restart the time alignment timer associated with this indicated TAG. (B) When a timing advance command is received in a random access response message for a serving cell belonging to a certain TAG or in an MSGB for an SpCell, some or all of the following (B-1) to (B-3) may be performed. (B-1) If the random access preamble is not selected by the MAC entity from among contention-based random access preambles, the following processes (B-1-1) to (B-1-2) are performed. (B-1-1) Apply the timing advance command for this TAG. (B-1-2) Start or restart the time consistency timer associated with this TAG. (B-2) If the condition of (B-1) is not met and the time consistency timer associated with this TAG is not running, the following steps (B-2-1) to (B-2-3) are performed. (B-2-1) Apply the timing advance command for this TAG. (B-2-2) Start the time consistency timer associated with this TAG. (B-2-3) When it is determined that contention resolution in the random access procedure was not successful, or when it is determined that contention resolution for an SI request was successful after sending HARQ feedback for a MAC PDU containing a UE contention resolution identity MAC control element, the time alignment timer associated with this TAG is stopped. (B-3) If neither the conditions (B-1) nor (B-2) are met, the received timing advance command is ignored. (C) When an Absolute Timing Advance Command is received in response to an MSGA transmission containing a C-RNTI MAC Control element, (1) apply the Timing Advance Command to the PTAG, and (2) start or restart the time alignment timer associated with the PTAG. (D) When the time alignment timer expires, some or all of the following (D-1) to (D-2) may be performed. (D-1) If the time consistency timer associated with the PTAG expires, some or all of the following processes (D-1-1) to (D-1-8) may be performed. (D-1-1) Flush all HARQ buffers of all serving cells. (D-1-2) If a PUCCH is configured in any of the serving cells, notify the RRC entity of the terminal device that the PUCCHs of all serving cells are to be released. (D-1-3) If SRS is configured in any of the serving cells, notify the RRC entity of the terminal device that the SRS of all serving cells will be released. (D-1-4) Clear all configured downlink assignments and configured uplink grants. (D-1-5) Clear all PUSCH resources for semi-persistent CSI reporting. (D-1-6) All running time consistency timers are considered to have expired. (D-1-7) Maintain the N_TA of all TAGs. (D-1-8) If the time alignment timer of the PTAG of the deactivated secondary cell group expires, do not perform beam failure detection and / or recovery in the cells of this secondary cell group. (D-2) If the condition of (D-1) is not met and the time consistency timer associated with the STAG expires, some or all of the following (D-2-1) to (D-2-6) may be performed for all serving cells belonging to this STAG. (D-2-1) Flush all HARQ buffers. (D-2-2) If a PUCCH has been set, notify the RRC entity of the terminal device that it will be released. (D-2-3) If an SRS has been configured, notify the RRC entity of the terminal device that it will be released. (D-2-4) Clear all configured downlink assignments and configured uplink grants. (D-2-5) Clear all PUSCH resources for semi-persistent CSI reporting. (D-2-6) Maintain the N_TA of this TAG.

[0141] When a MAC entity of a terminal device stops uplink transmission on an SCell as a result of the maximum difference in uplink timing between TAGs of this MAC, or the maximum difference in uplink timing between TAGs of any MAC entity of the terminal device, exceeding an upper limit, the MAC entity may consider the time alignment timer of the TAG associated with this SCell to have expired.

[0142] When a time alignment timer associated with a TAG to which a certain SCell belongs is not running, the MAC entity of the terminal device does not perform any transmissions other than the random access preamble and MSGA in this SCell. Furthermore, when a time alignment timer associated with a PTAG is not running, the MAC entity of the terminal device does not perform any transmissions other than the random access preamble and MSGA in the SpCell.

[0143] The flow of RRC messages transmitted and received between a terminal device and a base station device will be described. Fig. 4 is a diagram showing an example of a flow of a procedure for various settings in RRC according to an embodiment of the present invention. Fig. 4 shows an example of a flow when an RRC message is sent from a base station device (eNB102 and / or gNB108) to a terminal device (UE122).

[0144] In FIG. 4, the base station device creates an RRC message (step S400). The base station device may create an RRC message in order to deliver system information (SI) or paging information. The base station device may also create an RRC message in order to have a specific terminal device perform a process. The process to be performed by the specific terminal device may include, for example, security settings, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, and RRC connection release. The RRC connection reconfiguration process may include, for example, radio bearer control (establishment, modification, release, etc.), cell group control (establishment, addition, modification, release, etc.), measurement setting, handover, and security key update. The base station device may also create an RRC message in order to respond to an RRC message transmitted from the terminal device. The response to the RRC message transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, or a response to an RRC resumption request. An RRC message includes various information (parameters) for notification and configuration. These parameters may be called fields and / or information elements, and may be described using a description format called ASN.1 (Abstract Syntax Notation One).

[0145] 4, the base station device then transmits the created RRC message to the terminal device (step S402). Next, the terminal device performs processing such as setting according to the received RRC message if necessary (step S404). After performing the processing, the terminal device may transmit an RRC message as a response to the base station device (not shown).

[0146] The RRC messages may be used for other purposes, not limited to the above examples.

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

[0148] In addition, regardless of whether MR-DC is used, the RRC message for E-UTRA transmitted from eNB102 to UE122 may include an RRC message for NR, and the RRC message for NR transmitted from gNB108 to UE122 may include an RRC message for E-UTRA.

[0149] An example of parameters included in an RRC message related to RRC connection reconfiguration will be described. FIG. 7 shows an example of ASN.1 description representing fields and / or information elements related to radio bearer configuration included in the message related to RRC connection reconfiguration in NR in FIG. 4. FIG. 8 shows an example of ASN.1 description representing fields and / or information elements related to radio bearer configuration included in the message related to RRC connection reconfiguration in E-UTRA in FIG. 4. In the ASN.1 examples according to the embodiments of the present invention, including but not limited to FIGS. 7 and 8, the symbols "omitted" and "omitted" are not part of the ASN.1 notation and indicate that other information has been omitted. Note that information elements may be omitted even in places where "omitted" or "omitted" is not written. Note that the ASN.1 examples according to the embodiments of the present invention do not strictly follow the ASN.1 notation. The ASN.1 examples according to the embodiments of the present invention show examples of parameters of an RRC message according to the embodiments of the present invention, and other names and notations may be used. Note that in order to avoid complication of explanation, only examples of main information closely related to one embodiment of the present invention are shown. Note that parameters described in ASN.1 may be referred to as information elements without being distinguished as fields, information elements, etc. Furthermore, in the embodiments of the present invention, fields, information elements, etc. described in ASN.1 included in an RRC message may be referred to as information or parameters. Note that the message related to reconfiguration of the RRC connection may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

[0150] Cell activation and deactivation will now be described. In a terminal device communicating via dual connectivity, a master cell group (MCG) and a secondary cell group (SCG) are configured by the above-mentioned message related to re-establishment of the RRC connection. Each cell group may be composed of a special cell (SpCell) and zero or more other cells (secondary cells: SCell). The SpCell of the MCG is also referred to as a PCell. The SpCell of the SCG is also referred to as a PSCell. Cell deactivation does not apply to the SpCell, but may apply to the SCell.

[0151] Furthermore, cell deactivation may not be applied to PCells but may be applied to PSCells. In this case, cell deactivation may be performed differently for SpCells and SCells.

[0152] Cell activation and deactivation may be processed by a MAC entity that exists for each cell group. An SCell configured in a terminal device may be activated and / or deactivated by the following (A), (B), and / or (C). (A) Receipt of MAC CE indicating SCell activation / deactivation (B) SCell inactivity timer configured for each SCell for which PUCCH is not configured (SCell is deactivated based on the expiration of the timer) (C) SCell state (sCellState) set for each SCell by an RRC message (the SCell is activated based on the inclusion of the SCell state field in the SCell configuration)

[0153] Specifically, the MAC entity of the terminal device may perform some or all of the following processes (AD) for each SCell configured in the cell group.

[0154] (Processing AD) (1) If the RRC parameter (SCell state) is set to activated when the SCell is configured, or if a MAC CE for activating the SCell is received, the MAC entity of the UE 122 performs the process (AD-1). Otherwise, if a MAC CE for deactivating the SCell is received, or if the SCell inactivity timer expires for an SCell in the active state, the MAC entity of the UE 122 performs the process (AD-2). (2) If an uplink grant or downlink allocation is notified by the PDCCH of an active SCell, or if an uplink grant or downlink allocation for an active SCell is notified by the PDCCH of a serving cell, or if a MAC PDU is transmitted in the configured uplink grant, or if a MAC PDU is received in the configured downlink allocation, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. (3) If the SCell becomes inactive, the MAC entity of the UE 122 performs the process (AD-3).

[0155] (Process AD-1) The MAC entity of the terminal device may perform some or all of the following (1) to (3). (1) If, in NR, this SCell was in an inactive state before receiving a MAC CE activating this SCell, or if the RRC parameter (sCellState) configured for the SCell at the time of SCell configuration is set to activated, the MAC entity of UE 122 performs process (AD-1-1). (2) The MAC entity of the UE 122 starts, or restarts (if already started), the SCell inactivity timer associated with that SCell. (3) If the Active DL BWP is not a Dormant BWP, the MAC entity of the UE 122 (re)initializes a suspended Type 1 configured uplink grant associated with this SCell according to the stored configuration, if any, and the MAC entity of the UE 122 triggers a PHR.

[0156] (Process AD-1-1) The MAC entity of the terminal device may perform some or all of the following (1) to (3). (1) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is not set to a dormant BWP, the MAC entity of UE 122 performs process (AD-1-1-1). (2) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the RRC message for that SCell is configured as a dormant BWP, the MAC entity of UE 122 stops the BWP inactivity timer (bwp-InactivityTimer) for this serving cell if it is running. (3) The MAC entity of UE122 activates the downlink BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) and the uplink BWP indicated by the first active uplink BWP identifier (firstActiveUplinkBWP-Id) configured in the RRC message for that SCell.

[0157] (Process AD-1-1-1) The MAC entity of the terminal device may activate the SCell at a predetermined timing and apply (perform) normal SCell operations including some or all of the following (A) to (E). (A) Transmission of Sounding Reference Signal (SRS) in this SCell (B) Reporting of Channel State Information (CSI) for this SCell (C) Monitoring PDCCH in this SCell (D) Monitoring of PDCCH for this SCell (when scheduling for this SCell is performed in another serving cell) (E) If PUCCH is configured, PUCCH transmission on this SCell

[0158] (Process AD-2) The MAC entity of the terminal device may perform some or all of the following (A) to (D): (A) This SCell is deactivated at a predetermined timing. (B) Stop the SCell inactivity timer associated with this SCell. (C) Deactivate all Active BWPs associated with this SCell. (D) Flushes the HARQ buffer associated with this SCell.

[0159] (Process AD-3) The MAC entity of the terminal device may perform some or all of the following (A) to (D): (A) Do not transmit SRS on this SCell. (B) Do not report CSI for this SCell. (C) Do not transmit PUCCH, UL-SCH, and / or RACH on this SCell. (D) Do not monitor the PDCCH of this SCell and / or the PDCCH for this SCell.

[0160] As described above, the MAC entity performs the process (AD) to activate and deactivate the SCell.

[0161] Furthermore, as described above, when an SCell is added, the initial state of the SCell may be set by an RRC message.

[0162] Here, the SCell deactivation timer will be described. For an SCell for which a PUCCH is not configured, the value of the SCell deactivation timer (information regarding the time at which the timer is considered to have expired) may be notified by an RRC message. For example, if information indicating 40 ms as the value of the SCell deactivation timer is notified by an RRC message, the timer is considered to have expired when the notified time (here, 40 ms) has elapsed without the timer being stopped after the timer is started or restarted in the above process (AD). Furthermore, the SCell deactivation timer may be a timer named sCellDeactivationTimer.

[0163] Here, the band portion (BWP) will be explained.

[0164] A BWP may be a part or all of the band of the serving cell. A BWP may also be referred to as a carrier BWP. One or more BWPs may be configured in a terminal device. A BWP may be configured by information included in broadcast information associated with a synchronization signal detected in an initial cell search. A BWP may also be a frequency bandwidth associated with a frequency at which an initial cell search is performed. A BWP may also be configured by RRC signaling (e.g., dedicated RRC signaling). A downlink BWP (DL BWP) and an uplink BWP (UL BWP) may also be configured separately. One or more uplink BWPs may also be associated with one or more downlink BWPs. Furthermore, the correspondence between the uplink BWP and the downlink BWP may be a predetermined correspondence, or may be correspondence based on RRC signaling (e.g., Dedicated RRC signaling), or may be correspondence based on physical layer signaling (e.g., Downlink Control Information (DCI) notified on a Downlink Control Channel), or may be a combination thereof.

[0165] A BWP may be configured by a group of consecutive physical resource blocks (PRBs). Furthermore, parameters of the BWP (one or more BWPs) of each component carrier may be configured for a terminal device in a connected state. The BWP parameters for each component carrier may include some or all of the following: (A) type of cyclic prefix, (B) subcarrier spacing, (C) frequency location of the BWP (e.g., start location or center frequency location on the lower frequency side of the BWP) (for example, ARFCN may be used for the frequency location, or an offset from a specific subcarrier of the serving cell may be used. The offset may be in units of subcarriers or resource blocks. Both the ARFCN and the offset may be configured.), (D) bandwidth of the BWP (e.g., the number of PRBs), (E) resource configuration information for the control signal, and (F) center frequency location of the SS block (for example, ARFCN may be used for the frequency location, or an offset from a specific subcarrier of the serving cell may be used. The offset may be in units of subcarriers or resource blocks. Both the ARFCN and the offset may be configured.) Furthermore, the resource configuration information for the control signal may be included in the configuration of the BWP for at least some or all of the PCell and / or PSCell.

[0166] A terminal device may transmit and receive in an active BWP among one or more configured BWPs. Among one or more BWPs configured for one serving cell associated with the terminal device, at most one uplink BWP and / or at most one downlink BWP may be configured to be active BWPs at a given time. An activated downlink BWP is also referred to as an Active DL BWP. An activated uplink BWP is also referred to as an Active UL BWP.

[0167] Next, we will explain BWP deactivation. One or more BWPs may be configured in one serving cell. BWP switching in the serving cell is used to activate a deactivated BWP (also called an inactive BWP) and deactivate an activated BWP.

[0168] BWP switching is controlled by the PDCCH indicating a downlink assignment or uplink grant, the BWP inactivity timer, RRC signaling, or the MAC entity itself due to the initiation of a random access procedure. The active BWP of the serving cell is indicated by RRC or PDCCH.

[0169] Next, we will explain dormant BWP. Entering into or leaving a dormant BWP is performed by BWP switching. This control is performed by PDCCH for each SCell or for each group called a dormant SCell group. The configuration of a dormant SCell group is indicated by RRC signaling. In the current specifications, dormant BWP applies only to SCells. Note that dormant BWP does not change a certain BWP to a dormant state, but may be interpreted as one BWP configured for dormancy among one or more BWPs configured for a UE. There may be multiple BWPs configured for dormancy for a UE.

[0170] The fact that a certain BWP is a dormant BWP may be indicated by the absence of a specific parameter in the BWP configuration. For example, the fact that a BWP is a dormant BWP may be indicated by the absence of a PDCCH-Config information element, which is an information element for configuring UE-specific PDCCH parameters, included in the downlink BWP configuration. Furthermore, the fact that a BWP is a dormant BWP may be indicated by the absence of some of the parameters included in the PDCCH-Config information element, which is an information element for configuring UE-specific PDCCH parameters, included in the downlink BWP configuration. For example, the fact that a BWP is a dormant BWP may be indicated by the absence of some or all of the search space-related configuration, which is configured by the PDCCH-Config information element and defines where and / or how PDCCH candidates are searched for (searched), being configured in the BWP configuration.

[0171] In addition, in some configurations, the configuration of dormant BWP on an SpCell such as a PCell or PSCell and a PUCCH SCell on which PUCCH transmission can be performed may not be supported.

[0172] When a UE receives a PDCCH in an SpCell indicating that it will exit a dormant BWP outside a set period (active time), it activates the downlink BWP indicated by the first downlink BWP identifier previously notified by RRC signaling.

[0173] A UE that receives a PDCCH in an SpCell indicating that it will exit a dormant BWP within a certain set period (active time) activates the downlink BWP indicated by the second downlink BWP identifier previously notified by RRC signaling.

[0174] Upon receiving the PDCCH indicating entry into a dormant BWP, the UE activates the downlink BWP indicated by the third downlink BWP identifier (dormantDownlinkBWP-Id) notified in advance by RRC signaling.

[0175] The above-mentioned entry and exit of the dormant BWP is performed by BWP switching, and when a new BWP is activated, the previously active BWP is deactivated. In other words, when exiting a dormant BWP, the dormant BWP is deactivated, and when entering a dormant BWP, the dormant BWP is activated.

[0176] Here, the PDCCH indicating entry into a dormant BWP and the PDCCH indicating exit from a dormant BWP will be described.

[0177] For example, a UE configured with discontinuous reception (DRX) in the SpCell may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI format 2_6) outside the active time of DRX. The CRC of the DCI format may be scrambled with a certain RNTI (e.g., PS-RNTI). A UE configured with a dormant SCell group determines switching of the Active DL BWP based on bitmap information included in the payload of DCI format 2_6. For example, if a certain bit in the bitmap is associated with one dormant SCell group and the bit is 1, if the Active DL BWP is a dormant BWP, BWP switching may be performed to another pre-configured BWP, and if the Active DL BWP is not a dormant BWP, the UE may remain at that BWP. Alternatively, if the bit is 0, BWP switching may be performed so that the Active DL BWP becomes a dormant BWP.

[0178] The UE does not need to monitor the PDCCH for the purpose of detecting DCI format 2_6 during the DRX active time.

[0179] A UE configured with discontinuous reception (DRX) in the SpCell may monitor the PDCCH in the Active BWP of the SpCell to detect a certain DCI format (e.g., DCI formats 0_1 and 1_1) during the active time of DRX. The CRC of the DCI format may be scrambled with a certain RNTI (e.g., C-RNTI or MCS-C-RNTI). A UE configured with a dormant SCell group may determine switching of the Active DL BWP based on bitmap information included in the payload of DCI format 0_1 ​​or DCI format 1_1. For example, if a certain bit in the bitmap is associated with one dormant SCell group and the bit is 1, BWP switching may be performed to another pre-configured BWP if the Active DL BWP is a dormant BWP, and if the Active DL BWP is not a dormant BWP, the UE may remain at that BWP. Alternatively, if the bit is 0, BWP switching may be performed so that the Active DL BWP becomes a dormant BWP. Furthermore, the "different pre-set BWP" may be a BWP different from the "different pre-set BWP" used in the description of DCI format 2_6.

[0180] The UE does not need to monitor the PDCCH for the purpose of detecting DCI format 0_1 ​​and DCI format 1_1 outside the DRX active time.

[0181] Monitoring the PDCCH indicating exiting the dormant BWP may mean monitoring the PDCCH for the purpose of detecting DCI format 2_6 outside of the active time of DRX, and monitoring the PDCCH for the purpose of detecting DCI format 0_1 ​​and DCI format 1_1 during the active time of DRX.

[0182] In each activated serving cell in which a BWP is configured, the MAC entity may perform some or all of the following (A) to (H) if the BWP is activated (active BWP) and is not a dormant BWP: (A) Transmit UL-SCH with that BWP. (B) If a PRACH occasion is configured, transmit the RACH in that BWP. (C) Monitor the PDCCH with that BWP. (D) If PUCCH is configured, transmit PUCCH in that BWP. (E) Report the CSI in that BWP. (F) If SRS is configured, send SRS in that BWP. (G) Receive DL-SCH with that BWP. (H) Initialize any configured uplink grants of grant type 1 that were set up and suspended in that BWP.

[0183] In each activated serving cell in which a BWP is configured, the MAC entity may perform some or all of the following (A) to (G) if the BWP is activated (Active BWP) and if the BWP is a dormant BWP: (A) If the BWP inactivity timer of the serving cell for this BWP is running, stop it. (B) Do not monitor the PDCCH of that BWP. (C) Do not monitor the PDCCH for that BWP. (D) DL-SCH is not received in that BWP. (F) Do not send SRS with that BWP. (G) Do not transmit UL-SCH in that BWP. (H) Do not transmit RACH in that BWP. (I) Do not transmit PUCCH in that BWP. (J) Clear the configured downlink assignment and the configured uplink grant of grant type 2 associated with that SCell. (K) Suspend the configured uplink grant of grant type 1 associated with that SCell. (L) If beam failure settings are configured, detect beam failure and perform beam failure recovery if beam failure is detected.

[0184] A MAC entity may, if a BWP is deactivated, do some or all of the following: (A) Do not transmit UL-SCH in that BWP. (B) Do not transmit a RACH in that BWP. (C) Do not monitor the PDCCH in that BWP. (D) Do not transmit PUCCH in that BWP. (E) Not reporting a CSI in that BWP. (F) Do not send SRS with that BWP. (G) DL-SCH is not received on that BWP. (H) Clear the configured uplink grant of grant type 2 set in that BWP. (I) Suspend the configured uplink grant of grant type 1 of the deactivated BWP (inactive BWP).

[0185] Next, we will explain the random access procedure for a UE configured with BWP. When initiating the random access procedure in a serving cell, the MAC entity may perform some or all of the following steps (A) to (E) on the selected carrier of the serving cell. (A) If the resource (occasion) for transmitting the PRACH is not configured for the Active UL BWP, (A1) switch the Active UL BWP to the BWP indicated by the RRC parameter (initialUplinkBWP), and (A2) if the serving cell is an SpCell, switch the Active UL BWP to the BWP indicated by the RRC parameter initialDownlinkBWP. (B) If the resource (occasion) for transmitting the PRACH is configured for the Active UL BWP, if the serving cell is an SpCell and the Active DL BWP and the Active UL BWP do not have the same identifier (bwp-Id), the Active DL BWP is switched to a BWP with the same identifier as the Active UL BWP's identifier. (C) If the BWP inactivity timer associated with the Active Downlink BWP of this serving cell is running, stop this timer. (D) If the serving cell is an SCell, stop the BWP inactivity timer associated with the SpCell's Active DL BWP if this timer is running. (E) Perform the random access procedure on the Active DL BWP of the SpCell and the Active UL BWP of this serving cell.

[0186] Next, the BWP inactivity timer will be described. For each activated serving cell for which the BWP inactivity timer is set, the MAC entity performs the following process (A). The BWP inactivity timer may also be a timer named bwp-InactivityTimer. (A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP-Id) is not configured and the Active DL BWP is not the initialDownlinkBWP and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), the MAC entity performs the following processes (A-1) and (A-2). (A-1) If a PDCCH addressed to the C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received in an Active DL BWP, or if a PDCCH addressed to the C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant for an Active DL BWP is received, or if a MAC PDU is sent with a configured uplink grant or a MAC PDU is received with a configured downlink assignment, the MAC entity performs the following process (A-1-1). (A-1-1) If a random access procedure associated with this serving cell is not in progress or an ongoing random access procedure associated with this serving cell is successfully completed by receiving a PDCCH addressed to the C-RNTI, start or restart the BWP inactivity timer associated with the Active DL BWP. (A-2) If the BWP inactivity timer associated with the Active DL BWP expires, the MAC entity performs the following process (A-2-1). (A-2-1) If defaultDownlinkBWP-Id is set, BWP switching is performed to the BWP indicated by this defaultDownlinkBWP-Id, and if not, BWP switching is performed to the initialDownlinkBWP.

[0187] Furthermore, if the MAC entity receives a PDCCH for BWP switching and switches the Active DL BWP, it may perform the following process (A). (A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set and the switched-to Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched-to Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, start or restart the BWP inactivity timer associated with the Active DL BWP.

[0188] An example of an operation regarding a radio link failure (RLF) by an RRC-connected terminal device will be described.

[0189] The terminal device acquires information from the base station device in its coverage area, such as the values ​​(t310 and t313) of timers (e.g., T310 and T313) for detecting physical layer problems in the serving cell, N310 and N313 which are thresholds for the number of out-of-sync (OoS) detections, and N311 and N314 which are thresholds for the number of in-sync (IS) detections, via broadcast information or an RRC message for each user. Default values ​​may be set for the timer values ​​and count thresholds. The names of the timers may differ between EUTRA and NR.

[0190] For radio link monitoring, the physical layer processing unit of the terminal device notifies the RRC layer processing unit, which is a higher layer, of "out-of-sync" when it estimates that the radio link quality of the serving cell is worse than a specific threshold (Qout) for a specific period (e.g., TEvaluate_Qout=200 ms) based on information such as the received power of the received reference signal and / or the received power of the synchronization signal and / or the packet error rate. Furthermore, the physical layer processing unit notifies the RRC layer processing unit, which is a higher layer, of "in-sync" when it estimates that the radio link quality of the serving cell is greater than a specific threshold (Qin) for a specific period (e.g., TEvaluate_Qin=100 ms) based on information such as the received power of the received reference signal and / or the received power of the synchronization signal and / or the packet error rate. The physical layer processing unit may notify the higher layer of "out-of-sync" or "in-sync" at specific intervals (e.g., TReport_sync=10 ms) or more.

[0191] Here, for example, the threshold Qout may be defined as a level at which the downlink radio link cannot be reliably received and a hypothetical block error rate (BER) of a PDCCH transmission based on predetermined parameters is a first specific rate. Alternatively, for example, the threshold Qin may be defined as a level at which the downlink radio link quality can be significantly more reliably received than in the Qout state and a hypothetical block error rate of a PDCCH transmission based on predetermined parameters is a second specific rate. Alternatively, multiple BERs (levels of the threshold Qout and the threshold Qin) may be defined based on the frequency used, the subcarrier spacing, the type of service, and the like. Alternatively, the first specific rate and / or the second specific rate may be a default value defined in a specification. Alternatively, the first specific rate and / or the second specific rate may be a value notified or broadcast from the base station device to the terminal device.

[0192] The terminal device may perform radio link monitoring using a certain type of reference signal (e.g., a cell-specific reference signal (CRS)) in a serving cell (e.g., a PCell and / or a PSCell). The terminal device may also receive a configuration (radio link monitoring configuration: RadioLinkMonitoringConfig) indicating which reference signal is to be used for radio link monitoring in a serving cell (e.g., a PCell and / or a PSCell) from a base station device, and perform radio link monitoring using one or more configured reference signals (referred to here as RLM-RS). The terminal device may also perform radio link monitoring using other signals. When a condition for being synchronized in the serving cell (e.g., a PCell and / or a PSCell) is met, the physical layer processing unit of the terminal device may notify a higher layer that it is in synchronization.

[0193] The monitoring configuration (RadioLinkMonitoringConfig) may be set for each downlink BWP. The terminal device may perform radio link monitoring based on the monitoring configuration set for the BWP that is the Active DL BWP. Under specific conditions, the terminal device may perform radio link monitoring based on the monitoring configuration set for a default BWP or a BWP specified by the base station device.

[0194] The radio link monitoring configuration may include information indicating a monitoring purpose and identifier information indicating a reference signal. For example, the monitoring purpose may include a purpose of monitoring a radio link failure, a purpose of monitoring a beam failure, or both purposes. Furthermore, for example, the identifier information indicating the reference signal may include information indicating an identifier (SSB-Index) of a synchronization signal block (SSB) of a cell. That is, the reference signal may include a synchronization signal. Furthermore, for example, the identifier information indicating the reference signal may include information indicating an identifier linked to a channel state information reference signal (CSI-RS) configured in the terminal device.

[0195] In the primary cell, the RRC layer processing unit of the terminal device may start or restart the timer (T310) when it receives a predetermined number (N310) of consecutive out-of-sync notifications from the physical layer processing unit. The RRC layer processing unit of the terminal device may stop the timer (T310) when it receives a predetermined number (N311) of consecutive in-sync notifications. The RRC layer processing unit of the terminal device may transition to an idle state or perform an RRC connection re-establishment procedure when the timer (T310) expires. For example, the behavior of the terminal device may differ depending on the establishment status of AS security. If AS security is not established, the terminal device may transition to the RRC IDLE state, and if AS security is established, the terminal device may perform an RRC connection re-establishment procedure. The determination of whether to start or restart the timer T310 may also include a condition that none of a plurality of specific timers is running.

[0196] Furthermore, in the primary secondary cell, the RRC layer processing unit of the terminal device may start or restart a timer (T313) when it receives out-of-sync notification from the physical layer processing unit a predetermined number of times (N313 times) in a row. Furthermore, the RRC layer processing unit of the terminal device may stop the timer (T313) when it receives in-sync notification a predetermined number of times (N314 times) in a row. When the timer (T313) expires, the RRC layer processing unit of the terminal device may execute an SCG failure information procedure to notify the network of an SCG failure.

[0197] Furthermore, in an SpCell (PCell in an MCG and PSCell in an SCG), the RRC layer processing unit of the terminal device may start or restart a timer (T310) for each SpCell when it receives an out-of-sync notification from the physical layer processing unit for each SpCell a predetermined number of times (N310 times) consecutively. Furthermore, the RRC layer processing unit of the terminal device may stop a timer (T310) for each SpCell when it receives an in-sync notification for each SpCell a predetermined number of times (N311 times) consecutively. When the timer (T310) for each SpCell expires, the RRC layer processing unit of the terminal device may transition to an idle state or perform a procedure to re-establish an RRC connection if the SpCell is a PCell. Furthermore, if the SpCell is a PSCell, it may execute an SCG failure information procedure to notify the network of an SCG failure.

[0198] Also, for example, in order to detect an early physical layer problem, the RRC layer processing unit of the terminal device may start a timer (T314) when it receives an early out-of-sync notification from the physical layer processing unit a predetermined number of times (N310 times) in succession. Also, the RRC layer processing unit of the terminal device may stop the timer (T314) when it receives an in-sync notification a predetermined number of times (N311 times) in succession while T314 is running.

[0199] Furthermore, the RLM-RS may be undefined if it is not explicitly or implicitly configured by the network. If the RLM-RS is not configured by the network (e.g., a base station device), the terminal device may perform radio link monitoring using a reference signal that meets predetermined conditions.

[0200] Furthermore, the RLM-RS is a reference signal used for radio link monitoring, and multiple RLM-RSs may be configured in a terminal device. The resource of one RLM-RS may be one SS block or one CSI-RS resource (or port).

[0201] In addition, radio link monitoring using CRS may be performed in a EUTRA cell, and radio link monitoring using RLM-RS may be performed in an NR cell, but this is not limited to this.

[0202] Radio link failure detection based on radio link monitoring is described.

[0203] The terminal device determines that a radio link failure has been detected in the MCG when timer T310 expires, or when timer T312 expires, or when the MAC layer of the MCG notifies it of a random access problem while none of several specific timers are running, or when the RLC layer of the MCG notifies it that the retransmission of an SRB or DRB has reached the maximum number of retransmissions. The specific timers do not include timer T310 and timer T312.

[0204] The terminal device determines that a radio link failure has been detected in the SCG when timer T310 expires in the SCG, or when timer T312 expires in the SCG, or when a random access problem is notified from the MAC layer of the SCG when none of several specific timers are running, or when the RLC layer of the SCG notifies that the retransmission of an SRB or DRB has reached the maximum number of retransmissions. The specific timers do not include timer T310 and timer T312.

[0205] When the number of retransmissions of a random access preamble reaches a predetermined number in the MAC entity, if the random access preamble transmission is performed in an SpCell, the MAC entity of the cell group including the SpCell may notify a higher layer (here, the RRC entity) of the random access problem.

[0206] When the terminal device determines that a radio link failure has been detected in the MCG, it stores various information as radio link failure information. If AS security is not activated, it sets the release reason to "Other" and starts the process of leaving RRC_CONNECTED. If AS security is activated, it starts the RRC connection re-establishment procedure.

[0207] When timer T313 expires, or when the terminal device is notified of a random access problem by the MAC layer of the SCG, or when the terminal device is notified by the RLC layer of the SCG that the maximum number of retransmissions has been reached, the terminal device determines that a radio link failure has been detected in the SCG and starts processing to report related information to the base station device as an SCG radio link failure.

[0208] Next, we will explain the procedures for beam failure detection and recovery.

[0209] In the MAC entity, a beam failure recovery procedure may be configured by RRC for each serving cell. Beam failure is detected by counting beam failure instance notifications notified to the MAC entity from the lower layer (PHY layer). The MAC entity may perform some or all of the following processes (A), (B), and (C) for each serving cell to detect beam failure. (A) If a beam failure instance notification is received from the lower layer, start or restart the timer (beamFailureDetectionTimer) and increment the counter (BFI-COUNTER) by 1. If the value of BFI_COUNTER is equal to or greater than the configured threshold (beamFailureInstanceMaxCount), perform the process in (A-1) below. (A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, start a random access procedure in the SpCell. (B) If the beamFailureDetectionTimer for this serving cell expires, or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or reference signal settings for beam failure detection are changed by higher layers, set BFI_COUNTER to 0. (C) If the serving cell is an SpCell and the random access procedure is completed successfully, set BFI_COUNTER to 0, stop the timer (beamFailureRecoveryTimer), and consider the beam failure recovery procedure completed successfully. Otherwise, if the serving cell receives a PDCCH addressed to the C-RNTI on the SCell that indicates a new uplink grant for transmitting information for beam failure recovery of the SCell (e.g., information contained in the SCell BFR MAC CE), or if the SCell is in an inactive state, set BFI_COUNTER to 0, consider the beam failure recovery procedure completed successfully, and cancel all beam failure recoveries (BFRs) triggered for this serving cell.

[0210] The MAC entity shall perform the following process (A) if at least one Beam Failure Recovery (BFR) has been triggered by the Beam Failure Recovery procedure and has not been canceled. (A) If the UL-SCH resource can contain the BFR MAC CE of the SCell and its subheader taking into account the priority of the logical channel, include the BFR MAC CE of the SCell and its subheader. Otherwise, if the UL-SCH resource can contain the truncated BFR MAC CE of the SCell and its subheader taking into account the priority of the logical channel, include the truncated BFR MAC CE of the SCell and its subheader. Otherwise, trigger a scheduling request for SCell beam failure recovery.

[0211] The dormancy of an SCell is achieved by activating a dormant BWP in the SCell. Even when the SCell is in the dormant state, CSI measurement, automatic gain control (AGC), and beam management including beam failure recovery in the SCell may be performed.

[0212] Next, a method for adding a PSCell of an SCG and zero or more SCells to a terminal device will be described.

[0213] The addition of a PSCell of an SCG and zero or more SCells may be performed by an RRC message related to reconfiguration of an RRC connection. Figures 9 to 13 show examples of ASN.1 descriptions representing fields and / or information elements related to the addition of a PSCell of an SCG and zero or more SCells, which are included in a message related to reconfiguration of an RRC connection in NR.

[0214] To avoid complicating the explanation, the messages and / or information elements in each figure may differ from the actual message structure and / or information element structure, and some structured fields and information elements may be expanded and / or fields and information elements that are not directly related to the explanation may be omitted.

[0215] As shown in Fig. 9, an RRC reconfiguration message (RRCReconfiguration message) may be used to add a PSCell and zero or more SCells of an SCG. The RRC reconfiguration message may include some or all of the following information (A) to (E). The RRC reconfiguration message may also include other information. (A) RRC transaction identifier (rrc-TransactionIdentifier) (B) Configuration for adding, modifying, and releasing radio bearers (radioBearerConfig) (C) Secondary cell group settings (secondaryCellGroup) (D) Master cell group settings (masterCellGroup) (E) RRC configuration of secondary cell group in MR-DC (mrdc-SecondaryCellGroupConfig)

[0216] When an RRC reconfiguration message is notified to a terminal device using SRB3, the SCG configuration may be notified by the above setting (C) of the RRC Reconfiguration message. Also, when an RRC reconfiguration message is notified to a terminal device using SRB1, the SCG configuration may be notified by an RRC reconfiguration message generated by a secondary node, which is included in the above setting (E) of the RRC Reconfiguration message generated by the master node. In this case, the SCG configuration may be notified by the above setting (C) included in the RRC reconfiguration message generated by the secondary node. Also, a separate message may be used for the SCG configuration.

[0217] The configuration of the secondary cell group may be provided by a cell group configuration information element (CellGroupConfigIE). As shown in Figure 10, the cell group configuration information element may include some or all of the following information (A) to (H). The cell group configuration information element may also include other information. (A) Cell group identifier (cellGroupId) (B) Configuration for adding and / or modifying RLC bearers (rlc-BearerToAddModList) (C) Configuration for RLC bearer release (rlc-BearerToReleaseList) (D) MAC configuration for this cell group (mac-CellGroupConfig) (E) PHY configuration for this cell group (physicalCellGroupConfig) (F) SpCell configuration (spCellConfig) (G) Settings for adding and modifying SCells (sCellToAddModList) (H) Settings for releasing SCells (sCellToReleaseList)

[0218] The SpCell may be added and / or configured by the SpCell configuration in (F) above, and the SCell may be added, modified, and / or released by the configurations in (G) and (H) above. These may also be done by other messages.

[0219] The above SpCell settings may include some or all of the following information (A) to (D), as shown in Fig. 11. The SpCell settings may also include other information. (A) Index for identifying serving cells (servCellIndex) (B) Reconfiguration with Sync (C) Information on timer values ​​and constants used to determine radio link failures (rlf-TimersAndConstants) (D) SpCell device-specific parameter configuration (spCellConfigDedicated)

[0220] The above-mentioned information elements for synchronized reconfiguration may include some or all of the following information (A) to (D), as shown in Fig. 12. The synchronized reconfiguration information may also include other information. (A) SpCell cell-specific parameter settings (spCellConfigCommon) (B) New UE identifier (UE-Identity) value (newUE-Identity) (C) Value of timer T304 (t304) (D) RACH terminal device specific parameter setting (rach-ConfigDedicated)

[0221] The above-mentioned RACH UE-specific parameter configuration may include a parameter (CFRA) used for continuation-free random access. If this CFRA is not included in the configuration, the UE may perform contiguous random access in the random access procedure. The CFRA may include information on RA occasions used for contiguous random access.

[0222] The information element (ServingCellConfig IE) indicating the setting of the terminal device specific parameters of the SpCell may include some or all of the following information (A) to (C). (A) Initial downlink BWP information (initialDownlinkBWP) (B) Downlink BWP addition / modification information (downlinkBWP-ToAddModList) (C) Identifier information of the first active downlink BWP (First Active DL BWP) (firstActiveDownlinkBWP-Id)

[0223] The initial downlink BWP information is a configuration for a UE-specific initial downlink BWP (BWP identifier #0). If any optional IE is included in the initial downlink BWP information and configured, the UE may consider the BWP identifier #0 to be a BWP configured by RRC.

[0224] When identifier information of the first active downlink BWP is configured for the SpCell, the identifier of the first active downlink BWP is the identifier of the downlink BWP that is activated upon performing the RRC reconfiguration including this information. Also, when identifier information of the first active downlink BWP is configured for the SCell, the downlink BWP indicated by this identifier information is activated when the SCell is activated. Also, when identifier information of the first active downlink BWP is configured for the SpCell, the downlink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated. Also, for the uplink, the identifier information of the first active uplink BWP may be configured in the terminal device in the same information element as the identifier information of the first active downlink BWP or a different information element. The BWP identifier set in the identifier information of the first active downlink BWP and the BWP identifier set in the identifier information of the first active uplink BWP may be the same value or different values. When the identifier information of the first active uplink BWP is set for the SpCell, the uplink BWP of the SpCell indicated by this identifier information may be activated when the SCG is activated. In this case, the BWP identifier set in the identifier information of the first active downlink BWP and the BWP identifier set in the identifier information of the first active uplink BWP may be the same value.

[0225] The above-mentioned configuration of the cell-specific parameters of the SpCell may be provided by an information element (ServingCellConfigCommon IE) used to configure the cell-specific parameters of the serving cell. The information element used to configure the cell-specific parameters of the serving cell may include some or all of the following information (A) to (D), as shown in Fig. 13. Furthermore, the information element used to configure the cell-specific parameters of the serving cell may also include other information. (A) Physical cell identifier (physCellId) (B) Downlink common parameters in the cell (downlinkConfigCommon) (C) Uplink common parameters in the cell (uplinkConfigCommon) (D) Configuration of terminal device-specific parameters (including some cell-specific parameters) of SCell (sCellConfigDedicated) (E) SSB subcarrier spacing information (ssbSubcarrierSpacing)

[0226] The downlink common parameters in a cell may include downlink frequency information (frequencyInfoDL) and / or initial downlink BWP information (initialDownlinkBWP). The downlink frequency information may include information on the frequency of SSBs used in this serving cell.

[0227] The above-mentioned configuration for adding or modifying an SCell may be provided by one or more SCell configuration information elements (SCellConfigIE). The SCell configuration information element may include some or all of the following information (A) to (D), as shown in Fig. 14. The SCell configuration information element may also include other information. (A) Identifier for identifying SCell (sCellIndex) (B) Configuring cell-specific parameters for SCell (sCellConfigCommon) (C) Configuration of terminal device-specific parameters (including some cell-specific parameters) of SCell (sCellConfigDedicated) (D) Information that indicates SCell activation / inactivation (sCellState-r16)

[0228] As an example, a procedure for adding a PSCell and zero or more SCells to an SCG using the above RRC message and information elements will be described. Note that the RRC message and information elements used in the description are examples, and the names and structures when implemented are not limited to these.

[0229] The RRC entity of the terminal device that has received the RRCReconfiguration message may perform some or all of the following (A) to (F). The terminal device that has received the RRCReconfiguration message may also perform other processing. (A) If the RRCReconfiguration contains a masterCellGroup, then process (BD-1) for the master cell group based on this masterCellGroup. (B) If the RRCReconfiguration includes a secondaryCellGroup, process (BD-1) is performed on the secondary cell group based on this secondaryCellGroup. (C) If the RRCReconfiguration contains a radioBearerConfig, configure the radio bearer based on this radioBearerConfig. (D) Set the content to be included in the RRC reconfiguration complete message. (E) If the SpCell configuration (spCellConfig) of the received secondary cell group configuration includes reconfigurationWithSync, start the random access procedure in that SpCell. (F) If the SpCell configuration (spCellConfig) of the MCG or SCG includes reconfigurationWithSync and the above random access procedure is successfully completed in the NR cell group, stop timer T304 for that cell group.

[0230] (Process BD-1) The RRC entity of the terminal device may perform some or all of the following (A) to (G). (A) If CellGroupConfig includes spCellConfig including reconfigurationWithSync, the RRC entity of the terminal device performs some or all of the following (1) to (3). (1) Execute process (BD-2). (2) Resume all suspended radio bearers. (3) Resume SCG transmission for all radio bearers if suspended. (B) If the CellGroupConfig contains an rlc-BearerToReleaseList, the RLC bearer is released based on this rlc-BearerToReleaseList. (C) If CellGroupConfig contains rlc-BearerToAddModList, add and / or modify RLC bearers based on this rlc-BearerToAddModList. (D) If the CellGroupConfig contains a mac-CellGroupConfig, configure the MAC entity of this cell group based on this mac-CellGroupConfig. (E) If sCellToReleaseList is included in CellGroupConfig, release of SCell is performed based on this sCellToReleaseList. (F) If the CellGroupConfig contains an spCellConfig, configure the SpCell based on this spCellConfig. (G) If the CellGroupConfig contains sCellToAddModList, add and / or modify SCells based on this sCellToAddModList.

[0231] (Process BD-2) The RRC entity of the terminal device may perform some or all of the following (A) to (). (A) If AS security is not activated, execute the process to transition to RRC_IDLE and end the procedure. (B) Start timer T304 for the SpCell (to be configured) using the value of t304 included in reconfigurationWithSync. (C) If downlink frequency information (frequencyInfoDL) is included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync at the SSB frequency indicated in frequencyInfoDL is determined to be the target SpCell. (D) If the downlink frequency information (frequencyInfoDL) is not included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync at the SSB frequency of the original SpCell (Source SpCell) is determined to be the target SpCell. (E) Initiate downlink synchronization of the target SpCell. (F) Acquire the MIB of the target SpCell. (G) If a specific bearer (DAPS bearer) is not established, perform some or all of the following steps (1) to (4). (1) Reset the MAC entity of this cell group. (2) If an SCell not included in SCellToAddModList is configured in this cell group, this SCell is put into an inactive state. (3) The value of newUE-Identity is applied as the C-RNTI of this cell group. (4) Configure the lower layer based on the received spCellConfigCommon.

[0232] Next, timer T304 will be described. Timer T304 may exist for each cell group. Furthermore, the value (time information at which the timer expires) of a certain timer (here, timer T304) may be notified by an RRC message. For example, if information indicating a timer value of 1000 ms is notified by an RRC message, the timer may be considered to have expired if the notified time (1000 ms in this example) has elapsed since the timer was started or restarted without the timer being stopped.

[0233] Based on receiving an RRC reconfiguration message including reconfigurationWithSync, the terminal device may start timer T304 for the cell group to which the reconfigurationWithSync setting applies.

[0234] The terminal device may stop timer T304 for the cell group to which the reconfigurationWithSync setting applies based on the successful completion of random access to the target SpCell indicated by reconfigurationWithSync.

[0235] The terminal device may stop timer T304 for the SCG based on the SCG being released.

[0236] The terminal device may perform an RRC connection re-establishment procedure if the MCG timer T304 expires and if a specific bearer (DAPS bearer) is not configured.

[0237] The terminal device may notify the network of the failure of the synchronized reconfiguration by initiating an SCG failure information procedure when the SCG timer T304 expires.

[0238] The operation of the terminal device when the timer T304 of the SCG expires will now be further described.

[0239] If timer T304 of the secondary cell group expires, the RRC entity of the terminal device performs the following process (A) if MCG transmission is not suspended, and performs the following process (B) if MCG transmission is suspended. (A) If the terminal device specific preamble provided in rach-ConfigDedicated is set, release it and start the SCG failure information procedure to report the failure of the SCG synchronized reconfiguration. (B) Initiate the RRC connection re-establishment procedure.

[0240] Next, the SCG failure information procedure will be described, which may be referred to as the SCG failure information procedure.

[0241] This procedure may be used to notify the E-UTRAN or NR master node about an SCG failure experienced by the terminal device.

[0242] The RRC entity of the terminal device may initiate this procedure to report an SCG failure when MCG or SCG transmission is not suspended and any of the following conditions (A) to (D) is met: (A) SCG wireless link failure detected (B) SCG synchronization setting failure detected (C)SCG setting failure detected (D) The lower layer of the SCG notifies the failure of the integrity check for SRB3.

[0243] The RRC entity of the terminal device initiating this procedure performs some or all of the following (A) to (E). (A) Suspend SCG transmission for all SRBs and DRBs. (B) Reset the SCG MAC. (C) If timer T304 in this SCG is running, stop it. (D) If conditional reconfiguration for PSCell change is set, stop this evaluation. (E) Set the content to be included in the SCG Failure Information (SCGFailureInformation) message and submit this message to the lower layer for transmission.

[0244] The lower layer of the RRC of the terminal device may transmit the SCG failure information (SCGFailureInformation) message to the base station device.

[0245] Measurement will now be described. A base station apparatus transmits a measurement configuration information element (also referred to as measurement configuration) to a terminal apparatus using (including in) an RRC reconfiguration message of RRC signaling (radio resource control signal). The terminal apparatus performs measurements, event evaluation, and measurement reports for the serving cell and neighboring cells (including listed cells and / or detected cells) according to the information included in the notified measurement configuration. A listed cell is a cell listed in a measurement object (a cell notified to the terminal apparatus by the base station apparatus as a neighboring cell list). A detected cell is a cell detected by the terminal apparatus at the frequency and subcarrier spacing indicated by the measurement object but not listed in the measurement object (a cell detected by the terminal apparatus itself that is not notified as a neighboring cell list).

[0246] For example, (A) a first RRC reconfiguration message may include measurement configuration for the MCG, and a field indicating information about the SCG of the MR-DC included in the first RRC reconfiguration message may include an encapsulated RRC reconfiguration message for the SCG (second RRC reconfiguration message), and this second RRC reconfiguration message may include measurement configuration for the SCG. In this case, the first RRC reconfiguration message notifying the measurement configuration of the MCG and the first RRC reconfiguration message notifying the measurement configuration of the SCG may be the same RRC reconfiguration message or may be different RRC reconfiguration messages notified at different times. Alternatively, (B) the measurement configuration of the MCG may be notified by SRB1, and the measurement configuration of the SCG may be notified by SRB3.

[0247] The terminal device may have a variable VarMeasConfig for holding the notified measurement configuration. The terminal device may also have a variable VarMeasReportList for holding measurement information that matches the reporting conditions. The terminal device may be notified of the measurement configuration for each cell group. For each cell group, the terminal device may have a variable VarMeasConfig for holding each measurement configuration set for each cell group (or for a cell group, or linked to a cell group) and a variable VarMeasReportList for holding measurement information that matches the reporting conditions for each measurement configuration.

[0248] Measurements include three types: intra-frequency measurements, inter-frequency measurements, and inter-RAT measurements. Intra-frequency measurements are measurements on the downlink frequency of the serving cell with the same subcarrier spacing as the serving cell. Inter-frequency measurements are measurements on a frequency different from the downlink frequency of the serving cell, or on the same frequency with a different subcarrier spacing. Inter-RAT measurements are measurements on a radio technology (e.g., UTRA, GERAN, CDMA2000, E-UTRA, etc.) different from the radio technology (e.g., NR) of the serving cell.

[0249] The measurement configuration may include some or all of the following: a list of added and / or modified measurement identifiers (measId), a list of deleted measurement identifiers, a list of added and / or modified measurement objects (Measurement objects), a list of deleted measurement objects, a list of added and / or modified reporting configurations, a list of deleted reporting configurations, a quantity configuration (quantityConfig), a measurement gap configuration (measGapConfig), and a serving cell quality threshold (s-Measure) configuration.

[0250] <Quantity configuration (quantityConfig)> The quantity Config specifies the L3 filtering coefficient when the measurement objects are NR and / or E-UTRA. The L3 filtering coefficient specifies the ratio (proportion) between the latest measurement result and the past filtered measurement result. The filtering result is used for event evaluation in the terminal device.

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

[0252] <Measurement Identifier (measId)> Here, the measurement identifier (measId) is used to associate (or associate or link) measurement objects with reporting configurations; specifically, it links a measurement object identifier (measObjectId) with a reporting configuration identifier (reportConfigId). One measurement object identifier (measObjectId) and one reporting configuration identifier (reportConfigId) are associated with one measurement identifier (measId). Measurement configurations can be added, modified, or deleted in relation to the relationship between measurement identifier (measId), measurement objects, and reporting configurations.

[0253] The measurement identifier deletion list included in the measurement configuration includes a list of measurement identifiers, and the terminal device performs the following processes (A) to (C) for each measurement identifier included in the measurement identifier deletion list: (A) Delete the entry for this measurement identifier from the variable VarMeasConfig of the cell group that is the target of the measurement configuration. (B) If included, delete the measurement report entry for this measurement identifier from the variable VarMeasReportList of the cell group that is the target of the measurement configuration. (C) Stop the timer used for periodic reporting for this measurement identifier or timer T321 if the timer is started, and reset the related information for this measurement identifier. Note that timer T321 is a timer that starts when a measurement configuration including a reporting configuration intended to measure a cell global identifier is received. Furthermore, this timer is stopped when the deletion list of the reporting configuration, which will be described later, includes an identifier for a reporting configuration intended to measure a cell global identifier, or when the detected cell is not broadcasting SIB1.

[0254] The measurement identifier addition and / or modification list included in the measurement configuration includes a list of measurement identifiers, and the terminal device performs the following processes (A) to (C) for each measurement identifier included in the measurement identifier addition and / or modification list: (A) if an entry for a measurement identifier matching this measurement identifier exists in the list of measurement identifiers included in the variable VarMeasConfig of the cell group that is the target of the measurement configuration, replace the entry with the value received for this measId for this measurement identifier. Otherwise, add a new entry for this measurement identifier to the variable VarMeasConfig of the cell group that is the target of the measurement configuration. (B) if included, delete the measurement report entry for this measurement identifier from the variable VarMeasReportList of the cell group that is the target of the measurement configuration. (C) if the timer or timer T321 used for periodic reporting for this measurement identifier is started, stop it and reset the related information for this measurement identifier.

[0255] The measurement object removal list (measObjectToRemoveList) included in the measurement configuration is a field containing information to delete a specified measurement object identifier (measObjectId) and measurement objects (Measurement objects) corresponding to the specified measurement object identifier (measObjectId). At this time, all measurement identifiers (measId) of the cell group that is the target of the measurement configuration and associated with the specified measurement object identifier (measObjectId) may be deleted. This field allows multiple measurement object identifiers (measObjectId) to be specified at the same time.

[0256] The measurement object addition and / or modification list (measObjectToAddModList) included in the measurement setting is a field that contains information to modify the measurement object (Measurement objects) specified by the measurement object identifier (measObjectId) or to add the measurement object (Measurement objects) specified by the measurement object identifier (measObjectId). This field can specify multiple measurement object identifiers (measObjectId) at the same time.

[0257] The reporting configuration deletion list (reportConfigToRemoveList) included in the measurement configuration is a field containing information to delete the specified reporting configuration identifier (reportConfigId) and the reporting configurations corresponding to the specified reporting configuration identifier (reportConfigId). At this time, all measurement identifiers (measId) associated with the specified reporting configuration identifier (reportConfigId) are deleted. This command can specify multiple reporting configuration identifiers (reportConfigId) at the same time.

[0258] The report configuration addition and / or modification list (reportConfigToAddModList) is a field that contains information to modify or add reporting configurations specified by a reporting configuration identifier (reportConfigId). This field can specify multiple reporting configuration identifiers (reportConfigId) at the same time.

[0259] The measurement identifier deletion list (measIdToRemoveList) is a command to delete the specified measurement identifier (measId). At this time, the measurement object identifier (measObjectId) and report configuration identifier (reportConfigId) associated with the specified measurement identifier (measId) are not deleted and are maintained. This command can specify multiple measurement identifiers (measId) at the same time.

[0260] The measurement identifier add and / or modify list (measIdToAddModifyList) is a command that modifies the specified measurement identifier (measId) to correspond to the specified measurement object identifier (measObjectId) and the specified report configuration identifier (reportConfigId), or associates the specified measurement object identifier (measObjectId) and the specified report configuration identifier (reportConfigId) with the specified measurement identifier (measId), and adds the specified measurement identifier (measId). This command can specify multiple measurement identifiers (measId) at the same time.

[0261] <Measurement objects> Measurement objects are set (specified) for each RAT and frequency. Note that, when the RAT is NR, the measurement objects may be set for each frequency and subcarrier spacing. Furthermore, reporting configurations may be specified for NR and for RATs other than NR.

[0262] The measurement objects (Measurement objects) may include a measurement object NR (measObjectNR) where the measurement object associated with the measurement object identifier (measObjectId) is NR, and a measurement object EUTRA (measObjectEUTRA) where the measurement object is E-UTRA. The measurement objects may also include some or all of a measurement object UTRA (measObjectUTRA) where the measurement object is UTRA, a measurement object GERAN (measObjectGERAN) where the measurement object is GERAN, a measurement object CDMA2000 (measObjectCDMA2000) where the measurement object is CDMA2000, and a measurement object WLAN (measObjectWLAN) where the measurement object is WLAN.

[0263] The measurement object identifier (measObjectId) is an identifier used to identify the configuration of measurement objects. As described above, the configuration of measurement objects is specified for each radio access technology (RAT) and frequency, and further for each subcarrier spacing in NR. Measurement objects may be specified separately for E-UTRA, UTRA, GERAN, and CDMA2000. The measurement object for NR, the measurement object NR (measObjectNR), specifies information applied to the NR serving cell and neighboring cells. Note that which measurement object identifier corresponds to which measurement object corresponds to the serving cell may be indicated by an information element (e.g., serving cell configuration) included in an RRC message including the measurement configuration and / or an RRC message not including the measurement configuration.

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

[0265] The information on the list of cells to be measured includes information on cells to be the target of event evaluation and measurement reporting, such as physical cell IDs and cell-specific offsets (cellIndividualOffsets, which indicate measurement offset values ​​to be applied to neighboring cells).

[0266] <Reporting configurations> The reporting configurations include a reporting configuration NR (reportConfigNR) associated with a reporting configuration identifier (reportConfigId).

[0267] The reporting configuration identifier (reportConfigId) is an identifier used to identify measurement reporting configurations. As mentioned above, measurement reporting configurations may have specifications for NR and for RATs other than NR (some or all of UTRA, GERAN, CDMA2000, E-UTRA). The reporting configuration NR (reportConfigNR), which is a reporting configuration for NR, specifies the triggering criteria for events used to report measurements in NR.

[0268] In addition, the report configuration NR (reportConfigNR) may include some or all of the following: event identifier (eventId), trigger quantity (triggerQuantity), hysteresis (hysteresis), trigger time (timeToTrigger), report quantity (reportQuantity), maximum number of report cells (maxReportCells), report interval (reportInterval), and number of reports (reportAmount).

[0269] Next, the report configuration NR (reportConfigNR) will be explained. The event identifier (eventId) is used to select criteria for event triggered reporting. Here, event triggered reporting is a method of reporting measurements when the event trigger conditions are met. In addition to this, there is also event triggered periodic reporting, which reports measurements a certain number of times at regular intervals when the event trigger conditions are met.

[0270] When an event trigger condition specified by an event identifier (eventId) is satisfied, the terminal device sends a measurement report to the base station device. The trigger quantity (triggerQuantity) is a quantity used to evaluate the event trigger condition. That is, reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified. That is, the terminal device measures the downlink synchronization signal using the quantity specified by this trigger quantity (triggerQuantity) and determines whether the event trigger condition specified by the event identifier (eventId) is satisfied. The hysteresis (hysteresis) is a parameter used in the event trigger condition. The trigger time (timeToTrigger) indicates the period during which the event trigger condition should be satisfied. The report quantity (reportQuantity) indicates the quantity to be reported in the measurement report. Here, the quantity specified by the trigger quantity (triggerQuantity), or reference signal received power (RSRP) or reference signal received quality (RSRQ) is specified. The maximum number of report cells (maxReportCells) indicates the maximum number of cells to be included in a measurement report. The report interval (reportInterval) is used for periodic reporting or event-triggered periodic reporting, and periodic reporting is performed at the interval indicated by the report interval (reportInterval). The report amount (reportAmount) specifies the number of times periodic reporting is performed, if necessary.

[0271] In addition, the threshold parameters and offset parameters (a1_Threshold, a2_Threshold, a3_Offset, a4_Threshold, a5_Threshold1, a5_Threshold2, a6_Offset, c1_Threshold, c2_Offset) used in the event trigger conditions may be notified to the terminal device together with the event identifier (eventId) in the reporting configuration NR (reportConfigNR).

[0272] <Event trigger conditions> Multiple event trigger conditions for measurement reports are defined, each with its own joining and leaving conditions. That is, a terminal device that satisfies the joining conditions for an event specified by the base station device transmits a measurement report to the base station device. Also, a terminal device that satisfies the leaving conditions for an event specified by the base station device transmits a measurement report to the base station device if the base station device has configured the terminal device to trigger a report when the leaving conditions are satisfied (if reportOnLeave is included in the reporting configuration).

[0273] In addition, the reporting configuration InterRAT (reportConfigInterRAT), which is a reporting configuration for RATs other than NR, defines multiple triggering criteria for events used to report measurements in RATs other than NR. For example, if the measurement result of a neighboring cell (other RAT) is better than a threshold b1_Threshold set for each RAT after applying each parameter, event B1 occurs. Also, if the measurement result of the PCell is worse than a threshold b2_Threshold1 after applying each parameter and the measurement result of a neighboring cell (other RAT) is better than a threshold b2_Threshold2 set for each RAT after applying each parameter, event B2 occurs.

[0274] Note that the base station device may or may not notify the serving cell quality threshold (s-Measure). When the base station device configures the serving cell quality threshold (s-Measure) in the terminal device and the quality (RSRP value) after Layer 3 filtering of the PCell, which is the serving cell, is lower than the serving cell quality threshold (s-Measure), the terminal device measures neighboring cells of the frequency and RAT specified by the measurement target. On the other hand, when the base station device does not configure the serving cell quality threshold (s-Measure) in the terminal device, the terminal device measures neighboring cells regardless of the quality (RSRP value) of the serving cell.

[0275] <Measurement Resultについて> The terminal device may start the measurement reporting procedure when an event trigger condition is met, when the first measurement result for periodic reporting becomes available, or when the periodic reporting timer or timer T321 expires. The purpose of the measurement reporting procedure is to transfer a measurement report from the terminal device to the network. The measurement report contains a measurement result. A measurement result is set for each measurement identifier for which the measurement reporting procedure is triggered.

[0276] The measurement results may include a measurement identifier (measId), a list of serving measurement object measurement results (measResultServingMO), and neighbor cell measurement results (measResultNeighCellNR). The neighbor cell measurement results may include either a list of NR measurement results or a list of E-UTRA measurement results. The NR measurement results and E-UTRA measurement results include some or all of the following information: physical cell identifier, cell measurement results, and cell global identifier. The serving measurement object measurement results (measResultServingMO) are measurement results of measurement objects associated with the serving cell, and may include some or all of the following: the serving cell identifier, the serving cell measurement results, and the best neighbor cell measurement results.

[0277] In the measurement report procedure, the measurement results are set for each measurement identifier that triggered the measurement report procedure, and if the UE is configured with EN-DC, if SRB3 is configured, it submits a measurement report message including the measurement results to lower layers for transmission via SRB3 and terminates the procedure. If SRB3 is not configured, it encapsulates (embeds) the measurement report message in an E-UTRA RRC message and submits it to lower layers via E-UTRA MCG. If the UE is configured with NR-DC and the measurement configuration that triggered this measurement report is associated with SCG, it submits a measurement report message including the measurement results to lower layers for transmission via SRB3 and terminates the procedure. If SRB3 is not configured, it encapsulates (embeds) the measurement report message in an NR MCG RRC message and submits it to lower layers via NR MCG.

[0278] Conditional handover (CHO) will be described. The conditional handover may be the conditional handover described in Non-Patent Document 1 or the like. The terminal device may configure the conditional handover by receiving an RRC message including conditional handover configuration parameters from a base station device. The conditional handover configuration parameters may include configuration parameters for a target candidate SpCell and execution condition parameters for applying the configuration to the target candidate SpCell and executing a handover. The conditional handover may be a handover in which a handover procedure is executed by the terminal device when one or more execution conditions are satisfied. Note that the conditional handover may also be referred to as conditional reconfiguration. The conditional handover may also be referred to as handover. Note that the RRC message including the conditional handover configuration information element may be a message related to reconfiguration of an RRC connection or an RRC reconfiguration message.

[0279] Fig. 18 is an example of an ASN.1 description representing fields and / or information elements related to the configuration of a conditional handover. In Fig. 18, the information element represented by ConditionalReconfiguration may be an information element indicating the configuration of a target candidate SpCell in a conditional handover and a conditional handover execution condition. The information element represented by ConditionalReconfiguration may be rephrased as a conditional handover configuration information element or a conditional handover configuration. The conditional handover configuration information element may also be used for a conditional PSCell change. In other words, when ConditionalReconfiguration is configured for an SCG, the information element represented by ConditionalReconfiguration may be rephrased as a conditional PSCell change configuration information element or a conditional PSCell change configuration.

[0280] 18, a field represented by "attemptCondReconfig" included in the conditional handover configuration information element may be configured to indicate that, if this field exists, a conditional reset is to be performed on a candidate SpCell when the cell initially selected after a handover failure is one of the candidate SpCells included in the conditional handover configuration information element. The field represented by "attemptCondReconfig" may be referred to as an "attempt conditional reset field" or "attempt conditional reset."

[0281] 18, the information element represented by CondReconfigToRemoveList included in the conditional handover configuration information element and the conditional PSCell change configuration information element may be a list of candidate SpCells to be removed. The information element represented by CondReconfigToRemoveList may also be referred to as the conditional reconfiguration list information element to be deleted, or the conditional reconfiguration list to be deleted. The conditional reconfiguration list information element to be deleted may be a list of information elements represented by CondReconfigId, which will be described later.

[0282] 18, the information element represented by CondReconfigToAddModList included in the conditional handover configuration information element and the conditional PSCell modification configuration information element may be a list of candidate SpCell configurations to be added or modified. The information element represented by CondReconfigToAddModList may be rephrased as a conditional reconfiguration list information element or a conditional reconfiguration list. Furthermore, the conditional reconfiguration list information element may be a list of information elements represented by CondReconfigToAddMod. The information element represented by CondReconfigToAddMod may be rephrased as a conditional reconfiguration information element or a conditional reconfiguration.

[0283] 18, a field represented by condReconfigId included in the conditional reconfiguration information element may be an identifier for identifying the configuration of a conditional handover or a conditional PSCell change. The field represented by condReconfigId may be referred to as a conditional reconfiguration identifier field or a conditional reconfiguration identifier.

[0284] 18, a field represented by condExecutionCond included in the conditional reconfiguration information element and the conditional PSCell modification configuration information element may be an execution condition that must be satisfied to trigger the execution of conditional reconfiguration. The field represented by condExecutionCond may be referred to as a conditional reconfiguration execution condition field or a conditional reconfiguration execution condition. The reconfiguration execution condition field may include one or more identifiers (measurement identifiers) that identify measurement configurations. In other words, the execution of conditional reconfiguration may be triggered when a reporting condition for a measurement specified by a measurement identifier included in the reconfiguration execution condition field is satisfied.

[0285] In FIG. 18, the information element represented by "condRRCReconfig" included in the conditional reconfiguration information element may be an RRC reconfiguration message that is applied when the conditional reconfiguration execution condition indicated in the above-mentioned conditional reconfiguration execution condition field is satisfied. That is, the information element represented by "condRRCReconfig" may include some or all of the information elements and / or fields included in the RRC reconfiguration message. The information element represented by "condRRCReconfig" may be referred to as a conditional reconfiguration information element or conditional reconfiguration. Furthermore, the inclusion of a conditional reconfiguration information element in the information elements and / or fields of the RRC reconfiguration message included in the conditional reconfiguration information element may be prohibited.

[0286] The above-mentioned conditional reconfiguration information element may include, for example, some or all of the following settings (A) to (F): (A) Cell group configuration (which may be an information element represented by the name CellGroupConfig). (B) Information indicating whether or not the configuration is full (may be a field represented by fullConfig). (C) A NAS layer message (which may be an information element represented by the name DedicatedNAS-message). (D) Key update settings (which may be an information element represented by the name MasterKeyUpdate). (E) Measurement configuration (which may be an information element represented by the name MeasConfig). (F) Radio bearer setup.

[0287] Furthermore, the above-mentioned cell group setting information may include, for example, some or all of the following settings (1) to (6). (1) A cell group identifier (which may be an information element represented by the name CellGroupId). (2) RLC bearer configuration (which may be an information element represented by the name RLC-BearerConfig). (3) MAC layer configuration of the cell group (which may be an information element represented by the name MAC-CellGroupConfig). (4) Physical (PHY) layer configuration of the cell group (may be an information element represented by the name PhysicalCellGroupConfig). (5) SpCell configuration (which may be an information element represented by the name SpCellConfig). (6) SCell information (which may be an information element represented by the name SCellConfig).

[0288] The SpCell configuration in (5) may include a synchronized reconfiguration information element. The synchronized reconfiguration information element included in the SpCell configuration in (5) may include a physical cell identifier (which may be an information element represented by the name PhysCellId) of the target candidate SpCell.

[0289] Furthermore, the above-mentioned radio bearer configuration may include some or all of the following configurations (1) to (3). (1)SRB settings (2) DRB settings (3) Security configuration (which may be an information element represented by the name SecurityConfig).

[0290] In addition, the security settings in (3) may include information regarding the integrity protection algorithm and encryption algorithm for the SRB and / or DRB (which may be an information element named SecurityAlgorithmConfig), and / or information indicating whether to use an MCG key or an SCG key (which may be a field named keyToUse).

[0291] The above-mentioned candidate SpCell may be referred to as a target candidate SpCell. Also, the SpCell may be referred to as a Cell, a PCell, or a PSCell.

[0292] An example of processing by a terminal device in an embodiment of the present invention will be described using Fig. 19. Here, a PSCell change procedure will be described, but this procedure may also be applied to a PCell change (i.e., handover).

[0293] The receiver 500 of the UE 122 may receive an RRC message from the base station device. The processor 502 of the UE 122 may configure the UE 122 in accordance with the RRC message received from the base station device (step S1900).

[0294] An example of the initiation of the PSCell change procedure in step S1902 will be described. In step S1900, for example, if the RRC message received from the base station device includes a first synchronization-based reconfiguration information element and the first synchronization-based reconfiguration information element is not an information element included in the conditional PSCell change configuration information element, the processing unit 502 of the UE 122 may apply the first synchronization-based reconfiguration information element and start the PSCell change procedure for the first SpCell in accordance with the first synchronization-based reconfiguration information element. The above-mentioned case where the RRC message received from the base station device includes the first synchronization-based reconfiguration information element and the first synchronization-based reconfiguration information element is not an information element included in the conditional PSCell change configuration information element may be a case of a non-conditional PSCell change or a normal PSCell change. Note that if the RRC message received from the base station device does not include the first synchronization-based reconfiguration information element, the PSCell change procedure for the first SpCell does not need to be started. (Step S1902)

[0295] Furthermore, in step S1900, for example, if the RRC message received from the base station device includes a conditional PSCell modification configuration information element, the processing unit 502 of the UE 122 may configure the UE 122 in accordance with the above-mentioned conditional PSCell modification configuration information element. Here, the above-mentioned PSCell modification configuration information element may include a conditional reconfiguration list information element. Furthermore, the above-mentioned conditional reconfiguration list information element may include first to Nth conditional reconfiguration information elements (where N is a positive integer). At a certain point in time, if the mth conditional reconfiguration execution condition included in the mth conditional reconfiguration information element configured in the UE 122 is satisfied, the processing unit 502 of the UE 122 may perform processing including the following (A). Here, the above-mentioned m may be an integer greater than or equal to 1 and less than or equal to N. (A) The mth conditional reconfiguration information element included in the above-mentioned mth conditional reconfiguration information element may be applied, and a PSCell change procedure may be initiated for the mth SpCell in accordance with the mth synchronized reconfiguration information element included in the above-mentioned mth conditional reconfiguration information element.

[0296] The PSCell change for the m-th SpCell may be referred to as the conditional PSCell change for the m-th SpCell. If the m-th conditional reconfiguration execution condition is not satisfied, the processing unit 502 of the UE 122 does not need to perform the process (A) (step S1902).

[0297] Next, an example of activation and deactivation of SCG will be described.

[0298] In LTE and / or NR, a state in which the SCG is deactivated (SCG deactivated state) may be included as part of the RRC_CONNECTED state.

[0299] In LTE and / or NR, a state in which an SCG is deactivated (SCG deactivated state) may be a state in which a terminal device performs some or all of the following (A) to (J) in the SpCell (PSCell) of that SCG and / or in all cells of that SCG. (A) Do not transmit SRS in that cell. (B) Not reporting CSI for that cell and / or not reporting CSI in that cell. (C) Do not transmit PUCCH, UL-SCH, and / or RACH in that cell. (D) Do not monitor the PDCCH of that cell and / or the PDCCH for that cell. (E) Not monitoring the PDCCH of that cell and / or the PDCCH for that cell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission in that cell. (F) Do not perform automatic gain control (AGC) on that cell. (G) No beam management, including beam failure recovery, is performed in that cell. (H) Radio Link Monitoring (RLM) is not performed in that cell. (I) In that cell, the BWP that has been set as a dormant BWP is called the active BWP. (J) The C-RNTI is not monitored on the PDCCH in the activated dormant BWP of the cell.

[0300] Furthermore, when an SCG is in an inactive state, different processes may be performed while the time alignment timer is running in the SCG and while the time alignment timer is stopped (including when it has expired). For example, while the SCG is in an inactive state and the time alignment timer is running, CSI reporting may be performed in the SpCell of the SCG, and while the SCG is in an inactive state and the time alignment timer is stopped, CSI reporting may not be performed in the SpCell of the SCG. Also, for example, while the SCG is in an inactive state and the time alignment timer is running, RLM may be performed in the SpCell of the SCG, and while the SCG is in an inactive state and the time alignment timer is stopped, RLM may not be performed in the SpCell of the SCG. When the terminal device is in an SCG inactive state, the terminal device may not perform processes involving the initiation of a random access procedure. Furthermore, the timer may be another timer that starts, for example, when SCG deactivation is instructed or when the SCG is deactivated. The timer may be a timer managed by a MAC entity.

[0301] In addition, becoming an SCG inactive state may be referred to as entering an inactive SCG. In addition, the SCG inactive state may be a state in which the Active BWPs of all cells of the SCG are dormant BWPs. In addition, the above-mentioned SCG inactive state may be a state in which the SCG transitions from an activated state (SCG active state) described later when an RRC entity instructs entry into an inactive SCG.

[0302] In LTE and / or NR, the state in which the SCG is activated (SCG active state) may be included as part of the RRC_CONNECTED state.

[0303] In LTE and / or NR, an activated state of an SCG (SCG activated state) may be a state in which a terminal device performs some or all of the following (A) to (J) in the SpCell (PSCell) of that SCG and / or in any cell of that SCG. (A) Transmit SRS in that cell. (B) Report the CSI for that cell. (C) Transmit PUCCH, UL-SCH, and / or RACH in that cell. (D) Monitor the PDCCH of that cell and / or the PDCCH for that cell. (E) Monitor the PDCCH of that cell and / or the PDCCH for that cell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission in that cell. (F) Automatic gain control (AGC) is performed on that cell. (G) The cell performs beam management including beam failure recovery. (H) Radio Link Monitoring (RLM) is performed in that cell. (I) In that cell, a BWP that has been set as a dormant BWP is not set as an activated BWP (Active BWP). (J) Monitor the C-RNTI on the PDCCH in the activated BWP of that cell.

[0304] Furthermore, becoming an SCG active state may be referred to as entering an activated SCG. Furthermore, the SCG active state may be a state in which the Active BWPs of the SpCell and / or one or more SCells of the SCG are not dormant BWPs. Furthermore, the above-mentioned SCG inactive state may be a state to which the SCG transitions from an inactive state (SCG inactive state) when an RRC entity instructs the SCG to leave the inactive SCG.

[0305] In LTE and / or NR, a terminal device may transition an SCG to an inactive state (in other words, may deactivate an SCG) based on receiving some or all of the following (A) to (B). Note that the messages and control elements (A) to (C) below may be notified to the terminal device from a cell group other than the SCG. Furthermore, each piece of information may be notified to the terminal device via an RRC message, a MAC control element, or a physical control channel. (A) Information instructing inactivation of SCG (B) Information instructing SpCell inactivation (C) Information instructing the SpCell to switch its Active BWP to a specific BWP

[0306] Furthermore, the terminal device may transition the SCG from the active state to the inactive state based on a timer related to the deactivation of the SCG. Furthermore, the terminal device may transition the SCG from the active state to the inactive state based on a timer related to the deactivation of the PSCell.

[0307] In addition, the terminal device may transition the SCG from an inactive state to an active state when initiating a random access procedure due to a scheduling request (in other words, initiated by the MAC entity itself). The MAC entity of the terminal device may also obtain an instruction to activate the SCG, an instruction to resume from an inactive SCG, an instruction to resume from a dormant state of the SpCell, and / or other information from the RRC entity of the terminal device.

[0308] In LTE and / or NR, a terminal device may transition an SCG from an inactive state to an active state (in other words, may activate an SCG) based on receiving some or all of the following (A) to (D). Note that the messages and control elements (A) to (D) below may be notified to the terminal device from a cell group other than the SCG. Furthermore, each piece of information may be notified to the terminal device via an RRC message, a MAC control element, or a physical control channel. (A) Information that directs SCG activation (B) Information that directs the return of SCG from its inactive state (Resume) (C) Information that directs SpCell activation (D) Information that directs the return of SpCell from its inactivated state

[0309] Furthermore, the terminal device may transition the SCG from the inactive state to the active state based on a timer related to the deactivation of the SCG. Furthermore, the terminal device may transition the SCG from the inactive state to the active state based on a timer related to the deactivation of the PSCell.

[0310] In addition, the terminal device may transition the SCG from the inactive state to the active state when initiating a random access procedure due to a scheduling request triggered to transmit a MAC PDU including a MAC SDU. In addition, the terminal device may transition the SCG from the inactive state to the active state when initiating a random access procedure.

[0311] In addition, the terminal device may transition the SCG from an inactive state to an active state when initiating a random access procedure due to a scheduling request (in other words, initiated by the MAC entity itself). The MAC entity of the terminal device may also obtain an instruction to activate the SCG, an instruction to resume from an inactive SCG, an instruction to resume from a dormant state of the SpCell, and / or other information from the RRC entity of the terminal device.

[0312] Inactivation of an SCG may also be referred to as entering a dormant SCG. Alternatively, inactivation of an SCG may be activation of the dormant BWP of the SpCells in the cell group. Inactivation of an SCG may also be referred to as SCG dormancy or SCG suspension.

[0313] When an SCG is in a deactivated state and at least the time alignment timer is stopped, all uplink transmissions in the SCG may be stopped. In this case, information about the SCG may be transmitted in another cell group (e.g., MCG), or information about the SCG may be transmitted in the SCG that has left the deactivated state (activated SCG).

[0314] There may be cases where a random access procedure in an SpCell (PSCell) is initiated in a deactivated SCG by the MAC entity triggering a scheduling request to transmit a MAC PDU containing a MAC CE, or directly by the MAC entity, where the MAC PDU may not contain a MAC SDU.

[0315] On the other hand, a random access procedure in the SpCell (PSCell) may be initiated in a deactivated SCG by triggering a scheduling request to transmit a MAC PDU containing data (MAC SDU) from a higher layer, such as user data or an RRC message.

[0316] The return of an SCG from an inactive state (activation of an SCG) may be referred to as leaving a dormant SCG. The return of an SCG from an inactive state may also be a BWP switch from a dormant BWP to another (non-dormant) BWP in the SpCell of the cell group.

[0317] The restoration of SCG from an inactivated state may also be referred to as SCG activation.

[0318] A terminal device that deactivates an SCG may perform some or all of the following processes (A) to (I) in the SCG. (A) All SCells are in an inactive state. (B) All SCell inactivity timers associated with the active SCell are considered to have expired. (C) All SCell inactivity timers associated with the dormant SCell are considered to have expired. (D) Do not start or restart the SCell inactivity timers associated with all SCells. (E) Ignore the MAC CE that activates the SCell. For example, in the process (AD), if a MAC CE that activates the SCell is received and an instruction to deactivate the SCG has not been issued (or the SCG is not in a deactivated state), perform process (AD-1). (F) Executing the process (AD-2). For example, when inactivation of SCG is instructed in the process (AD) (or when SCG is inactivated), the process (AD-2) is executed. (G) Switch the Active BWP of a specific SCell to a Dormant BWP (i.e., put this SCell into a dormant state). The specific SCell may be an SCell instructed by the base station device, or may be an SCell for which a Dormant BWP is configured. (H) The Active BWP of the SpCell is switched to a specific BWP. The specific BWP may be a BWP designated by the base station device, a BWP set as the First Active BWP, or an Initial BWP. The BWP to be switched may be only a DL BWP, or both a DL BWP and an UL BWP. (I) Deactivate all BWPs in the SpCell. That is, when an SCell is deactivated, the same process as deactivating all BWPs in this SCell is performed on the SpCell.

[0319] A terminal device that restores an SCG from an inactivated state may perform some or all of the following processes (A) to (F) in the SCG. (A) To activate all SCells, process (AD-1) is executed. (B) All SCells remain in the deactivated state. However, since they are not in the deactivated state, for example, if a MAC CE to activate an SCell is received in the process (AD), since no instruction to deactivate the SCG has been given (or the SCG is not in the deactivated state), the process (AD-1) may be performed. (C) When the SCG returns from the deactivated state based on an RRC message, if this RRC message includes parameters related to random access to some or all SCells, a random access procedure is initiated on the target SCell based on the notified parameters. (D) When the recovery of the SCG from an inactivated state is performed based on an RRC message, if this RRC message includes information specifying the state of the SCell, a decision is made based on that information as to whether the state of each SCell should be set to an active state or an inactive state. (E) The Active BWP of the SpCell is switched to a specific BWP. The specific BWP may be a BWP designated by the base station device, or may be a BWP set as the First Active BWP. (F) Activate the BWP set as the First Active BWP of the SpCell.

[0320] Based on the above description, various embodiments of the present invention will be described. Note that the processes described above may be applied to the processes omitted in the following description.

[0321] Fig. 5 is a block diagram showing the configuration of a terminal device (UE 122) according to an embodiment of the present invention. To avoid complicating the explanation, Fig. 5 shows only the main components closely related to one embodiment of the present invention.

[0322] The UE 122 shown in FIG. 5 includes a receiver 500 that receives RRC messages and the like from a base station device, a processor 502 that performs processing according to parameters included in the received messages, and a transmitter 504 that transmits RRC messages and the like to the base station device. The base station device may be the eNB 102 or the gNB 108. The processor 502 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processor 502 may include some or all of the physical layer processor, MAC layer processor, RLC layer processor, PDCP layer processor, SDAP processor, RRC layer processor, and NAS layer processor. The UE 122 may also include a measurement unit (not shown) for performing measurements.

[0323] Fig. 6 is a block diagram showing the configuration of a base station device according to an embodiment of the present invention. To avoid complication of explanation, Fig. 6 shows only main components closely related to one embodiment of the present invention. The base station device may be an eNB 102 or a gNB 108.

[0324] 6 includes a transmitter 600 that transmits an RRC message or the like to the UE 122, a processor 602 that creates an RRC message including parameters and transmits it to the UE 122, causing the processor 502 of the UE 122 to process it, and a receiver 604 that receives the RRC message or the like from the UE 122. The processor 602 may include some or all of the functions of various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processor 602 may include some or all of the functions of the physical layer processor, MAC layer processor, RLC layer processor, PDCP layer processor, SDAP processor, RRC layer processor, and NAS layer processor.

[0325] Various examples of processing by the terminal device according to the embodiment of the present invention will be described below.

[0326] FIG. 15 is a diagram showing an example of processing performed by the terminal device in the embodiment of the present invention.

[0327] The terminal device (UE 122) receives a message from the base station device (eNB 102 or gNB 108) (step S1500). This message may include one or more downlink BWP configurations for the SpCell. Each downlink BWP configuration may include information on a reference signal used for radio link monitoring. This message may also include information for determining (or instructing) whether to activate or deactivate the cell group. The configuration and information may be notified in the same message or different messages. The message may be an RRC message, a MAC control element, a message including a MAC control element, or any other message, or a combination thereof.

[0328] The message may include information (BWP identifier) ​​indicating a specific BWP (first BWP) among the downlink BWPs.

[0329] Based on the fact that the received message contains information indicating that the cell group is to be deactivated (or based on the deactivation of the cell group), the terminal device switches the Active DL BWP of the SpCell of the cell group to the first BWP (step S1502). The terminal device performs radio link monitoring using a reference signal used for radio link monitoring set for the first BWP. The cell group may be a master cell group or a secondary cell group.

[0330] This allows the terminal device to efficiently perform the radio link monitoring required when the cell group is deactivated, and also allows the base station device to efficiently obtain information about the radio link failure of the cell group from the terminal device that deactivated the cell group.

[0331] An example in which the message is an RRC message will be shown. The terminal device receives an RRC message transmitted from a base station device (eNB 102 or gNB 108). This RRC message may include one or more downlink BWP configurations for the SpCell (e.g., BWP-Downlink information elements included in a ServingCellConfig information element in NR). Each downlink BWP configuration may include information on a reference signal used for radio link monitoring (e.g., a RadioLinkMonitoringConfig information element in NR). This RRC message may also include information for determining whether a cell group is in an active state or an inactive state. The configurations and information may be included in the same RRC message or in different RRC messages. This RRC message may also be an RRC connection reconfiguration message in LTE. This RRC message may also be an RRC reconfiguration message in NR.

[0332] The message may include information (for example, a BWP identifier) ​​indicating a specific BWP (first BWP) among the downlink BWPs.

[0333] The RRC entity of the terminal device notifies the MAC entity of the information indicating the first BWP based on the fact that the received message includes information indicating the first BWP.

[0334] The RRC entity of the terminal device notifies (instructs) the MAC entity of the cell group to deactivate the cell group based on the fact that the received message contains information indicating that the cell group is to be deactivated (or based on deactivating the cell group).

[0335] The MAC entity that has been notified (instructed) of the deactivation of the cell group switches the Active Downlink BWP of the SpCell of the cell group to the first BWP. The PHY entity of the terminal device may evaluate whether the first BWP is in-sync or out-of-sync based on the received power of a reference signal used for radio link monitoring configured for the first BWP. The RRC entity of the terminal device may perform radio link monitoring based on the evaluation by the PHY entity.

[0336] An example of the first BWP will be described. For example, the first BWP may be a BWP indicated by a first active downlink BWP identifier (firstActiveDownlinkBWP-Id). Also, for example, the first BWP may be an initial downlink BWP (initialDownlinkBWP) (i.e., a BWP with a BWP identifier of 0). Also, for example, the first BWP may be a BWP set as a dormant BWP. Also, for example, the first BWP may be a BWP with a BWP identifier designated by a base station device as a switching destination in a PSCell when a cell group is deactivated. Also, for example, the first BWP may be a BWP that was an active BWP in a PSCell until the terminal device deactivated an SCG.

[0337] This allows the terminal device to efficiently perform the radio link monitoring required when a cell group is deactivated based on the RRC reconfiguration message.

[0338] Furthermore, the RRC entity of the terminal device may perform radio link monitoring in the cell group based on relaxed requirements, based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated. The relaxed requirements may be requirements defined in advance by a specification, or may be requirements notified from the base station device.

[0339] FIG. 16 is a diagram showing an example of processing performed by the terminal device in the embodiment of the present invention.

[0340] The terminal device (UE 122) receives a message from the base station device (eNB 102 or gNB 108) (step S1600). This message may include measurement configuration. This message may also include information for determining (or instructing) whether to activate or deactivate a cell group. The measurement configuration and the information may be notified in the same message or in different messages. The message may be an RRC message, a MAC control element, a message including a MAC control element, or any other message, or a combination thereof.

[0341] The measurement configuration may include information (measurement identification information) that can identify whether the measurement is the first measurement or the second measurement (or whether it is not the first measurement). The measurement identification information may be information that indicates whether the measurement is the first measurement or the second measurement. Furthermore, the measurement identification information may be information that indicates that the measurement is the first measurement when the measurement identification information is included in the measurement configuration, and that indicates that the measurement is the second measurement when the measurement identification information is not included in the measurement configuration. Furthermore, the measurement identification information may be information that is included in an information element other than the measurement configuration.

[0342] The terminal device configures itself not to perform a first measurement and / or a first measurement result among the configured measurement configurations based on the fact that the received message includes information indicating that the cell group is to be deactivated (step S1602). At this time, the terminal device may continue to report a second measurement and / or a second measurement result among the configured measurement configurations. Alternatively, the RRC entity of the terminal device may process the first measurement among the measurement configurations configured in the cell group based on relaxed requirements based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated. The relaxed requirements may be requirements defined in advance by a specification or requirements notified from a base station device.

[0343] For example, the relaxed requirement may be that the maximum allowable time for the terminal device to identify a new cell on a certain frequency in the first measurement is longer than the maximum allowable time in the second measurement. Also, for example, the relaxed requirement may be that the period allowed for the terminal device to measure reference signal received power (RSRP) and / or reference signal received quality (RSRQ) with a required accuracy in the first measurement is longer than the period in the second measurement. The relaxed requirement may also be other conditions.

[0344] The cell group may be a master cell group or a secondary cell group.

[0345] This allows the terminal device to efficiently perform the necessary measurements when the cell group is deactivated, and the base station device can efficiently obtain the measurement results required by the base station device from the terminal device that has deactivated the cell group.

[0346] An example in which the message is an RRC message will be shown. The terminal device receives an RRC message transmitted from a base station device (eNB 102 or gNB 108). This RRC message may include measurement configuration. This RRC message may also include information for determining whether a cell group is in an active state or an inactive state. The measurement configuration and the information may be included in the same RRC message or in different RRC messages. This RRC message may also be an RRC connection reconfiguration message in LTE. This RRC message may also be an RRC reconfiguration message in NR.

[0347] The RRC entity of the terminal device determines whether each measurement identified by the measurement identifier is a first measurement or a second measurement based on the fact that the received RRC message includes a measurement configuration and that the measurement configuration includes measurement identification information.

[0348] The RRC entity of the terminal device (1) instructs the MAC entity of the cell group to deactivate the cell group based on the fact that the received RRC message contains information indicating that the cell group is to be deactivated, and (2) instructs the MAC entity of the cell group to activate the cell group based on the fact that the received RRC message contains information indicating that the cell group is to be activated.

[0349] The RRC entity of the terminal device processes not to report a first measurement and / or a first measurement result among the measurement configurations configured for the cell group, based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated. Alternatively, the RRC entity of the terminal device may process to perform the first measurement among the measurement configurations configured for the cell group based on relaxed requirements, based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated. The relaxed requirements may be requirements defined in advance by a specification, or may be requirements notified from a base station device.

[0350] The MAC entity of the terminal device may be notified of the activation or deactivation of a cell group by a higher layer (eg, the RRC layer) and / or by another MAC entity of the terminal device.

[0351] An example of measurement identification information will be described. For example, the measurement identification information may be information included in a measurement object. Based on the measurement identification information included in the measurement object, the RRC entity of the terminal device may determine whether measurements of all measurement identifiers associated with the measurement object are first measurements or second measurements.

[0352] Furthermore, for example, the measurement identification information may be information included in the reporting configuration. The RRC entity of the terminal device may determine whether measurements of all measurement identifiers associated with the reporting configuration are first measurements or second measurements based on the measurement identification information included in the reporting configuration.

[0353] Furthermore, for example, the measurement identification information may be information that is not included in the measurement configuration. In this case, the measurement identification information may include information indicating which measurement in the measurement configuration is the first measurement. For example, the measurement identification information may include some or all of the identifier information of the measurement targets of the first measurement, including (A) a measurement identifier, (B) a measurement target identifier, and (C) a reporting configuration identifier. The RRC entity of the terminal device may determine which measurement is the first measurement or the second measurement (or is not the first measurement) based on this measurement identification information.

[0354] The following shows an example of a process in which a terminal device does not report a first measurement and / or a first measurement result among the measurement configurations configured in a cell group based on the inclusion of information indicating that the cell group is to be deactivated in a received RRC message. For example, when the measurement identification information is included in a measurement object, the RRC entity of the terminal device may delete (Remove) the measurement object determined to be the first measurement based on the measurement identification information based on the inclusion of information indicating that the cell group is to be deactivated in the received RRC message. In this case, even if the cell group is activated, the deleted measurement object may not be restored.

[0355] Furthermore, for example, when the measurement identification information is included in the measurement object, the RRC entity of the terminal device may suspend the measurement object determined to be the first measurement by the measurement identification information based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated. In this case, the suspended measurement object may be resumed when the cell group is activated.

[0356] Also, if the measurement identification information is included in the reporting configuration, it may be deleted or suspended in the same way as when the measurement identification information is included in the measurement target.

[0357] Also, for example, the RRC entity of the terminal device may ignore a measurement determined to be the first measurement by the measurement identification information based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated.

[0358] In addition to the measurements specified by the measurement identification information as described above, there may be measurements that are not performed based on a predetermined rule or that are performed with relaxed requirements based on a predetermined rule. For example, the measurements may be inter-frequency measurements and / or inter-radio access technology measurements. Furthermore, the base station device may notify information indicating that measurements are not performed based on a predetermined rule or that measurements with relaxed requirements are enabled (or disabled).

[0359] This allows the terminal device to efficiently perform the necessary measurements when a cell group is deactivated based on the RRC reconfiguration message.

[0360] FIG. 17 is a diagram showing an example of processing by the terminal device in the embodiment of the present invention.

[0361] The terminal device (UE 122) receives a message from the base station device (eNB 102 or gNB 108) (step S1700). This message may include measurement configuration. This message may also include information on conditional reconfiguration. This message may also include information for determining (or instructing) whether to activate or deactivate a cell group. The configuration and information may be notified in the same message or in different messages. The message may be an RRC message, a MAC control element, a message including a MAC control element, or any other message, or a combination thereof.

[0362] The measurement configuration may include a measurement identifier indicating a combination of a measurement target and a reporting configuration, and the conditional reconfiguration may include one or more measurement identifiers as a condition for executing the conditional reconfiguration.

[0363] Based on the fact that the received RRC message includes information indicating the deactivation of a cell group (or based on the deactivation of a cell group), the terminal device configures the measurement configurations configured so as not to perform measurements that satisfy a first condition (step S1502). At this time, the terminal device may continue to report measurements that do not satisfy the first condition and / or results of measurements that do not satisfy the first condition among the configured measurement configurations. Alternatively, based on the fact that the received RRC message includes information indicating the deactivation of a cell group, the RRC entity of the terminal device may process measurements that satisfy the first condition among the measurement configurations configured in the cell group based on relaxed requirements. The relaxed requirements may be requirements defined in advance by a specification or may be requirements notified from a base station device. The first conditions may include some or all of the following conditions (A) to (C): (A) The measurement target is an inter-frequency measurement (the measurement target frequency is a frequency other than the serving cell, or the measurement target frequency is a serving frequency with a subcarrier spacing different from that of the serving cell) (B) Measurement target is inter-radio access technology measurement (C) The measurement identifier is not included in the conditional reset execution conditions of the conditional reset.

[0364] This allows the terminal device to efficiently perform the necessary measurements when the cell group is deactivated, and the base station device can efficiently obtain the measurement results required by the base station device from the terminal device that has deactivated the cell group.

[0365] An example in which the message is an RRC message will be shown. The terminal device receives an RRC message transmitted from a base station device (eNB 102 or gNB 108). This RRC message may include measurement configuration. This message may also include conditional reconfiguration information. This RRC message may also include information for determining whether a cell group is in an active state or an inactive state. The configuration and information may be included in the same RRC message or in different RRC messages. This RRC message may also be an RRC connection reconfiguration message in LTE. This RRC message may also be an RRC reconfiguration message in NR.

[0366] The RRC entity of the terminal device retains information about the measurement configuration including the measurement identifier based on the fact that the measurement configuration is included in the received RRC message.

[0367] The RRC entity of the terminal device stores information about the conditional reconfiguration, including one or more measurement identifiers included as a condition for executing the conditional reconfiguration, based on the conditional reconfiguration included in the received RRC message. The RRC entity of the terminal device determines whether the condition for executing the conditional reconfiguration is met based on the measurement results of the measurement configuration corresponding to the measurement identifiers included as a condition for executing the conditional reconfiguration.

[0368] The RRC entity of the terminal device (1) instructs the MAC entity of the cell group to deactivate the cell group based on the fact that the received RRC message contains information indicating that the cell group is to be deactivated, and (2) instructs the MAC entity of the cell group to activate the cell group based on the fact that the received RRC message contains information indicating that the cell group is to be activated.

[0369] The RRC entity of the terminal device configures the measurement configurations configured in the terminal device not to perform measurements that satisfy the first condition, based on the received message including information indicating that the cell group is to be deactivated (or based on the deactivation of the cell group). At this time, the terminal device may continue to report measurements that do not satisfy the first condition and / or results of measurements that do not satisfy the first condition, based on the received RRC message including information indicating that the cell group is to be deactivated. Alternatively, the RRC entity of the terminal device may process measurements that satisfy the first condition, based on relaxed requirements, based on the received RRC message including information indicating that the cell group is to be deactivated. The relaxed requirements may be requirements defined in advance by a specification or requirements notified from a base station device.

[0370] This allows the terminal device to efficiently perform the necessary measurements when a cell group is deactivated based on the RRC reconfiguration message.

[0371] In addition, in the above explanations, "based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated" may be rephrased as "based on deactivating the cell group." That is, even if the cell group is not explicitly deactivated by an RRC message, the above operations may be applied when the cell group is deactivated. Furthermore, any of the above processes may be performed in the terminal device, or some or all of the above processes may be performed.

[0372] The deactivated state of a cell group may also consist of one or more states, for example, a state in which the cell group is deactivated and the time alignment timer is running, and a state in which the cell group is deactivated and the time alignment timer is stopped.

[0373] For example, when a cell group is deactivated and the time consistency timer of the PTAG of the cell group is running, the first BWP in the SpCell of the cell group may become the Active BWP, and when the cell group is deactivated and the time consistency timer of the PTAG of the cell group is stopped, all BWPs in the SpCell of the cell group may be deactivated. In this case, when the cell group is deactivated and any BWP is Active, the terminal device may perform radio link monitoring using a reference signal for radio link monitoring set for that BWP, and may not perform radio link monitoring if all BWPs are Deactivated.

[0374] In the example of the measurement process described above, "based on the received RRC message including information indicating that the cell group is to be deactivated" may be rephrased as "based on the cell group being deactivated and the time alignment timer expiring." In other words, when the cell group is deactivated and the time alignment timer expires, some measurements may not be performed or may be performed under relaxed requirements.

[0375] The terminal device may also be provided with a timer that starts when the cell group is deactivated, and there may be a state in which the cell group is deactivated and the timer is running, and a state in which the cell group is deactivated and the timer has expired and stopped.

[0376] For example, when a cell group is deactivated and the timer is running, the first BWP in the SpCell of the cell group may become the Active BWP, and when the cell group is deactivated and the timer is stopped, all BWPs in the SpCell of the cell group may be deactivated. In this case, when the cell group is deactivated and any BWP is Active, the terminal device may perform radio link monitoring using a reference signal for radio link monitoring set for that BWP, and may not perform radio link monitoring when all BWPs are Deactivated.

[0377] In the above example of the measurement process, "based on the fact that the received RRC message includes information indicating that the cell group is to be deactivated" may be rephrased as "based on the fact that the cell group is deactivated and a certain timer has expired." In other words, when the cell group is deactivated and a certain timer has expired, some measurements may not be performed or may be performed under relaxed requirements.

[0378] "Including information indicating that the cell group is to be in an inactive state" may include not including information indicating that the cell group is to be in an active state. Similarly, "Including information indicating that the cell group is to be in an active state" may include not including information indicating that the cell group is to be in an inactive state.

[0379] Furthermore, activating (deactivating) a cell group and activating (deactivating) the SpCells of that cell group may be interchangeable. Similarly, placing a cell group in an active state (inactive state) and placing the SpCells of that cell group in an active state (inactive state) may be interchangeable.

[0380] Furthermore, the MAC entity of the terminal device may not stop the time alignment timer of the PTAG of the secondary cell group when the secondary cell group is deactivated. The MAC entity of the terminal device may initiate a random access procedure based on the fact that the time alignment timer of the PTAG of the secondary cell group is not running (stopped) when the secondary cell group is activated. The MAC entity of the terminal device may notify the upper layer (RRC entity) of information that enables it to determine that the time alignment timer has expired based on the fact that the secondary cell group is deactivated and the time alignment timer of the PTAG of the cell group has expired.

[0381] The radio bearer in the above description may be a DRB, an SRB, or a combination of a DRB and an SRB.

[0382] In the above description, expressions such as "link," "associate," and "link" may be interchangeable.

[0383] In the above description, the "SpCell of an SCG" may be replaced with the "PSCell."

[0384] In the above description, "dormant state" and "inactive state" may be interchangeable, and "state restored from dormant state" and "active state" may be interchangeable. Also, in the above description, "activated, inactivated" and "active state, inactive state" may be interchangeable.

[0385] In the above description, "activated BWP" and "Active BWP" may be interchangeable.

[0386] Furthermore, in each example of processing or each example of processing flow in the above description, some or all of the steps may not be executed. Furthermore, in each example of processing or each example of processing flow in the above description, the order of the steps may be different. Furthermore, in each example of processing or each example of processing flow in the above description, some or all of the processing within each step may not be executed. Furthermore, in each example of processing or each example of processing flow in the above description, the order of the processing within each step may be different. Furthermore, in the above description, "performing B based on A being true" may be rephrased as "performing B." In other words, "performing B" may be executed independently of "being A."

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

[0388] Also, in the above explanation, if condition "A" and condition "B" are conditions that cannot be satisfied at the same time, condition "B" may be expressed as an "other" condition of condition "A."

[0389] Various aspects of the terminal device and method according to embodiments of the present invention will now be described.

[0390] (1) A first embodiment of the present invention is a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and includes a receiving unit that receives an RRC message from the base station device and a processing unit that processes the RRC message received from the base station device, and based on BWP identifier information included in the RRC message, a first active downlink BWP and / or a first active uplink BWP is set, and based on the second cell group being deactivated, the Active DL BWP in the PSCell is switched to the first active downlink BWP, and radio link monitoring is performed using a reference signal for radio link monitoring that is set for the first active downlink BWP.

[0391] (2) A second embodiment of the present invention is a base station device that communicates with a terminal device, comprising: a transmitting unit that transmits an RRC message to the terminal device; and a processing unit that generates an RRC message to be transmitted to the terminal device; and based on BWP identifier information to be included in the RRC message, sets a first active downlink BWP and / or a first active uplink BWP in the terminal device; and based on deactivating a secondary cell group of the terminal device, causes the terminal device to switch an Active DL BWP in a PSCell to the first active downlink BWP and perform radio link monitoring using a reference signal for radio link monitoring set for the first active downlink BWP.

[0392] (3) A third embodiment of the present invention is a method applied to a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, comprising the steps of: receiving an RRC message from the base station device; and processing the RRC message received from the base station device; and configuring a first active downlink BWP and / or a first active uplink BWP based on BWP identifier information included in the RRC message; and switching the Active DL BWP in the PSCell to the first active downlink BWP based on the second cell group being deactivated, and performing radio link monitoring using a reference signal for radio link monitoring configured for the first active downlink BWP.

[0393] (4) A fourth embodiment of the present invention is an integrated circuit implemented in a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and causes the terminal device to perform a function of receiving an RRC message from the base station device and a function of processing the RRC message received from the base station device, and configures a first active downlink BWP and / or a first active uplink BWP based on BWP identifier information included in the RRC message, and switches an Active DL BWP in a PSCell to the first active downlink BWP based on deactivation of the second cell group, and performs radio link monitoring using a reference signal for radio link monitoring configured for the first active downlink BWP.

[0394] (5) A fifth embodiment of the present invention is a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and includes a processing unit that processes an RRC message received from the base station device, and a measurement unit that performs measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes measurement targets, reporting configurations, and measurement identifier information linking the measurement targets and reporting configurations, wherein measurement targets that include the first information are defined as a first measurement target group, and measurement targets that do not include the first information are defined as a second measurement target group, and wherein, based on the second cell group being in an active state, the first measurement target group and the second measurement target group are measured, and, based on the second cell group being in an inactive state, the first measurement target group is not measured or is measured under relaxed requirements.

[0395] (6) A sixth embodiment of the present invention is a base station device that communicates with a terminal device, comprising: a transmitting unit that transmits an RRC message to the terminal device; and a processing unit that generates an RRC message to be transmitted to the terminal device, wherein the measurement configuration included in the RRC message includes information on a measurement target, a reporting configuration, and a measurement identifier that links the measurement target and the reporting configuration; measurement targets that include first information are set to a first measurement target group; and measurement targets that do not include the first information are set to a second measurement target group; by instructing the terminal device to activate a secondary cell group, the terminal device is caused to measure the first measurement target group and the second measurement target group; and by instructing the terminal device to deactivate the secondary cell group, the terminal device is caused to not measure the first measurement target group or to measure it under relaxed requirements.

[0396] (7) A seventh embodiment of the present invention is a method applied to a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, the method comprising: a step of processing an RRC message received from the base station device; and a step of performing measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes measurement targets, reporting configurations, and measurement identifier information linking the measurement targets and reporting configurations; measurement targets that include the first information are defined as a first measurement target group; and measurement targets that do not include the first information are defined as a second measurement target group; and based on the second cell group being in an active state, the first measurement target group and the second measurement target group are measured; and based on the second cell group being in an inactive state, the first measurement target group is not measured or is measured under relaxed requirements.

[0397] (8) An eighth embodiment of the present invention is an integrated circuit implemented in a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and causes the terminal device to perform a function of processing an RRC message received from the base station device and a function of performing measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes measurement targets, reporting configurations, and measurement identifier information linking the measurement targets and reporting configurations, wherein measurement targets that include the first information are defined as a first measurement target group, and measurement targets that do not include the first information are defined as a second measurement target group, and wherein, based on the second cell group being in an active state, the first measurement target group and the second measurement target group are measured, and, based on the second cell group being in an inactive state, the first measurement target group is not measured or is measured under relaxed requirements.

[0398] (9) A ninth embodiment of the present invention is a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and includes: a processing unit that processes an RRC message received from the base station device; and a measurement unit that performs measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes information on a measurement target, a reporting condition, and a measurement identifier that links the measurement target and the reporting condition; when deactivating the second cell group, the terminal device determines whether to delete the measurement for the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell change configuration information element; and deletes the measurement for the measurement identifier based at least on the fact that the measurement identifier is not included in the reconfiguration execution condition field of the conditional PSCell change configuration information element.

[0399] (10) A tenth embodiment of the present invention is a base station device that communicates with a terminal device, comprising: a transmitting unit that transmits an RRC message to the terminal device; and a processing unit that generates an RRC message to be transmitted to the terminal device, wherein the measurement configuration included in the RRC message includes information on a measurement target, a reporting configuration, and a measurement identifier that links the measurement target and the reporting configuration; and by instructing the terminal device to deactivate a secondary cell group, the terminal device is caused to delete the measurement of the measurement identifier based at least on the fact that the measurement identifier is not included in a reconfiguration execution condition field of a conditional PSCell change configuration information element.

[0400] (11) An eleventh embodiment of the present invention is a method applied to a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, comprising the steps of: processing an RRC message received from the base station device; and performing measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes information on measurement targets, reporting conditions, and a measurement identifier that links the measurement targets and reporting conditions; when deactivating the second cell group, determining whether to delete the measurement for the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element; and deleting the measurement for the measurement identifier based at least on the fact that the measurement identifier is not included in the reconfiguration execution condition field of the conditional PSCell modification configuration information element.

[0401] (12) A twelfth embodiment of the present invention is an integrated circuit implemented in a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, and causes the terminal device to perform functions of processing an RRC message received from the base station device and performing measurements based on a measurement configuration included in the RRC message, wherein the measurement configuration includes information on a measurement target, a reporting condition, and a measurement identifier that links the measurement target and the reporting condition, and when the second cell group is deactivated, the integrated circuit determines whether to delete (pause, disable) the measurement of the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element, and deletes the measurement of the measurement identifier based at least on the fact that the measurement identifier is not included in the reconfiguration execution condition field of a conditional PSCell modification configuration information element.

[0402] A program running on an apparatus according to the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of the above-described embodiments according to the present invention. The program or information handled by the program is temporarily loaded into volatile memory such as random access memory (RAM) during processing, or stored in nonvolatile memory such as flash memory or a hard disk drive (HDD), and is read, modified, and written by the CPU as needed.

[0403] Note that a part of the device in the above-described embodiment may be implemented by a computer. In this case, a program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. The "computer system" here refers to a computer system built into the device, including hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0404] Furthermore, the term "computer-readable recording medium" may include 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, or a medium that stores a program for a certain period of time, such as a volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0405] Furthermore, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, typically an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each of the aforementioned circuits may be composed of digital circuits or analog circuits. Furthermore, if advances in semiconductor technology result in the emergence of integrated circuit technologies that can replace current integrated circuits, integrated circuits based on that technology may also be used.

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

[0407] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the gist of the present invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included. [Industrial Applicability]

[0408] The present invention can be used in, for example, communication systems, communication devices (for example, mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (for example, communication chips), programs, and the like. [Explanation of symbols]

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

Claims

1. A terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell. a processing unit for processing an RRC message received from the base station device; a measurement unit that performs measurement based on a measurement configuration included in the RRC message; The measurement setting includes information on a measurement target, a reporting condition, and a measurement identifier that links the measurement target and the reporting condition, When the second group of cells is inactivated, determining whether to delete the measurement with the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element; and deleting the measurement with the measurement identifier based at least on the measurement identifier not being included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element. Terminal device.

2. A base station device that communicates with a terminal device a transmitter for transmitting an RRC message to the terminal device; a processing unit for generating an RRC message to be transmitted to the terminal device, The measurement configuration included in the RRC message includes a measurement target, a reporting configuration, and information on a measurement identifier linking the measurement target and the reporting configuration, Instructing the terminal device to deactivate a secondary cell group causes the terminal device to delete the measurement of the measurement identifier based at least on the measurement identifier not being included in a reconfiguration execution condition field of a conditional PSCell change configuration information element. Base station equipment.

3. A method applied to a terminal device that communicates with one or more base station devices using a first cell group including a PCell and a second cell group including a PSCell, processing an RRC message received from the base station; performing measurements based on a measurement configuration included in the RRC message; The measurement setting includes information on a measurement target, a reporting condition, and a measurement identifier that links the measurement target and the reporting condition, When the second group of cells is inactivated, determining whether to delete the measurement with the measurement identifier based on whether the measurement identifier is included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element; and deleting the measurement with the measurement identifier based at least on the measurement identifier not being included in a reconfiguration execution condition field of a conditional PSCell modification configuration information element. method.

Images