Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, a method, and an integrated circuit, cable of efficiently monitoring a cell group.SOLUTION: A cellular mobile communication system includes a terminal device comprising a processing unit for performing communication using an MCG and an SCG and a reception unit for receiving RRC signaling from a base station device. The SCG includes a PSCell. Upon being set so as to perform beam failure detection (BFD) using the PSCell of the inactivated SCG, the processing unit performs, by RRC signaling, the BFD using the PSCell. Upon receiving a beam failure instance notification from a PHY layer, the processing unit: starts or restarts a beam failure detection timer; when the beam failure detection timer is expired, determines whether or not the BFD is stopped; when determining that the BFD is stopped, does not set a beam failure counter to 0; and, when determining that the BFD is not stopped, sets the beam failure counter to 0.SELECTED DRAWING: Figure 12

Description

Technical Field

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

Background Art

[0002] In the 3rd Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems including radio access, core network, services, etc. are being carried out.

[0003] For example, in 3GPP, E-UTRA (Evolved Universal Terrestrial Radio Access) was started for technical study and standardization as a radio access technology (RAT) for cellular mobile communication systems for the 3.9th and 4th generations. Even now, in 3GPP, technical studies and standardization of extended technologies of E-UTRA are being carried out. Note that E-UTRA is also referred to as Long Term Evolution (LTE: registered trademark), and extended technologies may also be referred to as LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

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

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

Non-Patent Document 6

Non-Patent Document 7

[0006] As an extension technology of NR, there is a dual connectivity (also called multi-connectivity) technology that uses multiple cell groups to enable large-capacity data communication between one or multiple base station devices and terminal devices. In order to communicate in each cell group, the terminal device needs to monitor each cell group for messages addressed to it. In order for the terminal device to be able to communicate with low latency when large amounts of data communication occurs, the terminal device needs to constantly monitor multiple cell groups, which poses a problem of consuming a lot of power. For this reason, a technology has been developed to monitor some cell groups less frequently or to stop monitoring them (cell group deactivation). The study of the technology has begun.

[0007] Non-patent documents 7 and 8 are RRC and MAC protocols created based on the matters agreed upon so far. However, there are still issues to be resolved in order to perform efficient communication control processing.

[0008] 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 communication method, and an integrated circuit that can efficiently perform communication control. [Means for solving the problem]

[0009] To achieve the above object, one aspect of the present invention takes the following means. That is, one aspect of the present invention is a terminal device that communicates with a base station device, including a processing unit that communicates using MCG and SCG, and a radio resource control (RRC) signal receiving unit that receives signaling, wherein the SCG includes a PSCell, and the processing unit is configured to perform beam failure detection (BFD) on the PSCell of the inactivated SCG based on the RRC signaling, and based on receiving a beam failure instance notification from the PHY layer, start or restart a beam failure detection timer. When the beam failure detection timer expires, determine whether the BFD is stopped. If it is determined that the BFD is stopped, do not set the beam failure counter to 0. If it is determined that the BFD is not stopped, set the beam failure counter to 0.

[0010] Also, one aspect of the present invention is a method for a terminal device that communicates with a base station device, which communicates using MCG and SCG, and receives radio resource control (RRC) signal Receiving a reconfiguration, wherein the SCG includes at least a PSCell, and based on being configured to perform beam failure detection (BFD) on the PSCell of the deactivated SCG by the RRC signaling, performing BFD on the PSCell; starting or restarting a beam failure detection timer based on receiving a beam failure instance notification from the PHY layer; determining whether the BFD is stopped when the beam failure detection timer expires; when it is determined that the BFD is stopped, not setting the beam failure counter to 0; and when it is determined that the BFD is not stopped, setting the beam failure counter to 0.

[0011] Also, an aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, the integrated circuit having a function of communicating using an MCG and an SCG, a function of receiving radio resource control (RRC) signaling from the base station device, wherein the SCG includes at least a PSCell, and based on being configured to perform beam failure detection (BFD) on the PSCell of the deactivated SCG by the RRC signaling, a function of performing BFD on the PSCell, a function of starting or restarting a beam failure detection timer based on receiving a beam failure instance notification from the PHY layer, a function of determining whether the BFD is stopped when the beam failure detection timer expires, a function of not setting the beam failure counter to 0 when it is determined that the BFD is stopped, and a function of setting the beam failure counter to 0 when it is determined that the BFD is not stopped.

[0012] Note that these general or specific aspects may be implemented in a system, apparatus, method, integrated circuit, computer program, or recording medium, or may be implemented in any combination of a system, apparatus, method, integrated circuit, computer program, and recording medium.

Advantages of the Invention

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

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Best Mode for Carrying Out the Invention

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

[0016] LTE (and LTE-A, LTE-A Pro) and NR may be defined as different Radio Access Technologies (RATs). Also, NR may be defined as a technology included in LTE. Also, LTE may be defined as a technology included in NR. Also, LTE that can be connected with NR and Multi-Radio Dual Connectivity (MR-DC) may be distinguished from conventional LTE. Also, LTE that uses 5GC for the core network (core network, Core Network: CN) may be distinguished from conventional LTE that uses EPC for the core network. Note that the conventional LTE may be LTE that does not implement the technology standardized after Release 15 in 3GPP. This embodiment may be applied to NR, LTE, and other RATs. In the following description, terms related to LTE and NR will be used for explanation, but this embodiment may be applied to other technologies that use other terms. Also, the term E-UTRA in this embodiment may be replaced with the term LTE, and the term LTE may be replaced with the term E-UTRA.

[0017] Note that in this embodiment, the names of each node and entity when the radio access technology is E-UTRA or NR, and the processing, etc. in each node and entity will be described, but this embodiment may be used for other radio access technologies. The names of each node and entity in this embodiment may be different names.

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

[0019] E-UTRA 100 may be a radio access technology. Also, E-UTRA 100 may be the air interface between the UE 122 and the eNB 102. The air interface between the UE 122 and the eNB 102 may be called the Uu interface. The eNB (E-UTRAN Node B) 102 may be the base station device of E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN. The air interface between the UE 122 and the eNB 102 may be called the Uu interface. The eNB (E-UTRAN Node B) 102 may be the base station device of E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN. The eNB (E-UTRAN Node B) 102 may be the base station device of E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may be composed of the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol described below. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol with respect to the UE 122. The radio access network composed of eNBs may be called E-UTRAN.

[0020] The EPC (Evolved Packet Core) 104 may be the core network. The interface 112 is the interface between the eNB 102 and the EPC 104 and may be called the S1 interface. The interface 112 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may be terminated by the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated by the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be called the S1-MME interface. The user plane interface of the interface 112 may be called the S1-U interface. The interface 112 is the interface between the eNB 102 and the EPC 104 and may be called the S1 interface. The interface 112 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may be terminated by the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated by the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be called the S1-MME interface. The user plane interface of the interface 112 may be called the S1-U interface. The interface 112 may have a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of the interface 112 may be terminated by the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated by the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be called the S1-MME interface. The user plane interface of the interface 112 may be called the S1-U interface. The control plane interface of the interface 112 may be terminated by the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated by the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be called the S1-MME interface. The user plane interface of the interface 112 may be called the S1-U interface. The user plane interface of the interface 112 may be called the S1-U interface.

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

[0022] NR 106 may be a radio access technology. Also, NR 106 may 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 the Uu interface. The gNB (g Node B) 108 may be a base station device of NR 106. The gNB 108 may have the NR protocol described below. The NR protocol may be composed of the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol described below. The gNB 108 may terminate the NR User Plane (UP) protocol and the NR Control Plane (CP) protocol for the UE 122.

[0023] The 5GC 110 may be a core network. The interface 116 is an interface between the gNB 108 and the 5GC 110 and may be referred to as the NG interface. The 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 the interface 116 may be terminated at an Access and mobility Management Function (AMF: not shown) within the 5GC 110. The user plane interface of interface 116 may terminate at a User Plane Function (UPF, not shown) within 5GC110. The control plane interface of interface 116 may be referred to as the NG-C interface. The user plane interface of interface 116 may be referred to as the NG-U interface.

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

[0025] eNB 102 may have a function to connect to 5GC110. eNB 102 having a function to connect to 5GC110 may be referred to as an ng-eNB. Interface 114 is an interface between eNB 102 and 5GC110 and may be called the NG interface. Control plane interfaces through which control signals pass, and / or user plane interfaces through which user data passes may exist therein. The control plane interface of interface 114 may terminate at the AMF within 5GC110. The user plane interface of interface 114 may terminate at the UPF within 5GC110. The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be referred to as the NG-U interface. A radio access network composed of ng-eNBs or gNBs may also be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may simply be referred to as the network. Also, the network may include eNBs, ng-eNBs, gNBs, etc.

[0026] One or more eNBs 102 may be connected to the 5GC 110 via the interface 114. An interface may exist (not shown) between multiple eNBs 102 connected to the 5GC 110. The interface between multiple eNBs 102 connected to the 5GC 110 may be referred to as the Xn interface. Also, the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be connected by the interface 120. The interface 120 between the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be referred to as the Xn interface.

[0027] The gNB 108 may have a function of connecting to the EPC 104. The gNB 108 having a function of connecting to the EPC 104 may be referred to as an en-gNB. The interface 118 is an interface between the gNB 108 and the EPC 104 and may be called the S1 interface. The interface 118 may have a user plane interface through which user data passes. The user plane interface of the interface 118 may terminate at the S-GW (not shown) within the EPC 104. The user plane interface of the interface 118 may be referred to as the S1-U interface. Also, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected by the interface 120. The interface 120 between the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be referred to as the X2 interface. The user plane interface of the interface 118 may terminate at the S-GW (not shown) within the EPC 104. The user plane interface of the interface 118 may be referred to as the S1-U interface. Also, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected by the interface 120. The interface 120 between the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be referred to as the X2 interface. The interface 124 is an interface between the EPC 104 and the 5GC 110 and may be an interface that passes only the CP, or only the UP, or both the CP and the UP. Also, 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 a communication carrier or the like.

[0028] The interface 124 is an interface between the EPC 104 and the 5GC 110 and may be an interface that passes only the CP, or only the UP, or both the CP and the UP. Also, 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 a communication carrier or the like. The interface 124 is an interface between the EPC 104 and the 5GC 110 and may be an interface that passes only the CP, or only the UP, or both the CP and the UP. Also, 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 a communication carrier or the like. The interface 124 is an interface between the EPC 104 and the 5GC 110 and may be an interface that passes only the CP, or only the UP, or both the CP and the UP. Also, 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 a communication carrier or the like.

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

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

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

[0032] The EPC 104 may not have a PDU session and / or a QoS flow. Also, the 5GC 110 may not have an EPS bearer. When the UE 122 is connected to the EPC 104, the UE 122 has information about the EPS bearer, but may not have information about the PDU session and / or the QoS flow. Also, when the UE 122 is connected to the 5GC 110, the UE 122 has information about the PDU session and / or the QoS flow, but may not have information about the EPS bearer.

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

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

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

[0036] Figure 3(A) shows the NR user plane (UP) protocol stack. As shown in Figure 3(A), the NR The UP protocol may be a protocol between the UE 122 and the gNB 108, i.e., the NR UP protocol. On the network side, the NR user plane protocol stack may be a protocol that terminates at the gNB 108. As shown in Figure 3(A), the NR user plane protocol stack may be composed of a radio physical layer PHY 300, a medium access control layer MAC 302, a radio link control layer RLC 304, a packet data convergence protocol layer PDCP 306, and a service data adaptation protocol layer SDAP (Service Data Adaptation Protocol) 310.

[0037] 2(B) is a diagram of the E-UTRA control plane (CP) protocol configuration. As shown in FIG. 2(B), in the E-UTRA CP protocol, RRC (Radio Resource Control) 208, which is a radio resource control layer, may be a protocol between the UE 122 and the eNB 102. That is, RRC 208 may be a protocol that terminates at the eNB 102 on the network side. Also, in the E-UTRA 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.

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

[0039] 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 the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and a part or all of the RRC 208. Layers including all of and / or any of PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308 It may be a layer that includes part or all of the above.

