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

Abstract

A terminal device wherein if a data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is a DRB of a secondary cell group and the secondary cell group has been deactivated, a radio resource control (RRC) layer processing unit is notified that uplink data for the DRB has arrived, and, on the basis of this notification, an RRC message notifying a base station device that uplink data to be transmitted is present in the secondary cell group is generated, and the RRC message is transmitted to the base station device.

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. 2021-125590 filed in Japan on July 30, 2021, the content of which is incorporated herein.

In the 3rd Generation Partnership Project (3GPP), 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 LTE Terrestrial Radio Access) is a radio access technology (RAT) for 3.9th and 4th generation cellular mobile communication systems. . At present, 3GPP is still conducting technical studies and establishing standards for extension techniques for E-UTRA (Non-Patent Document 2). E-UTRA is also called Long Term Evolution (LTE: registered trademark), and E-UTRA extension technologies are sometimes called LTE-Advanced (LTE-A) and LTE-Advanced Pro (LTE-A Pro). .

　In addition, NR (New Radio, or NR Radio access) has started technical study and standardization as a radio access technology for 5th Generation (5G) cellular mobile communication systems at 3GPP. At present, 3GPP is still conducting technical studies and establishing standards for NR extension technology (Non-Patent Document 1).

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. A terminal device needs to constantly monitor a plurality of cell groups so that communication can be performed with low delay when large-capacity data communication occurs, and there is a problem of consuming a lot of power. Therefore, a technique for performing or stopping monitoring of some cell groups at low frequency (cell group deactivation technique) is being studied.

However, how is it possible to detect that uplink data is generated when the cell group is deactivated and the transmission of the radio bearer and/or the cell group used by the cell group is suspended? It is not disclosed whether the

One aspect of the present invention has been made in view of the circumstances described above, and one object thereof is to provide a terminal device, a base station device, a 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 in which a secondary cell group is set from a base station device, and a data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is the secondary cell group and a PDCP layer processing unit that notifies a radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived based on the fact that the DRB is the DRB and that the secondary cell group is deactivated. , the RRC layer processing unit for generating an RRC message for notifying the base station apparatus that uplink data to be transmitted is in the secondary cell group based on the notification; and transmitting the RRC message to the base station apparatus. and a transmitter.

Further, one aspect of the present invention is a method applied to a terminal device in which a secondary cell group is set from a base station device, wherein a data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is and notifying a radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived based on the DRB of the secondary cell group and the deactivation of the secondary cell group. generating an RRC message for notifying the base station apparatus that uplink data to be transmitted is in the secondary cell group based on the notification; and transmitting the RRC message to the base station apparatus. is to provide

Further, one aspect of the present invention is an integrated circuit implemented in a terminal device in which a secondary cell group is set from a base station device, and is a data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity. is the DRB of the secondary cell group, and based on the fact that the secondary cell group is deactivated, notifies the radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived. a function of generating an RRC message for notifying the base station apparatus that uplink data to be transmitted is in the secondary cell group based on the notification; and a function of transmitting the RRC message to the base station apparatus. and to the terminal device.

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 an embodiment of the invention; FIG. FIG. 4 is a diagram of an example of NR UP protocol configuration according to an embodiment of the present invention; FIG. 3 is a diagram of an example of the NRCP protocol configuration according to the embodiment of the present invention; The figure which shows an example of the procedure for various settings in RRC which concerns on embodiment of this invention. The block diagram which shows the structure of the terminal device in embodiment of this invention. 1 is a block diagram showing the configuration of a base station apparatus according to an embodiment of the present invention; FIG. An example of ASN.1 description included in a message regarding RRC connection reconfiguration in NR according to an embodiment of the present invention. An example of ASN.1 description of an RRC reconfiguration message in an embodiment of the present invention. An example of ASN.1 description of the cell group setting information element in the embodiment of the present invention. An example of ASN.1 description of SpCell settings in the embodiment of the present invention. An example of ASN.1 description of a reset information element with synchronization in an embodiment of the present invention. An example of ASN.1 description of the ServingCellConfigCommon information element in the embodiment of the present invention. An example of ASN.1 description of the SCell configuration information element in the embodiment of the present invention. An example of processing of a terminal device according to an embodiment of the present invention. An example of processing of a terminal device according to an embodiment of the present invention.

Hereinafter, one embodiment of the present invention will be described in detail with reference to the drawings.

The following description relates to the name of each node and entity, processing, etc. when the radio access technology is E-UTRA or NR. It may be applied to access technologies. The name of each node or entity in this description may be another name.

FIG. 1 is an example of a schematic diagram of a communication system according to an embodiment of the present invention. It should be noted 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 embodiment of the present invention, and may have other functions.

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 (User Plane: UP) protocol, which will be described later, and an NR control plane (Control Plane: CP) protocol, which will be described later. gNB 108 may terminate NR user plane protocols and NR control plane protocols to UE 122 .

　5GC110 may be a 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.

　UE 122 may be a terminal device capable of receiving broadcast information and paging messages transmitted from gNB 108. Also, the UE 122 may be a terminal device capable of wireless connection with the gNB 108 . Also, the UE 122 may be a terminal device capable of establishing wireless connections with multiple gNBs 108 at the same time. UE 122 may have the NR protocol. Note that the wireless connection may include a Radio Resource Control (RRC) connection.

When UE122 communicates with gNB108, radio connection may be established by establishing a radio bearer (RB) between UE122 and gNB108. 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 Data Radio Bearer). 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).

If the core network connected to gNB108 with which UE122 communicates is 5GC110, each DRB established between UE122 and gNB108 is further included in one of the PDU (Packet Data Unit) sessions established within 5GC110. can be linked. There may be one or more QoS flows in each PDU session. Each DRB may be mapped with one, multiple QoS flows, or no QoS flows. Each PDU session may be identified with a PDU session identifier (Identity, Identifier, or ID). Each QoS flow may also be identified by a QoS flow identifier (Identity, Identifier, or ID). Also, the same QoS may be guaranteed for data such as IP packets and Ethernet frames passing through the same QoS flow.

In the following description, the gNB 108 is also simply referred to as a base station device, and the UE 122 is also simply referred to as a terminal device or UE.

　Figures 2 and 3 are diagrams showing an example of the NR protocol configuration according to the embodiment of the present invention. Note that the functions of each protocol described using FIGS. 2 and 3 are part of the functions closely related to the embodiment of the present invention, and may include other functions. In the embodiment of the present invention, an uplink (UL) may be a link from a terminal device to a base station device. In the embodiment of the present invention, a downlink (DL) may be a link from a base station apparatus to a terminal apparatus. In embodiments of the present invention, a sidelink (SL) may be a link from terminal to terminal.

Figure 2 is a diagram of the NR User Plane (UP) protocol stack. The NR UP protocol may be the protocol between UE 122 and gNB 108, as shown in FIG. That is, the NR UP protocol may be a protocol that terminates at the gNB 108 on the network side. As shown in Figure 2, the NR UP protocol stack consists of a physical layer PHY300, a medium access control layer MAC302, a radio link control layer RLC304, and packet data convergence. It may include PDCP 306, which is a protocol (Packet Data Convergence Protocol) layer, and SDAP 310, which is a Service Data Adaptation Protocol layer.

Fig. 3 is a diagram of the NR Control Plane (CP) protocol configuration. As shown in FIG. 3, in the NR CP protocol, the radio resource control layer, RRC 308, may be the protocol between the UE 122 and the gNB 108. That is, RRC 308 may be a protocol that terminates at gNB 108 on the network side. Also in the NR 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.

Note that the AS (Access Stratum) layer may be a layer that terminates between the UE 122 and the 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

　The entity in the NR AS layer will be explained. 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 functionality 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 simply referred to as MAC, RLC, PDCP, SDAP, and RRC, respectively.

The data provided to the lower layer from MAC, RLC, PDCP, and SDAP may be called MAC PDU (Protocol Data Unit), RLC PDU, PDCP PDU, and SDAP PDU, respectively. The data provided from lower layers to MAC, RLC, PDCP, and SDAP may also be called MAC PDU, RLC PDU, PDCP PDU, and SDAP PDU, respectively. Also, the data provided from the upper layer to MAC, RLC, PDCP, and SDAP may be called MAC SDU (Service Data Unit), RLC SDU, PDCP SDU, and SDAP SDU, respectively. Also, data provided from MAC, RLC, PDCP, and SDAP to upper layers may be called MAC SDU, RLC SDU, PDCP SDU, and SDAP SDU, respectively. A segmented RLC SDU may also be referred to as an RLC SDU segment.

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 high-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.

