WO2017190296A1 - 切换用户设备方法及设备 - Google Patents

切换用户设备方法及设备 Download PDF

Info

Publication number
WO2017190296A1
WO2017190296A1 PCT/CN2016/081030 CN2016081030W WO2017190296A1 WO 2017190296 A1 WO2017190296 A1 WO 2017190296A1 CN 2016081030 W CN2016081030 W CN 2016081030W WO 2017190296 A1 WO2017190296 A1 WO 2017190296A1
Authority
WO
WIPO (PCT)
Prior art keywords
control plane
source
base station
identifier
target
Prior art date
Application number
PCT/CN2016/081030
Other languages
English (en)
French (fr)
Inventor
朱方园
李岩
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16900818.2A priority Critical patent/EP3445086B1/en
Priority to PCT/CN2016/081030 priority patent/WO2017190296A1/zh
Priority to CN201680085311.XA priority patent/CN109076404B/zh
Publication of WO2017190296A1 publication Critical patent/WO2017190296A1/zh
Priority to US16/179,717 priority patent/US20190075497A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a method and device for switching user equipment.
  • the Long Term Evolution (LTE) network has been widely used.
  • LTE Long Term Evolution
  • UE User Equipment
  • the UE occurs in the handover between the base stations, and in the handover process, the network side records the location information of the UE, so that the UE can be found at any time, and the service is provided to the user without interruption. Therefore, when the UE performs handover, it mainly performs the following two forms: one is switching based on the X2 interface, and the other is switching based on the S1 interface.
  • the two switching modes are based on different interfaces, which means that the resource preparation process during handover is performed through the X2 interface between the base stations or through the S1 interface between the base station and the MME. Therefore, if the control plane device does not change, it is possible to use the X2 interface-based handover or the S1 interface-based handover; if the control plane device changes, the S1 interface-based handover is required.
  • the two switching modes in the core network have certain conditional constraints: the switching of the X2 interface cannot replace the control plane device, and only the eNBs under the same control plane device can switch between each other. Although the switching of the S1 interface can replace the control plane device, it involves more signaling interaction between the access network and the core network. In the switching method provided above, the switching mode is not uniform, and once the switching across the control plane occurs, the switching delay is caused, and the switching efficiency is low.
  • the embodiment of the invention provides a method and device for switching user equipment.
  • the technical solution is as follows:
  • the first aspect provides a method for switching a user equipment UE, including:
  • the target base station acquires the source control plane identifier and the context identifier of the UE from the source base station; the target base station sends the source control plane identifier and the context identifier of the UE to the target control plane device, the source control plane identifier and The context identifier of the UE is used for acquisition of the context of the UE.
  • the target control plane may directly request the UE context from the source control plane by acquiring the source control plane ID and the UE context ID allocated by the source control plane from the target eNB, thereby switching the UE to the target cell.
  • the switching of the X2 interface across the control plane is realized, thereby unifying the process of acquiring the context of the core network, simplifying the implementation of the core network, reducing the switching delay and improving the switching efficiency in the process of switching across control planes.
  • the process of automatically establishing a connection between the base stations can implement direct interaction between the target eNB and the source eNB, avoiding the process of forwarding by the core network, and greatly reducing the delay.
  • the method further includes:
  • the method further includes: the target base station triggering release of the source side device resource.
  • the source-side device refers to the source control plane device, the source base station, and other devices. By timely monitoring the release of resources, resources of the source-side device are avoided.
  • the target base station triggering release of the source side device resource includes: when the target base station receives the source forwarding plane change indication sent by the target control plane, the target base station is sent to the source The base station sends a resource release message, where the resource release message carries a source forwarding plane gateway change indication.
  • control plane device includes a mobility management entity; or a centralized control plane device.
  • the method can be applied to the traditional EPC architecture, and can also be applied to the CU separation architecture.
  • a second aspect provides a method for switching a user equipment UE, including: a target control plane device receiving a source control plane identifier sent by a target base station and a context identifier of the UE; and the target control plane device according to the source control plane identifier and the The context identifier of the UE acquires the context of the UE. Further, the target eNB determines whether it is a cross-control plane handover according to information such as a source control plane identifier provided by the source eNB. If it is cross-control plane switching, according to the load situation, a new control plane is selected as the target control plane, and the source control plane identifier and the UE context ID are sent to the target control plane. The new control plane determines the source control plane according to the source control plane identifier, and acquires the UE context from the source control plane, and implements an X2 interface switching method across the control plane.
  • the acquiring, by the target control plane device, the context of the UE according to the source control plane identifier and the context identifier of the UE includes:
  • the target control plane device is addressed to the source control plane according to the source control plane identifier, and sends a UE context request message to the source control plane, where the UE context request message carries a context identifier of the UE;
  • the control plane device receives the context of the UE returned by the source control plane.
  • the acquiring, by the target control plane device, the context of the UE according to the source control plane identifier and the context identifier of the UE includes: the target control plane device controls the source The face identifier and the context identifier of the UE are used as index information to acquire the context of the UE from a database.
  • the method further includes: determining, by the target control plane device, whether a forwarding plane gateway needs to be replaced; if the forwarding plane gateway needs to be replaced, the target control plane device is to the target
  • the base station sends a source forwarding plane change indication, where the source forwarding plane change indication is used to trigger release of the source side device resource.
  • control plane device includes: a mobility management entity; or a centralized control plane device.
  • a wireless communication system includes at least a user equipment UE, a source base station, a target base station, a source control plane device, and a target control plane device, where
  • the target base station is configured to acquire a source control plane identifier and a context identifier of the UE from the source base station, and send the source control plane identifier and the context identifier of the UE to the target control plane device;
  • the target control plane device is configured to receive the source control plane identifier and the context identifier of the UE, and obtain the context of the UE according to the source control plane identifier and the context identifier of the UE.
  • the target base station and the target control device in the wireless communication system are further configured to implement the method for switching user equipment according to any one of the first aspect and the second aspect.
  • a fourth aspect provides a base station, including multiple functional modules, for implementing the foregoing first aspect A method of switching user equipment in any of the possible implementations.
  • a fifth aspect provides a control plane device, including a plurality of function modules, for implementing a method for switching user equipment according to any of the foregoing possible implementation manners.
  • a base station comprising a transmitter, a receiver, a memory, and a processor coupled to the transmitter, the receiver, and the memory, respectively.
  • the base station may also include a common component such as an antenna, a baseband processing component, a medium-frequency radio processing component, and an input/output device, and the embodiment of the present invention is not limited thereto.
  • the base station is configured to: obtain a source control plane identifier and a context identifier of the UE from a source base station; the target base station sends the source control plane identifier and a context identifier of the UE to a target control plane device And the source control plane identifier and the context identifier of the UE are used for obtaining the context of the UE.
  • the base station is configured to: automatically establish a connection relationship between the target base station and the source base station, and obtain a source control plane identifier by using the source base station And a context identifier of the UE.
  • the base station is configured to: determine, according to the source control plane identifier, whether the target base station and the source control plane are There is a connection relationship; if there is no connection relationship with the source control plane, a control plane is selected as the target control plane.
  • the base station is configured to perform the following operations: triggering release of source side device resources.
  • the base station is configured to: when receiving a source forwarding plane change indication sent by the target control plane, send a resource release message to the source base station, where the resource is released The message carries a source forwarding plane gateway change indication.
  • control plane device includes a mobility management entity; or a centralized control plane device.
  • a control plane device comprising a transmitter, a receiver, a memory, and a processor coupled to the transmitter, the receiver, and the memory, respectively.
  • the control plane device may further include a common component such as an antenna, a baseband processing component, a medium RF processing component, and an input/output device.
  • a common component such as an antenna, a baseband processing component, a medium RF processing component, and an input/output device.
  • the control plane device is configured to: receive a source control plane identifier sent by the target base station and a context identifier of the UE; and acquire a context of the UE according to the source control plane identifier and the context identifier of the UE.
  • control plane device is configured to: address the source control plane according to the source control plane identifier, and send a UE context request to the source control plane a message, the UE context request message carries a context identifier of the UE; and receives a context of the UE returned by the source control plane.
  • control plane device is configured to: obtain the source control plane identifier and the context identifier of the UE as index information, and acquire the UE from a database Context.
  • control plane device is configured to: determine whether a forwarding plane gateway needs to be replaced; if the forwarding plane gateway needs to be replaced, send a source forwarding plane change to the target base station Instructing, the source forwarding plane change indication is used to trigger release of the source side device resource.
  • control plane device includes: a mobility management entity; or a centralized control plane device.
  • EPC Evolved Packet Core
  • FIG. 2 is a schematic diagram of a Self Organization Network (hereinafter referred to as SON) based on a traditional EPC network architecture;
  • SON Self Organization Network
  • FIG. 3 is an interaction flowchart of a method for handover UE based on the traditional EPC network architecture shown in FIG. 2;
  • FIG. 4 is an interaction flowchart of another method for handover UE based on the conventional EPC network architecture shown in FIG. 2;
  • CU Control/User plane
  • FIG. 6 is an interaction flowchart of a handover UE method based on the CU network architecture shown in FIG. 5;
  • FIG. 7 is an interaction flowchart of another method for handover UE based on the CU network architecture shown in FIG. 5;
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a control plane device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a control plane device according to an embodiment of the present invention.
  • Mobility Management Entity responsible for user mobility management, including user context and mobility state management, assigning user temporary identity, authenticating and authorizing users;
  • SGW Serving Gateway
  • QoS control supporting the main QoS parameters of the bearer, including QCI, ARP, GBR, responsible for information storage, and saving the EPS bearer context, including the tunnel identifier and the user identifier;
  • Packet Data Network Gateway is a forwarding plane anchor between the 3GPP access network and the non-3GPP access network, and an interface of an external packet data network (PDN). It can be combined with the SGW, responsible for IP address allocation, bearer establishment, modification and release, policy and charging rules function (Policy and Charging Rules Function, PCRF) selection, QoS control, policy and accounting execution function,
  • the bearer evolution system (Evolved Packet System, hereinafter referred to as EPS) bearer context, including the tunnel identifier and the user identifier;
  • eNB 1) for implementing radio resource management related functions, including radio bearer control; 2) transmission of paging message: after receiving the paging message from the control plane, the eNB sends a paging message to the air interface; 3) During the handover process, the eNB determines the handover and prepares resources required for handover;
  • Gateway user (Gateway-User, hereinafter referred to as GW-U): has the functions of user packet forwarding, encapsulation, and statistics;
  • Control plane integrates functions such as MME and gateway control plane. In addition to responsible for user mobility management, it also has IP address allocation, gateway user plane device selection, bearer management, and generation of gateway user plane forwarding rules.
  • SON mainly includes three functions, namely self-configuration, self-optimization, and self-healing.
  • the self-configuration function includes automatic acquisition of an IP address and automatic neighbor relationship configuration. Obtaining an IP address automatically means that the eNB automatically obtains an IP address after power-on and obtains the IP address of the NMS and access gateway.
  • the automatic neighbor relationship configuration is to establish an automatic neighbor relationship through the neighbor relationship list delivered by the network during the eNB self-establishment process. After the eNB enters the working state, the automatic neighbor relationship is optimized, thereby reducing the optimization and planning manpower. cost.
  • the automatic establishment of the eNB is one of the most basic functions of the SON. According to the standard protocol, a new eNB can automatically establish an IP connection between the eNB and the network element management (EM) when entering the network, and can automatically download software and automatically download wireless parameters and transmissions. Configure related data. Supports the automatic establishment of the X2 interface. After the establishment is completed, the eNB can self-check the working status and report the inspection result to the network management center.
  • EM network element management
  • FIG. 2 is a system architecture diagram of an embodiment of the present invention.
  • the system includes: a source MME, a target MME, a source SGW, a target SGW, and a PGW, and further includes a plurality of eNBs.
  • the system should also include devices such as UEs, which are not shown in the figure.
  • the source eNB refers to an eNB that is accessed before the UE changes its location
  • the target eNB is an eNB that is selected by the UE after the location eNB determines that the source eNB needs to perform handover.
  • the eNBs that access the same MME have an X2 interface, and the MME and the eNB have an S1 interface.
  • the self-configuration process of the eNB that supports the SON can automatically obtain an IP address. And configuring an X2 interface between eNBs that access different MMEs, so that eNBs accessing different MMEs can directly interact with each other through the self-configured X2 interface to implement X2 handover.
  • the source eNB automatically acquires the target eNB. Address without the core network, and the eNB is not subject to the jurisdiction of the control plane.
  • FIG. 3 is an interaction flowchart of a handover method according to an embodiment of the present invention.
  • the interaction flowchart of FIG. 3 is performed based on the system architecture shown in FIG. 2, and is used to describe an interaction scenario that does not involve SGW replacement.
  • the embodiment includes:
  • the source eNB performs an X2 interface connection with the target eNB through automatic configuration of the SON.
  • the decision process in the handover process is not described in detail. How does the specific UE report the measurement report and how the source eNB determines whether to perform the handover or the handover based on the UE's measurement report or other information, and the embodiments of the present invention are Not limited.
  • the source eNB makes a handover decision and decides which eNB to use as the target eNB for handover. If the source eNB does not store the IP address of the target eNB, the source eNB and the target eNB may not be connected. The same MME needs to perform step 300 to automatically configure the X2 interface between the eNBs.
  • the source eNB sends a handover request message to the target eNB, where the handover request message carries the GUMMEI and the MME UE S1AP ID of the source MME.
  • the target eNB determines that the target eNB has no connection with the source MME according to the GUMMEI of the source MME, then a new MME is selected to perform handover according to the load condition.
  • the selection of the MME according to the load condition means that the target eNodeB needs to select a MME pool to provide services for the UE. There are many MMEs in the MME Pool. The eNodeB selects the MME Pool based on the network topology and the average load of the MME Pool, so that the probability of changing the serving MME when the UE moves next is reduced.
  • the target eNB When receiving the handover request message, the target eNB sends a path switch request message to the target MME.
  • the path switch request message includes a cell global identifier of the target cell (Tracking Area Identity (TAI) + E-UTRAN Cell Global Identifier (ECGI) and The converted EPS bearer list, the UE security capability (Security Capabilities), the Closed Subscriber Group Identity (CSG ID), and the Cell Access Mode (hereinafter referred to as CAM).
  • the difference from the prior art is that the path switch request message further includes a source control plane identifier MME Globally Unique MME Identifier (hereinafter referred to as: GUMMEI) and a source MME user context identifier UE S1AP ID (user context identifier).
  • the path switching request message may acquire the context of the UE from the source MME by using the source MME GUMMEI (control plane identifier) and the user context identifier of the source MME, the UE S1AP ID (user context identifier).
  • the GUMMEI is a part of the Globally Unique Temporary Identity (GUTI), which can be used to uniquely identify the MME that allocates the GUTI.
  • the MME UE S1AP ID is used by the MME to uniquely identify the UE on the S1 interface.
  • the target MME When the target MME receives the path switch request sent by the target eNB, query the UE context locally according to the source MME UE S1AP ID.
  • the target MME When the target MME receives the path switch request sent by the target eNB, it can be known that this is a handover event, so the query of the UE context can be attempted locally.
  • the UE sends a UE context request message to the source MME indicated by the source MME GUMMEI, where the UE context request message carries the source MME UE S1AP ID.
  • the step 304 may include the target MME sending a UE context request message to the source MME according to the process of the source control plane identifier being addressed to the source control plane.
  • the source MME receives the UE context request message, query the UE context from the source according to the source MME UE S1AP ID.
  • the UE context includes the IMSI, the UE core network capability, the TA list, the cell ID where the UE resides on the source side, the address and TEID of the SGW/PGW on the S11 interface, the PDN type, the EPS bearer identifier, and the user's (Access Point Name, below) Abbreviation: APN), default EPS bearer QoS, PDN type, and so on.
  • the S11 interface refers to an interface between the MME and the SGW.
  • the source MME sends the UE context to the target MME.
  • the source MME After the source MME sends the UE context to the target MME, the source MME starts a timer to monitor when to release the UE resources stored by the source eNB and the locally stored UE resources.
  • the target MME determines whether to replace the SGW according to the UE context and the target cell ID.
  • the target MME may determine, according to the address of the S11 interface and the target cell ID of the SGW/PGW carried in the UE context, whether the path between the SGW and the target cell is an optimized path, if it is an optimal path. If you change the path, you can decide not to replace the SGW. If you are not optimizing the path, you can decide to replace the SGW.
  • a create session request message can be sent to the SGW according to the address obtained in step 305, where the create session request message includes the EPS bearer to be established. , the user's APN, the address and TEID of the target eNB of the user plane, and so on.
  • the SGW/PGW sends a create session response message to the target MME.
  • the target MME When the target MME receives the create session response message, the target MME sends a path switch request response message to the target eNB.
  • the path switch request response message includes an address and a TEID allocated by the SGW to the uplink data on the user plane.
  • the source MME After the timer expires, the source MME sends a resource release message to the source eNB to notify the source eNB to release the locally stored UE resources.
  • the source MME may also release the UE resource locally stored by the source MME.
  • the target MME completes the handover process according to the UE context.
  • the specific handover process may include a process in which the target MME synchronizes the UE to the target cell according to the UE context, and details are not described herein.
  • the embodiment shown in FIG. 3 is a handover method performed in a scenario where no SGW replacement is required, and in the handover process, the SGW may be replaced for the optimization of the routing path or the interface between the source SGW and the target MME.
  • 4 is an interaction flowchart of a handover method according to an embodiment of the present invention, which is used to describe an interaction scenario involving SGW replacement. Specifically, the embodiment includes:
  • the source eNB performs an X2 interface connection with the target side eNB through SON automatic configuration.
  • This step 400 is the same as step 300, and will not be described here.
  • the source eNB sends a handover request message to the target eNB, where the handover request message carries the GUMMEI and the MME UE S1AP ID of the source MME.
  • the target eNB sends a path switch request message to the target MME.
  • target MME When the target MME receives the path switch request message sent by the target eNB, query the UE context locally according to the source MME UE S1AP ID.
  • the target MME fails to perform the local query, send a UE context request message to the source MME indicated by the source MME GUMMEI, where the UE context request message carries the source MME UE S1AP ID.
  • the source MME receives the UE context request message, query the UE context locally according to the source MME UE S1AP ID.
  • the source MME sends the UE context to the target MME.
  • the target MME After receiving the UE context, the target MME decides to replace the SGW.
  • the target MME sends a UE context response message to the source MME, where the UE context response message carries an SGW change flag.
  • the source MME receives the UE context response message of the target MME, it is learned that the target MME side replaces the SGW, and starts a timer to monitor when to release the UE resource stored by the source eNB and the UE resource stored by the source SGW.
  • the target MME may decide to replace the SGW for the optimization of the routing path or the interface between the source SGW and the target MME, so that the replacement of the SGW needs to be notified to the source MME.
  • the target MME sends a create session request message to the target SGW, where the create session request message includes an address and a TEID, a bearer context, a PGW address, a TEID, and the like of the target eNB for the user plane.
  • the target SGW After receiving the create session request message, the target SGW sends a modify bearer request message to the PGW according to the received PGW address, where the modify bearer request message includes the SGW address and TEID of the target SGW downlink data allocation.
  • the PGW When receiving the modify bearer request message, the PGW sends a modify bearer response message to the target SGW, where the modify bearer response message includes a PGW address and a TEID allocated by the PGW for the uplink data. Charging ID.
  • the modified bearer response message may further include a charging ID, that is, a charging ID, for the PGW to charge the packet.
  • the target SGW After receiving the modify bearer response message, the target SGW sends a create session response message to the target MME, where the create session response message includes an address and a TEID allocated by the user plane target SGW for the uplink data.
  • the target MME sends a path switch request response message to the target eNB, where the path switch request response message includes an address and a TEID allocated by the user plane target SGW for the uplink data.
  • the source MME sends a resource release message to the source eNB.
  • the UE resource may include: a radio bearer of the UE and all resources related to the UE context of the control plane.
  • the source MME sends a delete session request message to the source SGW, where the delete session request message is used to release the UE resource stored by the source SGW.
  • the foregoing embodiment of FIG. 3 and FIG. 4 respectively describe the UE handover procedure in the traditional EPC network architecture.
  • the target MME may directly obtain the source control plane ID and the UE context ID allocated by the source MME from the target eNB.
  • the MME requests the UE context to switch the UE to the target cell, and implements the switching of the X2 interface across the control plane, thereby unifying the process of acquiring the context of the core network, simplifying the implementation of the core network, and reducing the cross-control plane switching process. Switching delays improve switching efficiency.
  • the target eNB determines whether to switch across the MME according to information such as the source control plane identifier provided by the source eNB. If the MME is switched, the new MME is selected as the target MME according to the load, and the source control plane identifier and the UE context ID are sent to the target MME. The new MME determines the source MME according to the source control plane identifier, and acquires the UE context from the source MME, and implements an X2 interface switching method across the control plane.
  • FIG. 5 is a structural diagram of a CU separation mobile network system according to an embodiment of the present invention.
  • the CU separation network architecture decouples the control plane function of the mobile gateway from the forwarding plane function, and combines the separated control plane function (GW-C) with the 3GPP traditional control network element MME, PCRF, etc. into a unified control plane.
  • the forwarding plane GW-U includes a forwarding plane (SGW-U) of the S-GW and a forwarding plane (PGW-U) of the P-GW.
  • the system includes: a source control plane device, a target control plane device, a source GW-U, a target GW-U, an SDN control device, and the like, and further includes multiple eNBs.
  • the system should also include UEs and the like. , not shown in the figure.
  • the difference from the architecture shown in FIG. 2 is that the system shown in FIG. 5 further includes a database as shown by the dashed box in the figure. After the UE enters the network, the control plane Controller synchronizes the UE context to the database, so that the database can The context is managed centrally.
  • the neighboring eNBs in the system can automatically establish an X2 interface through SON.
  • the source eNB makes a handover decision and decides which target eNB to switch to. If the source eNB does not store the IP address of the target eNB, the source eNB automatically establishes an X2 interface connection with the target eNB through SON automatic configuration.
  • the source eNB sends a handover request message to the target eNB, carrying the ID of the source controller. If the target eNB has no connection with the source controller, a new controller is selected according to the load condition to perform handover.
  • the target eNB In the path switch request message, the target eNB must carry the control plane identifier ID and the user context identifier ID, so that the target controller acquires the UE context from the source controller. After that, the target controller synchronizes the UE to the target cell according to the UE context, and completes the handover process.
  • FIG. 6 is a handover process of forwarding a separate mobile network architecture. Since the GW-U is only connected to one Controller after the CU is separated, the handover across the Controller necessarily involves replacing the GW-U. Therefore, providing a scenario involving replacement of the GW-U is provided. Switching method embodiment, the specific process is shown in Figure 6:
  • the source eNB performs an X2 interface connection with the target eNB through automatic configuration of the SON.
  • This step 600 is the same as step 300, and will not be described here.
  • the source eNB sends a handover request message to the target eNB, where the handover request message carries the source controller ID and the user context identifier UE S1AP ID of the source controller.
  • the target eNB sends a path switch request message to the target controller.
  • the path switch request message includes a cell global identifier (TAI+ECGI) of the target cell, and the converted EPS bearer list, the UE Security Capabilities, the CSG ID, and the Cell Access Mode, which are different from the prior art in that the path switch
  • the request message further includes a source controller ID (control plane identifier) and a user context identifier of the source controller, a UE S1AP ID (user context identifier), and the path switch request message may be carried by the source controller ID (control plane identifier) and the source controller.
  • the user context identifies the UE S1AP ID (user context identifier), and obtains the context of the UE from the source controller.
  • the source controller ID uniquely identifies the control plane, and the Controller UE S1AP ID is used by the controller to uniquely identify the UE on the S1 interface.
  • the target controller When the target controller receives the path switch request message sent by the target eNB, query the UE context locally according to the source Controller UE S1AP ID.
  • the target controller fails to perform the local query, send a UE context request message to the source controller indicated by the source controller ID, where the UE context request message carries the source Controller UE S1AP ID.
  • the source controller receives the UE context request message, query the UE context locally according to the source Controller UE S1AP ID.
  • the source controller sends the UE context to the target controller.
  • the target controller After receiving the UE context, the target controller sends a UE context response message to the source controller, where the UE context response message carries a GW-U change indication.
  • the target controller may determine whether to replace the forwarding plane gateway according to the cell location and the target cell location before the UE is switched. If the target controller is determined to be replaced, the resource release process of the source device may be triggered by the target controller, and step 607 is performed.
  • the UE context response message is sent to inform the source controller of the GW-U replacement, so that the source controller supervises the release of the source side resources.
  • the source controller receives the UE context response message of the target controller, it is learned that the target controller side replaces the GW-U, and starts a timer to supervise when to release the UE resource stored by the source eNB and the UE stored by the source GW-U. Resources.
  • the target controller After receiving the UE context, the target controller sends a downlink data forwarding rule to the target GW-U to indicate how the gateway forwarding plane processes the IP packet sent by the UE.
  • the target controller sends a path switch request response message to the target eNB.
  • the source controller sends a resource release message to the source eNB.
  • the source controller may also release the UE resource locally stored by the source controller.
  • the source controller sends a resource release message to the source GW-U.
  • steps 611 and 613 may be performed at the same time, or may be performed one after the other.
  • the actual execution sequence of the source controller is not limited.
  • the UE resources can be released.
  • the UE context in the embodiment shown in FIG. 6 is sent by the source controller to the target controller, and in another embodiment, the UE context can also be obtained from the database, as shown in FIG. 7, when the UE enters the network, any one of them
  • the controller such as the source controller in this embodiment, updates the database to the locally cached UE context, and the database centrally manages the storage of the control plane to implement dynamic resource migration and disaster recovery backup.
  • the source eNB performs an X2 interface connection with the target eNB through automatic configuration of the SON.
  • This step 700 is the same as step 300, and will not be described here.
  • the source eNB sends a handover request message to the target eNB, where the handover request message carries the source controller ID and the user context identifier UE S1AP ID of the source controller.
  • the target eNB sends a path switch request message to the target controller.
  • a new controller is selected to perform handover according to the load condition, and the selected Controller is also the target controller.
  • the path switch request message includes a cell global identifier (TAI+ECGI) of the target cell, and the converted EPS bearer list, the UE Security Capabilities, the CSG ID, and the Cell Access Mode, which are different from the prior art in that the path switch
  • the request message further includes a source controller ID (control plane identifier) and a user context identifier of the source controller, a UE S1AP ID (user context identifier), and the path switch request message may be carried by the source controller ID (control plane identifier) and the source controller.
  • the user context identifies the UE S1AP ID (user context identifier), and obtains the context of the UE from the source controller.
  • the source controller ID uniquely identifies the control plane, and the Controller UE S1AP ID is used by the controller to uniquely identify the UE on the S1 interface.
  • the target controller When the target controller receives the path switch request message sent by the target eNB, query the UE context locally according to the source Controller UE S1AP ID.
  • the database predicts the range of the area that the UE may move according to the UE movement trajectory or the location, and actively pushes the UE context to the target controller, and if the query is unsuccessful in step 703, the previous database intelligence is indicated. If the push fails, you need to obtain the UE context information from the database by using the source controller ID and the source Controller UE S1AP ID.
  • the target controller fails in the local query, send a UE context request message to the database, where the UE context request message carries the source Controller ID and the source Controller UE S1AP ID.
  • the UE context includes an IMSI, a UE core network capability, a TA list, a cell ID where the UE resides on the source side, an EPS bearer identifier, a user's APN, a default EPS bearer QoS, and the like.
  • the database sends the UE context to the target controller.
  • the foregoing steps 704 to 706 are processes in which the target control plane device uses the source control plane identifier and the context identifier of the UE as index information to acquire the context of the UE from a database.
  • the target controller After receiving the UE context, the target controller sends a downlink data forwarding rule to the target GW-U, where the target forwarding plane processes the IP packet sent by the UE.
  • the target controller may determine whether to replace the forwarding plane gateway according to the cell location and the target cell location before the UE is switched. If the target controller is determined to be replaced, the target controller may trigger the resource release process of the source side device by using the target eNB.
  • the target controller sends a path switch request response message to the target eNB, where the path switch request response message carries a GW-U change indication.
  • the embodiment of the present invention does not limit the order of execution between steps 707 and 708.
  • the target eNB After receiving the path switch request response message, the target eNB sends a resource release message to the source eNB, where the resource release message carries a GW-U change indication.
  • the source eNB After receiving the resource release message, the source eNB sends a resource release message to the source controller, where the resource release message carries a GW-U change indication.
  • the source controller sends a resource release message to the source GW-U.
  • the source controller sends a resource release message to the source GW-U due to the replacement of the GW-U.
  • the foregoing embodiment of FIG. 6 and FIG. 7 respectively describe the UE handover process in the CU network architecture.
  • the target controller can obtain the source control plane ID and the UE context ID allocated by the source controller from the target eNB, and directly to the source controller. Requesting the UE context, or synchronizing the UE context to the target controller through the database, realizes switching of the X2 interface across the control plane, thereby reducing the control plane delay and improving the switching efficiency.
  • the target eNB refuses to find that the source control plane identifier and the target eNB have no connection relationship after acquiring the source side information from the X2 interface in the existing X2 handover process.
  • the X2 switch does not trigger the new control plane selection process. In other words, the existing X2 interface switching process cannot be switched across the control plane.
  • the target eNB determines whether to switch across the controller according to information such as the source control plane identifier provided by the source eNB. If it is a cross-Controller switch, according to the load situation, select a new Controller as the target Controller, and send the source control plane identifier and the UE context ID to the target Controller.
  • the target controller can obtain the UE context from the source controller according to the source control plane identifier, or synchronize the UE context to the target controller through the database, and implement an X2 interface switching method across the control plane.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • the base station includes:
  • the obtaining module 801 is configured to obtain, by the source base station, a source control plane identifier and a context identifier of the UE.
  • the sending module 802 is configured to send the source control plane identifier and the context identifier of the UE to the target control plane device, where the source control plane identifier and the context identifier of the UE are used for acquiring the context of the UE.
  • the acquiring module 801 is configured to automatically establish a connection relationship between the target base station and the source base station, where the target base station acquires a source control plane identifier and the UE by using the source base station. Context identifier.
  • the base station further includes: a selecting module, configured to determine, according to the source control plane identifier, whether the target base station has a connection relationship with a source control plane; if the target base station and the source control If there is no connection, select a control surface as the target control surface.
  • a selecting module configured to determine, according to the source control plane identifier, whether the target base station has a connection relationship with a source control plane; if the target base station and the source control If there is no connection, select a control surface as the target control surface.
  • the base station further includes: a release module, configured to trigger release of the source side device resource.
  • the releasing module is configured to: when receiving the source forwarding plane change indication sent by the target control plane, send a resource release message to the source base station, where the resource release message carries a source forwarding plane gateway change indication.
  • the base station provided by the foregoing embodiment implements the function of switching the user equipment
  • only the division of the foregoing various functional modules is illustrated.
  • the foregoing functions may be assigned different functions according to actual needs.
  • the module is completed, that is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the specific manner in which the respective modules perform the operations has been described in detail in the embodiment related to the method, and will not be described in detail herein.
  • FIG. 9 is a schematic structural diagram of a control plane device according to an embodiment of the present invention.
  • the control plane device includes:
  • the receiving module 901 is configured to receive a source control plane identifier sent by the target base station and a context identifier of the UE.
  • the obtaining module 902 is configured to obtain, according to the source control plane identifier and the context identifier of the UE, The context of the UE.
  • the obtaining module 902 is configured to address the source control plane according to the source control plane identifier, and send a UE context request message to the source control plane, where the UE context request message carries Determining a context identifier of the UE; receiving a context of the UE returned by the source control plane.
  • the obtaining module 902 is configured to obtain the context of the UE from a database by using the source control plane identifier and the context identifier of the UE as index information.
  • control plane device further includes:
  • a judging module configured to determine whether a forwarding plane gateway needs to be replaced
  • the sending module is configured to: if the determining module determines that the forwarding plane gateway needs to be replaced, send a source forwarding plane change indication to the target base station, where the source forwarding plane change indication is used to trigger release of the source side device resource.
  • control plane device includes: a mobility management entity; or a centralized control plane device.
  • control plane device provided by the foregoing embodiment implements the function of switching the user equipment
  • only the division of the foregoing various functional modules is illustrated.
  • the foregoing functions may be allocated according to actual needs.
  • Different functional modules are completed, that is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the specific manner in which the respective modules perform the operations has been described in detail in the embodiment related to the method, and will not be described in detail herein.
  • FIG. 10 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • the base station includes a transmitter, a receiver, a memory, and a processor coupled to the transmitter, receiver, and memory, respectively.
  • the base station may also include a common component such as an antenna, a baseband processing component, a medium-frequency radio processing component, and an input/output device, and the embodiment of the present invention is not limited thereto.
  • the base station is configured to perform the user equipment switching method on the base station side provided by any one of the foregoing embodiments of FIG. 3, FIG. 4, FIG. 6, or FIG.
  • the above transmitter and receiver can also be transceivers.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • FIG. 11 is a schematic structural diagram of a control plane device according to an embodiment of the present invention.
  • the control plane device includes a transmitter, a receiver, a memory, and a transmitter, respectively The processor that connects the receiver to the memory.
  • the control plane device may further include a common component such as an antenna, a baseband processing component, a medium-frequency radio frequency processing component, and an input/output device, and the embodiment of the present invention is not limited thereto.
  • the control plane device is configured to perform the user equipment switching method on the control plane device side provided by any one of the foregoing embodiments of FIG. 3, FIG. 4, FIG. 6, or FIG.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明是关于一种用户设备切换方法及设备，属于无线通信技术领域。所述方法包括：目标基站从源基站获取源控制面标识和所述UE的上下文标识；所述目标基站将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。本发明实现了跨控制面的X2接口的切换，简化了核心网实现。

Description

切换用户设备方法及设备 技术领域
本发明涉及无线通信技术领域，特别涉及一种切换用户设备方法及设备。
背景技术
随着通信技术的快速发展，长期演进(Long Term Evolution，以下简称LTE)网络得到了广泛的应用，在LTE网络中，当用户设备(User Equipment，以下简称UE)的位置发生改变时，可能会发生在UE在基站间的切换，而在切换过程中，网络侧要记录UE的位置信息，这样才能随时找到UE，不间断地为用户提供服务。因此，在UE在进行切换时，主要通过下述两种形式进行：一种是基于X2接口的切换，另一种是基于S1接口的切换。两种切换方式基于不同的接口，意味着切换时的资源准备过程是通过基站之间的X2接口进行，还是通过基站和MME之间的S1接口进行。因此，若控制面设备不改变时，既可能采用基于X2接口的切换，也可能采用基于S1接口的切换；若控制面设备发生改变，则需要使用基于S1接口的切换。
核心网中的两种切换方式实现起来都有一定的条件约束：X2接口的切换不能更换控制面设备，只能是同一个控制面设备下的eNB之间相互切换。S1接口的切换虽然可以更换控制面设备，但是涉及到接入网和核心网之间的信令交互较多。上述提供的切换方法，切换模式不统一，一旦发生跨控制面的切换，则会造成切换延时，切换效率较低。
发明内容
本发明实施例提供了一种切换用户设备方法及设备。所述技术方案如下：
第一方面，提供了一种切换用户设备UE的方法，包括：
目标基站从源基站获取源控制面标识和所述UE的上下文标识；所述目标基站将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。
通过本发明实施例提供的技术方案，目标控制面可以通过从目标eNB获取源控制面分配的源控制面ID和UE上下文ID，直接向源控制面请求UE上下文，从而将UE切换到目标小区，实现了跨控制面的X2接口的切换，从而统一了核心网获取上下文的流程，简化了核心网实现，在跨控制面切换过程中，减少了切换延时，提高了切换效率。
在第一方面的第一种可能实现方式中，所述目标基站从源基站获取源控制面标识和所述UE的上下文标识包括：所述目标基站自动建立所述目标基站和所述源基站之间的连接关系，所述目标基站通过所述源基站获取源控制面标识和所述UE的上下文标识。通过基站之间自动建立连接的过程，可以实现目标eNB和源eNB之间的直接交互，避免了由核心网的转发等过程，大大节约了时延。
基于上述任一种可能的实现方式，在第一方面的第二种可能实现方式中，所述方法还包括：
所述目标基站根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；若所述目标基站与所述源控制面无连接关系，则所述目标基站选择一个控制面作为目标控制面。为跨控制面的切换提供了实现的可能性。
基于上述任一种可能的实现方式，在第一方面的第二种可能实现方式中，所述方法还包括：所述目标基站触发释放源侧设备资源。其中，源侧设备是指源控制面设备、源基站等设备，通过及时监督资源的释放，避免对源侧设备的资源浪费。
在第一方面的第三种可能实现方式中，所述目标基站触发释放源侧设备资源包括：当所述目标基站接收到目标控制面发送的源转发面改变指示时，所述目标基站向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
基于上述任一种可能的实现方式，在第一方面的第四种可能实现方式中，所述控制面设备包括移动性管理实体；或者，集中控制面设备。该方法可以适用于传统EPC架构下，也可以适用于CU分离架构下。
第二方面，提供了一种切换用户设备UE的方法，包括：目标控制面设备接收目标基站发送的源控制面标识和UE的上下文标识；所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文。进一步地，目标eNB根据源eNB提供的源控制面标识等信息，确定是否是跨控制面切换。 如果是跨控制面切换，则根据负载情况，选择新的控制面作为目标控制面，并将源控制面标识和UE上下文ID发送给目标控制面。新的控制面根据源控制面标识确定源控制面，并从源控制面获取UE上下文，实现了一种跨控制面的X2接口切换方法。
在第二方面的第一种可能实现方式中，所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文包括：
所述目标控制面设备根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；所述目标控制面设备接收所述源控制面返回的所述UE的上下文。
在第二方面的第二种可能实现方式中，所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文包括：所述目标控制面设备将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文。
在第二方面的第三种可能实现方式中，所述方法还包括：所述目标控制面设备判断是否需要更换转发面网关；若需要更换转发面网关，所述目标控制面设备向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
在第二方面的第四种可能实现方式中，所述控制面设备包括：移动性管理实体；或者，集中控制面设备。
第三方面，提供了一种无线通信系统，所述无线通信系统至少包括用户设备UE、源基站、目标基站、源控制面设备和目标控制面设备，其中，
所述目标基站，用于从所述源基站获取源控制面标识和所述UE的上下文标识，将所述源控制面标识和所述UE的上下文标识发送至所述目标控制面设备；
所述目标控制面设备，用于接收所述源控制面标识和所述UE的上下文标识，根据所述源控制面标识和所述UE的上下文标识获取所述UE的上下文。
该无线通信系统中的目标基站和目标控制设备还用于实现上述第一方面和第二方面中任一种切换用户设备方法。
第四方面，提供了一种基站，包括多个功能模块，用于实现上述第一方面 中任一种可能实现方式的切换用户设备方法。
第五方面，提供了一种控制面设备，包括多个功能模块，用于实现上述第二方面中任一种可能实现方式的切换用户设备方法。
第六方面，提供了一种基站，该基站包括发射机、接收机、存储器以及分别与发射机、接收机和存储器连接的处理器。当然，基站还可以包括天线、基带处理部件、中射频处理部件、输入输出装置等通用部件，本发明实施例在此不再任何限制。
所述基站被配置为执行以下操作：从源基站获取源控制面标识和所述UE的上下文标识；所述目标基站将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。
在第六方面的第一种可能实现方式中，所述基站被配置为执行以下操作：自动建立所述目标基站和所述源基站之间的连接关系，通过所述源基站获取源控制面标识和所述UE的上下文标识。
基于上述任一种可能的实现方式，在第一方面的第二种可能实现方式中，所述基站被配置为执行以下操作：根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；与所述源控制面无连接关系，则选择一个控制面作为目标控制面。
基于上述任一种可能的实现方式，在第一方面的第二种可能实现方式中，所述基站被配置为执行以下操作：触发释放源侧设备资源。
在第六方面的第三种可能实现方式中，所述基站被配置为执行以下操作：当接收到目标控制面发送的源转发面改变指示时，向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
基于上述任一种可能的实现方式，在第六方面的第四种可能实现方式中，所述控制面设备包括移动性管理实体；或者，集中控制面设备。
第七方面，提供了一种控制面设备，该控制面设备包括发射机、接收机、存储器以及分别与发射机、接收机和存储器连接的处理器。当然，控制面设备还可以包括天线、基带处理部件、中射频处理部件、输入输出装置等通用部件， 本发明实施例在此不再任何限制。
所述控制面设备被配置为执行以下操作：接收目标基站发送的源控制面标识和UE的上下文标识；根据源控制面标识和所述UE的上下文标识获取所述UE的上下文。
在第七方面的第一种可能实现方式中，所述控制面设备被配置为执行以下操作：根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；接收所述源控制面返回的所述UE的上下文。
在第七方面的第二种可能实现方式中，所述控制面设备被配置为执行以下操作：将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文。
在第七方面的第三种可能实现方式中，所述控制面设备被配置为执行以下操作：判断是否需要更换转发面网关；若需要更换转发面网关，向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
在第七方面的第四种可能实现方式中，所述控制面设备包括：移动性管理实体；或者，集中控制面设备。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是传统演进分组核心(Evolved Packet Core，以下简称：EPC)网络架构示意图；
图2是基于传统EPC网络架构的自组织网络(Self Organization Network，以下简称：SON)示意图；
图3是基于图2所示的传统EPC网络架构的一种切换UE方法的交互流程图；
图4是基于图2所示的传统EPC网络架构的另一种切换UE方法的交互流程图；
图5是控制面用户面(Control/User plane，以下简称：CU)分离网络架构示意图；
图6是基于图5所示的CU网络架构的一种切换UE方法的交互流程图；
图7是基于图5所示的CU网络架构的另一种切换UE方法的交互流程图；
图8是本发明实施例提供的一种基站的结构示意图；
图9是本发明实施例提供的一种控制面设备的结构示意图；
图10是本发明实施例提供的一种基站的结构示意图；
图11是本发明实施例提供的一种控制面设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
下面，以图1所示的传统EPC网络架构为例，对本发明实施例所涉及到的一些设备进行简要介绍：
移动管理实体(Mobility Management Entity，以下简称：MME)：负责用户的移动性管理，包括用户上下文和移动状态管理，分配用户临时身份标识，认证和授权用户；
服务网关(Serving Gateway，以下简称：SGW)：是3GPP接入网络间的转发面锚点，通过与基站以及P-GW之间的传输隧道实现UE报文转发，负责承载的建立、修改和释放，QoS控制，支持承载的主要QoS参数，包括QCI，ARP，GBR，负责信息存储，保存EPS承载上下文，包括隧道标识、用户标识；
分组数据网关(Packet Data Network Gateway，以下简称：PGW):是3GPP接入网络和非3GPP接入网络之间的转发面锚点，和外部分组数据网络(Packet Data Network，以下简称PDN)的接口，可与SGW合设，负责IP地址分配，承载建立、修改和释放，策略与计费规则功能单元(Policy and Charging Rules Function，以下简称：PCRF)选择，QoS控制，策略与计费执行功能，保存分组演进系统(Evolved Packet System，以下简称：EPS)承载上下文，包括隧道标识，用户标识；
eNB：1)用于实现无线资源管理相关的功能，包括无线承载控制；2)寻呼消息的传输:eNB在接收到来自控制面的寻呼消息后，向空中接口发送寻呼消息；3)在切换过程中时，eNB对切换进行判断，以及对切换所需资源进行准备；
网关用户面(Gateway-User，以下简称：GW-U)：具有用户报文转发，封装，统计等功能；
控制面(Controller)：集成了MME和网关控制面等功能，除了负责用户的移动性管理，还具有IP地址分配，选择网关用户面设备，承载管理，生成网关用户面转发规则等功能。
为了帮助LTE运营商更好地管理网络中巨大数量并且可能来自不同设备厂家的基站，降低运营成本，减少人工参与，SON的概念应运而生，其主要思路是实现无线网络的一些自主功能。SON主要包括三大功能，分别是自配置(Self-configuration)、自优化(Self-optimization)、自愈(Self-healing)。其中，自配置功能包括自动获取IP地址和自动邻区关系配置。自动获取IP地址是指eNB上电后自动获取IP地址，并获得网管和接入网关的IP地址。自动邻区关系配置是eNB自建立过程中，通过网络下发的邻区关系列表进行自动邻区关系的建立，eNB进入工作状态后，进行自动邻区关系的优化，从而降低优化和规划的人力成本。
eNB自动建立是SON的最基本功能之一，根据标准协议，一个新eNB在进入网络时可以自动建立eNB和网元管理(EM)之间IP连接，可以自动下载软件，自动下载无线参数和传输配置相关的数据。支持X2接口的自动建立，在完成建立后eNB可以自检工作状态并给网管中心报告检查结果。
图2是本发明实施例提供的一种系统架构图。参见图2，该系统包括：源MME、目标MME、源SGW、目标SGW以及PGW，还包括多个eNB，当然，该系统内还应包括UE等设备，在图中并未示出。
需要说明的是，该源eNB是指在UE发生位置变化之前所接入的eNB，而目标eNB则是在发生位置变化，由源eNB确定需要进行切换后，为UE所选择的eNB。
其中，接入同一个MME的eNB之间具有X2接口，MME与eNB之间具有S1接口，而通过支持SON的eNB的自配置过程，可以自动获取IP地址以 及配置接入不同MME的eNB之间的X2接口，使得接入不同MME的eNB之间可以通过自配置的X2接口进行直接交互，以实现X2切换，X2切换过程中，源eNB自动获取目标eNB的地址，而无需核心网，且eNB不受控制面管辖范围的约束。
图3是本发明实施例提供的一种切换方法的交互流程图。该图3的交互流程图是基于图2所示的系统架构进行的，用于描述一种不涉及SGW更换的交互场景，具体地，该实施例包括：
300、源eNB通过SON自动配置与目标eNB进行X2接口连接。
在此，不对切换过程中的决策过程进行赘述，具体UE如何上报测量报告以及源eNB如何基于UE的测量报告或其他信息，决定是否进行切换，或是进行什么样的切换，本发明实施例均不作限定。
在切换准备过程中，源eNB做出切换决策，决定切换将哪个eNB作为目标eNB以进行切换，若源eNB未保存有目标eNB的IP地址，则有可能是源eNB和目标eNB并未接入同一个MME，则需要执行步骤300，从而自动配置eNB之间的X2接口。
301、源eNB向目标eNB发送切换请求消息，该切换请求消息携带源MME的GUMMEI和MME UE S1AP ID。
进一步地，若目标eNB根据源MME的GUMMEI，确定该目标eNB与源MME无连接，则根据负载情况选择一个新的MME进行切换。
该根据负载情况选择MME是指：目标eNodeB需要选择MME池(Pool)为UE提供服务。MME Pool里面有很多MME，eNodeB基于网络拓扑和MME Pool的平均负载选择MME Pool，使UE后续移动时改变服务MME的概率降低。
302、目标eNB在接收到该切换请求消息时，向目标MME发送路径切换请求消息(Path switch request)。
其中，该路径切换请求消息包含目标小区的小区全局标识(跟踪区标识(Tracking Area Identity，以下简称：TAI)+E-UTRAN小区全局标识符(E-UTRAN Cell Global Identifier，以下简称：ECGI)和所转换的EPS承载列表、UE安全能力(Security Capabilities)、闭合用户群ID(Closed Subscriber Group Identity，以下简称：CSG ID)、小区接入模式(Cell Access Mode，以下简称CAM)， 与现有技术不同之处在于，该路径切换请求消息还包括源控制面标识MME全球唯一MME标识(Globally Unique MME Identifier，以下简称：GUMMEI)以及源MME的用户上下文标识UE S1AP ID(用户上下文标识)，该路径切换请求消息可以通过所携带的源MME GUMMEI(控制面标识)以及源MME的用户上下文标识UE S1AP ID(用户上下文标识)，从源MME获取UE的上下文。
其中，GUMMEI是全球唯一临时标识(Globally Unique Temporary Identity，以下简称：GUTI)的一部分，可以用于唯一标识分配GUTI的MME，MME UE S1AP ID用于MME在S1接口唯一标识UE。
303、当目标MME接收到目标eNB发送的路径切换请求时，根据源MME UE S1AP ID，在本地查询UE上下文。
当目标MME接收到目标eNB发送的路径切换请求时，可以获知这是一个切换事件，因此可以先从本地尝试对UE上下文的查询。
304、当目标MME在本地查询失败时，向源MME GUMMEI所指示的源MME发送UE上下文请求消息，UE上下文请求消息携带该源MME UE S1AP ID。
该步骤304可以包括所述目标MME根据所述源控制面标识寻址到源控制面的过程，向源MME发送UE上下文请求消息。
305、当源MME接收到该UE上下文请求消息，根据该源MME UE S1AP ID从本地查询UE上下文。
该UE上下文包括IMSI，UE核心网能力，TA列表，UE在源侧驻留的小区ID，SGW/PGW在S11接口的地址和TEID，PDN类型，EPS承载标识，用户的(Access Point Name，以下简称：APN)，默认EPS承载QoS，PDN类型等等。其中，S11接口是指MME和SGW之间的接口。
306、源MME向目标MME发送该UE上下文。
307、在源MME向目标MME发送该UE上下文后，源MME启动定时器，用来监督何时释放源eNB存储的UE资源和本地存储的UE资源。
308、该目标MME接收到该UE上下文后，根据UE上下文和目标小区ID决定是否更换SGW。
目标MME可以根据UE上下文中携带的SGW/PGW在S11接口的地址以及目标小区ID，判断SGW与目标小区之间的路径是否为优化路径，如果是优 化路径，则可以决定不更换SGW，如果不是优化路径，则可以决定更换SGW。
309、若目标MME决定不更换SGW，向SGW发送创建会话请求消息。
由于在步骤305中可以获取到SGW在S11接口的地址，因此，在步骤306中可以根据在步骤305中获取到的地址向SGW发送创建会话请求消息，该创建会话请求消息包含要建立的EPS承载，用户的APN，用户面的目标eNB的地址和TEID等等。
310、SGW/PGW向目标MME发送创建会话响应消息。
在图3的场景下，SGW和PGW均未发生更换。
311、当目标MME接收到该创建会话响应消息时，目标MME向目标eNB发送路径切换请求响应消息。
其中，该路径切换请求响应消息包含SGW在用户面为上行数据分配的地址和TEID。
312、当定时器超时后，源MME向源eNB发送资源释放消息，用来通知源eNB释放本地存储的UE资源。
进一步地，源MME在定时器超时时，也可以释放源MME本地存储的UE资源。
313、目标MME根据UE上下文完成切换过程。
该具体切换过程可以包括：目标MME根据UE上下文将UE同步到目标小区等过程，本发明实施例对此不做赘述。
图3所示实施例是在无需进行SGW更换的场景下进行的切换方法，而在切换过程中，为了路由路径的优化，或者是源SGW与目标MME之间无接口连接，则可以更换SGW，图4是本发明实施例提供的一种切换方法的交互流程图，用于描述一种涉及SGW更换的交互场景，具体地，该实施例包括：
400、源eNB通过SON自动配置与目标侧eNB进行X2接口连接。
该步骤400与步骤300同理，在此不做赘述。
401、源eNB向目标eNB发送切换请求消息，该切换请求消息携带源MME的GUMMEI和MME UE S1AP ID。
402、目标eNB向目标MME发送路径切换请求消息(Path switch request)。
403、当目标MME接收到目标eNB发送的路径切换请求消息时，根据源MME UE S1AP ID，在本地查询UE上下文。
404、当目标MME在本地查询失败时，向源MME GUMMEI所指示的源MME发送UE上下文请求消息，UE上下文请求消息携带该源MME UE S1AP ID。
405、当源MME接收到该UE上下文请求消息，根据该源MME UE S1AP ID在本地查询UE上下文。
406、源MME向目标MME发送该UE上下文。
407、目标MME在接收到UE上下文之后，决定更换SGW。
408、目标MME向源MME发送UE上下文响应消息，该UE上下文响应消息携带SGW改变指示(SGW change flag)。
409、当源MME接收到目标MME的UE上下文响应消息时，获知目标MME侧更换了SGW，启动定时器，用来监督何时释放源eNB存储的UE资源和源SGW存储的UE资源。
在上述步骤407和408中，目标MME为了路由路径的优化，或者源SGW与目标MME之间没有接口连接，则可以决定更换SGW，从而需要将该SGW的更换通知给源MME。
410、目标MME向目标SGW发送创建会话请求消息，该创建会话请求消息包含用于用户面的目标eNB的地址和TEID，承载上下文，PGW地址和TEID等。
411、目标SGW在接收到创建会话请求消息后，根据收到的PGW地址，向PGW发送修改承载请求消息，该修改承载请求消息包含目标SGW下行数据分配的SGW地址和TEID。
412、PGW在接收到修改承载请求消息时，向目标SGW发送修改承载响应消息，该修改承载响应消息包含PGW为上行数据分配的PGW地址和TEID。charging ID。
另外，该修改承载响应消息还可以包含计费ID，即charging ID，用于PGW对报文计费。
413、目标SGW在接收到该修改承载响应消息后，向目标MME发送创建会话响应消息，该创建会话响应消息包含在用户面目标SGW为上行数据分配的地址和TEID。
414、目标MME向目标eNB发送路径切换请求响应消息，该路径切换请求响应消息包含在用户面目标SGW为上行数据分配的地址和TEID。
415、当源MME的定时器超时，源MME向源eNB发送资源释放消息。
416、当源eNB接收到该资源释放消息时，释放UE资源。
该UE资源可以包括：UE的无线承载和控制面与UE上下文有关的所有资源。
417、源MME向源SGW发送删除会话请求消息，该删除会话请求消息用来释放源SGW存储的UE资源。
上述图3和图4的实施例，分别对传统EPC网络架构下的UE切换过程进行了具体描述，目标MME可以通过从目标eNB获取源MME分配的源控制面ID和UE上下文ID，直接向源MME请求UE上下文，从而将UE切换到目标小区，实现了跨控制面的X2接口的切换，从而统一了核心网获取上下文的流程，简化了核心网实现，在跨控制面切换过程中，减少了切换延时，提高了切换效率。
进一步地，目标eNB根据源eNB提供的源控制面标识等信息，确定是否是跨MME切换。如果是跨MME切换，则根据负载情况，选择新的MME作为目标MME，并将源控制面标识和UE上下文ID发送给目标MME。新的MME根据源控制面标识确定源MME，并从源MME获取UE上下文，实现了一种跨控制面的X2接口切换方法。
图5是本发明实施例提供的一种CU分离移动网络系统的架构图。CU分离网络架构将移动网关的控制面功能与转发面功能解耦，并将分离出的控制面功能(GW-C)与3GPP传统的控制网元MME，PCRF等合并成统一的控制面。转发面GW-U包含S-GW的转发面(SGW-U)和P-GW的转发面(PGW-U)。参见图5，该系统包括：源控制面设备、目标控制面设备、源GW-U、目标GW-U以及SDN控制设备等，还包括多个eNB，当然，该系统内还应包括UE等设备，在图中并未示出。与图2所示的架构不同之处在于，该图5所示的系统还包括数据库如图中虚线框所示)，当UE入网后，控制面Controller将UE上下文同步到数据库，这样数据库可以将上下文进行集中式管理。
该系统中的相邻eNB之间通过SON便可以实现自动建立X2接口。在切换准备过程中，源eNB做出切换决策，决定切换到哪个目标eNB，若源eNB未保存有目标eNB的IP地址，源eNB通过SON自动配置与目标侧eNB建立X2接口自动连接。
之后，源eNB向目标eNB发送切换请求消息，携带了源Controller的ID，若目标eNB跟源Controller无连接，则根据负载情况选择一个新的Controller进行切换。在path switch request消息中，目标eNB必须携带控制面标识ID和用户上下文标识ID，以便目标Controller向源Controller获取UE上下文。之后，目标Controller根据UE上下文将UE同步到目标小区，完成切换过程。
图6是转发分离移动网络架构的切换过程，由于CU分离之后，GW-U只与一个Controller相连接，所以跨Controller的切换必然涉及更换GW-U，因此，提供一个涉及更换GW-U场景的切换方法实施例，具体流程如图6所示：
600、源eNB通过SON自动配置与目标eNB进行X2接口连接。
该步骤600与步骤300同理，在此不做赘述。
601、源eNB向目标eNB发送切换请求消息，该切换请求消息携带源Controller ID和源Controller的用户上下文标识UE S1AP ID。
602、目标eNB向目标Controller发送路径切换请求消息(Path switch request)。
其中，该路径切换请求消息包含目标小区的小区全局标识(TAI+ECGI)和所转换的EPS承载列表、UE Security Capabilities、CSG ID、Cell Access Mode，与现有技术不同之处在于，该路径切换请求消息还包括源Controller ID(控制面标识)以及源Controller的用户上下文标识UE S1AP ID(用户上下文标识)，该路径切换请求消息可以通过所携带的源Controller ID(控制面标识)以及源Controller的用户上下文标识UE S1AP ID(用户上下文标识)，从源Controller获取UE的上下文。
其中，源Controller ID唯一标识控制面，Controller UE S1AP ID用于Controller在S1接口唯一标识UE。
603、当目标Controller接收到目标eNB发送的路径切换请求消息时，根据源Controller UE S1AP ID，在本地查询UE上下文。
604、当目标Controller在本地查询失败时，向源Controller ID所指示的源Controller发送UE上下文请求消息，UE上下文请求消息携带该源Controller UE S1AP ID。
605、当源Controller接收到该UE上下文请求消息，根据该源Controller UE S1AP ID在本地查询UE上下文。
606、源Controller向目标Controller发送该UE上下文。
607、目标Controller在接收到UE上下文之后，向源Controller发送UE上下文响应消息，该UE上下文响应消息携带GW-U改变指示。
目标Controller在获取到UE上下文后，可以根据UE切换前的小区位置和目标小区位置决定是否更换转发面网关，如果确定更换，则可以由目标Controller触发源侧设备的资源释放过程，执行步骤607中的UE上下文响应消息发送过程，以将GW-U更换的情况告知源Controller，使得源Controller监督进行源侧资源的释放。
608、当源Controller接收到目标Controller的UE上下文响应消息时，获知目标Controller侧更换了GW-U，启动定时器，用来监督何时释放源eNB存储的UE资源和源GW-U存储的UE资源。
609、目标Controller在接收到UE上下文之后，目标Controller向目标GW-U发送下行数据转发规则，用于指示网关转发面如何处理UE发送的IP报文。
610、目标Controller向目标eNB发送路径切换请求响应消息。
611、当源Controller的定时器超时，源Controller向源eNB发送资源释放消息。
进一步地，源Controller在定时器超时时，也可以释放源Controller本地存储的UE资源。
612、当源eNB接收到该资源释放消息时，释放UE资源。
613、源Controller向源GW-U发送资源释放消息。
614、当源GW-U接收到资源释放消息后，释放UE资源。
需要说明的是，上述步骤611和步骤613可以同时执行，或是一前一后执行，本发明实施例对其实际执行顺序不作限定，只要在源Controller的定时器超时能够使得源侧设备分别对UE资源进行释放即可。
图6所示实施例中的UE上下文是由源Controller发送给目标Controller的，而在另一实施例中，UE上下文也可以从数据库中获取，如图7所示，当UE入网后，任一个Controller，如本实施例中的源Controller对于本地缓存的UE上下文会向数据库同步更新，数据库将控制面存储的上下文集中式管理，可以实现资源动态迁移以及容灾备份等功能。
700、源eNB通过SON自动配置与目标eNB进行X2接口连接。
该步骤700与步骤300同理，在此不做赘述。
701、源eNB向目标eNB发送切换请求消息，该切换请求消息携带源Controller ID和源Controller的用户上下文标识UE S1AP ID。
702、目标eNB向目标Controller发送路径切换请求消息(Path switch request)。
进一步地，若目标eNB跟源Controller无连接，则根据负载情况选择一个新的Controller进行切换，该所选择的Controller也即是目标Controller。
其中，该路径切换请求消息包含目标小区的小区全局标识(TAI+ECGI)和所转换的EPS承载列表、UE Security Capabilities、CSG ID、Cell Access Mode，与现有技术不同之处在于，该路径切换请求消息还包括源Controller ID(控制面标识)以及源Controller的用户上下文标识UE S1AP ID(用户上下文标识)，该路径切换请求消息可以通过所携带的源Controller ID(控制面标识)以及源Controller的用户上下文标识UE S1AP ID(用户上下文标识)，从源Controller获取UE的上下文。
其中，源Controller ID唯一标识控制面，Controller UE S1AP ID用于Controller在S1接口唯一标识UE。
703、当目标Controller接收到目标eNB发送的路径切换请求消息时，根据源Controller UE S1AP ID，在本地查询UE上下文。
在UE移动到目标小区之前，数据库根据UE移动轨迹或者所在位置，预测UE可能移动的区域范围，将UE上下文主动推动到目标Controller，而如果在步骤703中查询不成功，则说明先前的数据库智能推送失败，则需要使用之前获取到的源Controller ID和源Controller UE S1AP ID，从数据库获取UE上下文信息。
704、当目标Controller在本地查询失败时，向数据库发送UE上下文请求消息，UE上下文请求消息携带该源Controller ID和源Controller UE S1AP ID。
705、当数据库接收到该UE上下文请求时，在数据库中查询该UE上下文。
该UE上下文包括IMSI，UE核心网能力，TA列表，UE在源侧驻留的小区ID，EPS承载标识，用户的APN，默认EPS承载QoS等等。
706、数据库向目标Controller发送该UE上下文。
上述步骤704至706是所述目标控制面设备将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文的过程。
707、目标Controller在接收到UE上下文之后，目标Controller向目标GW-U发送下行数据转发规则，用于指示网关转发面如何处理UE发送的IP报文。
目标Controller在获取到UE上下文后，可以根据UE切换前的小区位置和目标小区位置决定是否更换转发面网关，如果确定更换，则可以由目标Controller通过目标eNB触发源侧设备的资源释放过程。
708、目标Controller向目标eNB发送路径切换请求响应消息，该路径切换请求响应消息携带GW-U改变指示。
本发明实施例对步骤707和708之间的执行先后顺序不作限定。
709、目标eNB在接收到该路径切换请求响应消息后，向源eNB发送资源释放消息，该资源释放消息携带GW-U改变指示。
710、源eNB在接收到资源释放消息后，向源Controller发送资源释放消息，该资源释放消息携带GW-U改变指示。
711、源Controller向源GW-U发送资源释放消息。
712、当源GW-U接收到资源释放消息后，释放UE资源。
由于更换了GW-U，源Controller向源GW-U发送资源释放消息。
上述图6和图7的实施例，分别对CU网络架构下的UE切换过程进行了具体描述，目标Controller可以通过从目标eNB获取源Controller分配的源控制面ID和UE上下文ID，直接向源Controller请求UE上下文，或者通过数据库将UE上下文同步到目标Controller，实现了跨控制面的X2接口的切换，从而减少控制面延时，提高了切换效率。
进一步地，与现有的X2接口切换相比，现有的X2切换过程中，目标eNB在从X2接口获取源侧信息后如果发现是源控制面标识和目标eNB没有连接关系，目标eNB则拒绝X2切换，进而不会触发新控制面选择过程，换句话说，现有的X2接口切换过程不能进行跨控制面的切换。而本发明实施例中，目标eNB根据源eNB提供的源控制面标识等信息，确定是否是跨Controller切换。如果是跨Controller切换，则根据负载情况，选择新的Controller作为目标Controller，并将源控制面标识和UE上下文ID发送给目标Controller。目标Controller根据源控制面标识可以从源Controller获取UE上下文，或者通过数据库将UE上下文同步到目标Controller，实现了一种跨控制面的X2接口切换方法。
下述为本发明装置实施例，可以用于执行本发明方法实施例。对于本发明装置实施例中未披露的细节，请参照本发明方法实施例。
图8是本发明实施例提供的一种基站的结构示意图。参见图8，该基站包括：
获取模块801，用于从源基站获取源控制面标识和所述UE的上下文标识；
发送模块802，用于将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。
在一种可能实现方式中，所述获取模块801用于自动建立所述目标基站和所述源基站之间的连接关系，所述目标基站通过所述源基站获取源控制面标识和所述UE的上下文标识。
在一种可能实现方式中，所述基站还包括：选择模块，用于根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；若所述目标基站与所述源控制面无连接关系，则选择一个控制面作为目标控制面。
在一种可能实现方式中，所述基站还包括：释放模块，用于触发释放源侧设备资源。
在一种可能实现方式中，所述释放模块用于当接收到目标控制面发送的源转发面改变指示时，向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
需要说明的一点是，上述实施例提供的基站在实现切换用户设备的功能时，仅以上述各个功能模块的划分进行举例说明，实际应用中，可以根据实际需要而将上述功能分配由不同的功能模块完成，即将设备的内容结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图9是本发明实施例提供的一种控制面设备的结构示意图。参见图9，改控制面设备包括：
接收模块901，用于接收目标基站发送的源控制面标识和UE的上下文标识；
获取模块902，用于根据源控制面标识和所述UE的上下文标识获取所述 UE的上下文。
在一种可能实现方式中，所述获取模块902用于根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；接收所述源控制面返回的所述UE的上下文。
在一种可能实现方式中，所述获取模块902用于将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文。
在一种可能实现方式中，所述控制面设备还包括：
判断模块，用于判断是否需要更换转发面网关；
发送模块，用于若所述判断模块确定需要更换转发面网关，向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
在一种可能实现方式中，所述控制面设备包括：移动性管理实体；或者，集中控制面设备。
需要说明的一点是，上述实施例提供的控制面设备在实现其切换用户设备的功能时，仅以上述各个功能模块的划分进行举例说明，实际应用中，可以根据实际需要而将上述功能分配由不同的功能模块完成，即将设备的内容结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
请参考图10，其为本发明实施例所提供的一种基站的结构示意图。如图所示，该基站包括发射机、接收机、存储器以及分别与发射机、接收机和存储器连接的处理器。当然，基站还可以包括天线、基带处理部件、中射频处理部件、输入输出装置等通用部件，本发明实施例在此不再任何限制。
所述基站被配置为执行上述图3、图4、图6或图7中任一实施例所提供的基站侧的用户设备切换方法。
以上发射机和接收机还可以为收发机。该处理器可以为中央处理单元(CPU)、微处理器、单片机等。
请参考图11，其为本发明实施例所提供的一种控制面设备的结构示意图。如图所示，该控制面设备包括发射机、接收机、存储器以及分别与发射机、接 收机和存储器连接的处理器。当然，控制面设备还可以包括天线、基带处理部件、中射频处理部件、输入输出装置等通用部件，本发明实施例在此不再任何限制。
所述控制面设备被配置为执行上述图3、图4、图6或图7中任一实施例所提供的控制面设备侧的用户设备切换方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本申请旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本发明未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (30)

  1. 一种切换用户设备UE的方法，其特征在于，包括：
    目标基站从源基站获取源控制面标识和所述UE的上下文标识；
    所述目标基站将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。
  2. 根据权利要求1所述的方法，其特征在于，所述目标基站从源基站获取源控制面标识和所述UE的上下文标识包括：
    所述目标基站自动建立所述目标基站和所述源基站之间的连接关系，所述目标基站通过所述源基站获取源控制面标识和所述UE的上下文标识。
  3. 根据权利要求1或2任一项所述的方法，其特征在于，所述方法还包括：
    所述目标基站根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；
    若所述目标基站与所述源控制面无连接关系，则所述目标基站选择一个控制面作为目标控制面。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    所述目标基站触发释放源侧设备资源。
  5. 根据权利要求4所述的方法，其特征在于，所述目标基站触发释放源侧设备资源包括：
    当所述目标基站接收到目标控制面发送的源转发面改变指示时，所述目标基站向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述控制面设备包括移动性管理实体；或者，集中控制面设备。
  7. 一种切换用户设备UE的方法，其特征在于，包括：
    目标控制面设备接收目标基站发送的源控制面标识和UE的上下文标识；
    所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文。
  8. 根据权利要求7所述的方法，其特征在于，所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文包括：
    所述目标控制面设备根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；
    所述目标控制面设备接收所述源控制面返回的所述UE的上下文。
  9. 根据权利要求7或8所述的方法，其特征在于，所述目标控制面设备根据源控制面标识和所述UE的上下文标识获取所述UE的上下文包括：
    所述目标控制面设备将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文。
  10. 根据权利要求7至9任一项所述的方法，其特征在于，所述方法还包括：
    所述目标控制面设备判断是否需要更换转发面网关；
    若需要更换转发面网关，所述目标控制面设备向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
  11. 根据权利要求7至10任一项所述的方法，其特征在于，所述控制面设备包括：移动性管理实体；或者，集中控制面设备。
  12. 一种无线通信系统，其特征在于，所述无线通信系统至少包括用户设备UE、源基站、目标基站、源控制面设备和目标控制面设备，其中，
    所述目标基站，用于从所述源基站获取源控制面标识和所述UE的上下文标识，将所述源控制面标识和所述UE的上下文标识发送至所述目标控制面设备；
    所述目标控制面设备，用于接收所述源控制面标识和所述UE的上下文标识，根据所述源控制面标识和所述UE的上下文标识获取所述UE的上下文。
  13. 根据权利要求12所述的系统，其特征在于，所述目标基站用于自动建立所述目标基站和所述源基站之间的连接关系，并通过所述源基站获取源控制面标识和所述UE的上下文标识。
  14. 根据权利要求12或13任一项所述的系统，其特征在于，所述目标基站还用于根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；若所述目标基站与所述源控制面无连接关系，则选择一个控制面作为目标控制面。
  15. 根据权利要求12至14任一项所述的系统，其特征在于，所述目标基站还用于触发释放源侧设备资源。
  16. 根据权利要求15所述的系统，其特征在于，所述目标基站用于当接收到目标控制面发送的源转发面改变指示时，向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
  17. 根据权利要求12至16任一项所述的系统，其特征在于，所述目标控制面设备还用于判断是否需要更换转发面网关，若需要更换转发面网关，向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
  18. 根据权利要求12至17任一项所述的系统，其特征在于，所述目标控制面设备用于根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；还用于接收所述源控制面返回的所述UE的上下文。
  19. 根据权利要求12至17任一项所述的系统，其特征在于，所述目标控制面设备用于将所述源控制面标识和所述UE的上下文标识作为索引信息，从数 据库获取所述UE的上下文。
  20. 根据权利要求12至19任一项所述的系统，其特征在于，所述控制面设备包括移动性管理实体；或者，集中控制面设备。
  21. 一种基站，其特征在于，包括：
    获取模块，用于从源基站获取源控制面标识和所述UE的上下文标识；
    发送模块，用于将所述源控制面标识和所述UE的上下文标识发送至目标控制面设备，所述源控制面标识和所述UE的上下文标识用于所述UE的上下文的获取。
  22. 根据权利要求21所述的基站，其特征在于，所述获取模块用于自动建立所述目标基站和所述源基站之间的连接关系，所述目标基站通过所述源基站获取源控制面标识和所述UE的上下文标识。
  23. 根据权利要求21或22任一项所述的基站，其特征在于，所述基站还包括：选择模块，用于根据所述源控制面标识判断所述目标基站是否与源控制面有连接关系；若所述目标基站与所述源控制面无连接关系，则选择一个控制面作为目标控制面。
  24. 根据权利要求21至23任一项所述的基站，其特征在于，所述基站还包括：释放模块，用于触发释放源侧设备资源。
  25. 根据权利要求24所述的基站，其特征在于，所述释放模块用于当接收到目标控制面发送的源转发面改变指示时，向源基站发送资源释放消息，所述资源释放消息携带源转发面网关改变指示。
  26. 一种控制面设备，其特征在于，包括：
    接收模块，用于接收目标基站发送的源控制面标识和UE的上下文标识；
    获取模块，用于根据源控制面标识和所述UE的上下文标识获取所述UE的上下文。
  27. 根据权利要求26所述的控制面设备，其特征在于，所述获取模块用于根据所述源控制面标识寻址到源控制面，并向所述源控制面发送UE上下文请求消息，所述UE上下文请求消息携带所述UE的上下文标识；接收所述源控制面返回的所述UE的上下文。
  28. 根据权利要求26或27所述的控制面设备，其特征在于，所述获取模块用于将所述源控制面标识和所述UE的上下文标识作为索引信息，从数据库获取所述UE的上下文。
  29. 根据权利要求26至28任一项所述的控制面设备，其特征在于，所述控制面设备还包括：
    判断模块，用于判断是否需要更换转发面网关；
    发送模块，用于若所述判断模块确定需要更换转发面网关，向所述目标基站发送源转发面改变指示，所述源转发面改变指示用于触发释放源侧设备资源。
  30. 根据权利要求26至29任一项所述的控制面设备，其特征在于，所述控制面设备包括：移动性管理实体；或者，集中控制面设备。
