WO2014177089A1

WO2014177089A1 - Connection mobility management method and node device

Info

Publication number: WO2014177089A1
Application number: PCT/CN2014/077766
Authority: WO
Inventors: 施小娟; 黄亚达; 杜忠达
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-08-12
Filing date: 2014-05-19
Publication date: 2014-11-06
Also published as: CN104378841A

Abstract

The present invention relates to the field of mobile communications. Disclosed in an embodiment of the present invention are a connection mobility management method and node device, the method comprising: when a user equipment (UE) establishes a connection with one or more connection nodes, if one or more resource connection nodes determine that some or all of the connections between the UE and the resource connection nodes need to be managed, then the resource connection nodes initiate a management operation to the UE, the management operation being an operation of deleting or removing some or all of the connections, and the resource connection nodes initiating the management operation to the UE directly or via a primary connection node. Also disclosed in the embodiment of the present invention is a node device. The technical solution of the present invention realizes management of a connection between a UE and a resource connection node in a double-connection architecture.

Description

Connection mobility management method and node device

Technical field

The present invention relates to the field of mobile communications, and in particular, to a connection mobility management method and a node device.

Background technique

Since the development of the first generation of mobile communication systems in the 1980s, mobile communication technology has entered the 4G era, and users' mobile communication needs have also experienced a growth from a single voice service to a voice and basic data service to a data service. The process, mobile communications has gradually risen to the current era of mobile Internet. In the era of mobile Internet, the demand for new mobile applications, especially those for high-quality, high-speed, low-latency mobile applications, has exploded, according to the International Telecommunications Union (ITU). In 2010 and 2015, the mobile communication business will grow 15 to 30 times compared with the previous one. By 2020, the mobile communication service is likely to increase by more than 500 times.

The explosive growth of mobile communication services and higher expectations of users for mobile communication experiences, such as higher throughput, lower latency, faster rates, and lower cost, drive related mobile communication technologies and mobile communication networks. Forward development and upgrade, including capacity expansion, enhanced network coverage, enhanced collaboration between different cells in different networks, increased flexibility in network deployment, and reduced network deployment costs.

Statistics on user communication behaviors and habits can be found that most high-traffic traffic is concentrated in indoor environments and hotspots, such as shopping malls, schools, users' homes, large-scale performances, gathering places, etc., considering indoor environment and hotspot area distribution. A wide power node (LPN) emerged as a result of wide and wide, single-area range and user concentration. Conceptually, LPN refers to a radio access network node whose transmit power is lower than that of a macro node or a base station (BS) in a conventional macro network. The LPN may be a Pico Node. , Home base station (Femto/Home (e)NB) and any other cellular nodes that may have lower transmit power than traditional macro nodes or BSs. The deployment of LPN can effectively expand network capabilities, enhance network coverage, and ultimately improve end-user throughput and improve the communication experience of end users. Also due to LPN has low transmit power, and LPN can be plug-and-play. Therefore, network operators can flexibly and conveniently deploy LPNs according to their needs. Network operators can even open the rights to deploy LPNs to enterprises, schools, and other users, thereby improving The flexibility of network deployment, while reducing network deployment and operation and maintenance costs.

To achieve network capacity expansion for the network, enhance network coverage, increase network deployment flexibility, and reduce network deployment costs. For users, the objectives of improving user communication experience include: User Equipment, UE ) The throughput, improving the mobile performance of user terminal equipment, etc., LPN is expected to be deployed in large numbers, for example, for 4G LTE (Long Term Evolution) system, at 3gpp (the 3rd Generation Partner Project, third generation partner) After the release of Release 12 and R12+, it is expected to deploy a large number of LPNs based on traditional macro networks, both indoor and outdoor.

In order to improve the user's communication experience, especially to improve the throughput and mobile performance of user equipment, many operators and equipment vendors are eager to seek a new technical solution. Dual-connection/multi-connection (hereinafter collectively referred to as dual connectivity) is one of them. One. A dual connection means that the user equipment can simultaneously use resources of at least two different access network elements (access network nodes), and the at least two different access network nodes and their functions in the dual connection may not Depending on the functional characteristics of the access network node, for example, the at least two different access network nodes may be both traditional macro nodes or low power nodes, or one macro node and one low power node. Considering that low-power nodes may be deployed in hotspot areas and indoor coverage areas with macro node coverage, the dual-connection scheme in which user equipment uses both macro nodes and low-power node resources can greatly improve the user communication experience and meet new requirements. Mobile demand. However, the emergence of the dual connectivity scheme enables the user equipment to extend from resources that can only use one access network element to resources that can use two or more access network elements, or that the user equipment can only connect to one at present. The access network element is extended to connect to two or even multiple access network elements, which is bound to pose new challenges for connection mobility management. It is necessary to seek a new connection mobility management solution.

Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a connection mobility management method and a node device to meet the connection management requirements in a dual connectivity/multi-connection scenario.

