KR20180081649A - Methods and Apparatuses for controlling Multi-connectivity-based mobility - Google Patents

Abstract

The present invention relates to a method and apparatus for changing a base station based on a plurality of connections to a terminal in a next generation radio access network, and processing related data. In addition, the present invention provides a method and apparatus for processing data. It is possible to process data effectively by minimizing an interruption on a change procedure between a master base station and a secondary base station in a multi-connectivity environment.

Description

[0001] The present invention relates to a multi-connectivity-based mobility control method and apparatus,

And more particularly, to a method and apparatus for changing a base station based on a plurality of connections to a terminal in a next generation radio access network and a data processing method and apparatus related thereto.

The present invention relates to a method and apparatus for efficiently processing data that minimizes an interruption on a change procedure between a master base station and a secondary base station in a multi-connectivity environment in a data processing method.

1 is an exemplary diagram illustrating an SeNB addition procedure.
2 is a diagram illustrating an example of an MC-based inter-base station change procedure according to the present invention.
3 is a diagram showing another example of an MC-based inter-base station change procedure according to the present invention.
4 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
5 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

Herein, the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement. In this specification, the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement. Alternatively, the MTC terminal may refer to a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.

In other words, the MTC terminal in this specification may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC-related operations. Alternatively, the MTC terminal may support enhanced coverage over the existing LTE coverage or a UE category / type defined in the existing 3GPP Release-12 or lower that supports low power consumption, or a newly defined Release-13 low cost low complexity UE category / type.

The wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data and the like. A wireless communication system includes a user equipment (UE) and a base station (BS, or eNB). The user terminal in this specification is a comprehensive concept of a terminal in wireless communication. It is a comprehensive concept which means a mobile station (MS), a user terminal (UT), an SS (User Equipment) (Subscriber Station), a wireless device, and the like.

A base station or a cell generally refers to a station that communicates with a user terminal and includes a Node-B, an evolved Node-B (eNB), a sector, a Site, a BTS A base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell.

That is, the base station or the cell in this specification is interpreted as a comprehensive meaning indicating a partial region or function covered by BSC (Base Station Controller) in CDMA, NodeB in WCDMA, eNB in LTE or sector (site) And covers various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, and small cell communication range.

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. i) the device itself providing a megacell, macrocell, microcell, picocell, femtocell, small cell in relation to the wireless region, or ii) indicating the wireless region itself. i indicate to the base station all devices that are controlled by the same entity or that interact to configure the wireless region as a collaboration. An eNB, an RRH, an antenna, an RU, an LPN, a point, a transmission / reception point, a transmission point, a reception point, and the like are exemplary embodiments of a base station according to a configuration method of a radio area. ii) may indicate to the base station the wireless region itself that is to receive or transmit signals from the perspective of the user terminal or from a neighboring base station.

Therefore, a base station is collectively referred to as a base station, collectively referred to as a megacell, macrocell, microcell, picocell, femtocell, small cell, RRH, antenna, RU, low power node do.

Herein, the user terminal and the base station are used in a broad sense as the two transmitting and receiving subjects used to implement the technical or technical idea described in the present specification, and are not limited by a specific term or word. The user terminal and the base station are used in a broad sense as two (uplink or downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, and are not limited by a specific term or word. Here, an uplink (UL, or uplink) means a method of transmitting / receiving data to / from a base station by a user terminal, and a downlink (DL or downlink) .

There are no restrictions on multiple access schemes applied to wireless communication systems. Various multiple access schemes such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), OFDM-FDMA, OFDM- Can be used. An embodiment of the present invention can be applied to asynchronous wireless communication that evolves into LTE and LTE-advanced via GSM, WCDMA, and HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. The present invention should not be construed as limited to or limited to a specific wireless communication field and should be construed as including all technical fields to which the idea of the present invention can be applied.

A TDD (Time Division Duplex) scheme in which uplink and downlink transmissions are transmitted using different time periods, or an FDD (Frequency Division Duplex) scheme in which they are transmitted using different frequencies can be used.

In systems such as LTE and LTE-advanced, a standard is constructed by configuring uplink and downlink based on a single carrier or carrier pair. The uplink and the downlink are divided into a Physical Downlink Control Channel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel, a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control Channel (EPDCCH) Transmits control information through the same control channel, and is configured with data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel), and transmits data.

On the other hand, control information can also be transmitted using EPDCCH (enhanced PDCCH or extended PDCCH).

In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .

The wireless communication system to which the embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-point transmission / reception system in which two or more transmission / reception points cooperatively transmit signals. antenna transmission system, or a cooperative multi-cell communication system. A CoMP system may include at least two multipoint transmit and receive points and terminals.

The multi-point transmission / reception point includes a base station or a macro cell (hereinafter referred to as 'eNB'), and at least one mobile station having a high transmission power or a low transmission power in a macro cell area, Lt; / RTI >

Hereinafter, a downlink refers to a communication or communication path from a multipoint transmission / reception point to a terminal, and an uplink refers to a communication or communication path from a terminal to a multiple transmission / reception point. In the downlink, a transmitter may be a part of a multipoint transmission / reception point, and a receiver may be a part of a terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.

Hereinafter, a situation in which a signal is transmitted / received through a channel such as PUCCH, PUSCH, PDCCH, EPDCCH, and PDSCH is expressed as 'PUCCH, PUSCH, PDCCH, EPDCCH and PDSCH are transmitted and received'.

In the following description, an indication that a PDCCH is transmitted or received or a signal is transmitted or received via a PDCCH may be used to mean transmitting or receiving an EPDCCH or transmitting or receiving a signal through an EPDCCH.

That is, the physical downlink control channel described below may mean a PDCCH, an EPDCCH, or a PDCCH and an EPDCCH.

Also, for convenience of description, EPDCCH, which is an embodiment of the present invention, may be applied to the portion described with PDCCH, and EPDCCH may be applied to the portion described with EPDCCH according to an embodiment of the present invention.

Meanwhile, the High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.