The physical channels used for wireless communication between the terminal device and the base station device 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.

In addition, in NR, the PBCH may be used to report the time index (SSB-Index) within the period of the synchronization signal block (SS/PBCH block, also called 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 the set of PDCCH candidates may mean attempting to decode the PDCCH according to some DCI format. 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. Also, in the case of downlink, it may be used for transmission of system information (SI: System Information), random access response (RAR: Random Access Response), and the like.

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 control elements. 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 may be used to indicate initial connection establishment procedures, handover procedures, connection re-establishment procedures, synchronization (timing adjustments) for uplink transmissions, and requests for PUUCH resources. good.

I will explain an example of MAC functions. A MAC may be referred to as a MAC sublayer.

The MAC may have the function of mapping various logical channels (Logical Channel) to the 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.

　MAC may also have a function to perform error correction through HARQ (Hybrid Automatic Repeat reQuest). The MAC may also have a Scheduling Information Report 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.

　MAC may have a function to identify Multicast/Broadcast Service (MBS).

　MAC may have a function 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.

　MAC may have a Bandwidth Adaptation (BA) function. The MAC PDU may also include a MAC control element (MAC control element: MAC CE), which is an element for performing control in MAC.

　Explain 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.

　Explain the uplink mapping of logical channels and transport channels in 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.

　BCCH may be mapped to BCH (Broadcast Channel), which is a downlink transport channel, and/or 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 RLC may have a function to add a sequence number independent of the sequence number added by PDCP to the data provided by the upper layer PDCP. Also, RLC may have a function of segmenting data provided from PDCP and providing it to a lower layer. The RLC may also have a function of reassembling data provided from lower layers and providing the reassembled data to upper layers. The RLC may also have a data retransmission function and/or a retransmission request function (Automatic Repeat reQuest: ARQ).

Also, RLC may have a function to correct errors 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.

　In UM, the data received from the upper layer is divided and/or combined, the RLC header is added, etc., but data retransmission control does not have to be performed. 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 UM RLC entity. If the UM RLC entity is a bidirectional entity, the UM RRC entity may be configured as a UM RLC entity consisting of a transmitting side and a receiving side.

In AM, division and/or combination of data received from the upper layer, addition of RLC headers, data retransmission control, etc. may be performed. The AM RLC entity is a bi-directional entity and may be configured as an AM RLC consisting of a transmitting side and a receiving side.

Data provided to the lower layer by TM and/or data provided from the lower layer may be called TMD PDU. Data provided in UM to lower layers and/or data provided by lower layers may also be referred to as UMD PDUs. Data provided to lower layers by AM or data provided from lower layers may be referred to as AMD PDUs.

RLC PDUs may 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 data encryption/decryption functions. In addition, PDCP may have data integrity protection and integrity verification functions. 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.

A PDCP entity is a bi-directional entity and may consist of a transmitting PDCP entity and a receiving PDCP entity. 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, 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 mapping between downlink QoS flows and data radio bearers (DRBs) 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. There may be one SDAP entity in the terminal device per PDU session. Also, the SDAP entity of the terminal device may include a transmitting SDAP entity that processes uplink data and a receiving SDAP entity that processes downlink data.

I will explain an example of RRC functions.

　RRC may have a function to broadcast system information about AS and NAS. RRC may have a paging function initiated by the 5GC110. RRC may have an RRC connection management function. RRC may have security features including key management. RRC may have a radio bearer control function. RRC may have a cell group control function. RRC may have a mobility control function. The RRC may have terminal equipment measurement reporting and terminal equipment measurement reporting control functions. RRC may have QoS management functions. RRC may have radio link failure detection and recovery functionality. RRC may implement each function using RRC messages.

RRC messages may be sent using the logical channel BCCH, may be sent using the logical channel PCCH, may be sent using the logical channel CCCH, or may be sent using the logical channel CCCH, based on the message type. It may be sent using the channel's DCCH.

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, an RRC Setup Request message for requesting establishment of an RRC connection, a RRC Setup Request message for requesting resumption of a suspended RRC connection. RRC Resume Request message, RRC Reestablishment Request message for requesting re-establishment of RRC connection, RRC System Information Request message for requesting system information message required by terminal equipment (RRC System Info Request) message may be included. An RRC message sent in the uplink (UL) direction using CCCH may also include other RRC messages.

RRC messages sent in the downlink (DL) direction using CCCH include, for example, an RRC Reject message that rejects RRC connection establishment or RRC connection resumption, and an RRC setup for establishing SRB1, which will be described later. (RRC Setup) message, etc. may be included. An RRC message sent in the downlink (DL) direction using CCCH may also include other RRC messages.

RRC messages sent in the uplink (UL) direction using DCCH include, for example, a Measurement Report message used for notification of measurement results by the terminal equipment, and a message indicating successful completion of reconfiguration of the RRC connection. RRC Reconfiguration Complete message used to confirm, RRC Setup Complete message used to confirm successful completion of RRC connection establishment , RRC Reestablishment Complete message used to confirm successful completion of RRC connection re-establishment, confirm successful completion of RRC connection re-establishment RRC Resume Complete message used to confirm the successful completion of the security mode command, Security Mode Complete message used to confirm the successful completion of the security mode command, radio access of the terminal equipment A UE Capability Information message used to transfer capabilities may be included. Also, the RRC message sent in the uplink (UL) direction using DCCH may include other RRC messages.

RRC messages sent in the downlink (DL) direction using DCCH include, for example, an RRC Reconfiguration message used to command modification of an RRC connection, RRC connection release, Or RRC Release message used to instruct suspension of RRC connection, RRC Resume message used to resume suspended RRC connection, used for re-establishing SRB1 described later RRC Reestablishment message, Security Mode Command message used to direct the activation of AS security, UE used to request notification of the radio access capabilities of the terminal equipment. UE Capability Inquiry message, etc. may be included. RRC messages sent in the downlink (DL) direction using DCCH may also include other RRC messages.

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).

Note that an IP layer, a TCP (Transmission Control Protocol) layer above the IP layer, a UDP (User Datagram Protocol) layer, and the like may exist in layers (not shown) above the AS layer of the terminal device. An Ethernet layer may exist in a layer above the AS layer of the terminal device. It may be called a PDU layer (PDU layer) above the AS layer of the terminal device. The PDU layers may include IP layer, TCP layer, UDP layer, Ethernet layer, and so on. Application layers may exist in higher layers such as the IP layer, TCP layer, UDP layer, Ethernet layer, and PDU layer. The application layer may include SIP (Session Initiation Protocol) and SDP (Session Description Protocol) used in IMS (IP Multimedia Subsystem), which is one of the service networks standardized by 3GPP. The application layer may include protocols such as RTP (Real-time Transport Protocol) used for media communication and/or RTCP (Real-time Transport Control Protocol) and HTTP (HyperText Transfer Protocol) for media communication control. . The application layer may also include codecs for various media. Also, the RRC layer may be a higher layer than the SDAP layer.

Next, the states and state transitions of UE 122 in NR will be explained.

For UE 122 connecting to 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 part or all of the UE context 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 the RRC_CONNECTED state, RRC_INACTIVE state, and RRC_IDLE state may be called RRC connected mode, RRC inactive mode, and RRC idle mode, respectively. If there is no fear, the RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE states may simply be called connected, inactive and idle modes, respectively.

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 the gNB 108 may include the same information as part or all of the information included in the UE AS context held by the UE 122 . Also, the UE AS context held by the gNB 108 may contain information different from the information contained in the UE AS context held by the UE 122 .

The security context consists of the cryptographic key at the AS level, the Next Hop parameter (NH), the Next Hop Chaining Counter parameter (NCC) used to derive the access key for the next hop, the identifier of the selected AS level cryptographic algorithm, and the replay protection. may contain information for some or all of the counters used for

