Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, base station device, communication method, and integrated circuit that can efficiently perform communication control.SOLUTION: A MAC entity of a terminal device determines whether or not such a condition that a value of BFI_COUNTER is equal to or greater than beamFailureInstanceMaxCount is satisfied and whether a beam failure in PSCell has been notified to an RRC entity of a terminal device when the value of BFI_COUNTER of PSCell of SCG is equal to or greater than beamFailureInstanceMaxCount and the SCG has been deactivated, and notifies the RRC entity of a notification indicating the beam failure in PSCell on the basis of the satisfaction of the condition that the value of BFI_COUNTER is equal to or greater than beamFailureInstanceMaxCount is satisfied and the determination that the beam failure in PSCell has not been notified to the RRC entity.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, 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 in 3GPP. 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, 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) in 3GPP. Even now, in 3GPP, technical studies and standardization of extended technologies of NR are being carried out.

Prior Art Documents

Non-Patent Documents

[0005] ​ [Non-Patent Document 1] 3GPP TS 38.300 v16.4.0, "NR; NR and NG-RAN Overall description; Stage 2" pp10-134 [Non-Patent Document 2] 3GPP TS 36.300 v16.4.0, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2" pp19-362 [Non-Patent Document 3] 3GPP TS 38.331 v16.3.1, "NR; Radio Resource Control (RRC); Protocol specifications" pp21-881 [Non-Patent Document 4] 3GPP TS 36.331 v16.3.0, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specifications" pp25-1015 [Non-Patent Document 5] 3GPP TS 37.340 v16.4.0, "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-Connectivity; Stage 2" pp7-77 [Non-Patent Document 6] 3GPP TS 38.321 v16.3.0, "NR; Medium Access Control (MAC) protocol specification" pp8-152 [Non-Patent Document 7] R2-2204211, “Introduction of eDCCA” [Summary of the Invention]

Problems to be Solved by the Invention

[0006] As an NR extension technology to enable large-capacity data communication, there is a dual connectivity (also referred to as multi-connectivity) technology in which one or more base station apparatuses and terminal apparatuses communicate using a plurality of cell groups. In this dual connectivity, in order to perform communication in each cell group, the terminal apparatus needs to monitor the presence or absence of messages addressed to itself in each cell group. In order for the terminal apparatus to communicate with low latency when large-capacity data communication occurs, the terminal apparatus always needs to monitor a plurality of cell groups, which causes a problem of consuming a large amount of power. Therefore, a technique of monitoring some cell groups less frequently or stopping (cell group deactivation technology) has been started.

[0007] Non-Patent Document 7 is a CR (Change Request) draft of the MAC specification document created based on the specification details agreed upon so far. However, based on the current CR draft, when multiple beam failures are detected after the deactivation of the cell group, the MAC does not operate correctly. When multiple beam failures are detected after the deactivation of the cell group, the MAC does not operate correctly.

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

Means for Solving the Problems

[0009] To achieve the above object, one aspect of the present invention has taken the following means. That is, one aspect of the present invention is a terminal apparatus that communicates with a base station apparatus, comprising a processing unit that communicates using MCG and SCG, and a transmission unit that transmits signaling to the base station apparatus, wherein the SCG is at least At least including the PSCell, the processing unit executes processing in the MAC entity and processing in the RRC entity. The MAC entity determines whether the value of the BFI_COUNTER of the PSCell satisfies the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, and whether the beam failure in the PSCell has been notified to the RRC entity. Based on the determination that the value of the BFI_COUNTER satisfies the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount and the beam failure in the PSCell has not been notified to the RRC entity, the RRC entity is notified of a notification indicating the beam failure in the PSCell. The RRC entity determines whether the notification has been notified from the MAC entity, and based on the determination that the notification has been notified from the MAC entity, starts transmitting signaling indicating SCG failure information to the base station device.

[0010] Also, one aspect of the present invention is a method for a terminal device communicating with a base station device, which communicates using an MCG and an SCG. The SCG includes at least a PSCell. The MAC entity of the terminal device determines that the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount, and the SCG When it is deactivated, it is determined whether the value of the BFI_COUNTER satisfies the condition of being greater than or equal to the beamFailureInstanceMaxCount, and whether the beam failure in the PSCell has been notified to the RRC entity of the terminal device. Based on the determination that the value of the BFI_COUNTER satisfies the condition of being greater than or equal to the beamFailureInstanceMaxCount and that the beam failure in the PSCell has not been notified to the RRC entity, a notification indicating the beam failure in the PSCell is notified to the RRC entity. The RRC entity determines whether the notification has been notified from the MAC entity. Based on the determination that the notification has been notified from the MAC entity, the base station device starts transmitting signaling indicating SCG failure information to the base station device.

[0011] Also, one aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, communicates using MCG and SCG, the SCG includes at least a PSCell, and the integrated circuit determines whether the value of the BFI_COUNTER of the PSCell satisfies the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, and whether beam failure in the PSCell has been notified to the RRC entity of the terminal device. Based on the determination that the value of the BFI_COUNTER satisfies the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount and beam failure in the PSCell has not been notified to the RRC entity, the integrated circuit notifies the RRC entity of a notification indicating beam failure in the PSCell. The RRC entity determines whether the notification has been notified from the MAC entity, and based on the determination that the notification has been notified from the MAC entity, causes the terminal device to start transmitting signaling indicating SCG failure information to the base station device.

[0012] Also, one aspect of the present invention is a base station device that communicates with a terminal device, includes a processing unit that communicates using MCG and SCG, and a receiving unit that receives signaling from the terminal device, and the SCG includes at least a PSCell, and the processing unit determines, when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, whether the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount is satisfied in the MAC entity of the terminal device, and whether beam failure in the PSCell has been notified to the RRC entity of the terminal device. Based on the determination by the MAC entity of the terminal device that the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount is satisfied and beam failure in the PSCell has not been notified to the RRC entity of the terminal device, the MAC entity of the terminal device is caused to notify the RRC entity of the terminal device of a notification indicating beam failure in the PSCell. The RRC entity of the terminal device is caused to determine whether the notification has been notified from the MAC entity of the terminal device. Based on the determination by the RRC entity of the terminal device that the notification has been notified from the MAC entity of the terminal device, the terminal device receives signaling indicating SCG failure information from the terminal device.

[0013] 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

[0014] 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

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

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

[0017] 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 are 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.

[0018] 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 and the like in each node and entity are described, but this embodiment may be used for other radio access technologies. The names of each node and entity in this embodiment may be other names.

[0019] 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 some functions closely related to this embodiment, and may have other functions.

[0020] E-UTRA 100 may be a radio access technology. Also, E-UTRA 100 is between UE 122 and eNB 102 may be an air interface. The air interface between the UE 122 and the eNB 102 may be referred to as the Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device. 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 for the UE 122. The radio access network composed of eNBs may be referred to as the E-UTRAN. The eNB 102 may be a base station device. 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 for the UE 122. The radio access network composed of eNBs may be referred to as the E-UTRAN. The eNB 102 may terminate the E-UTRA User Plane (UP) protocol and the E-UTRA Control Plane (CP) protocol for the UE 122. The radio access network composed of eNBs may be referred to as the E-UTRAN.

[0021] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104 and may be referred to as 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 at the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated at the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be referred to as the S1-MME interface. The user plane interface of the interface 112 may be referred to as the S1-U interface. The interface 112 is an interface between the eNB 102 and the EPC 104 and may be referred to as 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 at the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated at the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be terminated at the Mobility Management Entity (MME: not shown) within the EPC 104. The user plane interface of the interface 112 may be terminated at the Serving Gateway (S-GW: not shown) within the EPC 104. The control plane interface of the interface 112 may be referred to as the S1-MME interface. The user plane interface of the interface 112 may be referred to as the S1-U interface.

[0022] One or more eNBs 102 may be connected to the EPC 104 via the interface 112. An interface may exist (not shown) between the plurality of eNBs 102 connected to the EPC 104. The interface between the plurality of eNBs 102 connected to the EPC 104 may be referred to as the X2 interface.