The eNB performs downlink transmission to the UEs. The eNB includes a physical downlink shared channel (PDSCH) as a main physical channel for unicast transmission, downlink control information such as scheduling required for reception of a PDSCH, A physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission in a Physical Uplink Shared Channel (PUSCH). Hereinafter, the transmission / reception of a signal through each channel will be described in a form in which the corresponding channel is transmitted / received.

In the conventional LTE (3GPP E-UTRAN), a service interruption occurs in a handover process of disconnecting a source cell and connecting a target cell. A longer downtime due to handover negatively affects the user experience. It is known that the downtime due to handover over the actual LTE network frequently occurs more than 50ms. In the next generation radio access network (NR), which is considered to be in operation after 3GPP Release 14, it may be required to be designed to satisfy 0 ms interruption for intra-NR mobility. To this end, it is necessary to improve the existing LTE mobility technology.

One of LTE's mobility enhancement technologies is dual connectivity technology. Dual connectivity is defined as the operating mode of a connected state terminal, which consists of a group of cells associated with two base stations. A dual capable capable mobile station can simultaneously transmit and receive to both the master base station and the secondary base station. For multiple RX / TX terminals in the RRC Connected state, the dual connectivity operation is configured to utilize the radio resources provided by two different schedulers located connected to two base stations connected via a non-ideal backhaul.

An SeNB addition procedure is used to set the terminal context to the SeNB in order to provide the terminal with radio resources from the SeNB.

Figure 1 shows the SeNB additional procedure.

The operations of FIG. 1 are as follows.

One. The MeNB decides to request the SeNB to allocate radio resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters corresponding to the UP option). In addition, MeNB indicates within SCG-ConfigInfo the MCG configuration (including security algorithm for SCG bearer) and the entire UE capabilities for UE reconfiguration on the basis of the reconfiguration by the SeNB, but does not include the SCG configuration. The MeNB can provide the latest measurement results for the SCG cell (s) requested to be added. The SeNB may reject the request.

2. If the RRM entity in the SeNB is able to admit the resource request, it allocates the respective radio resources and, depending on the bearer option, the respective transport network resources. The SeNB triggers Random Access so that synchronization of the SeNB radio resource configuration can be performed. The SeNB provides the new radio resource of SCG in SCG-Config to the MeNB. For SCG bearers, together with S1 DL TNL address information for the respective E-RAB and security algorithms, for split bearers.

3. If the MeNB endorses the new configuration, the MeNB sends the RRCConnectionReconfiguration message to the UE including the new radio resource configuration of the SCG-Config.

4. The UE applies the new configuration and replies with RRCConnectionReconfigurationComplete message. In case the UE does not comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure.

5. The MeNB informs the SeNB that the UE has completed the reconfiguration procedure successfully.

6. The UE performs synchronization towards the PSCell of the SeNB. The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure to the SCG is not defined. The RRC Connection Reconfiguration procedure is not successful.

7./8. In case of SCG bearers, and depending on the characteristics of the respective E-RAB, the MeNB may take actions to minimize service interruption due to activation of dual connectivity (data forwarding, SN status transfer).

9.-12. For SCG bearers, the update of the EPC is performed.