A cell group that is set by the base station device for the terminal device will be explained. A cell group may consist of only one special cell (Special Cell: SpCell). Also, a cell group may consist of one SpCell and one or more secondary cells (SCells). That is, a cell group may consist of one SpCell and optionally one or more SCells. Note that when a MAC entity is associated with a Master Cell Group (MCG), SpCell may mean a Primary Cell (PCell). Also, when the MAC entity is associated with a Secondary Cell Group (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. A SpCell may support PUCCH transmission and contention-based Random Access. A SpCell may remain activated at all times. 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 (SN), which will be described later. The SpCell may also be a cell used for purposes other than the above. Note that when a cell group is composed of SpCells and one or more SCells, it can be said that carrier aggregation (CA) is configured in this cell group. Also, in a terminal device in which CA is configured, a cell that provides additional radio resources to SpCell may mean SCell.

When Dual Connectivity (DC) or Multi-Radio Dual Connectivity (MR-DC) is performed, a cell group may be added to the terminal device from the base station device. DC is a technique of performing data communication using radio resources of cell groups respectively configured by a first base station apparatus (first node) and a second base station apparatus (second node). good. MR-DC may be a technology involved in DC. In order to perform DC, the first base station device may additionally configure the second base station device for the terminal device. 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.

MR-DC may include DC using E-UTRA for MCG and NR for SCG. MR-DC may include DC using NR for MCG and E-UTRA for SCG. MR-DCs may include DCs with NR for both MCG and SCG. 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 an RRC message received by the terminal device from the base station apparatus. In EN-DC and NGEN-DC, the MAC entity for MCG may be the E-UTRA MAC entity. Also, the MAC entity for the SCG may be the NR MAC entity. In NE-DC, the MAC entity for MCG may be the NR MAC entity. Also, the MAC entity for the SCG may be an E-UTRA MAC entity. In NR-DC, MAC entities for MCG and SCG may both be NR MAC entities.

The existence of one MAC entity for each cell group can be rephrased as the existence of one MAC entity for each SpCell. Also, one MAC entity for each cell group may be rephrased as one MAC entity for each SpCell.

I will explain the radio bearer. 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 messages and for NAS messages before the establishment of SRB2. RRC messages sent and/or received using SRB1 may include piggybacked NAS messages. The DCCH of the logical channel may be used for RRC messages and NAS messages transmitted and/or received using SRB1.

SRB2 may be an SRB for NAS messages and for RRC messages containing logged measurement information. The DCCH of the logical channel may be used for RRC messages and NAS messages transmitted and/or received using SRB2. Also, SRB2 may be transmitted and/or received at a lower priority than SRB1.

SRB3 may be an SRB used to transmit and/or receive a specific RRC message when a DC such as EN-DC, NGEN-DC, NR-DC is configured in the terminal device. The DCCH of the logical channel may be used for RRC messages and NAS messages transmitted and/or received using SRB3.

Also, other SRBs may be prepared for other uses.

The DRB may be a radio bearer for user data. Logical channel DTCH may be used for RRC messages transmitted and/or received using DRB.

　The radio bearer in the terminal device will be explained. Radio bearers may include RLC bearers. Also, "include" of the RLC bearer in the radio bearer and "associate" of the RLC bearer with the radio bearer may be interchanged. 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 in all states (RRC idle state, RRC connected state and RRC inactive state).

One SRB1 may be established and/or set in the terminal device based on the RRC message 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 set in the terminal device by an RRC message 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.

The PDCP 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 a terminal device based on RRC messages 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 based on the RRC message 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 may 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. Further, when a plurality of RLC bearers associated with a certain radio bearer are configured in the terminal device, information indicating to which RLC bearer the primary path is configured is transmitted to the terminal device by an RRC message received from the base station device. The device may be notified. The RLC entity handling the RLC bearers of the primary path may be called the primary RLC entity.

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 bearer and/or MN-terminated split bearer. 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.

Note that in NR, a DRB established and/or configured in a terminal device may be associated with one PDU session. SDAP entities, PDCP entities, RLC entities, and logical channels established and/or configured in the terminal may be established and/or configured by RRC messages received by the terminal from the base station.

A network configuration in which the master node is gNB108 and 5GC110 is the core network can be called NR or NR/5GC. When MR-DC is not configured, the master node described above may refer to a base station apparatus that communicates with terminal apparatuses.

Next, handover in NR will be explained. A handover may be a process in which a UE 122 in RRC Connected state changes serving cells. Handover may occur when UE 122 receives an RRC message from gNB 108 indicating a handover. An RRC message that instructs handover is a message related to RRC connection reconfiguration that includes an information element that instructs handover (for example, mobility control information (MobilityControlInfo) in E-UTRA, or reconfiguration with synchronization (ReconfigurationWithSync) in NR). It can be Also, the RRC message instructing handover may be a message indicating movement to another RAT cell (for example, MobilityFromEUTRACommand or MobilityFromNRCommand). Also, handover can be rephrased as reconfiguration with sync. Also, the conditions under which UE 122 can perform handover include some or all of when AS security is activated, when SRB2 is established, and at least one DRB is established. you can

Note that the terminal device may perform processing that does not change the serving cell based on the RRC message instructing handover. That is, the terminal device may perform a handover process with the same cell as the current serving cell as the target cell.

Explain the flow of RRC messages that are transmitted and received between the terminal device and the base station device. FIG. 4 is a diagram showing an example flow of procedures for various settings in RRC according to the embodiment of the present invention. FIG. 4 is an example flow when an RRC message is sent from the base station apparatus (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 broadcast information (SI: System Information) and paging information. Also, the creation of the RRC message in the base station apparatus may be performed so that the base station apparatus 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 the RRC message transmitted from the terminal apparatus. The response to the RRC message sent from the terminal device may include, for example, a response to the RRC setup request, a response to the RRC reconnection request, a response to the RRC resume request, 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 ASN.1 (Abstract Syntax Notation One) notation scheme.

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

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

In MR-DC, RRC messages on the master node side are used to transfer RRC messages for SCG side settings (cell group settings, radio bearer settings, measurement settings, etc.) to and from the terminal equipment. may For example, in NR-DC, the master node side NR RRC message transmitted and received between the gNB 108 and the UE 122 may include the secondary node side NR RRC message in the form of a container. The information in the RRC message for the configuration on the SCG side included in the RRC message on the master node side may be sent and/or received between the master node and the secondary node.

An example of the parameters included in the RRC message regarding reconfiguration of the RRC connection will be explained. FIG. 7 is an example of ASN.1 description representing fields and/or information elements related to radio bearer setup included in the message related to RRC connection reconfiguration in NR in FIG. In the examples of ASN.1 in the embodiments of the present invention, <omitted> and <omitted> indicate that other information is omitted, not part of the ASN.1 notation. Information elements may be omitted even where there is no description of <omitted> or <omitted>. The example of ASN.1 in the embodiment of the present invention is an example of notation of the parameters of the RRC message in the embodiment of the present invention, and other names and other notations may be used. In addition, the ASN.1 example shows only examples of main information closely related to one aspect of the present invention in order to avoid complicating the explanation. Note that all parameters described in ASN.1 may be referred to as information elements without distinguishing between fields, information elements, and the like. The message regarding RRC connection reconfiguration may be an RRC reconfiguration message in NR or an RRC connection reconfiguration message in E-UTRA.

Explain the activation and deactivation of cells. In a terminal device that communicates with dual connectivity, a master cell group (MCG) and a secondary cell group (SCG) are set by the aforementioned message regarding RRC connection reconfiguration.

Cell deactivation does not apply to SpCells, but may apply to SCells. Alternatively, cell deactivation may 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 (A), (B), and/or (C) below.
(A) Receipt of MAC CE indicating SCell activation/deactivation (B) SCell inactivity timer set for each SCell for which PUCCH is not set (SCell is deactivated based on timer expiration) a)
(C) SCell state (sCellState) set for each SCell by an RRC message (SCell is activated based on the inclusion of the SCell state field in the SCell configuration)

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

(processing AD)
(1) If the RRC parameter (SCell state) is set to activated when the SCell is configured, or if a MAC CE that activates the SCell is received, the MAC entity of UE 122 processes (AD-1 )I do. Otherwise, if a MAC CE is received that deactivates the SCell, or if the SCell inactivity timer expires in an active SCell, the MAC entity of UE 122 takes action (AD-2).
(2) if an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of an active SCell, or if an uplink grant or downlink allocation for an active SCell is signaled by the PDCCH of a certain serving cell; Or, if a MAC PDU is sent in a configured uplink grant or if a MAC PDU is received in a configured downlink allocation, the MAC entity of UE 122 will send a SCell Disable associated with that SCell. Restart the liveness timer.
(3) If the SCell becomes inactive, the MAC entity of UE 122 performs processing (AD-3).

(Processing AD-1)
The MAC entity of the terminal device may perform some or all of (1) to (3) below.
(1) If, in NR, this SCell was in an inactive state before receiving a MAC CE that activates this SCell, or if the RRC parameters ( sCellState) is set to activated, the MAC entity of UE 122 performs processing (AD-1-1).
(2) UE 122's MAC entity starts or restarts (if already started) the SCell inactivity timer associated with that 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 UE 122's MAC entity (re)initializes it. and) the MAC entity of UE 122 triggers the PHR.

