Method and apparatus for secondary base station change in mobile wireless communication system

Abstract

A method and apparatus for secondary base station change in a mobile communication system with multiple are provided. Method for secondary node change includes transmitting to a target SN a control message requesting conditional secondary node change, receiving from the target SN a Xn message including conditional secondary node change information, transmitting to a terminal LTE DL message for conditional secondary node change, receiving from the terminal a 1st LTE UL message including a transaction identifier, receiving from the terminal a conditional reconfiguration identifier and transmitting to a source SN a control message for data forwarding.

Description

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of Korean Patent Application No. 10-2021-0103238, filed on Aug. 5, 2021, the disclosure of which is incorporated herein by reference in its entirety.

BACKGROUND

The present disclosure relates to a mobile communication system with conditional secondary base station change. More specifically, the present disclosure relates to a secondary node change method and an apparatus for use in the mobile communication system with conditional reconfiguration configuration managed by a master node.

To meet the increasing demand for wireless data traffic since the commercialization of 4th generation (4G) communication systems, the 5th generation (5G) system is being developed. For the sake of high, 5G system introduced millimeter wave (mmW) frequency bands (e. g. 60 GHz bands). In order to increase the propagation distance by mitigating propagation loss in the 5G communication system, various techniques are introduced such as beamforming, massive multiple—input multiple output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna. In addition, base station is divided into a central unit and plurality of distribute units for better scalability. To facilitate introduction of various services, 5G communication system targets supporting higher data rate and smaller latency.

SUMMARY

Aspects of the present disclosure are to address the problems of conditional secondary node change. Accordingly, an aspect of the present disclosure is to provide a method and an apparatus for providing the configuration information for conditional secondary node change.

In accordance with an aspect of the present disclosure, a method of a base station in mobile communication system is provided. In the method, the base station transmits to a target node a base station control message for SGNB addition request, the base station receives from the target node a base station control message for SGNB addition response, the base station transmits LTE RRC message to UE for conditional secondary node change, the base station receives a first RRC response message, the base station receives a second RRC response message, the base station performs SGNB release procedure with source node for SN STATUS TRANSFER and data forwarding.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating the architecture of an LTE system and an E-UTRAN to which the disclosure may be applied;

FIG. 2 is a diagram illustrating a wireless protocol architecture in an LTE system to which the disclosure may be applied;

FIG. 3 is a diagram illustrating the architecture of an 5G system and a NG-RAN to which the disclosure may be applied;

FIG. 4 is a diagram illustrating a wireless protocol architecture in an 5G system to which the disclosure may be applied;

FIG. 5 is a diagram illustrating the architecture of an EN-DC to which the disclosure may be applied;

FIG. 6A is a diagram illustrating EN-DC operation performed by a UE and a base station according to the first embodiment of the present disclosure;

FIG. 6B is a diagram illustrating another EN-DC operation performed by a UE and a base station according to the first embodiment of the present disclosure;

FIG. 7 is a diagram illustrating a structure of LTE reconfiguration message for the 1st reconfiguration procedure;

FIG. 8 is a flow diagram illustrating an operation of a master base station according to the first embodiment of the present disclosure;

FIG. 9 is a flow diagram illustrating an operation of a terminal according to the first embodiment of the present disclosure;

FIG. 10 is a block diagram illustrating the internal structure of a UE to which the disclosure is applied;

FIG. 11 is a block diagram illustrating the configuration of a base station according to the disclosure;

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms used, in the following description, for indicating access nodes, network entities, messages, interfaces between network entities, and diverse identity information is provided for convenience of explanation. Accordingly, the terms used in the following description are not limited to specific meanings but may be replaced by other terms equivalent in technical meanings.

In the following descriptions, the terms and definitions given in the 3GPP standards are used for convenience of explanation. However, the present disclosure is not limited by use of these terms and definitions and other arbitrary terms and definitions may be employed instead.

In the following descriptions, UE and terminal are used as same terminology.

Table 1 lists the acronyms used throughout the present disclosure.

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

Table 2 lists the terminologies and their definition used throughout the present disclosure.

TABLE 2
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  An identity to uniquely identifying an NR cell. It is consisted of
identity     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  A structural element containing single or multiple fields is referred as
element      information element.
NR           NR radio access
PCell        SpCell of a master cell group.
Primary SCG  For dual connectivity operation, the SCG cell in which the UE
Cell         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  in MR-DC, a group of serving cells associated with the Master Node,
Group        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       either a gNB or an ng-eNB.
node
PSCell       SpCell of a secondary cell group.
Secondary    For a UE configured with CA, a cell providing additional radio
Cell         resources on top of Special Cell.
Secondary    in MR-DC, a group of serving cells associated with the Secondary
Cell Group   Node, comprising of the SpCell (PSCell) and optionally one or more
             SCells.
Secondary    in MR-DC, the radio access node, with no control plane connection to
node         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  a PSCell change procedure that is executed only when PSCell
PSCell       execution condition(s) are met.
Change
gNB Central  a logical node hosting RRC, SDAP and PDCP protocols of the gNB or
Unit (gNB-   RRC and PDCP protocols of the en-gNB that controls the operation of
CU)          one or more gNB-DUs. The gNB-CU terminates the F1 interface
             connected with the gNB-DU.
gNB          a logical node hosting RLC, MAC and PHY layers of the gNB or en-
Distributed  gNB, and its operation is partly controlled by gNB-CU. One gNB-DU
Unit (gNB-   supports one or multiple cells. One cell is supported by only one gNB-
DU)          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.401 [3].

Table 3 lists abbreviations of various messages, information elements and terminologies used throughout the present disclosure.

