Terminal device, method, and integrated circuit

Abstract

To provide a terminal device, a method, and an integrated circuit for activating a cell group in dual connectivity.SOLUTION: In a communication system, a MAC entity of a terminal device notifies an RRC entity that a random access procedure is required when activating an SCG on the basis of TAT associated with a TAG including a PScell having expired and the SCG being in an inactive state, and when transitioning the SCG from an inactive state to an active state, the RRC entity instructs the MAC entity to initiate a random access procedure on the basis of the notification from the MAC entity having been issued during the inactive state.SELECTED DRAWING: Figure 14

Description

[Technical field]

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

[0002] The 3G Partnership Project, a standardization project for cellular mobile communication systems In the 3rd Generation Partnership Project (3GPP), Technical studies and standardization of cellular mobile communication systems, including services, are currently underway.

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

[0004] In addition, 3GPP has begun technical discussions 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). Technical studies and standards development are underway. [Prior art documents] [Non-patent literature]

[0005]

Non-licensed literature 1

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

Non-licensed Document 7

[0006] As an extension of NR technology, there is a dual connectivity (also called multi-connectivity) technology in which one or multiple base station devices and terminal devices communicate using multiple cell groups to enable large-volume data communication. With this dual connectivity, in order to communicate in each cell group, the terminal device needs to monitor each cell group for the presence or absence of messages addressed to it. When large-volume data communication occurs, the terminal device needs to constantly monitor multiple cell groups so that it can communicate with low latency, which poses the problem of consuming a lot of power. For this reason, it is necessary to constantly monitor multiple cell groups so that the terminal device can communicate with low latency when large-volume data communication occurs. A technique to reduce or stop monitoring (deactivated cell groups) The study of the technology has begun.

[0007] Non-Patent Document 7 is a proposed Change Request (CR) for the RRC specifications, which was created based on the detailed specifications that have been agreed upon so far. However, based on the current CR proposal, For reasons of scalability, the MAC must initiate a random access procedure when not needed. There is a risk of unnecessary signaling occurring.

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

[0009] In order to achieve the above object, one aspect of the present invention provides the following means. That is, one aspect of the present invention provides a terminal device that communicates with a base station device, the terminal device comprising a processing unit that communicates using an MCG and an SCG, and a receiving unit that receives signaling from the base station device, the MCG being The SCG includes at least a PSCell, and the processing unit includes a MAC entity. The MAC entity determines whether a TAT associated with a TAG including the PSCell has expired and the SCG is in an inactive state, and based on the determination that a TAT associated with a TAG including the PSCell has expired and the SCG is in an inactive state, notifies the RRC entity of a notification indicating that a random access procedure is necessary when activating the SCG, and when transitioning the SCG from an inactive state to an active state, the RRC entity determines whether the notification has been notified from the MAC entity during the inactive state, and when transitioning the SCG from an inactive state to an active state, instructs the MAC entity to start a random access procedure based on the determination that the notification has been notified from the MAC entity during the inactive state.

[0010] Another aspect of the present invention is a method for a terminal device to communicate with a base station device, the method comprising: communicating using an MCG and an SCG, the MCG including at least a PCell, the SCG including at least a PSCell, The MAC entity of the terminal device detects that a TAT associated with a TAG including the PSCell has expired, and determining whether the SCG is in an inactive state, and based on the determination that a TAT associated with a TAG including the PSCell has expired and the SCG is in an inactive state, notifying an RRC entity of the terminal device of a notification indicating that a random access procedure is required when activating the SCG, and when transitioning the SCG from an inactive state to an active state, the RRC entity of the terminal device notifies the MAC entity of the notification during the inactive state. When the SCG is transitioned from an inactive state to an active state, Upon determining from the MAC entity that the notification was notified during the inactive state, Based on the received signal, the MAC entity of the terminal device is instructed to initiate a random access procedure. Show.

[0011] Another aspect of the present invention is an integrated circuit implemented in a terminal device that communicates with a base station device, communicating using an MCG and an SCG, the MCG including at least a PCell, and the SCG including at least a PSCell, and the integrated circuit causes the terminal device to perform a function of determining whether a TAT associated with a TAG including the PSCell has expired and the SCG is in an inactive state by a MAC entity of the terminal device, and based on the determination that a TAT associated with a TAG including the PSCell has expired and the SCG is in an inactive state, notifying an RRC entity of the terminal device of a notification indicating that a random access procedure is required when activating the SCG, and determining whether the RRC entity of the terminal device has notified the notification from the MAC entity during the inactive state when transitioning the SCG from an inactive state to an active state, and instructing the MAC entity of the terminal device to initiate a random access procedure based on the determination that the notification has been notified from the MAC entity during the inactive state when transitioning the SCG from the inactive state to the active state.

[0012] Another aspect of the present invention is a base station device that communicates with a terminal device, the base station device comprising: a processing unit that communicates using an MCG and an SCG; and a transmission unit that transmits signaling to the terminal device, the MCG being The SCG includes at least a PCell, and the SCG includes at least a PSCell, and the processing unit is configured to detect when a TAT associated with a TAG including the PSCell has expired and It is determined whether the SCG is in an inactive state, and a TAT associated with a TAG including the PSCell is Based on the determination that the SCG has expired and that the SCG is in an inactive state, the RRC entity of the terminal device is informed that a random access procedure is required when activating the SCG. The RRC entity of the terminal device notifies a MAC entity of the terminal device of a notification indicating the inactive state, and when the RRC entity of the terminal device transitions the SCG from an inactive state to an active state, the RRC entity of the terminal device determines whether the notification has been notified from the MAC entity during the inactive state, and when the RRC entity of the terminal device transitions the SCG from an inactive state to an active state, instructs the MAC entity of the terminal device to initiate a random access procedure based on the determination that the notification has been notified from the MAC entity during the inactive state.

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

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

[0015] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of an E-UTRA protocol configuration according to the present embodiment. [Diagram 3] FIG. 1 is a diagram showing an example of an NR protocol configuration according to the present embodiment. [Figure 4] FIG. 2 is a diagram showing an example of a procedure flow for various settings in the RRC according to the present embodiment. [Diagram 5] FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment. [Figure 6] FIG. 2 is a block diagram showing the configuration of a base station device in the present embodiment. [Figure 7] An example of an ASN.1 description included in a message regarding reconfiguration of an RRC connection in NR in this embodiment. [Figure 8] 13 is an example of an ASN.1 description included in a message regarding re-establishment of an RRC connection in E-UTRA in this embodiment. [Figure 9] 1 shows an example of a process for inactivating SCG in this embodiment. [Figure 10] 3 shows an example of a process related to SCG activation in this embodiment. [Figure 11] 1 shows an example of a process for inactivating SCG in this embodiment. [Figure 12] 4 is an example of processing related to a MAC entity of a terminal device in this embodiment. [Figure 13] 13 is an example of processing related to an RRC entity of a terminal device in this embodiment. [Figure 14] 1 shows an example of processing related to a base station device, a MAC entity of a terminal device, and an RRC entity in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0018] In this embodiment, the names of the nodes and entities and the processes in the nodes and entities are described when the radio access technology is E-UTRA or NR, but this embodiment may be used for other radio access technologies. The names of the nodes and entities in this embodiment may be different names.

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