NR can support multi-connectivity similar to dual connectivity. The multi-connectivity may be defined as a mode of operation of a UE for using radio resources configured by an LTE base station and / or a NR base station (Multi-Connectivity: a multiple Rx / Tx UE in the connected mode is configured to utilize radio resources amongst E-UTRA and / or NR provided by multiple distinct schedulers connected via non-ideal backhaul.

Conventional dual connectivity typically assumed a master base station providing a macro cell and a secondary base station providing a small cell. That is, in the environment where the macro cell coverage and the small cell coverage are overlapped, the UE can perform dual connection operation with two base stations. Therefore, there is no need to change between the master base station and the secondary base station, since the UE having the dual connectivity can be out of the coverage of the secondary base station before departing from the coverage of the master base station or out of coverage of the two base stations at the same time.

However, in a scenario where dual connectivity technology is used for additional handover improvement in an LTE environment or multi-connectivity technology is applied in an NR environment, a change procedure between a master base station and a secondary base station may be required. However, no concrete method was suggested. In addition, if the handover is performed based on the multi-connectivity based on the multi-connectivity based on the multi-connectivity, the security is updated according to the cell change.

As described above, in a scenario where the dual connectivity technique is used for additional handover improvement in the LTE environment or the multi-connectivity technique is applied in the NR environment, a change procedure between the master base station and the secondary base station may be required. But there was no concrete way to do this. Also, in this process, the security between the terminal and the base station must be updated and used, but no specific method has been provided.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a specific method for changing procedures between a master base station and a secondary base station in a multi-connectivity environment. It is another object of the present invention to provide an efficient data processing method and apparatus that minimizes an interruption on a change procedure between a master base station and a secondary base station in a multi-connectivity environment.

For example, as the terminal having dual connectivity moves to the coverage edge of the master base station according to the movement, the current master base station can change the role of the current secondary base station and the base station. As another example, the current master base station can change the role of the current secondary base station and the base station according to the state change of the base station, with respect to the terminal configured with dual connectivity. In another example, the base station may wish to perform dual connectivity based mobility control. It is possible to perform a handover that minimizes the interruption by performing the handover from the source cell to the target cell based on the dual connectivity. A DC-capable terminal can simultaneously transmit and receive to two base stations. Thus, data transmission can be performed with minimal interruption.

Hereinafter, for convenience of description, a change procedure between the base stations for a multi-connectivity capable terminal or a procedure for changing a multi-connectivity-based base station or a procedure for providing a dual connectivity based mobility is described as a change procedure between MC-based base stations. This is for convenience only and may be replaced by another name.

Based on the change between the MC-based BSs, the MS must change the RRC connection with the existing master BS. For example, the existing secondary base station should be changed to a new master base station by changing / modifying / setting / resetting / maintaining / reconfiguring the RRC connection. The existing secondary base station must generate a terminal configuration for operating as a new master base station and instruct it to the terminal. Hereinafter, a specific method for this will be described. The methods described below may be used individually or in combination / combination.

For convenience of description, the source base station, the old master base station, the old MeNB, and the new SeNB are denoted as the source base station in the MC-based base station change. Source MCell, old MCG PCell, and old MCG PCell, which are connected to the source base station, source PCell, source base station PCell, old MCG, old MCN, Can mean PCell. For convenience of description, the target base station, the old secondary base station, the old SeNB, and the new MeNB will be referred to as target base stations in the following description. A target MCell, a new MCG cell, and a new MCG PCell as target cells, and a cell associated with the target BS, a target PCell, and a target base station PCell It can mean.

How to send RRC connection confirmation directly to a new master base station

2 shows an example of an MC-based inter-base station change procedure according to the present invention. Hereinafter, this will be described in detail.

1. The source base station determines the change between MC based base stations.

2. The source base station issues an inter-base station interface message on the target side to send the necessary information to prepare for a change between MC based base stations. The source base station indicates the source base station configuration to be used as a basis for the reconfiguration by the target base station and the entire terminal capability. The inter-base station interface message for sending the necessary information to prepare for the change between the MC-based base stations described above includes a target cell ID, a new key value of the target base station, an RRC context, an AS-configuration, an E-RAB (or a 5G PDN / ) Context, the physical cell ID of the source cell, and short MAC-I.

3. The target base station constructs necessary resources according to the received radio bearer QoS information. The target base station prepares to change between MC based base stations via L1 / L2. And transmits a request confirmation message to the source base station. This message includes a container to be sent to the terminal as an RRC message for performing a change between MC-based base stations. For example, the target base station may include information for instructing the terminal to make a change between MC-based base stations. The target base station provides the Xn DL TNL address information for the source base split bearer.

4. If the source base station grants the new configuration, the source base station sends an RRC connection reconfiguration message containing the new radio resource configuration to the terminal.

5/6. The terminal applies the new configuration. And transmits an RRC connection acknowledgment to the old secondary base station, which becomes a new master base station.

If the received RRC connection reconfiguration message contains synchronization indication information for the previous secondary base station cell, the terminal performs synchronization with the target base station cell (or the PCcell of the target base station or the PSCell of the target base station). Otherwise step 5 may be omitted.

The concrete operation of the UE receiving the RRC connection reconfiguration message instructing the change between the MC-based BSs will be described later.

7. The target base station transmits a path change request message to the core network control plane entity (or an anchor base station if there is an anchor base station, hereinafter referred to as a core network control plane entity, but an anchor base station is also included in the scope of the present invention). And informs that the master base station of the terminal has been changed.

8. The core network control plane entity sends a user plane tunnel / flow / bearer modification request message to the core network user plane entity.

9. The core network user plane entity switches the downlink data path to the target side. The core network user plane entity sends one or more "end-marker" packets to the source base station on the previous path. And can release user plane resources to the source base station.

The core network user plane entity sends a user plane tunnel / flow / bearer modification response message to the core network control plane entity.

10. The core network control plane entity sends a path change request confirmation message to the target base station.

Hereinafter, the SN state transmission will be described. For convenience of explanation, FIG. 2 will be described, but it can be applied to FIG. 3 as well as FIG. In the prior art, the SN state transmission is performed after the source base station receives the handover request acknowledgment from the target base station or the master base station confirms the completion of the configuration for the dual connectivity configuration from the terminal and instructs the secondary base station to complete the reconfiguration.

However, in the case of changing between MC-based base stations, the DC-capable UE can perform transmission and reception simultaneously to two base stations. Thus, if a target base station connection is created, if a target base station MAC is created and a target base station radio bearer entity is created, data transmission can be performed with minimum interruption through two paths. Otherwise, if the target base station connection is already created with the secondary connection, the reconfiguration of the source base station radio bearer entity and the target base station radio bearer entity enables data transmission with minimal interruption through two paths through two paths have.

Therefore, the source base station first stops the data transmission and does not need to forward it to the target base station. After reconfiguration of the two radio paths is completed, the SN state transmission is performed, or during the path switching of the core network ) SN state transmission.

For example, in step 9 described above, the source base station receiving the " end-marker " packet from the core network user plane entity may perform the SN state transmission. Thereby transmitting an uplink PDCP SN receiver state and a downlink PDCP SN transmission state to a radio bearer to which PDCP state preservation is applied. The uplink PDCP SN receiver state may include a bitmap of the reception state of the PDCP SN of at least the first missing UL SDU and the out of sequence UL SDUs that the terminal needs to retransmit in the target cell. The downlink PDCP SN transmission state may indicate a next PDCP SN to be allocated to new SDUs for which the target base station does not yet have a PDCP SN.

The source base station may perform data forwarding to the target base station

As another example, the target base station receiving data from the terminal in step 5 or step 6 may send a notification message to the source base station. The source base station can perform the SN state transmission. Thereby transmitting an uplink PDCP SN receiver state and a downlink PDCP SN transmission state to a radio bearer to which PDCP state preservation is applied.

MC based mobility control method

3 shows another example of an MC-based inter-base station change procedure according to the present invention. Hereinafter, this will be described in detail.

1. The source base station decides to change between MC based base stations (MC based handover).

2. The source base station issues an inter-base station interface message on the target side to send the necessary information to prepare for a change between MC based base stations. The source base station indicates the source base station configuration to be used as a basis for the reconfiguration by the target base station and the entire terminal capability. The inter-base station interface message for sending the necessary information to prepare for the change between the MC-based base stations described above includes a target cell ID, a new key value of the target base station, an RRC context, an AS-configuration, an E-RAB (or a 5G PDN / ) Context, the physical cell ID of the source cell, and short MAC-I.

3. The target base station constructs necessary resources according to the received radio bearer QoS information. The target base station prepares to change between MC based base stations via L1 / L2. And transmits a request confirmation message to the source base station. This message includes a container to be sent to the mobile station in an RRC message for performing MC-based BS change. The target BS can provide the Xn DL TNL address information for the source base station split bearer. The target base station may provide core network interface DL TNL address information for the target base station split bearer. The target base station can configure the SRB between the target base station and the terminal for the direct RRC signaling through the air interface between the target base station and the terminal. To this end, the UE may include target base station SRB configuration information for RRC message transmission to the target base station.

4. If the source base station grants the new configuration, the source base station sends an RRC connection reconfiguration message containing the new radio resource configuration to the terminal. As an example, the source base station may generate and include information for instructing the terminal to make a change between MC based base stations.