TABLE 3
Abbreviation     Message/IE/Terminology
LTE RECNF        RRCConnectionReconfiguration
LTE RECNF CMP    RRCConnectionReconfigurationComplete
CAPENQ           UECapabilityEnquiry
CAPINF           UECapabilityInformation
NR RECNF         RRCReconfiguration
NR RECNF CMP     RRCReconfigurationComplete
ULIT             ULInformationTransferMRDC
SGNB ADD REQ     SGNB ADDITION REQUEST
SGNB ADD REQ ACK SGNB ADDITION REQUEST ACKNOWLEDGE
SGNB REL REQ     SGNB RELEASE REQUEST
SGNB REL REQ ACK SGNB RELEASE REQUEST ACKNOWLEDGE
SGNB RECNF CMP   SGNB RECONFIGURATION COMPLETE
Transaction ID   rrc-TransactionIdentifier
TCSPCELL         Target Candidate SpCell
CRID             CondReconfigurationId

Table 4 explains technical terminologies used throughout the present disclosure.

TABLE 4
Terminology      Definition
PSCell change    It means the current PSCell changes to a new PSCell. It
                 includes intra-SN PSCell change and inter-SN PSCell change.
                 PSCell addition is also considered as PSCell change.
CG-ConfigInfo IE The IE is transferred from MN to SN or from CU to DU. It
                 includes following information
                 ue-CapabilityInfo includes various information for
                 UE capability
                 MeasResultList2NR includes measurement results on
                 the candidate cells for serving cell
                 DRX configuration of MCG
CG-Config IE     The IE is transferred from SN to MN or from CU to DU. It
                 includes following information
                 NR RRCReconfiguration which includes SCG
                 configuration informatino. MN transfer the NR
                 RRCReconfiguration message to UE without
                 modifying it
                 Information related to SCG bearer. It includes the
                 information indicating the security key for the bearer
                 DRX configuration of SCG
                 ARFCN indicating the center frequency of PSCell
measConfig       It is configuration related to measurement and set by MN and
                 SN separately. It comprises at least one measurement object
                 (measObject), at least one report configuration (ReportConfig)
                 and at least one measurement identity (measId). A measObject
                 is identified by a MeasObjectId. A reportConfig is identified
                 by a ReportConfigId. A measId comprises a measObjectId and
                 a reportConfigId. MeasId instructs UE to perform a specific
                 operation when measurement result on the associated
                 measObject fulfils condition set by ReportConfigId
TCSPCELL         It indicates target candidate SPCell. In the 1st procedure,
                 plurality of cells of a single target node can be configured as
                 target candidate SpCell. TCSPCELL can be a cell selected, by
                 MN or S-SN, among the cells for which UE report
                 measurement result. Throughout the 1st procedure, one of
                 plurality of TCSPCELL becomes PSCell

FIG. 1 is a diagram illustrating the architecture of an LTE system and an E-UTRAN to which the disclosure may be applied.

The E-UTRAN consists of eNBs (102, 103, 104), providing the E-UTRA user plane (PDCP/RLC/MAC/PHY) and control plane (RRC) towards the UE. The eNBs (102, 103, 104) are interconnected with each other by means of the X2 interface. The eNBs are also connected to the MME (Mobility Management Entity) (105) and to the Serving Gateway (S-GW) (106) by means of the S1. The S1 interface supports a many-to-many relation between MMEs/Serving Gateways and eNBs. MME (105) and S-GW (106) may be realized either as a physical node or as separate physical nodes.

The eNB (102, 103, 104) hosts the functions listed below.

Functions for Radio Resource Management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink(scheduling); and

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

Selection of an MME at UE attachment when no routing to an MME can be determined from the information provided by the UE; and

Routing of User Plane data towards Serving Gateway; and

Scheduling and transmission of paging messages (originated from the MME).

The MME (105) hosts the functions such as NAS signaling, NAS signaling security, AS security control, S-GW selection, Authentication, Support for PWS message transmission and positioning management.

The S-GW (106) hosts the functions such as packet routing and forwarding, transport level packet marking in the uplink and the downlink, mobility anchoring for inter-eNB handover etc.

FIG. 2 is a diagram illustrating a wireless protocol architecture in an LTE system to which the disclosure may be applied.

User plane protocol stack consists of PDCP (201 or 202), RLC (203 or 204), MAC (205 or 206) and PHY (207 or 208). Control plane protocol stack consists of NAS (209 or 210), RRC (211 or 212), PDCP, RLC, MAC and PHY.

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

TABLE 5
Sublayer Functions
NAS      authentication, mobility management, security control etc
RRC      System Information, Paging, Establishment, maintenance and release of an
         RRC connection, Security functions, Establishment, configuration,
         maintenance and release of Signalling Radio Bearers (SRBs) and Data
         Radio Bearers (DRBs), Mobility, QoS management, Detection of and
         recovery from radio link failure, NAS message transfer etc.
PDCP     Transfer of data, Header compression and decompression, Ciphering and
         deciphering, Integrity protection and integrity verification, Duplication,
         Reordering and in-order delivery, Out-of-order delivery etc.
RLC      Transfer of upper layer PDUs, Error Correction through ARQ, Re-
         segmentation of RLC data PDUs,
         Concatenation/Segmentation/Reassembly of SDU, RLC re-establishment
         etc.
MAC      Mapping between logical channels and transport channels,
         Multiplexing/demultiplexing of MAC SDUs belonging to one or different
         logical channels into/from transport blocks (TB) delivered to/from the
         physical layer on transport channels, Scheduling information reporting,
         Priority handling between UEs, Priority handling between logical channels
         of one UE etc.
PHY      Channel coding, Physical-layer hybrid-ARQ processing, Rate matching,
         Scrambling, Modulation, Layer mapping, Downlink Control Information,
         Uplink Control Information etc.

FIG. 3 is a diagram illustrating the architecture of an 5G system and a NG-RAN to which the disclosure may be applied.

5G system consists of NG-RAN (301) and 5GC (302). An NG-RAN node is either:

• • a gNB, providing NR user plane and control plane protocol terminations towards the UE; or
  • an ng-eNB, providing E-UTRA user plane and control plane protocol terminations towards the UE.

The gNBs (305 or 306) and ng-eNBs (303 or 304) are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) and to the UPF (User Plane Function). AMF (307) and UPF (308) may be realized as a physical node or as separate physical nodes.

