WO2023132370A1 - Terminal device, method, and integrated circuit - Google Patents

Abstract

This terminal device is configured to: receive an RRC reconfiguration message; and, when the RRC reconfiguration message is received via an SRB3 and is not included in a message for master cell group (MCG) link recovery and when a secondary cell group (SCG) is inactive, transmit an RRC reconfiguration complete message to a secondary node via an SRB1.

Description

TERMINAL DEVICE, METHOD AND INTEGRATED CIRCUIT

The present invention relates to terminal devices, methods and integrated circuits.
This application claims priority to Japanese Patent Application No. 2022-1447 filed in Japan on January 7, 2022, the content of which is incorporated herein.

In the 3rd Generation Partnership Project (3GPP), which is a standardization project for cellular mobile communication systems, technical studies and standardization of cellular mobile communication systems, including radio access, core networks, services, etc., are being conducted. there is

For example, E-UTRA (Evolved Universal Terrestrial Radio Access) is a radio access technology (RAT) for 3.9th and 4th generation cellular mobile communication systems under 3GPP. rice field. At present, 3GPP is still conducting technical studies and establishing standards for extension technologies for E-UTRA. E-UTRA is also called Long Term Evolution (LTE: registered trademark), and extended technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro).

In addition, NR (New Radio or NR Radio access) is under technical review and standardization as Radio Access Technology (RAT) for 5th Generation (5G) cellular mobile communication systems at 3GPP. started. At present, 3GPP is still conducting technical studies and establishing standards for NR extension technology.

In order to enable large-capacity data communication as an NR extension technology, there is a dual connectivity (also called multi-connectivity) technology in which one or more base station devices and terminal devices communicate using multiple cell groups. . In this dual connectivity, in order to perform communication in each cell group, a terminal device needs to monitor whether there is a message addressed to itself in each cell group. In order to enable the terminal device to perform low-delay communication when a large volume of data communication occurs, the terminal device must always monitor a plurality of cell groups, and there has been a problem of consuming a lot of power. Therefore, studies have been started on techniques for performing or stopping monitoring of some cell groups at a low frequency (cell group deactivation technique).

　Non-Patent Document 7 is a draft revision of the specification regarding cell group activation. However, the decision considering the conditional reconfiguration is not reflected when applying the RRC reconfiguration message, and the terminal device cannot perform an efficient cell change.

One aspect of the present invention has been made in view of the circumstances described above, and one of the objects thereof is to provide a terminal device, a communication method, and an integrated circuit capable of efficiently performing communication control.

In order to achieve the above object, one aspect of the present invention takes the following measures. That is, one aspect of the present invention is a terminal device, a receiving unit that receives an RRC reset message and/or RRC signaling that includes the RRC reset message, and a processing unit that performs settings based on the RRC reset message and the processing unit determines that the RRC reconfiguration message was received via SRB3 (signaling radio bearer 3) and was included in a message for master cell group (MCG) link recovery. If not, and the secondary cell group (SCG) is inactive, send an RRC reconfiguration complete message to the secondary node via SRB1.

Further, one aspect of the present invention is a method applied to a terminal device, comprising: receiving an RRC reconfiguration message and/or RRC signaling including the RRC reconfiguration message; wherein the RRC reconfiguration message was received via SRB3 (signaling radio bearer 3) and was not included in a message for master cell group (MCG) link recovery; If the secondary cell group (SCG) is inactive, send an RRC reconfiguration complete message to the secondary node via SRB1.

Further, one aspect of the present invention is an integrated circuit implemented in a terminal device, a function of receiving an RRC reset message and / or RRC signaling containing the RRC reset message, and based on the RRC reset message The RRC reconfiguration message is received via SRB3 (signaling radio bearer 3) and included in a message for master cell group (MCG) link recovery. and the secondary cell group (SCG) is inactive, send an RRC reconfiguration complete message to the secondary node via SRB1.

In addition, these generic or specific aspects may be realized by systems, devices, methods, integrated circuits, computer programs, or recording media. may be realized by any combination of

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

1 is a schematic diagram of a communication system according to the embodiment; FIG. FIG. 2 is a diagram of an example of the E-UTRA protocol configuration according to the present embodiment; FIG. 2 is a diagram of an example of the NR protocol configuration according to this embodiment; The figure which shows an example of the flow of the procedure for various settings in RRC which concerns on this embodiment. FIG. 2 is a block diagram showing the configuration of a terminal device according to the embodiment; FIG. 2 is a block diagram showing the configuration of a base station apparatus according to this embodiment; 1 is an example of ASN.1 description included in a message regarding reconfiguration of RRC connection in NR in this embodiment. 1 is an example of ASN.1 description included in a message regarding reconfiguration of RRC connection in E-UTRA in this embodiment. An example of processing related to inactivation of SCG in this embodiment. An example of processing related to conditional resetting in the embodiment. An example of processing related to RRC resetting in the present embodiment.

The present embodiment will be described in detail below with reference to the drawings.

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

In this embodiment, the name of each node and entity, the processing in each node and entity, etc. when the radio access technology is E-UTRA or NR will be described, but this embodiment is applicable to other radio access technologies. may be used. The name of each node or entity in this embodiment may be another name.

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 part of the functions closely related to the present embodiment, and may have other functions.

　E-UTRA100 may be a radio access technology. E-UTRA 100 may also be the air interface between UE 122 and eNB 102 . The air interface between UE 122 and eNB 102 may be called the Uu interface. The eNB (E-UTRAN Node B) 102 may be a base station device of the E-UTRA 100. The eNB 102 may have the E-UTRA protocol described below. The E-UTRA protocol may consist of an E-UTRA user plane (User Plane: UP) protocol described later and an E-UTRA control plane (Control Plane: CP) protocol described later. eNB 102 may terminate E-UTRA User Plane (UP) and E-UTRA Control Plane (CP) protocols to UE 122 . A radio access network composed of eNBs may be called E-UTRAN.

The EPC (Evolved Packet Core) 104 may be a core network. Interface 112 is the interface between eNB 102 and EPC 104 and may be referred to as the S1 interface. 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 interface 112 may terminate at a Mobility Management Entity (MME; not shown) within EPC 104 . The user plane interface of interface 112 may terminate at a serving gateway (S-GW; not shown) within EPC 104 . The control plane interface of interface 112 may be called the S1-MME interface. The user plane interface of interface 112 may be called the S1-U interface.

Note that one or more eNBs 102 may be connected to the EPC 104 via the interface 112. Interfaces may exist between multiple eNBs 102 that connect to the EPC 104 (not shown). An interface between multiple eNBs 102 connected to an EPC 104 may be called an X2 interface.

NR106 may be a radio access technology. NR 106 may also be the air interface between UE 122 and gNB 108 . The air interface between UE 122 and gNB 108 may be called the Uu interface. A gNB (g Node B) 108 may be a base station device of NR 106 . gNB 108 may have the NR protocol described below. The NR protocol may consist of an NR User Plane (UP) protocol, which will be described later, and an NR Control Plane (CP) protocol, which will be described later. gNB 108 may terminate NR User Plane (UP) and NR Control Plane (CP) protocols to UE 122 .

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

Note that one or more gNBs 108 may be connected to the 5GC 110 via the interface 116. There may be interfaces between gNBs 108 that connect to the 5GC 110 (not shown). An interface between multiple gNBs 108 connected to a 5GC 110 may be called an Xn interface.

The eNB102 may have the function of connecting to the 5GC110. The eNB 102 with the function of connecting to the 5GC 110 may be called ng-eNB. Interface 114 is the interface between eNB 102 and 5GC 110 and may be called the NG interface. Interface 114 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 interface 114 may terminate at the AMF in 5GC 110 . The user plane interface of interface 114 may terminate at UPF in 5GC 110 . The control plane interface of interface 114 may be referred to as the NG-C interface. The user plane interface of interface 114 may be called the NG-U interface. A radio access network composed of ng-eNBs or gNBs may be referred to as NG-RAN. NG-RAN, E-UTRAN, etc. may simply be referred to as networks. Also, the network may include eNBs, ng-eNBs, gNBs, and the like.

Note that one or more eNBs 102 may be connected to the 5GC 110 via the interface 114. There may be interfaces between multiple eNBs 102 that connect to the 5GC 110 (not shown). An interface between multiple eNBs 102 connected to a 5GC 110 may be called an Xn interface. Also, eNB 102 connected to 5GC 110 and gNB 108 connected to 5GC 110 may be connected via interface 120 . The interface 120 between the eNB 102 connected to the 5GC 110 and the gNB 108 connected to the 5GC 110 may be referred to as the Xn interface.

gNB108 may have the ability to connect to EPC104. A gNB 108 with the ability to connect to an EPC 104 may be called an en-gNB. Interface 118 is the interface between gNB 108 and EPC 104 and may be referred to as the S1 interface. Interface 118 may include a user plane interface through which user data passes. The user plane interface of interface 118 may terminate at an S-GW (not shown) within EPC 104 . The user plane interface of interface 118 may be called the S1-U interface. Also, the eNB 102 connected to the EPC 104 and the gNB 108 connected to the EPC 104 may be connected via an interface 120 . The interface 120 between the eNB 102 that connects to the EPC 104 and the gNB 108 that connects to the EPC 104 may be referred to as the X2 interface.

The interface 124 is the interface between the EPC 104 and the 5GC 110, and may be an interface through CP only, UP only, or both CP and UP. Also, some or all of interfaces 114, 116, 118, 120, 124, etc. may not be present depending on the communication system provided by the carrier.

　UE 122 may be a terminal device capable of receiving system information and paging messages transmitted from eNB 102 and/or gNB 108. Also, UE 122 may be a terminal device capable of wireless connection with eNB 102 and/or gNB 108 . Also, the UE 122 may be a terminal device capable of establishing a wireless connection with the eNB 102 and a wireless connection with the gNB 108 at the same time. UE 122 may have an E-UTRA protocol and/or an NR protocol. Note that the wireless connection may be a Radio Resource Control (RRC) connection.