5. The terminal applies the new configuration. And sends an RRC connection acknowledgment to the source base station.

The concrete operation of the UE receiving the RRC connection reconfiguration message instructing the change between the MC-based BSs will be described later.

6. The source base station informs the target base station that the terminal has successfully performed the reconfiguration procedure.

7. If the received RRC reconnection message contains synchronization indication information to the previous secondary base station cell, the terminal performs synchronization with the target base station cell (or the target base station's PCcell or target base station's PSCell). Otherwise step 7 may be omitted.

8. The target base station transmits the path change request message to the core network control plane entity (or an anchor base station if there is an anchor base station, hereinafter referred to as a core network control plane entity, but an anchor base station is also included in the scope of the present invention). And informs that the master base station of the terminal has been changed.

9. The core network control plane entity sends a user plane tunnel / flow / bearer modification request message to the core network user plane entity.

10. The core network user plane entity switches the downlink data path to the target side. The core network user plane entity sends one or more "end-marker" packets to the source base station on the previous path. And can release user plane resources to the source base station.

The core network user plane entity sends a user plane tunnel / flow / bearer modification response message to the core network control plane entity.

11. The core network control plane entity sends a path change request confirmation message to the target base station.

Hereinafter, the SN state transmission will be described. In the prior art, the SN state transmission is performed after the source base station receives the handover request acknowledgment from the target base station or the master base station confirms the completion of the configuration for the dual connectivity configuration from the terminal and instructs the secondary base station to complete the reconfiguration.

However, in the case of changing between MC-based base stations, the DC-capable UE can perform transmission and reception simultaneously to two base stations. Therefore, if the target base station connection is generated, when the target base station MAC is generated and the target base station radio bearer entity is created, the handover can be performed while minimizing the interruption through the two paths. Otherwise, in a state where the target base station connection is generated by the secondary connection, handover can be performed while minimizing the interruption through reconstruction (or release of the source base station radio resource) of the source base station radio bearer entity and the target base station radio bearer entity.

Therefore, it is possible to perform the SN state transmission after the reconfiguration of the two radio paths is completed, without the source base station first stopping the data transmission and forwarding to the target base station, or after the source base station radio resource release is completed SN state transmission during the release of the core network, or to perform the SN state transmission during the path switch of the core network (or after the path switch of the core network).

For example, in step 10 described above, the source base station receiving the " end-marker " packet from the core network user plane entity may perform the SN state transmission. Thereby transmitting an uplink PDCP SN receiver state and a downlink PDCP SN transmission state to a radio bearer to which PDCP state preservation is applied. The uplink PDCP SN receiver state may include a bitmap of the reception state of the PDCP SN of at least the first missing UL SDU and the out of sequence UL SDUs that the terminal needs to retransmit in the target cell. The downlink PDCP SN transmission state may indicate a next PDCP SN to be allocated to new SDUs for which the target base station does not yet have a PDCP SN.

The source base station may perform data forwarding to the target base station

As another example, the target base station receiving the data from the terminal in step 5 may send a notification message to the source base station. The source base station can perform the SN state transmission. Thereby transmitting an uplink PDCP SN receiver state and a downlink PDCP SN transmission state to a radio bearer to which PDCP state preservation is applied.

As another example, the target base station receiving the data from the terminal in step 5 or step 7 described above may send a notification message to the source base station. The source base station can perform the SN state transmission. Thereby transmitting an uplink PDCP SN receiver state and a downlink PDCP SN transmission state to a radio bearer to which PDCP state preservation is applied.

As another example, the source base station that has received the release instruction from the target base station may instruct the terminal to release the source base station. And the source base station can perform the SN state transmission.

Hereinafter, the operation of the terminal receiving the RRC connection reconfiguration message will be described. This can be applied to the embodiment in Fig. 2 or Fig. This can also be applied to other embodiments other than FIG. 2 or FIG.

1) When the source base station and the target base station are dual When configured with connectivity

The case where the source base station and the target base station are configured with dual connectivity before receiving the RRC message will be described.

The MS receiving the RRC connection reconfiguration message including the radio resource configuration indicating the change between the MC-based BS performs the following operation.

The MS receiving the information indicating the change between the MC-based BSs may allow the MS to maintain the source BS / cell connection until a certain point in time.

The MS may consider the target BS cell (PSCell) as PCell at another specific time.

The UE reconfigures the PDCP entity with the target base station security configuration according to the PDCP configuration

The specific point in time or another specific point in time may include receiving an RRC reconfiguration message from the source base station, receiving a RRC message different from the RRC reconfiguration message received from the target base station, receiving a MAC CE from the target base station, After receiving the end market from the core network user plane path switching, it receives from the target base station, receives the PDCP control PDU of the target base station, and receives the end market from the core network user plane entity Receiving a specific indication, receiving a specific indication from a source base station, expiring a specific timer, or updating the security based on the target base station key.

2) In case of consisting of source base station and single connectivity - Source base station separation bearer

A description will be given of the case of a terminal composed of a source base station and a single connectivity before receiving an RRC message.

The MS receiving the RRC connection reconfiguration message including the radio resource configuration indicating the change between the MC-based BS performs the following operation.

The MS receiving the information indicating the change between the MC-based BSs may allow the MS to maintain the source BS / cell connection until a certain point in time.

If the RRC message received by the UE includes a new radio resource configuration for the source BS split bearer, it performs radio resource reconfiguration for the source BS detach bearer.

To this end, if the radio resource configuration for the received source base station split bearer includes a drb-Identity value to be further modified by the target base station and the DRB indicated by the drb-Identity is the MCG DRB (of the source base station) And establishes an RLC entity for the RLC entity.

If the target base station MAC is not part of the current terminal configuration, it creates a target base station MAC entity.

If the (primary) cell configuration of the target base station is included, a primer resister of the target base station is added according to the received configuration information.

The MS performs synchronization with the target base station cell (or the PC cell of the target base station or a specific cell of the target base station that is assumed to be the PSCell with the terminal). The terminal transmits the PRACH to the target base station cell.

The terminal maintains a dual connection with the source base station and the target base station cell and can transmit and receive data, respectively.