A gNB (305 or 306) or an ng-eNBs (303 or 304) hosts the functions listed below.

Functions for Radio Resource Management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink(scheduling); and

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

Selection of an AMF at UE attachment when no routing to an MME can be determined from the information provided by the UE; and

Routing of User Plane data towards UPF; and

Scheduling and transmission of paging messages; and

Scheduling and transmission of broadcast information (originated from the AMF or O&M); and

Measurement and measurement reporting configuration for mobility and scheduling; and

Session Management; and

QoS Flow management and mapping to data radio bearers; and

Support of UEs in RRC_INACTIVE state; and

Radio access network sharing; and

Tight interworking between NR and E-UTRA; and

Support of Network Slicing.

The AMF (307) hosts the functions such as NAS signaling, NAS signaling security, AS security control, SMF selection, Authentication, Mobility management and positioning management.

The UPF (308) hosts the functions such as packet routing and forwarding, transport level packet marking in the uplink, QoS handling and the downlink, mobility anchoring for mobility etc.

FIG. 4 is a diagram illustrating a wireless protocol architecture in an 5G system to which the disclosure may be applied.

User plane protocol stack consists of SDAP (401 or 402), PDCP (403 or 404), RLC (405 or 406), MAC (407 or 408) and PHY (409 or 410). Control plane protocol stack consists of NAS (411 or 412), RRC (413 or 414), PDCP, RLC, MAC and PHY.

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

TABLE 6
Sublayer Functions
NAS      authentication, mobility management, security control etc
RRC      System Information, Paging, Establishment, maintenance and release
         of an RRC connection, Security functions, Establishment,
         configuration, maintenance and release of Signalling Radio Bearers
         (SRBs) and Data Radio Bearers (DRBs), Mobility, QoS management,
         Detection of and recovery from radio link failure, NAS message
         transfer etc.
SDAP     Mapping between a QoS flow and a data radio bearer, Marking QoS
         flow ID (QFI) in both DL and UL packets.
PDCP     Transfer of data, Header compression and decompression, Ciphering
         and deciphering, Integrity protection and integrity verification,
         Duplication, Reordering and in-order delivery, Out-of-order delivery
         etc.
RLC      Transfer of upper layer PDUs, Error Correction through ARQ,
         Segmentation and re-segmentation of RLC SDUs, Reassembly of
         SDU, RLC re-establishment etc.
MAC      Mapping between logical channels and transport channels,
         Multiplexing/demultiplexing of MAC SDUs belonging to one or
         different logical channels into/from transport blocks (TB) delivered
         to/from the physical layer on transport channels, Scheduling
         information reporting, Priority handling between UEs, Priority
         handling between logical channels of one UE etc.
PHY      Channel coding, Physical-layer hybrid-ARQ processing, Rate
         matching, Scrambling, Modulation, Layer mapping, Downlink
         Control Information, Uplink Control Information etc.

FIG. 5 is a diagram illustrating the architecture of an EN-DC to which the disclosure may be applied.

E-UTRAN supports MR-DC via E-UTRA-NR Dual Connectivity (EN-DC), in which a UE is connected to one eNB (501 or 502) that acts as a MN and one en-gNB (503 or 504) that acts as a SN. The eNB (501 or 502) is connected to the EPC (505) via the S1 interface and to the en-gNB (503 or 504) via the X2 interface. The en-gNB (503 or 504) might also be connected to the EPC (505) via the S1-U interface and other en-gNBs via the X2-U interface.

LTE and NR are expected to coexist for considerable time to come. A single operator could deploy both LTE and NR within its network. For such case, providing to a UE both stable connection with LTE and high data rate with NR is possible if UE is connected to both. EN-DC enables simultaneous data transfer via LTE and NR.

In EN-DC, frequent SN change could happen due to narrow coverage of NR. SN change requires PSCell change, so they are technically synonymous. PSCell change procedure in general is consisted with that MN or S-SN get aware that PSCell change is needed, that T-SN determines the configuration of the new PSCell and that MN informs LIE the configuration of the new PSCell. Depending on a given circumstances, either immediately changing the PSCell upon receiving the PSCell configuration information or changing PSCell when certain condition is met could be appropriate. In the disclosure, the latter is 1^st reconfiguration (delayed reconfiguration or conditional reconfiguration) and the former is 2^nd reconfiguration. (or immediate reconfiguration or normal reconfiguration).

The disclosure provides operations of the terminal and the base station for the 1^st reconfiguration and for the 2^nd reconfiguration.

FIG. 6A is a diagram illustrating EN-DC operation performed by a UE and a base station according to the first embodiment of the present disclosure. FIG. 6B is a diagram illustrating another EN-DC operation performed by a UE and a base station according to the first embodiment of the present disclosure.

In 610, MN (602) decides SN change based on measurement result reported by UE (601).

MN (602) transmits, to T-SN (604), SGNB ADD REQ requesting resource allocation for the UE's EN-DC operation. SGNB ADDREQ includes following information.

• • 1^st information: Information indicating whether SGNB addition procedure is for 1^st reconfiguration or for 2^nd reconfiguration.
  • 2^nd information: It is included If 1^st reconfiguration is requested. 1^st reconfiguration execution condition and related information determined by MN. It includes execution condition and execution condition cell group IE.
  • Measurement results on T-SN's cells
  • Data radio bearer configuration related information: Information on DRBs to be established. It can be used for T-SN's call admission control.
  • Maximum data rate related information: Expected maximum data rate of the call. It can be used for T-SN's call admission control.

The 1^st information can be realized by various embodiments.

1^st reconfiguration and 2^nd reconfiguration can be distinguished by introducing new code point in SGNB Addition Trigger Indication IE. In the current specifications, SGNB Addition Trigger Indication IE is defined to indicate one of SN change, inter-eNB HO and intra-eNB HO. In this disclosure, new code point called Conditional PSCell Change is additionally defined for SGNB Addition Trigger Indication IE. If the IE indicates one of SN change, inter-eNB HO and intra-eNB HO, it is for the 2^nd reconfiguration procedure. If the IE indicates Conditional PSCell Change, it is for the 1^st reconfiguration procedure.