(Processing AD-1-1)
The MAC entity of the terminal device may perform some or all of (1) to (3) below.
(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 Dormant BWP, the MAC of UE 122 The 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 MAC of UE 122 The entity stops this serving cell's BWP-Inactivity Timer (bwp-InactivityTimer) if it is running.
(3) The MAC entity of UE 122 receives the downlink BWP indicated by the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the RRC message for that SCell and the first active uplink BWP identifier. Activate the uplink BWP indicated by (firstActiveUplinkBWP-Id).

(Processing AD-1-1-1)
The MAC entity of the terminal device may activate the SCell at predetermined timing and apply (execute) normal SCell operations including some or all of (A) to (E) below.
(A) Sounding Reference Signal (SRS) transmission for this SCell (B) Channel State Information (CSI) reporting for this SCell (C) PDCCH monitoring for this SCell (D) PDCCH monitoring for this SCell (etc.) (if scheduling for this SCell is done in the serving cell of
(E) If PUCCH is configured, PUCCH transmission on this SCell

(Processing AD-2)
The MAC entity of the terminal device may perform some or all of (A) to (D) below.
(A) Inactivate this SCell at a predetermined timing.
(B) Stop the SCell inactivity timer associated with this SCell.
(C) Deactivate all Active BWPs associated with this SCell.
(D) Flush the HARQ buffer associated with this SCell.

(Processing AD-3)
The MAC entity of the terminal device may perform 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, as described above, when an SCell is added, the initial state of the SCell may be set by an RRC message.

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 the RRC message. For example, when information indicating 40 ms is notified as the value of the SCell inactivity timer in the RRC message, the time notified without stopping the timer after starting or restarting the timer in the above process (AD) (here 40ms) has elapsed, the timer is considered expired. The SCell deactivation timer may also be a timer named sCellDeactivationTimer.

Explain the band part (BWP).

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 included in the broadcast 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.

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 parameters of the BWP of 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)  ( D) BWP bandwidth (for example, the number of PRBs), (E) control signal resource setting information, and (F) SS block center frequency position, may be included in part or all. 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. For the parameters (C) and (F) above, for the frequency position, for example, ARFCN may be used, or an offset from a specific subcarrier of the serving cell may be used. Also, the offset unit may be a subcarrier unit or a resource block unit. Also, both ARFCN and offset may be set.

A terminal device may transmit and/or receive in an active BWP (Active BWP) out of one or more set BWPs. Among one or more BWPs configured for one serving cell associated with the terminal device, at a given time, at most one uplink BWP and/or at most one downlink BWP, and May be set to be the active BWP. The activated downlink BWP is also called Active DL BWP. The activated uplink BWP is also called Active UL BWP.

Next, I will explain the inactivation of BWP. One or more BWPs may be configured in one serving cell. BWP switching in the serving cell is used to activate deactivated BWPs (also referred to as inactive BWPs) and deactivate activated BWPs.

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

Next, I will explain the Dormant BWP. Entering a dormant BWP or leaving a dormant BWP is performed by BWP switching. This control is performed by the PDCCH for each SCell or for each group called Dormancy SCell Group. Configuration of dormant SCell groups is indicated by RRC signaling. Dormant BWP may also be applied only to SCells. Note that a dormant BWP does not change a certain BWP to a dormant state, but may be interpreted as one BWP set for dormant use among one or more BWPs set for the UE. . Also, there may be a plurality of BWPs set in the UE for sleep use.

　A certain BWP is a dormant BWP may be indicated by not including a specific parameter in the BWP configuration. For example, by not including the PDCCH-Config information element, which is an information element for setting UE-specific (Specific) PDCCH parameters, included in the configuration of the downlink BWP, it is determined that the BWP is a dormant BWP. can be shown. Also, for example, some of the parameters included in the PDCCH-Config information element, which is an information element for configuring UE-specific PDCCH parameters included in the downlink BWP configuration, are not configured (not included). ) to indicate that the BWP is a dormant BWP. For example, some or all of the search space settings that define where and/or how to search for PDCCH candidates are configured by the PDCCH-Config information element as a BWP configuration. Not set (not included) may indicate that the BWP is a dormant BWP.

In addition, in certain settings, SpCells such as PCells and PSCells and settings of dormant BWPs for PUCCH SCells that can transmit PUCCH may not be supported.

A UE that has received a PDCCH indicating to exit from a dormant BWP outside a certain set period (active time) in SpCell uses the downlink BWP indicated by the first downlink BWP identifier notified in advance by RRC signaling. Activate.

A UE that has received a PDCCH in SpCell indicating that it will leave a dormant BWP within a certain set period (active time) uses the downlink BWP indicated by the second downlink BWP identifier notified in advance by RRC signaling. Activate.

A UE that receives a PDCCH indicating entry into a dormant BWP activates the downlink BWP indicated by the third downlink BWP identifier (dormantDownlinkBWP-Id) previously notified by RRC signaling.

Entry into and exit from the above-mentioned dormant BWP is performed by BWP switching, and when activating a new BWP, the previously active BWP is deactivated. That is, when exiting a dormant BWP, the dormant BWP is deactivated, and when entering a dormant BWP, the dormant BWP is activated.

Here, we will explain the PDCCH that indicates entering a dormant BWP and the PDCCH that indicates leaving a dormant BWP.

For example, a UE configured with discontinuous reception (DRX) in SpCell may monitor PDCCH in Active BWP of SpCell to detect a certain DCI format (e.g. DCI format 2_6) outside DRX active time. good. The DCI format CRC may be scrambled with a certain RNTI (eg PS-RNTI). A UE in which a dormant SCell group is set determines switching of Active DL BWP based on the bitmap information included in the DCI format 2_6 payload. For example, if a bit in the bitmap is associated with one dormant SCell group and the bit is 1, if the Active DL BWP is a dormant BWP, perform a BWP switch to another preset BWP, If an Active DL BWP is not a dormant BWP, it may stay on that BWP. A BWP switch may also be performed such that if the bit is 0, the Active DL BWP becomes the Dormant BWP.

　UE does not have to monitor PDCCH for the purpose of detecting DCI format 2_6 during DRX active time.

A UE configured for discontinuous reception (DRX) in SpCell may monitor PDCCH in Active BWP of SpCell to detect certain DCI formats (for example, DCI formats 0_1 and 1_1) during DRX active time. The DCI format CRC may be scrambled with an RNTI (eg, C-RNTI or MCS-C-RNTI). A UE in which a dormant SCell group is set determines switching of Active DL BWP based on the bitmap information included in the payload of DCI format 0_1 or DCI format 1_1. For example, if a bit in the bitmap is associated with one dormant SCell group and the bit is 1, if the Active DL BWP is a dormant BWP, perform a BWP switch to another preset BWP, If an Active DL BWP is not a dormant BWP, it may stay on that BWP. A BWP switch may also be performed such that if the bit is 0, the Active DL BWP becomes the Dormant BWP. Also, the "another preset BWP" may be a BWP different from the "another preset BWP" used in the description of the DCI format 2_6.

The UE does not have to monitor PDCCH for the purpose of detecting DCI format 0_1 and DCI format 1_1 outside the DRX active time.

Monitoring the PDCCH indicating exiting the dormant BWP means monitoring the PDCCH for detection of DCI format 2_6 outside the DRX active time, and DCI format 0_1 and DCI format 1_1 during the DRX active time. monitoring of the PDCCH for the purpose of detecting

For each activated serving cell with a BWP configured, the MAC entity shall, if the BWP is activated (is an Active BWP) and that BWP is not a dormant BWP, any of (A) through (H) below: Or you can do it all.
(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) Initialize configured uplink grants of grant type 1 that have been set and suspended in that BWP.