[0040] In the present embodiment, the E-UTRA protocol and the NR protocol may not be distinguished from each other, and the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may 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.

[0041] In this embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and the RRC 208 will be referred to as the PHY for E-UTRA or the PHY for LTE, the MAC for E-UTRA or the MAC for LTE, the RLC for E-UTRA or the RLC for LTE, the PDCP for E-UTRA or the PDCP for LTE ... RLC for E-UTRA or the RLC for LTE, the PDCP 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. Yes. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 may also be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. Also, PHY300, MAC302, RLC304, PDCP306, and RRC308 may sometimes be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

[0042] Entities in the AS layer of E-UTRA and / or NR are described. An entity having some or all of the functions of the MAC layer may be called a MAC entity. An entity having some or all of the functions of the RLC layer may be called an RLC entity. An entity having some or all of the functions of the PDCP layer may be called a PDCP entity. An entity having some or all of the functions of the SDAP layer may be called an SDAP entity. An entity having some or all of the functions of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be alternatively referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

[0043] In addition, the data provided by the lower layer to MAC, RLC, PDCP, SDAP, and / or the data provided by the lower layer to MAC, RLC, PDCP, SDAP may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided by the upper layer to MAC, RLC, PDCP, SDAP, and / or the data provided by MAC, RLC, PDCP, SDAP to the upper layer may be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Also, the segmented RLC SDU may be called an RLC SDU segment.

[0044] Here, the base station device and the terminal device exchange signals (transmit and receive) in the upper layer (higher layer). For example, the base station device and the terminal device perform radio resource control (RRC: A base station apparatus and a terminal apparatus may transmit and receive an RRC message (also referred to as an RRC message, RRC information, or RRC signaling) in a Radio Resource Control (MAC) layer. Furthermore, a base station apparatus and a terminal apparatus may transmit and receive a MAC control element in a Medium Access Control (MAC) layer. Furthermore, the RRC layer of the terminal apparatus acquires system information broadcast from the base station apparatus. Here, the RRC message, the system information, and / or the MAC control element are also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). Each of the parameters included in a higher layer signal received by a terminal apparatus may be referred to as a higher layer parameter. In PHY layer processing, the higher layer refers to a layer higher than the PHY layer, and may therefore refer to one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. For example, in MAC layer processing, the higher layer may refer to one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. Hereinafter, the meaning of "A is given (provided) by an upper layer" or "A is given (provided) by an upper layer" may mean that an upper layer (mainly an RRC layer, a MAC layer, etc.) of a terminal device receives A from a base station device, and the received A is given (provided) to a physical layer of the terminal device from the upper layer of the terminal device. For example, in a terminal device, "being provided with an upper layer parameter" may mean receiving an upper layer signal from a base station device, and providing an upper layer parameter included in the received upper layer signal from the upper layer of the terminal device to the physical layer of the terminal device. Setting an upper layer parameter in a terminal device may mean that the upper layer parameter is given (provided) to the terminal device. For example, setting an upper layer parameter in a terminal device may mean that the terminal device receives an upper layer signal from a base station device, and setting the received upper layer parameter in an upper layer.However, setting upper layer parameters in the terminal device may include setting default parameters that are pre-assigned to the upper layer of the terminal device. When describing transmission of an RRC message from a terminal device to a base station device, the expression "submitting a message from the RRC entity of the terminal device to a lower layer" may be used. In the terminal device, "submitting a message to a lower layer" from the RRC entity may mean submitting a message to the PDCP layer. In the terminal device, "submitting a message to a lower layer" from the RRC layer may mean submitting to a PDCP entity corresponding to each SRB, since RRC messages are transmitted using SRBs (SRB0, SRB1, SRB2, SRB3, etc.). When the RRC entity of the terminal device receives an indication from a lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

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

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

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

[0048] PBCH may be used to notify the system information required by the terminal device.

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

[0050] PDCCH may be used to transmit (or carry) the downlink control information (DCI) in downlink wireless communication (wireless communication from the base station device to the terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for the transmission of the downlink control information. That is, the fields for the downlink control information may be defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate link control information (Downlink Control Information: DCI) is transmitted (or carried) for use. Here, for the transmission of downlink control information, one or more DCIs (which may also be referred to as DCI formats) may be defined. That is, the fields for the downlink control information may be defined as DCI and mapped to information bits. ru field is defined as DCI and mapped to information bits. PDCCH is a PDCCH candidate The PDCCH may be transmitted in a complementary manner. The terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring the set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. The terminal device may also use a CORESET (Control Resource Set) to monitor the set of PDCCH candidates. The DCI format may be used for scheduling the PUSCH in the serving cell. The PUSCH may be used for transmitting user data, an RRC message (to be described later), etc.

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

[0052] 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.

[0053] The PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or HARQ-ACK and / or CSI together with the 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. Also, the PDSCH or PUSCH may be used to transmit RRC signaling (also referred to as an RRC message) and MAC CE. Here, in the PDSCH, the RRC signaling transmitted from the base station apparatus may be common signaling for a plurality of terminal apparatuses within the cell. Also, the RRC signaling transmitted from the base station apparatus may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal apparatus. That is, UE-specific information may be transmitted using dedicated signaling for a certain terminal apparatus. Also, the PUSCH may be used to transmit the UE's capability in the uplink.

[0054] The PRACH may be used to transmit a random access preamble. The PRACH may be used for an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, synchronization for uplink transmission (timing adjustment), and indicating a request for UL-SCH resources.

[0055] An example of the function of the MAC will be described. The MAC may be called a MAC sublayer. The MAC multiplexes various logical channels into corresponding transport It may have a function of performing mapping for a transport channel. The logical channel may be identified by a logical channel identifier (Logical Channel Identity, or Logical Channel ID). The MAC may be connected to the upper RLC through a logical channel. The logical channel may be divided into a control channel for transmitting control information and a traffic channel for transmitting user information according to the type of information to be transmitted. Also, the logical channel may be divided into an uplink logical channel and a downlink logical channel. The MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to the PHY. Also, the MAC may have a function of demultiplexing the MAC PDUs provided from the PHY and providing them to the upper layer through the logical channel to which each MAC SDU belongs. Also, the MAC may have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). Also, the MAC may have a function of a scheduling report (SR) that reports scheduling information. The MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have a function of performing priority processing for overlapping resources within one terminal device. The E-UTRA MAC may have a function of identifying Multimedia Broadcast Multicast Services (MBMS). Also, the NR MAC may have a function of identifying Multicast Broadcast Service (MBS). The MAC may have a function of selecting a transport format.The MAC may have functions such as discontinuous reception (DRX) and / or discontinuous transmission (DTX), a random access (RA) procedure, a power headroom report (PHR) function that notifies information about available transmission power, and a buffer status report (BSR) function that notifies information about the amount of data in the transmission buffer. The NR MAC may have a bandwidth adaptation (BA) function. The MAC PDU format used in the E-UTRA MAC may differ from that used in the NR MAC. The MAC PDU may also include a MAC control element (MAC CE), which is an element for performing control in the MAC.

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

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

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

[0059] 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 is 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.

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

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

[0062] The mapping between the logical channels and the transport channels in the uplink of E-UTRA and / or NR will be described.

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

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

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

[0066] The mapping between the logical channels and the transport channels in the downlink of E-UTRA and / or NR will be described.

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

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

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

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

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

[0072] An example of the RLC function will be described. RLC may be referred to as the RLC sublayer. E-UTRA RLC may have a function of segmenting and / or concatenating the data provided from the upper-layer PDCP and providing it to the lower layer. E-UTRA RLC may have a function of performing reassembly and re-ordering on the data provided from the lower layer and providing it to the upper layer. NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to the data provided from the upper-layer PDCP. Also, NR RLC may have a function of segmenting the data provided from PDCP and providing it to the lower layer. Also, NR RLC may have a function of performing reassembly on the data provided from the lower layer and providing it to the upper layer. Also, RLC may have a data retransmission function and / or an Automatic Repeat reQuest (ARQ) function. Also, RLC may have a function of performing error correction by ARQ. For performing ARQ, the control information indicating the data that needs to be retransmitted, which is sent from the receiving side of RLC to the transmitting side, may be referred to as a status report. Also, the matter of the status report transmission instruction sent from the transmitting side of RLC to the receiving side may be referred to as a poll. Also, RLC may have a function of detecting data duplication. Also, RLC may have a function of discarding data. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM, the segmentation of the data received from the upper layer is not performed, and the addition of the RLC header may not be performed. The TM RLC entity is a uni-directional entity and may be set as a transmitting TM RLC entity or a receiving TM RLC entity.In UM, the UM RLC entity performs functions such as segmenting and / or concatenating data received from a higher layer and adding an RLC header, but does not require data retransmission control. The UM RLC entity may be a unidirectional or 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, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, the UM RLC entity may perform functions such as segmenting and / or concatenating 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. Furthermore, data provided to a lower layer in UM and / or data provided from a lower layer may be referred to as a UMD PDU. Furthermore, data provided to or provided from a lower layer in AM may be called an AMD PDU. The RLC PDU format used in E-UTRA RLC may differ from the RLC PDU format used in NR RLC. 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).

[0073] An example of PDCP functionality is described below. PDCP may be called a PDCP sublayer. 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 (registered trademark) Header Compression) protocol. PDCP may also have a data encryption / decryption function. PDCP may also have data integrity protection / verification functions. PDCP may also have a reordering 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 to discard duplicated data. The PDCP entity is a bidirectional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from 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).

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

[0075] An example of the functions of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. It may have. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or 5GC 110. Also, the RRC may have an RRC connection management function. Also, the RRC may have a radio bearer control function. Also, the RRC may have a cell group control function. Also, the RRC may have a mobility control function. Also, the RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. Also, the RRC may have a QoS management function. Also, the RRC may have a function for detecting and recovering radio link failures. The RRC may perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, detection and recovery of radio link failures, etc. using RRC messages. 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.

[0076] The RRC message may be sent using the BCCH of the logical channel, or the PCCH of the logical channel, or the CCCH of the logical channel, or the DCCH of the logical channel. Also, the RRC message sent using the DCCH may be referred to as dedicated RRC signaling or RRC signaling.

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

[0078] RRC messages sent 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. may be included. Other RRC messages may also be included.

[0079] 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), 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. may be included. Other RRC messages may also be included.

[0080] RRC signaling sent in the uplink (UL) direction using the DCCH may include, for example, a measurement report It may include a message (Measurement Report), an RRC connection reconfiguration complete message (RRC Connection Reconfiguration Complete), an RRC connection setup complete message (RRC Connection Setup Complete), an RRC connection reestablishment complete message (RRC Connection Reestablishment Complete), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. Also, for example, it may include a measurement report message (Measurement Report), an RRC reconfiguration complete message (RRC Reconfiguration Complete), an RRC setup complete message (RRC Setup Complete), an RRC reestablishment complete message (RRC Reestablishment Complete), an RRC resume complete message (RRC Resume Complete), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), etc. Additionally, other RRC signaling may be included.

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

[0082] An example of the NAS function is explained below. The NAS may have an authentication function. The NAS may also have the functionality to perform security control. You can have it.

[0083] The above-mentioned PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are examples, and only a portion of each function is shown. In addition, some or all of the functions of each layer may be included in another layer.

[0084] Next, state transitions of the UE 122 in LTE and NR will be described. When the UE 122 connected to EPC or 5GC has an established RRC connection, 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.

[0085] Note that when the UE 122 is connected to the EPC, it does not have the RRC_INACTIVE state, but is connected to the E-UTRAN. The suspension of the RRC connection may be initiated by the UE 122. If the UE 122 is connected to the EPC, when the RRC connection is suspended, the 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 the UE 122 (e.g., the NAS layer) may initiate the resumption of the suspended RRC connection when the UE 122 retains the UE AS context, the E-UTRAN has permitted the resumption of the RRC connection, and the UE 122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0086] The definition of dormancy 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 return from dormancy may be different when UE 122 is connected to EPC (when UE 122 is dormant in RRC_IDLE state) and when UE 122 is connected to 5GC (when UE 122 is dormant in RRC_INACTIVE state).