Alternatively, Conditional PSCell Change (CPC) IE can be introduced to indicate the 1^st reconfiguration procedure. CPC IE can indicate whether the corresponding procedure is to replace the current conditional reconfiguration or to initiate new conditional reconfiguration. Or a list of cells determined based on measurement results from UE, for example list of TCSPCELLs, can be used as the 1^st information.

In 615, T-SN (604) performs call admission control and decides whether to accept the request or not. If decide to accept, T-SN (604) sends, to MN (602), SGNB ADD REQ ACK.

The message includes information on the resource allocated to the UE, for example IE related to maximum data rate, IE related to radio bearer, logical identity to identify UE on X2 interface and Cell group configuration (CG-Config) IE. The message also includes a 3^rd information indicating whether the procedure is 1^st reconfiguration procedure or 2^nd reconfiguration procedure. The 3^rd information can be a specific cell's global identity and maximum number of Conditional PSCell Change/Addition preparations for a UE toward a target GNB.

MN (602) determines whether to perform 1^st reconfiguration procedure or 2^nd reconfiguration procedure. If MN transmitted 1^st information and 2^nd information and received 3^rd information, MN performs 1^st reconfiguration procedure. If MN did not transmit 1^st information and 2^nd information and did not receive 3^rd information, MN performs 2^nd reconfiguration procedure. If MN decides to perform 1^st reconfiguration procedure, MN proceed to 620. If MN determines to perform 2^nd reconfiguration procedure, MN proceeds to 670. Alternatively, if SGNB ADD REQ includes conditional reconfiguration request information and SGNB ADD ACK includes conditional reconfiguration response information, MN consider 1^st reconfiguration procedure is accepted and perform 1^st reconfiguration procedure. If SGNB ADD REQ does not include conditional reconfiguration request information or SGNB ADD ACK does not include conditional reconfiguration response information, MN consider 2^nd reconfiguration procedure is accepted and perform 2^nd reconfiguration procedure.

In 620, MN (602) transmits to UE (601) 1^st LTE RECNF.

The structure of LTE RECNF to configure 1^st reconfiguration for EN-DC UE is explained in FIG. 7.

In 625, UE transmits to MN 1^st LTE RECNF CMP comprising 1^st Transaction id.

Optionally, UE determines execution condition based on execution condition IE and execution condition cell group IE. The execution condition IE comprises one or two MeasID(s). The execution condition cell group IE is information indicating either master cell group (or MN) or secondary cell group (or SN). Alternatively, the information indicates only master cell group and absence of the information can be interpreted as secondary cell group being indicated. MeasID in the execution condition IE is the MeasID of the MeasConfig of the cell group indicated by execution condition cell group IE. UE considers the MeasID of the indicated cell group's MeasConfig as the execution condition. UE recognize which measurement object to measure, and which condition triggers the 1^st reconfiguration execution based on the various parameters of MeasObject associated with the MeasID and based on the various parameters of ReportConfig associated with the MeasID.

The execution condition is determined by MN or S-SN. MN or S-SN express the determined execution condition using a MeasID defined in its MeasConfig. UE needs to know which node between MN and SN sets the execution condition to recognize what the MeasID really means. In the disclosure, above information is indicated to the UE via execution condition cell group IE.

In LTE, MeasID indicating a value between 1 and 32 and MeasID-v1250 indicating a value between 33 and 64 are defined. In the disclosure, former is 5 bit measld and latter is 5 bit measld-ext. In NR, MeasID indicating a value between 1 and 64 is defined. In the disclosure, it is 6 bit measld.

MN can inform T-SN measld for execution condition via SGNB ADD REQ. MN can transform a 5 bit measld or a 5 bit measld-ext to 6 bit measld and include it in SGNB ADD REQ. If MN selects a 1^st 5 bit measld for execution condition, MN sets the MSB of 6 bit measld to 0 and sets remaining of 6 bit measld to the 1^st 5 bit measld. If MN selects a 2^nd 5 bit measld for execution condition, MN sets the MSB of 6 bit measld to 1 and sets remaining of 6 bit measld to the 2^nd 5 bit measld.

UE receives 6 bit measld for the execution condition via RECNF. If the execution condition is determined by S-SN, UE determines the execution condition without transforming 6 bit measld. If the execution condition is determined by MN, UE determines the execution condition by transforming 6 bit measld either to 1^st 5 bit measld or to 2^nd 5 bit measld.

In 630, UE performs conditional reconfiguration evaluation to determine whether condition for conditional reconfiguration is fulfilled. UE determines whether measurement result for a cell corresponding to the cell identity indicated in 3^rd NR RECNF (i.e. TCSPCELL) fulfills execution condition. If so, UE executes conditional reconfiguration by applying 2^nd NR RECNF of the cell fulfilling the execution condition.

In 635, UE performs random access procedure with T-SN. During random access procedure, UE transmits preamble to a base station, the base station transmits random access response to the UE, UE performs PUSCH (Physical Uplink Shared Channel) transmission toward the base station and the base station transmits contention resolution message to UE.

In 640, UE transmits ULIT to MN. ULIT includes 1^st NR RECNF CMP. 1^st NR RECNF CMP includes 3^rd Transaction id. If MN receives ULIT from UE with ongoing 1^st reconfiguration procedure, MN recognizes that the 1^st reconfiguration is executed and performs required actions. For example, MN forwards to T-SN 1^st NR RECNF CMP included in ULIT and initiates SGNB release procedure with S-SN.

In 645, MN transmits SGNB RECNF CMP to T-SN. The message includes 1^st NR RECNF CMP. SN recognize the 1^st NR RECNF CMP is the response to 2^nd NR RECNF from that 1^st NR RECNF CMP includes 3^rd Transaction id.

In 650, MN (602) transmits SGNB REL REQ to S-SN (603) so that required steps such as SN STATUS TRANSFER procedure can be taken place. SGNB REL REQ includes GTP tunnel information for data forwarding.