[0023] 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 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 (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol described below. The gNB 108 may terminate the NR user plane (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol for the UE 122.

[0024] 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 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 5GC 110. 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.

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

[0026] eNB 102 may have a function to connect to 5GC 110. An eNB 102 having a function to connect to 5GC 110 may be referred to as an ng-eNB. Interface 114 is an interface between eNB 102 and 5GC 110 and may be called the NG interface. In interface 114, there may be a control plane interface through which control signals pass, and / or a user plane interface through which user data passes. The control plane interface of interface 114 may terminate at the AMF within 5GC 110. The user plane interface of interface 114 may terminate at the UPF within 5GC 110. 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.

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

[0028] 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 referred to as 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 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,

[0029] or both the CP and the UP. Also, the interface 114, the interface Some or all of the interfaces such as interface 116, interface 118, interface 120, and interface 124 may not exist depending on the communication system provided by a telecommunications carrier or the like.

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

[0031] 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 through 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.

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

[0033] The EPC 104 may not have a PDU session and / or 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 on the EPS bearer, but may not have information on the PDU session and / or QoS flow. Also, when the UE 122 is connected to the 5GC 110, the UE 122 has information on the PDU session and / or QoS flow, but may not have information on the EPS bearer. 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] Note that 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.

[0035] Figure 2 is a diagram of an example of the E-UTRA protocol architecture according to this embodiment. Also, Figure 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 Figure 2 and / or Figure 3 are some functions closely related to this embodiment, and may have other functions. In this embodiment, the uplink (UL) and The functions of each protocol described using Figure 2 and / or Figure 3 are some functions closely related to this embodiment, and may have other functions. In this embodiment, the uplink (UL) and downlink (downlink: DL) are defined as follows. may be a link from the terminal device to the base station device. Also, in this embodiment, the downlink (DL) may be a link from the base station device to the terminal device.

[0036] FIG. 2(A) is a diagram of the E-UTRA user plane (UP) protocol stack. As shown in FIG. 2(A), the E-UTRAN UP protocol may be a protocol between the UE 122 and the eNB 102. That is, the E-UTRAN UP protocol may be a protocol terminated at the eNB 102 on the network side. As shown in FIG. 2(A), 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, an RLC (Radio Link Control) 204 which is a radio link control layer, and a PDCP (Packet Data Convergence Protocol) 206 which is a packet data convergence protocol layer.

[0037] FIG. 3(A) is a diagram of the NR user plane (UP) protocol stack. As shown in FIG. 3(A), the NR UP protocol may be a protocol between the UE 122 and the gNB 108. That is, the NR UP protocol may be a protocol terminated at the gNB 108 on the network side. As shown in FIG. 3(A), the E-UTRA user plane protocol stack may be composed of a PHY 300 which is a radio physical layer, a MAC 302 which is a medium access control layer, an RLC 304 which is a radio link control layer, a PDCP 306 which is a packet data convergence protocol layer, and an SDAP (Service Data Adaptation Protocol) 310 which is a service data adaptation protocol layer.

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

[0039] Figure 3(B) is a diagram of the NR control plane (CP) protocol configuration. As shown in Figure 3(B), in the NR CP protocol, RRC308, which is the radio resource control layer, may be the protocol between UE122 and gNB108. That is, RRC308 may be the protocol that terminates at gNB108 on the network side. Also, in the E-UTRAN CP protocol, NAS312, which is the non-AS layer, may be the protocol between UE122 and the AMF. That is, NAS312 may be the protocol that terminates at the AMF on the network side. protocol.

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

[0041] In the present embodiment, when the protocols of E-UTRA and NR are not distinguished hereinafter, terms such as PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be used. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) may be the PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) of the E-UTRA protocol, respectively, 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. Also, SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

[0042] Also, in the present embodiment, when distinguishing between the protocols of E-UTRA and NR hereinafter, PHY200, MAC202, RLC204, PDCP206, and RRC208 are sometimes referred to as PHY for E-UTRA or PHY for LTE, MAC for E-UTRA or MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE, respectively. Also, there are cases where PHY200, MAC202, RLC204, PDCP206, and RRC208 are described as E-UTRA PHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, etc. Yes. Also, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 may be referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. In addition, PHY200, MAC302, RLC304, PDCP306, and RRC308 may sometimes be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

[0043] Describe the entities in the AS layer of E-UTRA and / or NR. An entity having some or all of the functions of the MAC layer may be called a MAC entity. An entity having some or all of the functions of the RLC layer may be called an RLC entity. The functions of the PDCP layer An entity having some or all of them 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. The functions of the RRC layer An entity having some or all of them 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.

[0044] Note that 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.

[0045] 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: In the Radio Resource Control (RRC) layer, RRC messages (also referred to as RRC messages, RRC information, or RRC signaling) may be transmitted and received. Also, the base station device and the terminal device may transmit and receive MAC (Medium Access Control) control elements in the MAC layer. Further, the RRC layer of the terminal device acquires system information notified from the base station device. Here, the RRC message, the system information, and / or the MAC control element are also referred to as upper layer signals (higher layer signaling) or upper layer parameters (higher layer parameter). Each parameter included in the upper layer signal received by the terminal device may be referred to as an upper layer parameter. In the processing of the PHY layer, the upper layer means the upper layer as seen from the PHY layer, and may mean one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non-Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may mean one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. Hereinafter, the meaning of "A is given (provided) by the upper layer" or "A is given (provided) by the upper layer" may mean that the upper layer (mainly the RRC layer, MAC layer, etc.) of the terminal device receives A from the base station device, and the received A is given (provided) from the upper layer of the terminal device to the physical layer of the terminal device. For example, in the terminal device, "an upper layer parameter is provided" may mean that the terminal device receives an upper layer signal from the base station device, and the upper layer parameter included in the received upper layer signal is provided from the upper layer of the terminal device to the physical layer of the terminal device 1. That the upper layer parameter is set in the terminal device may also mean that the upper layer parameter is given (provided) to the terminal device. For example, that the upper layer parameter is set in the terminal device may mean that the terminal device receives an upper layer signal from the base station device and sets the received upper layer parameter in the upper layer.However, the setting of the upper layer parameters in the terminal device may include the setting of the default parameters pre - given to the upper layer of the terminal device. When explaining the transmission of an RRC message from the terminal device to the base station device, the expression of "submitting a message from the RRC entity of the terminal device to the lower layer (lower layer)" may be used. In the terminal device, "submitting a message to the lower layer" from the RRC entity may mean submitting the message to the PDCP layer. In the terminal device, "submitting a message to the lower layer" from the RRC layer may mean that since the RRC message is transmitted using the SRB (such as SRB0, SRB1, SRB2, SRB3), it means submitting it to the PDCP entity corresponding to each SRB. When the RRC entity of the terminal device receives an indication from the lower layer, the lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

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

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

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

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

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

[0051] The PDCCH is a downlink radio communication channel (radio communication from a base station device to a terminal device). The UE may be used to transmit (or carry) Downlink Control Information (DCI), where one or more DCIs (DCI In other words, a format for the downlink control information may be defined. The fields corresponding to the PDCCH candidates may be defined as DCI and mapped to information bits. It may be transmitted in a candidate. The terminal device may monitor a set of PDCCH candidates in the serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode a PDCCH according to a certain DCI format. Also, the terminal device may use a CORESET (Control Resource Set) to monitor a set of PDCCH candidates. The DCI format may be used for scheduling PUSCH in the serving cell. PUSCH may be used for transmitting user data, transmitting an RRC message described later, etc.

[0052] PUCCH may be used to transmit uplink control information (Uplink Control Information: UCI) in uplink wireless communication (wireless communication from the terminal device to the base station device). Here, the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel. Also, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request UL-SCH (UL-SCH: Uplink Shared CHannel) resources. Also, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement). It may be included. It may be included. It may be included. It may be included.

[0053] PDSCH may be used for transmitting downlink data (DL-SCH: Downlink Shared CHannel) from the MAC layer. Also, PDSCH may be used for transmitting system information (SI: System Information), random access response (RAR: Random Access Response), etc. in the downlink case. It may be used.

[0054] 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. Further, 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. The RRC signaling transmitted from the base station apparatus may also 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. Further, the PUSCH may be used to transmit the UE's capability (UE Capability) in the uplink.

[0055] The PRACH may be used to transmit a random access preamble. The PRACH may also 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.

[0056] An example of the MAC function will be described. The MAC may be referred to as the MAC sublayer. The MAC may have a function of mapping various logical channels to corresponding transport channels. The logical channels may be identified by logical channel identifiers (Logical Channel Identity, or Logical Channel ID). The MAC may be connected to the upper RLC via logical channels. The logical channels 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 channels may be divided into uplink logical channels and downlink logical channels. The MAC may have a function of multiplexing MAC SDUs belonging to one or more different logical channels and providing 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 via the logical channels 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 scheduling report (SR) function of reporting 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 of 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 performing discontinuous reception (DRX) and / or discontinuous transmission (DTX), executing a random access (RA) procedure, notifying information on transmit power, a power headroom report (PHR) function, notifying data volume information of a transmit buffer, a buffer status report (BSR) function, etc. The NR MAC may have a bandwidth adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. Further, the MAC PDU may include a MAC control element (MAC CE), which is an element for performing control in the MAC.

[0057] The uplink (UL) and / or downlink (DL) logical channels used in E-UTRA and / or NR will be described. ownlink).

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

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

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

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

[0062] 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 on both the uplink and the downlink.

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

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

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

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

[0067] The mapping between the logical channels and the transport channels in the downlink of E-UTRA and / or NR Describe the mapping.

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

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

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

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

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

[0073] ​​​​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. To perform 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 act of sending a status report transmission instruction 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 data discard function. 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, data received from the upper layer is split and / or combined, an RLC header is added, etc., but retransmission control of data does not have to be performed. The UM RLC entity may be a unidirectional entity or a bi-directional entity. When the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. When the UM RLC entity is a bi-directional entity, the UM RRC entity may be configured as a UM RLC entity composed of a transmitting side and a receiving side. In AM, data received from the upper layer may be split and / or combined, an RLC header may be added, retransmission control of data, etc. may be performed. The AM RLC entity is a bi-directional entity and may be configured as an AM RLC composed of a transmitting side and a receiving side. Note that the data provided to the lower layer in TM, and / or the data provided from the lower layer may be called a TMDPDU. Also, the data provided to the lower layer in UM, and / or the data provided from the lower layer may be called a UMDPDU. Also, the data provided to the lower layer in AM, or the data provided from the lower layer may be called an AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Also, the RLC PDU may include a data RLC PDU and a control RLC PDU. The data RLC PDU may be called an RLC DATA PDU (RLC Data PDU, RLC data PDU). Also, the control RLC PDU may be called an RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).