Also, the UE 122 may be a terminal device capable of connecting with the EPC 104 and/or the 5GC 110 via the eNB 102 and/or gNB 108. When the connection destination core network of eNB102 and/or gNB108 with which UE122 communicates is EPC104, each data radio bearer (DRB: Data Radio Bearer ) may be uniquely associated with each EPS (Evolved Packet System) bearer passing through the EPC 104. Each EPS bearer may be identified by an EPS bearer identifier (Identity, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet (registered trademark) frames passing through the same EPS bearer.

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

　The EPC 104 may not have PDU sessions and/or QoS flows. Also, 5GC110 does not need to have an EPS bearer. When UE 122 is connected with EPC 104, UE 122 has information of EPS bearers, but may not have information within PDU sessions and/or QoS flows. Also, when the UE 122 is connected to the 5GC 110, the UE 122 may have information in PDU sessions and/or QoS flows, but not EPS bearer information.

In the following description, eNB 102 and/or gNB 108 are also simply referred to as base station apparatuses, and UE 122 is simply referred to as terminal apparatus or UE.

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

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

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

　Figure 2(B) is a diagram of the 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 (radio resource control layer), may be a protocol between UE 122 and eNB 102. That is, RRC 208 may be a protocol that terminates at 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 (non-AS layer), may be a protocol between UE 122 and MME. That is, the NAS 210 may be a protocol that terminates at the MME on the network side.

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

The AS (Access Stratum) layer may be a layer that terminates between UE 122 and eNB 102 and/or gNB 108. That is, the AS layer is a layer including part or all of PHY200, MAC202, RLC204, PDCP206 and RRC208 and/or a layer including part or all of PHY300, MAC302, RLC304, PDCP306, SDAP310 and RRC308. you can

In this embodiment, the E-UTRA protocol and the NR protocol are not distinguished, and PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer) , the term 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) are the PHY (PHY layer) of the E-UTRA protocol. ), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer), NR protocol, PHY (PHY layer), MAC (MAC layer), RLC (RLC layer), PDCP (PDCP layer), RRC (RRC layer), NAS (NAS layer). Also, the SDAP (SDAP layer) may be the SDAP (SDAP layer) of the NR protocol.

Further, in the present embodiment, when distinguishing between the E-UTRA protocol and the NR protocol, PHY 200, MAC 202, RLC 204, PDCP 206, and RRC 208 are respectively defined as E-UTRA PHY or LTE PHY, E-UTRA MAC or They are also called MAC for LTE, RLC for E-UTRA or RLC for LTE, PDCP for E-UTRA or PDCP for LTE, and RRC for E-UTRA or RRC for LTE. PHY200, MAC202, RLC204, PDCP206 and RRC208 respectively 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 It may also be described as RRC or LTE RRC. When distinguishing between E-UTRA protocol and NR protocol, PHY 300, MAC 302, RLC 304, PDCP 306, and RRC 308 are called PHY for NR, MAC for NR, RLC for NR, RLC for NR, and RRC for NR, respectively. There is also a thing. PHY 200, MAC 302, RLC 304, PDCP 306, and RRC 308 may also be described as NR PHY, NR MAC, NR RLC, NR PDCP, NR RRC, etc., respectively.

Explain the entities in the AS layer of E-UTRA and/or NR. An entity that has some or all of the functionality of the MAC layer may be called a MAC entity. An entity that has some or all of the functionality of the RLC layer may be called an RLC entity. An entity that has some or all of the functions of the PDCP layer may be called a PDCP entity. An entity that has some or all of the functionality of the SDAP layer may be called an SDAP entity. An entity that has some or all of the functionality of the RRC layer may be called an RRC entity. The MAC entity, RLC entity, PDCP entity, SDAP entity, and RRC entity may be replaced with MAC, RLC, PDCP, SDAP, and RRC, respectively.

The data provided from MAC, RLC, PDCP, SDAP to the lower layer and/or the data provided from the lower layer to MAC, RLC, PDCP, SDAP shall be MAC PDU (Protocol Data Unit), RLC respectively. You may call them PDUs, PDCP PDUs, and SDAP PDUs. In addition, MAC SDU (Service Data Unit) and RLC SDU for data provided from upper layers to MAC, RLC, PDCP, and SDAP and/or data provided from MAC, RLC, PDCP, and SDAP to upper layers, respectively , PDCP SDU, and SDAP SDU. A segmented RLC SDU may also be called an RLC SDU segment.

Here, the base station device and the terminal device exchange (transmit and receive) signals in a higher layer. For example, the base station apparatus and the terminal apparatus may transmit and receive RRC messages (also referred to as RRC message, RRC information, and RRC signaling) in the radio resource control (RRC) layer. Also, the base station apparatus and the terminal apparatus may transmit and receive MAC control elements in the MAC (Medium Access Control) layer. Also, the RRC layer of the terminal device acquires system information broadcast from the base station device. Here, RRC messages, system information and/or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each parameter 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 upper layer means the upper layer seen from the PHY layer, so it means one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non Access Stratum) layer, etc. good too. For example, higher layers in MAC layer processing may mean one or more of the RRC layer, the RLC layer, the PDCP layer, the NAS layer, and the like. Hereinafter, the meanings of "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" refer to the upper layers of the terminal device (mainly the RRC layer and the MAC layer). etc.) may mean that A is received from the base station apparatus, and the received A is provided (provided) from the upper layer of the terminal apparatus to the physical layer of the terminal apparatus. For example, "provided with upper layer parameters" in the terminal device means 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 transmitted from the upper layer of the terminal device to the terminal device 1. It may mean provided to the physical layer. Setting higher layer parameters in a terminal device may mean giving (providing) higher layer parameters to the terminal device. For example, setting upper layer parameters in a terminal device may mean that the terminal device receives an upper layer signal from the base station apparatus and sets the received upper layer parameters in the upper layer. However, the setting of the upper layer parameters in the terminal device may include the setting of default parameters previously given to the upper layer of the terminal device. When describing transmission of an RRC message from a terminal device to a base station device, the expression "submitting a message from the RRC entity of the terminal device to the lower layer" may be used. . In the terminal device, "submitting a message to the lower layer" from the RRC entity may mean submitting the message to the PDCP layer. In the terminal device, "submitting a message from the RRC layer to the lower layer" means that the RRC message is sent using SRB (SRB0, SRB1, SRB2, SRB3, etc.), so each SRB It may mean submitting to the corresponding PDCP entity. When a terminal's RRC entity receives an indication from a lower layer, that lower layer may mean one or more of the PHY layer, MAC layer, RLC layer, PDCP layer, and so on.

I will explain an example of PHY functions. The PHY of the terminal device may have a function of receiving data transmitted from the PHY of the base station device via a downlink (DL) physical channel. The PHY of the terminal device may have a function of transmitting data to the PHY of the base station device via an uplink (UL) physical channel. A PHY may be connected to a higher-level MAC via a Transport Channel. The PHY may pass data to the MAC over transport channels. The PHY may also be provided with data from the MAC over the transport channel. In the PHY, RNTI (Radio Network Temporary Identifier) may be used to identify various control information.

Here, the physical channel will be explained. Physical channels used for wireless communication between the terminal apparatus and the base station apparatus may include the following physical channels.

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)

The PBCH may be used to broadcast system information required by terminal equipment.

Also, in NR, the PBCH may be used to report the time index (SSB-Index) within the period of the synchronization signal block (SSB).

The PDCCH may be used to transmit (or carry) downlink control information (DCI) in downlink radio communication (radio communication from the base station device to the terminal device). Here, one or more DCIs (which may also be referred to as DCI formats) may be defined for transmission of downlink control information. That is, a field for downlink control information may be defined as DCI and mapped to information bits. A PDCCH may be sent in a PDCCH candidate. A terminal may monitor a set of PDCCH candidates in a serving cell. Monitoring a set of PDCCH candidates may mean attempting to decode the PDCCH according to a certain DCI format. Also, the terminal device may use CORESET (Control Resource Set) to monitor the set of PDCCH candidates. The DCI format may be used for PUSCH scheduling in the serving cell. PUSCH may be used for transmission of user data, transmission of RRC messages to be described later, and the like.

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

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

PUSCH may be used to transmit HARQ-ACK and/or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. PUSCH may also be used to transmit CSI only, or HARQ-ACK and CSI only. That is, PUSCH may be used to transmit UCI only. PDSCH or PUSCH may also be used to transmit RRC signaling (also referred to as RRC messages) and MAC CE. Here, in the PDSCH, RRC signaling transmitted from the base station apparatus may be signaling common to multiple terminal apparatuses within the cell. Also, the RRC signaling transmitted from the base station apparatus may be signaling dedicated to a certain terminal apparatus (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted using signaling dedicated to a certain terminal device. PUSCH may also be used to transmit UE Capability in the uplink.

The PRACH may be used to transmit random access preambles. PRACH is used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustments) for uplink transmissions, and requests for UL-SCH resources. may