[0020] The E-UTRA 100 may be a radio access technology. The air interface between the UE 122 and the eNB 102 may be referred to as a Uu interface. The eNB (E-UTRAN Node B) 102 is the basis of the E-UTRA 100. The eNB 102 may be a base station device. The eNB 102 may have an E-UTRA protocol, which will be described later. The E-UTRA protocol includes an E-UTRA User Plane (UP) protocol, which will be described later, and an E-UTRA control protocol, which will be described later. The eNB 102 may be configured with a control plane (CP) protocol. The eNB may terminate an E-UTRA User Plane (UP) protocol and an E-UTRA Control Plane (CP) protocol. A radio access network configured by the eNB may be referred to as an E-UTRAN.

[0021] The EPC (Evolved Packet Core) 104 may be a core network. The interface 112 is an interface between the eNB 102 and the EPC 104, and may be referred to as an S1 interface. The interface 112 may include a control plane interface through which control signals pass and / or a user plane interface through which user data passes. The control plane interface of this interface may terminate at a Mobility Management Entity (MME; not shown) in the EPC 104. The user plane interface of interface 112 may terminate at a service management entity (MME) in the EPC 104. The control plane interface of interface 112 may be referred to as an S1-MME interface. The interface may be called the S1-U interface.

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

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

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

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

[0026] The eNB 102 may have a function to connect to the 5GC 110. The eNB 102 having a function to connect to the 5GC 110 may be called an ng-eNB. The interface 114 is an interface between the eNB 102 and the 5GC 110, and is an NG The interface 114 may be referred to as a control plane through which control signals pass. There exists a user plane interface through which user data passes. The control plane interface of the interface 114 may terminate at an AMF in the 5GC 110. The user plane interface of the interface 114 may terminate at a UPF in the 5GC 110. The control plane interface of the interface 114 may be referred to as an NG-C interface. The user plane interface of the interface 114 may be referred to as an NG-U interface. A radio access network consisting of an ng-eNB or a gNB may be referred to as an NG-RAN. The NG-RAN, E-UTRAN, etc. may simply be referred to as a network. In addition, the network may include an eNB, an ng-eNB, a gNB, etc.

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

[0028] The gNB 108 may have a function to connect to the EPC 104. The gNB 108 having a function to connect to the EPC 104 may be called an en-gNB. The interface 118 is an interface between the gNB 108 and the EPC 104, and is an S1 The interface 118 may be referred to as a user program interface through which user data passes. There may be a lane interface. The user plane interface of the interface 118 may terminate at an S-GW (not shown) in the EPC 104. The interface between the eNB 102 and the gNB 108 may be referred to as an S1-U interface. The eNB 102 and the gNB 108 may be connected to the EPC 104 via an interface 120. The interface between the eNB 102 and the gNB 108 may be referred to as an X2 interface.

[0029] The interface 124 is an interface between the EPC 104 and the 5GC 110, and is either CP only or UP only. Alternatively, the interface 114 may be an interface that passes both the CP and the UP. Some or all of the interfaces such as interface 116, interface 118, interface 120, and interface 124 may be configured according to the communication system provided by the communication carrier or the like. It may not exist.

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

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

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

[0033] There may be no PDU sessions and / or QoS flows in the EPC 104. Also, there may be no EPS bearers in the 5GC 110. When the UE 122 is connected to the EPC 104, the UE 122 does not need to know the information of the EPS bearers. In addition, when the UE 122 is connected to the 5GC 110, the UE 122 has information about the PDU session and / or the QoS flow, but does not have information about the EPS bearer.

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

[0035] FIG. 2 is a diagram of an example of an E-UTRA protocol architecture according to this embodiment. FIG. 3 is a diagram of an example of an NR protocol architecture according to this embodiment. The functions of each protocol described with reference to FIG. 3 are some of the functions closely related to this embodiment. In this embodiment, the uplink (UL) and A downlink (DL) may be a link from a terminal device to a base station device. In this embodiment, a downlink (DL) may be a link from a base station device to a terminal device.

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

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

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

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

[0040] The AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the eNB 102 and / or the gNB 108. In other words, the AS layer may be a layer including the PHY 200, the MAC 202, the RLC 204, the PDCP 206, and a part of the RRC 208 or Layers including all of and / or any of PHY 300, MAC 302, RLC 304, PDCP 306, SDAP 310, and RRC 308. It may be a layer that includes part or all of the above.

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

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

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

[0044] Note that data provided from MAC, RLC, PDCP, and SDAP to lower layers, and / or data provided from lower layers to MAC, RLC, PDCP, and SDAP, may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, data provided from higher layers to MAC, RLC, PDCP, and SDAP, and / or data provided from MAC, RLC, PDCP, and SDAP to higher layers may be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Also, a segmented RLC SDU may be called an RLC SDU segment.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] BCCH (Broadcast Control Channel) is used to transmit control information such as System Information (SI). It may be a downlink logical channel for broadcasting control information.

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

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

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

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

[0063] Uplink logical channels and transport channels in E-UTRA and / or NR The mapping will now be described.

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

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

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

[0067] E-UTRA and / or NR downlink logical and transport channels The mapping will now be described.

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

[0069] The PCCH is mapped to the PCH (Paging Channel), which is a downlink transport channel. That's fine.

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

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

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

[0073] An example of the function of the RLC will be described. The RLC may be called an RLC sublayer. The E-UTRA RLC may have a function of segmenting and / or concatenating data provided from the PDCP of the higher layer and providing it to a lower layer. The E-UTRA RLC may have a function of reassembling and re-ordering the data provided from the lower layer and providing it to the higher layer. The NR RLC may have a function of adding a sequence number independent of the sequence number added by the PDCP to the data provided from the PDCP of the higher layer. The NR RLC may also have a function of segmenting the data provided from the PDCP and providing it to the lower layer. The NR RLC may also have a function of reassembling the data provided from the lower layer and providing it to the higher layer. The RLC may also have a function of retransmitting data and / or a function of requesting retransmission (Automatic Repeat reQuest: ARQ). RLC may also have a function to perform error correction by ARQ. The control information sent from the receiving side of RLC to the transmitting side to indicate data that needs to be retransmitted in order to perform ARQ may be called a status report. The status report transmission instruction sent from the transmitting side of RLC to the receiving side may be called a poll. RLC may also have a function to detect data duplication. RLC may also have a function to discard data. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). In TM, data received from the upper layer is not divided, and an RLC header does not need to be added. The TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or a receiving TM RLC entity.In UM, the division and / or concatenation of data received from a higher layer, the addition of an RLC header, etc. are performed, but the retransmission control of data is not required. The UM RLC entity may be a unidirectional entity or a bi-directional entity. If the UM RLC entity is a unidirectional entity, the UM RLC entity may be configured as a transmitting UM RLC entity or a receiving UM RLC entity. If the UM RLC entity is a bi-directional entity, the UM RLC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. In AM, the division and / or concatenation of data received from a higher layer, the addition of an RLC header, the retransmission control of data, etc. are performed. The AM RLC entity is a bi-directional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side. Note that data provided to a lower layer in TM and / or data provided from a lower layer may be called a TMD PDU. Also, data provided to a lower layer in UM and / or data provided from a lower layer may be called a UMD PDU. Moreover, data provided to a lower layer in AM or data provided from a lower layer may be called AMD PDU. The RLC PDU format used in E-UTRA RLC and the RLC PDU format used in NR RLC may be different. Furthermore, RLC PDUs may include RLC PDUs for data and RLC PDUs for control. The RLC PDUs for data may be called RLC DATA PDU (RLC Data PDU). The RLC PDUs for control may be called RLC CONTROL PDU (RLC Control PDU).