The MS may consider the target BS cell as PCell at another specific time.

The UE reconfigures the PDCP entity with the target base station security configuration according to the PDCP configuration.

 The terminal can release the source base station configuration at a specific point in time. For example, the base station can instruct the terminal to the rule / condition for this. In another example, the base station may send information to direct it. The above-mentioned rule / condition may be used to determine a specific threshold for the radio quality of the source cell, a specific timer, a radio link failure of the source cell, a threshold for radio link monitoring of the source cell (e.g., It may be one of the retransmission failures of a certain number or more in the RLC entity.

When releasing the source base station configuration, the UE can perform the PDCP data recovery procedure for the radio bearer in the source base station AM RLC mode. For this, when releasing the source base station RLC entity, it may indicate to the PDCP entity information about the PDCP PDUs that could not be successfully transmitted. The PDCP entity can retransmit it via a data recovery procedure.

The above-mentioned specific time point or another specific time point may be determined by receiving an RRC reconfiguration message from the source base station, an initial uplink transmission to the target base station, a RACH preamble transmission to the target base station, a first transmission of the PRACH to the target PCell, Receiving a RRC message different from the RRC reconfiguration message received from the source base station, receiving a MAC CE from the target base station, receiving PDCCH from the target base station, receiving a specific indication from the target base station, Receiving the end market according to the path switching from the target entity, receiving data from the target base station, receiving the PDCP control PDU of the target base station, receiving the specific indication information from the target base station receiving the end market according to the path switching from the core network user plane entity , sauce Specific indication from the station is received, a specific timer expires, after the update of the security key, the target base station based, reconfiguration of the UE PDCP entity of the target base station security arrangement, it could be one of any terminal operating point.

3) In case of consisting of source base station and single connectivity - Target base station separation bearer

A description will be given of the case of a terminal composed of a source base station and a single connectivity before receiving an RRC message.

The MS receiving the RRC connection reconfiguration message including the radio resource configuration indicating the change between the MC-based BS performs the following operation.

The MS receiving the information indicating the change between the MC-based BSs may allow the MS to maintain the source BS / cell connection until a certain point in time.

If the RRC message received by the MS includes a new radio resource configuration for the target BS split bearer, it performs radio resource reconfiguration for the target BS BS bearer.

If the DRB indicated by the drb-Identity is the MCG DRB (of the source base station), then the target base station is notified of the DRB- And establishes an RLC entity for the RLC entity.

The UE reconfigures the PDCP entity with the target base station security configuration according to the PDCP configuration

If the target base station MAC is not part of the current terminal configuration, it creates a target base station MAC entity.

If the (primary) cell configuration of the target base station is included, a primer resister of the target base station is added according to the received configuration information.

The terminal performs synchronization with the target base station cell (or the PCELL of the target base station or a specific cell of the target base station). The terminal transmits the PRACH to the target base station cell.

The terminal maintains a dual connection with the source base station and the target base station cell and can transmit and receive data, respectively.

The MS may consider the target BS cell as PCell at another specific time.

The terminal can release the source base station configuration at a specific point in time. For example, the base station can instruct the terminal to the rule / condition for this. In another example, the base station may send information to direct it. The above-mentioned rule / condition is based on a specific threshold for the radio quality of the source cell (such as RRM measurement or beam measurement or CQI measurement value), a specific timer, a radio link failure of the source cell, Value (e.g., out of sync count, etc.), the source cell RLC entity may be one of more than a certain number of retransmission failures.

When releasing the source base station configuration, the UE can perform the PDCP data recovery procedure for the radio bearer in the source base station AM RLC mode. For this, when releasing the source base station RLC entity, it may indicate to the PDCP entity information about the PDCP PDUs that could not be successfully transmitted. The PDCP entity can retransmit it via a data recovery procedure.

The above-mentioned specific time point or another specific time point may be a time point for receiving the RRC reconfiguration message from the source base station, the initial uplink transmission to the target base station, the RACH preamble transmission to the target base station, the first transmission of the PRACH to the target PCELL, After receiving an RRC reconfiguration message and another RRC message, receiving a MAC CE from a target base station, receiving a PDCCH from a target base station, receiving a specific indication from a target base station, and switching a path from a core network user plane entity, Receiving a PDCP control PDU from a target base station, receiving a specific indication from a target BS receiving an end market according to a path switching from a core network user plane entity, receiving a specific indication from a source BS, expiring a specific timer, Security Reconfiguring the terminal according to the PDCP entity after the date, the target base station security configuration, can be one of any terminal operating point.

In the conventional LTE, the security function between the terminal and the network is based on a security key called K _ASME . K _ASME is derived from the permanent keys stored in the USIM and HSS. The MME (core network control plane entity) receives K _ASME from the HSS. The terminal derives K _ASME as a result of an Authentication and Key Agreement (AKA) procedure in the NAS protocol. The terminal and the network perform mutual authentication and agree on K _ASME .

The UE and the eNB derive a K _eNB from K _ASME for signaling and protecting user data on the Uu interface between the UE and the eNB.

K eNB from the UE and the _eNB is the K _RRCint for integrity protection of RRC messages, the K derived reulreul K _{UPenc RRCenc} for ciphering of the RRC message and for the ciphering of user data.

The four AS keys are changed at each handover and connection reset. From the source base station to the target base station

For handover, the terminal and the source base station derive K _{eNB *} , which is the new K _eNB to be used in the target cell. The other AS keys are derived from K _{eNB *} . K _{eNB *} is transmitted from the terminal and the eNB to the current K _eNB Or NH based on nexthopChainingCounter.

The physical cell ID and the downlink carrier frequency of the target cell are also used to derive K _{eNB *} . The following is the content of TS 33.401 related to this.

Whenever an initial AS security context needs to be established between the UE and the eNB, the MME and the UE shall derive a _KNN and a Next Hop parameter (NH). The _KNN and the NH are derived from the K _ASME . A NH Chaining Counter (NCC) is associated with each _KNN and NH parameter. Every _KNN is associated with the NCC corresponding to the NH value from which it was derived. At initial setup, the _KNN is derived directly from K _ASME , which is then associated with a virtual NH parameter with NCC value equal to zero. At initial setup, the derived NH value is associated with the NCC value one. At the UE, the NH derivation associated with NCC = 1 could be delayed until the first handover was performed.

