Terminal device, method, and integrated circuit

Abstract

In a terminal device that communicates with a base station device, an RRC layer processing unit notifies a MAC layer processing unit on the basis of information that is included in RRC signaling and that indicates whether or not beam failure detection is performed in a PSCell of a disabled SCG, the MAC layer processing unit determines whether or not a condition is satisfied in which the RRC layer processing unit notifies that BFD is stopped in the PSCell of the disabled SCG, and performs BFD detection on the PSCell of the disabled SCG. When it is determined that the condition is satisfied, the beam failure detection timer is stopped, and when it is determined that the condition is not satisfied, the beam failure detection timer is not stopped, the beam failure detection timer being a timer started or restarted on the basis of the reception of the first notification from the PHY layer processing unit, and the beam failure detection timer being a timer restarted on the basis of the reception of the second notification from the PHY layer processing unit. The MAC layer processing unit sets the value of the first counter to zero on the basis of expiration of the beam failure detection timer.

Description

Technical Field

[0001] The present invention relates to a terminal device, a method and an integrated circuit. This application claims priority to Japanese Patent Application No. 2022-91573 filed in Japan on June 6, 2022, the contents of which are incorporated herein by reference. Background Art

[0002] In the 3rd Generation Partnership Project (3GPP, registered trademark), which is a cellular mobile communication system standardization project, technical research and specification formulation of cellular mobile communication systems including radio access, core network, services, etc. are being conducted.

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

[0004] In addition, 3GPP has started technical research and standardization of NR (New Radio or NR Radio access) as a radio access technology (Radio Access Technology: RAT) for cellular mobile communication systems for the 5th Generation (5G). Currently, 3GPP is also conducting technical research and standardization of NR extension technologies. Prior art literature Non-patent literature

[0005] Non-patent document 1: 3GPP TS 38.300v16.4.0, “NR; NR and NG-RAN Overall description; Stage 2” pp10-134 Non-patent document 2: 3GPP TS 36.300v16.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.331v16.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.321v16.3.0, "NR; Medium Access Control (MAC) protocol specification" pp8-152 Non-patent document 7: 3GPP TS 38.331v17.0.0, “NR; Radio Resource Control (RRC); Protocol specifications” Non-patent document 8: 3GPP TS 38.321v17.0.0, “NR; Medium Access Control (MAC) protocol specification” Non-Patent Document 9: R2-2204401, Draft_R2-117e_Meeting_Report_v1, "Report of 3GPP TSG RAN WG2 meeting#117-e" Summary of the invention Problem that the invention aims to solve

[0006] As an extension technology of NR, in order to enable large-capacity data communications, there is a dual connection (also called multi-connection) technology that uses multiple cell groups to communicate with one or more base station devices and terminal devices. In this dual connection, in order to communicate in each cell group, the terminal device needs to monitor each cell group for messages destined for itself. In order to enable the terminal device to communicate with low latency when large-capacity data communications are generated, the terminal device needs to monitor multiple cell groups at all times, which poses a problem of high power consumption. Therefore, research has begun on a technology that performs or stops monitoring of a portion of cell groups at a low frequency (cell group deactivated technology).

[0007] Non-patent documents 7 and 8 are RRC and MAC specifications that were created based on the matters that have been agreed upon so far. However, there are still problems in order to perform efficient communication control processing.

[0008] An aspect of the present invention has been made in view of the above-mentioned situation, and one of its objects is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can efficiently perform communication control. Technical Solution

[0009] In order to achieve the above-mentioned purpose, one scheme of the present invention adopts the following scheme. That is, one scheme of the present invention is a terminal device that communicates with a base station device, the terminal device comprising: a processing unit that uses MCG and SCG to communicate; and a receiving unit that receives Radio Resource Control (RRC) signaling from the base station device, the SCG includes a PSCell, the processing unit performs beam failure detection (BFD) in the PSCell based on the RRC signaling, based on the setting that beam failure detection (BFD) is performed in the PSCell of the disabled SCG, starts or restarts a beam failure detection timer based on receiving a beam failure instance notification from a PHY layer, and determines whether the BFD is stopped when the beam failure detection timer expires, does not set the beam failure counter to 0 when it is determined that the BFD is stopped, and sets the beam failure counter to 0 when it is determined that the BFD is not stopped.

[0010] In addition, one scheme of the present invention is a method of a terminal device, wherein the terminal device communicates with a base station device, in which method, MCG and SCG are used for communication, and Radio Resource Control (RRC) signaling is received from the base station device, and the SCG includes at least PSCell, and the method includes the following steps: through the RRC signaling, based on the PSCell set to perform beam failure detection (BFD) in the SCG that is disabled, BFD is performed in the PSCell; based on receiving a beam failure instance notification from the PHY layer, starting or restarting a beam failure detection timer; when the beam failure detection timer expires, determining whether the BFD is stopped; when it is determined that the BFD is stopped, not setting the beam failure counter to 0; and when it is determined that the BFD is not stopped, setting the beam failure counter to 0.

[0011] In addition, one scheme of the present invention is an integrated circuit installed in a terminal device that communicates with a base station device, and the integrated circuit performs the following functions: uses MCG and SCG to communicate; receives Radio Resource Control (RRC) signaling from the base station device; the SCG includes at least a PSCell, and through the RRC signaling, based on the PSCell being set to perform beam failure detection (BFD) in the SCG that is disabled, BFD is performed in the PSCell; based on receiving a beam failure instance notification from the PHY layer, starts or restarts a beam failure detection timer; when the beam failure detection timer expires, determines whether the BFD is stopped; when it is determined that the BFD is stopped, does not set the beam failure counter to 0; and when it is determined that the BFD is not stopped, sets the beam failure counter to 0.

[0012] It should be noted that these inclusive or specific solutions can be implemented through systems, devices, methods, integrated circuits, computer programs or recording media, or through any combination of systems, devices, methods, integrated circuits, computer programs and recording media. Beneficial Effects

[0013] According to one aspect of the present invention, a terminal device, a method, and an integrated circuit can implement efficient communication control processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a schematic diagram of the communication system according to this embodiment. Figure 2 This is a diagram showing an example of the E-UTRA protocol configuration according to this embodiment. Figure 3 This is a diagram showing an example of the NR protocol configuration of this embodiment. Figure 4 This is a diagram showing an example of the flow of procedures for various settings in RRC according to the present embodiment. Figure 5 This is a block diagram showing the configuration of a terminal device according to this embodiment. Figure 6 It is a block diagram showing the configuration of a base station apparatus according to this embodiment. Figure 7 This is an example of an ASN.1 representation included in a message related to RRC connection re-establishment in NR of this embodiment. Figure 8 This is an example of an ASN.1 expression included in a message related to RRC connection re-establishment in E-UTRA according to the present embodiment. Fig. 9 This is an example of processing related to disabling of SCG in this embodiment. Fig.10 This is an example of processing related to activation of SCG in this embodiment. Fig.11 This is an example of processing related to disabling of SCG in this embodiment. Fig.12 This is an example of processing performed by the terminal device in this embodiment. DETAILED DESCRIPTION

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

[0016] LTE (as well as LTE-A, LTE-A Pro) and NR can be defined as different radio access technologies (Radio Access Technology: RAT). In addition, NR can also be defined as a technology included in LTE. In addition, LTE can also be defined as a technology included in NR. In addition, LTE that can be connected to NR through multi-radio dual connectivity (Multi-Radio Dual Connectivity: MR-DC) can be distinguished from existing LTE. In addition, LTE using 5GC in the core network (Core Network: CN) can be distinguished from existing LTE using EPC in the core network. It should be noted that the existing LTE may refer to LTE that does not implement technologies standardized after Release 15 of 3GPP. This embodiment can be applied to NR, LTE, and other RATs. In the following description, terms associated with LTE and NR are used for description, but this embodiment can also be applied to other technologies using other terms. In addition, in this embodiment, the term E-UTRA can be replaced with the term LTE, and the term LTE can be replaced with the term E-UTRA.

[0017] It should be noted that in this embodiment, the name of each node or entity and the processing in each node or entity are described when the radio access technology is E-UTRA or NR, but this embodiment can be used for other radio access technologies. The name of each node or entity in this embodiment can be other names.

[0018] Figure 1 is a schematic diagram of the communication system of this embodiment. Figure 1 The functions of each node, wireless access technology, core network, interface, etc. described are part of the functions closely related to this embodiment and may have other functions.

[0019] E-UTRA100 may be a radio access technology. In addition, E-UTRA100 may be an air interface between UE122 and eNB102. The air interface between UE122 and eNB102 may be referred to as a Uu interface. eNB (E-UTRANNode B: E-UTRAN Node B) 102 may be a base station device of E-UTRA100. eNB102 may have an E-UTRA protocol described later. The E-UTRA protocol may be composed of an E-UTRA user plane (User Plane: UP) protocol described later and an E-UTRA control plane (Control Plane: CP) protocol described later. For UE122, eNB102 may terminate the E-UTRA user plane (UserPlane: UP) protocol and the E-UTRA control plane (Control Plane: CP) protocol. The radio access network composed of eNBs may also be referred to as E-UTRAN.

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

[0021] It should be noted that one or more eNBs 102 may be connected to the EPC 104 via the interface 112. An interface (not shown) may exist between the multiple eNBs 102 connected to the EPC 104. The interface between the multiple eNBs 102 connected to the EPC 104 may be called an X2 interface.

[0022] NR106 can be a radio access technology. In addition, NR106 can be an air interface between UE122 and gNB108. The air interface between UE122 and gNB108 can be called a Uu interface. gNB (g Node B: g node B) 108 can be a base station device of NR106. gNB108 can have the NR protocol described later. The NR protocol can be composed of the NR user plane (User Plane: UP) protocol described later and the NR control plane (Control Plane: CP) protocol described later. For UE122, gNB108 can terminate the NR user plane (User Plane: UP) protocol and the NR control plane (Control Plane: CP) protocol.

[0023] 5GC110 can be a core network. Interface 116 is an interface between gNB108 and 5GC110, which can be called an NG interface. Interface 116 may contain a control plane interface for control signals to pass through and / or a user plane interface for user data to pass through. The control plane interface of interface 116 can terminate at the access and mobility management function (Accessand mobility Management Function: AMF, not shown) within 5GC110. The user plane interface of interface 116 can terminate at the user plane function (User Plane Function: UPF, not shown) within 5GC110. The control plane interface of interface 116 can be called an NG-C interface. The user plane interface of interface 116 can be called an NG-U interface.

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

[0025] eNB102 may have a function of connecting to 5GC110. eNB102 having a function of connecting to 5GC110 may be referred to as ng-eNB. Interface 114 is an interface between eNB102 and 5GC110, and may be referred to as an NG interface. Interface 114 may include a control plane interface for control signals to pass through and / or a user plane interface for user data to pass through. The control plane interface of interface 114 may terminate at the AMF within 5GC110. The user plane interface of interface 114 may terminate at the UPF within 5GC110. The control plane interface of interface 114 may be referred to as an NG-C interface. The user plane interface of interface 114 may be referred to as an NG-U interface. A radio access network composed of ng-eNB or gNB may also be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may also be referred to as a network. In addition, a network may include eNB, ng-eNB, gNB, etc.

[0026] It should be noted that one or more eNBs 102 may be connected to 5GC 110 via interface 114. An interface (not shown) may exist between multiple eNBs 102 connected to 5GC 110. The interface between multiple eNBs 102 connected to 5GC 110 may be referred to as an Xn interface. In addition, the eNB 102 connected to 5GC 110 and the gNB 108 connected to 5GC 110 may be connected via interface 120. The interface 120 between the eNB 102 connected to 5GC 110 and the gNB 108 connected to 5GC 110 may be referred to as an Xn interface.

[0027] gNB108 may have a function of connecting to EPC104. gNB108 having a function of connecting to EPC104 may be referred to as en-gNB. Interface 118 is an interface between gNB108 and EPC104, and may be referred to as an S1 interface. There may be a user plane interface in interface 118 for user data to pass through. The user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC104. The user plane interface of interface 118 may be referred to as an S1-U interface. In addition, eNB102 connected to EPC104 and gNB108 connected to EPC104 may be connected via interface 120. Interface 120 between eNB102 connected to EPC104 and gNB108 connected to EPC104 may be referred to as an X2 interface.

[0028] Interface 124 is an interface between EPC 104 and 5GC 110, and may be an interface through CP only, UP only, or both CP and UP. In addition, depending on the communication system provided by a communication operator, some or all of interfaces 114, 116, 118, 120, and 124 may not exist.

[0029] UE122 may be a terminal device that can receive system information and paging messages sent from eNB102 and / or gNB108. In addition, UE122 may be a terminal device that can establish a wireless connection with eNB102 and / or gNB108. In addition, UE122 may be a terminal device that can establish a wireless connection with eNB102 and a wireless connection with gNB108 at the same time. UE122 may have an E-UTRA protocol and / or an NR protocol. It should be noted that a wireless connection may refer to a Radio Resource Control (RRC) connection.

[0030] In addition, UE122 can be a terminal device that can connect to EPC104 and / or 5GC110 via eNB102 and / or gNB108. When the connection destination core network of eNB102 and / or gNB108 with which UE122 communicates is EPC104, each data radio bearer (DRB: Data Radio Bearer) established between UE122 and eNB102 and / or gNB108 described later can be further uniquely associated with each EPS (Evolved Packet System: Evolved Packet System) bearer via EPC104. Each EPS bearer can be identified by an EPS bearer identifier (Identity or ID). In addition, the same QoS (Quality of Service) can be guaranteed for data such as IP packets, Ethernet (registered trademark) frames, etc. carried by the same EPS bearer.

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

[0032] There may be no PDU session and / or QoS flow in EPC104. In addition, there may be no EPS bearer in 5GC110. When UE122 is connected to EPC104, UE122 has information of EPS bearer, but may not have information in PDU session and / or QoS flow. In addition, when UE122 is connected to 5GC110, UE122 has information in PDU session and / or QoS flow, but may not have information in EPS bearer.

[0033] It should be noted that in the following description, eNB102 and / or gNB108 are also referred to as base station devices, and UE122 is also referred to as terminal devices or UE.