[0087] The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state are referred to as connection states, respectively. The RRC state may be referred to as connected mode, inactive mode, or idle mode, or may be referred to as RRC connected mode, RRC inactive mode, or RRC idle mode.

[0088] The UE AS context held by the UE 122 includes the current RRC configuration, the current security context, The information may include all or a part of the following: the UE AS context held by one or all of the eNB 102 and the gNB 108, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the source PCell, the cell identity, and the physical cell identity 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.

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

[0090] Next, the serving cell will be described. In a terminal device in the RRC connection state where CA and / or DC described later are not configured, the serving cell may be composed of one primary cell (PCell). Also, in a terminal device in the RRC connection state where CA and / or DC described later are configured, the plurality of serving cells may mean a set of cells composed of one or more special cells (SpCell) and one or more secondary cells (SCell). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be the cell used in the RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connection state. Also, the PCell may be the cell used in the RRC connection re-establishment procedure when the terminal device performs RRC connection re-establishment. The PCell may also be the cell used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes. used in the random access procedure during handover. The PSCell may be the cell used in the random access procedure when adding a secondary node described later. Also, the SpCell may be the cell used for purposes other than the above-mentioned purposes.

[0091] If the group of serving cells configured for a terminal device consists of a SpCell and one or more SCell, it may be regarded that carrier aggregation (CA) is configured for the terminal device. Also, for a terminal device with CA configured, a cell that provides additional radio resources for the SpCell may mean an SCell.

[0092] A group of serving cells configured by RRC, in which the uplink is configured for the cells using the same timing reference cell and the same timing advance value may be called a Timing Advance Group (TAG). Also, a TAG including the SpCell of the MAC entity may mean a Primary Timing Advance Group (PTAG). Also, a TAG other than the above PTAG may mean a Secondary Timing Advance Group (STAG). Note that one or more of the above TAGs may be configured for each cell group described later. The cell group (Cell Group) configured for the terminal device from the base station device will be described. The cell group may be composed of one SpCell. Also, the cell group may be composed of one SpCell and one or more SCell. That is, the cell group may be composed of one SpCell and optionally one or more SCell. Also, the cell group may be expressed as a set of cell(s).

[0093]

[0094] Dual Connectivity (DC) refers to a technology that performs data communication using the radio resources of cell groups respectively configured by a first base station device (first node) and a second base station device (second node). This may be the technology. When DC or MR-DC described later is performed, a cell group may be added to the terminal device from the base station device. To perform DC, the first base station device may add the second base station device. The first base station device may be called the Master Node (MN). Also, the cell group configured by the master node may be called the Master Cell Group (MCG). The second base station device may be called the Secondary Node (SN). Also, the cell group configured by the secondary node may be called the Secondary Cell Group (SCG). Note that the master node and the secondary node may be configured within the same base station device.

[0095] Also, in the case where DC is not set, the cell group set in the terminal device may be called MCG. Also, in the case where DC is not set, the SpCell set in the terminal device may be the PCell. Also, NR without DC set may be called NR Standalone.

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

[0097] 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, one MAC entity for the MCG and one MAC entity for the SCG may exist. The MAC entity for the MCG in the terminal device is used in all states (RRC idle state, RRC connected state, and RRC inactive state). The MAC entity for the SCG in the terminal device may always be established in the terminal device (e.g., in a standby state). The MAC entity for the SCG in the terminal device may be created by the terminal device when the SCG is configured in the terminal device. The MAC entity for each cell group in the terminal device may be configured by the terminal device receiving RRC signaling from the base station device. If the MAC entity is associated with the MCG, the SpCell may refer to the PCell. If the MAC entity is associated with the SCG, the SpCell may refer to the Primary SCG Cell (PSCell). If the MAC entity is not associated with a cell group, the SpCell may refer to the PCell. The PCell, PSCell, and SCell are serving cells. In the EN-DC and the 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 the 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, the MAC entities for the MCG and SCG may both 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. The existence of one MAC entity for each cell group may be rephrased as the existence of one MAC entity for each SpCell.

[0098] When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a radio connection. A radio bearer used for CP may be called a signaling radio bearer (SRB). A radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identity (ID). A radio bearer identifier for an SRB may be called an SRB identity (SRB ID). A radio bearer identifier for a DRB may be called a DRB identity (DRB ID). 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. SRB0 may be an SRB for RRC messages, which are transmitted and / or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before establishment of SRB2. RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. A logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB1. SRB2 may be an SRB for NAS signaling and RRC signaling including logged measurement information. A logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB2. SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and / or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. All RRC and NAS signaling transmitted and / or received using SRB3 may use the logical channel DCCH. Other SRBs may also be provided for other uses. DRBs may be radio bearers for user data.For RRC signaling in which transmission and / or reception is performed using a DRB, the DTCH of the logical channel may be used.

[0099] The radio bearer in the terminal device will be described. The radio bearer may include an RLC bearer. That's fine. The RLC bearer may be composed of one or two RLC entities and a logical channel. The RLC When there are two RLC entities in the RLC bearer, the RLC entities may be a TM RLC entity, and / or a transmission RLC entity and a reception RLC entity in the RLC entity in the unidirectional UM mode. SRB0 may be composed of one RLC bearer. The RLC bearer of SRB0 The RLC entity of the RLC may be composed of the RLC entity of the TM and the logical channel. SRB0 may always be established in the terminal device in all states (such as the RRC idle state, the RRC connected state, and the RRC inactive state). When the terminal device transitions from the RRC idle state to the RRC connected state, one SRB1 may be established and / or configured in the terminal device by the RRC signaling received from the base station device. SRB1 may be composed of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may be composed of the RLC entity of the AM and the logical channel. When the RRC signaling received from the base station device by the terminal device in the RRC connected state where the AS security is activated, one SRB2 may be established and / or configured in the terminal device. SRB2 may be composed of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB2 may be composed of the RLC entity of the AM and the logical channel. Note that the PDCP on the base station device side of SRB1 and SRB2 may be placed in the master node. When the secondary node is added in EN-DC, or NGEN-DC, or NR-DC, or when the secondary node is changed, one SRB3 may be established and / or configured in the terminal device by the RRC signaling received from the base station device by the terminal device in the RRC connected state where the AS security is activated. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may be composed of one PDCP entity and one or more RLC bearers. The RLC bearer of SRB3 may be composed of the RLC entity of the AM and the logical channel. The PDCP on the base station device side of SRB3 may be placed in the secondary node. One or more DRBs may be established and / or configured in the terminal device by the RRC signaling received from the base station device by the terminal device in the RRC connected state where the AS security is activated. DRB may be composed of one PDCP entity and one or more RLC bearers. The RLC bearer of DRB may be composed of the RLC entity of the AM or UM and the logical channel.

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

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

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

[0103] Note that in NR, the DRB established and / or configured in the terminal device may be associated with one PDU session. For one PDU session in the terminal device, one SDAP entity may be established and / or configured. The SDAP entity, PDCP entity, RLC entity, and logical channel established and / or configured in the terminal device may be established and / or configured by the RRC signaling received by the terminal device from the base station device.

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

[0105] Next, the handover in LTE and NR will be described. Handover is a process in which the UE122 in the RRC connected state changes the serving cell from the source SpCell to the target SpCell, and ​A handover may be performed when the UE 122 receives RRC signaling from the eNB 102 and / or the gNB 108 instructing the handover. The RRC signaling instructing the handover may be a reconfiguration of the RRC connection including a parameter instructing the handover (e.g., an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). It may be a message about the settings. This information element may be referred to as the mobility control setting information element, mobility control setting, or mobility control information. The element may be referred to as a synchronized reconfiguration information element or synchronized reconfiguration. Furthermore, the RRC signaling instructing a handover may be a message indicating movement to a cell of another RAT (e.g., MobilityFromEUTRACommand or MobilityFromNRCommand). Furthermore, the handover may be referred to as a synchronized reconfiguration (reconfiguration with sync). Furthermore, the conditions under which the UE 122 can perform a handover may include some or all of the following: AS security is activated, an SRB2 is established, and at least one DRB is established.

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

[0107] In FIG. 4, the base station apparatus creates an RRC message (step S400). The creation of the RRC message in the base station apparatus may be performed for the base station apparatus to distribute system information (SI) or a paging message. Further, the creation of the RRC message in the base station apparatus may be performed to transmit RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on the specific terminal device may include, for example, processing related to security, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, and the like. Further, the creation of the RRC message in the base station apparatus may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, and the like. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be referred to as fields and / or information elements, or may be described using a description method called ASN.1 (Abstract Syntax Notation One). The creation of the RRC message in the base station apparatus may be performed to transmit RRC signaling for causing a specific terminal device to perform processing. The processing to be performed on the specific terminal device may include, for example, processing related to security, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and the like. The RRC connection reconfiguration process may include, for example, control of radio bearers (establishment, change, release, etc.), control of cell groups (establishment, addition, change, release, etc.), measurement settings, handover, security key update, and the like. Further, the creation of the RRC message in the base station apparatus may be performed in response to RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, and the like. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be referred to as fields and / or information elements, or may be described using a description method called ASN.1 (Abstract Syntax Notation One).

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

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

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

[0111] It should be noted that the RRC signal for E-UTRA transmitted from the eNB 102 to the UE 122 is not limited to the case where MR-DC is used. The RRC signaling for NR may be included in the RRC signaling transmitted from the gNB 108 to the UE 122, and the RRC signaling for NR may include the RRC signaling for E-UTRA.

[0112] An example of parameters included in a message related to RRC connection re-establishment is shown below. Figure 7 shows the RRC connection re-establishment message in NR in Figure 4. FIG. 8 shows an example of an ASN.1 description representing fields and / or information elements related to cell group configuration in FIG. 4. ASN.1 notation representing the fields and / or information elements related to cell group configuration contained in the message 7 and 8, as well as in the ASN.1 examples in this embodiment, <omitted> and <omitted> This indicates that some other information is omitted, rather than being part of the ASN.1 notation. Note that information elements may be omitted even where there is no description such as <abbreviation> or <omitted in the middle>. Note that the ASN.1 example in this embodiment does not correctly follow the ASN.1 notation method. The ASN.1 example in this embodiment represents an example of the parameters of the RRC signaling in this embodiment, and other names and other notations may be used. Also, the ASN.1 example shows only examples related to the main information closely related to this embodiment in order to avoid complicated explanations. Note that the parameters described in ASN.1 may all be referred to as information elements without distinguishing them into fields, information elements, etc. Also, in this embodiment, the fields, information elements, etc. described in ASN.1 included in the RRC signaling may be rephrased as information or may be rephrased as parameters. Note that the message related to the reconfiguration of the RRC connection may be the RRC reconfiguration message in NR or the RRC connection reconfiguration message in E-UTRA.

[0113] In FIG. 7, the information element named CellGroupConfig may be an information element used for the configuration, change, release, etc. of the cell group of MCG or SCG in NR. The name CellGroupConfig The information element may include the TCI information element described later. The information element named CellGroupConfig may be referred to as the cell group configuration information element or the cell group configuration. Also, when the information element named CellGroupConfig is used for configuring the cell group of the SCG in NR, this information element named CellGroupConfig may be referred to as the configuration on the SCG side. The information element named SpCellConfig included in the information element named CellGroupConfig may be an information element used for configuring a special cell (SpCell). The information element named SpCellConfig may be referred to as the SpCell configuration information element or the SpCell configuration. The information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element configured in the deactivation of the SCG described later. The information element named DeactivatedSCG-Config-r17 may be referred to as the configuration in the deactivation of the SCG. Note that the information element named DeactivatedSCG-Config-r17 may include a parameter for instructing the terminal device whether to perform the BFD and / or RLM described later on the PSCell in the inactive state of the SCG indicated by bfd-and-RLM. The information element named TCI-Info included in the information element named SpCellConfig may be an information element indicating the TCI state. The information element named TCI-Info may be referred to as the TCI information element. Note that the information element named TCI-Info may also include a parameter of the identifier of the BWP described later indicated by BWP-Id.

[0114] Next, RLM (Radio Link Monitoring) will be described.