For each activated serving cell with a BWP configured, the MAC entity shall, if the BWP is activated (is an Active BWP) and that BWP is a dormant BWP, one of (A) through (G) below: You can do part or all.
(A) Stop the BWP inactivity timer for the serving cell of this BWP if it is running.
(B) Do not monitor PDCCH for that BWP.
(C) Do not monitor the PDCCH for that BWP.
(D) Do not receive DL-SCH on that BWP.
(F) Do not send SRS on that BWP.
(G) Do not transmit UL-SCH on that BWP.
(H) Do not send RACH on that BWP.
(I) Do not transmit PUCCH on that BWP.
(J) Clear the Configured Downlink Assignments and Configured Uplink Grants of Grant Type 2 associated with that SCell, respectively.
(K) Suspend the configured uplink grant of grant type 1 associated with that SCell.
(L) Detect Beam Failure if settings for beam failure are set, and perform Beam Failure Recovery if beam failure is detected.

The MAC entity may do some or all of (A) through (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 the configured uplink grant of grant type 2 set in that BWP.
(I) Suspend the configured uplink grant of grant type 1 for that deactivated BWP (inactive BWP).

Next, a random access procedure in the UE with BWP set will be described. When initiating a random access procedure in a serving cell, the MAC entity may perform some or all of the following (A) through (E) on selected carriers of this serving cell.
(A) If the PRACH transmission resource (occasion) is not set for the Active UL BWP, (A1) switch the Active UL BWP to the BWP indicated by the RRC parameter (initialUplinkBWP), and (A2) If the serving cell is a SpCell, switch the Active UL BWP to the BWP indicated by the RRC parameter initialDownlinkBWP.
(B) If the resource (occasion) for transmitting PRACH is configured for Active UL BWP, if the serving cell is SpCell and Active DL BWP and Active UL BWP have the same identifier (bwp-Id) If not, switch the Active DL BWP to a BWP with the same identifier as the Active UL BWP.
(C) If the BWP inactivity timer associated with this serving cell's Active DL BWP is running, stop this timer.
(D) If the serving cell is a SCell, stop the BWP inactivity timer associated with the SpCell's Active DL BWP if it is running.
(E) Execute a random access procedure on the SpCell's Active DL BWP and this serving cell's Active UL BWP.

Next, the BWP inactivity timer will be described. The MAC entity performs the following processing (A) for each activated serving cell for which the BWP inactivity timer is set. The BWP inactivity timer may also be a timer named bwp-InactivityTimer.
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), or if the default downlink BWP identifier (defaultDownlinkBWP- Id) is not set, the Active DL BWP is not the initialDownlinkBWP, and the Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), then the MAC entity follows (A-1) and (A-2) process.
(A-1) if, in Active DL BWP, received PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant, or if for Active DL BWP received a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant, or if a MAC PDU was sent with a configured uplink grant, or If a MAC PDU is received with configured downlink allocation, the MAC entity performs the following (A-1-1) processing.
(A-1-1) If the random access procedure associated with this serving cell is not in progress, or if the random access procedure in progress associated with this serving cell is received by the PDCCH addressed to the C-RNTI Once successfully completed, start or restart the BWP inactivity timer associated with the Active DL BWP.
(A-2) If the BWP inactivity timer associated with the Active DL BWP expires (Expire), the MAC entity performs the following processing (A-2-1).
(A-2-1) If defaultDownlinkBWP-Id is set, BWP switching is performed to BWP indicated by this defaultDownlinkBWP-Id, otherwise BWP switching is performed to initialDownlinkBWP.

Also, if the MAC entity receives the PDCCH for BWP switching and switches the Active DL BWP, it may perform the following processing (A).
(A) If the default downlink BWP identifier (defaultDownlinkBWP-Id) is set, the switched Active DL BWP is not the BWP indicated by the identifier (dormantDownlinkBWP-Id), and if the switched Active DL BWP is dormantDownlinkBWP- If not the BWP indicated by Id, start or restart the BWP inactivity timer associated with the Active DL BWP.

The SCell's dormancy is achieved by activating the dormant BWP in this SCell. Also, even when the SCell is in a dormant state, CSI measurement, automatic gain control (AGC), and beam control (beam management) including beam failure recovery may be performed in this SCell.

Next, we will explain how to add an SCG PSCell and zero or more SCells to a terminal device.

The addition of PSCells and 0 or more SCells of the SCG may be performed by RRC messages regarding reconfiguration of RRC connections. Figures 8 to 12 are examples of ASN.1 descriptions representing fields and/or information elements related to the addition of SCG PSCells and zero or more SCells, which are included in messages related to RRC connection reconfiguration in NR. .

To avoid complicating the explanation, the messages and/or information elements in each figure differ from the actual message structure and/or information element structure, and some structured fields and information elements are expanded. and/or omit fields or information elements not directly relevant to the description.

As shown in FIG. 8, an RRC reconfiguration message (RRCReconfiguration message) may be used to add a PSCell of an SCG and zero or more SCells. The RRC reconfiguration message may include some or all of the information (A) to (E) below. Also, the RRC reconfiguration message may include other information.
(A) RRC transaction identifier (rrc-TransactionIdentifier)
(B) Settings for adding, modifying, and releasing radio bearers (radioBearerConfig)
(C) Secondary cell group setting (secondaryCellGroup)
(D) Setting the master cell group (masterCellGroup)
(E) RRC configuration of secondary cell group in MR-DC (mrdc-SecondaryCellGroupConfig)

When the RRC reconfiguration message is notified to the terminal device in SRB3, the SCG setting may be notified by the above (C) setting of the RRCReconfiguration message generated by the secondary node. Also, when the RRC reconfiguration message is notified to the terminal device in SRB1, the SCG setting is such that the RRC reconfiguration message generated by the secondary node is added to the above (E) of the RRCReconfiguration message generated by the master node. May be included and notified. Also, other messages may be used for setting up the SCG.

The configuration of the above secondary cell group may be given in a cell group configuration information element (CellGroupConfigIE). As shown in FIG. 9, the cell group setting information element may include some or all of the following information (A) to (H). Also, the cell group setting information element may contain other information.
(A) Cell group identifier (cellGroupId)
(B) Settings for adding and/or modifying RLC bearers (rlc-BearerToAddModList)
(C) Setting for RLC bearer release (rlc-BearerToReleaseList)
(D) MAC configuration for this cell group (mac-CellGroupConfig)
(E) PHY configuration for this cell group (physicalCellGroupConfig)
(F) SpCell configuration (spCellConfig)
(G) Settings for adding and modifying SCells (sCellToAddModList)
(H) Setting for SCell release (sCellToReleaseList)

SpCells may be added and/or set by the SpCell settings in (F) above, and SCells may be added, modified, and/or released by the settings in (G) and (H) above. They may also be done by other messages.

As shown in FIG. 10, the above SpCell settings may include some or all of the following information (A) to (D). The SpCell configuration may also include other information.
(A) Index (servCellIndex) for identifying serving cells
(B) ReconfigurationWithSync
(C) Timer value and constant information (rlf-TimersAndConstants) used for determining radio link failure, etc.
(D) SpCell terminal device specific parameter setting (spCellConfigDedicated)

As shown in FIG. 11, the above information element of reset with synchronization may include some or all of the following information (A) to (D). Further, the reset information with synchronization may include other information.
(A) SpCell cell-specific parameter configuration (spCellConfigCommon)
(B) New terminal identifier (UE-Identity) value (newUE-Identity)
(C) Timer T304 value (t304)
(D) RACH terminal device specific parameter setting (rach-ConfigDedicated)

The setting of the RACH terminal device-specific parameters described above may include parameters (CFRA) used for contention-free random access. Note that if this CFRA is not included in the configuration, the terminal device may perform contention-based random access in a random access procedure. CFRA may include RA Occasion information used in collision-free random access.

The configuration of cell-specific parameters of the SpCell above may be given by an information element (ServingCellConfigCommon IE) used to configure the cell-specific parameters of the serving cell. Information elements used to configure cell-specific parameters of the serving cell may include some or all of the following information (A) to (D), as shown in FIG. Other information may also be included in the information element used to configure cell-specific parameters for the serving cell.
(A) Physical cell identifier (physCellId)
(B) Common downlink parameters in cells (downlinkConfigCommon)
(C) Common uplink parameters in cells (uplinkConfigCommon)
(D) Configuration of SCell terminal device-specific parameters (including some cell-specific parameters) (sCellConfigDedicated)
(E) SSB subcarrier spacing information (ssbSubcarrierSpacing)