[0034] Figure 2 is a diagram showing an example of the E-UTRA protocol architecture of this embodiment. Figure 3 is a diagram of an example of the NR protocol configuration of this embodiment. Figure 2 and / or Figure 3 The functions of each protocol described are part of the functions closely related to this embodiment, and may have other functions. It should be noted that in this embodiment, uplink (UL) may refer to a link from a terminal device to a base station device. In addition, in this embodiment, downlink (DL) may refer to a link from a base station device to a terminal device.

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

[0036] Figure 3 (A) is a diagram of the NR user plane (UP) protocol stack. Figure 3 As shown in (A), the NR UP protocol may be a protocol between UE 122 and gNB 108. That is, the NR UP protocol may be a protocol terminated at gNB 108 on the network side. Figure 3 As shown in (A), the NR user plane protocol stack can be composed of PHY300 as the wireless physical layer, MAC302 as the media access control layer, RLC304 as the radio link control layer, PDCP306 as the packet data convergence protocol layer, and SDAP (Service Data Adaptation Protocol) 310 as the service data adaptation protocol layer (Service Data Adaptation Protocol layer).

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

[0038] Figure 3 (B) is a diagram of the NR control plane (CP) protocol. Figure 3 As shown in (B), in the NR CP protocol, RRC308 as a radio resource control layer may be a protocol between UE122 and gNB108. That is, RRC308 may be a protocol terminated at gNB108 on the network side. In addition, in the NR CP protocol, NAS312 as a non-AS layer may be a protocol between UE122 and AMF. That is, NAS312 may be a protocol terminated at AMF on the network side.

[0039] It should be noted that the AS (Access Stratum) layer may refer to a layer terminated between the UE 122 and the eNB 102 and / or the gNB 108. That is, the AS layer may refer to a layer including a part or all of PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 and / or a layer including a part or all of PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308.

[0040] It should be noted that in this embodiment, the terms PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) are sometimes used below without distinguishing between the E-UTRA protocol and the NR protocol. In this case, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), and NAS (NAS layer) can 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. In addition, SDAP (SDAP layer) can be the SDAP (SDAP layer) of the NR protocol.

[0041] In addition, in the present embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, 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. In addition, PHY200, MAC202, RLC204, PDCP206, and RRC208 are sometimes referred to as E-UTRAPHY or LTE PHY, E-UTRA MAC or LTE MAC, E-UTRA RLC or LTE RLC, E-UTRA PDCP or LTE PDCP, and E-UTRA RRC or LTE RRC, respectively. In addition, when distinguishing between the E-UTRA protocol and the NR protocol, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes referred to as NR PHY, NR MAC, NR RLC, NR RLC, and NR RRC, respectively. In addition, PHY300, MAC302, RLC304, PDCP306, and RRC308 are sometimes referred to as NR PHY, NR MAC, NR RLC, NR PDCP, and NR RRC, respectively.

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

[0043] It should be noted that the data provided from MAC, RLC, PDCP, SDAP to the lower layer and / or the data provided from the lower layer to MAC, RLC, PDCP, SDAP can be respectively referred to as MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, SDAP PDU. In addition, the data provided from the upper layer to MAC, RLC, PDCP, SDAP and / or the data provided from MAC, RLC, PDCP, SDAP to the upper layer can be respectively referred to as MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, SDAP SDU. In addition, the segmented RLC SDU can be referred to as an RLC SDU segment.

[0044] Here, the base station device and the terminal device exchange (transmit and receive) signals in the upper layer (upper layer: higher layer). For example, the base station device and the terminal device can transmit and receive RRC messages (also called RRC message, RRC information: RRC information, RRC signalling: RRC signaling) in the radio resource control (RRC: Radio Resource Control) layer. In addition, the base station device and the terminal device can also transmit and receive MAC control elements in the MAC (Medium Access Control) layer. In addition, the RRC layer of the terminal device obtains system information broadcast from the base station device. Here, RRC messages, system information and / or MAC control elements are also referred to as upper layer signals (upper layer signals: higher layer signaling) or upper layer parameters (upper layer parameters: higher layer parameters). The parameters included in the upper layer signal received by the terminal device can be respectively referred to as upper layer parameters. In the processing of the PHY layer, the upper layer means the upper layer observed from the PHY layer, and therefore, it can also 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, the RLC layer, the PDCP layer, the NAS layer, and the like. In the following, "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" may mean that the upper layer of the terminal device (mainly the RRC layer, the MAC layer, etc.) receives A from the base station device, and gives (provides) the received A from the upper layer of the terminal device to the physical layer of the terminal device. For example, in the terminal device, "providing upper layer parameters" may mean that an upper layer signal is received from the base station device, and the upper layer parameters included in the received upper layer signal are provided from the upper layer of the terminal device to the physical layer of the terminal device. Setting upper layer parameters for the terminal device may mean giving (providing) upper layer parameters to the terminal device. For example, setting upper layer parameters for 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 parameters in the upper layer. Among them, setting upper layer parameters for the terminal device may include setting default parameters for the upper layer provided in advance to the terminal device. When explaining the transmission of an RRC message from a terminal device to a base station device, the expression "submitting a message to a lower layer" from the RRC entity of the terminal device may be used. In the terminal device, "submitting a message to a lower layer" from the RRC entity may also mean submitting a message to the PDCP layer.Since SRB (Signaling Radio Bearer) (SRB0, SRB1, SRB2, SRB3, etc.) is used to send RRC messages, "submitting a message to the lower layer" from the RRC layer in the terminal device may also mean submitting an RRC message 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 also mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, etc.

[0045] An example of the function of PHY is described. The PHY of the terminal device may have the function of receiving data transmitted via a downlink (Downlink: DL) physical channel (Physical Channel) from the PHY of the base station device. The PHY of the terminal device may have the function of sending data to the PHY of the base station device via an uplink (Uplink: UL) physical channel. The PHY can be connected to the upper MAC through a transport channel (Transport Channel). The PHY can deliver data to the MAC via the transport channel. In addition, the PHY can provide data from the MAC via the transport channel. RNTI (Radio Network Temporary Identifier: Radio Network Temporary Identifier) ​​can be used in the PHY to identify various control information.

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

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

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

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

[0050] PDCCH can be used to send (or transport) downlink control information (Downlink Control Information: DCI) in downlink wireless communication (wireless communication from a base station device to a terminal device). Here, one or more DCIs (also referred to as DCI formats) can be defined for the transmission of downlink control information. That is, the field for the downlink control information can be defined as DCI and mapped to information bits. PDCCH can be sent in a PDCCH candidate. The terminal device can monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. In addition, the terminal device may use CORESET (Control Resource Set: control resource set) to monitor a set of PDCCH candidates. The DCI format can also be used for scheduling PUSCH in a serving cell. PUSCH can be used for sending user data, sending RRC messages described later, and the like.

[0051] PUCCH can be used to send uplink control information (Uplink Control Information: UCI) in uplink wireless communication (wireless communication from a terminal device to a base station device). Here, the uplink control information may include channel state information (CSI: Channel State Information) for indicating the state of a downlink channel. In addition, the uplink control information may also include a scheduling request (SR: Scheduling Request) for requesting UL-SCH (UL-SCH: Uplink Shared CHannel (uplink shared channel)) resources. In addition, the uplink control information may also include HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement: Hybrid Automatic Repeat Request Acknowledgement).

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

[0053] PUSCH can be used to send uplink data (UL-SCH: Uplink SharedCHannel) from the MAC layer or to send HARQ-ACK and / or CSI together with the uplink data. In addition, PUSCH can also be used to send only CSI or only HARQ-ACK and CSI. That is, PUSCH can also be used to send only UCI. In addition, PDSCH or PUSCH can also be used to send RRC signaling (also called RRC message) and MAC CE. Here, in PDSCH, the RRC signaling sent from the base station device can be signaling shared by multiple terminal devices in the cell. In addition, the RRC signaling sent from the base station device can also be signaling dedicated to a certain terminal device (also called dedicated signaling). That is, terminal device-specific (UE-specific) information can also be sent using signaling dedicated to a certain terminal device. In addition, PUSCH can be used to send UE capabilities (UE Capability) in the uplink.

[0054] PRACH can be used to send a random access preamble. PRACH can be used to indicate the initial connection establishment procedure, the handover procedure, the connection re-establishment procedure, the synchronization (timing adjustment) for uplink transmission, and the request for UL-SCH resources.

[0055] An example of the function of MAC is described. MAC can be called a MAC sublayer (sublayer). MAC can have the function of mapping multiple logical channels (logical channels: Logical Channel) to the corresponding transmission channels. Logical channels can be identified by logical channel identifiers (Logical Channel Identity or Logical Channel ID). MAC can be connected to the upper RLC through logical channels (Logical Channel). Logical channels can be divided into control channels for transmitting control information and service channels for transmitting user information according to the type of information transmitted. In addition, logical channels can be divided into uplink logical channels and downlink logical channels. MAC can have the function of multiplexing MAC SDUs belonging to one or more different logical channels and providing them to PHY. In addition, MAC can also have the function of demultiplexing MAC PDUs provided from PHY and providing them to the upper layer via the logical channels to which each MAC SDU belongs. In addition, MAC can also have the function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). In addition, MAC may have a Scheduling Report (SR) function for reporting scheduling information (schedulinginformation). MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. In addition, MAC may also have a function of performing priority processing between logical channels within a terminal device. MAC may also have a function of performing priority processing of overlapping resources within a terminal device. E-UTRA MAC may have a function of identifying Multimedia Broadcast Multicast Services (MBMS). In addition, NR MAC may also have a function of identifying multicast / broadcast services (MBS). MAC may have a function of selecting a transmission format. MAC may have a function of performing discontinuous reception (DRX) and / or discontinuous transmission (DTX), a function of performing a random access (RA) process, a power headroom report (PHR) function for notifying information on the transmittable power, a buffer status report (BSR) function for notifying information on the amount of data buffered for transmission, and the like.NR MAC may have a bandwidth adaptation (BA) function. In addition, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. In addition, the MAC PDU may include a MAC control element (MAC Control Element: MAC CE) which is an element for controlling in MAC.

[0056] The following describes logical channels for uplink (UL: Uplink) and / or downlink (DL: Downlink) used in E-UTRA and / or NR.

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

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

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

[0060] DCCH (Dedicated Control Channel) can be a logical channel used to send dedicated control information in a point-to-point bidirectional manner between a terminal device and a base station device. Dedicated control information can refer to control information dedicated to each terminal device. DCCH can also be used when the terminal device has an RRC connection.

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

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

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

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

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

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

[0067] The BCCH may be mapped to a BCH (Broadcast Channel) and / or a DL-SCH (Downlink Shared Channel) which are downlink transmission channels.

[0068] The PCCH can be mapped to the PCH (Paging Channel) which is a downlink transmission channel.

[0069] The CCCH can be mapped to the DL-SCH (Downlink Shared Channel) which is a downlink transmission channel.

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

[0071] DTCH can also be mapped to DL-SCH (Downlink Shared Channel) which is a downlink transmission channel.

[0072] An example of the function of RLC is described. RLC may also be referred to as an RLC sublayer (sublayer). E-UTRA RLC may have a function of segmenting (Segmentation) and / or concatenating (Concatenation) the data provided from the upper layer PDCP and providing it to the lower layer (lower layer). E-UTRA RLC may have a function of reassembling (reassembling) and reordering (re-ordering) the data provided from the lower layer and providing it to the upper layer. NR RLC may have a function of attaching a sequence number independent of the sequence number attached in the PDCP to the data provided from the upper layer PDCP. In addition, NR RLC may also have a function of segmenting (Segmentation) the data provided from the PDCP and providing it to the lower layer. In addition, NR RLC may also have a function of reassembling (reassembling) the data provided from the lower layer and providing it to the upper layer. In addition, RLC may have a data retransmission function and / or a retransmission request function (Automatic Repeat reQuest: ARQ). In addition, RLC may also have a function of performing error correction through ARQ. The control information indicating the data that needs to be retransmitted and sent from the receiving side of the RLC to the sending side for ARQ can be called a status report. In addition, the status report sending indication sent from the sending side of the RLC to the receiving side can be called a poll. In addition, the RLC can also have the function of detecting data duplication. In addition, the RLC can also have the function of discarding data. There can be three modes in the RLC: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Under TM, the data received from the upper layer may not be segmented, and the RLC header may not be attached. The TM RLC entity may be a uni-directional entity, set as a transmitting TM RLC entity or a receiving TM RLC entity. In UM, the data received from the upper layer is segmented and / or concatenated, the RLC header is attached, etc., but the data retransmission control may not be performed. The UM RLC entity may be a uni-directional 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 bidirectional entity, the UM RLC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.In AM, segmentation and / or concatenation of data received from the upper layer, attachment of RLC headers, and data retransmission control can be performed. The AM RLC entity can be a bidirectional entity, which is set as an AM RLC consisting of a transmitting side and a receiving side. It should be noted that the data provided to the lower layer and / or the data provided from the lower layer in TM can be called TMD PDU. In addition, the data provided to the lower layer and / or the data provided from the lower layer in UM can be called UMD PDU. In addition, the data provided to the lower layer or the data provided from the lower layer in AM can be called AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC can be different. In addition, the RLC PDU can include RLC PDU for data and RLC PDU for control. The RLC PDU for data can be called RLC DATA PDU (RLC Data PDU, RLC data PDU). In addition, the control RLC PDU can be called RLC CONTROL PDU (RLC Control PDU, RLC control PDU, RLC control PDU).