[0074] An example of the functions of PDCP will be described. PDCP may be referred to as the PDCP sublayer. PDCP may have a function of maintaining sequence numbers. Also, PDCP may have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames in the radio section. The protocol used for header compression / decompression of IP packets may be called the ROHC (Robust Header Compression) protocol. Also, the protocol used for header compression / decompression of Ethernet frame headers may be called the EHC (Ethernet (registered trademark) Header Compression) protocol. Also, PDCP may have a function of encrypting / decrypting data. Also, PDCP may have a function of protecting data integrity / verifying data integrity. Also, PDCP may have a re-ordering function. Also, PDCP may have a retransmission function of PDCP SDU. Also, PDCP may have a function of discarding data using a discard timer. Also, PDCP may have a duplication function. Also, PDCP may have a function of discarding duplicate received data. The PDCP entity is a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. Also, the PDCP PDU may include a data PDCP PDU and a control PDCP PDU. The data PDCP PDU may be called the PDCP DATA PDU (PDCP Data PDU, PDCP data PDU). Also, the control PDCP PDU may be called the PDCP CONTROL PDU (PDCP Control PDU, PDCP control PDU, PDCP control PDU).

[0075] An example of the functions of SDAP will be described. SDAP is the service data adaptation protocol layer (service It is the Service Data Adaptation Protocol layer (SDAP). SDAP may have a function of associating (mapping) the downlink QoS flow sent from the 5GC 110 to the terminal device via the base station device with the data radio bearer (DRB), and / or mapping the uplink QoS flow sent from the terminal device to the 5GC 110 via the base station device with the DRB. Also, SDAP may have a function of storing mapping rule information. Further, SDAP may have a function of marking the QoS flow identifier (QFI). Note that the SDAP PDU may include a data SDAP PDU and a control SDAP PDU. The data SDAP PDU may be referred to as the SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). Also, the control SDAP PDU may be referred to as the SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). Note that there may be one SDAP entity in the terminal device for each PDU session.

[0076] It may have. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or the 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 use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, detection and recovery of radio link failures, etc. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.

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

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

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

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

[0081] 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. Further, other RRC signaling may be included.

[0082] RRC signaling sent in the downlink (DL) direction using DCCH may include, for example, an RRC Connection Reconfiguration message, an RRC Connection Release message, a Security Mode Command message, a UE Capability Enquiry 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 Enquiry message, etc. may be included. Other RRC signaling may also be included.

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

[0084] The functions of PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS described above are examples, and some or all of each function may not be implemented. Also, some or all of the functions of each layer may be included in other layers.

[0085] Next, the state transition of UE122 in LTE and NR will be described. When the UE122 is connected to the EPC or 5GC and the RRC connection has been established, the UE122 may be in the RRC_CONNECTED state. The state where the RRC connection has been established may include a state where the UE122 holds some or all of the UE context described below. Also, the state where the RRC connection has been established may include a state where the UE122 can transmit and / or receive unicast data. Also, when the RRC connection of the UE122 is suspended, the UE122 may be in the RRC_INACTIVE state. Also, the UE122 may enter the RRC_INACTIVE state when it is connected to the 5GC and the RRC connection is suspended. When the UE122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state, the UE122 may be in the RRC_IDLE state.

[0086] Note that when the UE122 is connected to the EPC, it does not have the RRC_INACTIVE state, but the suspension of the RRC connection may be started by the E-UTRAN. When the UE122 is connected to the EPC and the RRC connection is suspended, the UE122 may transition to the RRC_IDLE state while holding the UE's AS context and the resumeIdentity used for resume. The upper layer (e.g., NAS layer) of the RRC layer of the UE122 may start the resume of the suspended RRC connection when the UE122 holds the UE's AS context, the resume of the RRC connection is permitted by the E-UTRAN, and the UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state.

[0087] The definition of inactivity may be different between the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110. Also, all or some of the procedures for the UE 122 to resume from inactivity may be different between the case where the UE 122 is connected to the EPC (when the UE 122 is in the RRC_IDLE state and is inactivated) and the case where the UE 122 is connected to the 5GC (when the UE 122 is in the RRC_INACTIVE state and is inactivated).

[0088] Note that the states of RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE may be referred to as the connected mode, inactive mode, and idle mode, respectively, or may be referred to as the RRC connected mode, RRC inactive mode, and RRC idle mode, respectively. The UE AS context held by the UE 122 may be information including all or some of the current RRC configuration, the current security context, the PDCP state including the ROHC (RObust Header Compression) state, the C-RNTI (Cell Radio Network Temporary Identifier) used in the source PCell of the connection source, the cell identifier, and the physical cell identifier of the source PCell. Note that the UE AS context held by any or all of the eNB 102 and 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]

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

[0091] Next, the serving cell will be explained. CA and / or DC, which will be described later, In a terminal device in an unconfigured RRC connected state, the serving cell may be configured as one primary cell (PCell). In addition, the CA and / or DC described later may be configured. In a terminal device in an RRC connected state in which the plurality of serving cells are set, the plurality of serving cells may refer to a set of a plurality of cells (set of cell(s)) consisting of one or more special cells (SpCells) and one or more secondary cells (SCells). The SpCell may support PUCCH transmission and contention-based random access (CBRA), and the SpCell may always be activated. The PCell may be a cell used in an RRC connection establishment procedure when a terminal device in an RRC idle state transitions to an RRC connected state. The PCell may also be a cell used in an RRC connection re-establishment procedure in which the terminal device re-establishes an RRC connection. The PCell may also be a cell used in a random access procedure during handover. The PSCell may be a cell used in a random access procedure when a secondary node is added, which will be described later. The SpCell may also be a cell used for purposes other than those described above.

[0092] The fact that the group of serving cells configured for the terminal device is composed of a SpCell and one or more SCell may be regarded as 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. on:CA) may be considered to be set. Also, for a terminal device with CA set, a cell that provides additional radio resources for the SpCell may mean an SCell.

[0093] A group of serving cells configured by RRC, for which the same timing reference cell and the same timing advance value are used for the cells in which the uplink is configured 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. A group of serving cells configured by RRC, for which the same timing reference cell and the same timing advance value are used for the cells in which the uplink is configured 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.

[0094] A cell group (Cell Group) configured for the terminal device by 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 cells. A cell group (Cell Group) configured for the terminal device by 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 cells.

[0095] Dual Connectivity (DC) is a technology that enables data communication by 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 case for DC or for MR-DC described later. When DC or MR-DC 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.

[0096] Also, when DC is not set, the cell group set in the terminal device may be called MCG. Also, when 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.

[0097] 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. Also, MR-DC may be a technology that performs DC using NR for both MCG and SCG. Yes. MR-DC may be a technology included in DC. As an example of MR-DC using E-UTRA for MCG and NR for SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) using EPC for the core network, or NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC for the core network. Also, as an example of MR-DC using NR for MCG and E-UTRA for SCG, there may be NE-DC (NR-E-UTRA Dual Connectivity) using 5GC for the core network. Further, as an example of MR-DC using NR for both MCG and SCG, there may be NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.

[0098] Note that in the terminal device, there may be one MAC entity for each cell group. For example, when DC or MR-DC is configured in the terminal device, there may be one MAC entity for MCG and one MAC entity for SCG. The MAC entity for MCG in the terminal device may always be established in the terminal device in all states (such as RRC idle state, RRC connected state, and RRC inactive state, etc.). Also, the MAC entity for SCG in the terminal device may be created by the terminal device when SCG is configured in the terminal device. Further, the MAC entity for each cell group of the terminal device may be configured when the terminal device receives RRC signaling from the base station device. When the MAC entity is associated with MCG, SpCell may mean PCell. Also, the MAC enti ty... When the MAC entity is associated with MCG, SpCell may mean PCell. Also, the MAC entity When Ti is associated with the SCG, SpCell may mean the Primary SCG Cell (PSCell). Also, when the MAC entity is not associated with a cell group, SpCell may mean the PCell. PCell, PSCell, and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for the MCG may be an E-UTRA MAC entity, and the MAC entity for the SCG may be an NR MAC entity. Also, in NE-DC, the MAC entity for the MCG may be an NR MAC entity, and the MAC entity for the SCG may be an E-UTRA MAC entity. Also, in NR-DC, the MAC entities for both the MCG and the SCG may be NR MAC entities. Note that it may be rephrased that there is one MAC entity for each cell group, i.e., there is one MAC entity for each SpCell. Also, one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