Downlink common parameters in a cell may include downlink frequency information (frequencyInfoDL) and/or initial downlink BWP information (initialDownlinkBWP). The downlink frequency information may include information on the SSB frequency used in this serving cell.

The configuration for adding and modifying the above SCells may be given by one or more SCell configuration information elements (SCellConfigIE). As shown in FIG. 13, the SCell configuration information element may include some or all of the following information (A) to (D). Also, the SCell configuration information element may include other information.
(A) Identifier for identifying SCell (sCellIndex)
(B) SCell cell-specific parameter configuration (sCellConfigCommon)
(C) Configuration of SCell terminal device-specific parameters (including some cell-specific parameters) (sCellConfigDedicated)
(D) Information indicating SCell activation/deactivation (sCellState-r16)

As an example, the procedure for adding an SCG PSCell and 0 or more SCells using the above RRC message and information elements will be explained. Note that the RRC messages and information elements used in the description are examples, and the names and structures when implemented are not limited to these.

The RRC entity of the terminal device that has received the RRCReconfiguration message may perform some or all of (A) to (F) below. A terminal device that receives the RRCReconfiguration message may perform other processing.
(A) If masterCellGroup is included in RRCReconfiguration, process (BD-1) is executed for the master cell group based on this masterCellGroup.
(B) If secondaryCellGroup is included in RRCReconfiguration, the process (BD-1) is executed for the secondary cell group based on this secondaryCellGroup.
(C) If radioBearerConfig is included in RRCReconfiguration, configure radio bearers based on this radioBearerConfig.
(D) Set the content to be included in the RRC reconfiguration complete message.
(E) If reconfigurationWithSync is included in the SpCell configuration (spCellConfig) of the received secondary cell group configuration, the random access procedure is started in that SpCell.
(F) If reconfigurationWithSync is included in the MCG or SCG SpCell configuration (spCellConfig) and the random access procedure is successfully completed in the NR cell group, timer T304 of that cell group is stopped.

(Processing BD-1)
The RRC entity of the terminal device may perform some or all of (A) to (G) below.
(A) If CellGroupConfig includes spCellConfig including reconfigurationWithSync, the RRC entity of the terminal device performs some or all of (1) to (3) below.
(1) Execute processing (BD-2).
(2) Resume all suspended radio bearers.
(3) Resume SCG transmission for all radio bearers if suspended.
(B) If rlc-BearerToReleaseList is included in CellGroupConfig, release the RLC bearer based on this rlc-BearerToReleaseList.
(C) If the CellGroupConfig contains rlc-BearerToAddModList, perform RLC bearer addition and/or modification based on this rlc-BearerToAddModList.
(D) If CellGroupConfig contains mac-CellGroupConfig, configure the MAC entity of this cell group based on this mac-CellGroupConfig.
(E) If sCellToReleaseList is included in CellGroupConfig, release the SCell based on this sCellToReleaseList.
(F) If spCellConfig is included in CellGroupConfig, set SpCell based on this spCellConfig.
(G) If CellGroupConfig contains sCellToAddModList, then perform SCell addition and/or modification based on this sCellToAddModList.

(Processing BD-2)
The RRC entity of the terminal device may perform some or all of (A) to (G) below.
(A) If AS security is not activated, execute processing to transition to RRC_IDLE and terminate the procedure.
(B) Start timer T304 for the SpCell (to be configured) using the value of t304 included in reconfigurationWithSync.
(C) If downlink frequency information (frequencyInfoDL) is included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync in the SSB frequency indicated by frequencyInfoDL is the target SpCell. I judge.
(D) If downlink frequency information (frequencyInfoDL) is not included in reconfigurationWithSync, the cell indicated by the physical cell identifier (physCellId) included in reconfigurationWithSync in the SSB frequency of the original SpCell (Source SpCell), Determine that it is the target SpCell.
(E) Start downlink synchronization of the target SpCell.
(F) Acquire the MIB of the target SpCell.
(G) If no specific bearer (DAPS bearer) has been configured. Execute some or all of (1) to (4) below.
(1) reset the MAC entity for this cell group;
(2) If a SCell not included in SCellToAddModList is set in this cell group, this SCell is made inactive.
(3) apply the value of newUE-Identity as the C-RNTI for this cell group;
(4) Configure lower layers based on the received spCellConfigCommon.

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

In NR, the state in which the SCG is deactivated (SCG inactive state) may be included as part of the RRC_CONNECTED state.

In NR, the state in which the SCG is deactivated (SCG inactive state) means that the terminal device performs the following (A) to (J) in all cells of the SCG SpCell (PSCell) and / or the SCG may be in a state of implementing part or all of Also, in a state in which an SCG is deactivated, all SCells configured for terminals in that SCG may be deactivated.
(A) Do not transmit SRS in that cell.
(B) Do not report CSI for that cell.
(C) do not transmit PUCCH, UL-SCH, and/or RACH on that cell;
(D) Do not monitor the PDCCH for that cell and/or the PDCCH for that cell.
(E) the cell's PDCCH addressed to the C-RNTI, MCS-C-RNTI, and/or CS-RNTI indicating an uplink grant for UL-SCH transmission in that cell, and/or that cell; Do not monitor PDCCH for
(F) No Automatic Gain Control (AGC) in the cell.
(G) Do not perform beam management, including beam failure recovery, in that cell.
(H) Do not perform Radio Link Monitoring (RLM) in that cell.
(I) Make the BWP set to the dormant BWP in the cell the activated BWP (also referred to as the Active BWP).
(J) Do not monitor C-RNTI on PDCCH in the activated dormant BWP of that cell.

　In addition, entering the SCG inactive state may be referred to as entering an inactivated SCG. Also, the SCG inactive state may be a state in which the active BWPs of all cells of the SCG are dormant BWPs. In addition, the above-mentioned SCG inactive state transitions from the SCG activated state (SCG active state) described later when an RRC entity or another entity instructs to enter the deactivated SCG may be in a state where

In NR, the SCG activated state (SCG active state) may be included as part of the RRC_CONNECTED state.

In NR, the state in which the SCG is activated (SCG active state) means that the terminal device performs the following (A) to (J) in the SpCell (PSCell) of the SCG and/or any cell of the SCG It may be in a state in which part or all of it is implemented.
(A) transmit SRS in that cell;
(B) Report the CSI for that cell.
(C) transmit PUCCH, UL-SCH and/or RACH on that cell;
(D) monitor the PDCCH for that cell and/or the PDCCH for that cell;
(E) the cell's PDCCH addressed to the C-RNTI, MCS-C-RNTI, and/or CS-RNTI indicating an uplink grant for UL-SCH transmission in that cell, and/or that cell; monitor the PDCCH for
(F) Perform Automatic Gain Control (AGC) on the cell.
(G) Perform beam management, including beam failure recovery, in that cell.
(H) perform radio link monitoring (RLM) in the cell;
(I) In that cell, the BWP set to the dormant BWP is not set to the activated BWP (Active BWP).
(J) Monitor the C-RNTI on the PDCCH in the activated BWP of that cell.

Also, entering the SCG active state may be called entering the activated SCG. Also, the SCG active state may be a state in which the SCG SpCell and/or one or more SCell Active BWPs are not dormant BWPs. In addition, the above-mentioned SCG inactive state is a state in which the SCG is inactivated (SCG inactive state ) may be a transition state.

In NR, the terminal device may transition the SCG to the inactive state based on receiving some or all of the following information (A) to (B) (in other words, the SCG is inactive may be changed). Note that the message and control elements including the information may be notified from the SCG to the terminal device, or may be notified to the terminal device from a cell group other than the SCG. Also, the information may be notified to the terminal device by an RRC message, MAC control element, or physical control channel.
(A) Information instructing SCG inactivation (B) Information instructing SpCell inactivation

Also, the terminal device may transition the SCG from the active state to the inactive state based on the timer for deactivating the SCG. Also, the terminal device may transition the SCG from the active state to the inactive state based on a timer related to PSCell deactivation.

In NR, the terminal device may transition the SCG from the inactive state to the active state based on receiving some or all of the following (A) to (D) information (in other words, the SCG may be activated). Note that a message or control element including the above information may be notified to the terminal device from a cell group other than the SCG. Also, the above information may be notified to the terminal device using an RRC message, MAC control element, or physical control channel.
(A) Information instructing activation of SCG (B) Information instructing to resume from inactive state of SCG (C) Information instructing activation of SpCell (D) Inactivated state of SpCell information to restart from