[0073] An example of the function of PDCP is described. PDCP may also be referred to as a PDCP sublayer (sublayer). PDCP may have a function of maintaining a sequence number. In addition, PDCP may also have a header compression / decompression function for efficiently transmitting user data such as IP packets (IP Packets) and Ethernet frames in a wireless section. The protocol for header compression / decompression of IP packets may be referred to as the ROHC (Robust Header Compression) protocol. In addition, the protocol for Ethernet frame header compression / decompression may be referred to as the EHC (Ethernet (registered trademark) Header Compression: Ethernet Header Compression) protocol. In addition, PDCP may also have a data encryption / decoding function. In addition, PDCP may also have a data integrity protection / integrity verification function. In addition, PDCP may also have a reordering function. In addition, PDCP may also have a PDCP SDU retransmission function. In addition, PDCP may also have a data discarding function using a discard timer. In addition, PDCP may also have a multiplexing function. In addition, PDCP may also have a function of discarding duplicated received data. The PDCP entity can be a bidirectional entity, consisting of a transmitting PDCP entity and a receiving PDCP entity. In addition, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. In addition, the PDCP PDU may include a PDCP PDU for data and a PDCP PDU for control. The PDCP PDU for data may be referred to as a PDCP DATA PDU (PDCPData PDU, PDCP data PDU). In addition, the PDCP PDU for control may be referred to as a PDCP CONTROL PDU (PDCPControl PDU, PDCP control PDU, PDCP control PDU).

[0074] An example of the function of SDAP is described. SDAP is the service data adaptation protocol layer. SDAP may have the function of corresponding (mapping: mapping) the QoS flow of the downlink sent from 5GC110 to the terminal device via the base station device and the data radio bearer (DRB) and / or the mapping of the QoS flow of the uplink sent from the terminal device to 5GC110 via the base station device and the DRB. In addition, SDAP may also have the function of storing mapping rule information. In addition, SDAP may also have the function of marking the QoS flow identifier (QoS Flow ID: QFI). It should be noted that there may be SDAP PDU for data and SDAP PDU for control in the SDAP PDU. The SDAP PDU for data may be referred to as SDAP DATA PDU (SDAP Data PDU, SDAP data PDU). In addition, the SDAPPDU for control may be referred to as SDAP CONTROL PDU (SDAP Control PDU, SDAP control PDU, SDAP control PDU). It should be noted that the SDAP entity of the terminal device may exist for one PDU session.

[0075] An example of the functions of RRC is described. RRC may have a broadcast (broadcast: broadcast) function. RRC may have a paging (paging: Paging) function from EPC104 and / or 5GC110. RRC may have a paging (paging: Paging) function from eNB102 connected to gNB108 or 5GC110. In addition, RRC may also have an RRC connection management function. In addition, RRC may also have a radio bearer control function. In addition, RRC may also have a cell group control function. In addition, RRC may also have a mobility control function. In addition, RRC may also have a terminal device measurement report and a terminal device measurement report control function. In addition, RRC may also have a QoS management function. In addition, RRC may also have a radio link failure detection and recovery function. RRC may use RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement report and terminal device measurement report control, QoS management, detection and recovery of radio link failure, etc. It should be noted that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.

[0076] The RRC message can be sent using the BCCH of the logical channel, the PCCH of the logical channel, the CCCH of the logical channel, or the DCCH of the logical channel. In addition, the RRC message sent using the DCCH can also be renamed as dedicated RRC signaling or RRC signaling.

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

[0078] The RRC message sent in the uplink (UL) direction using CCCH may include, for example, an RRC setup request message (RRC Setup Request), and may also include an RRC resume request message (RRC Resume Request), an RRC reestablishment request message (RRC Reestablishment Request), an RRC system information request message (RRC SystemInfo Request), etc. In addition, for example, it may include 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. In addition, other RRC messages may also be included.

[0079] The RRC message sent in the downlink (DL) direction using CCCH may include, for example, an RRC connection rejection message (RRC Connection Reject), an RRC connection configuration message (RRC Connection Setup), an RRC connection reestablishment message (RRC Connection Reestablishment), an RRC connection reestablishment rejection message (RRC Connection Reestablishment Reject), etc. In addition, for example, an RRC rejection message (RRC Reject), an RRC configuration message (RRC Setup), etc. In addition, other RRC messages may also be included.

[0080] The RRC signaling sent in the uplink (UL) direction using the DCCH may include, for example, a measurement report message (Measurement Report), an RRC connection reconfiguration complete message (RRC Connection ReconfigurationComplete), an RRC connection configuration 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. In addition, for example, a measurement report message (Measurement Report), an RRC reconfiguration complete message (RRC ReconfigurationComplete), an RRC configuration 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. In addition, other RRC signaling may also be included.

[0081] The RRC signaling sent in the downlink (DL) direction using the DCCH may include, for example, an RRC connection reconfiguration message (RRC Connection Reconfiguration), an RRC connection release message (RRC Connection Release), a security mode command message (Security Mode Command), a UE capability inquiry message (UE Capability Enquiry), etc. In addition, for example, an RRC reconfiguration message (RRC Reconfiguration), an RRC restart message (RRCResume), an RRC release message (RRC Release), an RRC reestablishment message (RRC Reestablishment), a security mode command message (Security Mode Command), a UE capability inquiry message (UE Capability Enquiry), etc. In addition, other RRC signaling may also be included.

[0082] An example of the function of NAS is described below. NAS may have an authentication function. In addition, NAS may also have a function of performing mobility management. In addition, NAS may also have a security control function.

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

[0084] Next, the state transition of UE122 in LTE and NR is explained. When UE122 connected to EPC or 5GC has established an RRC connection (RRC connection has been established), UE122 may be in RRC_CONNECTED state. The state in which the RRC connection is established may include a state in which UE122 saves part or all of the UE context described later. In addition, the state in which the RRC connection is established may also include a state in which UE122 can send and / or receive unicast data. In addition, when the RRC connection of UE122 is terminated (suspended), UE122 may be in RRC_INACTIVE state. In addition, UE122 being in RRC_INACTIVE state may be when the RRC connection is terminated when UE122 is connected to 5GC. When UE122 is neither in RRC_CONNECTED state nor in RRC_INACTIVE state, UE122 may be in RRC_IDLE state.

[0085] It should be noted that, when UE122 is connected to EPC, it does not have the RRC_INACTIVE state, but the termination of the RRC connection can be initiated by E-UTRAN. When UE122 is connected to EPC, when the RRC connection is terminated, UE122 can save the UE's AS context and the identifier (resumeIdentity) for resumption (resume) and transition to the RRC_IDLE state. When UE122 saves the UE's AS context, and the resumption of the RRC connection is permitted (Permit) by E-UTRAN, and UE122 needs to transition from the RRC_IDLE state to the RRC_CONNECTED state, the upper layer of the RRC layer of UE122 (e.g., the NAS layer) can start the resumption of the terminated RRC connection.

[0086] The definition of suspension may be different in UE 122 connected to EPC 104 and UE 122 connected to 5GC 110. In addition, all or part of the process of UE 122 recovering from suspension may be different in the case where UE 122 is connected to EPC (the case where UE 122 is suspended in RRC_IDLE state) and the case where UE 122 is connected to 5GC (the case where UE 122 is suspended in RRC_INACTIVE state).

[0087] It should be noted that the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state can be respectively referred to as the connected state (connected mode), the disabled state (inactive mode), and the idle state (idle mode), and can also be referred to as the RRC connected state (RRC connected mode), the RRC disabled state (RRC inactive mode), and the RRC idle state (RRC idle mode).

[0088] The AS context of the UE saved by UE122 may include all or part of the current RRC settings, 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 PCell of the connection source (Source), the cell identifier (cellIdentity), and the physical cell identifier of the PCell of the connection source. It should be noted that the AS context of the UE saved by any or all of eNB102 and gNB108 may include the same information as the AS context of the UE saved by UE122, and may also include information different from the information included in the AS context of the UE saved by UE122.

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

[0090] Next, the serving cell (Serving Cell) is explained. In a terminal device in which the RRC connection state of CA and / or DC described later is not set, the serving cell may be composed of a primary cell (Primary Cell: PCell). In addition, in a terminal device in which the RRC connection state of CA and / or DC described later is set, multiple serving cells may refer to a set of multiple cells (set of cell(s)) consisting of one or more special cells (Special Cell: SpCell) and one or more secondary cells (Secondary Cell: SCell). SpCell can support PUCCH transmission and contention-based random access (contention-based Random Access: CBRA), and SpCell can be always activated. PCell can be a cell used in the RRC connection establishment process when a terminal device in the RRC idle state is converted to the RRC connected state. In addition, PCell can also be a cell used in the RRC connection re-establishment process when the terminal device re-establishes the RRC connection. In addition, PCell can also be a cell used in the random access process during switching. PSCell can be a cell used for the random access process when adding a secondary node described later. Furthermore, the SpCell may be a cell used for purposes other than those described above.

[0091] The group of serving cells configured for a terminal device is composed of SpCell and one or more SCells, which can be regarded as configuring carrier aggregation (CA) for the terminal device. In addition, for a terminal device configured with CA, a cell that provides additional radio resources to SpCell can be referred to as SCell.

[0092] In the group of service cells set by RRC, for the cells in which the uplink is set, the group of service cells using the same timing reference cell (timing reference cell) and the same timing advance value can be called a timing advance group (Timing Advance Group: TAG). In addition, the TAG of the SpCell including the MAC entity can mean the primary timing advance group (Primary Timing Advance Group: PTAG). In addition, the TAG other than the above-mentioned PTAG can mean the secondary timing advance group (Secondary Timing Advance Group: STAG). It should be noted that one or more of the TAGs can also be composed of each cell group described later.

[0093] The cell group (Cell Group) set from the base station device to the terminal device is described. The cell group can be composed of one SpCell. In addition, the cell group can also be composed of one SpCell and one or more SCells. That is, the cell group can be composed of one SpCell and one or more SCells as needed (optionally). In addition, the cell group can be expressed as a set of cells (set of cell(s)).

[0094] Dual Connectivity (DC) may refer to a technology for performing data communications using wireless resources of a cell group respectively constituted by a first base station device (first node) and a second base station device (second node). In the case of DC and MR-DC described later, a cell group may be added to the terminal device from the base station device. In order to perform DC, the first base station device may add a second base station device. The first base station device may be referred to as a master node (Master Node: MN). In addition, the cell group constituted by the master node may be referred to as a master cell group (Master Cell Group: MCG). The second base station device may be referred to as a secondary node (Secondary Node: SN). In addition, the cell group constituted by the secondary node may be referred to as a secondary cell group (Secondary Cell Group: SCG). It should be noted that the master node and the secondary node may be constituted in the same base station device.

[0095] In addition, when DC is not set, the cell group set in the terminal device can be called MCG. In addition, when DC is not set, the SpCell set in the terminal device can be PCell. In addition, the NR without DC can be called NR independent.

[0096] It should be noted that multi-radio dual connectivity (MR-DC) may refer to a technology for performing DC using E-UTRA in MCG and NR in SCG. In addition, MR-DC may refer to a technology for performing DC using NR in MCG and E-UTRA in SCG. In addition, MR-DC may refer to a technology for performing DC using NR in both MCG and SCG. MR-DC may be a technology included in DC. As an example of MR-DC using E-UTRA in MCG and NR in SCG, there may be EN-DC (E-UTRA-NR Dual Connectivity) using EPC in the core network, and there may be NGEN-DC (NG-RAN E-UTRA-NR Dual Connectivity) using 5GC in the core network. In addition, as an example of MR-DC using NR in MCG and E-UTRA in SCG, there may be NE-DC (NR-E-UTRA Dual Connectivity) using 5GC in the core network. In addition, as an example of MR-DC using NR in both MCG and SCG, there can be NR-DC (NR-NR Dual Connectivity) using 5GC in the core network.

[0097] It should be noted that, in the terminal device, there may be a MAC entity for each cell group. For example, when DC or MR-DC is set for the terminal device, there may be a MAC entity for MCG and a MAC entity for SCG. The MAC entity for MCG in the terminal device can always be established in the terminal device in all states (RRC idle state, RRC connected state, and RRC disabled state, etc.). In addition, when SCG is set in the terminal device, the MAC entity for SCG in the terminal device can be created (create) by the terminal device. In addition, the MAC entity for each cell group of the terminal device can be set by the terminal device receiving RRC signaling from the base station device. When the MAC entity is associated with the MCG, SpCell may mean PCell. In addition, when the MAC entity is associated with the SCG, SpCell may mean the primary SCG cell (Primary SCG Cell: PSCell). In addition, when the MAC entity is not associated with the cell group, SpCell may mean PCell. PCell, PSCell and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be an E-UTRA MAC entity, and the MAC entity for SCG may be an NR MAC entity. In addition, in NE-DC, the MAC entity for MCG may be an NR MAC entity, and the MAC entity for SCG may be an E-UTRA MAC entity. In addition, in NR-DC, the MAC entities for both MCG and SCG may be NR MAC entities. It should be noted that the existence of one MAC entity for each cell group may be renamed as the existence of one MAC entity for each SpCell. In addition, one MAC entity for each cell group may be renamed as one MAC entity for each SpCell.

[0098] The radio bearer is described. When the terminal device communicates with the base station device, a wireless connection can be established by establishing a radio bearer (RB: Radio Bearer) between the terminal device and the base station device. The radio bearer used for CP can be called a signaling radio bearer (SRB: Signaling Radio Bearer). In addition, the radio bearer used for UP can be called a data radio bearer (DRB: Data Radio Bearer). A radio bearer identifier (Identity: ID) can be assigned to each radio bearer. The radio bearer identifier for SRB can be called an SRB identifier (SRB Identity or SRB ID). The radio bearer identifier for DRB can be called a DRB identifier (DRB Identity or DRB ID). SRB0 to SRB2 can be defined for the SRB of E-UTRA, and SRBs other than these can be defined. SRB0 to SRB3 can be defined for the SRB of NR, and SRBs other than these can be defined. SRB0 can be an SRB for RRC messages sent and / or received using the CCCH of a logical channel. SRB1 can be an SRB used for RRC signaling and for NAS signaling before the establishment of SRB2. The RRC signaling sent and / or received using SRB1 may include piggybacked NAS signaling. The DCCH of the logical channel may be used for all RRC signaling and NAS signaling sent and / or received using SRB1. SRB2 may be an SRB used for NAS signaling and for RRC signaling including logged measurement information. The DCCH of the logical channel may be used for all RRC signaling and NAS signaling sent and / or received using SRB2. In addition, SRB2 may be a lower priority than SRB1. SRB3 may be an SRB used to send and / or receive specific RRC signaling to a terminal device when EN-DC, NGEN-DC, NR-DC, etc. are set. The DCCH of the logical channel may be used for all RRC signaling and NAS signaling sent and / or received using SRB3. In addition, other SRBs may also be prepared for other purposes. DRB may be a radio bearer for user data. The DTCH of the logical channel may be used for RRC signaling sent and / or received using DRB.