I will explain an example of MAC functions. A MAC may be referred to as a MAC sublayer. A MAC may have the capability to map various logical channels (Logical Channels) to corresponding transport channels. A logical channel may be identified by a logical channel identifier (Logical Channel Identity or Logical Channel ID). A MAC may be connected to an upper RLC via a logical channel (logical channel). Logical channels may be divided into control channels for transmitting control information and traffic channels for transmitting user information according to the type of information to be transmitted. Logical channels may also be divided into uplink logical channels and downlink logical channels. The MAC may have the ability to multiplex MAC SDUs belonging to one or more different logical channels and provide them to the PHY. The MAC may also have the function of demultiplexing the MAC PDUs provided by the PHY and providing them to upper layers via the logical channel to which each MAC SDU belongs. Also, the MAC may have a function of performing error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a Scheduling Report (SR) function for reporting scheduling information. The MAC may have a function of performing priority processing between terminal devices using dynamic scheduling. Also, the MAC may have a function of performing priority processing between logical channels within one terminal device. The MAC may have a function of prioritizing overlapping resources within one terminal device. The E-UTRA MAC may have the capability to identify MultimediaBroadcast Multicast Services (MBMS). The NR MAC may also have a function of identifying Multicast/Broadcast Service (MBS). A MAC may have the ability to select a transport format. MAC has a function of performing discontinuous reception (DRX) and / or discontinuous transmission (DTX: discontinuous transmission), a function of executing random access (RA) procedure, notifying information of transmittable power, power It may have a headroom report (Power Headroom Report: PHR) function, a buffer status report (BSR) function that notifies the amount of data in the transmission buffer, and so on. NR MAC may have a Bandwidth Adaptation (BA) function. Also, the MAC PDU format used in E-UTRA MAC and the MAC PDU format used in NR MAC may be different. The MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for performing control in MAC.

Explains the uplink (UL: Uplink) and/or downlink (DL: Downlink) logical channels used in E-UTRA and/or NR.

　BCCH (Broadcast Control Channel) may be a downlink logical channel for broadcasting control information such as system information (SI: System Information).

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

A CCCH (Common Control Channel) may be a logical channel for transmitting control information between a terminal device and a base station device. CCCH may be used when the terminal does not have an RRC connection. CCCH may also be used between the base station apparatus and a plurality of terminal apparatuses.

DCCH (Dedicated Control Channel) is a logical channel for transmitting dedicated control information in a one-to-one (point-to-point) bi-directional manner between a terminal device and a base station device. It's okay. Dedicated control information may be control information dedicated to each terminal device. DCCH may be used when a terminal device has an RRC connection.

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

　Explains the uplink mapping of logical channels and transport channels in E-UTRA and/or NR.

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

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

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

　Explains the mapping of downlink logical channels and transport channels in E-UTRA and/or NR.

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

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

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

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

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

Explain an example of RLC functions. RLC may be referred to as an RLC sublayer. The E-UTRA RLC may have the function of segmenting and/or concatenating data provided from the PDCP of the upper layer and providing it to the lower layer. E-UTRA RLC may have the function of reassembling and re-ordering data provided from lower layers and providing it to upper layers. The NR RLC may have a function of adding a sequence number independent of the sequence number added by PDCP to the data provided by PDCP of the upper layer. Also, the NR RLC may have a function of segmenting data provided from PDCP and providing it to lower layers. Also, the NR RLC may have a function of reassembling data provided from lower layers and providing it to upper layers. The RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ). Also, the RLC may have a function of error correction by ARQ. The control information sent from the RLC receiver to the sender for ARQ indicating the data that needs to be retransmitted may be referred to as a status report. Also, a status report transmission instruction sent from the RLC transmitting side to the receiving side can be called a poll. The RLC may also have the capability to detect data duplication. RLC may also have a function of discarding data. RLC may have three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The TM does not divide the data received from the upper layer, and does not need to add an RLC header. A TM RLC entity is a uni-directional entity and may be configured as a transmitting TM RLC entity or as a receiving TM RLC entity. The UM divides and/or combines the data received from the upper layer, adds an RLC header, etc., but does not need to perform data retransmission control. A 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 as a receiving UMRLC entity. If the UM RLC entity is a bidirectional entity, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side. The AM may divide and/or combine data received from an upper layer, add an RLC header, control data retransmission, and the like. 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. Data provided to lower layers by TM and/or data provided from lower layers may be referred to as TMD PDUs. Data provided by UM to lower layers and/or data provided by lower layers may also be referred to as UMD PDUs. Data provided to the lower layer by AM or data provided from the 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 differ. RLC PDUs may also include RLC PDUs for data and RLC PDUs for control. An RLC PDU for data may be called an RLC DATA PDU (RLC Data PDU). Also, the control RLC PDU may be called an RLC CONTROL PDU.

An example of PDCP functions will be explained. PDCP may be referred to as a PDCP sublayer. PDCP may have a function to maintain sequence numbers. PDCP may also have a header compression/decompression function for efficiently transmitting user data such as IP packets and Ethernet frames over a wireless section. A protocol used for IP packet header compression/decompression may be called ROHC (Robust Header Compression) protocol. Also, the protocol used for Ethernet frame header compression/decompression may be called EHC (Ethernet (registered trademark) Header Compression) protocol. PDCP may also have a data encryption/decryption function. PDCP may also have the functions of integrity protection and integrity verification of data. PDCP may also have a re-ordering function. PDCP may also have a retransmission function for 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 of discarding duplicated received data. The PDCP entity is a bi-directional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. Also, the PDCP PDU format used in E-UTRA PDCP and the PDCP PDU format used in NR PDCP may be different. PDCP PDUs may include data PDCP PDUs and control PDCP PDUs. A PDCP PDU for data may be called a PDCP DATA PDU (PDCP Data PDU). Also, the PDCP PDU for control may be called a PDCP CONTROL PDU (PDCP Control PDU).

An example of SDAP functions will be explained. SDAP is the Service Data Adaptation Protocol Layer (Service Data Adaptation Protocol Layer). SDAP is a mapping between a downlink QoS flow and a data radio bearer (DRB) sent from the 5GC 110 to the terminal device via the base station device, and/or from the terminal device via the base station device. It may have the ability to map uplink QoS flows sent to the 5GC 110 to the DRB. SDAP may also have the function of storing mapping rule information. SDAP may also have a function to mark QoS flow identifiers (QoS Flow ID: QFI). SDAP PDUs may include data SDAP PDUs and control SDAP PDUs. A data SDAP PDU may be called an SDAP DATA PDU. A control SDAP PDU may also be called an SDAP CONTROL PDU. Note that one SDAP entity of the terminal device may exist for each PDU session.

I will explain an example of RRC functions. RRC may have a broadcast function. RRC may have a paging function from EPC 104 and/or 5GC 110 . RRC may have paging capabilities from eNB 102 connecting to gNB 108 or 5GC 110 . RRC may also have an RRC connection management function. RRC may also have a radio bearer control function. RRC may also have a cell group control function. RRC may also have a mobility control function. RRC may also have terminal measurement reporting and terminal measurement reporting control functions. RRC may also have QoS management functions. RRC may also have radio link failure detection and recovery functionality. RRC uses RRC messages for broadcasting, paging, RRC connection management, radio bearer control, cell group control, mobility control, terminal equipment measurement reporting and terminal equipment measurement reporting control, QoS management, radio link failure detection and recovery, etc. may be performed. Note that the RRC messages and parameters used in E-UTRA RRC may differ from the RRC messages and parameters used in NR RRC.

The RRC message may be sent using the logical channel's BCCH, may be sent using the logical channel's PCCH, may be sent using the logical channel's CCCH, or may be sent using the logical channel's DCCH. may be sent. Also, the RRC message sent using the DCCH may be referred to as dedicated RRC signaling or RRC signaling.

The RRC message sent using BCCH may include, for example, a master information block (Master Information Block: MIB), each type of system information block (System Information Block: SIB) may be included, and others of RRC messages may be included. RRC messages sent using the PCCH may include, for example, paging messages and other RRC messages.

RRC messages sent in the uplink (UL) direction using CCCH include, for example, RRC Setup Request, RRC Resume Request, RRC Reestablishment Request, An RRC system information request message (RRC System Info Request) may be included. Also, for example, RRC Connection Request, RRC Connection Resume Request, RRC Connection Reestablishment Request, etc. may be included. Other RRC messages may also be included.

RRC messages sent in the downlink (DL) direction using CCCH include, for example, RRC Connection Reject message, RRC Connection Setup message, RRC Connection Reestablishment message, An RRC connection re-establishment rejection message (RRC Connection Reestablishment Reject) may be included. Also, for example, an RRC rejection message (RRC Reject), an RRC setup message (RRC Setup), etc. may be included. Other RRC messages may also be included.

RRC signaling sent in the uplink (UL) direction using the DCCH includes, for example, a Measurement Report message, an RRC Connection Reconfiguration Complete message, an RRC Connection Setup Complete message. ), RRC Connection Reestablishment Complete message, Security Mode Complete message, UE Capability Information message, and the like. Also for example Measurement Report message, RRC Reconfiguration Complete message, RRC Setup Complete message, RRC Reestablishment Complete message, RRC Resume Complete message ), a security mode complete message (Security Mode Complete), a UE capability information message (UE Capability Information), and the like. Also other RRC signaling may be included.

RRC signaling sent in the downlink (DL) direction using DCCH includes, for example, an RRC Connection Reconfiguration message, an RRC Connection Release message, a Security Mode Command message, A UE Capability Inquiry message and the like may be included. Also for example RRC Reconfiguration message, RRC Resume message, RRC Release message (RRC Release message), RRC Reestablishment message (RRC Reestablishment message), Security Mode Command message (Security Mode Command), UE Capability Inquiry message (UE Capability Enquiry), etc. may be included. Also other RRC signaling may be included.

An example of NAS functions will be explained. A NAS may have an authentication function. Also, the NAS may have a function of performing mobility management. The NAS may also have a security control function.

　The above PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS functions are examples, and some or all of the functions may not be implemented. Also, part or all of the functions of each layer (each layer) may be included in another layer (layer).

Next, state transitions of UE 122 in LTE and NR will be explained. For UE 122 connecting to EPC or 5GC, when RRC connection has been established, UE 122 may be in RRC_CONNECTED state. A state in which an RRC connection is established may include a state in which the UE 122 holds some or all of the UE contexts described below. Also, states in which an RRC connection is established may include states in which UE 122 is able to transmit and/or receive unicast data. UE 122 may also be in RRC_INACTIVE state when the RRC connection is suspended. Also, UE 122 may be in RRC_INACTIVE state when UE 122 is connected to 5GC and the RRC connection is dormant. A UE 122 may be in the RRC_IDLE state when the UE 122 is neither in the RRC_CONNECTED state nor in the RRC_INACTIVE state.