In order to solve the above technical problem, an embodiment of the present invention discloses a connection mobility management method. The method includes:

When a user equipment (UE) establishes a connection with one or more connection nodes, where one or more resource connection nodes determine that some or all connections between the UE and the resource connection node need to be managed, The resource connection node initiates a management operation to the UE, where the management operation is to delete or move the part or all of the connections, where the resource connection node initiates a management operation to the UE through the primary connection node, or The resource connection node initiates a management operation directly to the UE.

Optionally, in the foregoing method, the resource connection node determines that a partial or all connection between the UE and the resource connection node needs to be managed:

The resource connection node determines, according to one or more of the following information, that part or all of the connection between the UE and the resource connection node needs to be deleted or moved:

The measurement report reported by the user equipment, the radio resource management (RRM) algorithm, the load information of the resource connection node, and the service transmission information.

Optionally, in the foregoing method, the process in which the resource connection node initiates a management operation to the UE by using the primary connection node is as follows:

The resource connection node notifies the primary connection node that a management operation needs to be performed on some or all of the connections between the UE and the resource connection node;

After receiving the notification, the primary connection node initiates a management operation to the UE.

Optionally, in the foregoing method, when the resource connection node notifies the primary connection node that a partial or all connection between the UE and the resource connection node is required to be managed, the connection to be managed is referred to as a resource connection node. Part or all of the Radio Access Bearers (RABs) carried for user plane data transmission.

Optionally, in the foregoing method, after the primary connection node receives the notification, the connection to the UE for performing the management operation refers to:

Part or all of the user plane data radio bearer between the UE and the resource connection node

(DRB); or,

Part or all of the DRB and some or all of the control plane signaling radio bearers (SRBs) between the UE and the resource connection node. Optionally, in the foregoing method, when the primary connection node is the connection between the UE and the resource connection node, the uplink and downlink of data forwarding are reserved on the Xn interface of the resource connection node and the primary connection node. When the user plane tunnels the GPRS tunneling protocol, the resource connection node directly initiates a management operation to the UE.

Optionally, in the foregoing method, when the resource connection node directly initiates a management operation to the UE, the connection to be managed is:

Part or all of the user plane data radio bearer (DRB) between the UE and the resource connection node; or

The part or all of the DRB and some or all of the control plane signaling radio bearers (SRBs) between the UE and the resource connection node.

The embodiment of the invention further discloses a node device, including:

a first unit, configured to determine, when the node is a resource connection node, whether to manage part or all of the connection between the resource connection node and the user equipment (UE);

a second unit, configured to initiate a management operation to the UE when determining that a part or all of the connection between the resource connection node and the UE needs to be managed, where the management operation is to delete or move the part or all of the connection Operation

The second unit is configured to initiate a management operation to the UE by using the primary connection node, or initiate a management operation directly to the UE.

Optionally, in the foregoing node device, the first unit is further configured to: determine, according to one or more of the following information, a partial or all connection between the UE and the resource connection node that needs to be deleted or moved:

Optionally, the foregoing node device further includes:

The third unit is configured to: when the local node device is the primary connection node device, receive a notification that the resource connection node needs to perform a management operation on a part or all of the connection between the UE and the resource connection node, and according to the The notification initiates a management operation to the UE.

Optionally, the foregoing node device further includes: The fourth unit is configured to reserve, on the Xn interface of the resource connection node and the primary connection node, each connection between the UE and the resource connection node when the node device is the primary connection node device The data forwards the tunnel of the upstream and downstream user plane GPRS tunneling protocols.

With the technical solution of the present application, the connection management between the UE and the resource connection node in the dual connectivity architecture is realized, in particular, when the resource connection node is no longer suitable for providing information transmission to the UE or is no longer suitable for providing the UE with previous establishment. Connection management when all connected information is transmitted.

BRIEF abstract

1 is a system architecture diagram of a long term evolution system in related art;

2 is a system architecture diagram of a dual connectivity after a long-term evolution system is introduced;

3 is a flowchart of a method for connecting mobility management according to an embodiment of the present invention;

4 is a non-limiting schematic diagram of a scenario for applying a connection management method according to an embodiment of the present invention; FIG. 5 is a schematic diagram of a dual-connection wireless interface control plane architecture according to an embodiment of the present invention;