[0099] The radio bearer will be described. When the terminal device communicates with the base station device, a radio connection is established by establishing a radio bearer (RB) between the terminal device and the base station device. Okay. The radio bearers used for CP may be called Signaling Radio Bearers (SRBs). Also, the radio bearers used for UP may be called Data Radio Bearers (DRBs). Each radio bearer may be assigned a radio bearer identifier (Identity: ID). The radio bearer identifier for SRB may be called SRB Identity or SRB ID. The radio bearer identifier for DRB may be called DRB Identity or DRB ID. For E-UTRA, SRB0 to SRB2 may be defined, or other SRBs may be defined. For NR, SRB0 to SRB3 may be defined, or other SRBs may be defined. SRB0 may be an SRB for RRC messages transmitted and / or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2. The RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB1. SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB2. Also, 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 set in the terminal device. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB3. Also, other SRBs may be prepared for other purposes. DRB may be a radio bearer for user data.For RRC signaling transmitted and / or received using a DRB, the DTCH of the logical channel may be used.

[0100] The radio bearer in the terminal device will be described. The radio bearer may include an RLC bearer. An RLC bearer may be composed of one or two RLC entities and a logical channel. The RLC entity in the case where there are two RLC entities in the RLC bearer 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 with AS security 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 a 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 with AS security 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 with AS security 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.

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

[0102] 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 type of the DRB established and / or configured in the terminal device may be any of all the bearer types.

[0103] 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 the bearers, i.e., MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer, and SN terminated SCG bearer, may be an NR PDCP. Also, if an NGEN-DC, NE-DC, or NR-DC is configured in the terminal device, the PDCP entity established and / or configured for the radio bearers of all bearer types may be an NR PDCP.

[0104] In NR, a DRB established and / or configured in a terminal device may be associated with one PDU session. The SDAP entity, the PDCP entity, the RLC entity, and the logical channels established and / or configured in the terminal device may be used to establish and / or configure the SDAP entity, the PDCP entity, the RLC entity, and the logical channels that the terminal device receives from the base station device. The RRC signaling may be established and / or configured by the RRC signaling.

[0105] Regardless of whether MR-DC is configured or not, the master node is eNB102 and EPC104. A network configuration in which the master node is the gNB 108 and the 5GC 110 is the core network may be called E-UTRA / EPC. A network configuration in which the master node is the eNB 102 and the 5GC 110 is the core network may be called E-UTRA / 5GC. A network configuration in which the master node is the gNB 108 and the 5GC 110 is the core network may be called NR or NR / 5GC. When MR-DC is not set, the above-mentioned master node may refer to a base station device that communicates with a terminal device.

[0106] Next, we will explain handover in LTE and NR. Handover is a process in which a UE 122 in an RRC connected state changes its serving cell from a source SpCell to a target SpCell. Okay. The handover may be performed when the UE 122 receives RRC signaling for instructing the handover from the eNB 102 and / or the gNB 108. The RRC signaling for instructing the handover refers to a message for reconfiguring the RRC connection that includes parameters for instructing the handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). It may be a message regarding the reconfiguration. Note that the information element named MobilityControlInfo mentioned above may be referred to as a mobility control setting information element, or a mobility control setting, or a mobility control information. Note that the information element named ReconfigurationWithSync mentioned above may be referred to as a synchronized reconfiguration information element, or a synchronized reconfiguration. Also, the RRC signaling for instructing the handover may be a message indicating a movement to a cell of another RAT (for example, MobilityFromEUTRACommand or MobilityFromNRCommand). Also, the handover may be referred to as a reconfiguration with sync. Also, the conditions under which the UE 122 can perform the handover may include some or all of the following: when AS security is activated, when SRB2 is established, and when at least one DRB is established.

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

[0108] 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. Also, 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 caused to be performed on a specific terminal device may include, for example, processing such as security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, and release of the RRC connection. The RRC connection reconfiguration process may include, for example, processing such as 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. Also, 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 caused to be performed on a specific terminal device may include, for example, processing such as security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, and release of the RRC connection. The RRC connection reconfiguration process may include, for example, processing such as 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. Also, 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).

[0109] 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 settings, according to the received above-mentioned 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). Next, the terminal device performs processing if necessary, such as settings, according to the received above-mentioned 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).

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

[0111] In MR-DC, the RRC signaling for the SCG side settings (such as cell group settings, radio bearer settings, measurement settings, etc.) may be transferred between the master node and the terminal device. For example, in EN-DC or NGEN-DC, the NR RRC signaling may be included in the form of a container in the E-UTRA RRC signaling transmitted and received between the eNB 102 and the UE 122. Also, in NE-DC, the E-UTRA RRC signaling may be included in the form of a container in the NR RRC signaling transmitted and received between the gNB 108 and the UE 122. The RRC signaling for the SCG side settings may be transmitted and received between the master node and the secondary node. In addition, not limited to the case of using MR-DC, the NR RRC signaling may be included in the E-UTRA RRC signaling transmitted from the eNB 102 to the UE 122, and the E-UTRA RRC signaling may be included in the NR RRC signaling transmitted from the gNB 108 to the UE 122.

[0112] Note that not limited to the case of using MR-DC, the NR RRC signaling may be included in the E-UTRA RRC signaling transmitted from the eNB 102 to the UE 122, and the E-UTRA RRC signaling may be included in the NR RRC signaling transmitted from the gNB 108 to the UE 122. An example of a parameter included in the message related to the reconfiguration of the RRC connection will be described. FIG. 7 is an example of an ASN.1 description showing the fields and / or information elements related to the cell group setting included in the message related to the reconfiguration of the RRC connection in NR in FIG. 4. Also, FIG. 8 is an example of an ASN.1 description showing the fields and / or information elements related to the cell group setting included in the message related to the reconfiguration of the RRC connection in E-UTRA in FIG. 4. Not limited to FIGS. 7 and 8, examples of ASN.1 in the present embodiment, <omitted> and <omitted>

[0113] An example of a parameter included in the message related to the reconfiguration of the RRC connection will be described. FIG. 7 is an example of an ASN.1 description showing the fields and / or information elements related to the cell group setting included in the message related to the reconfiguration of the RRC connection in NR in FIG. 4. Also, FIG. 8 is an example of an ASN.1 description showing the fields and / or information elements related to the cell group setting included in the message related to the reconfiguration of the RRC connection in E-UTRA in FIG. 4. Not limited to FIGS. 7 and 8, examples of ASN.1 in the present embodiment, <omitted> and <omitted> This indicates that 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>. In this embodiment, the example of ASN.1 does not correctly follow the ASN.1 notation method. The example of ASN.1 in this embodiment represents an example of the parameters of RRC signaling in this embodiment, and other names and other notations may be used. Also, the example of ASN.1 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 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.

[0114] 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 below. 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 the configuration of the cell group of the SCG in NR, the 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 the configuration of the 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 below. 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 whether to perform the BFD and / or RLM described below 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.

[0115] Regarding the TCI (Transmission Configuration Indicator) state and the TCI information element This will be described below. The TCI state may associate a corresponding QCL (quasi - colocation) type with one or two downlink reference signals. Also, the TCI state may be set in the PDSCH and / or PDCCH. The TCI information element may be used to activate (and deactivate) the TCI state set in the PDSCH and / or PDCCH of the PSCell. Also, the TCI information element may indicate the TCI state used for receiving the PDCCH and / or the activated TCI state used for receiving the PDSCH. When the TCI information element is included in the SpCell setting, the terminal device may consider the indicated TCI state as the activated TCI state for receiving the PDCCH and / or PDSCH. In this case, if bfd - and - RLM is included in the setting for deactivation of the SCG and no reference signal is set in the radio link monitoring setting for BFD and / or RLM described below, the terminal device may use the indicated TCI state for receiving the PDCCH as the reference signal for BFD and / or RLM. Also, the TCI information element may be included only in the setting on the SCG side. When the TCI information element is not included in the SpCell setting, the terminal device may use the previously activated TCI state. If bfd - and - RLM is included in the setting for deactivation of the SCG and no reference signal is set in the radio link monitoring setting for BFD and / or RLM described below, the terminal device may use the previously activated TCI state for receiving the PDCCH as the reference signal for BFD and / or RLM.

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

[0117] The terminal device may perform 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 PSCell, etc.). Also, the terminal device may perform radio link monitoring in the serving cell (such as the PCell and / or PSCell, etc.). Receive a setting (RadioLinkMonitoringConfig: wireless link monitoring setting) indicating which reference signal to use for line link monitoring from the base station device, and perform wireless link monitoring using one or more configured reference signals (referred to here as RLM-RS). Also, the terminal device may perform wireless link monitoring using other signals. When the physical layer processing unit of the terminal device satisfies the conditions for being in synchronization in the serving cell (PCell and / or PSCell, etc.), it may notify the upper layer that it is in synchronization.

[0118] The wireless link monitoring setting may include information indicating the purpose of monitoring and identifier information indicating the reference signal. For example, the purpose of monitoring may include the purpose of monitoring wireless link failure, the purpose of monitoring beam failure, or both purposes, etc. Also, for example, the identifier information indicating the reference signal may include information indicating the SSB-Index of the SSB of the cell. That is, the reference signal may include a synchronization signal. Also, for example, the identifier information indicating the reference signal may include information indicating an identifier associated with a channel state information reference signal (CSI-RS) set in the terminal device.

[0119] Next, BFD (beam failure detection) will be described.