Note that if UE 122 is connected to EPC, it does not have the RRC_INACTIVE state, but E-UTRAN may initiate dormancy of the RRC connection. If the UE 122 is connected to EPC, when the RRC connection is suspended, the UE 122 may retain the AS context of the UE and an identifier (resumeIdentity) used for resume and transition to the RRC_IDLE state. A layer higher than the RRC layer of UE 122 (for example, NAS layer) confirms that UE 122 holds the AS context of the UE, and that the E-UTRAN permits recovery of the RRC connection, and that UE 122 exits the RRC_IDLE state. When it needs to transition to the RRC_CONNECTED state, it may initiate the resumption of a dormant RRC connection.

The UE 122 connected to the EPC 104 and the UE 122 connected to the 5GC 110 may have different definitions of dormancy. Also, when UE122 is connected to EPC (when UE122 is dormant in RRC_IDLE state) and when UE122 is connected to 5GC (when UE122 is dormant in RRC_INACTIVE state), UE122 all or part of the procedure for waking up from sleep may be different.

The RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be called connected mode, inactive mode, and idle mode, respectively, and RRC connected mode. , RRC inactive mode, and RRC idle mode.

The UE AS context held by UE 122 includes the current RRC settings, current security context, PDCP state including ROHC (RObust Header Compression) state, C-RNTI (Cell Radio Network Temporary Identifier), cell identifier (cellIdentity), and physical cell identifier of the connection source PCell, all or part of which may be information. Note that the UE AS context held by either or all of the eNB 102 and gNB 108 may contain the same information as the UE AS context held by the UE 122, or the information contained in the UE AS context held by the UE 122. may contain different information.

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

Next, the serving cell will be explained. In a terminal device in an RRC connected state in which CA and/or DC, which will be described later, is not configured, a serving cell may consist of one primary cell (PCell). Also, in a terminal device in an RRC connected state in which CA and / or DC described later are set, a plurality of serving cells include one or more special cells (Special Cell: SpCell) and one or more all secondary It may mean a set of cells (set of cell(s)) composed of cells (Secondary Cell: SCell). A SpCell may support PUCCH transmission and contention-based random access (CBRA). A PCell may be a cell used for an RRC connection establishment procedure when a terminal device in the RRC idle state transitions to the RRC connected state. Also, the PCell may be a cell used for the RRC connection re-establishment procedure in which the terminal device re-establishes the RRC connection. Also, the PCell may be a cell used for a random access procedure during handover. A PSCell may be a cell used in a random access procedure when adding a secondary node, which will be described later. PCell and PSCell may be SpCells. Also, the SpCell may be a cell that is used for purposes other than those described above.

The fact that a group of serving cells configured for a terminal device is composed of SpCells and one or more SCells may be regarded as carrier aggregation (CA) configured for the terminal device. . Also, a cell that provides an additional radio resource to a SpCell for a terminal device in which CA is configured may mean an SCell.

A group of serving cells configured by RRC that uses the same timing reference cell and the same timing advance value for cells in which uplink is configured. You can call it Timing Advance Group (TAG). Also, the TAG containing the SpCell of the MAC entity may mean the Primary Timing Advance Group (PTAG). Also, TAGs other than the PTAG may mean Secondary Timing Advance Group (STAG). One or more TAGs may be configured for each cell group, which will be described later.

A cell group that is set by the base station device for the terminal device will be explained. A cell group may consist of one SpCell. Also, a cell group may consist of one SpCell and one or more SCells. That is, a cell group may consist of one SpCell and optionally one or more SCells. A cell group may also be expressed as a set of cell(s).

Dual Connectivity (DC) performs data communication using the radio resources of cell groups each configured by a first base station device (first node) and a second base station device (second node). It can be technology. When DC or MR-DC, which will be described later, is performed, a cell group may be added from the base station apparatus to the terminal apparatus. A first base station apparatus may add a second base station apparatus to perform DC. The first base station device may be called a master node (Master Node: MN). Also, a cell group configured by a master node may be called a master cell group (MCG). The second base station device may be called a secondary node (SN). Also, a cell group configured by secondary nodes may be called a secondary cell group (SCG). Note that the master node and the secondary node may be configured within the same base station apparatus.

Also, when DC is not set, the cell group set in the terminal device may be called MCG. Also, when DC is not configured, SpCell configured in the terminal device may be PCell.

　Multi-Radio Dual Connectivity (MR-DC) may be a technology that performs DC using E-UTRA for MCG and NR for SCG. Also, MR-DC may be a technique of performing DC using NR for MCG and E-UTRA for SCG. Also, MR-DC may be a technique of performing DC using NR on both MCG and SCG. MR-DC may be a technology involved in DC. Examples of MR-DC using E-UTRA for MCG and NR for SCG include EN-DC (E-UTRA-NR Dual Connectivity) using EPC in the core network and NGEN-DC using 5GC in the core network. There may be DC (NG-RAN E-UTRA-NR Dual Connectivity). An example of MR-DC using NR for MCG and E-UTRA for SCG may be 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 may be NR-DC (NR-NR Dual Connectivity) using 5GC for the core network.

Note that 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 MCG and one MAC entity for SCG. The MAC entity for the MCG in the terminal may always be established in the terminal in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). Also, 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. Also, the MAC entity for each cell group of the terminal device may be set by the terminal device receiving RRC signaling from the base station apparatus. SpCell may mean PCell if the MAC entity is associated with the MCG. Also, when a MAC entity is associated with an SCG, SpCell may mean a Primary SCG Cell (PSCell). SpCell may also mean PCell if the MAC entity is not associated with a cell group. PCell, PSCell and SCell are serving cells. In EN-DC and NGEN-DC, the MAC entity for MCG may be the E-UTRA MAC entity and the MAC entity for SCG may be the NR MAC entity. Also, in NE-DC, the MAC entity for MCG may be the NR MAC entity, and the MAC entity for SCG may be the E-UTRA MAC entity. Also, in NR-DC, both MAC entities for MCG and SCG may be NR MAC entities. Note that one MAC entity for each cell group can be rephrased as one MAC entity for each SpCell. Also, one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

I will explain the radio bearer. When a terminal device communicates with a base station device, a radio connection may be established by establishing a radio bearer (RB) between the terminal device and the base station device. A radio bearer used for the CP may be called a signaling radio bearer (SRB). A radio bearer used for UP may be called a data radio bearer (DRB). Each radio bearer may be assigned a radio bearer identity (ID). The SRB radio bearer identifier may be called an SRB identity (SRB ID). A DRB radio bearer identifier may be called a DRB identity (DRB ID). SRB0 to SRB2 may be defined as SRBs of E-UTRA, and SRBs other than these may be defined. SRB0 to SRB3 may be defined as SRBs of NR, and SRBs other than these may be defined. SRB0 may be the SRB for RRC messages transmitted and/or received using the CCCH of the logical channel. SRB1 may be the SRB for RRC signaling and for NAS signaling before the establishment of SRB2. RRC signaling transmitted and/or received using SRB1 may include piggybacked NAS signaling. The logical channel DCCH may be used for all RRC 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. All RRC signaling and NAS signaling transmitted and/or received using SRB2 may use the DCCH of the logical channel. Also, SRB2 may have a lower priority than SRB1. SRB3 may be an SRB for transmitting and/or receiving specific RRC signaling when EN-DC, NGEN-DC, NR-DC, etc. are configured in the terminal device. All RRC and NAS signaling transmitted and/or received using SRB3 may use the DCCH of the logical channel. Other SRBs may also be provided for other uses. A DRB may be a radio bearer for user data. Logical channel DTCH may be used for RRC signaling transmitted and/or received using DRB.

　The radio bearer in the terminal device will be explained. Radio bearers may include RLC bearers. An RLC bearer may consist of one or two RLC entities and logical channels. The RLC entity when there are two RLC entities in the RLC bearer may be 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. An SRB0 RLC bearer may consist of a TM RLC entity and a logical channel. SRB0 may always be established in the terminal device in all states (RRC idle state, RRC connected state, RRC inactive state, etc.). One 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. SRB1 may consist of one PDCP entity and one or more RLC bearers. The SRB1 RLC bearer may consist of an AM RLC entity and a logical channel. One SRB2 may be established and/or configured in the terminal device by RRC signaling received by the terminal device in the RRC connected state with AS security activated from the base station device. SRB2 may consist of one PDCP entity and one or more RLC bearers. An SRB2 RLC bearer may consist of an AM RLC entity and a logical channel. Note that PDCPs on the base station device side of SRB1 and SRB2 may be placed in the master node. SRB3 is when a secondary node in EN-DC, NGEN-DC, or NR-DC is added, or when the secondary node is changed, the terminal device in the RRC connection state with AS security activated becomes the base station. One may be established and/or configured in the terminal by RRC signaling received from the device. SRB3 may be a direct SRB between the terminal device and the secondary node. SRB3 may consist of one PDCP entity and one or more RLC bearers. An SRB3 RLC bearer may consist of an AM RLC entity and a logical channel. The PDCP on the base station device side of SRB3 may be placed in the secondary node. One or more DRBs may be established and/or configured in the terminal device by RRC signaling received from the base station device by the terminal device in the RRC connected state with AS security activated. A DRB may consist of one PDCP entity and one or more RLC bearers. A DRB RLC bearer may consist of an AM or UM RLC entity and a logical channel.