In 655, S-SN (603) receives SGNB REL REQ and starts a specific timer and transmits SGNB REL REQ ACK to T-SN (604). S-SN (603) releases the resource allocated to the UE and discard related information upon expiry of the timer.

In 660, S-SN (603) transmits to MN (602) SN STATUS TRANSFER including uplink/downlink PDCP SN and HFN. MN forward it to T-SN (604). SN STATUS TRANSFER includes HFN and PDCP SN.

T-SN (604) determines, based on SN STATUS TRANSFER, HFN and PDCP SN of downlink PDCP packet to be transmitted to UE and PDCP SN of uplink PDCP packets for which retransmission is to be requested.

In 665, S-SN (603) forwards PDCP packets to MN. MN forwards them to T-SN (604). T-SN (604) transmits those downlink PDCP packets to UE. S-SN can perform data forwarding based on PDCP COUNT of the first PDCP PDU for data forwarding.

If 2^nd reconfiguration procedure is to be performed, MN proceeds to 670 after receiving SGNB ADD ACK.

In 670, MN(602) transmits to S-SN(603) SGNB REL REQ so that S-SN(603) can initiate necessary subsequent procedures. SGNB REL REQ includes GTP tunnel information for data forwarding.

In 671, S-SN (603) receives SGNB REL REQ and starts a specific timer and transmits SGNB REL REQ ACK to T-SN (604). S-SN (603) releases the resource allocated to the UE and discard related information upon expiry of the timer.

In 675, MN (602) transmits to UE(601) 2^nd LTE RECNF.

The 2^nd LTE reconfiguration includes 5^th Transaction id and 4^th NR RECNF which includes 6^th Transaction id and PSCell configuration information. T-SN(604) generates 2^nd NR RECNF, include it in CG-Config IE and deliver it to MN via SGNB ADD ACK. MN(602) includes 2^nd NR RECNF in 2^nd LTE RECNF and transmit it to UE(601).

In 676, UE (601) receives 2^nd LTE RECNF and transmits to MN (602) 2^nd LTE RECNF CMP which includes 5^th Transaction id and 2^nd NR RECNF CMP. 2^nd NR RECNF CMP includes 6^th Transaction id. MN recognizes based on the 5^th Transaction id that the 2^nd LTE RECNF CMP is response to 2^nd LTE RECNF.

In 677, MN(602) include, in SGNB RECNF, CMP 2^nd NR RECNF CMP included in 3^rd LTE RECNF CMP and transmit it to T-SN(604). T-SN recognizes, based on 6th Transaction id, 2^nd NR RECNF CMP is response to 4^th NR RECNF. Consequently, 2^nd LTE RECNF CMP includes at least two Transaction id. One of them is used by MN and the other is forwarded to T-SN by MN and used by T-SN.

After transmitting SGNB REL REQ ACK, S-SN(603) in 685 transmits to MN(602) SN STATUS TRANSFER and MN transmits it to T-SN(604).

In 690, S-SN(603) forwards to MN downlink PDCP packets and MN forwards them to T-SN(604). T-SN(604) transmits the PDCP packets to UE.

In 678, after transmitting 3^rd LTE RECNF CMP, UE(601) performs PSCell change procedure towards the PSCell indicated in 2^nd NR RECNF at 678.

In 680, UE performs random access in the PSCell. After completion of random access, UE(601) consider PSCell change procedure is completed and resume data transfer with T-SN(604).

As disclosed above, in the 1^st procedure MN initiates SGNB RELEASE procedure after UNIT or 2^nd uplink LTE control message is received from UE. On the other hands in the 2^nd procedure, MN initiates SGNB RELEASE procedure before ULIT or 2^nd uplink LTE control message is received from UE. The reason for MN to behave differently depending on the procedure is to control such that S-SN(603) can perform operation related to data forwarding at appropriate point of time.

FIG. 7 is a diagram illustrating a structure of LTE reconfiguration message for the 1^st reconfiguration procedure

LTE RECNF includes 1^st Transaction id generated by MN and 1^st NR RECNF (702) generated by T-SN. 1^st NR RECNF includes various information depending on the purpose of the related procedure. For the 1^st reconfiguration, 1^st NR RECNF includes conditionalReconfiguration (710) which includes at least one CondReconfigToAddMod IE (703 or 720 or 721).

Each CondReconfigToAddMod IE includes conditional Reconfiguration Identity (or 2^nd NR control information identity) (704), execution condition (705), execution condition cell group (722) and 2^nd NR RECNF (706) carrying various configuration information. 2^nd NR control information identity is mandatorily present. Execution condition, 2^nd NR RECNF and execution condition cell group are optionally present. If the 2^nd NR control information identity included in the 2^nd NR control information is new identity, execution condition and 2^nd NR RECNF are mandatorily present and execution condition cell group is optionally present.

The 2^nd NR RECNF includes radio bearer configuration (708), counter for security key (709) and 3^rd NR RECNF (707). The 3^rd NR RECNF includes secondaryCellGroup IE which includes configuration information of TCSPCELL.

Therefore, a single 1^st NR RECNF for 1^st reconfiguration procedure includes plurality of TCSPCELL configuration information. Each of plurality of TCSPCELL configuration information is associated with a single execution condition IE and a single execution condition cell group IE.

The 1^st NR RECNF includes 2^nd Transaction ID, the 2^nd NR RECNF includes 3^rd Transaction ID and the 3^rd NR RECNF includes 4^th Transaction ID,

FIG. 8 is a flow diagram illustrating an operation of a master node according to the first embodiment of the present disclosure.

In 801, 1^st base station transmits to 3^rd base station (T-SN) 1^st control message related to SGNB addition. The 1^st control message can include 1^st information and 2^nd information.

In 806, 1^st base station receives from 3^rd base station 2^nd control message related to SGNB addition. The 2^nd control message can include a 3^rd information and PSCell configuration information (or target SpCell configuration information).