[0074] An example of the function of PDCP will be described. PDCP may be called a PDCP sublayer. PDCP may have a function of maintaining sequence numbers. PDCP may also have a header compression / decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over wireless sections. A protocol used for header compression / decompression of IP packets may be called ROHC (Robust Header Compression) protocol. A protocol used for header compression / decompression of Ethernet frames may be called EHC (Ethernet (registered trademark) Header Compression) protocol. PDCP may also have a function of data encryption / decryption. PDCP may also have a function of data integrity protection / integrity verification. PDCP may also have a re-ordering function. PDCP may also have a function of retransmitting PDCP SDUs. PDCP may also have a function of discarding data using a discard timer. PDCP may also have a duplication function. PDCP may also have a function to discard duplicated data. The PDCP entity is a bidirectional entity and may be composed of a transmitting PDCP entity and a receiving PDCP entity. The PDCP PDU format used in E-UTRA PDCP may differ from the PDCP PDU format used in NR PDCP. The PDCP PDU may include data PDCP PDUs and control PDCP PDUs. The data PDCP PDU may be called PDCP DATA PDU (PDCP Data PDU). The control PDCP PDU may be called PDCP CONTROL PDU (PDCP Control PDU).

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

[0076] An example of the function of the RRC will be described. The RRC may have a broadcast function. The RRC may have a paging function from the EPC 104 and / or the 5GC 110. The RRC may have a paging function from the eNB 102 connected to the gNB 108 or the 5GC 110. The RRC may have an RRC connection management function. The RRC may have a radio bearer control function. The RRC may have a cell group control function. The RRC may have a mobility control function. The RRC may have a terminal device measurement reporting and terminal device measurement reporting control function. The RRC may have a QoS management function. The RRC may have a radio link failure detection and recovery function. The RRC may use RRC messages to perform notification, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal device measurement reporting and terminal device measurement reporting control, QoS management, radio link failure detection and recovery, and the like. Note that the RRC messages and parameters used in E-UTRA RRC may be different from the RRC messages and parameters used in NR RRC.

[0077] RRC messages may be sent using the logical channel BCCH or the logical channel PCCH. The RRC message may be sent using the logical channel CCCH, or may be sent using the logical channel DCCH. In addition, the RRC message sent using the DCCH may be referred to as Dedicated RRC signaling, or RRC signaling.

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

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

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

[0081] RRC signaling sent in the uplink (UL) direction using the DCCH includes, for example, measurement reports. The RRC signaling may include a Measurement Report, an RRC Connection Reconfiguration Complete, an RRC Connection Setup Complete, an RRC Connection Reestablishment Complete, a Security Mode Complete, a UE Capability Information, etc. Also, for example, a Measurement Report, an RRC Reconfiguration Complete, an RRC Setup Complete, an RRC Reestablishment Complete, an RRC Resume Complete, a Security Mode Complete, a UE Capability Information, etc. may also be included. Also, other RRC signaling may be included.

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

[0083] An example of the function of the NAS will be described. The NAS may have an authentication function. The NAS may also have the functionality to perform security control. You may have it.

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

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

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

[0087] The definition of dormancy may be different between the UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110. In addition, all or part of the procedure for UE 122 to return from dormancy may be different between when UE 122 is connected to the EPC (when UE 122 is dormant in the RRC_IDLE state) and when UE 122 is connected to the 5GC (when UE 122 is dormant in the RRC_INACTIVE state).

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

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

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

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

[0092] When a group of serving cells configured for a terminal device is composed of an SpCell and one or more SCells, it may be considered that carrier aggregation (CA) is configured for the terminal device. Also, for a terminal device in which CA is configured, a cell providing additional radio resources to the SpCell may refer to an SCell.

[0093] A group of serving cells configured by RRC, among which the uplink is configured The same timing reference cell and the same time for the cell being A group of serving cells using the Timing Advance value may be called a Timing Advance Group (TAG). A TAG including the above may refer to a Primary Timing Advance Group (PTAG). A TAG other than the above PTAG may refer to a Secondary Timing Advance Group (STAG). One or more of the TAGs may be configured for each cell group described later.

[0094] A cell group configured by a base station device for a terminal device will now be described. A cell group may be composed of one SpCell. Also, a cell group may be composed of one SpCell and one or more SCells. In other words, a cell group is composed of one SpCell and A cell group may optionally be composed of one or more SCells, and may be expressed as a set of cell(s).

[0095] Dual Connectivity (DC) is a technology for data communication using the wireless resources of cell groups that are respectively configured by a first base station device (first node) and a second base station device (second node). When DC or MR-DC is performed, the base station device A cell group may be added. To perform DC, a first base station device may add a second base station device. The first base station device may be called a Master Node (MN). The cell group that the master node configures may be called the Master Cell Group (MCG). The second base station device is called the Secondary Node (SN). A cell group configured by a secondary node may be called a secondary cell group (SCG). The master node and the secondary node may be configured in the same base station device.

[0096] In addition, when DC is not configured, the cell group configured in the terminal device may be called MCG. In addition, when DC is not configured, the SpCell configured in the terminal device may be PCell. In addition, NR in which DC is not configured may be called NR standalone.

[0097] In addition, Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC is a technology that performs DC using NR for MCG and E-UTRA for SCG. MR-DC is a technique for performing DC using NR in both MCG and SCG. MR-DC may be a technology included in DC. An example of MR-DC using E-UTRA for MCG and NR for SCG is EN-DC (E-UTRA-NR Dual Connectivity) using EPC for the core network. An example of MR-DC using NR for MCG and E-UTRA for SCG is NE-DC (NR-E-UTRA Dual Connectivity) using 5GC for the core network. An example of MR-DC using NR for both MCG and SCG is NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.

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

[0099] The radio bearer will now be explained. When a terminal device communicates with a base station device, a radio bearer (RB) is established between the terminal device and the base station device to establish a wireless connection. A radio bearer used for CP may be called a signaling radio bearer (SRB). A radio bearer used for UP may be called a data radio bearer (DRB). A radio bearer identity (ID) may be assigned to each radio bearer. A radio bearer identity for an SRB may be called an SRB identity (SRB ID). A radio bearer identity for a DRB may be called a DRB identity (DRB ID). SRB0 to SRB2 may be defined for the SRB of E-UTRA, or other SRBs may be defined. SRB0 to SRB3 may be defined for the SRB of NR, or other SRBs may be defined. SRB0 may be an SRB for an RRC message that is transmitted and / or received using the CCCH of the logical channel. SRB1 may be an SRB for RRC signaling and for NAS signaling before the establishment of SRB2. The RRC signaling transmitted and / or received using SRB1 may include piggybacked NAS signaling. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB1. SRB2 may be an SRB for NAS signaling and for RRC signaling including logged measurement information. The logical channel DCCH may be used for all RRC signaling and NAS signaling transmitted and / or received using SRB2. SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and / or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. All RRC and NAS signaling transmitted and / or received using SRB3 may use the logical channel DCCH. Other SRBs may also be provided for other uses. The DRB may be the radio bearer for user data.The logical channel DTCH may be used for RRC signaling that is transmitted and / or received using the DRB.

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

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

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

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

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

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

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

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