In addition, in MR-DC, the radio bearer in which PDCP is placed in the master node can be called the MN terminated (terminated) bearer. Also, in MR-DC, a radio bearer in which PDCP is placed in a secondary node may be called an SN terminated (terminated) bearer. In MR-DC, a radio bearer in which the RLC bearer exists only in the MCG may be called an MCG bearer. Also, in MR-DC, a radio bearer whose RLC bearer exists only in the SCG may be called an SCG bearer. Also, in DC, a radio bearer in which RLC bearers exist in both MCG and SCG may be called a split bearer.

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

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 E-UTRA RLC. Also, for an RLC bearer established and/or configured in a cell group configured with NR, the RLC entity established and/or configured may be NR RLC. If the terminal is configured with EN-DC, the PDCP entity established and/or configured for the MN-terminated MCG bearer may be either E-UTRA PDCP or NR PDCP. For other bearer type radio bearers, i.e. MN terminated split bearer, MN terminated SCG bearer, SN terminated MCG bearer, SN terminated split bearer and SN terminated SCG bearer, when EN-DC is configured in the terminal equipment. The PDCP established and/or configured by the NR may be the NR PDCP. Also, when NGEN-DC, NE-DC, or NR-DC is configured in the terminal device, the PDCP entity established and/or configured for radio bearers in all bearer types may be NR PDCP. .

Note that in NR, DRBs established and/or configured in terminal equipment may be associated with one PDU session. One SDAP entity may be established and/or configured for one PDU session in the terminal device. Established and/or Configured in Terminal The SDAP entity, PDCP entity, RLC entity, and logical channels may be established and/or configured by RRC signaling that the terminal receives from the base station.

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

Next, handover in LTE and NR will be explained. Handover may be the process by which a UE 122 in RRC Connected state changes its serving cell from a source SpCell to a target SpCell. Handover may occur when UE 122 receives RRC signaling from eNB 102 and/or gNB 108 indicating a handover. The RRC signaling indicating handover may be a message regarding reconfiguration of the RRC connection including parameters indicating handover (for example, an information element named MobilityControlInfo or an information element named ReconfigurationWithSync). Note that the information element named MobilityControlInfo described above may be rephrased as a mobility control setting information element, a mobility control setting, or mobility control information. Note that the above information element named ReconfigurationWithSync may be rephrased as a reset information element with synchronization or a reset with synchronization. Also, the RRC signaling indicating handover may be a message (for example, MobilityFromEUTRACommand or MobilityFromNRCommand) indicating movement to another RAT's cell. Handover can also be rephrased as reconfiguration with sync. Also, the conditions under which UE 122 can perform handover include some or all of the following: when AS security is activated, when SRB2 is established, and at least one DRB is established. good.

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

　In FIG. 4, the base station device creates an RRC message (step S400). The creation of the RRC message in the base station apparatus may be performed in order for the base station apparatus to distribute system information (SI: System Information) and paging messages. Also, the creation of the RRC message in the base station apparatus may be performed in order for the base station apparatus to transmit RRC signaling that causes a specific terminal apparatus to perform processing. The processing to be performed on a specific terminal device may include, for example, security-related settings, RRC connection reconfiguration, handover to a different RAT, RRC connection suspension, RRC connection release, and the like. RRC connection reset processing includes, for example, radio bearer control (establishment, change, release, etc.), cell group control (establishment, addition, change, release, etc.), measurement setting, handover, security key update, etc. may be included. Also, the creation of the RRC message in the base station apparatus may be performed in response to RRC signaling transmitted from the terminal apparatus. Responses to RRC signaling sent from the terminal may include, for example, responses to RRC setup requests, responses to RRC reconnection requests, responses to RRC resume requests, and the like. The RRC message contains information (parameters) for various information notifications and settings. These parameters may be called fields and/or information elements, and may be described using the description method ASN.1 (Abstract Syntax Notation One).

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

　RRC signaling is not limited to the above examples, and may be used for other purposes.

In MR-DC, RRC on the master node side is used to transfer RRC signaling for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal device. good. For example, in EN-DC or NGEN-DC, the information element (nr-SecondaryCellGroupConfig) for setting the SCG side of E-UTRA RRC signaling transmitted and received between eNB 102 and UE 122, NR RRC signaling is It may be included in the form of a container. In addition, in NE-DC, E-UTRA RRC signaling is included in the information element (MRDC-SecondaryCellGroupConfig information element) for SCG side configuration of NR RRC signaling transmitted and received between gNB 108 and UE 122 in the form of a container. may be included in RRC signaling for SCG side configuration may be sent and received between the master and secondary nodes. In addition, in NR-DC, NR RRC signaling is included in the form of a container in an information element (MRDC-SecondaryCellGroupConfig information element) for configuration on the SCG side of NR RRC signaling transmitted and received between gNB 108 and UE 122. can be RRC signaling for SCG side configuration may be sent and received between the master and secondary nodes.

Note that, not only when using MR-DC, RRC signaling for E-UTRA transmitted from eNB 102 to UE 122 may include RRC signaling for NR, or RRC signaling for NR transmitted from gNB 108 to UE 122. may include RRC signaling for E-UTRA.

An example of the parameters included in the message regarding RRC connection reconfiguration will be explained. FIG. 7 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in a message related to RRC connection reconfiguration in NR in FIG. FIG. 8 is an example of ASN.1 description representing fields and/or information elements related to cell group setting included in the message related to RRC connection reconfiguration in E-UTRA in FIG. Not limited to FIGS. 7 and 8, in the examples of ASN.1 in this embodiment, <omitted> and <omitted> are not part of the notation of ASN.1, but other information is omitted. indicates Information elements may be omitted even where there is no description of <omitted> or <omitted>. Note that the ASN.1 examples in the present embodiment do not correctly follow the ASN.1 notation method. In this embodiment, the example of ASN.1 represents an example of RRC signaling parameters in this embodiment, and other names and other representations may be used. Also, in order to avoid complicating the explanation, examples of ASN.1 show only examples of main information closely related to this embodiment. Note that all parameters described in ASN.1 may be referred to as information elements without distinguishing between fields, information elements, and the like. In addition, in the present embodiment, fields described in ASN.1, information elements, and the like included in RRC signaling may be rephrased as information or parameters. Note that the message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

The information element named CellGroupConfig in FIG. 7 may be an information element used for setting, changing, releasing, etc. of MCG or SCG cell groups in NR. The information element named CellGroupConfig may contain the TCI information element described below. The information element named CellGroupConfig may be rephrased as a cell group configuration information element or cell group configuration. In addition, when an information element named CellGroupConfig is used to configure an SCG cell group in NR, this information element named CellGroupConfig may be referred to as configuration on the SCG side. An information element named SpCellConfig contained in an 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 SpCell configuration information element or SpCell configuration. The information element named DeactivatedSCG-Config-r17 included in the information element named SpCellConfig may be an information element set in deactivation of SCG, which will be described later. The information element named DeactivatedSCG-Config-r17 may be rephrased as configuration for SCG deactivation.

Explain the activation and deactivation of cells. In a terminal device that communicates with Dual Connectivity, the master cell group (MCG) and secondary cell group (SCG) settings are notified from the base station device by the above-mentioned message regarding reconfiguration of the RRC connection. Each cell group may consist of SpCells and zero or more SCells. SpCell of MCG is also called PCell. SpCell of SCG is also called PSCell.

Cell deactivation does not apply to PCells, but may apply to PSCells. In this case, cell deactivation may be performed differently for SpCells and SCells.

Cell activation and deactivation may be handled by a MAC entity that exists for each cell group. The SCell configured in the terminal device may be activated and/or deactivated by some or all of (A) to (C) below.
(A) Reception of MAC CE that activates/deactivates SCell (B) Expiration of SCell inactivity timer set for each SCell (Even if the SCell is limited to SCell in which PUCCH is not set good)
(C) RRC parameter (sCellState) set for each SCell set in the terminal device

Specifically, the MAC entity of the terminal device may perform some or all of (1) to (3) of the following processing (AD) for each SCell set in the cell group.

Processing (AD)
(1) If the RRC parameter (sCellState) set in the SCell is set to activated when the SCell is set, or if a MAC CE that activates the SCell is received, the MAC entity of the terminal device performs processing ( Execute part or all of (1) to (3) of AD-1). Otherwise, if a MAC CE deactivating the SCell is received or if the SCell inactivity timer expires in the active SCell, the MAC entity of the terminal device performs process (AD-2).
(2) if an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of the active SCell, or if an uplink grant or downlink allocation for the active SCell is signaled by the PDCCH of a serving cell; , a MAC PDU is sent in a configured uplink grant or a MAC PDU is received in a configured downlink allocation, the MAC entity of UE 122 restarts the SCell inactivity timer associated with that SCell. .
(3) If the SCell becomes inactive, the MAC entity of the terminal device performs processing (AD-3).

Processing (AD-1)
(1) If, in NR, this SCell was in an inactive state before receiving the MAC CE that activates this SCell, or if the RRC parameter (sCellState) set in that SCell when setting up the SCell is If it is set to activated, the MAC entity of the terminal device performs part or all of the processing (1) to (3) of processing (AD-1-1).
(2) The MAC entity of the terminal device starts or restarts (if the SCell inactivity timer has already started) the SCell inactivity timer associated with the SCell.
(3) If the Active DL BWP is not a Dormant BWP, the suspended Type 1 Configured Uplink Grant associated with this SCell according to the stored configuration. If present, the terminal's MAC entity (re)initializes it. The terminal's MAC entity then triggers the PHR.

Treatment (AD-1-1)
(1) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is not set to a dormant BWP, the terminal device The MAC entity performs processing (AD-1-1-1).
(2) If the BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) set in the RRC message for that SCell is set to Dormant BWP, the terminal device The MAC entity will stop this serving cell's BWP-Inactivity Timer (bwp-InactivityTimer) if it is running.
(3) The MAC entity of the terminal device uses the downlink BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the RRC message for the SCell and the first active uplink BWP. Activate the uplink BWP indicated by the identifier (firstActiveUplinkBWP-Id).