The UE and the eNB use the K eNB to secure the communication between each other. On handovers, the basis for the K eNB that will be used between the UE and the target eNB, called K eNB *, is derived from either the currently active K eNB or from the NH parameter. If the _KNN * is derived from the currently active _KNN, this is referred to as a horizontal key derivation and if the _KNN * is derived from the NH parameter, the derivation is referred to as a vertical key derivation. On handovers with vertical key derivation, the NH is further bound to the target PCI and its frequency EARFCN-DL before it is taken into use as the _eNB in the target eNB. On handovers with horizontal key derivation The currently active _eNB is further bound to the target PCI and its frequency EARFCN-DL before it is taken into use as the _eNB in the target eNB.

As NH parameters are only computable by the UE and the MME, it is arranged so that the NH parameters are provided from the MME.

When the eNB decides to perform an intra -eNB handover it shall derive K eNB * as in Annex A.5 using target PCI, its frequency EARFCN-DL, and either NH or the current K eNB depending on the following criteria: the eNB shall _{use the NH for deriving K eNB *} if an unused {NH, NCC} pair is available in the eNB (this is referred to as a vertical key derivation), otherwise if no unused {NH, NCC} pair is available in the eNB, the eNB shall derive the _eNB * from the current _eNB (this is referred to as a horizontal key derivation).

_{The eNB shall use the K eNB *} as the K eNB after handover. The eNB shall send the NCC used for K _eNB * derivation to the UE in the HO Command message.

As in intra-eNB handovers, for X2 handovers, the source eNB shall have a vertical key derivation in case an unused {NH, NCC} pair. _{The source eNB shall first compute K eNB} * from target PCI, its frequency EARFCN-DL, and either from currently active K eNB in case of horizontal key derivation or from the NH in case of vertical key derivation

On the other hand, in case of DC, SCG dedicated bearer (for SCG-DRBs) separated K _{eNB (} SK _eNB ) is used. This key is derived from the key (K _eNB ) used for the MCG and the SCG counter used to ensure freshness. When performing handover, K _eNB and SK _eNB are refreshed while at least one SCG-DRB is configured and maintained.

NR can also assume the same security structure as LTE. That is, the base station key can be derived based on the core network key. In addition, the base station key and the AS key are updated each time a cell change is performed.

As the terminal having dual connectivity moves to the edge of coverage of the master base station according to the movement, the current master base station can change the role of the current secondary base station and the base station. The current master base station may attempt to change the role of the current secondary base station and the base station according to the state change of the base station with respect to the terminal configured with dual connectivity. The base station may wish to perform dual connectivity based mobility control. It is possible to perform a handover that minimizes the interruption by performing the handover from the source cell to the target cell based on the dual connectivity. A DC-capable terminal can simultaneously transmit and receive to two base stations. Thus, data transmission can be performed with minimal interruption.

Hereinafter, for convenience of description, a change procedure between the base stations for a multi-connectivity capable terminal or a procedure for changing a multi-connectivity-based base station or a procedure for providing a dual connectivity based mobility is described as a change procedure between MC-based base stations. This is for convenience only and may be replaced by another name.

Based on the change between the MC-based BSs, the MS must change the RRC connection with the existing master BS. For example, the existing secondary base station should be changed to a new master base station by changing / modifying / setting / resetting / maintaining / reconfiguring the RRC connection. The existing secondary base station must generate a terminal configuration for operating as a new master base station and instruct it to the terminal. Or MC-based base station, the UE can add the target base station radio resource to the source base station and release the source base station radio resource. As described above, according to the change between the MC-based base stations, each key is required to transmit and receive data using two base station radio resources. Hereinafter, a specific method for this will be described. The methods described below may be used individually or in combination / combination.

For convenience of description, the source base station, the old master base station, the old MeNB, and the new SeNB are denoted as the source base station in the MC-based base station change. Source MCell, old MCG PCell, and old MCG PCell, which are connected to the source base station, source PCell, source base station PCell, old MCG, old MCN, Can mean PCell. For convenience of description, the target base station, the old secondary base station, the old SeNB, and the new MeNB will be referred to as target base stations in the following description. A target MCell, a new MCG cell, and a new MCG PCell as target cells, and a cell associated with the target BS, a target PCell, and a target base station PCell It can mean.

Secondary  Additional station key configuration target  By base station key To update  Way

The source base station determines the change between MC based base stations. The source base station issues an inter-base station interface message on the target side to send the necessary information to prepare for a change between MC based base stations. The inter-base station interface message for sending the necessary information to prepare for the change between MC-based base stations includes a target cell ID, a secondary base station key value (K-SeNB), a target base station key value (K _eNB *), an RRC context, An AS-configuration, an E-RAB context, a physical layer ID of the source cell, and short MAC-I.

The target base station constructs necessary resources according to the received radio bearer QoS information. The target base station prepares to change between MC based base stations via L1 / L2. And transmits a request confirmation message to the source base station. This message includes a container to be sent to the terminal as an RRC message for performing a change between MC-based base stations. For example, the target base station may include information for instructing the terminal to make a change between MC-based base stations. The source base station sends an RRC connection reconfiguration request message to the terminal to instruct it to configure a new DRB for the target base station. The source base station calculates a secondary base station key value necessary for adding the target base station to the target base station as a secondary base station, a target base station key value for switching the secondary base station to the target base station according to the release of the source base station, and K _UPenc associated with the assigned secondary base station bearer And then an NCC filammeter according to the switching of the target base station. As an example, the aforementioned parameters may be SCG Counter and NHCC. As another example, the above-mentioned parameter may be a Counter value used when calculating the secondary base station key and a Counter value used when calculating the target base station key.

The terminal receiving the information indicating the change from the target base station to the MC based base station can maintain the connection in the source cell until a certain point of time. Alternatively, the terminal may be able to maintain a source cell / base station connection and a target cell / base station connection concurrently to a specific point in time. Or the terminal may be maintained until a certain point after adding the target cell / base station connection to the source cell / base station connection.