[0099] The wireless bearer in the terminal device is described. The wireless bearer may include an RLC bearer. The RLC bearer may be composed of one or two RLC entities and logical channels. When there are two RLC entities in the RLC bearer, the RLC entity may be a TM RLC entity and / or a sending RLC entity and a receiving RLC entity in a unidirectional UM mode RLC entity. SRB0 may be composed of one RLC bearer. The RLC bearer of SRB0 may be composed of an RLC entity and a logical channel of TM. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, and RRC disabled state, etc.). When the terminal device changes from the RRC idle state to the RRC connected state, an SRB1 may be established and / or set for the terminal device through the RRC signaling received from the base station device. SRB1 may be composed of a PDCP entity and one or more RLC bearers. The RLC bearer of SRB1 may be composed of an RLC entity and a logical channel of AM. An SRB2 can be established and / or set for a terminal device by RRC signaling received from a base station device by a terminal device in an AS-secure RRC connection state. SRB2 can be composed of a PDCP entity and one or more RLC bearers. The RLC bearer of SRB2 can be composed of an RLC entity and a logical channel of AM. It should be noted that the PDCP on the base station device side of SRB1 and SRB2 can be placed in the master node. When adding a secondary node in EN-DC, NGEN-DC, or NR-DC or changing a secondary node, an SRB3 can be established and / or set for a terminal device by RRC signaling received from a base station device by a terminal device in an AS-secure RRC connection state. SRB3 can be a direct SRB between a terminal device and a secondary node. SRB3 can be composed of a PDCP entity and one or more RLC bearers. The RLC bearer of SRB3 can be composed of an RLC entity and a logical channel of AM. The PDCP on the base station device side of SRB3 can be placed in a secondary node. One or more DRBs may be established and / or configured for a terminal device through RRC signaling received from a base station device by a terminal device in an AS-secured RRC connection state. A DRB may consist of a PDCP entity and one or more RLC bearers. The RLC bearer of a DRB may consist of an AM or UM RLC entity and a logical channel.

[0100] It should be noted that, in MR-DC, the radio bearer in which PDCP is placed in the primary node can be called an MN terminated (terminated) bearer. In addition, in MR-DC, the radio bearer in which PDCP is placed in the secondary node can be called an SN terminated (terminated) bearer. It should be noted that, in MR-DC, the radio bearer in which RLC bearer exists only in MCG can be called an MCG bearer (MCG bearer). In addition, in MR-DC, the radio bearer in which RLC bearer exists only in SCG can be called an SCG bearer (SCG bearer). In addition, in DC, the radio bearer in which RLC bearer exists in both MCG and SCG can be called a split bearer (split bearer).

[0101] When MR-DC is set for the terminal device, the bearer type of SRB1 and SRB2 established and / or set in the terminal device may be an MN terminated MCG bearer and / or an MN terminated split bearer. In addition, when MR-DC is set for the terminal device, the bearer type of SRB3 established and / or set in the terminal device may be an SN terminated SCG bearer. In addition, when MR-DC is set for the terminal device, the bearer type of DRB established and / or set in the terminal device may be any one of all bearer types.

[0102] For the RLC bearers established and / or configured in the cell group composed of E-UTRA, the RLC entity established and / or configured may be E-UTRA RLC. In addition, for the RLC bearers established and / or configured in the cell group composed of NR, the RLC entity established and / or configured may be NR RLC. In the case where EN-DC is set for 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. In addition, in the case where EN-DC is set for the terminal device, the PDCP established and / or configured for the radio bearers of other bearer types, namely, MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer and SN terminated SCG bearer may be NR PDCP. In addition, in the case where NGEN-DC or NE-DC or NR-DC is set for the terminal device, the PDCP entity established and / or configured for the radio bearers in all bearer types may be NR PDCP.

[0103] It should be noted that in NR, the DRB established and / or set in the terminal device can be associated with a PDU session. An SDAP entity can be established and / or set in the terminal device for a PDU session. The SDAP entity, PDCP entity, RLC entity and logical channel established and / or set in the terminal device can be established and / or set through RRC signaling received by the terminal device from the base station device.

[0104] It should be noted that regardless of whether MR-DC is set, the master node is eNB102, and the network configuration with EPC104 as the core network can also be called E-UTRA / EPC. In addition, the master node is eNB102, and the network configuration with 5GC110 as the core network can be called E-UTRA / 5GC. In addition, the network configuration with 5GC110 as the core network in gNB108, which is the master node, can 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.

[0105] Next, the switching in LTE and NR is explained. Switching may refer to the process of UE122 in RRC connected state changing the serving cell from the source SpCell to the target SpCell. Switching may be performed when UE122 receives RRC signaling indicating switching from eNB102 and / or gNB108. The RRC signaling indicating switching may refer to a message related to RRC connection reconfiguration including parameters indicating switching (e.g., an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). It should be noted that the above-mentioned information element named MobilityControlInfo may be renamed as mobility control setting information element, or mobility control setting, or mobility control information. It should be noted that the above-mentioned information element named ReconfigurationWithSync may be renamed as synchronous reconfiguration information element or synchronous reconfiguration. In addition, the RRC signaling indicating switching may refer to a message indicating movement to a cell of another RAT (e.g., MobilityFromEUTRammand or MobilityFromNRcommand). In addition, the switching may be renamed as synchronous reconfiguration (reconfiguration with sync). In addition, the conditions under which UE 122 can perform switching may include when AS security is activated, when SRB2 is established, and when part or all of at least one DRB is established.

[0106] The flow of RRC signaling transmitted and received between the terminal device and the base station device is described. Figure 4This is a diagram showing an example of the flow of procedures for various settings in RRC according to the present embodiment. Figure 4 This is an example of a process in which RRC signaling is sent from a base station device (eNB102 and / or gNB108) to a terminal device (UE122).

[0107] exist Figure 4 In step S400, the base station device generates an RRC message. The generation of the RRC message in the base station device may be performed in order for the base station device to transmit system information (SI: System Information) and paging messages. In addition, the generation of the RRC message in the base station device may be performed in order to send RRC signaling for the base station device to process a specific terminal device. The processing performed on a specific terminal device may include, for example, security-related settings, re-setting of the RRC connection, switching to a different RAT, termination of the RRC connection, release of the RRC connection, and other processing. The re-setting process of the RRC connection may include, for example, control of the radio bearer (establishment, change, release, etc.), control of the cell group (establishment, addition, change, release, etc.), measurement settings, switching, security key update, and other processing. In addition, the generation of the RRC message in the base station device may also be performed in order to respond to the RRC signaling sent from the terminal device. The response to the RRC signaling sent from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC restart request, and the like. The RRC message includes information (parameters) used for various information notifications and settings. These parameters may be referred to as fields and / or information elements, and may be expressed using ASN.1 (Abstract Syntax Notation One).

[0108] exist Figure 4 Then, the base station device sends the generated RRC signaling to the terminal device (step S402). Then, the terminal device processes the received RRC signaling if it needs to perform settings or other processing (step S404). The terminal device that performs the processing can send RRC signaling for response to the base station device (not shown).

[0109] RRC signaling is not limited to the above examples and can also be used for other purposes.

[0110] It should be noted that in MR-DC, the RRC on the master node side can be used to transmit RRC signaling for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) between the terminal device. For example, in EN-DC or NGEN-DC, the RRC signaling of E-UTRA sent and received between eNB102 and UE122 can include NR's RRC signaling in the form of a container. In addition, in NE-DC, the RRC signaling of NR sent and received between gNB108 and UE122 can include E-UTRA's RRC signaling in the form of a container. RRC signaling for SCG side settings can be sent and received between the master node and the slave node.

[0111] It should be noted that, not limited to the case of using MR-DC, the RRC signaling for E-UTRA sent from eNB102 to UE122 may also include RRC signaling for NR, and the RRC signaling for NR sent from gNB108 to UE122 may also include RRC signaling for E-UTRA.

[0112] An example of parameters included in a message related to re-setting of an RRC connection is described. Figure 7 It means in Figure 4 An example of an ASN.1 representation of fields and / or information elements related to cell group configuration included in a message related to reconfiguration of an RRC connection in NR. Figure 8 It means in Figure 4 An example of an ASN.1 representation of fields and / or information elements related to cell group configuration included in a message related to RRC connection reconfiguration in E-UTRA. Figure 7 , Figure 8In the example of ASN.1 in this embodiment, <omitted> and <omitted in part> indicate that other information is omitted and is not part of the ASN.1 expression. It should be noted that in places where there is no such record as <omitted> or <omitted in part>, the information element may be omitted. It should be noted that in this embodiment, the example of ASN.1 does not correctly follow the ASN.1 expression method. In this embodiment, the example of ASN.1 is an example of expressing the parameters of the RRC signaling of this embodiment, and other names and other expressions may also be used. In addition, in order to avoid complicating the description, the example of ASN.1 only represents an example of the main information closely related to this embodiment. It should be noted that sometimes all parameters expressed by ASN.1 are also referred to as information elements, without distinguishing between fields, information elements, etc. In addition, in this embodiment, the fields, information elements, etc. expressed by ASN.1 included in the RRC signaling may be renamed as information or parameters. It should be noted that the message related to the RRC connection reconfiguration may refer to the RRC connection reconfiguration message in NR or the RRC connection reconfiguration message in E-UTRA.

[0113] exist Figure 7In the information element named CellGroupConfig, the information element named CellGroupConfig may be an information element for setting, changing, releasing, etc. of a cell group of an MCG or SCG in NR. The information element named CellGroupConfig may include the TCI information element described later. The information element named CellGroupConfig may be renamed as a cell group setting information element or a cell group setting. In addition, in the case where the information element named CellGroupConfig is used for setting a cell group of an SCG in NR, the information element named CellGroupConfig may be renamed as a setting on the SCG side. The information element named SpCellConfig included in the information element named CellGroupConfig may be an information element for setting a special cell (SpCell). The information element named SpCellConfig may be renamed as a SpCell setting information element or a SpCell setting. The information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element set in the deactivation of an SCG described later. The information element named DeactivatedSCG-Config-r17 may be renamed as a setting in the deactivation of an SCG. It should be noted that the information element named DeactivatedSCG-Config-r17 may include a parameter represented by bfd-and-RLM for indicating whether the terminal device performs BFD and / or RLM described later in the PSCell in the disabled state of the SCG. 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 renamed as TCI information element. It should be noted that the information element named TCI-Info may include a parameter of the identifier of the BWP described later represented by BWP-Id.

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

[0115] The terminal device can use a certain reference signal (cell-specific reference signal (CRS) etc.) to monitor the wireless link in the serving cell (PCell and / or PSCell, etc.). In addition, the terminal device can receive a setting (wireless link monitoring setting: RadioLinkMonitoringConfig) from the base station device indicating which reference signal to use in the wireless link monitoring in the serving cell (PCell and / or PSCell, etc.), and use one or more reference signals (referred to herein as RLM-RS) that have been set to monitor the wireless link. In addition, the terminal device may also use other signals to monitor the wireless link. The physical layer processing unit of the terminal device can notify the upper layer of synchronization when the conditions for being in synchronization are met in the serving cell (PCell and / or PSCell, etc.).

[0116] The wireless link monitoring setting may include information indicating the purpose of monitoring and identifier information indicating a reference signal. For example, the purpose of monitoring may include the purpose of monitoring wireless link failures, the purpose of monitoring beam failures, or the purpose of both parties. In addition, 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. In addition, 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 a terminal device.

[0117] If the terminal device is not provided with RLM-RS but is provided with (multiple) TCI states for PDCCH reception including one or more CSI-RS, the terminal device implements part or all of the following (A) to (B). (A) In the case where the activated TCI state for PDCCH reception includes only one reference signal, the reference signal provided in the activated TCI state is used for radio link monitoring (B) In the case where the activated TCI state for PDCCH reception includes two reference signals, it is expected that the QCL type of one reference signal is set to type D, and the reference signal whose QCL type is set to type D is used for radio link monitoring (it is not expected that the QCL type of both reference signals is set to type D)

[0118] If multiple downlink BWPs described later are set for a certain service cell, the terminal device can perform RLM using the reference signal corresponding to the RLM-RS in the activated DL BWP described later. In addition, if multiple downlink BWPs described later are set for a certain service cell, and RLM-RS is provided for the activated DL BWP described later, the terminal device can perform RLM using the (multiple) reference signals provided in the activated TCI state for receiving PDCCH in the CORESET of the activated DL BWP.

[0119] Next, BFD (Beam Failure Detection) will be described.

[0120] In the MAC entity, the beam failure recovery process can be set by RRC for each serving cell. The beam failure recovery process can be used to notify the serving gNB (base station device that communicates with the terminal device) of a new SSB or CSI-RS when a beam failure is detected on one or more SSBs and / or CSI-RS of the serving cell. Beam failure is detected by counting the beam failure instance notifications notified to the MAC entity from the lower layer (PHY layer). In addition, if the SCG is in a disabled state, the MAC entity can use a certain type of reference signal (cell-specific reference signal (CRS) etc.) represented by the radio link monitoring setting in the PSCell for beam failure detection. The MAC entity can implement part or all of the following (A), (B), and (C) in each serving cell to detect beam failure. (A) If a beam failure instance notification is received from a lower layer (PHY, etc.), the beam failure detection timer (beamFailureDetectionTimer) is started or restarted, and the beam failure counter (BFI_COUNTER) is incremented by 1. If the value of BFI_COUNTER is greater than the set threshold (beamFailureInstanceMaxCount), the following (A-1) is implemented. (A-1) If the serving cell is an SCell, beam failure recovery (BFR) for the serving cell is triggered; otherwise, the following (A-2) is implemented. (A-2) If the serving cell is a PSCell and the SCG is in a disabled state, the following (A-3) is implemented, otherwise, a random access procedure is started in the SpCell. (A-3) If the beam failure of the PSCell is not notified to the upper layer after the SCG is disabled or the beam failure in the PSCell is not notified to the upper layer (RRC entity, etc.) after the SCG is finally reset through BFD-RS, the beam failure in the PSCell is notified to the upper layer (RRC entity, etc.). (B) If the beamFailureDetectionTimer for the serving cell expires or if the settings of beamFailureDetectionTimer, beamFailureInstanceMaxCount and / or the reference signal for beam failure detection (BFD-RS) are changed by the upper layer (RRC entity, etc.), BFI_COUNTER is set to 0. (C) If the serving cell is a SpCell and the random access process is successfully completed, the BFI_COUNTER is set to 0. If the beam failure recovery timer (beamFailureRecoveryTimer) is set and is running, it is stopped and the beam failure recovery process is deemed to be successfully completed. Otherwise, if the serving cell is a SCell and a PDCCH addressed to the C-RNTI representing a new uplink grant is received for sending information for beam failure recovery for the SCell (such as the information included in the BFR MAC CE of the SCell or the truncated BFR MAC CE of the SCell), or the SCell is in a disabled state, the BFI_COUNTER is set to 0, the beam failure recovery process is deemed to be successfully completed, and all beam failure recovery (BFR) triggered for the serving cell are canceled.