In 811, the 1^st base station checks whether 1^st condition is fulfilled. The 1^st base station proceeds to 816 if 1^st condition is fulfilled. The 1^st base station proceeds to 841 if 1^st condition is not fulfilled. If the 1^st base station has transmitted to 3^rd base station 1^st control information which include 1^st information and has received 2^nd control information, from the 3^rd base station in response to the 1^st control message, 1^st condition is fulfilled.

In 816, 1^st base station transmits to UE 1^st LTE RECNF which includes at least 1^st Transaction id and 1^st NR RECNF. 1^st Transaction id is determined and inserted by 1^st base station. 1^st NR RECNF is generated by 3^rd base station and transmitted to 1^st base station. 1^st NR RECNF includes at least one 2^nd Transaction id and CondReconfigMod IE.

In 821, 1^st base station receives, from UE, 1^st LTE RECNF CMP which includes 1^st Transaction id.

1^st base station checks if, from UE, ExecutionReport is received before ULIT is received. If ExecutionReport is received before ULIT, 1^st base station proceed to 831. If ULIT is received before ExecutionReport, 1^st base station proceeds to 851.

In 826, 1^st base station receives from UE ULIT which includes 1^st NR RECNF CMP and CRID. 1^st NR RECNF CMP includes at least 3^rd Transaction id. 1^st base station transmits to 3^rd base station SGNB RECNF CMP, which includes at least 1^st NR RECNF CMP.

In 831, 1^st base station and 2^nd base station performs SGNB release procedure. In the procedure, 1^st base station transmits to 2^nd base station SGNB REL REQ, 2^nd base station transmits to 1^st base station SGNB REL REQ ACK.

In 836, 1^st base station and 2^nd base station exchanges SN STATUS TRANSFER and performs data forwarding.

In 861, 1^st base station, UE and 2^nd base station complete the procedure and performs EN-DC operation.

In 841, 1^st base station and 2^nd base station performs SGNB release procedure.

In 846, 1^st base station transmits to UE 2^nd LTE RECNF which includes 5^th Transaction id and 4^th NR RECNF. 5^th Transaction id is determined and inserted by 1^st base station. 4^th NR RECNF is generated by 3^rd base station and transmitted to 1^st base station. 4^th NR RECNF includes at least 6^th Transaction id and PSCell configuration information.

In 851, 1^st base station receives from UE 3^rd LTE RECNF CMP which includes 5^th Transaction id and 4^th NR RECNF CMP. 4^th NR RECNF CMP includes at least 6th Transaction id. 1^st base station transmits to 3^rd base station SGNB RECNF CMP which includes 3^rd NR RECNF CMP.

In 856, 1^st base station and 2^nd base station exchange SN STATUS TRANSFER and perform data forwarding.

In 861, 1^st base station, UE and 2^nd base station complete the procedure and performs EN-DC operation.

FIG. 9 is a flow diagram illustrating an operation of a terminal according to the first embodiment of the present disclosure.

In 901, UE reports, to 1^st base station (MN or MeNB), UE capability related to EN-DC and 1^st reconfiguration procedure.

• • 1^st capability information: a list of band combinations supporting EN-DN
  • 2^nd capability information: a list of band combinations supporting 1^st reconfiguration and EN-DC or list of EN-DC band combinations supporting 1^st reconfiguration
  • 3^rd capability information: a list of band combinations comprising two NR bands

2^nd capability information indicates NR band of which band combination, included in the 1^st capability information, supports 1^st reconfiguration procedure. 2^nd capability information indicates intra-band 1^st reconfiguration support.

3^rd capability information is list of band combinations with two NR bands and each band combination indicates inter-band 1^st reconfiguration is supported between the NR bands. For example, if (N1, N2) is included in 3^rd capability information, inter-band 1^st reconfiguration between N1 and N2 is supported. NR bands included in the band combinations of 3^rd capability information are the NR bands supporting EN-DC.

A base station to which UE reports its capability, a base station from which UE receives LTE RECNF and a base station with which UE performs random access can be different base stations. The reason is because the capability reported by UE is stored in the core network and capability reporting is performed in the initial registration and not performed afterward.

In 906, UE receives LTE RECNF. The LTE RECNF includes 1^st NR RECNF. The 1^st NR RECNF includes 1^st information if the 1^st NR RECNF is for 1^st reconfiguration. The 1^st information includes at least one 2^nd information. In the 2^nd information, a 3^rd information and a 4^th information are mandatorily present, and a 5^th information is optionally present. Information from the 1^st information to the 5^th information are those defined between UE and base station. They are different from the 1^st information to the 3^rd information defined between MN and T-SN.

A 2^nd information corresponds to a TCSPCELL. A 3^rd information comprising one or two MeasID defines the execution condition for the TCSPCELL. A 4^th information is the 2^nd NR RECNF which includes radio bearer configuration, security key information and 3^rd NR RECNF for the configuration information of TCSPCELL. 5^th information indicates for which between MCG and SCG (or between MeNB and SgNB or between MN and S-SN) the execution condition is related to.

Each 3^rd information and each 5^th information define the execution condition for each associated TCSPCELL (or associated 2^nd information). Alternatively, it is also possible to define a common 3^rd information and a common 5^th information applicable to all TCSPCELL (or all 2^nd information) included in the 1^st NR RECNF. It is possible to define he common 3^rd information and the common 5^th information as sub-IE of 1^st information. Then UE ignores individual 3^rd information included under 2^nd information. UE applies common 3^rd information, if present, to all TCSPCELLs included in 1^st information. Otherwise, UE applies the 3^rd information included for each TCSPCELL.

A single LTE RECNF includes a single 1^st NR RECNF. A single 1^st NR RECNF includes plurality of 2^nd NR RECNFs. A single 2^nd NR RECNF includes a single 3^rd NR RECNF. Therefore, a single LTE RECNF includes a plurality of 3^rd NR RECNFs, a plurality of 3^rd information, a plurality of 4^th information and a plurality of 5^th information. The number of 3^rd NR RECNFs, the number of 3^rd information and the number of 4^th information are same while the number of 5^th information may be different.