[0108] In FIG. 4, the base station device creates an RRC message (step S400). The base station device may create an RRC message in order to deliver system information (SI) or a paging message. The base station device creates the message by sending RRC signaling to a specific terminal device to perform the process. The RRC message may be generated in order to receive the RRC signal from the terminal device. The processing to be performed on a specific terminal device may include, for example, security-related settings, reconfiguration of the RRC connection, handover to a different RAT, suspension of the RRC connection, release of the RRC connection, and other processing. The reconfiguration processing of the RRC connection may include, for example, control of the radio bearer (establishment, modification, release, etc.), control of the cell group (establishment, addition, modification, release, etc.), measurement setting, handover, security key update, and other processing. The creation of the RRC message in the base station device may be performed in order to respond to the RRC signaling transmitted from the terminal device. The response to the RRC signaling transmitted from the terminal device may include, for example, a response to an RRC setup request, a response to an RRC reconnection request, a response to an RRC resume request, and other responses. The RRC message includes information (parameters) for various information notifications and settings. These parameters may be called fields and / or information elements, and may be described using a description method called ASN.1 (Abstract Syntax Notation One).

[0109] In FIG. 4, the base station device then transmits the created RRC signaling to the terminal device (step (Step S402). Next, the terminal device performs processing such as setting according to the received RRC signaling if necessary (Step S404). After performing the processing, the terminal device may transmit RRC signaling for response to the base station device (not shown).

[0110] RRC signaling may be used for other purposes, not limited to the above examples.

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

[0112] In addition, the RRC signal for E-UTRA transmitted from the eNB 102 to the UE 122 may be transmitted in any case, regardless of whether the MR-DC is used or not. The RRC signaling for NR may be included in the gNB 108 RRC signaling transmitted to the UE 122, and the RRC signaling for NR may be included in the RRC signaling for E-UTRA transmitted from the gNB 108 to the UE 122.

[0113] An example of parameters included in a message regarding re-establishment of an RRC connection is described below. FIG. 7 shows the RRC connection re-establishment message in NR in FIG. FIG. 8 is an example of an ASN.1 description showing a field and / or information element related to cell group configuration in FIG. 4. FIG. 8 shows a message related to re-establishment of an RRC connection in E-UTRA in FIG. 7 and 8, and other examples of ASN.1 descriptions showing fields and / or information elements related to cell group configuration included in the message. indicates that other information is omitted, not a part of the ASN.1 notation. Note that even if there is no description of <omitted> or <omitted>, the information element may be omitted. Note that the example of ASN.1 in this embodiment does not correctly follow the ASN.1 notation method. In this embodiment, the example of ASN.1 is an example of an RRC signaling parameter in this embodiment, and other names and other notations may be used. In addition, in order to avoid the explanation becoming complicated, the example of ASN.1 shows only an example of main information closely related to this embodiment. Note that the parameters described in ASN.1 may not be distinguished as fields, information elements, etc., and may all be referred to as information elements. In this embodiment, the fields, information elements, etc. described in ASN.1 included in the RRC signaling may be referred to as information or parameters. Note that the message regarding the reconfiguration of the RRC connection may be an RRC reconfiguration message in NR, or an RRC connection reconfiguration message in E-UTRA.

[0114] In FIG. 7, the information element named CellGroupConfig may be an information element used for setting, changing, releasing, etc., of a cell group of an MCG or an SCG in the NR. The information element named CellGroupConfig may include a TCI information element, which will be described later. The information element named CellGroupConfig may be rephrased as a cell group configuration information element or cell group configuration. When the information element named CellGroupConfig is used to configure a cell group of an SCG in NR, this information element named CellGroupConfig may be rephrased as a configuration on the SCG side. An information element named SpCellConfig included in the information element named CellGroupConfig may be an information element used to configure a special cell (SpCell). The information element named SpCellConfig may be rephrased as a cell group configuration information element or cell group configuration. When the information element named CellGroupConfig is used to configure a cell group of an SCG in NR, this information element named CellGroupConfig may be rephrased as a configuration on the SCG side. The information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element set upon deactivation of the SCG, which will be described later. The information element named DeactivatedSCG-Config-r17 may be rephrased as a setting in deactivation of SCG. Note that the information element named DeactivatedSCG-Config-r17 may include a parameter for instructing a terminal device whether or not to perform BFD and / or RLM (described later) in the PSCell in the deactivated state of SCG indicated by bfd-and-RLM. The information element named TCI-Info included in the information element named SpCellConfig may be an information element indicating the TCI state. The information element named TCI-Info may be rephrased as a TCI information element. Note that the information element named TCI-Info includes a parameter of a BWP identifier (described later) indicated by BWP-Id.

[0115] Next, we will explain RLM (Radio Link Monitoring).

[0116] The terminal device receives a certain type of BS in a serving cell (PCell and / or PSCell, etc.). Radio link monitoring is performed using a reference signal (such as a cell-specific reference signal (CRS)). In addition, the terminal device may detect radio interference in a serving cell (PCell and / or PSCell, etc.). The base station receives a setting (radio link monitoring setting: RadioLinkMonitoringConfig) indicating which reference signal to use for radio link monitoring, and selects one or more of the set reference signals. The terminal device may perform radio link monitoring using a number of reference signals (referred to as RLM-RS in this specification). The terminal device may also perform radio link monitoring using other signals. When the conditions for being in synchronization are met, the in-synchronization may be notified to a higher layer.

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

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

[0119] Also, cell deactivation may not be applied to the PCell, but may be applied to the PSCell. In this case, the cell inactivation may be a different process for SpCells and SCells.

[0120] Cell activation and deactivation are handled by the MAC entity that exists for each cell group. The SCell configured in the terminal device may be activated by some or all of the following (A) to (C). and / or may be inactivated. (A) Reception of MAC CE to activate / deactivate SCell (B) A SCell inactivity timer set for each SCell for which a PUCCH is not configured. (C) RRC parameters (sCellState) set for each SCell set in the terminal device

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

[0122] (Processing AD) If the RRC parameter (sCellState) set for the SCell during SCell configuration is set to activated, or if a MAC CE for activating the SCell is received, the MAC end of the UE 122 The entity performs the process (AD-1). Otherwise, if the MAC CE that deactivates the SCell is received, If an uplink grant or downlink assignment is notified by the PDCCH of an active SCell, or if an inactivity timer of an active SCell expires, the MAC entity of the UE 122 performs a process (AD-2). By this, an uplink grant or a downlink allocation for an active SCell is communicated. When a MAC PDU is transmitted in a configured uplink grant, or Alternatively, when a MAC PDU is received in the configured downlink allocation, the MAC end of the UE 122 The entity restarts the SCell inactivity timer associated with that SCell. When the ell becomes inactive, the MAC entity of the UE 122 performs a process (AD-3).

[0123] (Process AD-1) If, in NR, the SCell was in an inactive state before receiving a MAC CE to activate the SCell, or the RRC parameter (sCellState) configured for the SCell during SCell configuration is set to activated, the MAC entity of UE 122 performs process (AD-1A) or process (AD-1B). The MAC entity of the UE 122 also starts or restarts (if already started) the SCell inactivity timer associated with that SCell. If the Active DL BWP is not a Dormant BWP (described later), the MAC entry of the UE 122 The Company will implement some or all of the following (A) to (B): (A) All suspended configured uplinks of grant type 1 associated with this SCell are cleared according to the stored configuration, if any. (Re)initialize link grants. (B) Trigger the PHR. If a MAC CE that activates an SCell is received, the MAC CE activates the SCell by RRC signaling. The first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is the configured If the BWP to be activated is not set to Dormant BWP, the MAC entity of the UE 122 performs process (AD-1A). If the MAC CE to activate the SCell is received and the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set for that SCell by RRC signaling is set to Dormant BWP, the MAC entity of the UE 122 performs process (AD-1B). In addition, the MAC entity of the UE 122 performs some or all of the following (A) to (B). (A) Activate the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in RRC signaling. (B) Activate the BWP indicated by the first active uplink BWP identifier (firstActiveUplinkBWP-Id) configured in the RRC signaling.

[0124] (Process AD-1A) The MAC entity of the UE 122 activates the SCell and performs some or all of the following steps (A) to (E): Carry out. (A) Transmit a sounding reference signal (SRS) on this SCell. (B) Report the CSI for this SCell. (C) Monitor the PDCCH of this SCell. (D) Monitor the PDCCH for this SCell (if scheduling for this SCell is performed in another serving cell). (E) If PUCCH is configured, transmit PUCCH on this SCell.

[0125] (Process AD-1B) The MAC entity of the UE 122 checks whether the BWP inactivity timer of this serving cell is running. The mule will stop.

[0126] (Process AD-2) The MAC entity of UE 122 performs some or all of the following (A) through (F). (A) This SCell is deactivated. (B) Stop the SCell inactivity timer associated with this SCell. (C) Deactivate all Active BWPs associated with this SCell. (D) Clear all configured downlink assignments and / or all configured uplink grants of grant type 2 associated with this SCell. (E) Configure all grant type 1 associated with this SCell. Suspend uplink grants. (F) Flush the HARQ buffer associated with this SCell.

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

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

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

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

[0131] Here, a parameter (timeAlignmentTimer) set by the RRC to maintain time alignment in the uplink (UL) will be described.

[0132] The timeAlignmentTimer may be set for each TAG. The timeAlignmentTimer may control the period for which the MAC entity considers serving cells belonging to a given TAG to be synchronized to UL time. The timeAlignmentTimer is also referred to as TAT.

[0133] When the timeAlignmentTimer associated with a PTAG expires, the MAC entity performs some or all of the following: (PT) (A) Flush the HARQ buffers for all serving cells that belong to the PTAG. . (B) Inform the RRC to release the PUCCH for all serving cells that belong to the PTAG, if any. (C) Inform the RRC to release the SRS for all serving cells that belong to the PTAG, if any. (D) Clear all configured downlink assignments and / or all configured uplink grants. (E) Consider all running timeAlignmentTimers to have expired.

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

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

[0136] Inactivation of SCG may mean inactivating SCG. is a MAC entity associated with an SCG and corresponding to the MAC entity Inactivation of an SCG may mean deactivating a cell group. Inactivation of an SCG may mean deactivating a PSCell (SpCell of an SCG) or deactivating a PSCell. Activation of an SCG may mean activating an SCG. Activation of an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity. Activation of an SCG may mean activating a PSCell (SpCell of an SCG) or activating a PSCell.

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

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

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

[0140] In LTE and / or NR, the active state of an SCG may be a state in which a terminal device performs some or all of the following (A) to (O) in a PSCell (SpCell) of the SCG. Also, the active state of an SCG may mean a state in which the SCG is activated (a state in which the SCG is not dormant). (SA-1) (A) Transmit SRS using this PSCell. (B) Measure the CSI for this PSCell. (C) Report the CSI for this PSCell. (D) Transmit PUCCH using this PSCell. (E) Transmit UL-SCH in this PSCell. (F) Transmit RACH on this PSCell. (G) Monitor the PDCCH of this PSCell. (H) Monitor the PDCCH for this PSCell. (I) Activate the inactive BWP in this PSCell. (J) This PSCell performs discontinuous reception (DRX). (K) Monitor the PDCCH of this PSCell and / or the PDCCH for this PSCell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicating an uplink grant for UL-SCH transmission in this PSCell. (L) BWP is activated in this PSCell, and uplink grant is received in the above BWP. The PDCCH of this PSCell addressed to the C-RNTI, MCS-C-RNTI, and / or CS-RNTI indicated , and / or monitor the PDCCH for this PSCell. (M) This PSCell includes automatic gain control (AGC) and beam failure recovery. Beam Failure Detection (BFD) and / or Radio Link Monitoring Radio Link Monitoring (RLM) is also performed. (N) Response to this PSCell according to the stored configuration, if any. Some or all of the suspended configurations of grant type 1 that are attached (Re)initialize the uplink grant for the ARD. (O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) that contains this PSCell. do.

[0141] In LTE and / or NR, a terminal device may determine that an SCG is in an inactive state based on some or all of the following (A) to (H). In addition, the following signaling (A) to (F) and The control element may be notified from the base station device to the terminal device via the SCG. Alternatively, the signaling and control elements (A) to (F) below may be transmitted to cells other than the SCG. The base station device may notify the terminal device via a group (MCG, SCG other than the relevant SCG, etc.) . (SD-2) (A) Reception of RRC signaling instructing the SCG to inactivate. (B) Reception of MAC CE instructing SCG to inactivate (C) Receipt of RRC signaling instructing the PSCell to be deactivated. (D) Receipt of a MAC CE instructing the PSCell to be deactivated (E) Reception of other RRC signaling (F) Reception of other MAC CEs (G) SCG inactivity timer expires (H) Expiration of PSCell inactivity timer

[0142] The RRC signaling in (A), (C), and (E) in (SD-2) above is, for example, a parameter called scg-State. If scg-State is included in the RRC signaling, it indicates the inactivation of the SCG. However, when scg-State is not included in the RRC signaling, it indicates the activation of the SCG. Also, scg-State may be included in an RRC reconfiguration message or an RRC resume message. The signaling may be generated in the MN.

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

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

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

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

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

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

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

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

[0151] If the terminal determines that the SCG is active based on (SA-2) above, the terminal When the RRC entity determines that the following (A) or (B) is satisfied, The SCG may instruct a corresponding SCG-related entity (such as a PSCell entity) to initiate a random access procedure in the PSCell of the SCG.

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

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

[0154] (A-2-1) A radio link failure is detected in the SCG. (A-2-2) The PSCell is set to perform RLM when the SCG is inactive, and A special indication (indication#A) is notified from the lower layer (MAC entity, etc.) . (A-2-3) A special notification (indication#B) is notified from a lower layer (such as a MAC entity). (A-2-4) The PSCell is not set to perform RLM when the SCG is in an inactive state.

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

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

[0157] (B) NR-DC is configured in the terminal device, an RRC reconfiguration message is received via SRB1 of the SCG, and an NR RRC signaling including an RRC reconfiguration message for the SCG side configuration in the form of a container is received. According to the FDA guidelines, SCG is not inactivated and satisfies either (B-1) or (B-2) below. .

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

[0159] Whether or not the PSCell is set to perform RLM in the inactive state of the SCG may be set by a parameter called bfd-and-RLM in Fig. 7. In other words, the above-mentioned "the PSCell is set to perform RLM in the inactive state of the SCG" may mean that the parameter indicates that the PSCell performs RLM in the inactive state of the SCG, or that the parameter is included in the configuration on the SCG side. Also, the above-mentioned "the PSCell is not set to perform RLM in the inactive state of the SCG" may mean that the parameter indicates that the PSCell does not perform RLM in the inactive state of the SCG, or that the parameter is not included in the configuration on the SCG side.

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

[0161] The above operation enables an efficient state change in the process of deactivating an SCG without the need for the transmitter 504 of the UE 122 to independently transmit a MAC CE for changing the state of the cell of the SCG to an inactive state. In addition, when the deactivation of an SCG is performed based on RRC signaling, the initial state is conventionally set in the RRC layer and the state is changed in the MAC layer, but the above operation makes it possible to efficiently change the state of the SCG while avoiding a mismatch between the instructions of the RRC layer and the instructions of the MAC layer.

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

[0163] Fig. 5 is a block diagram showing the configuration of a terminal device (UE 122) in this embodiment. In order to avoid a complicated explanation, Fig. 5 shows only main components closely related to this embodiment. Show only.

[0164] The UE 122 shown in FIG. 5 includes a receiver 500 that receives control information (DCI, RRC signaling, etc.) from a base station device, a processor 502 that performs processing according to parameters included in the received control information, and a transmitter 504 that transmits the control information (UCI, RRC signaling, etc.) to the base station device. The above-mentioned base station device may be eNB 102 or gNB 108. Furthermore, processing unit 502 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, processing unit 502 may include some or all of a physical layer processing unit, a MAC layer processing unit, an RLC layer processing unit, a PDCP layer processing unit, an SDAP processing unit, an RRC layer processing unit, and a NAS layer processing unit.

[0165] FIG. 6 is a block diagram showing the configuration of a base station device in this embodiment. In order to avoid clutter, FIG. 6 shows only the main components closely related to this embodiment. The above-mentioned base station device may be the eNB 102 or the gNB 108.

[0166] The base station apparatus shown in FIG. 6 includes a transmitter 600 that transmits control information (DCI, RRC signaling, etc.) to the UE 122, a processor 602 that creates control information (DCI, RRC signaling including parameters, etc.) and transmits it to the UE 122 to cause the processor 502 of the UE 122 to process it, and a receiver 604 that receives the control information (UCI, RRC signaling, etc.) from the UE 122. The processor 602 may include some or all of the functions of various layers (e.g., physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processor 602 may include some or all of the functions of the physical layer processor, MAC layer processor, RLC layer processor, PDCP layer processor, SDAP processor, RRC layer processor, and NAS layer processor. may be all inclusive.

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

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

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

[0170] The active state may be a state in which the SCG is activated. The above-mentioned active state may be a state in which the SCG resumes from a dormant state. The above-mentioned active state may be a state in which the SCG is activated. The active state may be a state in which the MAC PDU including the MAC SDU is not in a dormant state. The active state may be a state in which the MAC PDU is transitioned from the inactive state when a random access procedure is initiated due to a scheduling request triggered to transmit the MAC PDU including the MAC SDU. The active state may be a state in which the MAC PDU is transitioned from the inactive state when a return from the dormant state is instructed by the RRC entity.

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

[0172] When the UE 122 receives the information to activate the SCG, the UE 122 transitions the SCG from an inactive state to an active state. In other words, SCG may be activated. UE122 may also activate SCG from a dormant state. When it receives information instructing it to resume from the inactive state, it transitions the SCG from the inactive state to the active state. In addition, when the UE 122 receives information instructing the PSCell to return from the dormant state, When the UE 122 receives other information, the UE 122 may transition the SCG from the inactive state to the active state. When the UE 122 receives other information, the UE 122 may transition the SCG from the inactive state to the active state. The SCG may transition from an inactive state to an active state based on a sleep timer. In addition, the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the dormancy of the PSCell. In addition, the UE 122 may transition the SCG from the inactive state to the active state based on a timer related to the dormancy of the PSCell. The UE 122 may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request received from the UE 122. The UE 122 may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request (in other words, initiated by the MAC entity itself). The MAC entity of the UE 122 may obtain an instruction to activate the SCG, an instruction to resume from a dormant SCG, an instruction to resume from a dormant state of the PSCell, and / or other information from the RRC entity of the UE 122. After the MAC entity obtains the information from the RRC entity, the UE 122 may determine that the SCG is in an active state as shown in (SA-2) above and transition the SCG from the inactive state to the active state. The UE 122 may perform the process shown in (SA-3) above when transitioning the SCG from the inactive state to the active state.

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

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

[0175] An example of the operation of the UE 122 in the inactive state described above will be described. In the inactive state, the UE 122 performs the above-mentioned in each of the PSCell and / or one or more SCells of a certain cell group. A part or all of the processing as shown in (SD-1) of the above may be carried out.

[0176] The inactive state may be a state in which SCG is inactivated. The inactive state may be entering a dormant SCG. The inactive state may be the dormant state of the SCG. The inactive 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. The inactive state may be a state to which the active state transitions when an entry into the dormant state is instructed from the RRC entity.

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

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

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

[0180] 12 is a diagram showing an example of processing of a terminal device in this embodiment. The MAC entity 302 of the UE 122 judges whether to notify the RRC entity 308 of the UE 122 (step S1200), and notifies the RRC entity 308 based on the judgment (step S1202). The MAC entity 302 and the RRC entity 308 may be the MAC entity 202 and the RRC entity 208, respectively.

[0181] An example of the determination in step S1200 will be described. The MAC entity 302 of the UE 122 notifies the RRC entity 308 of the UE 122 of the expiration of the TAT associated with the TAG including the PSCell. In addition or instead, the MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 of the UE 122 based on whether the SCG is in an inactive state. In addition or instead, the MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 of the UE 122 based on a notification from the RRC entity 308 of the UE 122 that RLM is configured to be performed in the PSCell in the inactive state of the SCG. In addition or instead, the MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 based on a beam failure being detected in the PSCell. In addition or instead, the MAC entity 302 of the UE 122 may determine whether to notify the RRC entity 308 based on a configuration to perform BFD in the PSCell. Note that the TAG including a PSCell may be a PTAG. When the TAT associated with the TAG including the PSCell expires, the processing unit 502 of the UE 122 may perform some or all of the processing as shown in (PT) above. Also, the processing of the MAC entity 302 and the processing of the RRC entity 308 may be performed in the processing unit 502 of the UE 122.

[0182] An example of the notification in step S1202 will be described. The MAC entity 302 of the UE 122 may notify the RRC entity 308 of the indication#A based on the determination to notify the RRC entity 308 of the UE 122 in step S1200. In addition to or instead of that, the MAC entity 302 of the UE 122 may notify the RRC entity 308 of the indication#A in step S1200. In addition, the MAC entity 302 of the UE 122 may notify the RRC entity 308 of the indication #B based on the determination that the RRC entity 308 of the UE 122 is not to be notified in step S1200. Note that the processing of the MAC entity 302 and the processing of the RRC entity 308 may be performed in a processing unit 502 of the UE 122.

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

[0184] 13 is a diagram showing an example of a process of a terminal device in this embodiment. The RRC entity 308 of the UE 122 judges whether to instruct the MAC entity 302 of the UE 122 to start a random access procedure (step S1300), and instructs the MAC entity 302 to start a random access procedure based on the judgment (step S1302). The MAC entity 302 and the RRC entity 308 may be the MAC entity 202 and the RRC entity 208, respectively.

[0185] An example of the judgment in step S1300 will be described. The RRC entity 308 of the UE 122 When transitioning from an inactive state to an active state, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 to start a random access procedure based on the indication#A being notified from the MAC entity 302 of the UE 122 during the inactive state. In addition or instead, when transitioning an SCG from an inactive state to an active state, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 to start a random access procedure based on the indication#B being notified from the MAC entity 302 of the UE 122 during the inactive state. In addition or instead, when transitioning an SCG from an inactive state to an active state, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 to start a random access procedure based on the indication#B being notified from the MAC entity 302 of the UE 122 during the inactive state not being canceled. Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to initiate a random access procedure based on the fact that the SpCell configuration of the SCG includes a synchronized reconfiguration. Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to initiate a random access procedure based on the fact that a radio link failure is detected in the SCG. Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to initiate a random access procedure based on the fact that the PSCell of the SCG is not configured to perform RLM in the inactive state of the SCG.Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to start a random access procedure based on receiving a message regarding reconfiguration of the RRC connection including RadioLinkMonitoringConfig in an inactive state of the SCG. Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to start a random access procedure based on a reference signal (BFD RS) used for BFD being changed in an inactive state of the SCG. Additionally or alternatively, the RRC entity 308 of the UE 122 may determine whether to instruct the MAC entity 302 of the UE 122 to start a random access procedure based on a beam failure detected in a PSCell of the SCG being recovered. Note that the processing of the MAC entity 302 and the processing of the RRC entity 308 may be executed in the processing unit 502 of the UE 122.

[0186] An example of the notification in step S1302 will be described. The RRC entity 308 of the UE 122 may instruct the MAC entity 302 of the UE 122 to start a random access procedure based on the determination in step S1300 that the MAC entity 302 of the UE 122 should be instructed to start a random access procedure. In addition, the RRC entity 308 of the UE 122 may not instruct the MAC entity 302 of the UE 122 to start a random access procedure based on the determination in step S1300 that the MAC entity 302 of the UE 122 should be instructed to start a random access procedure. Based on the determination, the MAC entity 302 may not be instructed to initiate a random access procedure. The processing of Tee 308 may be performed in a processing unit 502 of the UE 122.

[0187] An example of processing by the base station device and the terminal device in this embodiment will be described with reference to FIG.

[0188] 14 is a diagram showing an example of processing by the base station device and the terminal device in this embodiment. At time T1400, the gNB 108 transmits signaling (RRC signaling, MAC CE, etc.) to the RRC entity 308 of the UE 122 and / or the MAC entity 302 of the UE 122 to instruct them to deactivate the SCG (step S1400), and after receiving the signaling in step S1400, the RRC entity 308 and / or the MAC entity 302 determine that the SCG is in an inactive state based on the above (SD-2) (not shown). Furthermore, after a certain time has elapsed from time T1400, at time T1404, gNB108 transmits signaling (RRC signaling, MAC CE, etc.) to the RRC entity 308 of UE122 and / or the MAC entity 302 of UE122 instructing them to activate the SCG (step S1404), and after receiving the signaling in step S1404, the RRC entity 308 and / or the MAC entity 302 determine that the SCG is in an active state based on the above (SA-2) (not shown). Between time T1400 and time T1404, the MAC entity 302 of the UE 122 determines whether to notify the RRC entity 308 of the UE 122 (not shown), and based on the determination to notify the RRC entity 308, notifies the RRC entity 308 at time T1402 between time T1400 and time T1404 (step S1402). Furthermore, after the notification from the MAC entity 302 of the UE 122, the RRC entity 308 of the UE 122 determines whether to instruct the MAC entity 302 to start a random access procedure in a PSCell of the SCG (not shown), and based on the determination to instruct the MAC entity 302 to start a random access procedure in the PSCell, instructs the MAC entity 302 at time T1406 after time T1404 (step S1406).In addition, the gNB 108, the MAC entity 302, and the RRC entity 308 may be the eNB 102, the MAC entity 202, and the RRC entity 208, respectively.

[0189] In step S1400, the RRC entity 308 of the UE 122 determines that the SCG is inactive. If the SCG is deactivated, the MAC entity 302 of the UE 122 is notified of the deactivation of the SCG based on the determination. The MAC entity 302 notifies the RRC entity 122 of the deactivation of the SCG. Based on the signaling received from the MAC entity 308, the MAC entity 302 may determine that the SCG is in an inactive state. If it determines that the SCG is in an inactive state, then based on that determination, it may send (notify) signaling indicating that the SCG is in an inactive state to the RRC entity 308, and the RRC entity 308 may determine that the SCG is in an inactive state based on the signaling received (notified) from the MAC entity 302.

[0190] In step S1404, the RRC entity 308 of the UE 122 determines that the SCG is active. If so, based on the determination, the MAC entity 302 of the UE 122 transmits (notifies) a signaling indicating that the SCG is in an active state, and the MAC entity 302 notifies the RRC entity 302 of the UE 122 of the SCG being in an active state. On the other hand, in step S1404, if the MAC entity 302 determines that the SCG is in an active state, the MAC entity 302 may transmit (notify) signaling indicating that the SCG is in an active state to the RRC entity 308 based on the determination, and the RRC entity 308 may notify the RRC entity 308 of the SCG being in an active state. may determine that the SCG is in an active state based on the signaling received (notified) from the MAC entity 302 .

[0191] The process of the MAC entity 302 of the UE 122 in step S1402 may follow the process described in Fig. 12. Also, the process of the RRC entity 308 of the UE 122 in step S1406 may follow the process described in Fig. 13.

[0192] Time T1400 may be a time when the RRC entity 308 of the UE 122 and / or the MAC entity 302 of the UE 122 receive signaling instructing to deactivate the SCG. Additionally or alternatively, time T1400 may be a time when the RRC entity 308 of the UE 122 and / or the MAC entity 302 of the UE 122 determine that the SCG is in an inactive state based on (SD-2) above. Note that the time when the signaling instructing to deactivate the SCG is received and the time when the SCG is determined to be in an inactive state may be different from each other.

[0193] The time T1402 may be the time when the TAT associated with the TAG that includes the PSCell expires. Additionally or alternatively, the time T1402 may include a period during which the MAC entity 302 of the UE 122 is configured to perform RLM in the PSCell in an inactive state of the SCG from the RRC entity 308 of the UE 122. Additionally or alternatively, time T1402 may be the time when a beam failure is detected in the PSCell. Additionally or alternatively, the time T1402 may be the same as the time T1400. Note that, when the TAT expires, the RLM is set to be performed in the PSCell in the inactive state of the SCG. The time at which signaling indicating that a beam failure has been detected in the PSCell is notified and the time at which a beam failure is detected in the PSCell may be different from each other.

[0194] The time T1404 may be a time when the RRC entity 308 of the UE 122 and / or the MAC entity 302 of the UE 122 receive signaling instructing the SCG to be activated. Additionally or alternatively, the time T1404 may be a time when the RRC entity 308 of the UE 122 and / or the MAC entity 302 of the UE 122 determine that the SCG is in an active state based on (SA-2) above. Note that the time when the signaling instructing the SCG to be activated is received and the time when the SCG is determined to be in an active state may be different from each other.

[0195] Time T1406 may be the time when a radio link failure is detected in the SCG. Additionally or alternatively, time T1406 may be the same as time T1404.

[0196] The SCG may be in an inactive state between time T1400 and time T1404. The SCG may be in an active state before time T1400 and after time T1404. stomach.

[0197] Between time T1402 and time T1406, the RRC entity 308 of the UE 122 may hold the notification from the MAC entity 302 of the UE 122 without canceling it. Also, between time T1402 and time T1404, that is, after the notification from the MAC entity 302 of the UE 122, the RRC entity 308 of the UE 122 may cancel the notification from the MAC entity 302 based on the determination that the MAC entity 302 is not to be instructed to start a random access procedure in the PSCell of the SCG in the inactive state of the SCG. For example, before transitioning the SCG from the inactive state to the active state, the RRC entity 308 of the UE 122 may cancel the indication#B notified from the MAC entity 302 based on the determination that the MAC entity 302 of the UE 122 is not to be instructed to start a random access procedure in the PSCell of the SCG.

[0198] Thus, in this embodiment, when the MAC entity of the UE determines that the TAT associated with the TAG including the PSCell has expired and the SCG is in an inactive state, the MAC entity of the UE activates the SCG. Indicate to the RRC entity that a random access procedure is required when This allows the RRC entity to instruct the MAC entity to initiate the random access procedure only when necessary, thereby eliminating the need for signaling when activating the SCG. This can be done efficiently.

[0199] In the above description, the MAC entity of the UE determines some or all of the following (A) to (C): Based on the determination, the RRC entity may notify the RRC entity of indication #A. (A) Expiration of the TAT associated with a TAG (PTAG) that contains a PSCell in an SCG (B) SCG is inactive (C) Notification from the RRC entity that the PSCell of the SCG is not configured to perform RLM in the inactive state of the SCG

[0200] In addition to or instead of the above description, the MAC entity of the UE may include: Based on the determination, the RRC entity may be notified to. (A) SCG is inactive. (B) Detection of beam failure (BF) in a PSCell (C) The PSCell of the SCG is configured to perform BFD.

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

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

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

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

[0205] Furthermore, unless otherwise specified, the radio bearer in the above description may be a DRB, an SRB, or a combination of a DRB and an SRB.

[0206] In addition, in the above description, expressions such as "to be notified" and "to be pointed out" may be interchangeable.

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

[0208] In addition, in the above description, expressions such as "includes," "included," and "was included" may be used interchangeably.

[0209] In the above description, "the above-mentioned" may be replaced with "the above-mentioned."

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

[0211] In the above explanation, "confirmed to be...", "set to...", "includes..." Expressions such as the above may be interchangeable.

[0212] In the above description, the "dormant state" may be rephrased as the "inactive state," and the "state restored from the dormant state" may be rephrased as the "active state." Also, in the above description, "activated" and "inactivated" may be rephrased as the "active state" and "inactive state," respectively.

[0213] In the above description, "transition from X to Y" may be rephrased as "X becomes Y." Also, in the above description, "cause a transition" may be rephrased as "determine a transition."

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

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

[0216] In the above explanation, if condition "A" and condition "B" are contradictory conditions, condition "B" may be expressed as the "other" condition of condition "A."

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

[0218] It should be noted that a part of the device in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the control function. The "computer system" here refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. The "computer-readable recording medium" may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, and the like.

[0219] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that stores a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such a case. The above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0220] Also, each functional block or feature of the device used in the above-described embodiment may be implemented or executed by an electric circuit, i.e., typically an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described herein may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable logic circuit (PLC), or a combination of such circuits. The general purpose processor may include a general purpose gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor, or each of the aforementioned circuits, may be composed of digital circuits or analog circuits. Also, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, an integrated circuit based on that technology may be used.

[0221] It should be noted that the present embodiment is not limited to the above-mentioned embodiment. In the embodiment, an example of the device is described, but the present embodiment is not limited to this, and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV devices, kitchen devices, cleaning / washing devices, air conditioners, office devices, vending machines, and other household appliances.

[0222] Although this embodiment has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes within the scope of the gist of this embodiment are also included. In addition, this embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this embodiment. In addition, configurations in which elements described in the above embodiment are replaced with elements that have the same effect are also included. [Explanation of symbols]

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

Claims

1. A terminal device that communicates with a base station device, A processing unit that communicates using the MCG and the SCG; A receiving unit that receives signaling from the base station device; Equipped with The MCG includes at least a PCell, The SCG includes at least a PSCell, The processing unit performs processing in a MAC entity and processing in an RRC entity; The MAC entity: The TAT associated with the TAG that includes the PSCell has expired, and determining whether the SCG is in an inactive state; The TAT associated with the TAG that includes the PSCell has expired, and Based on the determination that the SCG is in an inactive state, notifying the RRC entity of a notification indicating that a random access procedure is required when activating the SCG; The RRC entity: When transitioning the SCG from an inactive state to an active state, determining whether the notification has been notified from the MAC entity during the inactive state; When transitioning the SCG from an inactive state to an active state, based on determining that the notification has been notified from the MAC entity during the inactive state, instructing the MAC entity to initiate a random access procedure; Terminal device.

2. A method for a terminal device communicating with a base station device, comprising: Communicate using MCG and SCG, The MCG includes at least a PCell, The SCG includes at least a PSCell, The MAC entity of the terminal device: The TAT associated with the TAG that includes the PSCell has expired, and determining whether the SCG is in an inactive state; The TAT associated with the TAG that includes the PSCell has expired, and Based on the determination that the SCG is in an inactive state, notifying an RRC entity of the terminal device of a notification indicating that a random access procedure is required when activating the SCG; The RRC entity of the terminal device When transitioning the SCG from an inactive state to an active state, determining whether the notification has been notified from the MAC entity during the inactive state; When transitioning the SCG from an inactive state to an active state, based on determining that the notification has been notified from the MAC entity during the inactive state, instructing a MAC entity of the terminal device to initiate a random access procedure; method.

3. An integrated circuit implemented in a terminal device that communicates with a base station device, Communicate using MCG and SCG, The MCG includes at least a PCell, The SCG includes at least a PSCell, The integrated circuit comprises: a MAC entity of the terminal device, The TAT associated with the TAG that includes the PSCell has expired, and determining whether the SCG is in an inactive state; The TAT associated with the TAG that includes the PSCell has expired, and Based on the determination that the SCG is in an inactive state, notifying an RRC entity of the terminal device of a notification indicating that a random access procedure is required when activating the SCG; An RRC entity of the terminal device, When transitioning the SCG from an inactive state to an active state, determining whether the notification has been notified from the MAC entity during the inactive state; When transitioning the SCG from an inactive state to an active state, based on determining that the notification has been notified from the MAC entity during the inactive state, A function of instructing a MAC entity of the terminal device to initiate a random access procedure. causing the terminal device to exhibit a function; Integrated circuits.

Images