[0121] If at least one beam failure recovery (BFR) is triggered by the beam failure recovery procedure and is not canceled, the MAC entity implements the following (A). (A) If the UL-SCH resources can include the BFR MAC CE and its subheader of the SCell based on the priority of the logical channel, the BFR MAC CE and its subheader of the SCell are included. Otherwise, if the UL-SCH resources can include the truncated BFR MAC CE and its subheader of the SCell based on the priority of the logical channel, the truncated BFR MAC CE and its subheader of the SCell are included. Otherwise, a scheduling request for SCell beam failure recovery is triggered.

[0122] Here, the beamFailureRecoveryTimer (beam failure recovery timer) is explained. When the random access process is started to perform BFR of the SpCell, the MAC entity can start the beamFailureRecoveryTimer when the beam failure recovery setting (beamFailureRecoveryConfig) is set for the activated UL BWP (Active UL BWP). In addition, when the beamFailureRecoveryTimer is running or the beamFailureRecoveryTimer is not set, the terminal device can use contention-free Random Access (CFRA) for BFR. In addition, when the beamFailureRecoveryTimer expires or is not running, the terminal device may not use CFRA, but instead use, for example, CBRA for BFR.

[0123] The terminal device may provide a set of one or more reference signals for detecting beam failure and / or radio link failure (reference signal for detecting beam failure and / or radio link failure: BFD-RS described below) in each BWP in a serving cell. The BFD-RS may be a periodic CSI-RS (periodic CSI-RS) or other reference signals. The PHY of the terminal device may measure (assess) the quality of the radio link based on the set of BFD-RS. In addition, the PHY may also provide a notification to the upper layer (MAC, etc.) when the measured radio link quality is not worse than a threshold (rlmInSyncOutOfSyncThreshold) set by the upper layer (RRC, etc.).

[0124] The activation (Activation) and deactivation (Deactivation) of the cell are explained. In a terminal device that communicates through dual connections, the setting of the main cell group (MCG) and the setting of the secondary cell group (SCG) are performed through messages related to the above-mentioned RRC connection re-setting. Each cell group can be composed of a special cell (SpCell) and 0 or more other cells (secondary cells: SCell). The SpCell of MCG is also called PCell. The SpCell of SCG is also called PSCell. The deactivation of the cell may not be applied to the SpCell, but to the SCell.

[0125] In addition, the deactivation of a cell may not be applied to the PCell but to the PSCell. In this case, the deactivation of a cell may be handled differently in the SpCell and the SCell.

[0126] The activation and deactivation of the cell can be handled by the MAC entity existing in each cell group. The SCell set for the terminal device can be activated and / or deactivated by part or all of the following (A) to (C). (A) Reception of MAC CE for SCell activation / deactivation (B) SCell disable timer set in each SCell where PUCCH is not configured (C) RRC parameters (sCellState) configured in each SCell configured in the terminal device

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

[0128] If the RRC parameter (sCellState) for the SCell setting is set to activated when the SCell is set or a MAC CE for activating the SCell is received, the MAC entity of UE122 performs processing (AD-1). Otherwise, if a MAC CE for disabling the SCell is received or the SCell disabling timer expires in the activated SCell, the MAC entity of UE122 performs processing (AD-2). If an uplink grant or downlink allocation is notified through the PDCCH of the activated SCell, or an uplink grant or downlink is allocated for the activated SCell through the PDCCH of a certain serving cell, or a MAC PDU is sent in the set uplink grant, or a MAC PDU is received in the set downlink allocation, the MAC entity of UE122 restarts the SCell disabling timer associated with the SCell. If the SCell is in a disabled state, the MAC entity of UE122 performs processing (AD-3). (Processing AD-1)

[0129] If, in NR, the SCell is in a disabled state before receiving a MAC CE to activate the SCell, or the RRC parameter (sCellState) configured for the SCell is set to activated when the SCell is configured, the MAC entity of UE122 performs processing (AD-1A) or processing (AD-1B). In addition, the MAC entity of UE 122 starts or (if already started) restarts the SCell deactivation timer corresponding to the SCell. When the Active DL BWP is not a Dormant BWP described later, the MAC entity of UE 122 implements part or all of the following (A) to (B). (A) If present, all configured uplink grants of grant type 1 corresponding to the SCell are (re)initialized according to the stored configuration. (B) Triggering PHR. Upon receiving a MAC CE for activating the SCell, and when the BWP indicated by the first activated downlink BWP identifier (firstActiveDownlinkBWP-Id) set for the SCell through RRC signaling is not set to a dormant BWP, the MAC entity of UE122 performs processing (AD-1A). Upon receiving a MAC CE for activating the SCell, and when the BWP indicated by the first activated downlink BWP identifier (firstActiveDownlinkBWP-Id) set for the SCell through RRC signaling is set to a dormant BWP, the MAC entity of UE122 performs processing (AD-1B). In addition, the MAC entity of UE122 implements part or all of the following (A) to (B). (A) Activate the BWP indicated by the first Active Downlink BWP-Id set by RRC signaling (B) Activate the BWP indicated by the first Active Uplink BWP-Id set by RRC signaling (Processing AD-1A)

[0130] The MAC entity of UE122 activates the SCell and implements part or all of the following (A) to (E). (A) A sounding reference signal (SRS) is transmitted in the SCell. (B) Report the CSI for this SCell. (C) Monitor the PDCCH in the SCell. (D) Monitor the PDCCH for the SCell. (When scheduling for the SCell is performed in other serving cells) (E) If PUCCH is configured, PUCCH is sent in the SCell. (Processing AD-1B)

[0131] If the BWP disable timer of the serving cell is running, the MAC entity of UE 122 stops. (Processing AD-2)

[0132] The MAC entity of UE122 implements part or all of the following (A) to (F). (A) Disable the SCell. (B) Stop the SCell disable timer associated with the SCell. (C) Disable all active BWPs associated with the SCell. (D) Clear all configured downlink allocations and / or all configured uplink grants of grant type 2 that correspond to the SCell. (E) Suspend all configured uplink grants of grant type 1 corresponding to the SCell. (F) Refresh the HARQ buffer corresponding to the SCell. (Processing AD-3)

[0133] The MAC entity of UE122 implements part or all of the following (A) to (D). (A) SRS is not sent in this SCell. (B) CSI for this SCell is not reported. (C) PUCCH, UL-SCH and / or RACH are not sent in the SCell. (D) The PDCCH of the SCell and / or the PDCCH for the SCell is not monitored.

[0134] As described above, the activation and deactivation of SCell is performed through the MAC entity (AD).

[0135] In addition, as described above, when adding an SCell, the initial state of the SCell can be set through RRC signaling.

[0136] Here, the SCell deactivation timer is described. For an SCell for which PUCCH is not set, the value of the SCell deactivation timer (information related to the time considered as the expiration of the timer) can be notified by RRC signaling. For example, in the case where information indicating 40ms is notified by RRC signaling as the value of the SCell deactivation timer, in the above-mentioned process (AD), when the timer is not stopped after the notified time (here 40ms) has passed after the timer is started or restarted, the timer is considered to have expired. In addition, the SCell deactivation timer can be a timer named sCellDeactivationTimer.

[0137] Here, the partial bandwidth (BWP) is described.

[0138] BWP can be part of or all of the frequency band of the serving cell. In addition, BWP can be called carrier BWP. One or more BWPs can be set in the terminal device. A certain BWP can be set by the information included in the system information corresponding to the synchronization signal detected by the initial cell search. In addition, a certain BWP can be a frequency bandwidth corresponding to the frequency for the initial cell search. In addition, a certain BWP can be set by RRC signaling (e.g., Dedicated RRC signaling). In addition, the downlink BWP (DL BWP) and the uplink BWP (ULBWP) can be set separately. In addition, one or more uplink BWPs can be established in correspondence with one or more downlink BWPs. In addition, the correspondence between the uplink BWP and the downlink BWP can be a predetermined correspondence, or a correspondence established through RRC signaling (e.g., Dedicated RRC signaling), or a correspondence established through physical layer signaling (e.g., downlink control information (DCI) notified by the downlink control channel, or a combination of them. In addition, CORESET can be set in the downlink BWP.

[0139] A BWP can be composed of a group of continuous physical radio blocks (PRB: Physical Resource Block). In addition, the parameters of the BWP (one or more BWPs) of each component carrier can be set for a terminal device in a connected state. The parameters of the BWP of each component carrier may include: (A) the type of cyclic prefix; (B) the subcarrier spacing; (C) the frequency position of the BWP (for example, the starting position or the center frequency position of the low frequency side of the BWP) (the frequency position can use, for example, ARFCN, or an offset from a specific subcarrier of the serving cell. In addition, the unit of the offset can be a subcarrier unit or a resource block unit. In addition, both ARFCN and the offset may be set); (D) the bandwidth of the BWP (for example, the number of PRBs); (E) the resource setting information of the control signal; (F) the center frequency position of the SS block (the frequency position can use, for example, ARFCN, or an offset from a specific subcarrier of the serving cell. In addition, the unit of the offset can be a subcarrier unit or a resource block unit. In addition, both ARFCN and the offset may be set). In addition, the resource setting information of the control signal may be included in at least the setting of a part or all of the BWP in the PCell and / or PSCell.

[0140] The terminal device can transmit and receive in an activated BWP (Active BWP) among one or more set BWPs. One or more BWPs can be set in a service cell associated with the terminal device. It can also be set so that at most one uplink BWP and / or at most one downlink BWP at a time in one or more BWPs set for a service cell associated with the terminal device is activated. The activated BWP of the downlink is also referred to as an activated DL BWP. The activated BWP of the uplink is also referred to as an activated UL BWP. In addition, a BWP that is not an activated BWP among the one or more BWPs set for the terminal device may also be referred to as an inactive BWP.

[0141] Next, activation / deactivation of BWP is described. Activation of BWP may mean activation of BWP or activation of disabled BWP. In addition, deactivation of BWP may mean deactivation of BWP or deactivation of activated BWP. BWP switching in a serving cell is used to activate a disabled BWP and deactivate an activated BWP.

[0142] BWP switching is controlled by the MAC entity itself, and is indicated by PDCCH for downlink allocation or uplink grant, BWP disable timer, RRC signaling or the start of random access procedure. The activated BWP of the serving cell is indicated by RRC or PDCCH.

[0143] Next, the BWP disable timer is described. The MAC entity implements the following (A) for each activated serving cell (Activated Serving Cell) for which the BWP disable timer is set. In addition, the BWP disable timer may be a timer named bwp-InactivityTimer. (A) If the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is set, and the activated DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the identifier of the default downlink BWP (defaultDownlinkBWP-Id) is not set, and the activated DL BWP is not initialDownlinkBWP, and the activated DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), the MAC entity implements the following (B) and (D). (B) If a PDCCH addressed to a C-RNTI or CS-RNTI representing a downlink assignment or an uplink grant is received through an activated DL BWP, or if a PDCCH addressed to a C-RNTI or CS-RNTI representing a downlink assignment or an uplink grant for an activated DL BWP is received, or if a MAC PDU is sent through a configured uplink grant, or a MAC PDU is received through a configured downlink assignment, the MAC entity implements the following (C). (C) If no random access procedure associated with the serving cell is being performed, or the random access procedure associated with the serving cell being performed is successfully completed by reception of a PDCCH addressed to the C-RNTI, then the BWP disable timer associated with the activated DL BWP is started or restarted. (D) If the BWP disable timer associated with the activated DL BWP expires (Expire), the MAC entity implements the following (E). (E) If defaultDownlinkBWP-Id is set, BWP switching is performed on the BWP indicated by the defaultDownlinkBWP-Id; otherwise, BWP switching is performed on the initialDownlinkBWP.

[0144] In addition, if the MAC entity receives a PDCCH for BWP switching and switches the activated DL BWP, the following (A) is implemented. (A) If the identity of the default downlink BWP (defaultDownlinkBWP-Id) is set, the switched active DL BWP is not the BWP indicated by the identity (dormantDownlinkBWP-Id), and if the switched active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, then start or restart the BWP deactivation timer associated with the active DL BWP.

[0145] In each activated serving cell in which BWP is set, if BWP is activated (activated BWP), and the activated DL BWP in the serving cell is not a dormant BWP (dormant BWP), the MAC entity performs part or all of the following (A) to (H). (A) UL-SCH is transmitted through this BWP. (B) If the PRACH opportunity is set, RACH is transmitted via the BWP. (C) PDCCH is monitored through the BWP. (D) If PUCCH is configured, PUCCH is transmitted via the BWP. (E) Report CSI via the BWP. (F) If SRS is set, SRS is sent through this BWP. (G) Receive DL-SCH through the BWP. (H) If any, (re)initialize all configured uplink grants of grant type 1 that are suspended and set by the activated BWP according to the stored configuration.

[0146] If BWP is disabled, the MAC entity performs some or all of the following (A) to (I). (A) UL-SCH is not transmitted through this BWP. (B) RACH is not transmitted via the BWP. (C) PDCCH is not monitored through the BWP. (D) PUCCH is not sent through this BWP. (E) CSI is not reported via this BWP. (F) SRS is not sent through this BWP. (G) DL-SCH is not received through the BWP. (H) Clear all configured downlink allocations and / or all configured uplink grants of grant type 2 set by this BWP. (I) Suspend all configured uplink grants of grant type 1 for the disabled BWP (Inactive BWP).

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

