KR20230127608A - Method and Apparatus for activating or deactivating a SCG in wireless communication system - Google Patents

Abstract

The present invention relates to a method and a device for activating or deactivating a secondary cell group in a wireless mobile communication system. The method comprises the steps of: transmitting an SGNB addition request message; receiving an SGNB addition request acknowledge message; and transmitting an LTE RRC connection reconfiguration message.

Description

Method and apparatus for activating or deactivating a secondary cell group in a wireless mobile communication system {Method and Apparatus for activating or deactivating a SCG in wireless communication system}

The present disclosure relates to a method and apparatus for activating or deactivating a secondary cell group in a wireless mobile communication system.

In order to meet the growing demand for wireless data traffic after the commercialization of 4G communication systems, 5G communication systems are being developed. In order to achieve a high data rate, the 5G communication system has introduced a very high frequency (mmWave) band (eg, such as the 60 GHz band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming and large scale antenna technologies are used. In the 5G communication system, scalability is increased by dividing the base station into a central unit and a distribution unit. In addition, the 5G communication system aims to support very high data rates and very low transmission delays in order to support various services.

LTE and NR are expected to coexist for a considerable period of time in the future. It is also common for one operator to have both LTE and NR. In this case, if the terminal simultaneously transmits and receives data in LTE and NR, the terminal can receive a high transmission rate through NR and stably maintain the RRC connection through LTE. When EN-DC is set, the terminal can transmit and receive data through LTE and NR.

SCG addition/change for EN-DC operation causes a lot of signaling load and considerable delay. Delay and signaling load cause degradation of performance and quality of service. For more efficient EN-DC operation, a quick SCG addition/change procedure is required.

An object of the present disclosure is to provide a method and apparatus for activating or deactivating a secondary cell group in a wireless mobile communication system.

According to an embodiment of the present disclosure, in the method of the base station, the master node transmits an SGNB Addition Request message for the terminal to the secondary node, and the master node receives the SGNB Addition Request Acknowledge message for the terminal from the secondary node. and the master node transmitting an LTE RRCConnectionReconfiguration message to the terminal. The SGNB Addition Request message includes UE capability information, and the UE capability information includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities. The UE capability information includes capability information related to SCG deactivation. The SCG deactivation-related capability information includes a 1-bit indicator indicating whether the UE supports SCG deactivation for the first band combination list, and the first band combination list includes one or more band combinations. The first band combination list is included in the second container for the MRDC function. Functions related to SCG deactivation are included in the third or second container. The SGNB Addition Request Acknowledge message includes an NR RRCReconfiguration message, and the NR RRCReconfiguration message includes SCG configuration information for the UE. The LTE RRCConnectionReconfiguration message includes the NR RRCReconfiguration message generated by the secondary node. If the SCG-STATE is not included in the SGNB Addition Request Acknowledge message or if the SCG-STATE indicating the first value is included in the SGNB Addition Request Acknowledge message, the scg-State is not included in the LTE RRCConnectionReconfiguration message. If the SCG-STATE indicating the second value is included in the SGNB Addition Request Acknowledge message, the scg-State is included in the LTE RRCConnectionReconfiguration message.

The disclosed embodiment provides a method and apparatus for activating or deactivating a secondary cell group in a wireless mobile communication system.

1A is a diagram illustrating structures of an LTE system and an E-UTRAN according to the present disclosure.
Figure 1b is a diagram illustrating a radio protocol structure in an LTE system according to the present disclosure.
1c is a diagram illustrating the structure of a 5G system and NG-RAN according to the present disclosure.
1d is a diagram illustrating a radio protocol structure in an LTE system according to the present disclosure.
1e is a diagram illustrating the structure of an EN-DC according to the present disclosure.
Figure 1f is a diagram illustrating bandwidth portion adjustment and bandwidth portion.
1G is a diagram illustrating a search period and a control resource set.
2A is a diagram illustrating operations of a terminal and a base station according to an embodiment of the present disclosure.
3A is a flowchart for explaining an operation of a base station according to an embodiment of the present disclosure.
4A is a block diagram showing the internal structure of a terminal to which the present invention is applied.
4B is a block diagram showing the internal structure of a base station to which the present invention is applied.

Hereinafter, embodiments of the present invention will be described in detail with accompanying drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, the definition will have to be made based on the contents throughout this specification.

A term used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network entities, and a term referring to various types of identification information. Etc. are illustrated for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings may be used.

For convenience of description below, the present invention uses terms and names defined in the 3rd Generation Partnership Project (3GPP) standard, which is the most up-to-date among existing communication standards. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards.

Hereinafter, in the present disclosure, UE and terminal are used in the same meaning.

Abbreviations used in the present invention are listed in the table below.

Acronym full name Acronym full name 5GC 5G Core Network NG-RAN NG Radio Access Network 5GS 5G System NR NR Radio Access 5QI 5G QoS Identifier NR-DC NR-NR Dual Connectivity ACK Acknowledgment PBR Prioritized Bit Rate AMF Access and Mobility Management Function PCC Primary Component Carrier ARQ Automatic Repeat Request PCell Primary Cell AS Access Stratum PCI Physical Cell Identifier ASN.1 Abstract Syntax Notation One PDCCH Physical Downlink Control Channel BSR Buffer Status Report PDCP Packet Data Convergence Protocol BWP Bandwidth Part PDSCH Physical Downlink Shared Channel BFD Beam Failure Detection PDUs Protocol Data Unit CAG Closed Access Group PLMN Public Land Mobile Network CAG-ID Closed Access Group Identifier PRACH Physical Random Access Channel CG Cell Group PRB Physical Resource Block CHO Conditional Handover PSCell Primary SCG Cell CIF Carrier Indicator Field PSS Primary Synchronization Signal CORESET Control Resource Set PUCCH Physical Uplink Control Channel CPC Conditional PSCell Change PUSCH Physical Uplink Shared Channel CQI Channel Quality Indicator PWS Public Warning System C-RNTI Cell RNTI QFI QoS Flow ID CSI Channel State Information QoE Quality of Experience DC Dual Connectivity QoS Quality of Service DCI Downlink Control Information RACH Random Access Channel DRB (user) Data Radio Bearer RAN Radio Access Network DRX Discontinuous Reception RA-RNTI Random Access RNTI ECGI E-UTRAN Cell Global Identifier RAT Radio Access Technology eNB E-UTRAN NodeB RB Radio Bearer EN-DC E-UTRA-NR Dual Connectivity RLC Radio Link Control EPC Evolved Packet Core RNA RAN-based Notification Area EPS Evolved Packet System RNAU RAN-based Notification Area Update E-RAB E-UTRAN Radio Access Bearer RNTI Radio Network Temporary Identifier ETWS Earthquake and Tsunami Warning System RRC Radio Resource Control E-UTRA Evolved Universal Terrestrial Radio Access RRM Radio Resource Management E-UTRAN Evolved Universal Terrestrial Radio Access Network RSRP Reference Signal Received Power FDD Frequency Division Duplex RSRQ Reference Signal Received Quality FDM Frequency Division Multiplexing RSSI Received Signal Strength Indicator GBR Guaranteed Bit Rate SCC Secondary Component Carrier HARQ Hybrid Automatic Repeat Request SCell Secondary Cell HPLMN Home Public Land Mobile Network SCG Secondary Cell Group IDC In-Device Coexistence SCS Subcarrier Spacing IE Information element SDAP Service Data Adaptation Protocol IMSI International Mobile Subscriber Identity SDU Service Data Unit KPAS Korean Public Alert System SeNB Secondary eNBs L1 Layer 1 SFN System Frame Number L2 Layer 2 S-GW Serving Gateway L3 Layer 3 SI System Information LCG Logical Channel Group SIB System Information Block MAC Medium Access Control (S-/T-)SN (Source/Target) Secondary Node MBR Maximum Bit Rate SpCell Special Cell MCG Master Cell Group SRB Signaling Radio Bearer MCS Modulation and Coding Schemes SRS Sounding Reference Signal MeNB Master eNB SSB SS/PBCH block MIB Master Information Block SSS Secondary Synchronization Signal MIMO Multiple Input Multiple Output SUL Supplementary Uplinks MME Mobility Management Entity TDD Time Division Duplex MN Master Node TDM Time Division Multiplexing MR-DC Multi-Radio Dual Connectivity TRP Transmit/Receive Point NAS Non-Access Stratum UCI Uplink Control Information NCGI NR Cell Global Identifier UE User Equipment NE-DC NR-E-UTRA Dual Connectivity UL-SCH Uplink Shared Channel NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity UPF User Plane Function

The table below defines terms frequently used in the present invention.

Terminology Definition Cell combination of downlink and optionally uplink resources. The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources. Global cell identity An identity to uniquely identify an NR cell. It is consisted of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1. gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. Information element A structural element containing single or multiple fields is referred as information element. NR NR radio access PCell SpCell of a master cell group. Primary SCG Cell For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure. Serving Cell For a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. For a UE in RRC_CONNECTED configured with CA/ DC the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells. SpCell primary cell of a master or secondary cell group. Cell Group in dual connectivity, a group of serving cells associated with either the MeNB or the SeNB. En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC. Master Cell Group in MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells. master node in MR-DC, the radio access node that provides the control plane connection to the core network. It may be a Master eNB (in EN-DC), a Master ng-eNB (in NGEN-DC) or a Master gNB (in NR-DC and NE-DC). NG-RAN node either a gNB or an ng-eNB. PSCell SpCell of a secondary cell group. Secondary Cell For a UE configured with CA, a cell providing additional radio resources on top of Special Cell. Secondary Cell Group in MR-DC, a group of serving cells associated with the Secondary Node, comprising of the SpCell (PSCell) and optionally one or more SCells. Secondary node in MR-DC, the radio access node, with no control plane connection to the core network, providing additional resources to the UE. It may be an en-gNB (in EN-DC), a Secondary ng-eNB (in NE-DC) or a Secondary gNB (in NR-DC and NGEN-DC). Conditional PSCell Change a PSCell change procedure that is executed only when PSCell execution condition(s) are met. gNB Central Unit (gNB-CU) a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected with the gNB-DU. gNB Distributed Unit (gNB-DU) a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU. E-RAB An E-RAB uniquely identifies the concatenation of an S1 Bearer and the corresponding Data Radio Bearer. When an E-RAB exists, there is a one-to-one mapping between this E-RAB and an EPS bearer of the Non Access Stratum (NAS) as defined in TS 23.1d-01 [3].

The table below is a description of the main technical terms used in the present invention.

Terminology Definition PSCell change The change means that the current PSCell is changed to a new PSCell, and includes both a change of the PSCell within the same SN and a change of the PSCell between SNs. In addition, the addition of a PSCell can also be seen as a PSCell change. CG-ConfigInfo IE It is transmitted from the MN to the SN or from the CU to the DU and consists of the following information: l UE's capability information (ue-CapabilityInfo) l Measurement results of candidate cells that can be added as a serving cell (MeasResultList2NR)
l MCG's DRX information, etc. CG-Config IE SN delivers to MN or CU to DU and consists of the following information. l NR RRCReconfiguration message containing SCG configuration information. The MN transmits the RRCReconfiguration message to the UE as it is without processing it.
l Information related to the SCG bearer. It includes information specifying a security key to be used in the bearer.
l DRX setting information of SCG
l ARFCN information indicating the center frequency of PSCell measConfig This is measurement-related information set independently by MN and SN. It is composed of at least one measurement object information (MeasObject), at least one report setting information (ReportConfig), and at least one measurement identifier (MeasId). Measurement target information and report setting information are identified as MeasObjectId and ReportConfigId, respectively, and MeasId consists of one MeasObjectId and one ReportConfigId. MeasId is information instructing to perform a predetermined operation when the measurement result for the related MeasObject meets the condition set in ReportConfigId.

1 is a diagram illustrating the structure of an LTE system and an E-UTRAN according to an embodiment of the present disclosure. The E-UTRAN (1a-01) includes an E-UTRA user plane (PDCP/RLC/MAC/PHY) and It consists of ENBs (1a-02, 1a-03, 1a-04) that provide the control plane (RRC) to the UE. ENBs are interconnected with each other via the X2 interface. ENB is connected to MME (Mobility Management Entity) (1a-05)/S-GW (Serving-Gateway) (1a-06) through S1 interface. The S1 interface supports a many-to-many relationship between MME/S-GW and ENB. MME (1a-05) and S-GW (1a-06) can be composed of one physical node or separate physical nodes.

The eNBs (1a-02, 1a-03, 1a-04) host the functions listed below.

Functions for radio resource management: radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink, downlink and sidelink (constant);

IP and Ethernet header compression, uplink data decompression and encryption of user data streams

AMF selection when AMF cannot be selected with information provided by the terminal, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (derived from AMF or O&M), for mobility and scheduling Measurement and measurement reporting configuration, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing, tight interaction between NR and E-UTRA, network slicing support

MME 1a-05 hosts functions such as NAS signaling, NAS signaling security, AS security control, S-GW selection, authentication, PWS message transmission support and location management.

S-GW (1a-06) hosts functions such as packet routing and forwarding, transport level packet marking on uplink and downlink, and mobility anchoring for handover between eNBs.

1B is a diagram illustrating a radio protocol structure of an LTE system.

The user plane protocol stack consists of PDCP (1b-01 to 1b-02), RLC (1b-03 to 1b-04), MAC (1b-05 to 1b-06), and PHY (1b-07 to 1b-08). do. The control clearing protocol stack consists of NAS (1b-09 to 1b-10), RRC (1b-11 to 1b-12), PDCP, RLC, MAC, and PHY.

Each protocol sublayer performs functions related to the operations listed in the table below.

Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, recovery from radio link failure detection and recovery, NAS message transmission, etc. PDCP Data transmission, header compression and decompression, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and out-of-order delivery, etc. RLC Upper layer PDU transmission, error correction through ARQ, RLC SDU concatenation/division/reassembly, RLC data PDU reassembly, RLC re-establishment, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in a transport block (TB) carried in the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels ranking processing, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

1C is a diagram showing the structure of a 5G system and NG-RAN according to an embodiment of the present disclosure. The 5G system is composed of NG-RAN (1c-01) and 5GC (1c-02). An NG-RAN node is one of the two below. gNB providing NR user plane and control plane towards UE; or

ng-eNB providing E-UTRA user plane and control plane towards UE.

gNBs (1c-05 to 1c-06) and ng-eNBs (1c-03 to 1c-04) are interconnected through an Xn interface. The gNB and ng-eNB are connected to an Access and Mobility Management Function (AMF) (1c-07) and a User Plane Function (UPF) (1c-08) through an NG interface. AMF (1c-07) and UPF (1c-08) can be composed of one physical node or separate physical nodes.

gNBs (1c-05 to 1c-06) and ng-eNBs (1c-03 to 1c-04) host the functions listed below.

Functions for radio resource management: radio bearer control, radio admission control, link mobility control, dynamic allocation of resources to UEs in uplink, downlink and sidelink (constant);

IP and Ethernet header compression, uplink data decompression and encryption of user data streams

AMF selection when AMF cannot be selected with information provided by the terminal, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (derived from AMF or O&M), for mobility and scheduling Measurement and measurement reporting configuration, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing, tight interaction between NR and E-UTRA, network slicing support

AMF (1c-07) hosts functions such as NAS signaling, NAS signaling security, AS security control, S-GW selection, authentication, mobility management and location management.

UPF 1c-08 hosts functions such as packet routing and forwarding, transport-level packet marking on the uplink and downlink, QoS management, and mobility anchoring for mobility.

1d is a diagram illustrating a radio protocol structure of a 5G system.

The user plane protocol stack is SDAP (1d-01 to 1d-02), PDCP (1d-03 to 1d-04), RLC (1d-05 to 1d-06), MAC (1d-07 to 1d-08), PHY (1d-09 to 1d-10). The control clearing protocol stack consists of NAS (1d-11 to 1d-12), RRC (1d-13 to 1d-14), PDCP, RLC, MAC, and PHY.

Each protocol sublayer performs functions related to the operations listed in the table below.

Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, recovery from radio link failure detection and recovery, NAS message transmission, etc. SDAP Mapping between QoS flows and data radio bearers, QoS flow ID (QFI) marking of DL and UL packets. PDCP Data transmission, header compression and decompression, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and out-of-order delivery, etc. RLC Higher layer PDU transmission, error correction through ARQ, RLC SDU division and re-division, SDU reassembly, RLC re-establishment, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in a transport block (TB) carried in the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels ranking processing, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

1E is a diagram illustrating the structure of an EN-DC according to an embodiment of the present disclosure. The E-UTRAN supports MR-DC through E-UTRA-NR dual connectivity (EN-DC), and the UE It is connected to one eNB (1e-01 to 1e-02) serving as the MN and to one en-gNB (1e-03 to 1e-04) serving as the SN. The eNBs (1e-01 to 1e-02) are connected to the EPC (1e-05) via the S1 interface and to the en-gNB (1e-03 to 1e-04) via the X2 interface. The en-gNBs 1e-03 to 1e-04 may be connected to the EPC 1e-05 via the S1-U interface and another en-gNB via the X2-U interface.

2A illustrates the operation of UE, MN and SN for SCG activation and SCG deactivation.

The mobile communication system includes at least a UE 2a-01, a Master Node (hereinafter referred to as MN 2a-03) and a Secondary Node (hereinafter referred to as SN 2a-05).

In 2a-11, the UE transmits the LTE UECapabilityInformation RRC message and the MN receives it.

The UECapabilityInformation message includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities. The UECapabilityInformation message includes capability information related to SCG deactivation. The SCG deactivation related capability information includes a 1-bit indicator indicating whether the terminal supports SCG deactivation for the first band combination list, and the first band combination list includes one or more band combinations. The first band combination list is included in the second container for the MRDC function. Capability information related to SCG deactivation is included in the first container or the second container.

At 2a-13, the UE transmits an LTE RRCConnectionReconfiguration message and the MN receives it.

The RRC message includes configuration information determined based on the LTE UECapabilityInformation message. The UE and MN perform data transmission using the above configuration. At some point the MN decides that EN-DC operation with the SN is required.

At 2a-21, the MN sends an SGNB ADDITION REQUEST message to the SN.

The MN requests the SN to allocate resources for an EN-DC connection operation for a specific UE by sending the above message. In the SGNB ADDITION REQUEST message, the MN includes CG-ConfigInfo. CG-ConfigInfo is used by the MN to request the SN to perform a specific task such as setting, modifying or releasing the SCG. The message may include additional information to help the SN set up the SCG configuration, for example. CG-ConfigInfo includes fields such as ue-CapabilityInfo and measConfigMN. ue-CapabilityInfo includes UE capability information for NR and UE capability information for EN-DC. measConfigMN includes measurement settings set by MN.

At 2a-23, the SN sends an SGNB ADDITION REQUEST message to the MN in response to the SGNB ADDITION REQUEST message.

The SGNB ADDITION REQUEST message may include: CG-Config, SCG-STATES, etc.

CG-Config is used to transmit the SCG radio configuration generated by the SN. CG-Config includes the following fields. scg-CellGroupConfig, scg-RB-Config, measConfigSN, etc.

The scg-CellGroupConfig field includes an RRCReconfiguration message generated by the SN and transmitted to the UE.

The scg-RB-Config contains the RadioBearerConfig IE to be sent to the UE used to (re)configure the SCG RB configuration.

measConfigSN contains the measurement configuration created by SN.

The SCG-STATES field includes 1-bit information indicating that SCG is activated or SCG is deactivated. When SCG is disabled. The SN includes SCG-STATES indicating SCG deactivation in the SCG ADDITION REQUEST ACKNOWLEDGE message. If the SCG is to be activated, the SN includes a SCG-STATE indicating SCG activation or the SN does not include a SCG-STATE in the SCG ADDITION REQUEST ACKNOWLEDGE message.

If SCG-STATES is not included in the SGNB Addition Request Acknowledge message or if SCG-STATE is set to a value indicating "SCG_activated", the MN does not include scg-State in the RRCReconfiguration message. The MN determines that the SCG is activated according to the absence of the SCG-STATE or the value indicated in the SCG-STATE of the SGNB ADDITION REQUEST message. The UE determines that SCG is activated based on the absence of scg-state in the RRCReconfiguration message.

If SCG-STATES included in the SGNB Addition Request Acknowledge message is set to a value indicating “SCG_deactivated”, the MN includes the scg-State in the LTE RRCConnectionReconfiguration message.

In 2a-25, the MN transmits an LTE RRCConnectionReconfiguration message and the UE receives it.

The LTE RRCConnectionReconfiguration message may include the following fields: rrc-TransactionIdentifier, scg-State, nr-SecondaryCellGroupConfig, nr-RadioBearerConfig1, nr-RadioBearerConfig2, etc.

The nr-SecondaryCellGroupConfig field contains the NR RRCReconfiguration message generated by the SN. The NR RRCReconfiguration message is a message included in the scg-CellGroupConfig field.

In the NR RRCReconfiguration message, the SN may configure measurement and radio link monitoring for each BWP of each serving cell.

The NR RRCReconfiguration message may include a secondaryCellGroup field and a measConfig field.

The secondaryCellGroup field includes CellGroupConfig IE for SCG.

The UE determines SCG configuration and SCG status based on the received message. The UE applies the determined SCG configuration and SCG status.

In 2a-27, the UE transmits an LTE RRCConnectionReconfigurationComplete message and the MN receives it.

The LTE RRCConnectionReconfigurationComplete message contains the following fields. rrc-TransactionIdentifier, scg-ConfigResponseNR .

scg-ConfigResponseNR includes an NR RRCReconfigurationComplete message that is a response to the NR RRCReconfiguration message included in the nr-SecondaryCellGroupConfig field.

At 2a-29, the MN transmits the SGNB RECONFIGURATION COMPLETE message and the SN receives it.

The purpose of the SGNB RECONFIGURATION COMPLETE message is to provide the SN with information about whether the requested configuration was successfully applied by the UE. The SGNB RECONFIGURATION COMPLETE message includes the NR RRCReconfigurationComplete message.

In 2a-31, UE and SN perform Random Access Procedure in PSCell.

The UE performs synchronization on the SN's PSCell.

The UE selects one UL BWP from among a plurality of UL BWPs of the PSCell. The UE selects the UL BWP indicated by firstActiveUplinkBWP-Id for the random access procedure.

The UE selects an uplink for the random access procedure based on the first rsrp threshold included in the ServingCellConfigCommon of the PSCell.

The UE selects one SSB from among a plurality of SSBs measured in the DL BWP for the random access procedure based on the second rsrp threshold included in the ServingCellConfigCommon of the PSCell. DL BWP is indicated by firstActiveDownlinkBWP-Id.

The UE selects a preamble corresponding to the SSB.

firstActiveUplinkBWP-Id and firstActiveDownlinkBWP-Id are included in ServingCellConfig of PSCell. ServingCellConfig of PSCell and ServingCellConfigCommon of PSCell are included in CellGroupConfig of NR RRCReconfiguration message of LTE RRCConnectionReconfiguration message.

The UE transmits the preamble in the PSCell and receives the SN. SN transmits RAR in PSCell and UE receives it.

The UE and SN determine that SGNB addition has succeeded when the random access procedure is successfully completed.

At 2a-33, the UE and MN and SN perform an activated SCG EN-DC operation.

At some point, the MN decides to deactivate the SCG based on, for example, the UE's reduced traffic volume. The MN performs the SGNB modification procedure to request SCG deactivation.

At 2a-41, the MN transmits the SGNB MODIFICATION REQUEST message and the SN receives it.

SGNB MODIFICATION REQUEST includes a REQUEESTED-SCG-STATES field. If the REQUESTED-SCG-STATES field contains an IE indicating "SCG_deactivation_requested", the SN recognizes that the SCG should be deactivated.

If the currently active SCG is to be deactivated, the MN sets the REQUESTED-SCG-STATES field to "SCG_deactivation_requested". If a currently deactivated SCG needs to be activated, the MN sets the REQUESTED-SCG-STATES field to "SCG_activation_requested".

The SN determines whether to deactivate SCG based on the received REQUESTED-SCG-STATES.

In 2a-42, the SN transmits the SGNB MODIFICATION REQUEST ACKNOWLEDGE message and the MN receives it.

The SGNB MODIFICATION REQUEST ACKNOWLEDGE message includes a SCG-STATES field. SN sets the SCG-STATES field to indicate "deactivate_SCG". The MN recognizes that the SCG should be deactivated based on the received SCG-STATE.

If the SCG-STATE field indicating "deactivate_SCG" is included in the SGNB MODIFICATION REQUEST ACKNOWLEDGE message, the MN includes the scg-State in the LTERRCConnectionReconfiguration message. If the SCG-STATE field indicating "activate_SCG" is included in the SGNB MODIFICATION REQUEST ACKNOWLEDGE message, the MN does not include the scg-State in the LTE RRCConnectionReconfiguration message.

In 2a-43, the MN transmits an LTE RRCConnectionReconfiguration message and the UE receives it.

The LTE RRCConnectionReconfiguration message includes a scg-state field indicating "deactivated".

If the LTE RRCConnectionReconfiguration message contains scg -State and the LTE RRCConnectionReconfiguration message is not received within the mrdc-SecondaryCellGroup and within the NR RRCRresume message, the UE considers SCG disabled.

If the LTE RRCConnectionReconfiguration message does not contain scg-State, the LTE RRCConnectionReconfiguration message is not received in the mrdc-SecondaryCellGroup and in the NR RRCResume message, and the SCG is currently inactive, the UE considers the SCG active.

The mrdc-SecondaryCellGroup field includes an RRC message for SCG configuration in NR-DC or NE-DC. In the case of NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the NR RRCReconfiguration message generated by the SN gNB. In the case of NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRCConnectionReconfiguration message.

In the NR RRCReconfiguration message, the bfd-and-RLM field may be included in the SpCellConfig field of the CellGroupConfig IE included in the secondaryCellGroup field.

One bfd-and-RLM field and a plurality of Purpose fields may be included in one NR RRCReconfiguration message.

If the bfd-and-RLM field is included, the UE performs RLM for the first RadioLinkMonitoringRS set if SCG is inactive.

The 1st RadioLinkMonitoringRS set is composed of one or more RadioLinkMonitoringRS configured for the 1st DL BWP of the PSCell with the Purpose field set to 'rlf' or 'both'.

If the bfd-and-RLM field is included, the UE performs BFD for the second RadioLinkMonitoringRS configuration if SCG is inactive.

The second RadioLinkMonitoringRS set is composed of one or more RadioLinkMonitoringRS configured for the first DL BWP of the PSCell with the Purpose field set to 'beamFailure' or 'both'.

At 2a-45, the UE performs an SCG deactivation operation.

The UE generates an LTE RRCConnectionReconfigurationComplete message.

At 2a-47, the UE sends an LTE RRCConnectionReconfigurationComplete message and the MN receives it.

The LTE RRCConnectionReconfigurationComplete message includes rrc-TransactionIdentifier. Based on the rrc-TransactionIdentifier, the MN recognizes that the SCG has been disabled.

At 2a-49, the MN transmits the SGNB RECONFIGURATION COMPLETE message and the SN receives it.

The MN includes the SFN-SUBFRAME IE in the SGNB RECONFIGURATION COMPLETE message. The SFN-SUBFRAME IE indicates the SFN and subframe number at the time of receiving the RRCConnectionReconfigurationComplete message from the UE in response to the RRCConnectionReconfiguration message for activating or deactivating the SCG. Alternatively, SFN-SUBFRAME indicates an SFN and subframe number for a UL-SCH in which a MAC PDU including an RRCConnectionReconfigurationComplete message is successfully received. SN recognizes when SCG is deactivated based on SFN-SUBFRAME.

At 2a-51, the UE, MN and SN perform a deactivated SCG EN-DC operation.

At any point in time, new data occurs on the UE's SCG bearer. The UE initiates a UEAssistanceInformation transmission procedure to inform the SN that SCG should be activated.

At 2a-53, the UE transmits the LTE UEAssistanceInformation message and the MN receives it.

The LTE UEAssistanceInformation message may include an uplinkData field. The uplinkData field contains IEs enumerated with a single value of "true". The MN recognizes that the SCG should be activated based on the presence of the uplinkData field.

The MN decides to trigger the SGNB modification procedure to request SCG activation.

Or the UE transmits the LTE ULInformationTransferMRDC message and the MN receives it. The message includes the NR UEAssistanceInformation message.

Then, the MN transmits the RRC Transfer message and the SN receives it. The RRC Transfer message includes the NR UEAssistanceInformation message. The SN determines to activate SCG when UEAssistanceInformation includes an uplinkData field indicating a value of "true". According to the decision, the SN transmits the SGNB Modification Required message and the MN receives it. The SN includes the SCG-STATE field indicating "Activated" in the SGNB Modification Required message.

When the SGNB Modification Required message including the SCG-STATE field indicating "Activated" is received from the SN, the MN moves to 2a-65.

Or the UE transmits the LTE ULInformationTransferMRDC message and the MN receives it. The message includes the NR UEAssistanceInformation message.

Then, the MN transmits the RRC Transfer message and the SN receives it. The RRC Transfer message includes the NR UEAssistanceInformation message. The SN determines to activate SCG when UEAssistanceInformation includes an uplinkData field indicating a value of "true". According to the decision, the SN transmits the SGNB Modification Required message and the MN receives it. The SN includes a NEXT-SCG-STATE field indicating "Activated" in the SGNB Modification Required message.

The MN transmits the SGNB Modification Request message containing the REQUESTED-SCG-STATE field and MCG configuration and the SN receives it.

The SN transmits the SGNB Modification Request Acknowledge message including the NR RRCReconfiguration message including the SCG-STATE field and the new SCG configuration, and the MN receives it.

MN moves to 2a-65.

At 2a-61, the MN transmits the SGNB MODIFICATION REQUEST message and the SN receives it.

If the LTE UEAssistanceInformation message includes the uplinkData field, the MN includes the Uplink Data Indicator in the SGNB MODIFICATION REQUEST message. Alternatively, when the LTE UEAssistanceInformation message includes the uplinkData field, the MN may include the REQUEESTED-SCG-STATES field indicating "SCG_activation_requested".

The SN determines whether SCG activation is possible. Depending on the decision, the SN generates a SGNB MODIFICATION REQUEST ACKNOWLEDGE message.

In 2a-63, the SN transmits the SGNB MODIFICATION REQUEST ACKNOWLEDGE message and the MN receives it.

The SN includes SCG-STATES in the SGNB MODIFICATION REQUEST message. If the SN decides to activate the SCG, SCG-STATES is set to "activated". If it is determined that the SN does not activate the SCG, SCG-STATES is set to "deactivated".

In 2a-65, the MN transmits an LTE RRCConnectionReconfiguration message and the UE receives it.

When SCG-STATE is set to "activated", the MN does not include the scg-state field in the LTE RRCConnectionReconfiguration message.

If SCG-STATE is set to "deactivated", the MN includes the scg-state field in the LTE RRCConnectionReconfiguration message.

If scg-State is included in the LTE RRCConnectionReconfiguration message and the LTE RRCConnectionReconfiguration message is not received within the mrdc-SecondaryCellGroup and within the NR RRCResume message, the UE considers SCG to remain disabled.

If the LTE RRCConnectionReconfiguration message does not contain scg-State, the LTE RRCConnectionReconfiguration message is not received within the mrdc-SecondaryCellGroup or within the NR RRCRresume message, and the SCG is currently inactive, the UE considers the SCG active.

The LTE RRCConnectionReconfiguration message may include an NR RRCReconfiguration message including updated SCG configuration.

At 2a-67, the UE performs an SCG activation operation.

The UE generates an LTE RRCConnectionReconfigurationComplete message.

In 2a-69, the UE transmits an LTE RRCConnectionReconfigurationComplete message and the MN receives it.

The LTE RRCConnectionReconfigurationComplete message includes the rrc-TransactionIdentifier and (if the NR RRCReconfiguration message is included in the LTE RRCConnectionReconfiguration message) the NR RRCReconfigurationComplete message. Based on the rrc-TransactionIdentifier, the MN recognizes that the SCG has been disabled.

The UE determines whether to perform a random access procedure.

If the NR RRCReconfiguration message is included in the LTE RRCConnectionReconfiguration message, the UE random access to the SpCell of the SCG if conditions A, condition B, condition C, and condition D are all satisfied and at least one of condition E, condition F, and condition G is met. start the process The UE also starts a random access procedure for the SpCell of the SCG when Condition A, Condition B, Condition C, and Condition D1 are all satisfied. The reason is that when the beam is not maintained during SCG deactivation, the beam must be selected through a random access procedure. Therefore, if RLM/BFD is set, the TA timer is running, and the beam/radio link is maintained, random access is not required. However, if RLM/BFD is not configured, upon SCG activation, random access is required regardless of whether the TA timer is running or has expired.

Condition A: When RRCReconfiguration message is received through E-UTRA SRB1.

Condition B: When SCG is not deactivated (or SCG is activated) according to the E-UTRA RRC message including the RRCReconfiguration message (ie, when scg-State is not included in the E-UTRA RRC message)

Condition B1: When SCG is not deactivated (or SCG is activated) according to an E-UTRA RRC message that does not include an RRCReconfiguration message (ie, when the E-UTRA RRC message does not include scg -State)

Condition C: If SCG is disabled before receiving E-UTRA RRC message including RRCReconfiguration message

Condition C1: If SCG is disabled before receiving E-UTRA RRC message that does not include RRCReconfiguration message

Condition D: If RLM/BFD is configured for the disabled PSCell (if the bfd-and-RLM field is included in the SpCellConfig of the previously received NR RRCReconfiguration message)

Condition D1: If RLM/BFD is not configured for the disabled PSCell (if the bfd-and-RLM field is not included in the SpCellConfig of the previously received NR RRCReconfiguration message)

Condition E: When a radio link error is detected (or declared) to the SCG (or PSCell ) while the SCG is disabled.

Condition F: When a beam fault is detected (or declared) to the SCG (or PSCell) while the SCG is disabled.

Condition G: When the TA timer for the PSCell (or the TA timer for the SCG's PTAG) has expired.

If the NR RRCReconfiguration message is not included in the LTE RRCConnectionReconfiguration message, the UE performs a random access procedure for SpCell of the SCG when condition B1, condition C1, and condition D are all satisfied and at least one of condition E, condition F, and condition G is satisfied. Start. The UE also initiates a random access procedure for the SpCell of the SCG when Condition B1, Condition C1 and Condition D1 are all satisfied.

At 2a-71, the MN transmits the SGNB RECONFIGURATION COMPLETE message and the SN receives it.

The MN includes the SFN-SUBFRAME IE in the SGNB RECONFIGURATION COMPLETE message. The SFN-SUBFRAME IE indicates the SFN and subframe number at the time of receiving the RRCConnectionReconfigurationComplete message from the UE in response to the RRCConnectionReconfiguration message for activating or deactivating the SCG. Alternatively, SFN-SUBFRAME indicates an SFN and subframe number for a UL-SCH in which a MAC PDU including an RRCConnectionReconfigurationComplete message is successfully received. SN recognizes when SCG is deactivated based on SFN-SUBFRAME.

In 2a-73, the UE and the SN perform a random access procedure.

The UE performs synchronization on the SN's PSCell.

The UE selects one UL BWP from among a plurality of UL BWPs of the PSCell. The UE selects the UL BWP indicated by firstActiveUplinkBWP-Id for the random access procedure.

The UE selects an uplink for a random access procedure based on the first rsrp threshold included in the ServingCellConfigCommon of the PSCell.

The UE selects one SSB from among a plurality of SSBs measured in the DL BWP for the random access procedure based on the second rsrp threshold included in the ServingCellConfigCommon of the PSCell. DL BWP is indicated by firstActiveDownlinkBWP -Id.

The UE selects a preamble corresponding to the SSB.

firstActiveUplinkBWP-Id and firstActiveDownlinkBWP-Id are included in ServingCellConfig of PSCell. ServingCellConfig of PSCell and ServingCellConfigCommon of PSCell are included in CellGroupConfig of NR RRCReconfiguration message of LTE RRCConnectionReconfiguration message.

The UE transmits the preamble in the PSCell and receives the SN. SN transmits RAR in PSCell and UE receives it.

The UE and SN determine that SGNB modification has succeeded when the random access procedure is successfully completed.

At 2a-75, the UE, MN and SN perform a deactivated SCG EN-DC operation.

<SCG deactivation task>

The UE deactivates data transmission through the SCG by performing "SCG bearer operation when SCG is deactivated" in slot n + RRC_Processing_delay_in_slot.

To disable lower layer activity in SCG, perform "lower layer action when SCG deactivated" in slot m+d. d can be d1 or d2 or d3.

Slot n is a slot where an RRC message causing SCG state change is successfully received (or an RRCConnectionReconfiguration message is successfully received, or an RRC message causing SCG deactivation is received).

RRC_Processing_delay_in_slot is the number of slots of the first active DL BWP corresponding to UE processing delay for the RRC message. It is calculated by dividing the UE processing delay by the slot length.

Slot m is a slot where the first RRCConnectionReconfigurationComplete message transmission occurs. The first RRCConnectionReconfigurationComplete message is a response message to the RRCConnectionReconfiguration message that caused SCG deactivation.

d1 or d2 or d3 are SCG deactivation delays and each has a fixed value.

<SCG bearer operation when SCG is disabled>

If the UE is in RRC_CONNECTED and SCG was active before receiving the message that initiated this procedure, and SRB3 was configured before receiving RRCConnectionReconfiguration, and SRB3 is not released according to nr-RadioBearerConfig2 included in RRCConnectionReconfiguration, then the UE will Trigger the PDCP entity to perform "SDU discard" and reset the RLC entity in SRB3.

The UE triggers the PDCP entity of the 1st SCG DRB to perform "SDU discard". The UE triggers the PDCP entity of the second DRB to perform "Data Recovery". The UE resets the RLC entity of the SCG DRB. The UE resets the SCG RLC entity of the SN terminated split bearer.

The UE may suspend SCG DRB.

SCG DRB is a DRB with RLC bearers only in SCG.

To reset the RLC entity, the RLC entity performs the following tasks. The RLC entity discards all RLC SDUs and RLC SDU segments and RLC PDUs. The RLC entity stops and resets all timers. The RLC entity resets all state variables to their initial values.

The first SCG DRB is an SCG DRB in which DiscardTimer is not configured.

The second SCG DRB is an SN termination split DRB in which PDCP duplication is activated before reception of an RRC message causing SCG deactivation is received.

In the case of "SDU discard", the PDCP entity discards all stored PDCP SDUs and PDCP PDUs.

For “Data Recovery”, the PDCP entity will retransmit all PDCP Data PDUs previously submitted to the SCG AM RLC entity in ascending order of their associated COUNT values for which successful delivery has not been confirmed by lower layers.

<Lower layer behavior when SCG is disabled>

The UE deactivates all configured SCells of the SCG at m+d1.

The UE deactivates the PSCell at m+d2.

At U E m+d2, the MAC entity of SCG is reset.

The UE stops the bwp-InactivityTimer associated with the PSCell at m+d3.

The UE stops the bwp-InactivityTimer associated with the SCell at m+d3.

At m+d2, the uplink HARQ buffer of the PSCell and the uplink HARQ buffer related to the SCell of the PTAG are flushed.

The UE deactivates the active BWP associated with the SCG's configured SCell at m+d1.

At m+d2, the active UL/DL BWP associated with the PSCell is deactivated and the first DL BWP associated with the PSCell is activated. Alternatively, the UE deactivates the currently active UL BWP and keeps the currently active DL BWP active.

The UE stops timeAlignmentTimers related to STAG of SCG at m+d2.

If beam failure detection and radio link monitoring are not configured to be performed for an inactive SCG, the UE stops timeAlignmentTimers associated with the SCG's PTAG at m+d2.

If beam error detection and radio link monitoring are configured for disabled SCGs:

The UE maintains timeAlignmentTimers associated with the SCG's PTAG; and

UE releases PUCCH for all serving cells of SCG at m+d2+d4; and

UE releases SRS for all serving cells of SCG at m+d2+d4; and

The UE releases the downlink assignment configured at m+d2+d4; and

The UE releases all PUSCH resources for semi-persistent CSI reporting on all serving cells of the SCG at m+d2+d4.

The first DL BWP associated with the PSCell is a DL BWP indicated by firstActiveDownlinkBWP-Id of the PSCell. Alternatively, the first DL BWP associated with the PSCell is the initial DL BWP of the PSCell.

d1 is less than or equal to d2. d2 is less than or equal to d3. Applying another deactivation delay is to properly distribute the UE processing load. d4 is a delay associated with RRC processing for resource release.

In the case of a disabled PSCell, the UE does not transmit SRS on the PSCell, the UE does not report CSI on the PSCell, the UE does not transmit on UL-SCH on the PSCell, the UE does not transmit PUCCH on the PSCell, The UE does not monitor PDCCH for PSCell. The UE does not monitor the PDCCH in the PSCell.

In the case of a deactivated SCell, the UE does not transmit SRS on the SCell, the UE does not report CSI for the SCell, the UE does not transmit on UL-SCH on the SCell, the UE does not transmit PUCCH on the SCell, The UE does not monitor the PDCCH for the SCell, and the UE does not monitor the PDCCH in the SCell.

In case of MAC reset, the UE stops all timers except: If SCG is disabled and RLM/BFD is configured for the disabled PSCell (i.e. the bfd-and-RLM field is included within the SpCellConfig field within the CellGroupConfig IE for the SecondaryCellGroup field), the beamFailureDetectionTimer and timeAlignmentTimer associated with the PSCell. The UE stops the ongoing random access procedure. The UE suspends the buffer status reporting procedure and the UE suspends the power headroom reporting procedure.

Timers that are stopped upon MAC reset include periodic timers related to BSR or PHR, inhibit timers related to scheduling requests, timeAlignmentTimer for STAG, sCellDeactivationTimer, and DRX related timers (eg drx-onDurationTimer, drx-InactivityTimer, etc.).

<SCG Activation Task>

In the case of the SCG activation operation, the UE activates the lower layer activity in the SCG by performing a "lower layer operation when SCG activation" in slot m+a. a may be a1 or a2 or a3 or a4.

Slot m is a slot where the first RRCConnectionReconfigurationComplete message transmission occurs. The first RRCConnectionReconfigurationComplete message is a response message to the RRCConnectionReconfiguration message that caused SCG deactivation.

a1 or a2 or a3 or a4 is the SCG activation delay. a1 and a2 each have a fixed value. a3 and a4 have varying values.

< Lower layer behavior when SCG is activated >

The UE activates the second DL BWP associated with the PSCell at m+a1.

activates the second UL BWP associated with the PSCell at m+a1.

The UE starts CSI reporting for the second UL BWP related to the PSCell at m+a2.

The UE starts SRS transmission in the second UL BWP associated with the PSCell at m+a3.

The UE starts PDCCH monitoring in the second DL BWP associated with the PSCell at m+a4.

The second DL BWP associated with the PSCell is a DL BWP indicated by firstActiveDownlinkBWP-Id of the PSCell.

The second UL BWP associated with the PSCell is a UL BWP indicated by the firstActive UplinkBWP-Id of the PSCell.

<Disabled SCG EN-DC operation>

The UE and MN perform data transmission through MCG DRB.

The UE and the SN perform data transmission through the MCG RLC bearer of the SN termination split DRB.

The UE performs RLM for the 1st DL BWP associated with the PSCell based on the information included in RadioLinkMonitoringConfig and the presence/absence of bfd-and-RLM.

The UE performs BFD on the first DL BWP associated with the PSCell based on the information included in RadioLinkMonitoringConfig and the presence/absence of bfd-and-RLM.

The UE performs intra-frequency measurements related to the deactivated SCG based on MeasConfig configured by the SN and included in the NR RRCReconfiguration message in the LTE RRCConnectionReconfiguration message.

The UE performs inter-frequency measurement based on measConfig configured by the SN and included in the NR RRCReconfiguration message in the LTE RRCConnectionReconfiguration message.

<Activated SCG EN-DC operation>

The UE and MN perform data transmission through MCG DRB.

The UE and the SN perform data transmission through the MCG RLC bearer of the DRB terminating the SN.

Based on RadioLinkMonitoringConfig, RLM is performed on the 2nd DL BWP associated with the PSCell.

Based on RadioLinkMonitoringConfig, BFD is performed on the 2nd DL BWP associated with the PSCell.

Based on RadioLinkMonitoringConfig, BFD is performed on the second DL BWP associated with each SCell.

The UE performs intra-frequency measurements related to the activated SCell based on MeasConfig configured by the SN and included in the NR RRCReconfiguration message in the LTE RRCConnectionReconfiguration message.

The UE performs intra-frequency measurements related to the deactivated SCell based on MeasConfig configured by the SN and included in the NR RRCReconfiguration message in the LTE RRCConnectionReconfiguration message.

The UE performs inter-frequency measurement based on MeasConfig configured by the SN and included in the NR RRCReconfiguration message in the LTE RRCConnectionReconfiguration message.

The second DL BWP associated with the PSCell is the currently active DL BWP of the PSCell.

The second DL BWP associated with the PSCell is the currently active DL BWP of the SCell.

The UE performs radio link quality measurement for the active DL BWP of the active serving cell based on the RdioLinkMonitoringConfig IE of the active DL BWP.

Radio link quality measurements are used to detect radio link failures and/or beam failures.

The UE measures a plurality of RadioLinkMonitoringRSs indicated in RdioLinkMonitoringConfig for each serving cell.

The UE performs intra-frequency measurement on the carrier frequency of the serving cell.

Below, no DRX means that DRX is not configured for SCG. In the tables below, DRX cycle and T_DRX are DRX cycles applied to the current SCG.

Below, no DRX_R means reference_DRX_cycle is not configured. In the tables below, DRX_R cycle and T_DRX_R are reference_DRX_cycle. reference_DRX_cycle is not applied to DRX operation and is used to determine various time periods. Or reference_DRX_cycle is the DRX cycle configured for SCG. If two DRX cycles are configured for the SCG, reference_DRX_cycle is the last used cycle before the SCG is deactivated. Or reference_DRX_cycle is a long DRX cycle.

The reason for using reference_DRX_cycle is that when SCG is disabled, SCG DRX is disabled and there is no currently applied DRX cycle.

Below, the SMTC period for intra-frequency measurement for the serving carrier is the period of the MeasObject IE's basic measurement timing configuration indicated by the ServingCellMO of the corresponding serving cell (when only SMTP1 is configured) or the period of the secondary measurement timing configuration (SMTC1 and SMTC2 are all configured) or the longest SMTC period (if two or more SMTCs are configured). In the tables below, the SMTC period for inter-frequency measurement is either the period of the primary measurement timing configuration (if only SMTP1 is configured) or the period of the secondary measurement timing configuration (if both SMTC1 and SMTC2 are configured) of the MeasObject IE related to that frequency, or the most Long SMTC period (if two or more SMTCs are configured).

<Wireless Link Monitoring>

The UE determines, for the first BWP or the second BWP of the PSCell, whether the downlink radio link quality for the plurality of RadioLinkMonitoringRSs estimated during the last T_Evaluate_out_SSB becomes worse than threshold_Qout_SSB within the T_Evaluate_out_SSB period.

threshold_Qout_SSB corresponds to the out-of-sync block error rate of the PDCCH and is fixed at 10%.

The UE determines, for the first BWP or the second BWP of the PSCell, whether the downlink radio link quality for the plurality of RadioLinkMonitoringRS estimated during the last T_Evaluate_in_SSB becomes better than threshold_Qin_SSB within the T_Evaluate_in_SSB period.

threshold_Qin_SSB corresponds to the in-sync block error rate of the PDCCH and is fixed at 2%.

When the SCG is activated, T_Evaluate_out_SSB and T_Evaluate_in_SSB for the second BWP of the PSCell are determined as follows.

No DRX:

T_Evaluate_out_SSB = Max(200, Ceil(10 * P) * T_SSB)

T_Evaluate_in_SSB = Max(100, Ceil(5 * P) * T_SSB)

DRX cycle ≤ 320 ms:

T_Evaluate_out_SSB = Max(200, Ceil(15 * P) * Max(T_DRX,T_SSB))

T_Evaluate_in_SSB = Max(100, Ceil(7.5 * P) * Max(T_DRX,T_SSB))

DRX period > 320 ms:

T_Evaluate_out_SSB = Ceil(10 * P) * T_DRX

T_Evaluate_in_SSB = Ceil(5 * P) * T_DRX

When the SCG is disabled, T_Evaluate_out_SSB and T_Evaluate_in_SSB for the first BWP of the PSCell are determined as follows based on reference_DRX_cycle.

No DRX_R:

T_Evaluate_out_SSB = Max(200, Ceil(10 * P) * T_SSB)

T_Evaluate_in_SSB = Max(100, Ceil(5 * P) * T_SSB)

DRX_R period ≤ 320 ms:

T_Evaluate_out_SSB = Max(200, Ceil(15 * P) * Max(T_DRX_R,T_SSB))

T_Evaluate_in_SSB = Max(100, Ceil(7.5 * P) * Max(T_DRX_R,T_SSB))

DRX_R period > 320 ms:

T_Evaluate_out_SSB = Ceil(10 * P) * T_DRX_R

T_Evaluate_in_SSB = Ceil(5 * P) * T_DRX_R

The UE determines whether RLF has occurred based on the determination. When RLF is declared, the UE reports it to the MN using the SCGFailure message.

<Beam failure detection>

The UE determines whether the downlink radio link quality for the plurality of RadioLinkMonitoringRSs estimated during the last T_Evaluate_BFD_SSB for the first BWP or the second BWP of the PSCell becomes worse than threshold_Qout_LR_SSB within the T_Evaluate_BFD_SSB period.

threshold_Qout_LR_SSB corresponds to the out-of-sync block error rate of the PDCCH and is fixed at 10%.

When SCG is activated, T_Evaluate_BFD_SSB is determined as follows.

No DRX:

T_Evaluate_BFD_SSB = Max(50, Ceil(5 * P) * T_SSB)

DRX cycle ≤ 320 ms:

T_Evaluate_BFD_SSB = Max(50, Ceil(7.5 * P) * Max(T_DRX,T_SSB))

DRX period > 320 ms:

T_Evaluate_BFD_SSB = Ceil(5 * P) * T_DRX

When SCG is disabled, T_Evaluate_BFD_SSB is determined based on reference_DRX_cycle as follows.

No DRX_R:

T_Evaluate_BFD_SSB = Max(50, Ceil(5 * P) * T_SSB)

DRX_R period ≤ 320 ms:

T_Evaluate_BFD_SSB = Max(50, Ceil(7.5 * P) * Max(T_DRX_R,T_SSB))

DRX_R period > 320 ms:

T_Evaluate_BFD_SSB = Ceil(5 * P) * T_DRX_R

< Measurement within frequency >

Any measurement is defined as an SSB-based intra-frequency measurement if the center frequency of the SSB of the serving cell indicated for measurement is the same as the center frequency of the SSB of the neighboring cell and the subcarrier spacing of the two SSBs is the same.

The UE identifies a cell within the new frequency and performs SS-RSRP, SS-RSRQ and SS-SINR measurements of the cell within the identified frequency.

If the UE is not instructed to report SSB-based RRM measurement results with associated SSB indexes (reportQuantityRsIndexes or maxNrofRSIndexesToReport are not configured) or if the UE is instructed that the neighboring cell is synchronized with the serving cell ( derivativeSSB-IndexFromCell is enabled ), the UE identifies the cell in the new detectable frequency in T_identify_intra_without_index.

If the UE is instructed to report SSB-based RRM measurement results with associated SSB indexes (reportQuantityRsIndexes or maxNrofRSIndexesToReport is configured) or if the UE is not instructed that the neighboring cell is synchronized with the serving cell (derivativeSSB-IndexFromCell is disabled), The UE identifies the cell within the new detectable frequency within T_identify_intra_with_index.

The UE identifies within_identify_intra_without_index the SS block within the new detectable frequency of the already detected cell.

T_identify_intra_without_index = (T_PSS_SSS_sync_intra + T_ SSB_measurement_period_intra) ms

T_identify_intra_with_index = (T_PSS_SSS_sync_intra + T_ SSB_measurement_period_intra + T_SSB_time_index_intra) ms

T_PSS_SSS_sync_intra

T_PSS_SSS_sync_intra is a period used for PSS/SSS detection. T_PSS_SSS_sync_intra for an intra frequency is determined according to the SCG DRX cycle and whether the SCell corresponding to the corresponding frequency is activated.

For intra-frequency measurement associated with the SCG SCell when the corresponding SCell is active, and for intra-frequency measurement associated with the PSCell when the SCG is active, T_PSS_SSS_sync_intra is determined as follows.

No DRX:

T_PSS_SSS_sync_intra = max( 600 ms, ceil( 5 x K _p ) x SMTC period ) x CSCF

DRX cycle ≤ 320 ms:

T_PSS_SSS_sync_intra = Max(50, Ceil(7.5 * P) * Max(T_DRX,T_SSB))

DRX period > 320 ms:

T_PSS_SSS_sync_intra = Ceil(5 * P) * T_DRX

When the corresponding SCell is inactive and the SCG is active, T_PSS_SSS_sync_intra is determined as follows for intra-frequency measurement associated with the SCG SCell.

No DRX:

T_PSS_SSS_sync_intra = 5 x measCycleSCell x CSCF

DRX cycle ≤ 320 ms:

T_PSS_SSS_sync_intra = 5 x Max(measCycleSCell, 1.5xDRX cycle) x CSCF

DRX period > 320 ms:

T_PSS_SSS_sync_intra = 5 x Max(measCycleSCell, DRX cycle) x CSCF

For intra-frequency measurements associated with the SCG SCell when the SCG is inactive, T_PSS_SSS_sync_intra is equal to noOfMeasCycle * measCycleSCG * CSCF.

For intra-frequency measurements associated with PSCell when SCG is inactive, T_PSS_SSS_sync_intra is equal to noOfMeasCycle * measCycleSCG * CSCF.

noOfMeasCycle is greater than 5 and is configured per measObject. noOfMeasCycle is determined/configured by SN. A plurality of noOfMeasCycle is included in the RRCReconfiguration message of the LTE RRCConnectionReconfiguration message.

Alternatively, when the SCG is inactivated, T_PSS_SSS_sync_intra is determined as follows for intra-frequency measurement associated with the SCG SCell and intra-frequency measurement associated with the PSCell.

No DRX_R:

T_PSS_SSS_sync_intra = 5 x measCycleSCell x CSCF

DRX_R period ≤ 320 ms:

T_PSS_SSS_sync_intra = 5 x Max(measCycleSCell, 1.5xDRX_R cycle) x CSCF

DRX_R period > 320 ms:

T_PSS_SSS_sync_intra = 5 x Max(measCycleSCell, DRX_R cycle) x CSCF

reference_DRX_cycle is set for each cell group. reference_DRX_cycle is determined/configured by SN. reference_DRX_cycle is included in the RRCReconfiguration message within the LTE RRCConnectionReconfiguration message. The LTE RRCConnectionReconfiguration message includes scg -State.

T_SSB_time_index_intra

T_SSB_time_index_intra is a period used to acquire the index of the SSB under measurement.

T_SSB_time_index_intra is determined as follows for intra-frequency measurement associated with the SCG SCell when the corresponding SCell is active and for intra-frequency measurement associated with the PSCell when the SCG is active.

No DRX:

T_SSB_time_index_intra = max(120 ms, ceil( 3 x K _p ) x SMTC period) x CSCF

DRX cycle ≤ 320 ms:

T_SSB_time_index_intra = max(120 ms, ceil (M2 x 3 x K _p ) x max(SMTC period, DRX cycle)) x CSCF

DRX period > 320 ms:

T_SSB_time_index_intra = Ceil(3 x K _p ) x DRX cycle x CSCF

When the corresponding SCell is inactive and the SCG is active, T_SSB_time_index_intra is determined as follows for intra-frequency measurement associated with the SCG SCell.

No DRX:

T_SSB_time_index_intra = 3 x measCycleSCell x CSCF

DRX cycle ≤ 320 ms:

T_SSB_time_index_intra = 3 x Max(measCycleSCell , 1.5xDRX cycle) x CSCF

DRX period > 320 ms:

T_SSB_time_index_intra = 3 x Max(measCycleSCell , DRX cycle) x CSCF

For intra-frequency measurements associated with the SCG SCell when the SCG is inactive, T_SSB_time_index_intra is equal to noOfMeasCycle2 * measCycleSCG * CSCF.

For intra-frequency measurements associated with PSCell when SCG is inactive, T_SSB_time_index_intra is equal to noOfMeasCycle * measCycleSCG * CSCF.

noOfMeasCycle2 is greater than 3 and is configured per measObject. noOfMeasCycle2 is determined/configured by SN. Multiple noOfMeasCycle2 may be included in the RRCReconfiguration message within the LTE RRCConnectionReconfiguration message.

Alternatively, when the SCG is inactive, T_SSB_time_index_intra is determined as follows for intra-frequency measurement associated with the SCG SCell and intra-frequency measurement associated with the PSCell.

No DRX_R:

T_SSB_time_index_intra = 3 x measCycleSCell x CSCF

DRX_R period ≤ 320 ms:

T_SSB_time_index_intra = 3 x Max(measCycleSCell , 1.5xDRX_R cycle) x CSCF

DRX_R period > 320 ms:

T_SSB_time_index_intra = 3 x Max(measCycleSCell , DRX_R cycle) x CSCF

T_SSB_measurement_period_intra

T_SSB_measurement_period_intra is a measurement period of SSB-based measurement.

T_SSB_measurement_period_intra is determined as shown in the table below for intra-frequency measurement associated with the SCG SCell when the corresponding SCell is active and for intra-frequency measurement associated with the PSCell when the SCG is active.

No DRX:

T_SSB_measurement_period_intra = max(200ms, ceil(5 x K _p ) x SMTC period) x CSCF

DRX cycle ≤ 320 ms:

T_SSB_measurement_period_intra = max(200 ms, ceil (7.5 x K _p ) x max(SMTC period, DRX cycle)) x CSCF

DRX period > 320 ms:

T_SSB_measurement_period_intra = Ceil(5 x K _p ) x DRX cycle x CSCF

When the corresponding SCell is inactive and the SCG is active, T_SSB_measurement_period_intra is determined as follows for intra-frequency measurement associated with the SCG SCell.

No DRX:

T_SSB_measurement_period_intra = 5 x measCycleSCell x CSCF

DRX cycle ≤ 320 ms:

T_SSB_measurement_period_intra = 5 x max(measCycleSCell, 1.5xDRX cycle) x CSCF

DRX period > 320 ms:

T_SSB_measurement_period_intra = 5 x max(measCycleSCell, DRX cycle) x CSCF

For intra-frequency measurements associated with the SCG SCell when the SCG is inactive, T_SSB_measurement_period_intra is equal to noOfMeasCycle2 * measCycleSCG * CSCF.

For intra-frequency measurements associated with PSCell when SCG is inactive, T_SSB_measurement_period_intra is equal to noOfMeasCycle * measCycleSCG * CSCF.

Alternatively, when the SCG is deactivated, T_SSB_measurement_period_intra is determined as follows for intra-frequency measurement associated with the SCG SCell and intra-frequency measurement associated with the PSCell.

No DRX_R:

T_SSB_measurement_period_intra = 5 x measCycleSCell x CSCF

DRX_R period ≤ 320 ms:

T_SSB_measurement_period_intra = 5 x max(measCycleSCell, 1.5xDRX_R cycle) x CSCF

DRX_R period > 320 ms:

5 x max(measCycleSCell, DRX_R cycle) x CSCF

CSCF is a scaling factor for each carrier and is determined according to the EN-DC scenario. 1 or more

K _P is the measurement gap and SMTC is determined depending on whether they overlap. 1 or more

< Measurement between frequencies >

If not defined as an intra-frequency measurement, the measurement is defined as an SSB-based inter-frequency measurement.

The UE identifies a new inter-frequency cell when carrier frequency information is provided by the PCell or PSCell and performs SS-RSRP, SS-RSRQ, and SS-SINR measurements of the identified inter-frequency cell.

If the UE is not instructed to report SSB-based RRM measurement results with associated SSB indexes (reportQuantityRsIndexes or maxNrofRSIndexesToReport are not configured) or if the UE is instructed that the neighboring cell is synchronized with the serving cell (derivativeSSB-IndexFromCell is enabled ), the UE identifies a new detectable inter-frequency cell within T_identify_inter_without_index.

If the UE is instructed to report SSB-based RRM measurement results with associated SSB indexes (reportQuantityRsIndexes or maxNrofRSIndexesToReport is configured) or if the UE is not instructed that the neighboring cell is synchronized with the serving cell (derivativeSSB-IndexFromCell is disabled), The UE identifies a new detectable inter-frequency cell in T_identify_inter_with_index.

The UE identifies within_identify_intra_without_index a new detectable inter-frequency SS block of an already detected cell.

T_identify_inter_without_index = (T_PSS_SSS_sync_inter + T_ SSB_measurement_period_inter ) ms

T_identify_inter_with_index = ( T_PSS_SSS_sync_inter + T_ SSB_measurement_period_inter + T_SSB_time_index_inter ) ms

T_PSS_SSS_sync_inter

T_PSS_SSS_sync_inter is a period used for PSS/SSS detection for an inter-frequency cell.

For inter-frequency measurement, when SCG is active, T_PSS_SSS_sync_inter is determined as follows.

No DRX:

T_PSS_SSS_sync_inter = Max(600ms, 8 * Max(MGRP, SMTC period)) * CSCF

DRX cycle ≤ 320 ms:

T_PSS_SSS_sync_inter = Max(600ms, Ceil(8*1.5) * Max(MGRP, SMTC period, DRX cycle)) * CSCF

DRX period > 320 ms:

T_PSS_SSS_sync_inter = 8 * DRX cycle * CSCF

For inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_PSS_SSS_sync_inter is equal to noOfMeasCycle_inter * measCycleSCG * CSCF.

noOfMeasCycle_inter is greater than 7 and is configured per measObject. noOfMeasCycle_inter is determined/configured by SN. A plurality of noOfMeasCycle_inter may be included in the RRCReconfiguration message in LTE RRCConnectionReconfiguration.

Alternatively, for inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_PSS_SSS_sync_inter is determined as follows.

No DRX_R:

T_PSS_SSS_sync_inter = Max(600ms, 8 * Max(MGRP, SMTC period)) * CSCF

DRX_R period ≤ 320 ms:

T_PSS_SSS_sync_inter = Max(600ms, Ceil(8*1.5) * Max(MGRP, SMTC period, DRX_R cycle)) * CSCF

DRX_R period > 320 ms:

T_PSS_SSS_sync_inter = 8 * DRX_R cycle * CSCF

T_SSB_time_index_inter

T_SSB_time_index_inter is a time period used to obtain an index of an SSB measured in an inter-frequency cell.

For inter-frequency measurements, when SCG is activated, T_SSB_time_index_inter is determined as follows.

No DRX:

T_SSB_time_index_inter = Max(120ms, 3 * Max(MGRP, SMTC period)) * CSCF

DRX cycle ≤ 320 ms:

T_SSB_time_index_inter = Max(120ms, Ceil(3 * 1.5) * Max(MGRP, SMTC period, DRX cycle)) * CSCF

DRX period > 320 ms:

T_SSB_time_index_inter = 3 * DRX cycle * CSCF

For inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_SSB_time_index_inter is equal to noOfMeasCycle2_inter * measCycleSCG * CSCF.

noOfMeasCycle2_inter is greater than 7 and is configured per measObject. noOfMeasCycle2_inter is determined/configured by SN. A plurality of noOfMeasCycle2_inter may be included in the RRCReconfiguration message in LTE RRCConnectionReconfiguration.

Alternatively, for inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_SSB_time_index_inter is determined as follows.

No DRX_R:

T_SSB_time_index_inter = Max(120ms, 3 * Max(MGRP, SMTC period)) * CSCF

DRX_R period ≤ 320 ms:

T_SSB_time_index_inter = Max(120ms, Ceil(3 * 1.5) * Max(MGRP, SMTC period, DRX_R cycle)) * CSCF

DRX_R period > 320 ms:

T_SSB_time_index_inter = 3 * DRX_R cycle * CSCF

T_SSB_measurement_period_inter

T_SSB_measurement_period_inter is a measurement period of SSB-based inter-frequency measurement.

For inter-frequency measurement, if SCG is active, T_SSB_measurement_period_inter is determined as follows.

No DRX:

T_SSB_measurement_period_inter = max(200ms, ceil(5 x K _p ) x SMTC period) x CSCF

DRX cycle ≤ 320 ms:

T_SSB_measurement_period_inter = max(200 ms, ceil (7.5 x K _p ) x max(SMTC period, DRX cycle)) x CSCF

DRX period > 320 ms:

T_SSB_measurement_period_inter = Ceil(5 x K _p ) x DRX cycle x CSCF

For inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_SSB_measurement_period_inter is equal to noOfMeasCycle2_inter * measCycleSCG * CSCF.

Alternatively, for inter-frequency measurements configured by SN and associated with SCG, if SCG is inactive, T_SSB_measurement_period_inter is determined as follows.

No DRX_R:

T_SSB_measurement_period_inter = max(200ms, ceil(5 x K _p ) x SMTC period) x CSCF

DRX_R period ≤ 320 ms:

T_SSB_measurement_period_inter = max(200 ms, ceil (7.5 x K _p ) x max(SMTC period, DRX_R cycle)) x CSCF

DRX_R period > 320 ms:

T_SSB_measurement_period_inter = Ceil(5 x K _p ) x DRX_R cycle x CSCF

<CellGroupConfig>

The CellGroupConfig IE includes the following IEs. MAC-CellGroupConfig, PhysicalCellGroupConfig, SpCellConfig and multiple SCellConfigs.

SpCellConfig IE includes the following IEs. ReconfigurationWithSync, RLF-TimersAndConstants, ServingCellConfig.

ReconfigurationWithSync IE includes the following IEs: ServingCellConfigCommon, RNTI-value.

The SCellConfig IE includes the following IEs. ServingCellConfigCommon, ServingCellConfig.

mac-CellGroupConfig contains MAC parameters applicable to the entire cell group. mac-CellGroupConfig includes DRX-Config and TAG-Config.

DRX-Config is used to configure DRX related parameters. DRX-Config includes a drx-LongCycleStartOffset field and a drx-ShortCycle field. The drx-LongCycleStartOffset field represents a long DRX cycle and the drx-ShortCycle field represents a short DRX cycle.

TAG-Config includes a plurality of TimeAlignmentTimer IEs. Each TimeAlignmentTimer IE represents a duration in ms and can be associated with PTAG or STAG. TimeAlignmentTimer is also called TA timer. The Timing Advance Group is a group of Serving Cells set by RRC, and uses the same Timing Reference Cell and the same Timing Advance value. A timing advance group containing SpCells is referred to as a Primary Timing Advance Group (PTAG), while the term Secondary Timing Advance Group (STAG) refers to other TAGs.

timeAlignmentTimer (per TAG) controls the period during which a MAC entity considers serving cells belonging to its associated TAG as uplink time aligned.

The MAC entity does not perform any uplink transmission in the serving cell except for random access preamble and MSGA transmission when the timeAlignmentTimer associated with the TAG to which this serving cell belongs is not running.

spCellConfig contains parameters for the SpCell of this cell group (PCell in MCG or PSCell in SCG).

PhysicalCellGroupConfig is used to configure L1 parameters per cell group.

RLF-TimersAndConstants is used to configure UE specific timers and constants. RLF -TimersAndConstants IE contains the following fields. t310, n310, n311, t311.

ServingCellConfigCommon is used to configure cell specific parameters of the UE's serving cell.

ServingCellConfig is used to configure (add or modify) a UE with a serving cell, which can be a SpCell or SCell of MCG or SCG. The ServingCellConfig IE may include a bwp-InactivityTimer field, a sCellDeactivationTimer field, and a servingCellMO field.

The bwp-InactivityTimer field represents a duration in ms. When the bwp-InactivityTimer of the serving cell expires, the UE falls back to the basic bandwidth portion of the serving cell.

The sCellDeactivationTimer field represents a duration in ms. The UE deactivates the SCell when the sCellDeactivationTimer of the corresponding SCell expires.

The serveCellMO field includes measObjectId of MeasObjectNR associated with the serving cell.

One ServingCellConfigCommon and one ServingCellConfig are signaled for each serving cell (ie, SpCell or SCell of MCG or SCG). A plurality of DL BWPs and a plurality of UL BWPs may be configured for each serving cell. Each DL BWP of each serving cell may be configured with a RadioLinkMonitoringConfig IE.

ServingCellConfig includes multiple BWP-Downlinks, multiple BWP-Uplinks, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, and BWP-DownlinkDedicated for initial DL BWP.

BWP-Downlink includes bWP-Id, BWP-DownlinkCommon and BWP-DownlinkDedicated.

BWP-Uplink includes bwp-Id, BWP-UplinkCommon and BWP-UplinkDedicated.

bwp-Id is an integer between 0 and 4. bwp-Id 0 is used only for the BWP indicated in SIB1. bwp-Id1 to 4 can be used for the BWP indicated in the RRCReconfiguration message.

BWP-DownlinkCommon contains the following information: frequency domain location and bandwidth of this bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PDCCH of this BWP, cell specific parameters for PDSCH of this BWP.

BWP-UplinkCommon contains the following information: frequency domain location and bandwidth of this bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PUCCH of this BWP, cell specific parameters for PUSCH of this BWP, cell Specific random access parameters.

BWP-DownlinkDedicated is used to configure dedicated (UE specific) parameters of the downlink BWP. This includes cell specific parameters for PDCCH of this BWP, cell specific parameters for PDSCH of this BWP. This includes the RadioLinkMonitoringConfig IE.

BWP-UplinkDedicated is used to configure dedicated (UE specific) parameters of uplink BWP.

firstActiveDownlinkBWP-Id includes the ID of the DL BWP to be activated when RRC (re)configuration is performed.

defaultDownlinkBWP-Id is the ID of the downlink bandwidth portion to be used when the BWP inactivity timer expires.

<radioLinkMonitoringConfig>

radioLinkMonitoringConfig is a UE-specific configuration of radio link monitoring for detecting occurrence of cell radio link failure and occurrence of beam radio link failure. radioLinkMonitoringConfig includes the following IE. Multiple RadioLinkMonitoringRS, beamFailureInstanceMaxCount, beamFailureDetectionTimer.

RadioLinkMonitoringRS IE includes ssb-Index or csi-RS-Index. The index indicates a reference signal that the UE should use for radio link monitoring or beam failure detection.

The RadioLinkMonitoringRS IE includes a Purpose field. The Purpose field represents one of beamFailure or rlf or both.

<Radio Bearer Settings>

nr-RadioBearerConfig1 and nr-RadioBearerConfig2 include the NR RadioBearerConfig IE. The field contains the configuration of RBs composed of NR PDCPs. nr-RadioBearerConfig1 is an MCG RB configuration and nr-RadioBearerConfig2 is an SCG RB configuration. RadioBearerConfig of nr-RadioBearerConfig2 is included in scg -RB-Config.

The MCG RB is either an MCG bearer or an MN terminated split bearer. SCG RBs are SCG bearers or SN terminated split bearers. A split bearer is a radio bearer with an RLC bearer in both MCG and SCG. The SN terminated bearer is a radio bearer where PDCP is located in the SN. The SCG bearer is a radio bearer with an RLC bearer only in SCG. The MN terminated bearer is a radio bearer where PDCP is located in the MN. The MCG bearer is a radio bearer having an RLC bearer only in MCG. An RLC bearer is an RLC configuration and a MAC logical channel configuration of radio bearers in one cell group.

<MeasConfig>

MeasConfig is measurement related information set independently by MN and SN. It is composed of at least one measurement object information (MeasObject), at least one report setting information (ReportConfig), and at least one measurement identifier (MeasId). Measurement target information and report setting information are identified as MeasObjectId and ReportConfigId, respectively, and MeasId consists of one MeasObjectId and one ReportConfigId. MeasId is information instructing to perform a predetermined operation when the measurement result for the related MeasObject meets the condition set in ReportConfigId.

The measurement configuration includes a measurement object, which is a list of objects for which the UE should perform measurements. In the case of intra-frequency and inter-frequency measurements, the measurement object represents the frequency/time location and subcarrier spacing of the reference signal to be measured.

For intra-frequency and inter-frequency measurements respectively, the measurement object is constructed by the MeasObjectNR IE. The first NR RRCReconfiguration, the second NR RRCReconfiguration, or the third RRCReconfiguration may include 0 or one or more MeasObjectNRs.

The MeasObjectNR IE may include smtc1 field, smtc2 field, smtc3List field, measCycle field, measCycleSCG field, noOfMeasCycle field, noOfMeasCycle2 field, and noOfMeasCycle_inter field.

smtc1 includes SSB-MTC (Measurement Timing Configuration) IE. SSB-MTC IE includes periodityAndOffset IE and duration IE. This is the default measurement timing setting.

smtc2 contains the SSB-MTC2 IE. SSB-MTC2 IE includes pci-List IE and period IE. This is the secondary measurement timing setting applied to the cells listed in the pci-List. The second measurement timing setting has a different period and the same offset as the first measurement timing setting. smtc2 is an optional IE.

The smtc3List IE includes a plurality of SSB-MTC3 IEs. SSB-MTC3 IE includes pci-List IE and offset IE. smtc3List is used when the offset of an adjacent cell is different from that indicated by the primary measurement timing due to greatly different propagation delay. It is mainly used in NTN networks. smtc3List is an optional IE. If the smtc3List IE exists in the measObject IE and the smtc1 IE does not exist, the UE cannot follow RRCReconfiguration and initiates a connection re-establishment procedure.

If smtc2 is present, for the cell indicated in the pci-List parameter of smtc2 in the same MeasObject, the UE shall set additional SMTC according to the period parameter received in the smtc2 configuration and use the offset and period parameters in the smtc1 configuration. The first subframe of each SMTC occasion occurs in the SFN and subframe of the NR SpCell that meets the above conditions.

If smtc3list exists, for the cell indicated in the pci-List parameter of each SSB-MTC3 element of smtc3list in the same MeasObject IE, the UE sets additional SS block measurement timing configuration according to the offset parameter received from each SSB and Use period and duration parameters of smtc1. The first subframe of each SMTC opportunity in each SSB-MTC3 configuration occurs at the SFN and subframe of the NR SpCell that meets the above conditions. The offset IE of each SSB-MTC3 is an integer selected (or determined) from the same set of integers used in smtc1 for period determination.

The measObjectId of MO corresponding to each serving cell is indicated by servingCellMO in serving cell configuration (ie, ServingCellConfig).

The measCycle field of an arbitrary MeasObject IE indicates a value in ms for determining various cycles related to intra-frequency measurement when the servingCellMO of an arbitrary SCell indicates the MeasObject, the SCell is inactive and the SCG is active.

The measCycleSCG field of any MeasObject IE indicates a value in ms for determining various cycles related to intra-frequency measurement when the servingCellMO of an arbitrary SCell indicates the MeasObject, the SCell is inactive, and the SCG is inactive.

The measCycleSCG field of any MeasObject IE indicates a value in ms for determining various cycles related to intra-frequency measurement related to the PSCell when the servingCellMO of the PSCell indicates the MeasObject and the SCG is inactivated.

The measCycleSCG field of any MeasObject IE indicates a value in ms for determining various cycles related to inter-frequency measurement for a corresponding measurement target when SCG is deactivated.

The noOfMeasCycle field of an arbitrary MeasObject IE indicates an integer value for determining various cycles related to intra-frequency measurement when the servingCellMO of an arbitrary SCell indicates the MeasObject and the SCG is inactive.

The noOfMeasCycle field of any MeasObject IE represents an integer value for determining various cycles related to intra-frequency measurement when the PSCell's servingCellMO indicates the MeasObject and the SCG is inactive.

The noOfMeasCycle2 field of an arbitrary MeasObject IE represents an integer value for determining various cycles related to intra-frequency measurement when the servingCellMO of an arbitrary SCell indicates the MeasObject and the SCG is inactive.

The noOfMeasCycle2 field of any MeasObject IE represents an integer value for determining various cycles related to intra-frequency measurement when the servingCellMO of the PSCell indicates the MeasObject and the SCG is inactive.

The noOfMeasCycle_inter field of any MeasObject IE represents an integer value for determining various cycles related to inter-frequency measurement for a corresponding measurement target when SCG is deactivated.

<Terminal operation>

In this disclosure, the terminal performs the following.

The UE transmits the UECapabilityInformation message to the master node. The UECapabilityInformation message includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities. The UECapabilityInformation message includes capability information related to SCG deactivation. The SCG deactivation-related capability information includes a 1-bit indicator indicating whether the UE supports SCG deactivation for the first band combination list, and the first band combination list includes one or more band combinations. The first band combination list is included in the second container for the MRDC function. Functions related to SCG deactivation are included in the first container or the second container.

A UE receives a 1 LTE RRCConnectionReconfiguration message from a master base station, the 1 LTE RRCConnectionReconfiguration message includes a 1 NR RRCReconfiguration message, and the 1 NR RRCReconfiguration message includes SCG configuration information.

A UE receives a 1 LTE RRCConnectionReconfiguration message from a master base station, the 1 LTE RRCConnectionReconfiguration message includes a 1 NR RRCReconfiguration message, and the 1 NR RRCReconfiguration message includes SCG configuration information. SCG configuration information includes a plurality of radioLinkMonitoringConfig, each of the plurality of radioLinkMonitoringConfig includes a plurality of RadioLinkMonitoringRS, each of the plurality of RadioLinkMonitoringRS includes a ssb-index and a Purpose field, and the Purpose field indicates one of beamFailure or rlf or both .

The first NR RRCReconfiguration message further includes DRX-config, and the DRX-config includes a first field indicating the length of a long DRX cycle and a second field indicating the length of a short DRX cycle.

The terminal transmits a 1 LTE RRCConnectionReconfigurationComplete message to the master base station, and the 1 LTE RRCConnectionReconfigurationComplete message includes a 1 NR RRCReconfigurationComplete message.

The terminal receives a second LTE RRCConnectionReconfiguration message from the master base station, the second LTE RRCConnectionReconfiguration message includes a second NR RRCReconfiguration message and a scg-state field, and the second NR RRCReconfiguration message rrc-transactionIdentifier field and bfd-and-RLM field and RadioBearerConfig IE

The terminal transmits a 2 LTE RRCConnectionReconfigurationComplete message to the master base station, the 2 LTE RRCConnectionReconfigurationComplete message includes a 2 NR RRCReconfigurationComplete message, and the 2 NR RRCReconfigurationComplete message includes an rrc- Contains the transactionIdentifier field.

If the 2nd LTE RRCConnectionReconfiguration message includes scg-State and the 2nd LTE RRCConnectionReconfiguration message is not received either in the NR RRCReconfiguration or in the NR RRCRResume message, the first action set and the second action set are determined by the UE to perform

A first set of actions is initiated by the terminal at a first time point, the first time point is determined based at least in part on a time point at which a second LTE RRCConnectionReconfiguration message is received, and the first set of actions is released by SRB3 according to the RadioBearerConfig IE. If not, includes resetting the PDCP entity of SRB3.

A second set of actions is initiated by the terminal at a second time point, the second time point is determined based at least in part on the time point at which the second LTE RRCConnectionReconfigurationComplete message is transmitted, and the second set of actions includes MAC reset

The second set of operations stops the bwp-InactivityTimer associated with the PSCell, flushes the uplink HARQ buffer associated with the PSCell, flushes the uplink HARQ buffer associated with the first SCell, disables the currently active DL BWP and UL BWP associated with the PSCell, and and activating a 1st DL BWP associated with, wherein the 1st SCell is a SCell associated with a PTAG of the SCG, and the 1st BWP associated with the PSCell is indicated by an index included in the 2nd NR RRCReconfiguration message. The index of the first downlink BWP may be different from firstActiveDownlinkBWP-Id of PSCell. The index of the first downlink BWP may be included outside the ServingCellConfig of the PSCell. The index of the first downlink BWP may be included in a higher IE than ServingCellConfig.

The terminal receives the third LTE RRCConnectionReconfiguration message from the master base station.

The UE transmits a 3rd LTE RRCConnectionReconfigurationComplete message to the master base station, and the 3rd LTE RRCConnectionReconfigurationComplete message includes a 3rd NR RRCReconfigurationComplete message.

If the 3rd LTE RRCConnectionReconfiguration message does not include scg-State and the LTE RRCConnectionReconfiguration message is not received neither within the NR RRCReconfiguration message nor within the NR RRCResume message and the SCG is inactive when the 3rd LTE RRCConnectionReconfiguration message is received, the third action set and the fourth action set It is determined by the terminal to perform.

A third set of actions is initiated by the terminal at a third point in time. If the random access procedure has not been initiated for SCG activation, the third time point is determined based at least in part on the fixed delay and when the third LTE RRCConnectionReconfigurationComplete message is transmitted, and the third set of operations includes a CSI report.

A fourth set of actions is started by the terminal at a fourth point in time. If the random access procedure is not initiated for SCG activation, the fourth time point is determined based at least in part on the variable delay and the time point at which the second LTE RRCConnectionReconfigurationComplete message is transmitted, and the fourth set of operations includes SRS transmission

A third set of actions is initiated by the terminal at a third point in time. If the random access procedure is initiated for SCG activation, the third time point is determined at least partially based on the first variable delay and the time point at which the UE acquires a valid TA command for the PSCell (or SCG PTAG) in the random access procedure, The third action set includes CSI reporting. A valid TA command is obtained when the PSCell receives RAR or contention is resolved.

A fourth set of actions is started by the terminal at a fourth point in time. If the random access procedure is initiated for SCG activation, the fourth time point is determined based at least in part on the second variable delay and the time point at which the UE acquires a valid TA command for the PSCell (or SCG PTAG) in the random access procedure, The fourth action set includes SRS transmission

Triggered by the UE so that the PDCP entity of the first SCG DRB performs the first set of operations and the PDCP entity of the second DRB performs the second set of operations, the first SCG DRB is an SCG DRB for which DiscardTimer is not configured, and 2 SCG DRB is an SN termination split DRB in which PDCP replication is activated before receipt of an RRC message triggering SCG deactivation, the first set of actions includes discarding all stored PDCP SDUs and PDCP PDUs, and the second set of actions includes the previous Including performing retransmission of the PDCP Data PDU submitted to the SCG AM RLC entity.

The terminal evaluates the downlink radio link quality of the first RadioLinkMonitoringRS based on the first threshold when the scg-state field is included in the second LTE RRCConnectionReconfiguration message and the bfd-and-RLM field is included in the second NR RRCReconfiguration and evaluates the downlink radio link quality of the second RadioLinkMonitoringRS based on the second threshold.

The first RadioLinkMonitoringRS is a RadioLinkMonitoringRS included in RadioLinkMonitoringConfig corresponding to the first DL BWP related to the PSCell and having a corresponding Purpos field set to rlf or both.

The 2nd RadioLinkMonitoringRS is a RadioLinkMonitoringRS included in RadioLinkMonitoringConfig corresponding to the 1st DL BWP related to the PSCell and whose Purpos field is set to beamFailure or both.

The first threshold is fixed to a first value and the second threshold is fixed to a second value, and the second value is higher than the first value.

The 1st DL BWP related to the PSCell is indicated by the 2nd NR RRCReconfiguration message.

If the scg-state field is included in the second LTE RRCConnectionReconfiguration message, the PSCell and the PSCell based at least in part on the presence of the bfd-and-RLM field included in the first RadioLinkMonitoringConfig included in the first NR RRCReconfiguration message and the second NR RRCReconfiguration message The UE performs radio link monitoring for an associated 1st DL BWP, the 1st DL BWP is indicated by the index of the 1st NR RRCReconfiguration message, the 1st RadioLinkMonitoringConfig is a RadioLinkMonitoringConfig related to the 1st DL BWP, and the 1st NR RRCReconfiguration The message includes a plurality of RadioLinkMonitoringConfig, and the second NR RRCReconfiguration message includes one bfd-and -RLM field.

If the scg-state field is included in the second LTE RRCConnectionReconfiguration message, the PSCell and the PSCell based at least in part on the presence of the bfd-and-RLM field included in the first RadioLinkMonitoringConfig included in the first NR RRCReconfiguration message and the second NR RRCReconfiguration message The terminal performs beam failure detection for the associated 1st DL BWP, the 1st DL BWP is indicated by the index of the 1st NR RRCReconfiguration message, the 1st RadioLinkMonitoringConfig is a RadioLinkMonitoringConfig related to the 1st DL BWP, and the 1st NR RRCReconfiguration The message includes a plurality of RadioLinkMonitoringConfig, and the second NR RRCReconfiguration message includes bfd-and -RLM fields.

If RLF is declared based on radio link monitoring, the terminal transmits an LTE ULInformationTransferMRDC message to the master base station.

The LTE ULInformationTransferMRDC message includes an NR SCGFailure message, the NR SCGFailure message includes a failureType field, and the failureType field indicates a value indicating the cause of RLF occurrence in the deactivated SCG.

If beam failure has been detected in the deactivated SCG at the time the UE receives the NRRRCReconfiguration message that triggers SCG activation, a random access procedure for the PSCell is started.

If the bfd-and-RLM field is included in the second NRReconfiguration message, radio link monitoring is performed for the first RadioLinkMonitoring set and beam failure detection is performed for the second RadioLinkMonitoring set. The first RadioLinkMonitoring set has a destination field set to 'rlf' or 'both' and includes one or more RadioLinkMonitoringRS configured for the first DL BWP of the PSCell, and the second RadioLinkMonitoringRS set has a destination field set to 'beamFailure' or 'both' and includes one or more RadioLinkMonitoringRS configured for the first DL BWP of the PSCell.

If the SCG is not deactivated according to the 3rd LTE RRCConnectionReconfiguration message and the SCG is deactivated before receiving the 3rd LTE RRCConnectionReconfiguration message and the UE is not configured to perform BFD and RLM when the SCG is deactivated, the UE random access procedure for the PSCell Initiate.

If the SCG is not deactivated according to the 3rd LTE RRCConnectionReconfiguration message and the SCG is deactivated before receiving the 3rd LTE RRCConnectionReconfiguration message and the UE is configured to perform BFD and RLM when the SCG is deactivated and a radio link failure is detected for the SCG, the UE discloses a UE random access procedure for the PSCell.

The SCG is not deactivated according to the 3rd LTE RRCConnectionReconfiguration message and the SCG is deactivated before receiving the 3rd LTE RRCConnectionReconfiguration message and the UE is configured to perform BFD and RLM when the SCG is deactivated and the beam for the PSCell while the SCG is deactivated When a failure is detected, the UE initiates a UE random access procedure for the PSCell.

If the SCG is not deactivated according to the 3rd LTE RRCConnectionReconfiguration message and the SCG is deactivated before receiving the 3rd LTE RRCConnectionReconfiguration message and the UE is configured to perform BFD and RLM when the SCG is deactivated and the timeAlignmentTimer associated with the PTAG of the SCG is not running The UE initiates a UE random access procedure for the PSCell.

If the downlink radio link quality of the first DL BWP of the PSCell estimated during the first period when the SCG is not deactivated (or activated) is evaluated by the UE and the SCG is deactivated, the second period of the PSCell estimated during the second period The downlink radio link quality of the DL BWP is evaluated by the UE. The first DL BWP is indicated in the NR RRCReconfiguration message triggering SCG activation, the second DL BWP is indicated in the NR RRCReconfiguration message triggering SCG deactivation, the first period is determined based on the first DRX cycle, and the second period Is determined based on the second DRX cycle. The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

The second period is determined based at least in part on the first constant and the second DRX period when the second DRX period is equal to or less than 320 ms, and based at least in part on the second constant and the second DRX period when the second period is greater than 320 ms It is decided. The first constant is greater than the second constant.

The UE measures a cell in a frequency associated with the PSCell based at least in part on the first cycle, and the first cycle for the cell in the frequency associated with the PSCell is determined based on the measCycle and the first DRX cycle if the SCG is active, and the SCG is If it is inactive, it is determined based on measCycle and the second DRX cycle.

The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

A plurality of measCycles are included in the second NR RRCReconfiguration message, and the measCycle used to determine the first cycle for cell measurement within a frequency associated with the PSCell is a measCycle corresponding to the carrier frequency of the PSCell among the plurality of measCycles.

The first cycle is determined by comparing measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and determined by comparing the value obtained by multiplying the measCycle and the second DRX cycle by a constant when the second DRX cycle is greater than 320 ms, and the constant is greater than 1

The UE measures a cell in a frequency associated with the PSCell based at least in part on the first cycle, and the first cycle for the cell in the frequency associated with the PSCell is determined based on the measCycle and the first DRX cycle if the SCG is active, and the SCG is If it is inactive, it is determined based on measCycle and the second DRX cycle.

The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

A plurality of measCycles are included in the second NR RRCReconfiguration message, and the measCycle used to determine the first cycle for cell measurement within a frequency associated with the PSCell is a measCycle corresponding to the carrier frequency of the PSCell among the plurality of measCycles.

The first cycle is determined by comparing measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and determined by comparing the value obtained by multiplying the measCycle and the second DRX cycle by a constant when the second DRX cycle is greater than 320 ms, and the constant is greater than 1

If not instructed to report the SSB-based RRM measurement result together with the associated SSB index, the UE identifies a cell within a frequency associated with the PSCell within the first period.

The first period is determined by adding the second period for PSS/SSS detection, the third period for intra-frequency measurement period, and the fourth period for SSB index acquisition.

The second cycle for the cell within the frequency associated with the PSCell is determined based at least in part on MeasCycle and the first DRX cycle and the first constant if the SCG is active, and on measCycle and the second DRX cycle and the first constant if the SCG is inactive. determined at least in part based on

The third cycle for the cell within the frequency associated with the PSCell is determined based at least in part on MeasCycle and the first DRX cycle and the second constant if the SCG is active and at least on the measCycle and the second DRX cycle and the second constant if the SCG is inactive. determined in part on the basis of

The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

A plurality of measCycles are included in the second NR RRCReconfiguration message. The measCycle used to determine the first period is a measCycle corresponding to the carrier frequency of the PSCell among a plurality of measCycles.

The second cycle of the inactive SCG is determined by comparing measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and when the second DRX cycle is greater than 320 ms, by comparing measCycle and multiplying the second DRX cycle by the fourth constant It is decided. The fourth constant is greater than 1.

The third cycle of the inactive SCG is determined by comparing measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and when the second DRX cycle is greater than 320 ms, by comparing measCycle and multiplying the second DRX cycle by the fifth constant It is decided. The fifth constant is greater than 1.

The first constant and the second constant are equal to each other. The first constant, the third constant, and the fourth constant are different from each other.

When instructed to report the SSB-based RRM measurement result together with the associated SSB index, the UE identifies a cell within a frequency associated with the PSCell within the first period.

The first period is determined by adding the second period for PSS/SSS detection, the third period for intra-frequency measurement period, and the fourth period for SSB index acquisition.

For a cell within a frequency associated with the PSCell, the second cycle is determined based at least in part on the first DRX cycle and the first constant if the SCG is active, and based at least on measCycle and the second DRX cycle and the first constant if the SCG is inactive. determined in part on the basis of

A third cycle for a cell within a frequency associated with the PSCell is determined based at least in part on the first DRX cycle and the second constant if the SCG is active and at least in part on the measCycle and the second DRX cycle and the second constant if the SCG is inactive. is determined based on

A fourth cycle for a cell within a frequency associated with the PSCell is determined based at least in part on measCycle and the first DRX cycle and a third constant if the SCG is active and at least based on measCycle and the second DRX cycle and a third constant if the SCG is inactive. determined in part on the basis of

The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

A plurality of measCycles are included in the second NR RRCReconfiguration message. The measCycle used to determine the first period is a measCycle corresponding to the carrier frequency of the PSCell among a plurality of measCycles.

If the SCG is inactive, the second cycle is determined by comparing the measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and when the second DRX cycle is greater than 320 ms, the measCycle and the product of the second DRX cycle multiplied by the fourth constant are compared. It is decided by The fourth constant is greater than 1.

When the SCG is inactive, the third cycle is determined by comparing the measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and when the second DRX cycle is greater than 320 ms, the measCycle and the product of the second DRX cycle multiplied by the fifth constant are compared. It is decided by The fifth constant is greater than 1.

If SCG is inactive, the fourth cycle is determined by comparing measCycle and the second DRX cycle when the second DRX cycle is 320 ms or less, and when the second DRX cycle is greater than 320 ms, the measCycle and the product of the second DRX cycle multiplied by the sixth constant are compared. It is decided by The sixth constant is greater than 1.

The first constant and the second constant are equal to each other. The first constant, the third constant, and the fourth constant are different from each other.

Based on the first period when the SCG is activated and based at least in part on the second period when the SCG is inactive, the terminal performs inter-frequency measurements configured by the secondary node.

If the first DRX cycle is less than or equal to 320 ms, the first period is determined by multiplying the first DRX cycle by the seventh constant, and if the first DRX cycle is greater than 320 ms, the first period is determined by multiplying the first DRX cycle by the eighth constant.

If the second DRX cycle is less than or equal to 320 ms, the second period is determined by multiplying the second DRX cycle by the seventh constant, and if the second DRX cycle is greater than 320 ms, the second period is determined by multiplying the second DRX cycle by the eighth constant.

The first DRX cycle is a DRX cycle configured for the SCG and applied to the current SCG, and the second DRX cycle is a DRX cycle configured for the SCG and not applied to the current SCG.

The seventh constant is greater than the eighth constant.

<Base station operation>

In this disclosure, the base station performs the following.

In the step of the master node transmitting the SGNB Addition Request message for the UE to the secondary node, the SGNB Addition Request message includes UE capability information. The UE capability information includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities. The UE capability information includes capability information related to SCG deactivation. The SCG deactivation-related capability information includes a 1-bit indicator indicating whether the UE supports SCG deactivation for the first band combination list, and the first band combination list includes one or more band combinations. The first band combination list is included in the second container for the MRDC function. Functional information related to SCG deactivation is included in either the first container or the second container.

The master node receives the SGNB Addition Request Acknowledge message for the UE from the secondary node, the SGNB Addition Request Acknowledge message includes the NR RRCReconfiguration message, and the NR RRCReconfiguration message includes SCG configuration information for the UE.

The master node transmits an LTE RRCConnectionReconfiguration message to the terminal. The LTE RRCConnectionReconfiguration message includes the NR RRCReconfiguration message generated by the secondary node.

If the SCG-STATE is not included in the SGNB Addition Request Acknowledge message or if the SCG-STATE indicating the first value is included in the SGNB Addition Request Acknowledge message, the scg-State is not included in the LTE RRCConnectionReconfiguration message.

If the SCG-STATE indicating the second value is included in the SGNB Addition Request Acknowledge message, the scg-State is included in the LTE RRCConnectionReconfiguration message.

The master node receives the LTE RRCConnectionReconfigurationComplete message from the terminal. The LTE RRCConnectionReconfigurationComplete message includes the NR RRCReconfigurationComplete message

The master node sends the SGNB Reconfiguration Complete message to the secondary node. The SGNB Reconfiguration Complete message includes the NR RRCReconfigurationComplete message.

The master node transmits the SGNB Modification Request message to the secondary node.

The SGNB Modification Request message includes REQUESTED-SCG-STATE. The master node sets REQUESTED-SCG-STATE to the second value if SCG should be disabled. The master node sets REQUESTED-SCG-STATE to the first value if SCG needs to be activated.

The second value indicates that SCG should be disabled. The first value indicates that SCG should be enabled.

The master node receives the SGNB Modification Request Acknowledge from the secondary node. SGNB Modification Request Acknowledge includes SCG-STATE and NR RRCReconfiguration messages.

The master node transmits an LTE RRCConnectionReconfiguration message to the terminal. The LTE RRCConnectionReconfiguration message includes the scg-State and the NR RRCReconfiguration message generated by the secondary node.

If the SCG-STATE indicating the first value is included in the SGNB Modification Request Acknowledge message, the scg-State is not included in the LTE RRCConnectionReconfiguration message.

The scg-State is included in the LTE RRCConnectionReconfiguration message when the SCG-STATE indicating the second value is included in the SGNB Modification Request Acknowledge message.

The master node receives the LTE RRCConnectionReconfigurationComplete message from the terminal. The LTE RRCConnectionReconfigurationComplete message includes an rrc-TransactionIdentifier field. The rrc-TransactionIdentifier field includes a value included in the rrc-TransactionIdentifier field of the LTE RRCConnectionReconfiguration message.

The master node sends the SGNB Reconfiguration Complete message to the secondary node. The SGNB Reconfiguration Complete message includes the SFN-SUBFRAME field. The SFN-SUBFRAME field includes the SFN and subframe number determined based at least in part on the time the master node received the LTE RRCConnectionReconfigurationComplete message.

If SRB3 is not released according to NR RRCReconfiguration, the secondary node reconfigures the PDCP entity of SRB3 at the first time. The first time point is determined based at least in part on the SFN-SUBFRAME field.

The master node receives the ULInformationTransferMRDC message from the terminal. The ULInformationTransferMRDC message includes the UEAssistanceInformation message. The UEAssistanceInformation message includes an uplinkData field indicating the first value.

The master node sends an RRC TRANSFER message to the secondary node. The RRC TRANSFER message includes UEAssistanceInformation.

Determine by the secondary node whether to activate the SCG based at least in part on the UplinkData field in the UEAssistanceInformation and the presence or absence of the UplinkData field.

Secondary node sends SGNB Modification Required message to master node. The SGNB Modification Required message optionally includes a SCG-STATE field.

SCG-State is not included in the LTE RRCConnectionReconfiguration message when the SCG-STATE indicating the first value is included in the SGNB Modification Required message.

The scg-State is included in the LTE RRCConnectionReconfiguration message when the SCG-STATE is not included in the SGNB Modification Required message and the SGNB Modification Required message includes the NR RRCReconfiguration message.

The master node transmits LTE RRCConnectionReconfiguration to the terminal. The LTE RRCConnectionReconfiguration message does not include the scg-State if the SGNB Modification Required message includes the SCG-STATE field indicating the first value.

The master node sends the SGNB Reconfiguration Complete message to the secondary node. The SGNB Reconfiguration Complete message includes the SFN-SUBFRAME field. The SFN-SUBFRAME field includes the SFN and subframe number determined based at least in part on the time the master node received the LTE RRCConnectionReconfigurationComplete message.

3a illustrates the operation of a base station.

In step 3a-11, the master node transmits the SGNB Addition Request message for the terminal to the secondary node. The SGNB Addition Request message includes UE capability information. The UE capability information includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities. The UE capability information includes capability information related to SCG deactivation. The SCG deactivation-related capability information includes a 1-bit indicator indicating whether the UE supports SCG deactivation for the first band combination list, and the first band combination list includes one or more band combinations. The first band combination list is included in the second container for the MRDC function. Functions related to SCG deactivation are included in the third or second container.

In step 3a-13, the master node receives the SGNB Addition Request Acknowledge message for the UE from the secondary node, the SGNB Addition Request Acknowledge message includes the NR RRCReconfiguration message, and the NR RRCReconfiguration message includes SCG configuration information for the UE. .

In step 3a-15, the master node transmits an LTE RRCConnectionReconfiguration message to the terminal. The LTE RRCConnectionReconfiguration message includes the NR RRCReconfiguration message generated by the secondary node.

If the SCG-STATE is not included in the SGNB Addition Request Acknowledge message or if the SCG-STATE indicating the first value is included in the SGNB Addition Request Acknowledge message, the scg-State is not included in the LTE RRCConnectionReconfiguration message. If the SCG-STATE indicating the second value is included in the SGNB Addition Request Acknowledge message, the scg-State is included in the LTE RRCConnectionReconfiguration message.

4A is a block diagram showing the internal structure of a terminal to which the present invention is applied.

Referring to the drawing, the terminal includes a control unit 4a-01, a storage unit 4a-02, a transceiver 4a-03, a main processor 4a-04, and an input/output unit 4a-05.

The controller 4a-01 controls overall operations of the UE related to mobile communication. For example, the controller 4a-01 transmits and receives signals through the transceiver 4a-03. Also, the controller 4a-01 writes and reads data in the storage unit 4a-02. To this end, the controller 4a-01 may include at least one processor. For example, the controller 4a-01 may include a communication processor (CP) that controls communication and an application processor (AP) that controls upper layers such as application programs. The controller 4a-01 controls the storage unit and the transceiver so that the terminal operations of FIGS. 2A and 3A are performed. The transceiver is also referred to as a transceiver.

The storage unit 4a-02 stores data such as a basic program for operation of the terminal, an application program, and setting information. The storage unit 4a-02 provides stored data according to the request of the control unit 4a-01.

The transver 4a-03 includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal, transmits the signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), and the like. The RF processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

The main processor 4a-04 controls overall operations except for operations related to mobile communication. The main processor 4a-04 processes the user's input transmitted from the input/output unit 4a-05, stores necessary data in the storage unit 4a-02, and controls the control unit 4a-01 for mobile communication It performs related operations and delivers output information to the input/output unit 4a-05.

The input/output unit 4a-05 is composed of a device that accepts user input, such as a microphone and a screen, and a device that provides information to the user, and performs input and output of user data under the control of the main processor.

4B is a block diagram showing the configuration of a base station according to the present invention.

As shown in the figure, the base station includes a control unit 4b-01, a storage unit 4b-02, a transceiver 4b-03, and a backhaul interface unit 4b-04.

The controller 4b-01 controls overall operations of the base station. For example, the control unit 4b-01 transmits and receives signals through the transceiver 4b-03 or the backhaul interface unit 4b-04. Also, the controller 4b-01 writes and reads data in the storage unit 4b-02. To this end, the controller 4b-01 may include at least one processor. The controller 4b-01 is a transceiver so that the operation of the base station shown in FIG. 2A is performed. storage. Controls the backhaul interface.

The storage unit 4b-02 stores data such as a basic program for the operation of the main base station, an application program, and setting information. In particular, the storage unit 4b-02 may store information on bearers assigned to the connected terminal, measurement results reported from the connected terminal, and the like. In addition, the storage unit 4b-02 may store information that is a criterion for determining whether to provide or stop multiple connections to the terminal. And, the storage unit 4b-02 provides the stored data according to the request of the control unit 4b-01.

The transceiver 4b-03 includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processor upconverts the baseband signal provided from the baseband processor into an RF band signal, transmits the signal through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. The RF processing unit may perform a downlink MIMO operation by transmitting one or more layers. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

The backhaul interface unit 4b-04 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 4b-04 converts a bit string transmitted from the main base station to another node, for example, a secondary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. convert to heat

Claims (1)

In a wireless communication system, in a base station method,
The master node transmits the SGNB Addition Request message for the terminal to the secondary node, the master node receives the SGNB Addition Request Acknowledge message for the terminal from the secondary node, and the master node transmits the LTE RRCConnectionReconfiguration message to the terminal. Including, the SGNB Addition Request message includes UE capability information, the UE capability information includes a first container for EUTRA capabilities, a second container for MRDC capabilities, and a third container for NR capabilities, and the UE capability information SCG deactivation-related capability information, wherein the SCG deactivation-related capability information includes a 1-bit indicator indicating whether the terminal supports SCG deactivation for a first band combination list, and the first band combination list includes one or more band combinations. and the first band combination list is included in the second container for the MRDC function, the function related to SCG deactivation is included in the first container or the second container, the SGNB Addition Request Acknowledge message contains the NR RRCReconfiguration message, and the NR RRCReconfiguration The message includes SCG configuration information for the UE, the LTE RRCConnectionReconfiguration message includes an NR RRCReconfiguration message generated by the secondary node, and SCG-STATE is not included in the SGNB Addition Request Acknowledge message or SCG indicating the first value If -STATE is included in the SGNB Addition Request Acknowledge message, scg-State is not included in the LTE RRCConnectionReconfiguration message, and if the SCG-STATE representing the second value is included in the SGNB Addition Request Acknowledge message, scg-State is not included in the LTE RRCConnectionReconfiguration message. How to be included in.