6 is a flowchart of a method according to Example 1 of the present invention;

7 is a flowchart of initiating connection management by a master node according to an example of the present invention;

FIG. 8 is a flowchart of initiating connection management directly to a UE according to an example of the present invention;

9 is a flowchart of a method of Example 2 of the present invention;

10 is a flowchart of connection management according to Example 2 of the present invention;

FIG. 11 is a schematic structural diagram of a node device according to an embodiment of the present invention.

Preferred embodiment of the invention

The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings. The features of the embodiments and the embodiments of the present application may be arbitrarily combined with each other without conflict.

Example 1 FIG. 1 is a system architecture diagram of a long-term evolution system in a related art, where a Mobility Management Entity (MME) and a Serving Gateway (SGW) of a core network (CN) network element are included in an LTE system. a base station (eNB1 and eNB2) of a Radio Access Network (RAN) network element, and a user equipment UE. The UE communicates with the serving base station eNB1 through the air interface (Uu interface), and the serving base station eNB1 implements signaling transmission through the control plane S1 interface protocol S1-MME/S1-C and the MME, and implements the user plane through the user plane S1 interface protocol S1-U. data transmission. The serving base station SeNB1 can implement control plane signaling and user plane data transmission with the neighboring base station SeNB2 through the X2 interface protocol between the base stations. As shown in FIG. 1 , in a long term evolution system, a user equipment UE is only connected to one base station, and only uses resources of the one base station; and the one user equipment UE is also connected to only one MME/SGW.

FIG. 2 is a schematic diagram of a system architecture in which a dual connectivity is introduced in a long term evolution system. Referring to the single connection system architecture of FIG. 1, in FIG. 2, a UE may simultaneously connect to a base station eNB1 and a base station eNB2 through an air interface Uul and Uu2, that is, a UE. The resources of eNB 1 and eNB 2 can be used simultaneously to implement dual connectivity of air interface resources. For the core network control plane mobility management entity MME, the UE is connected to the MME only through the base station eNB1, so as to avoid modification and signal impact on the core network caused by the introduction of the air interface dual connection. In the core network user plane, one of the purposes of the dual connection is to improve the throughput of the UE. According to different network architecture design requirements, the UE can access the SGW through the S1-U interface of the eNB1, and the UE can also pass through the eNB2. The S1-U interface is connected to the SGW. In addition, the eNB1 and the eNB2 establish an Xn interface to implement interaction of control plane information or to simultaneously exchange control plane information and user plane information. In Figure 2, the types of two base stations in which the UE implements dual connectivity are not limited. eNB1 and eNB2 may both be macro nodes, or may be low power nodes, or one macro node may be a low power node, or may be Other possible access network nodes; eNB1's standard is also not limited, and may be Time Division Duplexing (TDD) or Frequency Division Duplexing (FDD), or one for TDD and the other for FDD system. In addition, the dual connection of FIG. 2 is only an example, and the UE can also implement a multi-connection scheme with more than two eNBs.

In Figure 2, on the air interface, the UE is connected to eNB1 and eNB2 through Uul and Uu2 at the same time. However, in order to reduce the modification and signaling impact on the core network, the control plane UE only connects to the MME through eNB1, that is, the eNB1 implements the UE and the MME. The control plane is connected to the anchor point. In this application, an access network element (such as the base station eNB 1 in FIG. 2) that implements an anchor function of the UE control plane to access the MME is referred to as a primary connection node, and other access network elements connected to the UE are used. (such as the base station in Figure 2) eNB2) is called a resource connection node. In addition to the primary connection node providing information transmission for the UE, the resource connection node may also provide information transmission for the UE, and information transmission between the UE and the primary connection node and the resource connection node may be based on the hardware capability of the UE and the configuration of the network. It is transmitted at the same time, or it can be coordinated in time division multiplexing. In addition to the above-mentioned unrestricted base stations, the access network element may also be a device that completes control and management of the corresponding access network resources, for example, when applied to a Universal Mobile Telecommunications System (UMTS). It is a Radio Network Controller (RNC) that performs the response function.

As shown in the dual connectivity architecture of FIG. 2, the UE can extend from the resources of only one access network element eNB1 to two or more access network elements (eNB1 and eNB2 in FIG. 2). The resource, or the UE can only connect to one access network element eNB1 for service transmission extension to connect to two or more access network elements (eNB1 and eNB2 in FIG. 2) for service transmission, Currently, the related technologies only have connection management for a single connection. Therefore, after the dual connection is introduced, it is necessary to solve the connection mobility management after the introduction of the dual connectivity architecture.