[0120] In the MAC entity, a beam failure recovery procedure may be set by RRC for each serving cell. The beam failure recovery procedure may be used to notify the serving gNB (the 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-RSs of the serving cell. A beam failure is detected by counting beam failure instance notifications notified from the lower layer (PHY layer) to the MAC entity. Also, if the SCG is in an inactive state, the MAC entity may perform beam failure detection in the PSCell using a certain 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) in each serving cell for beam failure detection. It may be possible to perform some or all of the following (A), (B), and (C) in each serving cell for beam failure detection. Yes. (A) If a beam failure instance notification is received from the lower layer (such as PHY), start or restart the beam failure detection timer (beamFailureDetectionTimer) and increment the 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). 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 the random access procedure in the SpCell. (A-3) If the condition that the value of BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount is satisfied. If the beam failure in the PSCell has occurred and has not been notified to the upper layer (such as the RRC entity), notify the beam failure in the PSCell to the upper layer (RRC entity, etc.). (B) If the beamFailureDetectionTimer for this serving cell has expired, or if the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the setting of the reference signal for beam failure detection (BFD-RS) has been changed by the upper layer (RRC entity, etc) set the BFI_COUNTER to 0. (C) If the serving cell is the SpCell and the random access procedure has been successfully completed set the BFI_COUNTER to 0, stop the beam failure recovery timer (beamFailureRecoveryTimer) if it is set and running, and consider the beam failure recovery procedure to have been successfully completed. Otherwise, if the serving cell is the SCell and a PDCCH addressed to the C-RNTI indicating a new uplink grant for transmitting information for SCell beam failure recovery (e.g., information included in the SCell's BFR MAC CE or the truncated BFR MAC CE of the SCell) is received or if the SCell is in the inactive state, set the BFI_COUNTER to 0, consider the beam failure recovery procedure to have been successfully completed, and cancel all beam failure recoveries (BFR) triggered for this serving cell. The MAC entity shall perform the following (A) if at least one beam failure recovery (BFR) has been triggered by the beam failure recovery procedure and it has not been cancelled.

[0121] If at least one beam failure recovery (BFR) has been triggered by the beam failure recovery procedure and it has not been cancelled, the MAC entity shall perform the following (A). (A) If the UL-SCH resource can include the BFR MAC CE of the SCell and its sub-header considering the priority of the logical channel, include the BFR MAC CE of the SCell and its sub-header. Otherwise, if the UL-SCH resource can include the truncated BFR MAC CE of the SCell and its sub-header considering the priority of the logical channel, include the truncated BFR MAC CE of the SCell and its sub-header. Otherwise, trigger a scheduling request for SCell beam failure recovery. Here, explain the beamFailureRecoveryTimer (beam failure recovery timer). When a random access procedure is started for the BFR of the SpCell and the beamFailureRecoveryConfig (beam failure recovery configuration) is set in the Active UL BWP, the MAC entity may start the beamFailureRecoveryTimer. Also, when the beamFailureRecoveryTimer is running or not set, the terminal device may use contention-free random access (CFRA) for BFR. Also, when the beamFailureRecoveryTimer expires or is not running, the terminal device may not use CFRA for BFR and instead use, for example, CBRA. Next, explain the SCG Failure Information procedure. The SCG Failure Information procedure means that the terminal device experiences SCG failures (SCG radio link failure, failure of SCG resynchronization, RRC signaling on SRB3) at the master node of E-UTRA or NR.

[0122] If the UL-SCH resource can include the BFR MAC CE of the SCell and its sub-header considering the priority of the logical channel, include the BFR MAC CE of the SCell and its sub-header. Otherwise, if the UL-SCH resource can include the truncated BFR MAC CE of the SCell and its sub-header considering the priority of the logical channel, include the truncated BFR MAC CE of the SCell and its sub-header. Otherwise, trigger a scheduling request for SCell beam failure recovery.

[0123] Next, explain the SCG Failure Information procedure.

[0124] The SCG Failure Information procedure means that the terminal device experiences SCG failures (SCG radio link failure, failure of SCG resynchronization, RRC signaling on SRB3) at the master node of E-UTRA or NR. The SCG Failure Information procedure means that the terminal device experiences SCG failures (SCG radio link failure, failure of SCG resynchronization, RRC signaling on SRB3) at the master node of E-UTRA or NR. It is a procedure for notifying (e.g., failure of SCG configuration, failure of SCG integrity verification, etc.) This is acceptable. The RRC entity of the terminal device may start the SCG failure information procedure if neither the transmission in MCG nor the transmission in SCG is suspended and one of the following (A) to (E) is satisfied. If neither the transmission in MCG nor the transmission in SCG is suspended and one of the following (A) to (E) is satisfied, the SCG failure information procedure may be started. (A) Detection of radio link failure for SCG (B) Detection of beam failure in the PSCell in the inactive state of SCG (C) Failure of synchronized reconfiguration of SCG (D) Failure of SCG configuration (E) Notification of failure of integrity verification from the lower layer (such as PDCP entity) of SCG regarding SRB3

[0125] When starting the SCG failure information procedure based on beam failure in the PSCell in the inactive state of SCG, the RRC entity of the terminal device may perform some or all of the following (A), (B), and (C). (A) If the timer T304 for SCG is running, stop it. (B) If the evaluation of conditional reconfiguration for conditional PSCell change (CPC) is set, stop it. (C) If the terminal device is within (NG) EN-DC, start the transmission of E-UTRA RRC signaling indicating SCG failure information (SCGFailureInformationNR), otherwise, start the transmission of NR RRC signaling indicating SCG failure information (SCGFailureInformation).

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

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

[0128] 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 part or all of the following (A) to (C). (A) Receiving 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

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

[0130] (Processing AD) If, when configuring the SCell, the RRC parameter (sCellState) configured for the SCell is set to activated, or if the UE122's MAC entity receives a MAC CE for activating the SCell, the MAC entity of UE122 performs process (AD-1). Otherwise, if the UE122'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 UE122 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, or if a MAC PDU is transmitted in a configured uplink grant, or if a MAC PDU is received in a configured downlink assignment, the MAC entity of UE122 restarts the SCell Inactivity Timer associated with that SCell. If the SCell becomes inactive, the MAC entity of UE122 performs process (AD-3).

[0131] (Process AD-1) If, in NR, this 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 is set to activated when configuring the SCell, the MAC entity of UE122 performs process (AD-1A) or process (AD-1B). Also, the MAC entity of UE122 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 UE122 UE122 performs part or all of the following (A) to (B). (A) If any, re-initialize all configured suspended grant type 1 link grants associated with this SCell according to the stored configuration. (B) Trigger a PHR. 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 the 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 the Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs part or all of the following (A) to (B). 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 the 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 the Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs part or all of the following (A) to (B). Set by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell If the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is not set as the Dormant BWP, the MAC entity of UE122 performs process (AD-1A). If the BWP indicated by the firstActiveDownlinkBWP-Id configured by RRC signaling for this SCell is set as the Dormant BWP, the MAC entity of UE122 performs process (AD-1B). Also, the MAC entity of UE122 performs part or all of the following (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

[0132] (Process AD-1A) The MAC entity of UE122 activates the SCell and performs part or all of the following (A) to (E). (A) Transmit a sounding reference signal (SRS) on this SCell. (B) Report CSI for this SCell. (C) (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.

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

[0134] (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.

[0135] (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.

[0136] As described above, by the MAC entity performing the process (AD), the SCell is activated and deactivated.

[0137] Also, when an SCell is added as described above, the initial state of the SCell may be set by RRC signaling. state may be set.

[0138] Here, the SCell inactivity timer will be described. For an SCell for which PUCCH is not configured, the value of the SCell inactivity timer (information regarding the time when the timer is considered to have expired) may be notified by RRC signaling. For example, when information indicating 40 ms is notified as the value of the SCell inactivity timer by RRC signaling, in the above process (AD), when the time (here, 40 ms) notified without the timer stopping after starting or restarting the timer has elapsed, the timer is considered to have expired. Also, the SCell inactivity timer timer may be a timer named sCellDeactivationTimer. timer may be a timer named sCellDeactivationTimer. timer may be a timer named sCellDeactivationTimer.

[0139] Next, the deactivation and activation of the SCG will be described.

[0140] The deactivation of the SCG may mean deactivating the SCG. Also, the deactivation of the SCG is that the MAC entity is associated with the SCG and corresponding to the MAC entity It may mean deactivating a cell group. Also, deactivation of the SCG may mean deactivating the PSCell (SpCell of the SCG), or deactivating the PSCell. Activation of the SCG may mean activating the SCG. Also, activation of the SCG may mean that a MAC entity is associated with the SCG and activating the cell group corresponding to the MAC entity. Also, activation of the SCG may mean activating the PSCell (SpCell of the SCG), or activating the PSCell.

[0141] 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 on this PSCell. (B) Do not measure CSI for this PSCell. (C) Do not report CSI for this PSCell. (D) Do not transmit PUCCH on this PSCell. (E) Do not transmit UL-SCH on this PSCell. (F) Do not trigger random access on this PSCell. (G) Do not monitor the PDCCH of this PSCell. (H) Do not monitor the PDCCH for this PSCell. (I) Inactivate the Active BWP in this PSCell. (J) Perform discontinuous reception (DRX) on 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 on this PSCell. (L) The BWP is activated in this PSCell, and the uplink grant in the above-mentioned BWP is not addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating this PSCell, and / or does not monitor the PDCCH for this PSCell. (M) Perform automatic gain control (AGC), beam failure detection (BFD) including beam failure recovery, and / or radio link monitoring (RLM) in this PSCell. (N) Suspend some or all of the configured uplink grants of grant type 1 associated with this PSCell. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) including this PSCell. (P) Reset the MAC entity on the SCG side.

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

[0143] (P) of the above (SD-1) may include some or all of (A) to (O) of the above (SD-1). Also, (P) of the above (SD-1) may include some or all of (P-1) to (P-15) below. Note that in (P-1) below, the value of parameter Bj may remain 0 in the inactive state of the SCG. (P-1) Initialize the parameter Bj set for each logical channel related to the SCG to 0. If beam failure detection (BFD) is configured in the inactive state of (P-2) SCG, the PSCell stops if all timers are running, except for the beam failure detection timer associated with it and the time alignment timer (TAT). (P-3) Set the value of the New Data Indicator (NDI) of all uplink HARQ processes to 0 to do so. (P-4) Stop any ongoing random access procedure, if any. (P-5) Discard the resources of explicitly signalled contention-free Random Access (CFRA) of 4-step and 2-step RA types, if any. (P-6) Flush the buffer of Msg3. (P-7) Flush the buffer of MSGA. (P-8) Cancel any triggered SR procedure, if any. (P-9) Cancel any triggered BSR procedure, if any. (P-10) Cancel any triggered PHR procedure, if any. (P-11) Cancel the confirmation of any triggered configured uplink grant, if any. (P-12) Flush the soft buffers of all downlink HARQ processes. (P-13) In each downlink HARQ process, consider the next received transmission for a transport block (TB) as the very first transmission. (P-14) Release the Temporary C-RNTI, if any. (P-15) In SCG, beam failure detection (BFD) is set by the parameter (bfd-and-RLM). If not, reset the counter (BFI_COUNTER) associated with the PSCell.

[0144] In LTE and / or NR, the active state of an SCG may be a state in which a terminal device performs some or all of the following (A) to (P) in a PSCell (SpCell) of the SCG. Also, the active state of an SCG may mean a state in which the SCG is activated (a state in which the SCG is not dormant). (SA-1) (A) Transmit SRS using this PSCell. (B) Measure the CSI for this PSCell. (C) Report the CSI for this PSCell. (D) Transmit PUCCH using this PSCell. (E) Transmit UL-SCH in this PSCell. (F) Perform random access on this PSCell if triggered. (G) Monitor the PDCCH of this PSCell. (H) Monitor the PDCCH for this PSCell. (I) Activate the inactive BWP in this PSCell. (J) This PSCell performs discontinuous reception (DRX). (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 an uplink grant for UL-SCH transmission in this PSCell. (L) BWP is activated in this PSCell, and uplink grant is received in the above BWP. The PDCCH of this PSCell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicated and / or monitor the PDCCH for this PSCell. (M) Perform automatic gain control (AGC), beam failure detection (BFD) including beam failure recovery, and / or radio link monitoring (RLM) in this PSCell. (N) If any, initialize (again) a part or all of the suspended configured uplink grants of grant type 1 associated with this PSCell according to the stored configuration. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) including this PSCell. (P) Initialize the parameter Bj set for each logical channel related to the SCG to 0.

[0145] 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 from (A) to (F) below may be notified from the base station device to the terminal device via the SCG. In addition or instead, the signaling and control elements from (A) to (F) below 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.). (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) Receiving a MAC CE instructing to deactivate the PSCell (E) Receiving other RRC signaling (F) Receiving other MAC CE (G) Expiration of the SCG inactivation timer (H) Expiration of the PSCell inactivation timer

[0146] The RRC signaling of (A), (C), and (E) in the above (SD-2) may include a parameter such as scg-State. When scg-State is included in the RRC signaling, it indicates the inactivation of the SCG, and when scg-State is not included in the RRC signaling, it indicates the activation of the SCG. Also, scg-State may be included in the RRC reconfiguration message or the RRC resume message. Further, the RRC signaling may be generated at the MN. When scg-State is included in the RRC signaling, it indicates the inactivation of the SCG, and when scg-State is not included in the RRC signaling, it indicates the activation of the SCG. Also, scg-State may be included in the RRC reconfiguration message or the RRC resume message. Further, the RRC signaling may be generated at the MN. When scg-State is included in the RRC signaling, it indicates the inactivation of the SCG, and when scg-State is not included in the RRC signaling, it indicates the activation of the SCG. Also, scg-State may be included in the RRC reconfiguration message or the RRC resume message. Further, the RRC signaling may be generated at the MN. signaling may be generated at the MN.

[0147] 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). Further, based on the determination, the processing unit 502 of the UE 122 deactivates the SCG and performs the operations as shown in the above (SD-1) in the inactive state of the SCG (step S1102). signaling may be generated at the MN.

[0148] In LTE and / or NR, the terminal device may determine that the SCG is in an active state based on some or all of the following (A) to (K). Note that the signaling and control elements of the following (A) to (F) may be notified from the base station device to the terminal device via the SCG. In addition or instead, the signaling and control elements of the following (A) to (F) may be from a cell group other than the SCG. The signaling and control elements of the following (A) to (F) may be notified from the base station device to the terminal device via the SCG. In addition or instead, the signaling and control elements of the following (A) to (F) may be from a cell group other than the SCG. The signaling and control elements of the following (A) to (F) may be notified from the base station device to the terminal device via the SCG. In addition or instead, the signaling and control elements of the following (A) to (F) may be from a cell group other than the SCG. It may be notified from the base station apparatus to the terminal apparatus via a loop (MCG, SCG other than the said SCG, etc.). That the SCG is in an active state may mean that the SCG is not in an inactive state. (SA-2) (A) Reception of RRC signaling instructing to activate the SCG (B) Reception of MAC CE instructing to activate the SCG (C) Reception of RRC signaling instructing to activate the PSCell (D) Reception of MAC CE instructing to activate the PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) Inactive timer of the SCG (H) Inactive timer of the PSCell (I) Scheduling request triggered to transmit a MAC PDU containing a MAC SDU Start of a random access procedure due to (J) Start of a random access procedure (K) Start of a random access procedure due to a scheduling request (in other words, the MAC entity itself started)

[0149] The RRC signaling of (A), (C), and (E) of the above (SA-2) may not be included in, for example, a parameter named scg-State in the RRC reconfiguration message and / or the RRC resume message. Also, the said RRC signaling may be generated at the MN.

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

[0151] A terminal device that deactivates the SCG may perform some or all of the following (A) to (I) in the SCG. (SD-3) (A) Consider that the SCG is deactivated. (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 SCG was activated before receiving the signaling indicating deactivation of the SCG, and if SRB3 was configured before receiving the RRC reconfiguration message or the RRC connection reconfiguration message, and the SRB3 is not released according to the RRC signaling (RadioBearerConfig) for any radio bearer configuration included in the RRC reconfiguration message or the RRC connection reconfiguration message, trigger the execution of SDU discard at the PDCP entity of the SRB3, and in addition to or instead of that, re-establish the RLC entity of the SRB3. (D) Deactivate all SCell. (E) Assume that all SCell inactivity timers associated with the active SCell have expired. (F) Assume that all SCell inactivity timers associated with the dormant SCell have expired. (G) Do not start or restart any SCell inactivity timers associated with all SCell. (H) Ignore the MAC CE for activating the SCell. For example, in the above processing (AD), the SCell ​​​​When a MAC CE for activation is received and the terminal device is not instructed to deactivate the SCG (or is not in the deactivated state of the SCG), perform process (AD-1). (I) Execute the said process (AD-2). For example, in the said process (AD), when instructed to deactivate the SCG (or when the SCG is in the deactivated state), perform process (AD-2).

[0152] When the MAC entity of the terminal device is instructed by the upper layer (such as the RRC entity) to deactivate the SCG based on (B) of the above (SD-3), all SCell of the SCG may be deactivated, and in addition to or instead of that, the PSCell may be deactivated based on the above (SD-1).

[0153] A terminal device that activates the SCG may perform some or all of the following (A) to (D) in the said SCG. (SA-3) (A) Consider that the SCG is activated. (B) If an SCG in the deactivated state was set before the terminal device receives signaling instructing it to activate the SCG, instruct the lower layer (such as the MAC entity) to activate the SCG. (C) Perform process (AD-1) to activate all SCell. (D) When activating the SCG based on RRC signaling, if this RRC signaling includes parameters related to random access for the PSCell (SpCell), start the random access procedure in this PSCell based on the notified parameters.

[0154] When the MAC entity of the terminal device is instructed by the upper layer (such as the RRC entity) to activate the SCG based on (B) of the above (SA-3), the SCG may be activated based on the above (SA-1). ​​

[0155] When the terminal device determines that the SCG is in the active state based on the above (SA-2), the terminal device 's RRC entity may instruct the lower layer (such as the MAC entity) to start a random access procedure at the PSCell of the SCG when it determines that the following (A) or (B) is satisfied.

[0156] (A) EN-DC or NGEN-DC is set in the terminal device, the RRC reconfiguration message is received via the SRB1 of E-UTRA or the RRC connection reconfiguration message of E-UTRA (handover from NR stand-alone to (NG) EN-DC), and the RRC connection reconfiguration message of E-UTRA containing the RRC reconfiguration message for the SCG side in the form of a container does not contain the parameter scg-State, and the following (A-1) or (A-2) is satisfied.

[0157] (A-1) The synchronized reconfiguration was included in the SpCell configuration of the SCG. (A-2) Before receiving the RRC signaling of E-UTRA containing the RRC reconfiguration message for the SCG side described in (A) in the form of a container, the SCG was deactivated, and when activating the SCG, the lower layer (such as the MAC entity) considers that a random access procedure is required.

[0158] (B) NR-DC is set in the terminal device, the RRC reconfiguration message is received via the SRB1 of the SCG, and the RRC reconfiguration message of NR or the RRC resume message containing the RRC reconfiguration message for the SCG side in the form of a container does not contain the parameter scg-State, and the following (B-1) or (B-2) is satisfied.

[0159] ​​​​(B-1) The synchronous reconfiguration was included in the SpCell configuration of the SCG. (B-2) Before receiving the NR RRC signaling that contains, in the form of a container, the RRC reconfiguration message for the SCG side settings described in (B), the SCG is deactivated, and when activating the SCG, the lower layer (such as the MAC entity, etc.) considers that a random access procedure is required. Whether it is set to perform BFD on the PSCell in the inactive state of the 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 in the inactive state of the SCG means that the parameter indicates performing BFD on the PSCell in the inactive state of the SCG, or the parameter may be included in the SCG side settings. Also, the above-mentioned not being set to perform BFD on the PSCell in the inactive state of the SCG means that the parameter indicates not performing BFD on the PSCell in the inactive state of the SCG, or the parameter may not be included in the SCG side settings.

[0160] Whether it is set to perform BFD on the PSCell in the inactive state of the 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 in the inactive state of the SCG means that the parameter indicates performing BFD on the PSCell in the inactive state of the SCG, or the parameter may be included in the SCG side settings. Also, the above-mentioned not being set to perform BFD on the PSCell in the inactive state of the SCG means that the parameter indicates not performing BFD on the PSCell in the inactive state of the SCG, or the parameter may not be included in the SCG side settings.

[0161] FIG. 9 is a diagram showing an example of an embodiment. In FIG. 9, the UE 122 receives signaling (RRC signaling, MAC CE, etc.) instructing to deactivate the SCG from the eNB 102 or the gNB 108 (step S900). The UE 122 controls some or all of the cells of the SCG to be in an inactive state based on the above notification (step S902). From the eNB 102 or the gNB 108, the UE 122 receives signaling (RRC signaling, MAC CE, etc.) instructing to deactivate the SCG (step S900). Based on the above notification, the UE 122 controls some or all of the cells of the SCG to be in an inactive state (step S902).

[0162] By the above operation, in the process of inactivating the SCG, the transmission unit 504 of the UE 122 can perform an efficient state change without independently transmitting a MAC CE for changing the state of the cell of the SCG to an inactive state. Further, when the inactivation 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 operation, 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.

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

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

[0165] The UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, RRC signaling, etc.) from a 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 (UCI, RRC signaling, etc.) to the base station device. The above-described 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, the MAC layer, the RLC layer, the PDCP layer, the SDAP layer, the RRC layer, and the NAS layer). That is, the processing unit 502 may include some or all of a physical layer processing unit, a MAC layer processing unit, an RLC layer processing unit, a PDCP layer processing unit, an SDAP processing unit, an RRC layer processing unit, and a NAS layer processing unit.