Treatment (AD-1-1-1)
The MAC entity of the terminal device activates the SCell at a predetermined timing and applies normal SCell operations including some or all of (A) to (E) below.
(A) Transmit a Sounding Reference Signal (SRS) on this SCell.
(B) Report CSI for this SCell.
(C) Monitor the PDCCH of this SCell.
(D) Monitor the PDCCH for this SCell. (If scheduling is done for this SCell in another serving cell)
(E) If PUCCH is configured, transmit PUCCH in this SCell.

Processing (AD-2)
The MAC entity of the terminal equipment implements some or all of (A) to (F) below.
(A) Inactivating this SCell.
(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 grant type 2 configured uplink grants associated with this SCell.
(E) Suspend all configured uplink grants of grant type 1 associated with this SCell.
(F) Flush the HARQ buffer associated with this SCell.

Processing (AD-3)
The MAC entity of the terminal equipment implements some or all of (A) to (D) below.
(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.

As described above, the SCell is activated and deactivated by the processing (AD) performed by the MAC entity.

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

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

Here, the bandwidth part (BWP) will be explained.

The BWP may be part or all of the bandwidth of the serving cell. A BWP may also be called a carrier BWP. A terminal device may be configured with one or more BWPs. A certain BWP may be set by information contained in the system information associated with the synchronization signal detected in the initial cell search. Also, a certain BWP may be a frequency bandwidth associated with a frequency for initial cell search. Some BWPs may also be configured with RRC signaling (eg Dedicated RRC signaling). Also, the downlink BWP (DL BWP) and the uplink BWP (UL BWP) may be configured separately. Also, one or more uplink BWPs may be associated with one or more downlink BWPs. Further, the association between the uplink BWP and the downlink BWP may be a default association, may be an association by RRC signaling (for example, Dedicated RRC signaling), or may be associated by physical layer signaling (for example, downlink The association may be based on downlink control information (DCI) notified by a control channel, or a combination thereof, and CORESET may be set in the downlink BWP.

A BWP may consist of a group of consecutive physical radio blocks (PRB: Physical Resource Block). Also, parameters of the BWP (one or more BWPs) of each component carrier may be set for the terminal device in the connected state. The BWP parameters for each component carrier include (A) the type of cyclic prefix, (B) the subcarrier spacing, (C) the frequency position of the BWP (for example, the start position or center frequency position on the low frequency side of the BWP) ( For the frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used.In addition, the offset unit may be a subcarrier unit or a resource block unit. Also, both ARFCN and offset may be configured), (D) BWP bandwidth (e.g. number of PRBs), (E) control signal resource configuration information, (F) SS block center frequency location (For the frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used. Further, the offset unit may be a subcarrier unit, a resource block unit Also, both the ARFCN and the offset may be set.) may be included. Also, the resource configuration information of the control signal may be included in the BWP configuration of at least some or all of the PCell and/or PSCell.

A terminal device may transmit and receive in an Active BWP out of one or more set BWPs. One or more BWPs may be configured in one serving cell associated with the terminal. Of the one or more BWPs configured for one serving cell associated with the terminal, at most one uplink BWP and/or at most one downlink BWP is Active BWP at any given time. may be set to be Downlink Active BWP is also called Active DL BWP. Uplink Active BWP is also called Active UL BWP. Also, among the BWPs set in one or more terminal devices, a BWP that is not an active BWP may be referred to as an inactive BWP.

Next, I will explain the activation/deactivation of BWP. Activating a BWP may mean activating a BWP or activating an Inactive BWP. Also, deactivation of BWP may mean deactivation of BWP or deactivation of Active BWP. BWP switching in the serving cell is used to activate the Inactive BWP and deactivate the Active BWP.

BWP switching is controlled by the MAC entity itself for PDCCH indicating downlink assignment or uplink grant, BWP inactivity timer, RRC signaling, or initiation of random access procedures. Active BWP of the serving cell is indicated by RRC or PDCCH.

Next, I will explain the BWP inactivity timer (bwp-InactivityTimer). For each activated serving cell for which the BWP inactivity timer is set, the MAC entity performs some or all of (1) to (2) of the following processing (DB) to implement.

Processing (DB)
(1) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set and the Active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, but the Active DL BWP is indicated by the dormant BWP identifier (dormantBWP-Id) not a BWP, or if the defaultDownlinkBWP-Id of the default downlink BWP is not set, the Active DL BWP is not the initial downlink BWP (initialDownlinkBWP), and the Active DL BWP is not the BWP indicated by the dormantBWP-Id The MAC entity of the device performs (1) and (2) of the following processing (DB-A).
(2) If the MAC entity of the terminal device receives the PDCCH for BWP switching and switches the Active DL BWP, it performs the following process (DB-B).

Processing (DB-A)
(1) if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received in Active DL BWP, or if for Active DL BWP, Received PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant or if MAC PDU was sent with configured uplink grant or configured downlink If a MAC PDU has been received for allocation, the MAC entity of the terminal performs the following processing (DB-A-1).
(2) If the BWP inactivity timer associated with the Active DL BWP expires (Expire), the MAC entity of the terminal device performs the following process (DB-A-2).

Processing (DB-A-1)
If the random access procedure associated with this serving cell is not in progress, or the ongoing random access procedure associated with this serving cell was successfully completed by receiving a PDCCH addressed to C-RNTI ), start or (if the BWP inactivity timer was already started) restart the BWP inactivity timer associated with the Active DL BWP.

Processing (DB-A-2)
If defaultDownlinkBWP-Id is set, perform BWP switching to the BWP indicated by this defaultDownlinkBWP-Id; otherwise, perform BWP switching to initialDownlinkBWP.

Processing (DB-B)
If defaultDownlinkBWP-Id is set, the switched Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, and if the switched Active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id, then the Active DL BWP is associated with Starts or restarts the BWP inactivity timer (if the BWP inactivity timer has already started).

In each activated serving cell where the BWP is configured, the MAC entity of the terminal equipment, if the BWP is activated (is Active BWP) and the Active DL BWP in that serving cell is not a dormant BWP (dormant BWP) If so, perform some or all of (A) to (H) below.
(A) Transmit UL-SCH on that BWP.
(B) If a PRACH occasion is configured, send RACH on that BWP.
(C) Monitor the PDCCH on that BWP.
(D) If PUCCH is configured, transmit PUCCH on that BWP.
(E) Report CSI on its BWP.
(F) If SRS is configured, send SRS on that BWP.
(G) Receive DL-SCH on that BWP.
(H) (Re)initialize all suspended configured uplink grants of grant type 1 configured in that Active BWP according to the stored configuration, if any.

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

Next, I will explain the deactivation and activation of SCG.

Inactivation of SCG may mean inactivation of SCG. Also, deactivating an SCG may mean deactivating a cell group in which a MAC entity is associated with the SCG and corresponds to the MAC entity. Inactivation of SCG may mean inactivation of PSCell (SpCell of SCG) or inactivation of PSCell. Activation of SCG may mean activating SCG. Also, activating an SCG may mean activating a cell group in which a MAC entity is associated with the SCG and corresponds to said MAC entity. Activation of SCG may mean activation of PSCell (SpCell of SCG) or activation of PSCell.

In LTE and/or NR, the SCG inactive state means that the terminal device performs some or all of (A) to (P) of the following processing (SD-1) in the SCG PSCell (SpCell). may be in a state where In addition, the inactive state of SCG may mean a state in which SCG is inactivated.

Processing (SD-1)
(A) Do not transmit SRS in this PSCell.
(B) Measure CSI for this PSCell.
(C) Do not report CSI for this PSCell.
(D) Do not transmit PUCCH in this PSCell.
(E) Do not transmit UL-SCH on this PSCell.
(F) Do not transmit RACH on this PSCell.
(G) Do not monitor the PDCCH of this PSCell.
(H) Do not monitor PDCCH for this PSCell.
(I) Inactivate the Active BWP in this PSCell.
(J) Perform discontinuous reception (DRX) in this PSCell.
(K) PDCCH for this PSCell addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this PSCell and/or this PSCell Do not monitor PDCCH for
(L) PDCCH for this PSCell with BWP activated on this PSCell and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or do not monitor the PDCCH for this PSCell.
(M) This PSCell performs Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and/or Radio Link Monitoring (RLM).
(N) Suspend some or all configured uplink grants of grant type 1 associated with this PSCell.
(O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this PSCell.
(P) Have the SCG MAC entity perform a partial MAC reset.

(M) of the above process (SD-1) may be implemented based on the inclusion of the bfd-and-RLM parameter in the SCG side settings.

(P) of the above treatment (SD-1) may include some or all of (A) to (O) of the above treatment (SD-1).

In LTE and/or NR, the SCG active state means that the terminal device performs some or all of (A) to (O) of the following processing (SA-1) in the SCG PSCell (SpCell). state. Moreover, the active state of SCG may mean a state in which SCG is activated.

Treatment (SA-1)
(A) Transmit SRS with this PSCell.
(B) Measure CSI for this PSCell.
(C) Report CSI for this PSCell.
(D) Transmit PUCCH in this PSCell.
(E) Transmit UL-SCH on this PSCell.
(F) Transmit RACH on this PSCell.
(G) Monitor the PDCCH of this PSCell.
(H) Monitor the PDCCH for this PSCell.
(I) Activate the Inactive BWP in this PSCell.
(J) Perform discontinuous reception (DRX) in this PSCell.
(K) PDCCH for this PSCell addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant for UL-SCH transmission on this PSCell and/or this PSCell monitor the PDCCH for
(L) PDCCH for this PSCell with BWP activated on this PSCell and addressed to C-RNTI, MCS-C-RNTI and/or CS-RNTI indicating uplink grant in said BWP; and / Or monitor the PDCCH for this PSCell.
(M) This PSCell performs Automatic Gain Control (AGC), Beam Failure Detection (BFD) including beam failure recovery, and/or Radio Link Monitoring (RLM).
(N) (re)initialize some or all suspended configured uplink grants of grant type 1 associated with this PSCell according to the stored configuration, if any; .
(O) Maintain the timeAlignmentTimer (TAT) associated with the TAG (PTAG) containing this PSCell.

In LTE and/or NR, the terminal device may determine that the SCG is inactive based on some or all of (A) to (H) of the following conditions (SD-2). Note that the signaling and control elements (A) to (F) of the following condition (SD-2) may be notified from the base station apparatus to the terminal apparatus via the SCG. Additionally or alternatively, the signaling and control elements in (A) through (F) of the following conditions (SD-2) shall be provided via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). The terminal device may be notified from the station device.

Conditions (SD-2)
(A) Reception of RRC signaling instructing to deactivate SCG (B) Reception of MAC CE instructing to deactivate SCG (C) Reception of RRC signaling instructing to deactivate PSCell Reception (D) Reception of MAC CE instructing PSCell to be deactivated (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) Expiration of SCG inactivity timer (H) PSCell expiration of the inactivity timer of

The RRC signaling of (A), (C), and (E) of the above condition (SD-2) may include a parameter called scg-State, for example. If scg-State is included in RRC signaling, it may indicate SCG deactivation, and if scg-State is not included in RRC signaling, it may indicate SCG activation. Also, the scg-State may be included in the RRC Connection Reconfiguration message, RRC Reconfiguration message, and/or RRC Resume message. Also, the RRC signaling may be generated at the MN. Also, the scg-State may not be included in the RRC signaling generated by the SN. In this case, the SCG activation/deactivation may not be determined based on whether scg-State is included in the RRC signaling generated by the SN.

In LTE and/or NR, the terminal device may determine that the SCG is activated based on some or all of (A) to (K) of the following conditions (SA-2). The signaling and control elements (A) to (F) of condition (SA-2) below may be notified from the base station apparatus to the terminal apparatus via the SCG. Additionally or alternatively, the signaling and control elements of (A) to (F) of the following condition (SA-2) shall be transmitted to the base via a cell group other than the SCG (MCG, SCG other than the SCG, etc.). The terminal device may be notified from the station device. The SCG being in an active state may also mean that the SCG is not in an inactive state.

Condition (SA-2)
(A) Reception of RRC signaling instructing to activate SCG (B) Reception of MAC CE instructing to activate SCG (C) Reception of RRC signaling instructing to activate PSCell (D) ) Receipt of MAC CE instructing to activate PSCell (E) Reception of other RRC signaling (F) Reception of other MAC CE (G) SCG inactivity timer (H) PSCell inactivity timer (I ) initiation of a random access procedure due to a scheduling request triggered to transmit a MAC PDU containing a MAC SDU; (J) initiation of a random access procedure; (K) due to a scheduling request (in other words, the MAC entity itself initiated) random access procedure

The RRC signaling of (A), (C), and (E) of the above conditions (SA-2) is that the parameter scg-State, for example, is not included in the RRC reconfiguration message and/or the RRC restart message. good. Also, the RRC signaling may be generated at the MN.

A terminal device that deactivates an SCG may implement part or all of (A) to (I) of the following process (SD-3) in the SCG.

Processing (SD-3)
(A) Consider that SCG is inactivated.
(B) Instruct lower layers (MAC entity, etc.) to deactivate the SCG.
(C) If the terminal device is in the RRC_CONNECTED state and the SCG was activated before receiving signaling instructing to deactivate the SCG, send an RRC reconfiguration message or RRC connection reconfiguration message. SRB3 is configured before receiving, and the SRB3 is released according to RRC signaling (RadioBearerConfig) for any radio bearer configuration included in the RRC reconfiguration message or the RRC connection reconfiguration message. If not, trigger the PDCP entity of said SRB3 to perform a discard of the SDU and additionally or alternatively re-establish the RLC entity of said SRB3.
(D) Inactivate all SCells.
(E) Consider all of the SCell inactivity timers associated with the active SCell to have expired.
(F) Consider all of the SCell inactivity timers associated with the dormant SCell to have expired.
(G) Do not start or restart the SCell inactivity timers associated with all SCells.
(H) Ignore MAC CE that activates SCell. For example, in the processing (AD), when receiving MAC CE to activate SCell and not instructed to deactivate SCG (or SCG is not inactive state), processing (AD -1).
(I) Execute the above process (AD-2). For example, when the treatment (AD) instructs to inactivate SCG (or SCG becomes inactive), treatment (AD-2) is performed.

When the MAC entity of the terminal device instructs the MAC entity so that the upper layer (RRC entity, etc.) deactivates the SCG based on (B) of the above process (SD-3), all of the SCG Inactivating SCells may additionally or alternatively inactivate PSCells based on the above treatment (SD-1).

A terminal device that activates an SCG may implement part or all of (A) to (D) of the following process (SA-3) in that SCG.

Treatment (SA-3)
(A) SCG is considered to be activated.
(B) If an inactive SCG has been set before the terminal receives signaling to activate the SCG, instruct the lower layer (such as the MAC entity) to activate the SCG. do.
(C) Treatment (AD-1) is performed to activate all SCells.
(D) If SCG activation is performed based on RRC signaling, if this RRC signaling includes parameters related to random access to PSCell (SpCell), based on the notified parameters, the random access procedure in this PSCell Start.

The MAC entity of the terminal device performs the above process (SA-1 ) may activate the SCG.

FIG. 9 is a diagram showing an example of an embodiment. In FIG. 9, UE 122 receives a message (RRC signaling, MAC CE, etc.) notifying to deactivate SCG from eNB 102 or gNB 108 (step S900). UE 122 controls the SCG to be inactive based on the notification (step S902). Also, in FIG. 9, UE 122 receives a message (RRC signaling, MAC CE, etc.) notifying activation of SCG from eNB 102 or gNB 108 (step S900). UE 122 controls the SCG to be active based on the notification (step S902).

By the above operation, in the process of deactivating the SCG, the transmission unit 504 of the UE 122 transmits independently the MAC CE for changing the state of the cell of the SCG to the inactive state, efficient state change is possible. Further, when deactivation of SCG is performed based on RRC signaling, conventionally, the initial state is set in the RRC layer, and the state change is performed in the MAC layer. It is possible to efficiently change the state of the SCG while avoiding a mismatch between the instruction and the MAC layer instruction.

Explain conditional reconfiguration. The network may configure one or more candidate target SpCells for the terminal. Configuration parameters for each candidate target SpCell may be included in a conditional reconfiguration information element (Conditional Reconfiguration IE) of an RRC message and notified from the base station apparatus to the terminal apparatus. The terminal device evaluates whether an execution condition associated with each configured candidate target SpCell is satisfied. The terminal may apply a conditional reconfiguration that is tied to one of the candidate target SpCells that meet the execution conditions.

By means of the conditional reconfiguration information element included in the RRC reconfiguration message, the terminal device specifies the execution condition (condExecutionCond or condExecutionCondSN) that must be satisfied to trigger the execution of the conditional reconfiguration and the execution condition. One or more pairs with information (condRRCReconfig) indicating the RRC reconfiguration message to be applied when satisfying may be set. Said condRRCReconfig may be an RRC message (RRC reconfiguration message) containing configuration parameters for accessing candidate target SpCells. Further, the conditional reconfiguration information element may include an identifier (CondReconfigId) that is associated with each of the one or more pairs and that can identify each pair. Conditional reconfiguration when the candidate target SpCell is a PCell is also called Conditional Handover. Conditional resetting when the candidate target SpCell is a PSCell is also called conditional PSCell Change.

In addition, when a PSCell change (intra-SN CPC: intra-SN Conditional PSCell Change) to a candidate target SpCell with the same SN as the current SN is performed, and the MN is not involved in the PSCell change Alternatively, the RRC reconfiguration message to be applied when the execution condition is satisfied, notified by the condRRCReconfig, may be an RRC reconfiguration message generated by the SN.

Also, if no SN is currently configured and a PSCell addition (inter-SN CPA: inter-SN Conditional PSCell Addition) to the candidate target SpCell of the SN is performed, the candidate target SpCell of the SN different from the current SN When a PSCell change (inter-SN CPC: inter-SN Conditional PSCell Change) is performed, or when intra-SN CPC is performed and the MN is involved in the PSCell change, it is notified by the condRRCReconfig The RRC reconfiguration message applied when the execution condition is satisfied may be the RRC reconfiguration message generated by the MN. In this case, the configuration parameters for accessing the candidate target SpCell may be included in the information element (MRDC-SecondaryCellGroupConfig) in the RRC reconfiguration message generated by the MN. Also, when intra-SN CPC is performed and the MN is not involved in the PSCell change, the RRC reconfiguration message, which is notified by the condRRCReconfig and is applied when the execution condition is satisfied, is sent by the MN to the MN. It may be a generated RRC reconfiguration message.

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

Various embodiments of the present invention will be described based on the above description. In addition, each process demonstrated above may be applied about each process abbreviate|omitted by the following description.

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

UE 122 shown in FIG. 5 includes a receiving unit 500 that receives control information (DCI, MAC CE, RRC signaling, etc.) from the base station apparatus, a processing unit 502 that performs processing according to the parameters included in the received control information, and a base station. It consists of a transmission section 504 that transmits control information (UCI, MAC CE, RRC signaling, etc.) to the station equipment. The base station apparatus described above may be eNB 102 or gNB 108 . Also, processing unit 502 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 502 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can

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

The base station apparatus shown in FIG. 6 creates a transmission unit 600 that transmits control information (DCI, MAC CE, RRC signaling, etc.) to UE 122, and creates control information (DCI, MAC CE, RRC signaling, etc.) and transmits it to UE 122. Thus, it consists of a processing unit 602 that causes the processing unit 502 of the UE 122 to perform processing, and a receiving unit 604 that receives control information (UCI, MAC CE, RRC signaling, etc.) from the UE 122 . Also, processing unit 602 may include some or all of the functionality of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer, RRC layer, and NAS layer). That is, the processing unit 602 includes part or all of the physical layer processing unit, MAC layer processing unit, RLC layer processing unit, PDCP layer processing unit, SDAP processing unit, RRC layer processing unit, and NAS layer processing unit. you can