Also, the terminal device may cause the SCG to transition from the inactive state to the active state based on the timer for deactivating the SCG. Also, the terminal device may transition the SCG from the inactive state to the active state based on a timer related to PSCell deactivation.

Also, the terminal device may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request triggered to transmit a MAC PDU containing a MAC SDU. Also, the terminal device may transition the SCG from the inactive state to the active state when starting the random access procedure.

Also, the terminal device may transition the SCG from the inactive state to the active state when starting a random access procedure caused by a scheduling request (in other words, initiated by the MAC entity itself). In addition, the MAC entity of the terminal device sends an instruction to activate the SCG, an instruction to resume the deactivated SCG, an instruction to resume SpCell from dormancy, and/or other information to the RRC entity of the terminal device, It may be obtained from the PHY entity and/or other MAC entities.

It should be noted that the deactivation of the SCG may be the activation of a specific BWP (for example, dormant BWP) of SpCells in the cell group. Inactivation of SCG may also be referred to as SCG dormant or SCG suspension.

All uplink transmissions may be paused (suspended) in the SCG when the SCG is in a deactivated state. In this case, information about that SCG may be sent in another cell group (eg, MCG). Alternatively, the information about that SCG may be sent in that SCG that has left the deactivated state (activated SCG). Also, when the SCG is in a deactivated state, some or all of the radio bearers associated with the RLC bearers of the SCG may be paused (suspended).

The random access procedure in the SpCell (PSCell) may be initiated in the deactivated SCG by triggering a scheduling request by the MAC entity to send a MAC PDU containing the MAC CE or directly by the MAC entity. good too. At this time, the MAC PDU may not contain the MAC SDU.

On the other hand, the SCG in which the random access procedure in the SpCell (PSCell) is deactivated by triggering a scheduling request to transmit a MAC PDU containing data (MAC SDU) from higher layers such as user data and RRC messages. may be started at

Resuming the SCG from an inactivated state (activating the SCG) may be referred to as leaving the dormant SCG. Also, resuming from the inactivated state of the SCG may be BWP switching from a dormant BWP to another (non-dormant BWP) BWP in the SpCell of the cell group.

In addition, the resumption of SCG from an inactivated state may be referred to as SCG activation or SCG re-activation.

A terminal device that performs SCG deactivation may perform some or all of the following processes (A) to (F) in the SCG.
(A) All SCells are inactivated.
(B) Assume that all of the SCell inactivity timers associated with the active SCell have expired.
(C) Assume that all SCell inactivity timers associated with the dormant SCell have expired.
(D) Do not start or restart the SCell inactivity timers associated with all SCells.
(E) Ignore MAC CEs that activate SCells. For example, in the processing (AD), if MAC CE for activating SCell is received and SCG deactivation is not instructed (or SCG is not deactivated), processing ( AD-1) is performed.
(F) Execute the above process (AD-2). For example, when inactivation of SCG is instructed (or SCG is inactivated) in the processing (AD-2), processing (AD-2) is performed.

A terminal device that resumes an SCG from an inactivated state may perform some or all of the following (A) to (D) processes in the SCG.
(A) Execute processing (AD-1) to activate all SCells.
(B) Leave all SCells inactive. However, since it is not in an inactivated state, for example, in the processing (AD), when a MAC CE for activating SCell is received, deactivation of SCG is not instructed (or SCG is inactivated is not in the state of being completed), processing (AD-1) may be performed.
(C) When performing resumption from the SCG deactivated state based on the RRC message, if this RRC message contains parameters related to random access to some or all SCells, the notified parameters Based on this, a random access procedure is initiated in the target SCell.
(D) When resuming the SCG from a deactivated state based on an RRC message, if this RRC message contains information specifying the state of the SCell, set the state of each SCell to the active state. based on that information.

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) according to the embodiment of the present invention. In order to avoid complicating the description, FIG. 5 shows only main components closely related to one embodiment of the present invention.

UE 122 shown in FIG. 5 includes a receiving unit 500 that receives an RRC message or the like from a base station device, a processing unit 502 that performs processing according to parameters included in the received message, and a transmitting unit that transmits the RRC message or the like to the base station device. consists of 504. The base station apparatus described above may be the 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 layer processing unit, RRC layer processing unit, and NAS layer processing unit. can be

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

The base station apparatus shown in FIG. 6 includes a transmission unit 600 that transmits an RRC message and the like to UE 122, and a processing unit that creates an RRC message including parameters and transmits it to UE 122, thereby allowing processing unit 502 of UE 122 to perform processing. 602 and a receiver 604 that receives RRC messages and the like 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 layer processing unit, RRC layer processing unit, and NAS layer processing unit. can be

Various examples of processing of the terminal device according to the embodiment of the present invention will be described below.

FIG. 14 is a diagram showing an example of processing of the terminal device (UE 122) according to the embodiment of the present invention.

In the process of FIG. 14, the transmitting SDAP entity of the terminal device receives the first SDAP SDU for the first QoS flow from the SDAP upper layer of the terminal device (step S1400).

The transmitting SDAP entity of the terminal device maps the SDAP SDU to the default DRB if there is no rule for the first QoS flow in the QoS flow-DRB mapping rules it retains (step S1402 ). Note that a maximum of one default DRB for a PDU session may be set in the terminal device by the configuration (radioBearerConfig) for adding, modifying, and/or releasing radio bearers included in the RRC reconfiguration message.

If a rule for the first QoS flow exists in the QoS flow-DRB mapping rule held by the transmitting SDAP entity of the terminal device, the SDAP SDU is mapped to the first QoS flow according to the rule. is mapped to the DRB associated with (step S1404).

The transmitting SDAP entity of the terminal device constructs an uplink SDAP data PDU using the first SDAP SDU (step S1406).

The SDAP entity of the terminal device notifies the RRC layer of the terminal device or the The upper layer is notified (step S1408).

The SDAP entity of the terminal device sends the constructed SDAP data PDU to a lower layer of the SDAP of the terminal device (such as the PDCP layer or the RLC layer) based on the fact that the DRB to which the SDAP SDU is mapped does not satisfy the first condition. (step S1410).

The first condition may be any one of the following conditions (A) to (H) or a combination thereof.
(A) the DRB and/or transmission of the DRB is suspended (B) the DRB is a deactivated cell group (e.g. SCG) bearer (C) the DRB and/or the DRB is suspended based on the cell group (e.g. SCG) being deactivated (D) the DRB is associated with the RLC bearer of the deactivated cell group (e.g. SCG) (E) transmission on the cell group of the RLC bearer associated with that DRB is suspended; (F) if multiple RLC entities are associated with that DRB, the primary RLC entity is deactivated; (G) If more than one RLC bearer is associated with that DRB, the DRB's primary path is set to a deactivated cell group (e.g. SCG) (H) If multiple RLC bearers are associated with that DRB, the primary path of that DRB is set to a cell group whose transmission is suspended (e.g. SCG)

The entity of the RRC layer of the terminal device or the upper layer of SDAP, which was notified of the arrival of the uplink data in step S1408, performs processing to activate the deactivated cell group. For example, the RRC entity notified of the arrival of uplink data is provided with information requesting activation of the deactivated cell group (and/or indicating that uplink data has occurred in the deactivated cell group information) may be transmitted to the base station apparatus, for example, using the MCG signaling radio bearer. Also, for example, the RRC layer of the terminal device that has been notified of the arrival of uplink data may initiate a procedure for activating a deactivated cell group. Also, for example, an SDAP higher layer entity of the terminal device that has been notified of the arrival of uplink data may instruct the RRC layer to start the cell group activation procedure. Also, for example, the RRC layer of the terminal device, which has been notified of the arrival of uplink data, may instruct the MAC layer to initiate a random access procedure in a cell of the deactivated cell group.

Further, the processing of the entity notified of the arrival of uplink data in step S1408 is, for example, based on the information regarding the possibility of autonomous activation of the cell group notified (set) from the base station device, which processing is performed. It may be decided whether to do so.

In addition, in step S1408, the SDAP entity that has notified the RRC layer of the terminal device or the upper layer of SDAP that the uplink data for this DRB has arrived indicates that the DRB to which the SDAP SDU is mapped meets the first condition. is not satisfied, the constructed SDAP data PDU may be submitted to the SDAP lower layer of the terminal device (e.g. PDCP layer or RLC layer), regardless of whether the first condition is satisfied. Instead, the constructed SDAP data PDU may be submitted to the SDAP lower layer (eg PDCP layer or RLC layer) of the terminal device.