Based on the above idea, this embodiment provides a connection mobility management method, including the following operations: When a UE establishes a connection with one or more connection nodes, where a resource connection node determines that a connection between the UE and the resource is required When the part or all of the connection is managed, the resource connection node initiates a management operation to the UE, and the management operation is to delete or move the part or all of the connections, wherein the resource connection node manages the operation to the UE through the primary connection node, Or initiate a management operation directly to the UE.

In the above method, in particular, the case where the resource connection node is no longer suitable for providing connection management when the information transmission is performed for the UE, that is, for the case where the connection between the UE and the resource connection node needs to be deleted, or the UE needs to be connected to the resource. The connection between the nodes moves to the primary connection node, after which the primary connection node can move the connection to other resource connection nodes. In the above content, the connection between the UE and the resource connection node includes a user plane data connection between the UE and the resource connection node, or includes a user plane data connection and a control plane signaling connection between the UE and the resource connection node.

The following assumes that the UE is originally connected to one or more connection nodes, and the process of connection mobility management is described in conjunction with FIG. 3, which includes the following steps 301 to 302:

Step 301. The resource connection node determines that some or all connections between the UE and the resource connection node need to be deleted or moved; In this step, the resource connection node may determine, according to the received measurement report, the RRM algorithm, the load information of the resource connection node, and one or more factors in the service transmission situation, whether to delete or move between the UE and the resource connection node. Part or all of the connections.

Step 302: The resource connection node initiates the deleting or moving operation;

The operation of this step is further divided into the following two steps:

Step 302-1. The resource connection node notifies the primary connection node that the resource connection node needs to delete or move the connection;