[0166] FIG. 6 is a block diagram showing the configuration of a base station device in the present embodiment. In order to avoid complicating the description, FIG. 6 shows only the main components closely related to the present embodiment. is shown. The above base station device may be the eNB 102 or the gNB 108.

[0167] The base station device shown in FIG. 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 122, 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.

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

[0169] FIG. 10 is a diagram showing an example of the processing of the terminal device in the present 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). Further, the processing unit 502 of the UE 122 may perform operations in the active state based on the determination (step S1002).

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

[0171] The active state may be a state in which the SCG is activated. Further, the above active state may be a state in which the SCG has resumed from the dormant state. Further, the above active state is the above SCG It may be in a state that is not the dormant state. Also, the above active state may be a state that transitions from the inactive state when a random access procedure triggered by a scheduling request for transmitting a MAC PDU containing a MAC SDU is started. Further, the above active state may be a state that transitions from the inactive state when a return from the dormant state is instructed from the RRC entity.

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

[0173] When the UE 122 receives information for activating the SCG, it may transition the SCG from the inactive state to the active state (in other words, it may activate the SCG). Also, when the UE 122 receives information instructing a return (Resume) of the SCG from the dormant state, it may transition the SCG from the inactive state to the active state. Further, when the UE 122 receives information instructing a return of the PSCell from the dormant state, it may transition the SCG from the inactive state to the active state. Also, when the UE 122 receives other information, it may transition the SCG from the inactive state to the active state. Also, the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the dormancy 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 dormancy of the PSCell. Further, when the UE 122 transmits a MAC PDU containing a MAC SDU, it may be triggered. cause a random access procedure to be started. Also, when the UE 122 receives information instructing a return of the PSCell from the dormant state, it may transition the SCG from the inactive state to the active state. Also, when the UE 122 receives other information, it may transition the SCG from the inactive state to the active state. Also, the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the dormancy 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 dormancy of the PSCell. Also, when the UE 122 transmits a MAC PDU containing a MAC SDU, When starting a random access procedure due to a scheduled scheduling request, the SCG may be transitioned from an inactive state to an active state. Also, UE122 may transition the SCG from an inactive state to an active state when starting a random access procedure. Also, UE122 may transition the SCG from an inactive state to an active state when starting a random access procedure caused by a scheduling request (in other words, initiated by the MAC entity itself). Also, the MAC entity of UE122 may obtain an instruction to activate the SCG, an instruction to resume from a dormant SCG, an instruction to resume from a dormant state of the PSCell, and / or other information from the RRC entity of UE122. Also, after the MAC entity of UE122 obtains the above information from the RRC entity, as shown in (SA-2) above, UE122 may determine that the SCG is in an active state and transition the SCG from an inactive state to an active state. When transitioning the SCG from an inactive state to an active state, UE122 may perform the processing as shown in (SA-3) above.

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

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

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