An example of the processing of the terminal device in this embodiment will be described using FIG.

FIG. 10 is a diagram showing an example of processing related to conditional resetting of the terminal device in this embodiment. The processing unit 502 of the UE 122 determines whether an execution condition for triggering execution of conditional reconfiguration is satisfied for each configured candidate target SpCell (step S1000). A cell whose execution condition is satisfied is also called a triggered cell. If there are one or more triggered cells, the processing unit 502 of the UE 122 selects one cell from among them and applies condRRCReconfig (RRC reconfiguration message) of the selected cell (step S1002).

FIG. 11 is a diagram showing an example of processing related to RRC resetting in this embodiment. Processing unit 502 of UE 122 receives an RRC reconfiguration message from eNB 102 and/or gNB 108 and/or performs conditional reconfiguration (condRRCReconfig (RRC reconfiguration message) is applied). Based on this, RRC reconfiguration using the RRC reconfiguration message is performed (step S1100). The processing unit 502 of the UE 122 generates an RRC reconfiguration complete message, and the transmitting unit 504 of the UE 122 transmits the RRC reconfiguration complete message to the eNB 102 and/or gNB 108 (step S1102).

In step S1100, processing section 502 of UE 122 determines that the RRC reconfiguration message is neither (A) received via SRB3 nor (B) received included in the mrdc-SecondaryCellGroup information element. Based on this, a decision to activate or deactivate the SCG based on whether information (eg, scg-State) is included in the RRC reconfiguration information may be made. In other words, the processing unit 502 of the UE 122 determines whether the applicable RRC reconfiguration message is (A) received via SRB3 or (B) received included in the mrdc-SecondaryCellGroup information element. , the decision to activate or deactivate the SCG based on whether information (eg, scg-State) is included in the RRC reconfiguration information may not be performed.