The connection that the resource connection node notifies the primary connection node to delete or move refers to one or more radio access bearers carried by the resource connection node for user plane data transmission of the UE described above (Radio Access Bearer (abbreviated as RAB), the radio access bearer on the air interface refers to the user plane data radio bearer (DRB) between the resource connection node and the UE.

Step 302-2. The resource connection node notifies the UE to delete or move (reconfigure) the connection; or, after receiving the notification of the 302-1, the primary connection node notifies the UE to delete or move (reconfigure) The connection.

The resource connection node or the primary connection node notifying the UE to delete or move the connection may be implemented by the resource connection node or the primary connection node reconfiguring the UE by using an air interface message, where the air interface The operation of instructing the UE to perform reconfiguration is to delete the connection, or delete the connection and create the connection between the UE and the primary connection node, where the latter is equivalent to moving the connection to the primary connection node. .

The connection that the resource connection node or the primary connection node notifies the UE to delete or move refers to one or more user planes DRB between the UE and the resource connection node, or the one or more user plane DRBs. And one or more control plane signaling Radio Bearers (SRBs) between the UE and the resource connection node.

When the resource connection node notifies the UE to delete or move (reconfigure) the connection in step 302-2, operation 302-1 is optional, because the primary connection node accesses the MME as the UE control plane. Anchor point, can know the information of all connections established between the UE and the resource connection node, and when the UE establishes a connection with the resource connection node, if the main connection node is on the Xn interface of the resource connection node and the main connection node Reserve data forwarding for each connection For the uplink and downlink GTP-U (GPRS Tunneling Protocol for the user plane) tunnel, the operation 302-1 is optional, otherwise the operation 302-1 is a mandatory operation.

Through the above method, for the case of deleting some or all of the connections between the UE and the resource connection node, the resource connection node and the UE stop receiving and transmitting information on the deleted part or all of the connections. For the case of moving some or all of the connections between the UE and the resource connection node to the primary connection node, after the mobile is successful, the primary connection node and the UE continue to receive and transmit information on the connection to the primary connection node. Thereby the deletion of the connection or the movement of the connection and the connection of the data are achieved.

A non-limiting schematic diagram of the application scenario of the connection management method of the present application shown in FIG. 4 is further described. The UE is in the coverage of the cell 2 deployed by the cell 1 and the node 2 deployed by the node 1 at point A, and thus the UE At point A, a connection is established with node 1 and node 2, where node 1 is the primary connection node of the UE, and node 2 is the resource connection node of the UE. The moving path of the UE is as shown by the solid arrow in the figure. When the UE moves to point B, the signal quality of the cell 2 is no longer suitable for the information transmission of the UE. Therefore, the connection between the UE and the node 2 needs to be deleted, or The connection between the UE and Node 2 is moved to the primary connection node.

FIG. 5 is a schematic diagram of a dual-connection wireless interface control plane architecture in the present application. A radio resource control (RRC) entity is deployed on the primary connection node and the UE, and the RRC entity on the primary connection node and the UE implements all RRC functions in the related technology LTE system, including system broadcast message transmission and reception and RRC connection. Control all the features. The RRC entity is also deployed on the resource connection node. In addition to transmitting the RRC message between the primary connection node and the UE, the RRC message may also be transmitted between the resource connection node and the UE.

The process of connection management by the above method will be described in detail below by way of non-limiting application examples and with the accompanying drawings. The embodiments of the following non-limiting application examples in the embodiments of the present invention are exemplified by the dual connectivity of the UE and the two nodes in the LTE system, but the embodiment of the present invention is not limited to the UE being connected to two or more nodes. The examples are not intended to limit the embodiments of the present invention to other wireless network systems.

The application examples of this application are applicable to the following three scenarios:

Scenario 1. Applicable to the scenario shown in Figure 4, the UE is originally between the primary connection node and the resource connection node. A dual connection is established. After that, the UE detects that the signal quality of the cell (cell 2) covered by the resource connection node where the UE is located is deteriorated, and is no longer suitable for the UE to continue to maintain the connection on the resource connection node, and needs to connect the UE and the resource. All connections to the connected node are moved to the primary connected node.

Scenario 2: The resource connection node according to its own load situation: The resource connection node judges that the load on the resource connection node is too large according to at least one or more of hardware load, transport layer load, radio resource load, interference load and the like, and needs to be Some or all of the UE's connection with the resource connection node moves to the primary connection node.

Scenario 3: The resource connection node monitors the transmission of data on each connection between the UE and the resource connection node, and determines that some or all of the connections have no data transmission within the time set by the algorithm, and then the decision deletes part or all of the connection.

Example one

6 is a flowchart of a connection mobility management method of the first example. The UE originally establishes a connection with one or more connection nodes, and the connection mobility management process includes steps 601 to 602:

Step 601. The resource connection node determines that some or all connections between the UE and the resource connection node need to be deleted or moved;

The resource connection node determines, according to the received measurement report, the RRM algorithm, the load information of the resource connection node, the one or more factors in the service transmission situation, whether to delete or move the part between the UE and the resource connection node or All connected.

Step 602: The resource connection node initiates the deleting or moving operation;

The operation of this step is further divided into the following two steps:

Step 602-1. The resource connection node notifies the primary connection node that the resource connection node needs to delete or move the connection;

Step 602-2. The resource connection node notifies the UE to delete or move (reconfigure) the connection;

Step 602-1 is optional, and the primary connection node is used as an anchor point of the UE control plane to access the MME, and can obtain information about all connections established between the UE and the resource connection node, and further establish a connection between the UE and the resource connection node. At the time, if the primary connection node reserves the uplink and downlink GTP-U for data forwarding for each connection on the Xn interface of the resource connection node and the primary connection node (GPRS) Tunneling Protocol for the user plane, the user plane GPRS tunneling protocol tunnel, step 602-1 is optional.

In the first example, when the resource connection node determines to delete or move part or all of the connection between the UE and the resource connection node to the main connection node, the connection management process is as shown in FIG. 7, and includes steps 701 to 705:

Step 701. The user equipment reports a measurement report to the resource connection node, where the measurement report includes the measurement result of the cell 2.

The implementation step is applicable to the scenario 1 stated above. For the scenario 2 and the scenario 3, the resource connection node may delete part or all of the connection between the UE and the resource connection node without requiring the measurement report reported by the user equipment. Move to the decision of the primary connection node.

Step 702. The resource connection node decides to delete or move some or all of the connections on the resource connection node to the primary connection node.

The decision strategy of the resource connection node is described in detail in the above three scenarios.

Step 703. The resource connection node sends a connection reconfiguration request to the primary connection node.

The connection reconfiguration request contains the information that the resource connection node decides to delete, or the connection that is decided to be removed from the resource connection node. The information of the deleted/removed connection may be the identification information of the connection, and may also include an indication of whether each deleted/removed connection performs data forwarding.

Or, in this embodiment, the signal quality of the cell 2 is deteriorated, and the resource connection node determines to move all the connections of the UE on the resource connection node to the primary connection node, where the connection reconfiguration request message may not include any connection. Information, defining the connection reconfiguration message itself means deleting all connections between the UE and the resource connection node.

The "connection reconfiguration request" is merely an exemplary message name of the present embodiment, and the message name is not limited to the embodiment, and the present description is applicable to all message names in all embodiments of the present invention.

Step 704. The primary connection node returns a connection reconfiguration response to the resource connection node.

The connection reconfiguration response includes information about all connections deleted/removed by the resource connection node, the connection information may be identification information of the connection, and may also include each deleted/removed connection provided by the primary connection node at the resource connection node. Uplink and downlink GTP-U (GPRS Tunnelling Protocol for the user plane) for data forwarding on the Xn interface of the primary connection node Tunnel Protocol) Tunnel identification information.