The specific point in time may include receiving an RRC reconfiguration message from the source base station, receiving a RRC message different from the RRC reconfiguration message received from the source base station, receiving a MAC CE from the target base station, receiving a specific indication from the target base station, Receives a PDCP control PDU from a target BS, receives specific indication information from a target BS that receives an end market according to path switching from a core network user plane entity, It may be one of any terminal operation time after receiving a specific indication from the base station, expiration of a specific timer, and security update based on the target base station key.

To minimize disruption, the terminal adds a source cell / base station connection and a target cell / base station connection in the process of changing between MC based base stations.

If a target cell / base station based radio bearer configuration is included in the target cell / base station connection addition process, a secondary base station key is required.

Or if a base station function change is performed between a source base station and a target base station after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

Or if a source base station release is performed after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

The MS receiving the RRC connection reconfiguration message calculates the secondary base station key value for connecting the target base station to the secondary base station. For example, the key value of the secondary base station may be K-SeNB. The terminal calculates K _UPenc for the DRB allocated in association with the target base station.

The MS can send an RRC connection completion message to the source BS.

The source base station sends a target base station reconfiguration complete message to the target base station to inform the target base station configuration result. Upon receipt of this message (On receipt of this message), the target base station can activate encryption / decryption with the terminal. When the target base station receives the random access request or the first data from the terminal, the target base station can activate encryption / decryption.

In the dual connection state between the source base station and the target base station in the process of changing between the MC-based base station, the terminal and the base station transmit the AS keys (RRC message) transmitted through the key calculated based on the key calculation parameter K for K _RRCint, ciphering of the RRC message, for integrity protection _RRCenc and can lead to _UPenc K) for the ciphering of user data.

If the terminal releases the source base station radio resource, the terminal updates the target base station key value. For example, the key value of the target base station may be K _eNB *. When the terminal and the base station are disconnected from the source base station after the change procedure between the MC-based base station, for example, the AS keys associated with the key calculated based on the key calculation parameter associated with the target base station key (integrity of the RRC message _RRCenc K for K _RRCint, ciphering of the RRC messages for protection and can lead to _UPenc K) for the ciphering of user data.

Secondary  The base station key target  How to use it as a base station key

The source base station determines the change between MC based base stations. The source base station issues an inter-base station interface message on the target side to send the necessary information to prepare for a change between MC based base stations. The inter-base station interface message for sending the necessary information to prepare for the change between the MC-based base stations described above includes a target cell ID, a key value of the target base station, a RRC context, an AS- configuration, an E-RAB context, ID, and short MAC-I.

For example, the key value of the target base station may be K-SeNB.

The target base station constructs necessary resources according to the received radio bearer QoS information. The target base station prepares to change between MC based base stations via L1 / L2. And transmits a request confirmation message to the source base station. This message includes a container to be sent to the terminal as an RRC message for performing a change between MC-based base stations. For example, the target base station may include information for instructing the terminal to make a change between MC-based base stations. The source base station sends an RRC connection reconfiguration request message to the terminal to instruct it to configure a new DRB for the target base station. The source base station may include a parameter for instructing the _terminal to calculate the key value of the target base station and the K _UPenc associated with the assigned bearer. For example, the above-mentioned parameter may be an SCG Counter. As another example, the above-mentioned parameter may be a Counter value used when calculating the target base station key.

The terminal receiving the information indicating the change from the target base station to the MC based base station can maintain the connection in the source cell until a certain point of time. Alternatively, the terminal may be able to maintain a source cell / base station connection and a target cell / base station connection concurrently to a specific point in time. Or the terminal may be maintained until a certain point after adding the target cell / base station connection to the source cell / base station connection.

The specific point in time may include receiving an RRC reconfiguration message from the source base station, receiving a RRC message different from the RRC reconfiguration message received from the source base station, receiving a MAC CE from the target base station, receiving a specific indication from the target base station, Receives a PDCP control PDU from a target BS, receives specific indication information from a target BS that receives an end market according to path switching from a core network user plane entity, It may be one of any terminal operation time after receiving a specific indication from the base station, expiration of a specific timer, and security update based on the target base station key.

To minimize disruption, the terminal adds a source cell / base station connection and a target cell / base station connection in the process of changing between MC based base stations.

If a target cell / base station based radio bearer configuration is included in the target cell / base station connection addition process, a target cell / base station key is required.

Or if a base station function change is performed between a source base station and a target base station after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

Or if a source base station release is performed after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

The MS receiving the RRC connection reconfiguration message calculates a key value for connecting the target BS to the secondary BS. For example, the key value of the target base station may be K-SeNB. The terminal calculates K _UPenc for the DRB allocated in association with the target base station.

The MS can send an RRC connection completion message to the source BS.

The source base station sends a target base station reconfiguration complete message to the target base station to inform the target base station configuration result. Upon receipt of this message (On receipt of this message), the target base station can activate encryption / decryption with the terminal. When the target base station receives the random access request or the first data from the terminal, the target base station can activate encryption / decryption.

After the change procedure between the MC base station and the base station, the terminal and the base station transmit the AS keys (K _RRCint for integrity protection of the RRC message, RRC message for the integrity protection of the RRC message, which are transmitted through the keys calculated on the basis of the key- It can lead to K and K _{RRCenc UPenc)} for the ciphering of user data for ciphering.

target  Add using base station key Secondary  How to use it as a base station key

The source base station determines the change between MC based base stations. The source base station issues an inter-base station interface message on the target side to send the necessary information to prepare for a change between MC based base stations. The inter-base station interface message for sending the necessary information to prepare for the change between the MC-based base stations includes a target cell ID, a key value of the target base station, a NexthopChaingCounter, an RRC context, an AS-configuration, an E-RAB context, Physical layer ID, and short MAC-I.

For example, the key value of the target base station may be KeNB *.

Whenever an initial AS context needs to be established between the terminal and the base station, the core network control plane entity and the terminal derive the K _eNB and NH parameters from K _ASME . NexthopChainingCounter (NCC) is associated with each K _eNB and NH parameter.