[0148] timeAlignmentTimer can be set for each TAG. In addition, timeAlignmentTimer can control the period of time synchronization between the serving cell and the UL that the MAC entity considers to belong to the associated TAG. timeAlignmentTimer is also called TAT.

[0149] If the timeAlignmentTimer associated with the PTAG expires, the MAC entity performs some or all of the following (A) to (E). (PT) (A) Refresh the HARQ buffers for all serving cells belonging to the PTAG. (B) If present, notify RRC to release PUCCH for all serving cells belonging to PTAG. (C) If present, notify RRC to release SRS for all serving cells belonging to PTAG. (D) Clear all configured downlink allocations and / or all configured uplink grants. (E) All running timeAlignmentTimers are considered to have expired.

[0150] If the timeAlignmentTimer associated with the STAG expires, the MAC entity performs part or all of the following (A) to (D) with respect to all serving cells belonging to the TAG. (A) Refresh the HARQ buffer. (B) If it exists, notify RRC to release PUCCH. (C) If present, notify RRC to release SRS. (D) Clear all configured downlink allocations and / or all configured uplink grants.

[0151] Next, the deactivation (Deactivation) and activation (Activation) of SCG are explained.

[0152] Disabling of SCG may refer to disabling SCG. In addition, disabling of SCG may refer to that the MAC entity has established an association with the SCG, and the cell group corresponding to the MAC entity is disabled. In addition, disabling of SCG may also refer to disabling of PSCell (SpCell of SCG) or disabling of PSCell. Activating SCG may refer to activating SCG. In addition, activating SCG may refer to that the MAC entity has established an association with the SCG, and the cell group corresponding to the MAC entity is activated. In addition, activating SCG may also refer to activating PSCell (SPCell of SCG) or activating PSCell.

[0153] In LTE and / or NR, the disabled state of SCG may be a state in which the terminal device implements part or all of the following (A) to (P) in the PSCell (SpCell) of the SCG. In addition, the disabled state of SCG may refer to a state in which the SCG is disabled (a state in which the SCG is dormant). (SD-1) (A) SRS is not sent in this PSCell. (B) CSI for this PSCell is not measured. (C) CSI for this PSCell is not reported. (D) PUCCH is not sent in the PSCell. (E) UL-SCH is not sent in the PSCell. (F) RACH is not sent in the PSCell. (G) The PDCCH of the PSCell is not monitored. (H) The PDCCH for this PSCell is not monitored. (I) If present, switch to the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) in the PSCell. (J) Discontinuous reception (DRX) is performed in the PSCell. (K) Not monitoring the PDCCH of the PSCell and / or the PDCCH for the PSCell addressed to the C-RNTI, MCS-C-RNTI and / or CS-RNTI representing the uplink grant for sending the UL-SCH in the PSCell. (L) The BWP is activated for the PSCell, and the PDCCH of the PSCell and / or the PDCCH for the PSCell addressed to the C-RNTI, MCS-C-RNTI and / or CS-RNTI representing the uplink grant is not monitored in the BWP. (M) Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and / or Radio Link Monitoring (RLM) are performed in the PSCell. (N) Suspend some or all configured uplink grants of grant type 1 corresponding to the PSCell. (O) Maintain a time alignment timer (TAT) associated with the TAG (PTAG) including the PSCell. (P) Enable the MAC entity on the SCG side to perform a partial MAC reset.

[0154] The above-mentioned (M) of (SD-1) can be implemented based on parameters such as bfd-and-RLM included in the settings on the SCG side.

[0155] The (P) of (SD-1) may include part or all of (A) to (O) of (SD-1). In addition, the (P) of (SD-1) may include part or all of (P-1) to (P-15) described below. (P-1) Initialize the parameter Bj set for each logical channel to 0. (P-2) If all timers associated with the PSCell are running except for the timer for BFD (beamFailureDetectionTimer) and timeAlignmentTimer (TAT), stop them. (P-3) Set the value of the New Data Indicator (NDI) of all uplink HARQ processes to 0. (P-4) If yes, stop the ongoing random access procedure. (P-5) If present, explicitly signaled, 4-step and 2-step RA type contention-free Random Access (CFRA) resources are discarded. (P-6) Refresh the buffer of Msg3. (P-7) Refresh the MSGA buffer. (P-8) If present, cancel the triggered SR process. (P-9) If present, cancel the triggered BSR process. (P-10) If present, cancel the triggered PHR process. (P-11) Cancel the confirmation of the triggered configured uplink grant. (P-12) Refresh the soft buffers of all downlink HARQ processes. (P-13) In each downlink HARQ process, the next received transmission for a certain transport block (TB) is considered to be the very first transmission. (P-14) If present, release the Temporary C-RNTI. (P-15) All BFI_COUNTERs associated with the PSCell except the counter (BFI_COUNTER) used for BFD are reset.

[0156] In LTE and / or NR, the activation state of the SCG may be a state in which a terminal device implements part or all of the following (A) to (O) in the PSCell (SpCell) of the SCG. In addition, the activation state of the SCG may refer to a state in which the SCG is activated or not (a state in which the SCG is dormant). (SA-1) (A) SRS is transmitted in the PSCell. (B) Determination of the CSI for this PSCell. (C) Report the CSI for this PSCell. (D) Send PUCCH in the PSCell. (E) Send UL-SCH in the PSCell. (F) Send RACH in the PSCell. (G) Monitor the PDCCH in the PSCell. (H) Monitor the PDCCH for the PSCell. (I) If present, switch to the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) in the PSCell. (J) Discontinuous reception (DRX) is performed in the PSCell. (K) Monitoring the PDCCH of the PSCell and / or the PDCCH for the PSCell addressed to the C-RNTI, MCS-C-RNTI and / or CS-RNTI representing the uplink grant for sending the UL-SCH in the PSCell. (L) The BWP is activated in the PSCell, and the PDCCH of the PSCell and / or the PDCCH for the PSCell addressed to the C-RNTI, MCS-C-RNTI and / or CS-RNTI representing the uplink grant is monitored in the BWP. (M) Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and / or Radio Link Monitoring (RLM) are performed in the PSCell. (N) If present, then (re)initialize, according to the stored configuration, some or all of the pending configured uplink grants of grant type 1 corresponding to the PSCell. (O) Maintain a time alignment timer (TAT) associated with the TAG (PTAG) including the PSCell.

[0157] In LTE and / or NR, the terminal device can determine that the SCG is in a disabled state based on part or all of the following (A) to (H). It should be noted that the signaling and control elements of (A) to (F) below can be notified to the terminal device from the base station device via the SCG. In addition to or instead of this, the signaling and control elements of (A) to (F) below can also be notified to the terminal device from the base station device via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). (SD-2) (A) Reception of RRC signaling indicating disabling of SCG (B) Receipt of a MAC CE indicating disabling of the SCG (C) Reception of RRC signaling indicating disabling of PSCell (D) Reception of MAC CE indicating disabling of PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CEs (G) SCG disable timer expires (H)PSCell disable timer expires

[0158] The RRC signaling of (A), (C), and (E) of (SD-2) above may also include parameters such as scg-State. The SCG may be disabled by including scg-State in the RRC signaling. The SCG may also be activated by not including scg-State in the RRC signaling. The indication of activating the SCG included in the RRC signaling may be that the RRC signaling does not include an indication of disabling the SCG. The indication that the RRC signaling does not include disabling the SCG may be that the RRC signaling does not include parameters such as the scg-State. The indication that the SCG is disabled included in the RRC signaling may be that the RRC signaling includes parameters such as the scg-State. In addition, the parameter such as the scg-State may be information indicating the disabling of the SCG. In addition, the scg-State may be included in the RRC reset message or the RRC restart message. In addition, the RRC signaling may be generated in the MN.

[0159] Fig.11 FIG. 1 is a diagram showing an example of an implementation method. Fig.11 In the process, the processing unit 502 of UE122 determines that the SCG is in a disabled state based on the above (SD-2) (step S1100). In addition, the processing unit 502 of UE122 disables the SCG based on the above determination, and performs the action shown in the above (SD-1) in the disabled state of the SCG (step S1102).

[0160] In LTE and / or NR, the terminal device can determine that the SCG is in an activated state based on part or all of the following (A) to (K). It should be noted that the signaling and control elements of (A) to (F) below can be notified to the terminal device from the base station device via the SCG. In addition or instead, the signaling and control elements of (A) to (F) below can also be notified to the terminal device from the base station device via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). The SCG being in an activated state may mean that the SCG is not in a disabled state. (SA-2) (A) Receipt of RRC signaling indicating activation of SCG (B) Receipt of MAC CE indicating activation of SCG (C) Reception of RRC signaling indicating activation of PSCell (D) Reception of MAC CE indicating activation of PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CEs (G) SCG Disable Timer (H)PSCell Disable Timer (I) Start of random access procedure caused by a scheduling request triggered for sending a MAC PDU including a MAC SDU (J) Start random access process (K) Start the random access procedure caused by the scheduling request (in other words, start the MAC entity itself)

[0161] The RRC signaling of (A), (C), and (E) of (SA-2) above, such as parameters such as scg-State, may be included in an RRC reset message and / or an RRC restart message. In addition, the RRC signaling may be generated in the MN.

[0162] Fig.10 FIG. 1 is a diagram showing an example of an implementation method. Fig.10 In the process, the processing unit 502 of UE122 determines that the SCG is in an activated state based on the above (SA-2) (step S1000). In addition, the processing unit 502 of UE122 activates the SCG based on the above determination and performs the actions shown in the above (SA-1) under the activated state of the SCG (step S1002).

[0163] A terminal device that disables SCG may implement some or all of the following (A) to (I) in the SCG. (SD-3) (A) Consider SCG to be disabled. (B) Instructs lower layers (MAC entity, etc.) to disable SCG. (C) If the terminal device is in the RRC_CONNECTED state and the SCG has been activated before receiving the signaling indicating the disabling of the SCG, SRB3 is set before receiving the RRC re-configuration message or the RRC connection re-configuration message, and SRB3 is released (released) in accordance with any RRC signaling (RadioBearerConfig) for radio bearer setting included in the RRC re-configuration message or the RRC connection re-configuration message, thereby triggering the PDCP entity of the SRB3 to discard the SDU, and in addition to or instead of this, re-establish the RLC entity of the SRB3. (D) Disable all SCells. (E) It is deemed that all SCell deactivation timers associated with the activated SCell have expired. (F) It is deemed that all SCell disabling timers associated with the SCell in the dormant state have expired. (G) Do not start or restart all SCell disable timers associated with the SCell. (H) Ignore MAC CE for activating SCell For example, in the process (AD), when a MAC CE for activating SCell is received and there is no indication to disable SCG (or the SCG is not in a disabled state), process (AD-1) is performed. (I) Execute the process (AD-2). For example, in the process (AD), when it is instructed to disable the SCG (or the SCG is in a disabled state), the process (AD-2) is performed.

[0164] The MAC entity of the terminal device can disable all SCells of the SCG when (B) based on the above (SD-3) instructs the MAC entity to cause the upper layer (RRC entity, etc.) to disable the SCG. In addition to or instead of this, the PSCell can be disabled based on the above (SD-1).

[0165] The terminal device that activates the SCG can implement part or all of the following (A) to (D) in the SCG. (SA-3) (A) Consider that SCG is activated. (B) If the SCG is set to a disabled state before receiving signaling instructing the terminal device to activate the SCG, the lower layer (MAC entity, etc.) is instructed to activate the SCG. (C) In order to activate all SCells, process (AD-1) is performed. (D) When activation of the SCG is performed based on RRC signaling, if the RRC signaling includes parameters related to random access to the PSCell (SpCell), the random access procedure is started in the PSCell based on the notified parameters.

[0166] The MAC entity of the terminal device can activate the SCG based on the above (SA-1) when (B) of the above (SA-3) instructs the MAC entity to activate the upper layer (RRC entity, etc.) SCG.

[0167] When the terminal device determines that the SCG is in an activated state based on the above (SA-2), the RRC entity of the terminal device can instruct the lower layer (MAC entity, etc.) to start a random access process in the PSCell of the SCG when it determines that the following (A) or (B) is met.

[0168] (A) EN-DC or NGEN-DC is set for the terminal device, and an RRC reconfiguration message is received via SRB1 of E-UTRA or an RRC connection reconfiguration message of E-UTRA (switching from NR standalone to (NG) EN-DC), and according to the RRC signaling of E-UTRA that includes the RRC reconfiguration message for the setting on the SCG side in the form of a container, the SCG is not disabled, and the following (A-1) or (A-2) is satisfied.

[0169] (A-1) Synchronous resetting includes SpCell setting in SCG. (A-2) Before receiving the RRC signaling of E-UTRA recorded in (A) including the RRC reconfiguration message for the configuration on the SCG side in the form of a container, the SCG is disabled and at least one or more of the following (A-2-1) to (A-2-4) is satisfied.