Step 705: The resource connection node sends the transmission sequence status of the data transmission on each deleted/removed connection to the primary connection node, for example, including the uplink PDCP SDU (Packet Data Protocol Protocol Service Data Unit). The reception status indication, the count number of the first lost uplink PDCP SDU, the count number of the first lost downlink PDCP SDU, and the like.

In the case where the connection is deleted and the data on the connection has been transmitted, such as scenario 3, this step is not required.

Step 705-1. This step is optional. For the case where the deleted/removed connection is Acknowledge Mode (AM), the resource connection node forwards the data to the primary connection node.

In the case where the connection is deleted and the data on the connection has been transmitted, such as scenario 3, this step is not required. After receiving the forwarding data, the master node may select to transmit the forwarding data on the connection reestablished by the UE and the primary connection node after completing steps 705-x and 706.

Step 705-x. The resource connection node sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message deletes or reconfigures some or all of the connections between the UE and the resource connection node to the primary connection node.

Receiving, by the UE, the RRC connection reconfiguration message, deleting part or all of the connection between the indicated UE and the resource connection node according to the indication of the RRC connection reconfiguration message, after which the UE stops part or all of the connection in the deletion Receiving and transmitting information on the network; or reconfiguring part or all of the connection between the indicated UE and the resource connection node to the primary connection node according to the indication of the RRC connection reconfiguration message, after which the UE is in the reconfiguration Continue to receive and send information to the connection on the primary connection node.

The steps 705-x for the resource connection node to notify the UE to delete or reconfigure some or all of the connections on the air interface and the steps 705, 705-1 for transmitting the transmission sequence state and forwarding data to the primary connection node on the Xn interface by the resource connection node on the Xn interface Can be executed in parallel.

After the user equipment UE receives the RRC connection reconfiguration message, there are two possible operations:

The first operation includes the following steps 706a and 707a.

706a. The UE sends an RRC Connection Reconfiguration Response message to the primary connection node. Then optional, 707a. The primary connection node notifies the resource connection node that the connection reconfiguration succeeds, that is, the connection is deleted or the migration is successful.

The second operation 2 includes the following step 706b.

706b. The UE directly sends an RRC connection reconfiguration response message to the resource connection node.

For the above two operations, if in step 705-x, the resource connection node notifies the UE to delete all connections between the UE and the resource connection node, including all user plane data connections and control plane signaling connections, the UE capture operation 1 , Unable to retrieve operation 2. If, in step 705-x, the resource connection node retains at least one control plane signaling connection between the UE and the resource connection node, the UE may retrieve the first operation or the second operation.

According to the above operation of the present example, for the case of deleting part or all of the connection between the UE and the resource connection node, the resource connection node and the UE stop receiving and transmitting information on the deleted part or all of the connection. For the case of moving some or all of the connections between the UE and the resource connection node to the primary connection node, after the mobile is successful, the primary connection node and the UE continue to receive and transmit information on the connection to the primary connection node. Thereby the deletion of the connection or the movement of the connection and the connection of the data are achieved.

In the first example, the resource connection node determines to delete or move some or all connections between the UE and the resource connection node to the primary connection node, and the primary connection node accesses the anchor point of the MME as the UE control plane, and can learn the UE. Information about all connections established between the nodes connected to the resources, and when the UE establishes a connection with the resource connection node, the primary connection node reserves a reservation for each connection on the Xn interface of the resource connection node and the primary connection node. The upstream and downstream GTP-U (GPRS Tunneling Protocol for the user plane) tunnel for data forwarding. In this case, the connection management process is as shown in Figure 8, including steps 801 to 804:

Step 801. The user equipment reports a measurement report to the resource connection node, where the measurement report includes the measurement result of the cell 2. See the description of step 701 above.

Step 802. The resource connection node decides to delete some or all of the connections on the resource connection node. In addition to or move to the primary connection node. See the description of step 702 above.

Step 803. The resource connection node directly sends the transmission sequence status of the data transmission on each deleted/removed connection to the primary connection node, for example, including the uplink PDCP SDU (Packet Data Convergence Protocol Service Data Unit). The reception status indication, the count number of the first lost uplink PDCP SDU, the count number of the first lost downlink PDCP SDU, and the like. This step is not required for the case where the connection is deleted and the data on the connection has been transferred.