[0177] The inactive state may be a state in which the SCG is deactivated. Also, the above inactive state is It may also be the entry into the dormant SCG. Further, the above inactive state may be the dormant state of the above SCG. Also, 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 the entry from the RRC entity to the dormant state is instructed.

[0178] 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 indicated by the above (SD-2).

[0179] When the UE122 receives information instructing the inactivation of the SCG, it may transition the SCG from the active state to the inactive state. Also, when the UE122 receives information instructing the entry into the dormant SCG, it may transition the SCG from the active state to the inactive state. Also, 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, when the UE122 receives other information, it may transition the SCG from the active state to the inactive state. Also, when the timer related to the dormancy of the SCG expires, the UE122 may transition the SCG from the active state to the inactive state. Also, when the timer related to the dormancy of the PSCell expires, the UE122 may transition the SCG from the active state to the inactive state. Also, the MAC entity of the UE122 The entity may obtain an instruction to deactivate the SCG, an instruction to enter the dormant SCG, an instruction to put the PSCell into dormancy, and / or other information from the RRC entity of the UE122. Further, after the MAC entity has obtained the above information from the RRC entity, the UE122 may determine that the SCG is in an inactive state as shown in (SD-2) above, and transition the SCG from an active state to an inactive state. When transitioning the SCG from an active state to an inactive state, the UE122 may perform the processing as shown in (SD-3) above.

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

[0181] FIG. 12 is a diagram showing an example of the processing of the terminal device in this embodiment. The MAC entity 302 of the UE122 determines whether to notify the RRC entity 308 of the UE122 (step S1200), and based on the determination, notifies the RRC entity 308 (step S1202). The MAC entity 302 and the RRC entity 308 may be replaced with the MAC entity 202 and the RRC entity 208, respectively.

[0182] An example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 determines whether to notify the RRC entity 308 based on the fact that the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG has been deactivated. In this case, the notification in step S1202 may be a notification indicating a beam failure in the PSCell. If the value of the BFI_COUNTER satisfies the condition of being greater than or equal to beamFailureInstanceMaxCount and the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122.