[0170] (A-2-1) Radio link failure is detected in SCG. (A-2-2) It is configured to perform RLM in the PSCell of the disabled SCG and notify a special notification (indication #A) from the lower layer (MAC entity, etc.). (A-2-3) A special notification (indication#B) is notified from the lower layer (MAC entity, etc.). (A-2-4) RLM is not set to be performed in the PSCell of the disabled SCG.

[0171] The above-mentioned (A-2-2) can be replaced by the following (A-2-2'). (A-2-2') A special notification (indication #A) is notified from the lower layer (MAC entity, etc.).

[0172] The above (A-2-3) can be replaced by the following (A-2-3'). (A-2-3') A special notification (indication #B) is notified from a lower layer (MAC entity, etc.) and the indication #B is not canceled.

[0173] (B) When NR-DC is set for the terminal device, an RRC reconfiguration message is received via SRB1 of the SCG, and according to the RRC signaling of the NR including the RRC reconfiguration message for the setting on the SCG side in the form of a container, the SCG is not disabled and the following (B-1) or (B-2) is satisfied.

[0174] (B-1) Synchronous resetting includes SpCell settings in SCG. (B-2) Before receiving the RRC signaling of the NR recorded in (B) including the RRC reconfiguration message for the configuration on the SCG side in the form of a container, the SCG is disabled and at least one of the above (A-2-1) to (A-2-4) is satisfied.

[0175] Whether to set RLM in the PSCell of the disabled SCG can be determined by Figure 7 In other words, the above setting to perform RLM in the PSCell of the disabled SCG may be that the parameter indicates that RLM is performed in the PSCell or the parameter is included in the setting on the SCG side. In addition, the above not setting to perform RLM in the PSCell of the disabled SCG may be that the parameter indicates that RLM is not performed in the PSCell or the parameter is not included in the setting on the SCG side. In addition, whether BFD is set to be performed in the PSCell of the disabled SCG can be determined by Figure 7 The parameter such as bfd-and-RLM can be set. In other words, the above setting to perform BFD in the PSCell of the disabled SCG may be that the parameter indicates that BFD is performed in the PSCell or the parameter is included in the setting on the SCG side. In addition, not setting to perform BFD in the PSCell of the disabled SCG may be that the parameter indicates that BFD is not performed in the PSCell or the parameter is not included in the setting on the SCG side. In addition, whether to perform RLM in the PSCell of the disabled SCG and whether to perform BFD in the PSCell can be set independently of each other. In addition, the value of the parameter being set to true (True) may mean that it is set to perform RLM and BFD in the PSCell of the disabled SCG, and the value of the parameter being set to false (false) may mean that it is not set to perform RLM and BFD in the PSCell of the disabled SCG.

[0176] Fig. 9 FIG. 1 is a diagram showing an example of an implementation method. Fig. 9 In the process, UE122 receives signaling (RRC signaling, MAC CE, etc.) indicating disabling of SCG from eNB102 or gNB108 (step S900). Based on the notification, UE122 controls so that part or all of the cells of SCG are in a disabled state (step S902).

[0177] Through the above-mentioned actions, in the process of disabling the SCG, the sending unit 504 of UE122 can perform an efficient state change without independently sending a MAC CE for changing the state of the cell of the SCG to a disabled state. In addition, in the case of disabling the SCG based on RRC signaling, the initial state is previously set at the RRC layer and the state change is performed at the MAC layer, but through the above-mentioned actions, the mismatch between the indication of the RRC layer and the indication of the MAC layer can be avoided, and the state change of the SCG can be performed effectively.

[0178] Based on the above description, various embodiments of the present invention are described. It should be noted that the processes omitted in the following description can be applied to the processes described above.

[0179] Figure 5 1 is a block diagram showing the configuration of the terminal device (UE122) according to the present embodiment. Figure 5 Only the main components closely related to this embodiment are shown.

[0180] Figure 5 The UE 122 shown is composed of 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 sending unit 504 that sends control information (UCI, RRC signaling, etc.) to the base station device. The above-mentioned base station device may refer to eNB 102 or gNB 108. In addition, the processing unit 502 may include part or all of the functions of various layers (for example, the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 may include part or all of the physical layer processing unit, the MAC layer processing unit, the RLC layer processing unit, the PDCP layer processing unit, the SDAP processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0181] Figure 6 is a block diagram showing the configuration of a base station device according to this embodiment. Figure 6 Only the main components closely related to this embodiment are shown. The above-mentioned base station device can refer to eNB102 or gNB108.

[0182] Figure 6The base station device shown is composed of a sending unit 600 that sends control information (DCI, RRC signaling, etc.) to UE122, a processing unit 602 that generates control information (including DCI, parameter RRC signaling, etc.) and sends it to UE122 so that the processing unit 502 of UE122 processes it, and a receiving unit 604 that receives control information (UCI, RRC signaling, etc.) from UE122. In addition, the processing unit 602 may include part or all of the functions of various layers (such as the physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 may include part or all of the physical layer processing unit, the MAC layer processing unit, the RLC layer processing unit, the PDCP layer processing unit, the SDAP processing unit, the RRC layer processing unit, and the NAS layer processing unit.

[0183] use Fig.10 An example of processing performed by the terminal device according to the present embodiment will be described.

[0184] Fig.10 1 is a diagram showing an example of processing of the terminal device of this embodiment. The processing unit 502 of UE122 can determine that the SCG is in an activated state based on the above (SA-2) (step S1000). In addition, the processing unit 502 of UE122 can perform an action in the activated state based on the judgment (step S1002).

[0185] An example of the operation of the UE 122 in the above-mentioned activated state is described below. In the activated state, the UE 122 may perform part or all of the processing shown in the above-mentioned (SA-1) in each of the PSCell and / or one or more SCells of a certain cell group.

[0186] The activation state may be a state in which the SCG is activated. In addition, the activation state may be a state in which the SCG is resumed from a sleep state. In addition, the activation state may be a state in which the SCG is not in a sleep state. In addition, the activation state may be a state in which the SCG is transitioned from a disabled state when a random access process caused by a scheduling request triggered for sending a MAC PDU including a MAC SDU is started. In addition, the activation state may be a state in which the SCG is transitioned from a disabled state when the RRC entity indicates the resumption from the sleep state.

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

[0188] If UE122 receives an indication to activate the SCG, the SCG can be changed from a disabled state to an activated state (in other words, the SCG can be activated). In addition, if UE122 receives information indicating resumption from the sleep state of the SCG, the SCG can be changed from a disabled state to an activated state. In addition, if UE122 receives information indicating resumption from the sleep state of the PSCell, the SCG can be changed from a disabled state to an activated state. In addition, if UE122 receives other information, the SCG can be changed from a disabled state to an activated state. In addition, based on a timer for SCG sleep, UE122 can change the SCG from a disabled state to an activated state. In addition, based on a timer for PSCell sleep, UE122 can change the SCG from a disabled state to an activated state. In addition, UE122 can change the SCG from a disabled state to an activated state in the case of starting a random access process caused by a scheduling request triggered for sending a MAC PDU including a MAC SDU. In addition, UE122 can change the SCG from a disabled state to an activated state in the case of starting a random access process. In addition, UE122 can change the SCG from a disabled state to an activated state when starting a random access process caused by a scheduling request (in other words, starting the MAC entity itself). In addition, the MAC entity of UE122 can obtain an indication of activating the SCG, an indication of recovering from a dormant SCG, an indication of recovering from a dormant state of the PSCell, and / or other information from the RRC entity of UE122. In addition, after the MAC entity obtains the information from the RRC entity, UE122 can determine that the SCG is in an activated state as shown in (SA-2) above, and change the SCG from a disabled state to an activated state. UE122 can perform the processing shown in (SA-3) above when changing the SCG from a disabled state to an activated state.

[0189] use Fig.11 An example of processing performed by the terminal device according to the present embodiment will be described.

[0190] Fig.11 1 is a diagram showing an example of processing of the terminal device of this embodiment. The processing unit 502 of UE122 can determine that the SCG is in a disabled state based on the above (SD-2) (step S1100). In addition, the processing unit 502 of UE122 can perform an action in the disabled state based on the judgment (step S1102).

[0191] An example of the operation of the UE 122 in the deactivated state is described below. In the deactivated state, the UE 122 may perform part or all of the processing shown in (SD-1) in each of the PSCell and / or one or more SCells of a certain cell group.

[0192] The disabled state may be a state in which the SCG is disabled. In addition, the disabled state may be a state in which the SCG is entering a dormant state. In addition, the disabled state may be a state in which the Active BWP of the PSCell and / or one or more SCells of the SCG is a dormant BWP. In addition, the disabled state may also be a state in which a transition from an activated state is made when an indication is given to enter a dormant state from an RRC entity.

[0193] In step S1100, as shown in (SD-2) above, the processing unit 502 of UE 122 may determine that the SCG has changed from an activated state to a deactivated state.

[0194] If UE122 receives information indicating the disabling of SCG, the SCG may be changed from an activated state to a disabled state. In addition, if UE122 receives information indicating entering a dormant SCG, the SCG may be changed from an activated state to a disabled state. In addition, if UE122 receives information indicating the dormancy of a PSCell, the SCG may be changed from an activated state to a disabled state. In addition, if UE122 receives other information, the SCG may be changed from an activated state to a disabled state. In addition, in the event that the timer regarding the dormancy of the SCG expires, the UE122 may change the SCG from an activated state to a disabled state. In addition, in the event that the timer regarding the dormancy of the PSCell expires, the UE122 may change the SCG from an activated state to a disabled state. In addition, the MAC entity of UE122 may obtain an indication of disabling the SCG, an indication of entering a dormant SCG, an indication of dormancy of the PSCell, and / or other information from the RRC entity of UE122. In addition, after the MAC entity obtains the information from the RRC entity, UE122 can determine that the SCG is in a disabled state as shown in (SD-2) above, and change the SCG from an activated state to a disabled state. UE122 can perform the processing shown in (SD-3) above when changing the SCG from an activated state to a disabled state.

[0195] use Fig.12 An example of processing performed by the terminal device according to the present embodiment will be described.

[0196] Fig.12 This is a diagram showing an example of processing of a terminal device according to the present embodiment. The processing unit 502 of the UE 122 configured to perform BFD in the PSCell of the disabled SCG by the RRC signaling received from the transmission unit 600 of the gNB 108 makes a condition judgment (step S1200), and performs an action based on the judgment (step S1202).

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

[0198] If UE122 determines in step S1200 that one or both of the conditions (1) and (2) are satisfied, in step S1202, UE122 may set the beam failure counter to 0. If UE122 determines in step S1200 that neither of the conditions (1) and (2) are satisfied, in step S1202, UE may not set the beam failure counter to 0. “Setting the beam failure counter to 0” may be renamed as “resetting the beam failure counter”, and “not setting the beam failure counter to 0” may be renamed as “not resetting the beam failure counter”.

[0199] The condition (c) may also be renamed to mean that BFD is not stopped. For example, it may be replaced with statements such as "performing BFD", "not notifying the upper layer of beam failure", "restarting BFD after the last notification of beam failure to the upper layer", "not stopping BFD to the lower layer", "restarting BFD after the last notification of stopping BFD to the lower layer". In addition, the statement "restarting BFD" may also be replaced with other similar expressions. For example, it may be renamed to "performing BFD from the upper layer notification", "changing BFD-RS", "performing BFD to the lower layer notification", and so on.

[0200] In addition, use Fig.12 Another example of the processing of the terminal device of the present embodiment is described. The processing unit 502 of the UE 122 configured to perform BFD in the PSCell of the disabled SCG by the RRC signaling received from the transmission unit 600 of the gNB 108 makes a condition judgment (step S1200), and takes action based on the judgment (step S1202).

[0201] UE 122 may determine whether a condition is met in step S1200. The condition may be one or more combinations of the following conditions. (a) Notify the upper layer of beam failure. (b) Notify the upper layer to stop BFD. (c) Notify the lower layer to stop BFD.

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

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

[0204] In addition, the condition (b) may also mean that the upper layer instructs the lower layer to stop BFD in the PSCell. In addition, the condition (c) may also be replaced by a condition for notifying the lower layer to stop BFD. For example, it may be a combination of multiple conditions from the conditions (a-1) to (a-7). In addition, the statement "notifying the lower layer to stop BFD" may be renamed as "notifying the lower layer not to measure BFD-RS", "not providing notification of beam failure instances to the lower layer", "disabling BWP for BFD", etc. In addition, the condition (c) may be renamed as "not resetting the SCG through the BFD-RS after the last notification to the lower layer to stop BFD", "not changing the BFD-RS after the last notification to the lower layer to stop BFD", etc.

[0205] In addition, use Fig.12 Another example of the processing of the terminal device of this embodiment is described. The processing unit 502 of UE122 that receives the RRC signaling including the indication of activating SCG from the sending unit 600 of gNB108 makes a condition judgment (step S1200) and takes action based on the judgment (step S1202).

[0206] The RRC of UE 122 notifies the lower layer of the activation of the SCG based on the RRC signaling including the instruction to activate the SCG received from the base station apparatus. The MAC of UE 122 instructed to activate the SCG from the upper layer can determine whether one or more of the following conditions are satisfied in step S1200. (a) Beam failure in PSCell. (b) TAT associated with PTAG is not running.

[0207] The MAC of UE122 determines in step S1200 whether one or more of the conditions are met. If it is determined that one or more of the conditions are met, the MAC of UE122 may notify the upper layer of the need for a random access procedure in step S1202. If it is determined that any of the conditions is not met, the MAC of UE122 may not notify the upper layer of the need for a random access procedure in step S1202.

[0208] The condition (a) can also be expressed as follows. (a-1) In the PSCell, the beam failure counter is equal to or greater than the beam failure counter threshold. (a-2) BFD is stopped in PSCell. (a-3) After the failure of the PSCell beam is finally notified to the upper layer, the BFD-RS of the PSCell is not reset.

[0209] The various embodiments may also be combined with each other. In addition, in each embodiment, stopping BFD may mean stopping BFD in MAC, or stopping BFD in PHY, and further, stopping BFD in both MAC and PHY. Stopping BFD in MAC may mean not performing part or all of the process for beam failure detection and beam failure recovery. In addition, stopping BFD in PHY may mean not performing the measurement of BFD-RS corresponding to the stopped BFD in PHY, disabling BWP for BFD, or not providing the beam failure instance notification to MAC regardless of the measurement result of BFD-RS corresponding to the stopped BFD. In addition, BFD in MAC may be stopped by RRC or indicated by RRC. In addition, BFD in MAC may be stopped by MAC. In addition, BFD in PHY may be stopped by MAC or indicated by MAC. In addition, MAC or PHY may stop BFD based on an upper layer indicating to stop BFD. Restarting BFD may be interchangeable with performing BFD. The judgment of whether to restart or stop BFD may be made for each service cell, or the judgment of whether to restart or stop BFD may be made for each service cell.

[0210] In addition, in each embodiment, the MAC entity of UE122 configured to perform BFD in the PSCell of the disabled SCG starts or restarts the beam failure detection timer (beamFailureDetectionTimer) based on the beam failure instance notification (beam failure instanceindication) received (has been received) from the lower layer, increases the value of the beam failure counter (BFI_COUNTER) by 1, and notifies the upper layer of the beam failure of the PSCell based on at least the value of the beam failure counter being above the beam failure counter threshold (beamFailureInstanceMaxCounter). Other conditions for notifying the upper layer of the beam failure of the PSCell may be added. In addition, when the conditions for notifying the upper layer of the beam failure of the PSCell are met, the MAC may stop BFD for the lower layer notification. In addition, the statement "stop BFD for the lower layer notification" may be renamed as "do not measure BFD-RS for the lower layer notification", "do not provide beam failure instance notification for the lower layer notification", "disable BWP for BFD", etc. The MAC may determine that a beam failure is detected based on the value of the beam failure counter being above the beam failure counter threshold. In addition, the detection of a beam failure may also be simply renamed as a beam failure. The UE may set the value of the beam failure counter to 0 when the beam failure detection timer, the beam failure counter threshold, or the BFD-RS is reset by the upper layer. In addition, the UE may also set the value of the beam failure counter to 0 based on at least the expiration of the beam failure detection timer. In addition, other conditions for setting the value of the beam failure counter to 0 may also be added. In addition, the PHY300 of the UE122 that is set to perform BFD in the PSCell of the disabled SCG may provide a notification to the upper layer (MAC, etc.) when the radio link quality of the BFD-RS measured in the BWP of the PSCell is worse (lower) than the threshold set by the upper layer (RRC, etc.). The notification may be a beam failure instance notification.

[0211] In addition, in each embodiment, the BFD-RS may be a reference signal for beam failure detection (BFD). In addition, the BFD-RS may be a reference signal as follows: in a radio link monitoring RS setting (RadioLinkMonitoringRS) including radio link monitoring RS identifier information (RadioLinkMonitoringRS-Id) for identifying a reference signal, information indicating the purpose of monitoring the failure of a beam is set in the information indicating the purpose of monitoring, or information indicating both the purpose of monitoring the failure of a radio link and the purpose of monitoring the failure of a beam. The radio link monitoring RS setting may be included in the radio link monitoring setting. The radio link monitoring setting may be a setting for radio link monitoring for setting a beam and / or for detecting the failure of a cell radio link. "Resetting the BFD-RS" may be "resetting the BFD-RS according to the radio link monitoring setting related to the BFD-RS included in a message related to the RRC resetting". Resetting the BFD-RS according to the radio link monitoring setting related to the BFD-RS included in a message related to the RRC resetting may also be referred to as changing the BFD-RS. The wireless link monitoring setting related to BFD-RS can be a wireless link monitoring setting including a wireless link monitoring RS setting, and the wireless link monitoring setting includes information indicating the purpose of monitoring the failure of the beam or information indicating both the purpose of monitoring the failure of the wireless link and the purpose of monitoring the failure of the beam in the information indicating the purpose of monitoring.

[0212] In addition, the RRC of UE122 may stop the BFD of the PSCell based on the notification of the beam failure of the PSCell from the lower layer, or may stop the BFD of the PSCell based on the reconfiguration by the base station device, for example, using parameters such as bfd-and-RLM, so that BFD is not performed in the PSCell of the disabled SCG, or may stop the BFD of the PSCell based on the detection of a radio link failure in the SCG, or may stop the BFD of the PSCell based on other conditions. In addition, the RRC of UE122 may also notify the lower layer to start or restart BFD in the PSCell based on the RRC signaling received from the base station device, such as reconfiguring the BFD-RS to perform BFD in the PSCell of the disabled SCG, setting or reconfiguring to perform BFD in the PSCell of the disabled SCG, receiving an activated SCG, etc. In addition, "notifying the lower layer to start or restart BFD" may be renamed as "notifying the lower layer to perform BFD."

[0213] In addition, once the beam failure detection timer and the timer including TAT are started, they run (running) until they stop (stop) or expire (expire), otherwise they do not run. In addition, the timer is started when it is not running, and restarted when it is running. In addition, the timer is always started or restarted from the initial value. The interval from the start or restart of the timer to the expiration is not updated until the timer stops or expires. In the case where the MAC entity sets the interval from the start or restart of the timer to the expiration to 0, the timer expires immediately after starting unless otherwise specified for other conditions.

[0214] Based on non-patent document 9, a UE configured to perform BFD in a PSCell of a disabled SCG stops BFD when it is determined that a beam has failed. When BFD in PHY is stopped but BFD in MAC is not stopped, based on non-patent document 8, in MAC, a beam failure instance notification is not provided from the lower layer, thereby setting the beam failure counter to 0 despite the beam failure. In this case, sometimes when the SCG is activated, it is determined that it is not a beam failure, and the need for a random access procedure is not notified to the upper layer. Through the above embodiments, the UE can appropriately determine whether a random access procedure is required when the SCG is activated.

[0215] In the above description, the MAC entity of the UE can judge part or all of the following (A) to (C), and based on these judgments, notify the RRC entity of indication #A. (A) Expiration of the TAT associated with the TAG (PTAG) of the PSCell including the SCG (B) SCG is disabled (C) Notification from the RRC entity that is not configured to perform RLM in the PSCell of the disabled SCG

[0216] In addition to or instead of the above description, the MAC entity of the UE may determine part or all of the following (A) to (C), and based on these determinations, notify the RRC entity of indication #B. (A) SCG is disabled (B) Detection of beam failure (BF) in PSCell (C) Set to perform BFD in the PSCell of the disabled SCG

[0217] In the above description, the instruction #A may be a notification (signaling) indicating the following (A) and / or (B). In addition to or instead of this, the instruction #A may be a notification (signaling) indicating something other than the following (A) and (B). (A) A random access procedure is required when activating SCG (B) Expiration of the TAT associated with the TAG (PTAG) of the PSCell including the SCG

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

[0219] In addition to or in lieu of the above description, the RRC entity of the UE may cancel indication #B based on part or all of the following (A) to (C). In addition to or in lieu of the above description, the RRC entity of the UE may cancel indication #B based on anything other than the following (A) to (C). (A) A message related to re-setting of an RRC connection including RadioLinkMonitoringConfig is received in the disabled state of the SCG (B) In the disabled state of SCG, the reference signal for BFD (BFD RS) is changed (C) Beam failure detected in the PSCell of the SCG has been recovered

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

[0221] In addition, unless otherwise specified, the wireless bearer in the above description may be a DRB, an SRB, or a DRB and an SRB.

[0222] Furthermore, in the above description, expressions such as "notify", "accept the blame", etc. can be used interchangeably.

[0223] Furthermore, in the above description, expressions such as “associated with”, “establishing correspondence”, and “establishing association” can be interchangeable.

[0224] Furthermore, in the above description, expressions such as “include”, “contain”, “including”, etc. can be replaced with each other.

[0225] Furthermore, in the above description, "the" may be replaced by "the above-mentioned".

[0226] In addition, in the above description, "SpCell of SCG" can be renamed as "PSCell".

[0227] Furthermore, in the above description, expressions such as "determined to be ...", "set to be ...", and "including ..." can be replaced with each other.

[0228] In the above description, "sleep state" may be renamed as "disabled state", and "state restored from sleep state" may be renamed as "activated state". In addition, in the above description, "activate" and "disable" may be renamed as "activated state" and "disabled state", respectively.

[0229] In the above description, “transition from X to Y” may be replaced by “transition from X to Y.” Also, in the above description, “cause transition” may be replaced by “determine transition.”

[0230] In addition, in the examples of each processing or the examples of the processes of each processing in the above description, some or all of the steps may not be executed. In addition, in the examples of each processing or the examples of the processes of each processing in the above description, the order of the steps may be different. In addition, in the examples of each processing or the examples of the processes of each processing in the above description, some or all of the processing in each step may not be executed. In addition, in the examples of each processing or the examples of the processes of each processing in the above description, the order of the processing in each step may be different. In addition, in the above description, "based on A, perform B" may also be renamed as "perform B". That is, "perform B" may also be performed independently of "is A".

[0231] It should be noted that in the above description, "A may be renamed as B" includes not only the meaning of renaming A as B, but also the meaning of renaming B as A. In addition, in the above description, when "C may be D" and "C may be E" are recorded, the case of "D may be E" may be included. In addition, in the above description, when "F may be G" and "G may be H" are recorded, the case of "F may be H" may be included.

[0232] Furthermore, in the above description, when the condition “A” and the condition “B” are opposite conditions, the condition “B” can be expressed as an “other” condition of the condition “A”.

[0233] The program operated by the device of this embodiment can be a program that controls the central processing unit (CPU) and the like to make the computer function to realize the functions of this embodiment. The program or the information processed by the program is temporarily read into a volatile memory such as a random access memory (RAM) or stored in a non-volatile memory such as a flash memory or a hard disk drive (HDD) during processing, and is read, modified, or written by the CPU as needed.

[0234] It should be noted that a part of the device in the above-mentioned embodiment can be implemented by a computer. In this case, the program for implementing the control function can be recorded in a computer-readable recording medium, and the program recorded in the recording medium is read into a computer system and executed. The "computer system" mentioned here refers to a computer system built into the device, and includes a computer system of hardware such as an operating system and peripheral devices. In addition, the "computer-readable recording medium" can be any one of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, etc.

[0235] Furthermore, "computer-readable recording medium" may also include: a recording medium that stores a program dynamically for a short period of time, such as a communication line when the program is transmitted via a network such as the Internet or a communication line such as a telephone line; and a recording medium that stores a program for a fixed period of time, such as a volatile memory inside a computer system that serves as a server or client in this case. In addition, the above program may be a program for realizing a part of the above functions, or a program that can realize the above functions by combining with a program already recorded in a computer system.

[0236] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be implemented or executed by a circuit, that is, typically by an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, and the processor may also be replaced by an existing processor, controller, microcontroller or state machine. The general-purpose processor or the above-mentioned circuits may be composed of digital circuits or analog circuits. In addition, in the case of an integrated circuit technology that replaces the existing integrated circuits as semiconductor technology advances, integrated circuits based on this technology may also be used.

[0237] It should be noted that the present embodiment is not limited to the above-mentioned embodiment. In the embodiment, an example of a device is described, but the present embodiment is not limited thereto and can be applied to fixed or non-movable electronic devices set up indoors and outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as other living equipment.

[0238] The present embodiment has been described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present embodiment. In addition, the present embodiment can be modified in various ways within the scope indicated by the claims, and the embodiment obtained by appropriately combining the technical solutions disclosed in different embodiments is also included in the technical scope of the present embodiment. In addition, it also includes a configuration obtained by replacing elements that have the same effect as the elements described in the above embodiments with each other. Industrial Applicability

[0239] One aspect of the present invention can be used for example in a communication system, a communication device (such as a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (such as a communication chip), a program, or the like. Description of Reference Numerals 100: E-UTRA 102: eNB 104: EPC 106: NR 108: gNB 110:5GC 112, 114, 116, 118, 120, 124: Interface 122:UE 200, 300: PHY 202, 302: MAC 204, 304: RLC 206, 306: PDCP 208, 308: RRC 310: SDAP 210, 312: NAS 500, 604: Receiving department 502, 602: Processing Department 504, 600: Sending department

Claims

1. A terminal device for communicating with a base station device, the terminal device comprising: A processing unit, communicating using a primary cell group MCG and a secondary cell group SCG; and a receiving unit, receiving, from the base station device, radio resource control RRC signaling including information indicating the deactivation of the SCG, The SCG includes a primary and secondary cell PSCell, The processing unit at least includes a radio resource control (RRC) layer processing unit, a media access control (MAC) layer processing unit and a physical (PHY) layer processing unit. The RRC layer processing unit notifies the MAC layer processing unit according to the information included in the RRC signaling, indicating whether beam failure detection BFD is performed in the PSCell of the disabled SCG, The MAC layer processing unit determines whether a condition that the BFD is stopped in the PSCell of the disabled SCG is notified from the RRC layer processing unit is satisfied, and if it is determined that the condition is satisfied, stops the beam failure detection timer, and if it is determined that the condition is not satisfied, does not stop the beam failure detection timer, The beam failure detection timer is a timer that is started or restarted based on receiving a first notification from the PHY layer processing section, and the MAC layer processing section sets a value of a first counter to 0 based on expiration of the beam failure detection timer.

2. A method for a terminal device, the terminal device communicating with a base station device, in which: Use the main cell group MCG and the secondary cell group SCG for communication. receiving, from the base station device, radio resource control RRC signaling including information indicating deactivation of the SCG, The SCG at least includes a primary and secondary cell PSCell, At least perform processing at the radio resource control RRC layer, the media access control MAC layer, and the physical PHY layer. The method comprises: The RRC layer notifies the MAC layer according to the information included in the RRC signaling, indicating whether beam failure detection BFD is performed in the PSCell of the disabled SCG; and The MAC layer determines whether a condition that the BFD is stopped in the PSCell of the disabled SCG is notified from the RRC layer, and if the condition is determined to be met, stops the beam failure detection timer; if the condition is determined not to be met, does not stop the beam failure detection timer. The beam failure detection timer is a timer that is started or restarted based on receiving a first notification from the PHY layer, and the MAC layer sets a value of a first counter to 0 based on expiration of the beam failure detection timer.

3. An integrated circuit installed in a terminal device that communicates with a base station device, the integrated circuit having the following functions: Function of communicating using the primary cell group MCG and the secondary cell group SCG; A function of receiving, from the base station device, radio resource control RRC signaling including information indicating deactivation of the SCG; At least perform the processing of the radio resource control RRC layer, the media access control MAC layer and the physical PHY layer; The function of the RRC layer is to notify the MAC layer according to the information included in the RRC signaling, indicating whether beam failure detection BFD is performed in the PSCell of the disabled SCG; and The function of the MAC layer is to determine whether a condition that the BFD is stopped in the PSCell of the disabled SCG is notified from the RRC layer, and if it is determined that the condition is met, the beam failure detection timer is stopped; if it is determined that the condition is not met, the beam failure detection timer is not stopped. The SCG at least includes a primary and secondary cell PSCell, The beam failure detection timer is a timer that is started or restarted based on receiving a first notification from the PHY layer, and the MAC layer sets a value of a first counter to 0 based on expiration of the beam failure detection timer.

Images