PCT/CN2016/081030 2016-05-04 2016-05-04 切换用户设备方法及设备 WO2017190296A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16900818.2A EP3445086B1 (en) 2016-05-04 2016-05-04 Method and device for switching user equipment
PCT/CN2016/081030 WO2017190296A1 (zh) 2016-05-04 2016-05-04 切换用户设备方法及设备
CN201680085311.XA CN109076404B (zh) 2016-05-04 2016-05-04 切换用户设备方法及设备
US16/179,717 US20190075497A1 (en) 2016-05-04 2018-11-02 User equipment handover method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/081030 WO2017190296A1 (zh) 2016-05-04 2016-05-04 切换用户设备方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/179,717 Continuation US20190075497A1 (en) 2016-05-04 2018-11-02 User equipment handover method and device

Publications (1)

Publication Number Publication Date
WO2017190296A1 true WO2017190296A1 (zh) 2017-11-09

Family

ID=60202637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081030 WO2017190296A1 (zh) 2016-05-04 2016-05-04 切换用户设备方法及设备

Country Status (4)

Country Link
US (1) US20190075497A1 (zh)
EP (1) EP3445086B1 (zh)
CN (1) CN109076404B (zh)
WO (1) WO2017190296A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019015627A1 (zh) * 2017-07-20 2019-01-24 华为技术有限公司 切换方法、设备及系统
US10757941B2 (en) 2016-07-22 2020-09-01 Syngenta Participations Ag Microbiocidal oxadiazole derivatives
US11160004B2 (en) 2017-07-20 2021-10-26 Huawei Technologies Co., Ltd. Handover method, device, and system

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018072833A1 (en) * 2016-10-20 2018-04-26 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for attaching a radio base station to a core network node
US10917927B2 (en) 2017-05-12 2021-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Local identifier locator network protocol (ILNP) breakout
US10931586B2 (en) * 2018-10-30 2021-02-23 Verizon Patent And Licensing Inc. Method and system for predictive edge resources
EP3878214B1 (en) 2018-11-07 2024-04-03 Telefonaktiebolaget LM Ericsson (publ) Local identifier locator network protocol (ilnp) breakout
CN111669841B (zh) * 2019-03-06 2023-08-22 华为技术有限公司 确定小区站点网关csg的方法和装置
US11659453B2 (en) 2020-03-02 2023-05-23 Nokia Solutions And Networks Oy Efficient transfer of access context for user equipment among network nodes
EP3876602B1 (en) * 2020-03-02 2024-02-28 Nokia Solutions and Networks Oy Efficient transfer of access context for user equipment among network nodes
CN113810960A (zh) * 2020-06-16 2021-12-17 北京佰才邦技术股份有限公司 一种切换方法、核心网、装置及介质
CN114531418A (zh) * 2020-10-30 2022-05-24 北京三星通信技术研究有限公司 通信方法及装置
CN114585025A (zh) * 2020-11-30 2022-06-03 中国移动通信有限公司研究院 移动性管理方法、装置、设备及可读存储介质
EP4311305A1 (en) * 2022-07-20 2024-01-24 Ntt Docomo, Inc. Communication network component and method for re-establishment of a communication connection

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101594652A (zh) * 2008-05-28 2009-12-02 大唐移动通信设备有限公司 一种切换过程中发起更新承载配置的方法、系统及装置
CN101785334A (zh) * 2007-08-15 2010-07-21 日本电气株式会社 提供用于所请求连接的源连接标识符的方法、装置和计算机程序
CN102238669A (zh) * 2010-04-29 2011-11-09 北京三星通信技术研究有限公司 一种通过家用基站HeNB进行X2切换的方法
CN103096405A (zh) * 2011-11-04 2013-05-08 北京三星通信技术研究有限公司 支持组切换的方法及设备
US20130250917A1 (en) * 2010-12-03 2013-09-26 Lg Electronics Inc. Method and Apparatus for Performing Access Control in Wireless Communication System
CN105517066A (zh) * 2015-11-24 2016-04-20 武汉虹信技术服务有限责任公司 一种lte s1-mme接口的海量数据用户识别的方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070254667A1 (en) * 2006-04-28 2007-11-01 Joanna Jokinen Inter-MME handover in evolved communication systems
CN101521869A (zh) * 2008-02-25 2009-09-02 三星电子株式会社 更新用户设备位置信息的方法
CN101610504B (zh) * 2008-06-18 2012-08-08 上海华为技术有限公司 接入、获取用户设备上下文及用户设备标识的方法和装置
CN102300190B (zh) * 2010-06-28 2013-01-23 华为技术有限公司 切换方法、通信装置和通信系统
CN102595532A (zh) * 2011-01-07 2012-07-18 中兴通讯股份有限公司 无线中继系统中切换类型选择方法及系统
US9088922B2 (en) * 2011-10-10 2015-07-21 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for mobile relay handover
CN104105143B (zh) * 2013-04-03 2020-04-24 北京三星通信技术研究有限公司 一种支持sipto业务的方法
CN105992292A (zh) * 2015-02-13 2016-10-05 中兴通讯股份有限公司 异构网中的基站切换方法与基站

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101785334A (zh) * 2007-08-15 2010-07-21 日本电气株式会社 提供用于所请求连接的源连接标识符的方法、装置和计算机程序
CN101594652A (zh) * 2008-05-28 2009-12-02 大唐移动通信设备有限公司 一种切换过程中发起更新承载配置的方法、系统及装置
CN102238669A (zh) * 2010-04-29 2011-11-09 北京三星通信技术研究有限公司 一种通过家用基站HeNB进行X2切换的方法
US20130250917A1 (en) * 2010-12-03 2013-09-26 Lg Electronics Inc. Method and Apparatus for Performing Access Control in Wireless Communication System
CN103096405A (zh) * 2011-11-04 2013-05-08 北京三星通信技术研究有限公司 支持组切换的方法及设备
CN105517066A (zh) * 2015-11-24 2016-04-20 武汉虹信技术服务有限责任公司 一种lte s1-mme接口的海量数据用户识别的方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10757941B2 (en) 2016-07-22 2020-09-01 Syngenta Participations Ag Microbiocidal oxadiazole derivatives
WO2019015627A1 (zh) * 2017-07-20 2019-01-24 华为技术有限公司 切换方法、设备及系统
US11160004B2 (en) 2017-07-20 2021-10-26 Huawei Technologies Co., Ltd. Handover method, device, and system
US11716667B2 (en) 2017-07-20 2023-08-01 Huawei Technologies Co., Ltd. Handover method, device, and system

Also Published As

Publication number Publication date
EP3445086A1 (en) 2019-02-20
EP3445086B1 (en) 2019-09-04
US20190075497A1 (en) 2019-03-07
CN109076404B (zh) 2020-07-24
EP3445086A4 (en) 2019-02-20
CN109076404A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
WO2017190296A1 (zh) 切换用户设备方法及设备
US12096285B2 (en) Federated X2 gateway
US10791486B1 (en) Method and system for supporting fast recovery of user equipment
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
EP3602978B1 (en) Coordinated selection of user plane functions in core and radio access networks
WO2021088850A1 (zh) 消息发送方法和装置、消息接收方法和装置、设备和存储介质
US11641602B2 (en) Systems and methods for handover of dual connectivity user equipment
US11184875B2 (en) Paging method and apparatus for wireless communication
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
US11259223B2 (en) Systems and methods for handover for user equipment that supports 5G standalone operation

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016900818

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016900818

Country of ref document: EP

Effective date: 20181115

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16900818

Country of ref document: EP

Kind code of ref document: A1