[0115] The terminal device performs radio link monitoring using a certain type of reference signal (such as a cell-specific reference signal (CRS)) in the serving cell (such as the PCell and / or the PSCell). In addition, the terminal device may The radio link monitoring unit receives a setting (RadioLinkMonitoringConfig) from the base station device that indicates which reference signal to use for radio link monitoring, and uses one or more of the set reference signals. The terminal device may perform radio link monitoring using a number of reference signals (referred to herein as RLM-RS). The terminal device may also perform radio link monitoring using other signals. The physical layer processing unit of the terminal device performs radio link monitoring in the serving cell (PCell and / or PSCell, etc.). If the conditions for being in synchronization are met, the higher layer may be notified that it is in synchronization.

[0116] 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 SSB-Index of an 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.

[0117] If the terminal device is not provided with an RLM-RS and has one or more CSI-RSs, If the TCI status(es) for transmission are provided, the terminal equipment shall Or do all of them. (A) If the activated TCI state for PDCCH reception includes only one reference signal, the reference signal provided in that activated TCI state is used for radio link monitoring. (B) If the activated TCI state for PDCCH reception includes two reference signals, one reference Expect the QCL type of the signal to be set to Type D, and use the reference signal with QCL type set to Type D for radio link monitoring (do not expect the QCL type of both reference signals to be set to Type D)

[0118] If multiple downlink BWPs (described later) are configured in a serving cell, The terminal device may perform RLM using a reference signal corresponding to the RLM-RS in the Active Downlink BWP described later. If the RLM-RS is not provided in the Active DL BWP described below, the terminal device may perform RLM using the reference signal(s) provided in the activated TCI state for receiving the PDCCH in the CORESET of the Active DL BWP.

[0119] Next, we will explain BFD (Beam Failure Detection).

[0120] In the MAC entity, a beam failure recovery procedure may be configured by RRC for each serving cell. The beam failure recovery procedure may be used to notify the serving gNB (base station device communicating with the terminal device) of a new SSB or CSI-RS when a beam failure is detected on one or more SSBs and / or CSI-RS of the serving cell. Beam failure is detected by counting beam failure instance notifications notified to the MAC entity from the lower layer (PHY layer). In addition, if the SCG is in an inactive state, the MAC entity may perform beam failure detection in the PSCell using a type of reference signal (such as a cell-specific reference signal (CRS)) indicated in the radio link monitoring configuration. The MAC entity may perform some or all of the following (A), (B), and (C) for each serving cell to detect beam failure. stomach. (A) If a beam failure instance notification is received from a lower layer (such as PHY), start or restart the beam failure detection timer (beamFailureDetectionTimer), and increment the beam failure counter (BFI_COUNTER) by 1. If the value of BFI_COUNTER is greater than or equal to the set threshold (beamFailureInstanceMaxCount), perform the following (A-1). (A-1) If the serving cell is an SCell, trigger beam failure recovery (BFR) for this serving cell; otherwise, perform the following (A-2). (A-2) If the serving cell is a PSCell and the SCG is in an inactive state, perform the following (A-3) ; otherwise, start a random access procedure in the SpCell. (A-3) If the beam failure of the PSCell has not been notified to the upper layer since the SCG was deactivated, or if the beam failure in the PSCell has not been notified to the upper layer (such as the RRC entity) since the SCG was last reconfigured with BFD-RS, notify the beam failure in the PSCell to the upper layer (such as the RRC entity). (B) If the beamFailureDetectionTimer for this serving cell has expired, or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the configuration of the reference signal for beam failure detection (BFD-RS) has been changed by the upper layer (such as the RRC entity) , set BFI_COUNTER to 0. (C) If the serving cell is an SpCell and the random access procedure has been successfully completed , set BFI_COUNTER to 0 and the beam failure recovery timer (beamFailureRecoveryTimer) If configured and running, it will be stopped and the beam failure recovery procedure will be completed successfully. Otherwise, if the serving cell is an SCell, and the information for beam failure recovery of the SCell (e.g., the information included in the BFR MAC CE of the SCell or the truncated BFR MAC CE of the SCell) is used, When a PDCCH addressed to the C-RNTI indicating a new uplink grant for transmitting a beamforming notification is received, or if the SCell is in an inactive state, the BFI_COUNTER is set to 0 and the beamforming notification is sent. The failure recovery procedure is considered to have been completed successfully and all beam failure recoveries (BFRs) triggered for this serving cell are cancelled.

[0121] The MAC entity shall perform (A) below if at least one Beam Failure Recovery (BFR) has been triggered by a Beam Failure Recovery procedure and has not been canceled. (A) If the UL-SCH resource can include the BFR MAC CE of the SCell and its subheader after considering the priority of the logical channel, 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 channels, If so, include the truncated BFR MAC CE of the SCell and its subheader; otherwise If so, it triggers a scheduling request for SCell beam failure recovery.

[0122] Here, we will explain the beamFailureRecoveryTimer. When a random access procedure is initiated for BFR of the SpCell and the beam failure recovery configuration (beamFailureRecoveryConfig) is set to Active UL BWP, the MAC entity may start the beamFailureRecoveryTimer. Also, if the beamFailureRecoveryTimer is running or not configured, the terminal device may use contention-free random access (CFRA) for BFR. Also, if the beamFailureRecoveryTimer has expired or is not running, the terminal device may not use CFRA for BFR and may instead use, for example, CBRA.

[0123] A terminal device may be provided with a set of one or more reference signals for detecting beam failure and / or radio link failure (BFD-RS, described below) for detecting beam failure and / or radio link failure in each BWP in one serving cell. The BFD-RS may be a periodic CSI-RS or another reference signal. A PHY of the terminal device may assess radio link quality based on the set of BFD-RS. The PHY may also provide a notification to a higher layer (e.g., MAC) if the measured radio link quality becomes worse than a threshold (rlmInSyncOutOfSyncThreshold) set by a higher layer (e.g., RRC).

[0124] Describe the activation and deactivation of cells. In a terminal device communicating with Dual Connectivity, the configuration of the master cell group (MCG) and the secondary cell group (SCG) are set by the message regarding the reconfiguration of the aforementioned 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 the PCell. The SpCell of the SCG is also referred to as the PSCell. The deactivation of a cell is not applied to the SpCell and may be applied to the SCell.

[0125] Also, the deactivation of a cell is not applied to the PCell and may be applied to the PSCell. In this case, the deactivation of a cell may be different processing for the SpCell and the SCell.

[0126] The activation and deactivation of cells may be processed by the MAC entity existing for each cell group. The SCell set in the terminal device may be activated and / or deactivated by a part or all of the following (A) to (C). (A) Reception of a MAC CE for activating / deactivating the SCell (B) SCell Inactivity Timer set for each SCell where PUCCH is not set (C) RRC parameter (sCellState) set for each SCell set in the terminal device

[0127] Specifically, the MAC entity of the terminal device may perform the following processing (AD) for each SCell set in the cell group.

[0128] (Processing AD) If, when configuring the SCell, the RRC parameter (sCellState) configured for the SCell is set to activated, or if the UE 122's MAC entity receives a MAC CE for activating the SCell, the MAC entity of the UE 122 performs process (AD-1). Otherwise, if the UE 122's MAC entity receives a MAC CE for deactivating the SCell, or if the SCell Inactivity Timer expires for an active SCell, the MAC entity of the UE 122 performs process (AD-2). If an uplink grant or a downlink assignment is signaled by the PDCCH of an active SCell, or if an uplink grant or a downlink assignment for an active SCell is signaled by the PDCCH of a serving cell through, or if a MAC PDU is transmitted in the configured uplink grant, or if a MAC PDU is received in the configured downlink assignment, the MAC entity of the UE 122 restarts the SCell Inactivity Timer associated with that SCell. If the SCell becomes inactive, the MAC entity of the UE 122 performs process (AD-3). (Process AD-1)

[0129] (Process AD-1) If, in NR, the SCell was in an inactive state before receiving a MAC CE for activating this SCell, or if the RRC parameter (sCellState) configured for this SCell at the time of SCell configuration is set to activated, the MAC entity of the UE 122 performs process (AD-1A) or process (AD-1B). Also, the MAC entity of the UE 122 starts, or (if already started) restarts, the SCell Inactivity Timer associated with that SCell. If the Active DL BWP is not the Dormant BWP described below, the MAC entity of the UE 122 UE122 performs some or all of the following from (A) to (B). (A) If any, according to the stored configuration, re-initialize all configured suspended grant type 1 uplink links associated with this SCell. (B) Trigger a PHR. (C) If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is not set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1A). If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs some or all of the following from (A) to (B). (A) Activate the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling. (B) Activate the BWP indicated by the firstActiveUplinkBWP-Id configured by RRC signaling. (Process AD-1A) The MAC entity of UE122 activates the SCell and performs some or all of the following from (A) to (E). (A) Transmit a sounding reference signal (SRS) on this SCell. (B) Report CSI for this SCell.

[0130] (C) If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is not set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1A). If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs some or all of the following from (A) to (B). (A) Activate the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling. (B) Activate the BWP indicated by the firstActiveUplinkBWP-Id configured by RRC signaling. (D) Transmit a sounding reference signal (SRS) on this SCell. (E) Report CSI for this SCell. (F) If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is not set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1A). If a MAC CE for activating the SCell is received and the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is set as a Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs some or all of the following from (A) to (B). (A) Activate the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling. (B) Activate the BWP indicated by the firstActiveUplinkBWP-Id configured by RRC signaling. (Process AD-1B) (C) Monitor the PDCCH of this SCell. (D) Monitor the PDCCH for this SCell. (When scheduling for this SCell is performed in another serving cell) (E) If PUCCH is configured, transmit PUCCH on this SCell.

[0131] (Procedure AD-1B) The MAC entity of UE122 stops if the BWP inactivity timer of this serving cell is running. Otherwise.

[0132] (Procedure AD-2) The MAC entity of UE122 performs some or all of the following (A) to (F). (A) Inactivate this SCell. (B) Stop the SCell inactivity timer associated with this SCell. (C) Inactivate all Active BWPs associated with this SCell. (D) Clear all configured downlink allocations and / or all grant type 2 configured uplink grants associated with this SCell. (E) Suspend all grant type 1 configured uplink grants associated with this SCell. (F) Flush the HARQ buffer associated with this SCell.

[0133] (Procedure AD-3) The MAC entity of UE122 performs 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.

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

[0135] Also, as mentioned above, when an SCell is added, the initial state of the SCell is updated by RRC signaling. A state may be set.

[0136] Here, the SCell inactivity timer is explained. For SCells where PUCCH is not configured The SCell inactivity timer value (the time at which the timer is considered to have expired) is updated by RRC signaling. For example, the SCell inactivity time may be notified by RRC signaling. If information indicating 40 ms as the value of the timer is notified, in the above process (AD), the timer is considered to have expired when the notified time (here, 40 ms) has passed without the timer being stopped after the timer was started or restarted. The mer may be a timer named sCellDeactivationTimer.

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

[0138] The BWP may be a part or all of the band of the serving cell. The BWP may also be called a carrier BWP. One or more BWPs may be set in the terminal device. A BWP is system information associated with a synchronization signal detected in the initial cell search. A BWP may be set by the information included in the initial cell search. A BWP may be a frequency bandwidth associated with a frequency. For example, it may be set by dedicated RRC signaling. Also, the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be set individually. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. Also, the association between the uplink BWP and the downlink BWP may be a default association, or an association by RRC signaling (e.g., dedicated RRC signaling), or an association by physical layer signaling (e.g., association by downlink control information (DCI) notified by a downlink control channel), or a combination