Step 803-1. This step is optional. For the case where the deleted/removed connection is Acknowledge Mode (AM), the resource connection node forwards the data to the primary connection node.

Step 803-x. The resource connection node sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message deletes or reconfigures some or all of the connections between the UE and the resource connection node to the primary connection node.

The above steps 803-x for the resource connection node to notify the UE to delete or reconfigure part or all of the connections on the air interface and the steps 803 and 803-1 for transmitting the transmission sequence status and forwarding data to the primary connection node on the Xn interface by the resource connection node on the Xn interface Can be executed in parallel.

Step 804. The UE directly sends an RRC connection reconfiguration response message to the resource connection node.

For the description of this step, refer to the description of step 705 above. See also the description of operation one or operation two above.

According to the above operation, for the case of deleting part or all of the connection between the UE and the resource connection node, the resource connection node and the UE stop receiving and transmitting information on the deleted part or all of the connection. For the case of moving some or all of the connections between the UE and the resource connection node to the primary connection node, after the mobile is successful, the primary connection node and the UE continue to receive and transmit information on the connection to the primary connection node. Thereby the deletion of the connection or the movement of the connection and the connection of the data are achieved.

Using the method of the first example, the connection management between the UE and the resource connection node in the dual connectivity architecture is implemented.

9 is a flowchart of a connection mobility management method of the second embodiment. The UE originally establishes a connection with one or more connection nodes, and the process includes steps 901 to 902: Step 901. The resource connection node determines that some or all connections between the UE and the resource connection node need to be deleted or moved;

Step 902. The resource connection node initiates the deleting or moving operation;

The operation of this step is further divided into the following two steps:

Step 902-1. The resource connection node notifies the primary connection node that the resource connection node needs to delete or move the connection;

Step 902-2. After receiving the notification, the primary connection node notifies the UE to delete or move (reconfigure) the connection.

In the second example, when the resource connection node decides to delete or move part or all of the connection between the UE and the resource connection node to the primary connection node, the connection management process includes the following steps 1001 to 1007:

Step 1001: The user equipment reports a measurement report to the resource connection node, where the measurement report includes the measurement result of the cell 2. See the description of step 701 above.

Step 1002. The resource connection node decides to delete or move some or all of the connections on the resource connection node to the primary connection node.

Step 1003. The resource connection node sends a connection reconfiguration request to the primary connection node. A description of the connection reconfiguration request can be found in the description of step 703 above.

Step 1004. The primary connection node returns a connection reconfiguration response to the resource connection node. A description of the connection reconfiguration response can be found in the description of step 704 above.

Step 1004-x. The primary connection node sends an RRC connection reconfiguration message to the UE. The RRC Connection Reconfiguration message deletes or reconfigures some or all of the connections between the UE and the resource connection node to the primary connection node.

Above the primary connection node on the air interface informs the UE to delete or reconfigure part or all of the connection The step 1004-x and the step 1004 of the primary connection node feeding back the connection reconfiguration response to the resource connection node on the Xn interface may be performed in parallel.

Step 1005. The resource connection node sends, to the primary connection node, a transmission sequence status of the data transmission on each of the deleted/removed connections, for example, including an uplink PDCP SDU (Packet Data Protocol Protocol Service Data Unit). The reception status indication, the count number of the first lost uplink PDCP SDU, the count number of the first lost downlink PDCP SDU, and the like.

Step 1005-1. This step is optional. For the case where the deleted/removed connection is Acknowledge Mode (AM), the resource connection node forwards the data to the primary connection node.

The above steps 1005 and 1005-1 can be performed in parallel.

Step 1006: The UE sends an RRC Connection Reconfiguration Response message to the primary connection node.

Step 1007. The primary connection node notifies the resource connection node that the connection reconfiguration succeeds, that is, the connection is deleted or the mobile is successful.

As can be seen from the above example, for the case of deleting a partial or all connection between the UE and the resource connection node, the resource connection node and the UE stop receiving and transmitting information on the deleted part or all of the connection. For the case of moving some or all of the connections between the UE and the resource connection node to the primary connection node, after the mobile is successful, the primary connection node and the UE continue to receive and transmit information on the connection to the primary connection node. Thereby the deletion of the connection or the movement of the connection and the connection of the data are achieved.

Example 2

The embodiment provides a node device, which can implement the mobility connection management method of the foregoing embodiment 1, which includes at least two units as shown in FIG.

The first unit is configured to determine, when the node is a resource connection node, whether to manage part or all of the connection between the resource connection node and the UE;