A single RECNF includes a single Transaction id. The LTE RECNF includes 1^st Transaction id. The 1^st NR RECNF includes 2^nd Transaction id. The 2^nd NR RECNF includes 3^rd Transaction id. The 3^rd NR RECNF includes 4^th Transaction id.

In 911, UE transmits LTE RECNF CMP to the 1^st base station. The LTE RECFN CMP includes 1^st Transaction id.

In 916, UE initiates 1^st reconfiguration if 1^st reconfiguration information is included in 1^st NR RECNF in 1^st LTE RECNF received by UE

In 921, UE determines, based on 3^rd information and 5^th information, to which cell group (or which node) MeasID indicated in the 3^rd information is related. If 5^th information is absent, UE determines that execution condition for the corresponding TCSPCELL is set by S-SN and that the MeasID is related to source SCG (or S-SN). UE interprets MeasID according to MeasConfig of source SCG (or S-SN). If 5^th information is present, UE determines that execution condition for the corresponding TCSPCELL is set by MN and that the MeasID is related to MCG (or MN). UE interprets MeasID according to MeasConfig of MCG (or MN). Alternatively, if 5^th information is present, UE determines that execution condition for the corresponding TCSPCELL is set by a CG (or by a node) between MCG and SCG (or between MN and S-SN) and UE interprets MeasID according to the MeasConfig of determined CG (or determined node).

In LTE, MeasID indicating a value between 1 and 32 and MeasID-v1250 indicating a value between 33 and 64 are defined. In the disclosure, former is 5 bit measld and latter is 5 bit measld-ext. In NR, MeasID indicating a value between 1 and 64 is defined. In the disclosure, it is 6 bit measld.

MN can inform T-SN measId for execution condition via SGNB ADD REQ. MN can transform a 5 bit measId or a 5 bit measId-ext to 6 bit measId and include it in SGNB ADD REQ. If MN selects a 5 bit measId for execution condition, MN sets the MSB of 6 bit measId to 0 and sets remaining of 6 bit measId to the 5 bit measId. If MN selects a 5 bit measId-Ext for execution condition, MN sets the MSB of 6 bit measId to 1 and sets remaining of 6 bit measId to the 5 bit measId-Ext.

UE receives 6 bit measId for execution condition in RECNF. If the execution condition is determined by S-SN, UE determines the execution condition with 6 bit measId as it is. If the execution condition is determined by MN, UE determines the execution condition with 5 bit measId or 5 bit measId-Ext transformed from 6 bit measId. If MSB of 6 bit measId is 0, UE takes the remaining 5 bit aslst 5 bit measId and selects associated ReportConfig and MeasObject accordingly. If MSB of 6 bit measId is 1, UE takes the remaining 5 bit as 5 bit measId-Ext and selects associated ReportConfig and MeasObject accordingly.

In 926, UE performs conditional reconfiguration evaluation. For each 2^nd information included in 1^st information, UE considers the serving cell indicated in 3^rd NR RECNF of 2^nd information (i.e. target candidate cell) as applicable cell. UE consider the target candidate cell as a triggered cell if event associated with the trigger condition for the cell is fulfilled.

In 931, UE executes conditional reconfiguration. UE apply the 2^nd NR RECNF for the triggered cell.

In 936, UE transmits to 2^nd base station ULIT. ULIT includes 1^st NR RECNF CMP. 1^st NR RECNF CMP includes 3^rd Transaction id. ULIT also includes CRID corresponding to triggered cell (or 2^nd NR RECFN corresponding to triggered cell)

FIG. 10 is a block diagram illustrating the internal structure of a UE to which the disclosure is applied.

Referring to the diagram, the UE includes a controller (1001), a storage unit (1002), a transceiver (1003), a main processor (1004) and I/O unit (1005).

The controller (1001) controls the overall operations of the UE in terms of mobile communication. For example, the controller (1001) receives/transmits signals through the transceiver (1003). In addition, the controller (1001) records and reads data in the storage unit (1002). To this end, the controller (1001) includes at least one processor. For example, the controller (1001) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls the upper layer, such as an application program. The controller controls storage unit and transceiver such that UE operations illustrated in FIG. 9 is performed.

The storage unit (1002) stores data for operation of the UE, such as a basic program, an application program, and configuration information. The storage unit (1002) provides stored data at a request of the controller (1001).

The transceiver (1003) consists of a RF processor, a baseband processor and plurality of antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up—converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down—converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital—to—analog converter (DAC), an analog—to—digital converter (ADC), and the like. The RF processor may perform MIMO and may receive multiple layers when performing the MIMO operation. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the system. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.

The main processor (1004) controls the overall operations other than mobile operation. The main processor (1004) process user input received from I/O unit (1005), stores data in the storage unit (1002), controls the controller (1001) for required mobile communication operations and forward user data to I/O unit (1005).

I/O unit (1005) consists of equipment for inputting user data and for outputting user data such as a microphone and a screen. I/O unit (1005) performs inputting and outputting user data based on the main processor's instruction.

FIG. 11 is a block diagram illustrating the configuration of a base station according to the disclosure.

As illustrated in the diagram, the base station includes a controller (1101), a storage unit (1102), a transceiver (1103) and a backhaul interface unit (1104).

The controller (1101) controls the overall operations of the main base station. For example, the controller (1101) receives/transmits signals through the transceiver (1103), or through the backhaul interface unit (1104). In addition, the controller (1101) records and reads data in the storage unit (1102). To this end, the controller (1101) may include at least one processor. The controller controls transceiver, storage unit and backhaul interface such that base station operation illustrated in FIG. 8 are performed.

The storage unit (1102) stores data for operation of the main base station, such as a basic program, an application program, and configuration information. Particularly, the storage unit (1102) may store information regarding a bearer allocated to an accessed UE, a measurement result reported from the accessed UE, and the like. In addition, the storage unit (1102) may store information serving as a criterion to deter mine whether to provide the UE with multi—connection or to discontinue the same. In addition, the storage unit (1102) provides stored data at a request of the controller (1101).