[0139] thereof. Also, in the downlink BWP, a CORESET may be set. The BWP may be composed of a group of consecutive physical resource blocks The terminal may include some or all of the following information: (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (e.g., the starting position on the low-frequency side or the center frequency position of the BWP) (the frequency position may be represented by, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. The unit of the offset may be in subcarriers or resource blocks. Both the ARFCN and the offset may be set.), (D) the bandwidth of the BWP (e.g., the number of PRBs), (E) the resource setting information of the control signal, (F) the center frequency position of the SS block (the frequency position may be represented by, for example, an ARFCN, or an offset from a specific subcarrier of the serving cell. The unit of the offset may be in subcarriers or resource blocks. Both the ARFCN and the offset may be set.). Also, the resource setting information of the control signal may be included in the setting of at least a part or all of the BWPs of the PCell and / or PSCell.

[0140] Among one or more configured BWPs, the terminal may perform transmission and reception on the Active BWP (active BWP). One or more BWPs may be configured for one serving cell associated with the terminal. Among one or more BWPs configured for one serving cell associated with the terminal, at a certain time, at most one uplink BWP and / or at most one downlink BWP may be set as the Active BWP. The Active BWP in the downlink may also be referred to as the Active DL BWP. The Active BWP in the uplink may also be referred to as the Active UL BWP. Also, among the one or more configured BWPs of the terminal, the BWP that is not the Active BWP may be referred to as the Inactive BWP (inactive BWP).

[0141] Next, we will explain the activation / deactivation of BWPs. Activating a BWP may mean activating a BWP or activating an inactive BWP. Deactivating a BWP may mean deactivating a BWP or deactivating an active BWP. BWP switching in the serving cell is used to activate an inactive BWP and deactivate an active BWP.

[0142] BWP switching is performed by the PDCCH, which indicates a downlink assignment or an uplink grant, and the BWP deactivation. The Active BWP of the serving cell is indicated by the RRC or PDCCH.

[0143] 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 (A). The BWP inactivity timer may also be a timer named bwp-InactivityTimer. (A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, Therefore, 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, 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 (B) and (D). (B) 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 in a configured uplink grant or a MAC PDU is received in a configured downlink assignment, the MAC entity performs the following (C). (C) 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 has been successfully completed by the reception of a PDCCH addressed to the C-RNTI. Then, start or restart the BWP inactivity timer associated with the Active DL BWP. (D) If the BWP inactivity timer associated with an Active DL BWP expires The MAC entity performs the following (E). (E) If a defaultDownlinkBWP-Id is set, this defaultDownlinkBWP-Id If not, switch to initialDownlinkBWP. Make the switch.

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

[0145] In each activated serving cell where a BWP is configured, the MAC entity, if the BWP is activated (is an Active BWP) and the Active DL BWP in that serving cell is not a dormant BWP, performs some or all of the following (A) to (H). (A) Transmit UL-SCH on that BWP. (B) If a PRACH occasion is configured, transmit RACH on that BWP. (C) Monitor PDCCH on that BWP. (D) If PUCCH is configured, transmit PUCCH on that BWP. (E) Report CSI on that BWP. (F) If SRS is configured, transmit SRS on that BWP. (G) Receive DL-SCH on that BWP. (H) If any, according to the stored configuration, all configured uplink grant type 1 suspended link grants set on that Active BWP are (re-)initialized.

[0146] The MAC entity, if the BWP is deactivated, performs some or all of the following (A) to (I). (A) Do not transmit UL-SCH on that BWP. (B) Do not transmit RACH on that BWP. (C) Do not monitor PDCCH on that BWP. (D) Do not transmit PUCCH on that BWP. (E) Do not report CSI on that BWP. (F) Do not transmit SRS on that BWP. (G) Do not receive DL-SCH on that BWP. (H) Clear all configured downlink allocations and / or all configured grant type 2 configured uplink grants set on that BWP. (I) Suspend all grant type 1 configured uplink grants of that Inactive BWP.

[0147] Here, the parameter (timeAlignmentTimer) configured by RRC to maintain time alignment in the uplink (UL) is described.

[0148] timeAlignmentTimer may be configured for each TAG. Also, timeAlignmentTimer may control the period that the MAC entity considers when the serving cells belonging to the associated TAG are synchronized in UL time. timeAlignmentTimer is also referred to as TAT.

[0149] When the timeAlignmentTimer associated with the PTAG expires, the MAC entity performs some or all of the following (A) to (E). (PT) (A) Flash the HARQ buffer for all serving cells belonging to the PTAG. . (B) If any, notify RRC to release the PUCCH for all serving cells belonging to the PTAG. (C) If any, notify RRC to release the SRS for all serving cells belonging to the PTAG. (D) Clear all configured downlink assignments and / or all configured uplink grants. (E) Consider all running timeAlignmentTimers to have expired.

[0150] When the timeAlignmentTimer associated with a STAG expires, the MAC entity performs some or all of the following (A) through (D) for all serving cells belonging to this STAG. (A) Flush the HARQ buffer. (B) Notify RRC to release PUCCH, if any. (C) Notify the RRC to release the SRS, if any. (D) Clear all configured downlink assignments and / or all configured uplink grants.

[0151] Next, deactivation and activation of SCG will be explained.

[0152] Inactivation of SCG may mean inactivating SCG. is a MAC entity associated with an SCG and corresponding to said MAC entity Inactivating an SCG may mean inactivating a cell group. Inactivating an SCG may mean inactivating a PSCell (SpCell of an SCG) or inactivating a PSCell. Activating an SCG may mean activating an SCG. Inactivating an SCG may mean activating a cell group that corresponds to a MAC entity associated with the SCG. Inactivating an SCG may mean activating a PSCell (SpCell of an SCG) or activating a PSCell.

[0153] In LTE and / or NR, the inactive state of the SCG may be a state in which the terminal device performs some or all of the following (A) to (P) in the PSCell (SpCell) of the SCG. Also, the inactive state of the SCG may mean a state in which the SCG is deactivated (a state in which the SCG is in a dormant state). (SD-1) (A) Do not transmit SRS in this PSCell. (B) Do not measure CSI for this PSCell. (C) Do not report CSI for this PSCell. (D) Do not transmit PUCCH in this PSCell. (E) Do not transmit UL-SCH in this PSCell. (F) Do not transmit RACH in this PSCell. (G) Do not monitor the PDCCH of this PSCell. (H) Do not monitor the PDCCH for this PSCell. (I) If any, switch to the BWP indicated by the firstActiveDownlinkBWP-Id in this PSCell. (J) Perform discontinuous reception (DRX) in this PSCell. (K) Do not monitor the PDCCH of this PSCell, and / or the PDCCH for this PSCell, addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating the uplink grant for UL-SCH transmission in this PSCell. (L) The BWP is activated in this PSCell, and in the above-mentioned BWP, the PDCCH of this PSCell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating the uplink grant and / or the PDCCH for this PSCell are not monitored. (M) In this PSCell, including automatic gain control (AGC) and beam failure recovery Beam Failure Detection (BFD) and / or Radio Link Monitoring Radio Link Monitoring (RLM) is performed. (N) Suspend some or all configured uplink grants of grant type 1 associated with this PSCell. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this PSCell. do. (P) Causes the MAC entity on the SCG side to perform a partial MAC reset. do.

[0154] The (M) in (SD-1) above is based on the bfd-and-RLM parameter included in the SCG settings. may be implemented.

[0155] (P) of the above (SD-1) may include some or all of (A) to (O) of the above (SD-1). In addition, (P) in the above (SD-1) may include some or all of the following (P-1) to (P-15). (P-1) A parameter Bj set for each logical channel is initialized to 0. (P-2) All timers associated with the PSCell, except for the timer used to perform BFD (beamFailureDetectionTimer) and the timeAlignmentTimer (TAT), are stopped if they are running. (P-3) Set the New Data Indicator (NDI) value of all uplink HARQ processes to 0. do. (P-4) Stop any ongoing random access procedures. (P-5) If any, discard the resources for 4-step and 2-step RA type contention-free Random Access (CFRA) that have been explicitly signalled. (P-6) Flash the buffer for Msg3. (P-7) Flash the buffer for MSGA. (P-8) If any, cancel the triggered SR procedure. (P-9) If any, cancel the triggered BSR procedure. (P-10) If any, cancel the triggered PHR procedure. (P-11) If any, cancel the confirmation of the triggered configured uplink grant. (P-12) Flash the soft buffers of all downlink HARQ processes. (P-13) In each downlink HARQ process, consider the next received transmission for a certain transport block (TB) as the very first transmission. (P-14) If any, release the Temporary C-RNTI. (P-15) Reset all BFI_COUNTERs except the BFI_COUNTER used for BFD associated with the PSCell.

[0156] In LTE and / or NR, the active state of the SCG may be a state in which the terminal device performs some or all of (A) to (O) below in the PSCell (SpCell) of the SCG. Also, the active state of the SCG may mean a state in which the SCG is activated (the SCG is not in a dormant state). (SA-1) (A) Transmit SRS on this PSCell. (B) Measure CSI for this PSCell. (C) Report CSI for this PSCell. (D) Transmit PUCCH on this PSCell. (E) Transmit UL-SCH on this PSCell. (F) Transmit RACH on this PSCell. (G) Monitor the PDCCH of this PSCell. (H) Monitor the PDCCH for this PSCell. (I) If any, switch to the BWP indicated by the firstActiveDownlinkBWP-Id in this PSCell. (J) Perform discontinuous reception (DRX) on this PSCell. (K) Monitor the PDCCH of this PSCell, and / or the PDCCH for this PSCell, addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating the uplink grant for UL-SCH transmission on this PSCell. (L) The BWP is activated on this PSCell, and the PDCCH of this PSCell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating the uplink grant in the above-mentioned BWP and / or the PDCCH for this PSCell are monitored. (M) Perform Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and / or Radio Link Monitoring (RLM) on this PSCell. including beam failure recovery on this PSCell. (N) If any, according to the stored configuration, part or all of the suspended configurations of grant type 1 associated with this PSCell are Re-initialize the uplink grant on the Ard. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) that includes this PSCell. Do.

[0157] In LTE and / or NR, the terminal device may determine that the SCG is in an inactive state based on some or all of the following (A) to (H). Note that the signaling and control elements in the following (A) to (F) may be notified from the base station device to the terminal device via the SCG. In addition or instead of that, the signaling and control elements in the following (A) to (F) may be notified from the base station device to the terminal device via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). Do. (SD-2) (A) Reception of RRC signaling instructing to deactivate the SCG (B) Reception of MAC CE instructing to deactivate the SCG (C) Reception of RRC signaling instructing to deactivate the PSCell (D) Reception of MAC CE instructing to deactivate the PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) Expiration of the SCG inactivation timer (H) Expiration of the PSCell inactivation timer

[0158] The RRC signaling in (A), (C), and (E) of the above (SD-2) may include a parameter such as scg-State, for example. By including scg-State in the RRC signaling, the SCG becomes inactive. When scg-State is included in the RRC signaling, the SCG becomes inactive. The scg-State may be included in the RRC signaling to indicate that the SCG is activated. The scg-State may not be included in the RRC signaling to indicate that the SCG is activated. The RRC signaling may include an instruction to activate the SCG, meaning that the RRC signaling does not include an instruction to deactivate the SCG. The RRC signaling may not include an instruction to deactivate the SCG, meaning that the scg-State parameter is not included in the RRC signaling. The scg-State parameter may be included in the RRC signaling to indicate that the SCG is deactivated. Furthermore, the scg-State parameter may be information indicating the deactivation of the SCG. Furthermore, the scg-State may be included in an RRC reconfiguration message or an RRC resumption message. Furthermore, the RRC signaling may be generated by the MN.

[0159] FIG. 11 is a diagram showing an example of an embodiment. In FIG. 11, the processing unit 502 of the UE 122 determines that the SCG is in an inactive state based on the above (SD-2) (step S1100). Furthermore, the processing unit 502 of the UE 122 deactivates the SCG based on the determination, and performs the above-mentioned processing in the inactive state of the SCG. The operation shown in (SD-1) above is performed (step S1102).