Also, "the arrival of uplink data for this DRB" in step S1408 may be other information. For example, "that uplink data for this DRB has arrived" may be any of the following information (A) to (D), a combination thereof, or information other than this: .
(A) Arrival of uplink data in a cell group whose transmission is suspended (B) Arrival of uplink data for a suspended radio bearer (C) Activation of a deactivated cell group is required (D) Uplink data cannot be transmitted to this DRB

As a result, it is possible to efficiently perform uplink transmission of the radio bearer associated with the cell group in which the terminal device is deactivated.

FIG. 15 is a diagram showing an example of processing of the terminal device (UE 122) according to the embodiment of the present invention.

In the process of FIG. 15, the transmitting PDCP entity of the terminal device receives the PDCP SDU from the higher layer of PDCP of the terminal device (step S1500).

The transmitting PDCP entity of the terminal device may perform header compression, encryption, and/or integrity protection of PDCP SDUs as necessary (step S1502).

The transmitting PDCP entity of the terminal device detects that uplink data for this radio bearer has arrived based on the fact that the radio bearer associated with this transmitting PDCP entity satisfies a first condition to be described later. is notified to the upper layer (for example, RRC) (step S1504).

The transmitting PDCP entity of the terminal device transmits the PDCP PDU constructed based on the PDCP SDU to the RLC entity of the terminal device based on the fact that the radio bearer associated with this transmitting PDCP entity does not satisfy the first condition described later. Submit (step S1506).

The first condition may be any one of the following conditions (A) to (H) or a combination thereof.
(A) the radio bearer and/or transmission of the radio bearer is suspended (B) the radio bearer is a bearer of a deactivated cell group (eg SCG) (C) the radio bearer, and /or the transmission of that radio bearer is suspended based on the cell group (e.g. SCG) being deactivated (D) the radio bearer is the RLC bearer of the deactivated cell group (e.g. SCG) (E) transmission in the cell group of the RLC bearer associated with that radio bearer is suspended (F) if multiple RLC entities are associated with that radio bearer, Primary RLC entity is in a deactivated cell group (e.g. SCG) (G) If multiple RLC bearers are associated with that radio bearer, the cell whose primary path for that radio bearer is deactivated set to a group (e.g. SCG) (H) If multiple RLC bearers are associated with that radio bearer, the primary path of that radio bearer is set to a cell group (e.g. SCG) whose transmission is suspended. ing

The entity of the PDCP upper layer (for example, the RRC layer) of the terminal device that was notified of the arrival of the uplink data in step S1504 performs processing to activate the inactivated cell group. For example, the RRC entity notified of the arrival of uplink data is provided with information requesting activation of the deactivated cell group (and/or indicating that uplink data has occurred in the deactivated cell group information) may be transmitted to the base station apparatus, for example, using the MCG signaling radio bearer. Also, for example, an entity in a PDCP higher layer (for example, the RRC layer) of the terminal device that is notified of the arrival of uplink data may initiate a cell group activation procedure. Also, for example, an entity in a higher layer of PDCP (eg, RRC layer) of the terminal device that is notified of the arrival of uplink data instructs the MAC layer to start a random access procedure in the deactivated cell group. may

Further, the processing of the entity notified of the arrival of the uplink data in step S1504 is, for example, based on the information regarding the possibility of autonomous activation of the cell group notified (set) from the base station device, which processing is performed. It may be decided whether to do so.

Note that, in step S1504, the PDCP entity that has notified the upper layer of PDCP (eg, RRC) of the terminal device that the uplink data for this DRB has arrived is the radio bearer associated with this PDCP entity. The constructed PDCP PDU may be submitted to the RLC entity of the terminal device based on the fact that the first condition is not satisfied, or the constructed PDCP PDU may be submitted to the terminal device regardless of whether the first condition is satisfied may be submitted to any RLC entity.

Also, "the arrival of uplink data for this radio bearer" in step S1504 may be other information. For example, ``that uplink data for this radio bearer has arrived'' may be any of the following information (A) to (D), or a combination thereof, or information other than this: good.
(A) Arrival of uplink data in a cell group whose transmission is suspended (B) Arrival of uplink data for a suspended radio bearer (C) Activation of a deactivated cell group is required (D) Uplink data cannot be transmitted to this DRB

As a result, it is possible to efficiently perform uplink transmission of the radio bearer associated with the cell group in which the terminal device is deactivated.

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

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

The "dormant state" in the above description may be replaced with the "inactive state", and the "state resumed 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".

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.

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" may include "D may be E". Further, 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.

Various aspects of the terminal device and method in the embodiments of the present invention will be described below.

(1) A first embodiment of the present invention is a terminal device in which a secondary cell group is set from a base station device, and a data radio bearer ( a SDAP layer processing unit that notifies a radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived based on the DRB) satisfying a first condition; and based on the notification, the secondary cell The RRC layer processing unit generates an RRC message for group activation, and a transmission unit transmits the RRC message to the base station apparatus, wherein the first condition is that the data radio bearer is Suspended due to inactivation of the cell group.

(2) A second embodiment of the present invention is a method applied to a terminal device to which a secondary cell group has been set from a base station device, in which a service data adaptation protocol service data unit (SDAP SDU) is mapped. a step of notifying a radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived based on the data radio bearer (DRB) satisfying a first condition; generating an RRC message for activation of a secondary cell group; and transmitting the RRC message to the base station apparatus, wherein the first condition is that the data radio bearer is activated by the secondary cell group. It is suspended due to being deactivated.

(3) A third embodiment of the present invention is an integrated circuit implemented in a terminal device to which a secondary cell group has been set from a base station device, in which a service data adaptation protocol service data unit (SDAP SDU) is mapped. A function of notifying a radio resource control (RRC) layer processing unit that uplink data for the DRB has arrived based on the fact that the data radio bearer (DRB) received satisfies a first condition, and based on the notification, causing the terminal device to exhibit a function of generating an RRC message for activation of the secondary cell group and a function of transmitting the RRC message to the base station device; is suspended due to the secondary cell group being deactivated.

A program that runs on a device according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the above-described embodiments according to one aspect of the present invention. There may be. 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, a 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 in 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.

Furthermore, "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. , such as a volatile memory inside a computer system serving as a server or a client in that case, which holds the program for a certain period of time. Further, the program may be for realizing 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.

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

Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are included within the scope of the present invention. Further, one aspect of the present invention can be modified in various ways within the scope of the claims, and an embodiment obtained by appropriately combining technical means disclosed in different embodiments can also be Included in the scope. 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.

106NR
108 gNB
110 5GC
116 interfaces
122 UEs
300 PHYs
302 MAC
304 RLC
306 PDCP
308 RRC
310 SDAP
312 NAS
500, 604 receiver
502, 602 processor
504, 600 transmitter

Claims (3)

1. A terminal device in which a secondary cell group is set from a base station device,
   A data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is the DRB of the secondary cell group, and based on the fact that the secondary cell group is deactivated, to the DRB a PDCP layer processing unit that notifies a radio resource control (RRC) layer processing unit that uplink data has arrived;
   the RRC layer processing unit that generates an RRC message that notifies the base station device that uplink data to be transmitted is in the secondary cell group based on the notification;
   A terminal device, comprising: a transmission unit that transmits the RRC message to the base station device.
2. A method applied to a terminal device in which a secondary cell group is set from a base station device,
   A data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is the DRB of the secondary cell group, and based on the fact that the secondary cell group is deactivated, to the DRB notifying a radio resource control (RRC) layer processor that uplink data has arrived;
   generating an RRC message for notifying the base station apparatus that uplink data to be transmitted is in the secondary cell group based on the notification;
   and transmitting the RRC message to the base station apparatus.
3. An integrated circuit mounted in a terminal device in which a secondary cell group is set from a base station device,
   A data radio bearer (DRB) associated with a packet data convergence protocol (PDCP) entity is the DRB of the secondary cell group, and based on the fact that the secondary cell group is deactivated, to the DRB A function of notifying a radio resource control (RRC) layer processing unit that uplink data has arrived;
   A function of generating an RRC message for notifying the base station apparatus that uplink data to be transmitted is in the secondary cell group based on the notification;
   An integrated circuit that causes the terminal device to exhibit a function of transmitting the RRC message to the base station device.

Images