At step S1102, the processing unit 502 of the UE 122 may perform the following process SCR.

(Processing SCR)
(1) If the RRC reconfiguration message includes the MRDC-SecondaryCellGroupConfig information element and the SCG is NR, processing section 502 of UE 122 uses the information element (nr -SCG-Response information element) contains the RRC reconfiguration complete message for the SN. Also, at this time, if this RRC reconfiguration message is applied by performing conditional reconfiguration, the condReconfigId of the cell selected in the conditional reconfiguration is sent to the RRC reconfiguration complete message for the MN and/or the RRC reconfiguration for the SN. May be included in the completion message.
(2) otherwise, if the RRC reconfiguration message was received via SRB3 and was not included in the message for MCG link recovery (DLInformationTransferMRDC), or if RRC reconfiguration If the message is received via SRB1, contains the MRDC-SecondaryCellGroupConfig information element, and the SCG is NR, processing section 502 of UE 122 performs the following (2-A). you can
(2-A) If this RRC reconfiguration message is applied by performing conditional reconfiguration, processing section 502 of UE 122 sets condReconfigId of the cell selected in conditional reconfiguration to RRC reconfiguration completion for SN. message and/or RRC Reconfiguration Complete message to MN. Note that the processing unit 502 of the UE 122 may include the condReconfigId in the RRC reconfiguration complete message only when the SCG is inactive. Note that the condReconfigId included in the RRC reconfiguration complete message may be other information for identifying the selected cell (for example, information such as physical cell identifier, SSB frequency, and/or SSB subcarrier spacing).

In step S1102, the processing unit 502 of the UE 122 that generated the RRC reset completion message may perform the following process SR.

(Processing SR)
(1) If the RRC reconfiguration message was received via SRB3 and was not included in the message for MCG link recovery (DLInformationTransferMRDC), if the SCG is not inactive (active state), the processing unit 502 of the UE 122 executes the following (1-A), and if the SCG is not in an active state (is in an inactive state), the processing unit 502 of the UE 122 executes the following (1-B) to run.
(1-A) In order to transmit the RRC reconfiguration complete message via SRB3, processing section 502 of UE 122 submits the RRC reconfiguration complete message to the lower layer of the RRC layer. The lower layer may be the PDCP layer of UE 122, for example.
(1-B) In order to transmit an RRC reconfiguration complete message to SN via MCG (SRB1), processing section 502 of UE 122 is configured for uplink transfer of MR-DC dedicated information. The RRC reconfiguration complete message is embedded in the message (ULInformationTransferMRDC message) used for the RRC layer, and the ULInformationTransferMRDC message is submitted to the lower layer of the RRC layer. The lower layer may be the PDCP layer of UE 122, for example.

The aforementioned RRC reconfiguration message may be an RRC connection reconfiguration message or other RRC signaling. Also, the aforementioned RRC reconfiguration complete message may be an RRC connection reconfiguration complete message, or may be other RRC signaling.

Thus, in this embodiment, when the SCG is in an inactive state when conditional reconfiguration is executed, necessary information can be transmitted to the SN using an appropriate SRB.

Unless otherwise specified, the radio bearer in the above description may be DRB, SRB, or both DRB and SRB.

Also, in the above description, expressions such as "notified" and "receiving indication" may be replaced with each other.

Also, in the above description, expressions such as "associate", "associate", and "associate" may be replaced with each other.

Also, in the above description, expressions such as "included", "contained", and "was included" may be exchanged for each other.

Also, in the above explanation, "the above-mentioned" may be replaced with "the above-mentioned".

Also, in the above explanation, "SCG SpCell" may be replaced with "PSCell".

Also, in the above description, expressions such as "determined as", "set with", and "including" may be exchanged for each other.

In the above description, the "dormant state" may be replaced with the "inactive state", and the "state recovered from the dormant state" may be replaced with the "active state". In the above description, "activation" and "inactivation" may be replaced with "active state" and "inactive state", respectively.

In the above explanation, "transition from X to Y" can be rephrased as "transition from X to Y". Moreover, in the above description, "make a transition" may be rephrased as "determine a transition".

Also, in the example of each process or the example of the flow of each process in the above description, some or all of the steps may not be executed. In addition, the order of the steps may be different in the example of each process or the example of the flow of each process in the above description. In addition, in the examples of each process or the example of the flow of each process in the above description, some or all of the processes in each step may not be executed. Further, in the example of each process or the example of the flow of each process in the above description, the order of the processes in each step may be different. Also, in the above description, "perform B based on A" may be rephrased as "perform B." That is, "doing B" may be performed independently of "being A".

In addition, in the above explanation, "A may be rephrased as B" may include the meaning of rephrasing B as A in addition to rephrasing A as B. In addition, in the above description, when "C may be D" and "C may be E" are stated, "D may be E" may be included. In addition, in the above description, when "F may be G" and "G may be H" may include "F may be H".

Also, in the above explanation, if the condition "A" and the condition "B" are contradictory conditions, the condition "B" may be expressed as the "other" condition of the condition "A". good.

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

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

In addition, "computer-readable recording medium" means a medium that dynamically stores programs for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. , it may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. .

Also, each functional block or feature of the apparatus used in the embodiments described above may be implemented or performed in an electrical circuit, typically an integrated circuit or multiple integrated circuits. Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may be composed of digital circuits or may be composed of analog circuits. In addition, when an integrated circuit technology that replaces current integrated circuits emerges due to advances in semiconductor technology, it is also possible to use integrated circuits based on this technology.

Note that this embodiment is not limited to the embodiment described above. In the embodiment, an example of the device was described, but the present embodiment is not limited to this, and is a stationary or non-movable electronic device installed indoors or outdoors, such as AV equipment, kitchen equipment , cleaning/washing equipment, air-conditioning equipment, office equipment, vending machines, other household equipment, and other terminal equipment or communication equipment.

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, etc. within the scope of this embodiment are also included. In addition, the present embodiment can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also within the technical scope of the present embodiment. include. Further, it also includes a configuration in which the elements described in the above embodiments are replaced with the elements having the same effect.

One aspect of the present invention is, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program, etc. be able to.

100 E-UTRA
102 eNB
104 EPCs
106NR
108 gNB
110 5GC
112, 114, 116, 118, 120, 124 interfaces
122 UEs
200, 300 PHYs
202, 302 MACs
204, 304 RLC
206, 306 PDCP
208, 308 RRC
310 SDAP
210, 312 NAS
500, 604 receiver
502, 602 processor
504, 600 transmitter

Claims (3)

1. A terminal device,
   a receiver for receiving an RRC reconfiguration message and/or RRC signaling encapsulating said RRC reconfiguration message;
   A processing unit that performs settings based on the RRC reconfiguration message,
   The processing unit is
   The RRC reconfiguration message is received via SRB3 (signaling radio bearer 3), is not included in a message for master cell group (MCG) link recovery, and secondary cell group (SCG) is If inactive, the terminal sends an RRC reconfiguration complete message to the secondary node via SRB1.
2. A method applied to a terminal device, comprising:
   receiving an RRC reconfiguration message and/or RRC signaling encapsulating said RRC reconfiguration message;
   performing configuration based on the RRC reconfiguration message;
   The RRC reconfiguration message is received via SRB3 (signaling radio bearer 3), is not included in a message for master cell group (MCG) link recovery, and secondary cell group (SCG) is If inactive, how to send an RRC Reconfiguration Complete message to the secondary node via SRB1.
3. An integrated circuit mounted in a terminal device,
   the ability to receive an RRC reconfiguration message and/or RRC signaling encapsulating said RRC reconfiguration message;
   causing the terminal device to exhibit a function of performing configuration based on the RRC reconfiguration message;
   The RRC reconfiguration message is received via SRB3 (signaling radio bearer 3), is not included in a message for master cell group (MCG) link recovery, and secondary cell group (SCG) is If inactive, send an RRC reconfiguration complete message to the secondary node via SRB1 Integrated circuit.

Images