The first unit may be further configured to determine, according to one or more of the following information, that part or all of the connection between the UE and the resource connection node needs to be deleted or moved:

Measurement report, RRM algorithm, load information of the resource connection node, and service reported by the user equipment transmit information.

a second unit, configured to determine that a partial or all connection between the resource connection node and the UE needs to be managed, and initiate a management operation to the UE, where the management operation is to delete or move the part or all connections;

In a different application scenario, the node device may be a master node device in addition to the resource node device, and thus the node device further includes a third unit. The third unit is configured to: when the local node device is the primary connection node device, receive a notification that the resource connection node needs to perform a management operation on a part or all of the connection between the UE and the resource connection node, and initiate the notification to the UE according to the notification. Manage operations.

In addition, the foregoing node device may further include a fourth unit, configured to reserve an Xn interface between the resource connection node and the primary connection node for each connection between the UE and the resource connection node when the local node device is the primary connection node device. A tunnel for uplink and downlink user plane GPRS tunneling protocols for data forwarding. At this time, for the resource node device, the management operation can be directly initiated to the UE.

For the operation of the foregoing node device as the resource node device, refer to the corresponding content in the foregoing Embodiment 1, and details are not described herein again. For the same reason, the operation of the foregoing node device as the master node device can also be referred to the corresponding content in the foregoing embodiment 1, and details are not described herein again. In addition, the foregoing node device is an access network element that performs the above functions, and the non-limiting device may be a base station, a wireless network controller, or the like that performs the above functions.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct the associated hardware, such as a read only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. This application is not limited to any specific combination of hardware and software. The above is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the embodiments of the present invention. Any modifications, equivalent substitutions, improvements, etc., which are within the spirit and scope of the embodiments of the present invention, are intended to be included within the scope of the present invention.

Industrial applicability

Claims

Claim

A connection mobility management method, the method comprising:

When a user equipment (UE) establishes a connection with one or more connection nodes, where one or more resource connection nodes determine that some or all connections between the UE and the resource connection node need to be managed, the resource connection The node initiates a management operation to the UE, where the management operation is to delete or move the part or all of the connections, where the resource connection node initiates a management operation to the UE through the primary connection node, or the resource connection node directly A management operation is initiated to the UE.

2. The method according to claim 1, wherein the resource connection node determines that management of a part or all of the connection between the UE and the resource connection node is required:

The method according to claim 1 or 2, wherein the process in which the resource connection node initiates a management operation to the UE through the primary connection node is as follows:

4. The method of claim 3, wherein

When the resource connection node notifies the primary connection node that a partial or all connection between the UE and the resource connection node needs to be managed, the connection to be managed refers to the user carried by the resource connection node. Part or all of the radio access bearer (RAB) of the data transmission.

5. The method according to claim 3, wherein, after the primary connection node receives the notification, the connection initiated by the UE to perform a management operation refers to:

Part or all of the user plane data radio bearer between the UE and the resource connection node (DRB); or,

6. The method of claim 1, wherein

When the primary connection node reserves the uplink and downlink user plane GPRS tunneling protocol tunnel for data forwarding on the Xn interface of the resource connection node and the primary connection node for each connection between the UE and the resource connection node And the resource connection node directly initiates a management operation to the UE.

The method according to claim 1 or 6, wherein, when the resource connection node initiates a management operation directly to the UE, the connection to be managed is:

(DRB); or,

8. A node device, comprising:

a first unit, configured to determine, when the node is a resource connection node, whether to manage part or all of the connection between the resource connection node and a user equipment (UE);

a second unit, configured to initiate a management operation to the UE when determining that a part or all of the connection between the resource connection node and the UE needs to be managed, where the management operation is to delete or move the part or all Connection operation

The second unit is further configured to initiate a management operation to the UE by using the primary connection node, or initiate a management operation directly to the UE.

The node device according to claim 8, wherein the first unit is configured to determine, according to one or more of the following information, that a part between the UE and the resource connection node needs to be deleted or moved. Or all connections:

10. The node device of claim 9, the node device further comprising: a third unit, configured to receive, when the local node device is a primary connection node device, a notification that the resource connection node needs to perform a management operation on a part or all of the connection between the UE and the resource connection node, and A management operation is initiated to the UE according to the notification.

The node device according to claim 8 or 9, the node device further includes: a fourth unit, configured to: when the node device is a primary connection node device, the UE and the resource connection node Each connection between the resource connection node and the Xn interface of the primary connection node reserves a tunnel for uplink and downlink user plane GPRS tunneling protocols for data forwarding.