The target base station constructs necessary resources according to the received radio bearer QoS information. The target base station prepares to change between MC based base stations via L1 / L2. And transmits a request confirmation message to the source base station. This message includes a container to be sent to the terminal as an RRC message for performing a change between MC-based base stations. For example, the target base station may include information for instructing the terminal to make a change between MC-based base stations. The source base station sends an RRC connection reconfiguration request message to the terminal to instruct it to configure a new DRB for the target base station. The target base station may include a parameter for instructing the _terminal to calculate the key value of the target base station and the K _UPenc associated with the assigned bearer. For example, the above-mentioned parameter may be NexthopChainingCounter. As another example, the above-mentioned parameter may be a Counter value used when calculating the target base station key.

The terminal receiving the information indicating the change from the target base station to the MC based base station can maintain the connection in the source cell until a certain point of time. Alternatively, the terminal may be able to maintain a source cell / base station connection and a target cell / base station connection concurrently to a specific point in time. Or the terminal may be maintained until a certain point after adding the target cell / base station connection to the source cell / base station connection.

The specific point in time may include receiving an RRC reconfiguration message from the source base station, receiving a RRC message different from the RRC reconfiguration message received from the source base station, receiving a MAC CE from the target base station, receiving a specific indication from the target base station, Receives a PDCP control PDU from a target BS, receives specific indication information from a target BS that receives an end market according to path switching from a core network user plane entity, It may be one of any terminal operation time after receiving a specific indication from the base station, expiration of a specific timer, and security update based on the target base station key.

To minimize disruption, the terminal adds a source cell / base station connection and a target cell / base station connection in the process of changing between MC based base stations.

If a target cell / base station based radio bearer configuration is included in the target cell / base station connection addition process, a target cell / base station key is required.

Or if a base station function change is performed between a source base station and a target base station after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

Or if a source base station release is performed after adding a target cell / base station connection, a target cell / base station key for a target cell / base station based radio bearer configuration is required.

The MS receiving the RRC connection reconfiguration message calculates a key value for connecting the target BS to the secondary BS. The terminal may update the target base station K _eNB key based on the current K _eNB or NH using the nexthopChaingCount value. As an example, the key value of the target base station may be K _eNB *. The terminal calculates K _UPenc for the DRB allocated in association with the target base station.

The MS can send an RRC connection completion message to the target BS.

After the change procedure between the MC base station and the base station, the terminal and the base station transmit the AS keys (K _RRCint for integrity protection of the RRC message, RRC message for the integrity protection of the RRC message, which are transmitted through the keys calculated on the basis of the key- It can lead to K and K _{RRCenc UPenc)} for the ciphering of user data for ciphering.

The target base station can generate a new K-SeNB new SCG counter needed to add the source base station to the secondary base station. The target base station may transmit a new SCG counter required for adding the source base station to the secondary base station.

After the cell change, the base station key is transmitted through a new RRC message update  How to

For example, in the process of changing between MC-based BSs, the target BS and the MS can process the security functions based on the source BS key (for example, the PDCP entity can process the data).

For example, after handing over to the target BS, the target BS transmits a K _eNB RRC message for change can be transmitted. This can provide uninterrupted handover. As another example, after handing over to the target BS, the target BS transmits a K _eNB RRC message for change can be transmitted. This can provide uninterrupted handover.

Another example may be to perform key updates via another RRC procedure. Thus, it is possible to process the security function without changing the security key (or security refresh) in the MC base station change process or based on the secondary base station key, and transmit and receive data without changing the security function. The base station may then instruct the other RRC procedure (e.g., the RRC reconfiguration procedure) to change the security key.

Hereinafter, a method for solving a problem that may occur in the process of using two security between a terminal and a base station will be described.

In the MC base station change process, the PDCP entity of the UE uses the security key based on the source base station before changing the MC base station. Then, in the MC base station change process, the target base station is added to the secondary base station or the security key based on the target base station is used when releasing the source base station radio resource.

It may be necessary for the terminal and the base station to know each other about which security key is used to process the PDCP data. For example, it can avoid deciphering based on false security keys.

For this purpose, the sender (the source base station for the downlink or the terminal for the uplink) may send an end marker packet (including the PDCP SN) indicating to the receiver the last PDCP PDU ciphered by the source base station key. After receiving the end marker packet, the receiver assumes that the PDCP PDUs with a COUNT value greater than the COUNT value corresponding to the SN in the end marker packet are ciphered with the target base station key. The accurate transmission of the end marker packet for the uplink can occur when the terminal switches the PDCP key. Such an end marker packet can be provided through the PDCP Control PDU.

As described above, the present invention is capable of stably changing a cell or changing a base station while reducing a data transmission interruption time due to movement of the terminal. Further, the present invention has an effect of efficiently performing a cell change or a base station change by using a security key while reducing a data transmission interruption time due to movement of a terminal.

4 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.

Referring to FIG. 4, a base station 1000 according to another embodiment includes a control unit 1010, a transmission unit 1020, and a reception unit 1030.

The controller 1010 controls the overall operation of the base station according to providing an efficient data processing method and apparatus for minimizing an interruption on a change procedure between the master base station and the secondary base station in the multi-connectivity environment required for performing the above-described present invention .

The transmitting unit 1020 and the receiving unit 1030 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention to and from the terminal.

5 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

5, the user terminal 1100 according to another embodiment includes a receiving unit 1110, a control unit 1120, and a transmitting unit 1130.

The receiving unit 1110 receives downlink control information, data, and messages from the base station through the corresponding channel.

In addition, the controller 1120 controls the overall operation of the terminal according to providing an efficient data processing method and apparatus for minimizing an interruption on the change procedure between the master base station and the secondary base station in the multi-connectivity environment required for performing the above- do.

The transmitter 1130 transmits uplink control information, data, and a message to the base station through the corresponding channel.

The standard content or standard documents referred to in the above-mentioned embodiments constitute a part of this specification, for the sake of simplicity of description of the specification. Therefore, it is to be understood that the content of the above standard content and portions of the standard documents are added to or contained in the scope of the present invention.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (1)

In a data processing method,
A method for efficiently processing data that minimizes disruption on a change procedure between a master base station and a secondary base station in a multi-connectivity environment.

Images