The transceiver (1103) consists of a RF processor, a baseband processor and plurality of antennas. The RF processor performs functions for transmitting/receiving signals through a wireless channel, such as signal band conversion, amplification, and the like. Specifically, the RF processor up—converts a baseband signal provided from the baseband processor into an RF band signal, transmits the same through an antenna, and down—converts an RF band signal received through the antenna into a baseband signal. The RF processor may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. The RF processor may perform a down link MIMO operation by transmitting at least one layer. The baseband processor performs a function of conversion between a baseband signal and a bit string according to the physical layer specification of the first radio access technology. For example, during data transmission, the baseband processor encodes and modulates a transmission bit string, thereby generating complex symbols. In addition, during data reception, the baseband processor demodulates and decodes a baseband signal provided from the RF processor, thereby restoring a reception bit string.

The backhaul interface unit (1104) provides an interface for communicating with other nodes inside the network. The backhaul interface unit (1104) converts a bit string transmitted from the base station to another node, for example, another base station or a core network, into a physical signal, and converts a physical signal received from the other node into a bit string.

Claims

1. A method performed by a Master Node (MN), the method comprising; transmitting, by the MN, to a target Secondary Node (SN) a first base station control message requesting resource allocation;receiving, by the MN, from the target SN a second base station control message accepting request,determining, by the MN, to perform a 1st reconfiguration procedure or a 2nd reconfiguration procedure;performing, by the MN, the 1st reconfiguration procedure in response to MN receiving a 2nd information;performing, by the MN, the 2nd reconfiguration procedure in response to MN not receiving the 2nd information;transmitting, by the MN in response to MN determining to perform the 1st reconfiguration procedure, to a terminal a first Downlink (DL) message, wherein the first DL message includes a first identifier and one or more CondReconfigToAddMod, wherein each of the one or more CondReconfigToAddMod includes an execution condition, a second identifier, and a reconfiguration message, wherein the first identifier is a transaction identifier and the second identifier is a conditional reconfiguration identifier;receiving, by the MN, from the terminal a first Uplink (UL) message, wherein the first UL message includes the first identifier; andtransmitting, by the MN, to a source SN a third base station control message after a second UL message is received from the terminal, wherein the second UL message includes the second identifier, wherein the second identifier corresponds to the reconfiguration message in the CondReconfigToAddMod, wherein the second UL message is received after the first UL message is received, and wherein the third base station control message requests release of the source SN,wherein 1st information is comprised in the first base station control message in case that the 1st reconfiguration procedure is requested,wherein the 2nd information comprises a specific cell's global identity.

2. The method of claim 1, wherein the first base station control message further includes measurement results for the second base station.

3. The method of claim 1, wherein the first base station control message includes first information indicating that a first reconfiguration procedure is requested.

4. The method of claim 3, wherein the first reconfiguration is conditional PSCell addition.

5. The method of claim 3, wherein the first information includes assistance information for the second base station to determine resource for the terminal.

6. The method of claim 1, wherein the first base station control message further includes Data Radio Bearer (DRB) configuration of a one or more DRBs.

7. The method of claim 1, further comprising: receiving from the target SN a second base station control message in response to the first base station control message.

8. The method of claim 7, wherein the second base station control message includes second information in response that first information was included in the first base station control message.

9. The method of claim 8, wherein the second information includes a cell global identifier of a specific cell for a first reconfiguration procedure.

10. The method of claim 8, wherein the second information includes information related to a plurality of PSCells.

11. The method of claim 7, wherein the second base station control message includes Cell Group configuration.

12. The method of claim 11, wherein the Cell Group configuration includes the reconfiguration message.

13. The method of claim 11, wherein the Cell Group configuration further includes: information related to Secondary Cell Group bearer; andDiscontinuous Reception configuration of Secondary Cell Group.

14. The method of claim 1, wherein the first DL message includes a parameter for execution condition.

15. The method of claim 1, wherein the first DL message further includes a parameter indicate the execution condition is related to measurement configuration of Secondary Cell Group.

16. The method of claim 15, wherein the parameter for execution condition is determined by the source SN.

17. The method of claim 1, further comprising: transmitting to the target SN a third base station control message, wherein the third base station control message includes the second UL message.

18. The method of claim 1, wherein: the first UL message is not forwarded to the first SN; andthe second UL message is forwarded to the first SN.

19. The method of claim 1, further comprising: transmitting to the target SN a fourth base station control message, wherein the fourth base station control message includes Packet Data Convergence Protocol (PDCP) sequence number, and wherein data forwarding is performed based on the PDCP sequence number.

20. A Master Node (MN) in a wireless communication system, the MN comprising: a transceiver configured to transmit and receive a signal; anda controller configured to control the transceiver to:transmit to a target Secondary Node (SN) a first base station control message requesting resource allocation;receive from the target SN a second base station control message accepting request,determine to perform a 1st reconfiguration procedure or a 2nd reconfiguration procedure;perform the 1st reconfiguration procedure in response to MN receiving a 2nd information;perform the 2nd reconfiguration procedure in response to MN not receiving the 2nd information;transmit, in response to MN determining to perform the 1st reconfiguration procedure, to a terminal a first Downlink (DL) message, wherein the first DL message includes a first identifier and one or more CondReconfigToAddMod, wherein each of the one or more CondReconfigToAddMod includes an execution condition, a second identifier, and a reconfiguration message, wherein the first identifier is a transaction identifier and the second identifier is a conditional reconfiguration identifier;receive from the terminal a first Uplink (UL) message, wherein the first UL message includes the first identifier; andtransmit to a source SN a third base station control message after a second UL message is received from the terminal, wherein the second UL message includes the second identifier, wherein the second identifier corresponds to the reconfiguration message in the CondReconfigToAddMod, wherein the second UL message is received after the first UL message is received, and wherein the third base station control message requests release of the source SN,wherein 1st information is comprised in the first base station control message in case that the 1 st reconfiguration procedure is requested,wherein the 2nd information comprises a specific cell's global identity.