[0160] In LTE and / or NR, a terminal device may determine that an SCG is active based on some or all of the following (A) to (K). Note that the signaling and control (A) to (F) below may also be used. The control element may be notified from the base station device to the terminal device via the SCG. Alternatively, the signaling and control elements (A) through (F) below may be transmitted to a cell group other than the SCG in question. The SCG may be notified from the base station device to the terminal device via a loop (MCG, an SCG other than the SCG, etc.). The SCG being in an active state may mean that the SCG is not in an inactive state. (SA-2) (A) Receipt of RRC signaling instructing the SCG to activate. (B) Receipt of MAC CE instructing the activation of SCG. (C) Receipt of RRC signaling instructing activation of PSCell (D) Receipt of MAC CE instructing to activate PSCell (E) Receiving other RRC signaling (F) Receiving other MAC CEs (G) SCG inactivity timer (H) PSCell inactivity timer (I) A scheduling request triggered to transmit a MAC PDU containing a MAC SDU. Initiation of a random access procedure due to an EST (J) Initiation of random access procedure (K) due to a scheduling request (in other words, the MAC entity itself Initiation of the random access procedure

[0161] The RRC signaling in (A), (C), and (E) in (SA-2) above is implemented using a parameter called scg-State. data may not be included in the RRC reconfiguration message and / or the RRC restart message. Also, the RRC signaling may be generated in the MN.

[0162] 10 is a diagram showing an example of an embodiment. In FIG. 10, the processing unit 502 of the UE 122 determines that the SCG is in an active state based on the above (SA-2) (step S1000). Based on the determination, the unit 502 activates the SCG and performs the operation as shown in (SA-1) above when the SCG is in an active state (step S1002).

[0163] A terminal device that deactivates an SCG may perform some or all of the following (A) to (I) in the SCG. (SD-3) (A) Consider that SCG is inactivated. (B) Instruct the lower layer (such as the MAC entity) to deactivate the SCG. (C) If the terminal device is in the RRC_CONNECTED state and the system If the SCG was activated before receiving an RRC reconfiguration message or an RRC connection reconfiguration message, and if an SRB3 was configured before receiving an RRC reconfiguration message or an RRC connection reconfiguration message, and the SRB3 is not released in accordance with the RRC signaling for any radio bearer configuration (RadioBearerConfig) included in the RRC reconfiguration message or the RRC connection reconfiguration message, the SCG triggers the PDCP entity of the SRB3 to discard SDUs, and additionally or alternatively, re-establishes the RLC entity of the SRB3. (D) Deactivate all SCells. (E) All SCell inactivity timers associated with the active SCell are considered to have expired. Eggplant. (F) All SCell inactivity timers associated with the dormant SCell are considered to have expired. Eggplant. (G) Start or restart the SCell inactivity timers associated with all SCells. Not available. (H) Ignore the MAC CE that activates the SCell. For example, in the process (AD), When a MAC CE to activate the SCG is received and an instruction to deactivate the SCG has not been issued (or the SCG is not in an inactive state), processing (AD-1) is performed. (I) Execute the process (AD-2). For example, when the process (AD) is instructed to inactivate SCG (or when SCG becomes inactive), the process (AD-2) is executed.

[0164] If a higher layer (such as an RRC entity) instructs the MAC entity to deactivate an SCG based on (B) of (SD-3) above, the MAC entity of the terminal device may deactivate all SCells of the SCG, and in addition or instead may deactivate the PSCell based on (SD-1) above.

[0165] A terminal device that activates an SCG may implement some or all of the following (A) to (D) in the SCG. (SA-3) (A) Consider that SCG is activated. (B) If an inactive SCG has been configured before the terminal device receives signaling instructing it to activate the SCG, it shall instruct the lower layer (e.g., MAC entity) to activate the SCG. Instruct the operator to do so. (C) To activate all SCells, process (AD-1) is performed. (D) When SCG activation is performed based on RRC signaling, if this RRC signaling includes parameters related to random access to a PSCell (SpCell), a random access procedure is initiated in this PSCell based on the notified parameters.

[0166] When an upper layer (such as an RRC entity) instructs the MAC entity to activate the SCG based on (B) of (SA-3) above, the MAC entity of the terminal device shall SCG may be activated based on

[0167] If the terminal device determines that the SCG is active based on (SA-2) above, the terminal device The RRC entity of the Instructs the SCG to initiate a random access procedure in the PSCell of the SCG. You may.

[0168] (A) EN-DC or NGEN-DC is configured in the terminal device, an RRC reconfiguration message is received via E-UTRA SRB1 or an E-UTRA RRC connection reconfiguration message (handover from NR standalone to (NG)EN-DC), the SCG is not deactivated according to E-UTRA RRC signaling containing an RRC reconfiguration message for SCG side configuration in the form of a container, and the following (A-1) or (A-2) is met:

[0169] (A-1) Synchronous reconfiguration was included in the SpCell configuration of the SCG. (A-2) Before receiving E-UTRA RRC signaling containing an RRC reconfiguration message for SCG side configuration in the form of a container as described in (A-2)(A), the SCG is deactivated, and at least one of the following (A-2-1) to (A-2-4) is satisfied:

[0170] (A-2-1) A radio link failure is detected in the SCG. (A-2-2) The PSCell of the inactivated SCG is configured to perform RLM, and Another indication (indication#A) is sent from a lower layer (such as a MAC entity). (A-2-3) A special notification (indication #B) is sent from a lower layer (such as a MAC entity). (A-2-4) PSCs in inactivated SCGs are not configured to perform RLM.

[0171] The above (A-2-2) may be replaced with the following (A-2-2'): (A-2-2') A special notification (indication #A) is sent from a lower layer (such as a MAC entity).

[0172] The above (A-2-3) may be replaced with the following (A-2-3'): (A-2-3’) A special indication (indication#B) is notified from a lower layer (such as a MAC entity), and the indication#B has not been cancelled.

[0173] (B) NR-DC is set in the terminal device, an RRC reconfiguration message is received via SRB1 of the SCG, and an RRC signaling of NR including the RRC reconfiguration message for the SCG side settings in the form of a container According to the ring, the SCG is not deactivated and satisfies the following (B-1) or (B-2) .

[0174] (B-1) Synchronization reconfiguration was included in the SpCell configuration of the SCG. (B-2) Before receiving the RRC signaling of NR including the RRC reconfiguration message for the SCG side settings described in (B) in the form of a container, the SCG is deactivated and satisfies at least one of the above (A-2-1) to (A-2-4).

[0175] Whether it is set to perform RLM on the PSCell of the deactivated SCG may be set by the parameter "bfd-and-RLM" in FIG. 7. In other words, the above-mentioned being set to perform RLM on the PSCell of the deactivated SCG means that the parameter indicates performing RLM on the PSCell, or the parameter may be included in the SCG-side settings. Also, the above-mentioned not being set to perform RLM on the PSCell of the deactivated SCG means that the parameter indicates not performing RLM on the PSCell, or the parameter may not be included in the SCG-side settings. Also, whether it is set to perform BFD on the PSCell of the deactivated SCG may be set by the parameter "bfd-and-RLM" in FIG. 7. In other words, the above-mentioned being set to perform BFD on the PSCell of the deactivated SCG means that the parameter indicates performing BFD on the PSCell, or the parameter may be included in the SCG-side settings. Also, not being set to perform BFD on the PSCell of the deactivated SCG means that the parameter indicates not performing BFD on the PSCell, or the parameter may not be included in the SCG-side settings. Also, whether it is set to perform RLM on the PSCell of the deactivated SCG and whether it is set to perform BFD on the PSCell may be set independently of each other. Also, the value of the parameter being set to True may mean that it is set to perform RLM and BFD on the PSCell of the deactivated SCG, and the value of the parameter being set to false may mean that it is not set to perform RLM and BFD on the PSCell of the deactivated SCG.

[0176] FIG. 9 is a diagram showing an example of an embodiment. In FIG. 9, UE 122 is either eNB 102 or gNB 108 Receive signaling (such as RRC signaling, MAC CE, etc.) that instructs to deactivate the SCG (step S900). Based on the above notification, UE122 controls some or all of the cells of the SCG to be in an inactive state (step S902).

[0177] By the above operations, in the process of deactivating the SCG, the transmitting unit 504 of UE122 can perform an efficient state change without independently transmitting a MAC CE for changing the state of the cells of the SCG to an inactive state. Also, when the deactivation of the SCG is executed based on RRC signaling, conventionally, the initial state was set in the RRC layer and the state change was performed in the MAC layer. However, by the above operations, it is possible to efficiently change the state of the SCG while avoiding a mismatch between the RRC layer instruction and the MAC layer instruction.

[0178] Based on the above description, various embodiments will be described. Note that the above-described various processes may be applied to each process omitted in the following description.

[0179] FIG. 5 is a block diagram showing the configuration of the terminal device (UE122) in the present embodiment. In order to avoid complicating the description, FIG. 5 shows the main components related closely to the present embodiment.

[0180] The UE122 shown in FIG. 5 includes a receiving unit 500 that receives control information (such as DCI, RRC signaling, etc.) from the base station device, a processing unit 502 that performs processing according to parameters included in the received control information, and a transmitting unit 504 that transmits control information (such as UCI, RRC signaling, etc.) to the base station device. This is the case. The above base station device may be the eNB 102 or the gNB 108. Further, the processing unit 502 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit.

[0181] [[ID=**4**]]Figure 6 is a block diagram showing the configuration of the base station device in the present embodiment. Note that, to avoid complication of the description, only the main components closely related to the present embodiment are shown in Figure 6. The above base station device may be the eNB 102 or the gNB 108. To avoid complication of the description, only the main components closely related to the present embodiment are shown in Figure 6. The above base station device may be the eNB 102 or the gNB 108. The above base station device may be the eNB 102 or the gNB 108.

[0182] The base station device shown in Figure 6 includes a transmission unit 600 that transmits control information (DCI, RRC signaling, etc.) to the UE 122, and a processing unit 602 that creates control information (DCI, RRC signaling including parameters, etc.) and causes the processing unit 502 of the UE 122 to perform processing by transmitting it to the UE 12, and a reception unit 604 that receives control information (UCI, RRC signaling, etc.) from the UE 122. Further, the processing unit 602 may include some or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. That is, the processing unit 602 may include some or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit.

[0183] An example of the processing of the terminal device in the present embodiment will be described with reference to Figure 10.

[0184] FIG. 10 is a diagram showing an example of processing of a terminal device in this embodiment. The processing unit 502 of the UE 122 may determine that the SCG is in an active state based on the above (SA-2) (step S1000). Furthermore, the processing unit 502 of the UE 122 may perform an operation in an active state based on the determination (step S1001). Step S1002).

[0185] An example of the operation of the UE 122 in the above-mentioned active state will be described. In the active state, the UE 122 may perform some or all of the processes shown in (SA-1) above in each of the PSCell and / or one or more SCells of a certain cell group.

[0186] The active state may be a state in which the SCG is activated. The active state may also be a state in which the SCG has resumed from a dormant state. The active state may also be a state in which the SCG has resumed from a dormant state. The active state may be a state in which the MAC SDU is not in a dormant state. The active state may be a state to which the MAC SDU transitions from the inactive state when a random access procedure is initiated due to a scheduling request triggered to transmit a MAC PDU containing the MAC SDU. The active state may be a state to which the MAC SDU transitions from the inactive state when a wake-up instruction from the RRC entity is received.

[0187] In step S1000, processing unit 502 of UE 122 may determine that the SCG has transitioned from an inactive state to an active state, as shown in (SA-2) above.

[0188] When the UE 122 receives the instruction to activate the SCG, the UE 122 transitions the SCG from an inactive state to an active state. In other words, SCG may be activated. When it receives information instructing it to resume from the inactive state, it transitions the SCG from the inactive state to the active state. It may also be possible. Further, when the UE 122 receives information instructing the return from the dormant state of the PSCell , it may transition the SCG from the inactive state to the active state. Further, when the UE 122 receives other information, it may transition the SCG from the inactive state to the active state. Further, the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the sleep of the SCG. Also , the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the sleep of the PSCell. Further, when the UE 122 starts a random access procedure due to a scheduled request triggered for transmitting a MAC PDU containing a MAC SDU , it may transition the SCG from the inactive state to the active state. Also, when the UE 122 starts a random access procedure, it may transition the SCG from the inactive state to the active state. Also, when the UE 122 starts a random access procedure triggered by a scheduling request (in other words, started by the MAC entity itself), it may transition the SCG from the inactive state to the active state. Further, the MAC entity of the UE 122 may obtain an instruction to activate the SCG, an instruction for the return from the dormant SCG, an instruction for the return from the dormant state of the PSCell, and / or other information from the RRC entity of the UE 122. Also, after the MAC entity of the UE 122 obtains the above information from the RRC entity, as shown in (SA-2) above, the UE 122 may determine that the SCG is in the active state and transition the SCG from the inactive state to the active state. When transitioning the SCG from the inactive state to the active state, the UE 122 may perform processing as shown in (SA-3) above.

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

[0190] FIG. 11 is a diagram showing an example of the processing of the terminal device in the present embodiment. The processing unit 502 of the UE122 may determine that the SCG is in an inactive state based on the above (SD-2) (step S1100). Further, the processing unit 502 of the UE122 may perform operations in the inactive state based on the determination (step S1102).

[0191] An example of the operation of the UE122 in the above inactive state will be described. In the inactive state, the UE122 may perform some or all of the processes as shown in the above (SD-1) in each of the PSCell and / or one or more SCell of a certain cell group.

[0192] The inactive state may be a state in which the SCG is deactivated. Further, the above inactive state may be an entry (Entering) into the dormant SCG. Further, the above inactive state may be the dormant state of the above SCG. Further, the inactive state may be a state in which the Active BWP of the PSCell and / or one or more SCell of the SCG is the dormant BWP. Further, the above inactive state may be a state that transitions from the active state when an entry from the RRC entity to the dormant state is instructed.

[0193] In step S1100, the processing unit 502 of the UE122 may determine that the SCG has transitioned from the active state to the inactive state as shown in the above (SD-2).

[0194] When the UE122 receives information instructing the deactivation of the SCG, it may transition the SCG from the active state to the inactive state. Further, when the UE122 receives information instructing the entry (Entering) into the dormant SCG, it may transition the SCG from the active state to the inactive state. Further, when the UE122 receives information instructing the dormancy of the PSCell, it may transition the SCG from the active state to the inactive state. Also In addition, the UE 122 may transition the SCG from the active state to the inactive state when receiving other information. In addition, the UE 122 may transition the SCG from the active state to the inactive state when a timer related to the SCG dormancy expires. In addition, the UE 122 may transition the PSCell to the inactive state when the timer related to the PSCell dormancy expires. When the SCG is completed, the SCG may be transitioned from the active state to the inactive state. The MAC entity may obtain an instruction to deactivate the SCG, an instruction to enter a dormant SCG, an instruction to put a PSCell into dormancy, and / or other information from the RRC entity of UE 122. After the MAC entity obtains the information from the RRC entity, UE 122 may determine that the SCG is in an inactive state as described above in (SD-2) and transition the SCG from an active state to an inactive state. UE 122 may perform the process described above in (SD-3) when transitioning the SCG from an active state to an inactive state.

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

[0196] 12 is a diagram showing an example of processing by a terminal device in this embodiment. The processing unit 502 of the UE 122, which has been configured to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the transmission unit 600 of the gNB 108, determines the conditions (step S1200) and operates based on the determination (step S1202).

[0197] In step S1200, the UE 122 may determine whether one or both of the following conditions (1) and (2) are satisfied. (1) (a) The beam failure detection timer expires, and (c) BFD is not stopped. (2)(b) The beam failure detection timer, the beam failure counter threshold, or any BFD-RS is reconfigured by a higher layer.

[0198] In step S1200, when UE122 determines that either or both of the conditions (1) and (2) are satisfied, in step S1202, UE122 may set the beam failure counter to 0. In step S1200, when UE122 determines that neither of the conditions (1) and (2) is satisfied, in step S1202, the UE does not have to set the beam failure counter to 0. "Setting the beam failure counter to 0" may also be paraphrased as "resetting the beam failure counter", and "not setting the beam failure counter to 0" may also be paraphrased as "not resetting the beam failure counter". It is not necessary to set it to 0. "Setting the beam failure counter to 0" may also be paraphrased as "resetting the beam failure counter", and "not setting the beam failure counter to 0" may also be paraphrased as "not resetting the beam failure counter".

[0199] The condition (c) may also be paraphrased into an expression meaning that BFD is not stopped. For example, it may be replaced with expressions such as "BFD is being performed", "not notifying the upper layer that there is a beam failure", "after notifying the upper layer that there is a beam failure for the last time and then BFD is resumed", "not notifying the lower layer to stop BFD", "after notifying the lower layer to stop BFD for the last time and then BFD is resumed", etc. Also, the expression "BFD is resumed" may be paraphrased with other similar expressions. For example, it may be paraphrased with expressions such as "notified by the upper layer to perform BFD", "BFD-RS is changed", "notified the lower layer to perform BFD", etc.

[0200] Also, another example of the processing of the terminal device in this embodiment will be described with reference to FIG. 12. The processing unit 502 of UE122, which is set to perform BFD on the PSCell of the deactivated SCG by the RRC signaling received from the transmission unit 600 of gNB108, makes a condition determination (step S1200) and operates based on the determination (step S1202).

[0201] UE122 may determine whether the condition is satisfied in step S1200. The condition may be one or a combination of the following conditions. (a) Notified the upper layer that there is a beam failure. (b) Notified by the upper layer to stop BFD. (c) Notified the lower layer to stop BFD.

[0202] In step S1200, if UE122 determines that the condition is satisfied, in step S1202, UE122 may stop the beam failure detection timer. In step S1200, if UE122 determines that the condition is not satisfied, in step S1202, the UE may not stop the beam failure detection timer.

[0203] The condition (a) may be replaced with a condition for notifying the upper layer that there is a beam failure. For example, it may be a combination of multiple conditions among the following conditions. (a-1) Received a beam failure instance notification from the lower layer. (a-2) The beam failure counter is equal to or greater than the beam failure counter threshold. (a-3) The serving cell is the PSCell and the SCG is deactivated. (a-4) After the SCG is deactivated, the upper layer has not been notified of the beam failure of the PSCell, or after the SCG was last reset with BFD-RS, the upper layer has not been notified of the beam failure of the PSCell. (a-5) After the SCG is deactivated, the upper layer has not been notified of the beam failure of the PSCell, or after the SCG was last reset with bfd-and-RLM, the upper layer has not been notified of the beam failure of the PSCell. (a-6) BFD is not stopped. (a-7) BFD is not stopped in this serving cell.

[0204] Further, the condition (b) may mean that the upper layer instructs the lower layer to stop BFD at the PSCell. Further, the condition (c) may be replaced with a condition for notifying the lower layer to stop BFD. For example, it may be a combination of a plurality of conditions among the conditions (a-1) to (a-7). Also, the statement "notified the lower layer to stop BFD" may be paraphrased as "notified the lower layer not to perform BFD-RS measurement", "notified the lower layer not to provide beam failure instance notification", "inactivated the BWP used for BFD", etc. Further, the condition (c) may be paraphrased as "since the last notification to the lower layer to stop BFD, the SCG has not been reset with BFD-RS", "since the last notification to the lower layer to stop BFD, the BFD-RS has not been changed", etc.

[0205] Also, another example of the processing of the terminal device in the present embodiment will be described with reference to FIG. 12. The processing unit 502 of the UE 122 that has received RRC signaling including an instruction to activate the SCG from the transmission unit 600 of the gNB 108 makes a condition determination (step S1200) and operates based on the determination (step S1202).

[0206] The RRC of the UE 122 notifies the lower layer that the SCG is activated in accordance with the RRC signaling including the instruction to activate the SCG received from the base station device. The MAC of the UE 122 instructed by the upper layer to activate the SCG determines in step S1200 whether one or more of the following conditions are satisfied. (a) Beam failure occurs at the PSCell. (b) The TAT associated with the PTAG is not running.

[0207] The MAC of the UE 122 determines in step S1200 whether one or more of the above conditions are satisfied If it is determined that one or more of the above conditions are met, in step S1202, it may notify the upper layer that a random access procedure is required; if it is determined that none of the above conditions are met, it may not be necessary to notify the upper layer that a random access procedure is required in step S1202.

[0208] The condition (a) may be rephrased as follows: (a-1) In the PSCell, the beam failure counter is equal to the beam failure counter threshold. Or big. (a-2) BFD is stopped in the PSCell. (a-3) After the last notification of the beam failure of the PSCell to the upper layer, the BFD-RS of the PSCell is Not configured.

[0209] Each embodiment may be combined with another. Also, each embodiment can disable BFD. may mean stopping BFD on the MAC, may mean stopping BFD on the PHY, or may mean stopping both BFD on the MAC and PHY. Stopping BFD in MAC may mean not performing some or all of the procedures for beam failure detection and beam failure recovery. Also, stopping BFD in PHY means not performing measurements of the BFD-RS corresponding to the BFD to be stopped in PHY, and not performing measurements of the BFD-RS used for BFD. This may mean deactivating the BWP associated with the BFD, or not providing a beam failure instance notification to the MAC regardless of the measurement results of the BFD-RS corresponding to the BFD to be stopped. Also, the BFD in the MAC may be stopped by the RRC, or may be instructed to be stopped by the RRC. Yes. Also, BFD in the MAC may be stopped by the MAC. Also, BFD in the PHY may be stopped by the MAC or may be instructed to be stopped by the MAC. Further, the MAC or the PHY may stop BFD based on an instruction from a higher layer to stop BFD. . Resuming BFD may be equivalently stated as performing BFD. The determination of whether to resume or stop BFD may be made for each serving cell, and the determination of whether BFD is resumed or stopped may also be made for each serving cell.

[0210] Also, in each embodiment, the MAC entity of UE122 configured to perform BFD on the PSCell of the deactivated SCG starts or restarts a beam failure detection timer (beamFailureDetectionTimer) based on having received a beam failure instance indication from a lower layer, increments the value of a beam failure counter (BFI_COUNTER) by 1, and notifies an upper layer of a beam failure of the PSCell based on at least the value of the beam failure counter being greater than or equal to a beam failure counter threshold (beamFailureInstanceMaxCounter). Other conditions for notifying an upper layer of a beam failure of the PSCell may be added. Also, when conditions for notifying an upper layer of a beam failure of the PSCell are met, the MAC may notify a lower layer to stop BFD. Also, the phrase "notify a lower layer to stop BFD" may be paraphrased as "notify a lower layer not to perform measurements of BFD-RS", "notify a lower layer not to provide a beam failure instance indication", "deactivate the BWP used for BFD", etc. The MAC may determine that a beam failure has been detected based on the value of the beam failure counter being greater than or equal to the beam failure counter threshold. Also, detecting a beam failure may simply be paraphrased as being a beam failure. When the beam failure detection timer, the beam failure counter threshold, or BFD-RS is reset by an upper layer, the UE may set the value of the beam failure counter to 0. Also, the UE may set the value of the beam failure counter to 0 based on at least the beam failure detection timer expiring. Other conditions for setting the value of the beam failure counter to 0 may be added.Furthermore, the PHY 300 of the UE 122 configured to perform BFD on a PSCell of a deactivated SCG may provide a notification to a higher layer (such as a MAC) if the radio link quality of the BFD-RS measured by the BWP of the PSCell becomes worse (lower) than a threshold set by a higher layer (such as an RRC). The notification may be a beam failure instance notification.

[0211] In each embodiment, the BFD-RS may be a reference signal used for beam failure detection (BFD). The BFD-RS may be a reference signal in which, in a radio link monitoring RS configuration (RadioLinkMonitoringRS) including radio link monitoring RS identifier information (RadioLinkMonitoringRS-Id) for identifying the reference signal, information indicating the purpose of monitoring is set to indicate that the purpose is to monitor beam failures, or information indicating that the purpose is both to monitor radio link failures and to monitor beam failures. The radio link monitoring RS configuration may be included in the radio link monitoring configuration. The radio link monitoring configuration may be a configuration used to configure radio link monitoring for detecting beam and / or cell radio link failures. "Reconfiguring the BFD-RS" may also mean "reconfiguring the BFD-RS in accordance with the radio link monitoring configuration for the BFD-RS included in the message related to RRC reconfiguration." Reconfiguring the BFD-RS in accordance with the radio link monitoring configuration for the BFD-RS included in the message related to RRC reconfiguration may also be referred to as modifying the BFD-RS. A radio link monitoring configuration for a BFD-RS may be a radio link monitoring configuration including a radio link monitoring RS configuration in which the information indicating the purpose of monitoring includes information indicating that the purpose is to monitor beam failures, or information indicating that the purpose is both to monitor radio link failures and to monitor beam failures.

[0212] Also, the RRC of UE122 may stop the BFD of the PSCell based on being notified of the beam failure of the PSCell from a lower layer, or may not perform BFD on the PSCell of the deactivated SCG. For example, based on being reconfigured by the base station device using parameters such as bfd-and-RLM, the BFD of the PSCell may be stopped, or the BFD of the PSCell may be stopped based on detecting a radio link failure in the SCG, or the BFD of the PSCell may be stopped based on other conditions. Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD". For example, based on being reconfigured by the base station device using parameters such as bfd-and-RLM, the BFD of the PSCell may be stopped Also, the RRC of UE122 may stop the BFD of the PSCell based on being notified of the beam failure of the PSCell from a lower layer, or may not perform BFD on the PSCell of the deactivated SCG. For example, based on being reconfigured by the base station device using parameters such as bfd-and-RLM, the BFD of the PSCell may be stopped, or the BFD of the PSCell may be stopped based on detecting a radio link failure in the SCG, or the BFD of the PSCell may be stopped based on other conditions. Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD". Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD". Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD". Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD". Also, the RRC of UE122 is set to perform BFD on the PSCell of the deactivated SCG by RRC signaling received from the base station device, based on the BFD-RS being reconfigured, being set or reconfigured to perform BFD on the PSCell of the deactivated SCG, receiving an instruction to activate the SCG, etc., and may notify the lower layer to start or resume BFD in the PSCell. Also, "notify the lower layer to start or resume BFD" may be paraphrased as "notify the lower layer to perform BFD".

[0213] Also, timers including the beam failure detection timer and TAT, once started, run until they are stopped or expire, and otherwise do not run. Also, a timer can be started when it is not running, and can be restarted when it is running. Also, a timer always starts or restarts from its initial value. The interval from when the timer starts or restarts until it expires is not updated until the timer is stopped or expires. If the MAC entity sets the interval from when the timer starts or restarts until it expires to 0, other conditions Also, timers including the beam failure detection timer and TAT, once started, run until they are stopped or expire, and otherwise do not run. Also, a timer can be started when it is not running, and can be restarted when it is running. Also, a timer always starts or restarts from its initial value. The interval from when the timer starts or restarts until it expires is not updated until the timer is stopped or expires. If the MAC entity sets the interval from when the timer starts or restarts until it expires to 0, other conditions Also, timers including the beam failure detection timer and TAT, once started, run until they are stopped or expire, and otherwise do not run. Also, a timer can be started when it is not running, and can be restarted when it is running. Also, a timer always starts or restarts from its initial value. The interval from when the timer starts or restarts until it expires is not updated until the timer is stopped or expires. If the MAC entity sets the interval from when the timer starts or restarts until it expires to 0, other conditions Also, timers including the beam failure detection timer and TAT, once started, run until they are stopped or expire, and otherwise do not run. Also, a timer can be started when it is not running, and can be restarted when it is running. Also, a timer always starts or restarts from its initial value. The interval from when the timer starts or restarts until it expires is not updated until the timer is stopped or expires. If the MAC entity sets the interval from when the timer starts or restarts until it expires to 0, other conditions Also, timers including the beam failure detection timer and TAT, once started, run until they are stopped or expire, and otherwise do not run. Also, a timer can be started when it is not running, and can be restarted when it is running. Also, a timer always starts or restarts from its initial value. The interval from when the timer starts or restarts until it expires is not updated until the timer is stopped or expires. If the MAC entity sets the interval from when the timer starts or restarts until it expires to 0, other conditions Unless otherwise specified, the timer expires as soon as it starts.

[0214] Based on Non-Patent Document 9, a UE configured to perform BFD on the PSCell of an inactivated SCG stops BFD when it determines that there is a beam failure. If BFD in the PHY is stopped and BFD in the MAC is not stopped, based on Non-Patent Document 8, in the MAC, since no beam failure instance notification is provided from the lower layer, the beam failure counter is set to 0 even though there is a beam failure. In this case, when activating the SCG, it may be determined that there is no beam failure and the upper layer may not be notified that a random access procedure is required. According to each of the above embodiments, the UE can make an appropriate determination as to whether a random access procedure is required when activating the SCG.

[0215] In the above description, the MAC entity of the UE may determine some or all of the following (A) to (C) and notify indication#A to the RRC entity based on those determinations. (A) Expiration of the TAT associated with the TAG (PTAG) including the PSCell of the SCG (B) The SCG being in an inactive state (C) Notification from the RRC entity that RLM is not configured to be performed on the PSCell of the inactivated SCG

[0216] In addition to or instead of the above description, the MAC entity of the UE may determine some or all of the following (A) to (C) and notify indication#B to the RRC entity based on those determinations. (A) The SCG being in an inactive state (B) Detection of beam failure (BF) at the PSCell (C) The PSCell of the inactivated SCG is configured to perform BFD.

[0217] In the above description, indication #A may be a notification (signaling) indicating the following (A) and / or (B). Additionally or alternatively, indication #A may be a notification (signaling) indicating something other than the following (A) and (B). (A) A random access procedure is required to activate SCG. (B) The TAT associated with the TAG (PTAG) containing the PSCell of the SCG has expired.

[0218] In addition to or instead of the above description, indication #B may be a notification (signaling) indicating the following (A) and / or (B): In addition to or instead of that, indication #B may be a notification (signaling) indicating something other than the following (A) and (B). (A) A random access procedure is required to activate SCG. (B) Beam failure detected in the PSCell of the SCG.

[0219] In addition to or instead of the above description, the RRC entity of the UE may perform the following (A) to (C): Additionally or alternatively, the RRC entity of the UE may cancel indication #B based on any or all of the following: You may cancel. (A) When the SCG is in an inactive state, a message regarding reconfiguration of the RRC connection including RadioLinkMonitoringConfig is received. (B) In the inactive state of the SCG, the reference signal used for BFD (BFD RS) was changed. thing (C) Beam failure detected in the PSCell of the SCG was recovered.

[0220] The random access procedure in the above description may be the random access procedure described in part or all of (I) to (K) of the above (SA-2).

[0221] Also, the radio bearer in the above description may be a DRB, an SRB, or both a DRB and an SRB, unless otherwise specified.

[0222] Also, in the above description, expressions such as "being notified" and "receiving a notice" may be paraphrased with each other.

[0223] Also, in the above description, expressions such as "associating", "correlating", and "relating" may be paraphrased with each other.

[0224] Also, in the above description, expressions such as "being included", "being contained", and "having been contained" may be paraphrased with each other.

[0225] Also, in the above description, "the above ~" may be paraphrased as "the aforementioned ~".

[0226] Also, in the above description, "the SpCell of the SCG" may be paraphrased as "the PSCell".

[0227] Also, in the above description, expressions such as "being determined as ~", "being set as ~", and "including ~" may be paraphrased with each other.

[0228] In the above description, "the dormant state" may be paraphrased as "the inactive state", and "the state of having returned from the dormant state" may be paraphrased as "the active state". Also, in the above description, "activation" and "deactivation" may be paraphrased as "the active state" and "the inactive state", respectively.

[0229] In the above description, "transitioning from X to Y" may be paraphrased as "becoming from X to Y". Also, in the above description, "causing a transition" may be paraphrased as "determining a transition".

[0230] In addition, in the examples of each process or the examples of the flow of each process in the above description, some or all of the steps may not be executed. Also, in the examples of each process or the examples of the flow of each process in the above description, the order of the steps may be different. Further, in the examples of each process or the examples of the flow of each process in the above description, some or all of the processes within each step may not be executed. Also, in the examples of each process or the examples of the flow of each process in the above description, the order of the processes within each step may be different. Also, in the above description, "performing B based on the fact that A" may be rephrased as "performing B". That is, the act of "performing B" may be executed independently of "the fact that A".

[0231] Note that in the above description, "A may be rephrased as B" may include, in addition to rephrasing A as B, the meaning of rephrasing B as A. Also, in the above description, when "C may be D" and "C may be E" are described, "D may be E" may be included. Also, in the above description, when "F may be G" and "G may be H" are described, "F may be H" may be included.

[0232] Also, in the above description, when the condition "A" and the condition "B" are contradictory conditions, the condition "B" may be expressed as the "other" condition of the condition "A".

[0233] The program that operates on the apparatus according to the present embodiment 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 present embodiment. The program or the information handled by the program may be temporarily read into a volatile memory such as a Random Access Memory (RAM) during processing, or stored in a non-volatile memory such as a flash memory or a Hard Disk Drive (HDD), and read out, corrected, and written by the CPU as needed.

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

[0235] Furthermore, the "computer-readable recording medium" may include, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, something that holds the program dynamically for a short time, or something that holds the program for a certain time like a volatile memory inside a computer system that becomes a server or a client in that case. Also, the above program may be for realizing a part of the aforementioned functions, and may further be realizable in combination with a program already recorded in the computer system for realizing the aforementioned functions.

[0236] Also, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, that is, typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described in this specification includes a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable It may include a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or combinations 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 circuits described above, may be composed of digital circuits or analog circuits. Also, when an integrated circuit technology that replaces current integrated circuits appears due to the progress of semiconductor technology, it is also possible to use integrated circuits based on such technology.

[0237] Note that this embodiment is not limited to the above-described embodiment. In the embodiment, an example of the apparatus has been described, but this embodiment is not limited thereto, and it can also be applied to stationary or non-mobile electronic devices installed indoors and outdoors, such as terminal devices or communication devices such as AV devices, kitchen devices, cleaning and washing devices, air conditioning devices, office devices, vending machines, and other household appliances.

[0238] As described above, this embodiment has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and design changes and the like within the scope not departing from the gist of this embodiment are also included. Also, this embodiment can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. Also, configurations in which elements described in the above embodiment and elements having the same effect are replaced with each other are also included.

Description of Reference Numerals

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

Claims

1. A terminal device that communicates with a base station device, a processing unit that communicates using MCG and SCG, a receiving unit that receives radio resource control (RRC) signaling from the base station device, and is provided with, the SCG includes a PSCell, based on the fact that the processing unit is set to perform beam failure detection (BFD) on the PSCell of the inactivated SCG by the RRC signaling, perform BFD on the PSCell, start or restart a beam failure detection timer based on receiving a beam failure instance notification from the PHY layer, when the beam failure detection timer expires, determine whether the BFD is stopped, if it is determined that the BFD is stopped, do not set the beam failure counter to 0, if it is determined that the BFD is not stopped, set the beam failure counter to 0, A terminal device.

2. A method for a terminal device that communicates with a base station device, communicate using MCG and SCG, receive radio resource control (RRC) signaling from the base station device, the SCG includes at least a PSCell, based on the fact that the RRC signaling is set to perform beam failure detection (BFD) on the PSCell of the inactivated SCG, perform the step of performing BFD on the PSCell, start or restart a beam failure detection timer based on receiving a beam failure instance notification from the PHY layer, when the beam failure detection timer expires, perform the step of determining whether the BFD is stopped, if it is determined that the BFD is stopped, perform the step of not setting the beam failure counter to 0, if it is determined that the BFD is not stopped, perform the step of setting the beam failure counter to 0, including. A method.

3. An integrated circuit implemented in a terminal device that communicates with a base station device, a function of communicating using MCG and SCG, a function of receiving radio resource control (RRC) signaling from the base station device, ​ ​ ​ ​ ​ The SCG includes at least a PSCell, Based on being configured to perform Beam Failure Detection (BFD) on the PSCell of the deactivated SCG by the RRC signaling, the function of performing BFD on the PSCell, Based on receiving a beam failure instance notification from the PHY layer, the beam fail The function of starting or restarting a beam failure detection timer, When the beam failure detection timer expires, the function of determining whether the BFD is stopped Function, When it is determined that the BFD is stopped, the function of not setting the beam failure counter to 0 Function, When it is determined that the BFD is not stopped, the function of setting the beam failure counter to 0, and to exhibit, Integrated circuit.

Images