[0183] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, the MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308 based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122 after the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount is satisfied for the last time. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0184] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122 after the SCG is deactivated and after the condition that the value of the BFI_COUNTER is greater than or equal to beamFailureInstanceMaxCount is satisfied, the MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0185] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, if the BFI_COUNTER has been set to 0 and the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122, the MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0186] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122 after the BFI_COUNTER was last set to 0, the MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0187] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122 after the SCG was deactivated and after the BFI_COUNTER was set to 0, the MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0188] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308 based on the following conditions: when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, the beamFailureDetectionTimer of the PSCell has expired, and the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0189] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308 based on the following condition: when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122 after the beamFailureDetectionTimer of the PSCell expired last time. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0190] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308 based on the fact that when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, after the SCG is deactivated and after the beamFailureDetectionTimer of the PSCell expires, the beam failure in the PSCell has not been notified to the RRC entity 308 of the UE122. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0191] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 may determine whether to notify the RRC entity 308 based on the fact that when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the setting of the BFD-RS of the PSCell have been changed by the RRC entity 308 etc. of the UE122, and the beam failure in the PSCell has not been notified to the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0192] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell in the MAC entity 302 of the UE122 is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, based on the fact that after the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the setting of the BFD-RS of the PSCell have been changed by the RRC entity 308 of the UE122 or the like, the beam failure in the PSCell has not been notified to the RRC entity 308, it may be determined whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0193] Another example of the determination in step S1200 will be described. When the value of the BFI_COUNTER of the PSCell in the MAC entity 302 of the UE122 is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, after the SCG is deactivated and after the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the setting of the BFD-RS of the PSCell have been changed by the RRC entity 308 of the UE122 or the like, based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308, it may be determined whether to notify the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0194] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE122 is PS Cell's BFI_COUNTER value is greater than or equal to beamFailureInstanceMaxCount and the SCG is inactive When it has been configured, the RRC entity 308 of the UE 122 may determine whether to notify the RRC entity 308 based on the fact that the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the configuration change of the BFD-RS of the PSCell have been notified to the RRC entity 308 of the UE 122, and the beam failure in the PSCell has not been notified to the RRC entity 308. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0195] Another example of the determination in step S1200 will be described. The MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 based on the fact that the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, and the beam failure in the PSCell has not been notified to the RRC entity 308 after the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or the configuration change of the BFD-RS of the PSCell have been notified to the RRC entity 308 of the UE 122. In this case, the notification in step S1202 may be a notification indicating the beam failure in the PSCell.

[0196] Another example of the determination in step S1200 will be described. When the value of BFI_COUNTER of the PSCell is equal to or greater than beamFailureInstanceMaxCount and the SCG is deactivated, the MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 based on the fact that the beam failure in the PSCell has not been notified to the RRC entity 308 since the SCG was deactivated and since the RRC entity 308 of the UE 122 notified the change in the beamFailureDetectionTimer, beamFailureInstanceMaxCount, and / or BFD-RS settings of the PSCell. In this case, the notification in step S1202 may be a notification indicating a beam failure in the PSCell.

[0197] In the above explanation, the change in the BFD-RS setting of the PSCell when the SCG is inactive is based on the radio link model included in the message regarding the reconfiguration of the RRC connection, including the settings on the SCG side. This may be done using the monitoring configuration or the TCI information element. "Change in settings" may be rephrased as "resetting," and "settings are changed" may be rephrased as "resetting."

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

[0199] 13 is a diagram showing an example of processing of a terminal device in this embodiment. The RRC entity 308 of the UE 122 determines whether to perform an operation (step S1300), and performs an operation based on the determination (step S1302). The RRC entity 308 may be replaced with the RRC entity 208.

[0200] An example of the determination in step S1300 will be described. Based on the notification indicating beam failure in the PSCell being notified during the inactive state of the SCG from the MAC entity 302, it may be determined whether to perform an operation. In this case, the operation in step S1302 may be to start transmitting E-UTRA RRC signaling indicating SCG failure information (SCGFailureInformationNR) to the eNB 102 if the UE 122 is within (NG) EN-DC, or otherwise, to start transmitting NR RRC signaling indicating SCG failure information (SCGFailureInformation) to the gNB 108.

[0201] Thus, in this embodiment, when the value of the BFI_COUNTER of the PSCell of the UE MAC entity is greater than or equal to beamFailureInstanceMaxCount, and the SCG is deactivated, and the condition that the value of the BFI_COUNTER is greater than or equal to the beamFailureInstanceMaxCount is satisfied, and it is determined that the beam failure in the PSCell has not been notified to the RRC entity, a notification indicating the beam failure in the PSCell can be notified to the RRC entity. Thereby, even when a beam failure in the PSCell is detected for the second time or later after the SCG is deactivated, it can be notified to the RRC entity, and necessary signaling can be efficiently performed.

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

[0203] Also, in the above description, expressions such as "notified" and "received an indication" may be paraphrased with each other.

[0204] Also, in the above description, expressions such as "associate", "correlate", and "relate" may be paraphrased with each other.

[0205] In the above description, expressions such as "included", "being included", and "having been included" may be paraphrased with each other.

[0206] In the above description, "the above-mentioned ~" may be paraphrased as "the ~".

[0207] In the above description, "the SpCell of SCG" may be paraphrased as "PSCell".

[0208] In the above description, expressions such as "determined as ~", "set as ~", and "included ~" may be paraphrased with each other.

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

[0210] In the above description, "transition from X to Y" may be paraphrased as "become from X to Y". Also, in the above description, "cause to transition" may be paraphrased as "determine the transition".

[0211] In the examples of each process or the examples of each process flow 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 each process flow in the above description, the order of the steps may be different. Also, in the examples of each process or the examples of each process flow 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 each process flow in the above description, the order of the processes within each step may be different. Also, in the above description, "perform B based on the fact that A" may be paraphrased as "perform B". That is, the act of "performing B" may be executed independently of "the fact that A".

[0212] In the above description, "A may be rephrased as B" may include, in addition to rephrasing A as B, 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 also be included. Further, in the above description, when "F may be G" and "G may be H" are described, "F may be H" may also be included.

[0213] 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".

[0214] The program that operates on the device according to this embodiment may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of this embodiment. The program or the information handled by the program is 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 by the CPU as needed for modification and writing.

[0215] Note that a part of the device in the above-described embodiment may be realized by a computer. In that case, the 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 and including hardware such as an operating system and peripheral devices. Also, the "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0216] Furthermore, the "computer-readable recording medium" may include those that hold a program dynamically for a short time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system serving as a server or a client in that case. Also, the above program may be for realizing a part of the aforementioned functions, and furthermore, it may be capable of realizing the aforementioned functions in combination with a program already recorded in the computer system.

[0217] Also, each functional block or various features of the device used in the above-described embodiments 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 may include a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose use processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose use processor or each of the above-described circuits may be composed of a digital circuit or an analog circuit. Also, when a technology for integrating circuits 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.

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

[0219] As described above with reference to the drawings in detail regarding this embodiment, 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. Further, configurations in which elements described in the above embodiment and having the same effects are replaced with each other are also included.

Explanation of Reference Numerals

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

Claims

1. A terminal device that communicates with a base station device, a processing unit that communicates using MCG and SCG, a transmission unit that transmits signaling to the base station device, comprising: the SCG includes at least a PSCell, the processing unit executes processing in the MAC entity and processing in the RRC entity, the MAC entity, when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, determines whether the condition that the value of the BFI_COUNTER is greater than or equal to the beamFailureInstanceMaxCount is satisfied, and whether the beam failure in the PSCell has been reported to the RRC entity, if it is determined that the condition that the value of the BFI_COUNTER is greater than or equal to the beamFailureInstanceMaxCount is satisfied and the beam failure in the PSCell has not been reported to the RRC entity, notifies the RRC entity of a notification indicating the beam failure in the PSCell, the RRC entity, determines whether the notification has been notified from the MAC entity, based on the determination that the notification has been notified from the MAC entity, starts transmitting signaling indicating SCG failure information to the base station device, a terminal device.

2. A method for a terminal device that communicates with a base station device, communicating using MCG and SCG, the SCG includes at least a PSCell, the MAC entity of the terminal device, when the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, determines whether the condition that the value of the BFI_COUNTER is greater than or equal to the beamFailureInstanceMaxCount is satisfied, and whether the beam failure in the PSCell has been reported to the RRC entity of the terminal device, The value of the BFI_COUNTER satisfies the condition of being greater than or equal to the beamFailureInstanceMaxCount, and based on the determination that the beam failure in the PSCell has not been notified to the RRC entity, based on this, notify the RRC entity of a notification indicating the beam failure in the PSCell, the RRC entity, determines from the MAC entity whether the notification has been notified, based on the determination from the MAC entity that the notification has been notified, start transmitting signaling indicating SCG failure information to the base station apparatus, method.

3. An integrated circuit implemented in a terminal device that communicates with a base station apparatus, communicates using MCG and SCG, the SCG includes at least a PSCell, the integrated circuit, when the MAC entity of the terminal device, the value of the BFI_COUNTER of the PSCell is greater than or equal to beamFailureInstanceMaxCount and the SCG is deactivated, determines whether the value of the BFI_COUNTER satisfies the condition of being greater than or equal to the beamFailureInstanceMaxCount, and whether the beam failure in the PSCell has been notified to the RRC entity of the terminal device, and determines whether the beam failure in the PSCell has been notified to the RRC entity, The value of the BFI_COUNTER satisfies the condition of being greater than or equal to the beamFailureInstanceMaxCount, and based on the determination that the beam failure in the PSCell has not been notified to the RRC entity, based on this, notify the RRC entity of a notification indicating the beam failure in the PSCell, the RRC entity, determines from the MAC entity whether the notification has been notified, based on the determination from the MAC entity that the notification has been notified, causes the terminal device to exhibit a function of starting to transmit signaling indicating SCG failure information to the base station apparatus, integrated circuit.

Images