WO2016026088A1 - 路径切换方法、移动锚点及基站 - Google Patents

路径切换方法、移动锚点及基站 Download PDF

Info

Publication number
WO2016026088A1
WO2016026088A1 PCT/CN2014/084730 CN2014084730W WO2016026088A1 WO 2016026088 A1 WO2016026088 A1 WO 2016026088A1 CN 2014084730 W CN2014084730 W CN 2014084730W WO 2016026088 A1 WO2016026088 A1 WO 2016026088A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
path switching
parameter
key
identifier
Prior art date
Application number
PCT/CN2014/084730
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 CN201480029180.4A priority Critical patent/CN105532035B/zh
Priority to EP14900188.5A priority patent/EP3171635B1/en
Priority to PCT/CN2014/084730 priority patent/WO2016026088A1/zh
Publication of WO2016026088A1 publication Critical patent/WO2016026088A1/zh
Priority to US15/436,527 priority patent/US20170164244A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0064Transmission or use of information for re-establishing the radio link of control information between different access points
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/14Mobility data transfer between corresponding nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24Cell structures
    • H04W16/32Hierarchical cell structures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0038Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of security context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/12Reselecting a serving backbone network switching or routing node

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a path switching method, a mobile anchor point, and a base station. Background technique
  • the small stations are called the new favorite of operators because of their low cost, convenient site selection and simple deployment.
  • the intensive deployment of the small station enables the user equipment (User Equipment, UE for short) to increase the frequency of path switching during the movement between the small stations.
  • the path switching procedure of the UE includes path switching between the UE and the small station, the path switching between the small station and the core network device. That is to say, each time the UE performs path switching, the target base station needs to send a handover request message to the core network device.
  • the signaling load on the core network is bound to be excessive.
  • the prior art adopts the Dual Connectivity technology, so that the UE receives data from the macro station and the small station at the same time, provides wide coverage by the macro station, reduces the number of handovers, and shares the data capacity of the hotspot area through the small station.
  • the dual connectivity technology the user plane data of the UE is terminated by the macro station, and the user plane data of the UE is transparent to the core network during the mobile station movement. That is to say, if the UE moves between the small stations, the UE only needs to switch the path between the UE and the small station without performing the path switching on the core network side, thereby reducing the signaling load of the core network.
  • the dual connectivity technique must be based on the fact that the UE has at least dual receivers and dual transmitters and must have coverage of the macro stations.
  • the current network there are still a large number of single-receiver or single-transmitter UEs, or in some scenes, there is no coverage of the macro station, so that path switching based on the dual-connection technology cannot be supported and executed.
  • the implementation scenario of the path switching solution based on the dual connectivity technology is limited in the prior art, and the problem of large core network signaling load in all scenarios cannot be solved.
  • Summary of the invention The embodiments of the present invention provide a path switching method, a mobile anchor point, and a base station, so as to solve the problem that the execution scenario of the prior art solution is limited, and the signaling load of the core network in all scenarios cannot be solved.
  • an embodiment of the present invention provides a path switching method, including:
  • the mobility anchor receives the path switch request message sent by the target base station
  • the mobility anchor keeps the user plane path between the mobility anchor and the serving gateway SGW unchanged;
  • the mobility anchor will switch the user plane path between the source base station to the target base station.
  • the method further includes:
  • the mobility anchor sends the path switching request message to the mobility management entity MME to trigger modification of a user plane path between the mobility anchor and the SGW.
  • the method further includes:
  • the mobility anchor determines to perform global path switching or local path switching.
  • the moving anchor point determines whether to perform global path switching or local path switching, including:
  • the mobile anchor point determines whether to perform global path switching or local path switching by comparing the number of switching times with the preset threshold value
  • the mobility anchor determines to perform a global path switch
  • the mobility anchor determines to perform local path switching.
  • the path switching request message includes: an access identifier of the UE, an access identifier of the UE, and the source An identifier assigned by the anchor device connected by the base station to the UE;
  • the mobility anchor determines whether to perform global path switching or local path switching, including:
  • the mobility anchor determines to perform global path switching or local path switching by performing an access identifier of the UE;
  • the mobile anchor point determines to perform global path switching
  • the mobility anchor retrieves the UE according to the access identifier of the UE, the mobile anchor determines to perform local path switching.
  • the method further includes:
  • the moving anchor point generates a first next hop NH parameter
  • the mobility anchor sends the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines a key used by the next base station according to the first NH parameter;
  • the next base station is a base station other than the source base station and the target base station.
  • the moving anchor point generates the first NH parameter, including:
  • the mobility anchor generates the first NH parameter according to the access management security entity key and the first peer input parameter;
  • the first peer input parameter includes: a first source base station key, and a second NH parameter.
  • the method further includes:
  • the mobility anchor receives the access management security entity key, the first source base station key, and the second NH parameter sent by the MME;
  • the mobility anchor sends the second NH parameter to the source base station, so that the source base station determines a key used by the target base station according to the second NH parameter.
  • the first source base station key is the MME according to the access management security entity key, and Determined by the non-access stratum counter;
  • the second NH parameter is determined by the MME according to the access management security real key and the second peer input parameter.
  • the moving anchor point generates the first NH parameter, including:
  • the mobility anchor generates the first NH parameter according to the second source base station key and a random number.
  • the method further includes: The mobility anchor receives the second source base station key sent by the MME; wherein the second source base station key is determined by the MME according to an access management security entity key and a non-access stratum counter ; or
  • the second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the embodiment of the present invention provides a path switching method, including:
  • the target base station determines to perform global path switching or local path switching
  • the target base station If the target base station performs local path switching, the target base station sends a first path switching request message to the mobility anchor point, so that the mobility anchor point keeps the user plane path between the mobility anchor point and the SGW unchanged, and The mobile anchor point is switched to the target base station with a user plane path between the source base station.
  • the determining, by the target base station, the global path switching or the local path switching includes:
  • the target base station determines to perform global path switching or local path switching by comparing the number of switching times with the preset threshold value
  • the target base station determines to perform global path switching
  • the target base station determines to perform local path handover.
  • the method before the target base station determines to perform global path switching or local path switching, the method further includes:
  • the target base station receives the handover request message sent by the source base station;
  • the handover request message includes: an anchor identifier that is connected by the source base station;
  • the target base station determines to perform global path switching or local path switching, including:
  • the target base station determines to perform global path switching or local path switching by comparing an anchor point identifier connected to the source base station with an identifier of the mobility anchor point;
  • the target base station determines to perform local path switching
  • the target base station determines to perform global path switching; or
  • the handover request message includes: an identifier of a base station cluster where the source base station is located;
  • the determining, by the target base station, the global path switching or the local path switching the determining, by the target base station, determining the global path by comparing the identifier of the base station cluster where the source base station is located with the identifier of the base station cluster where the target base station is located Switch or local path switch;
  • the target base station determines to perform local path switching
  • the target base station determines to perform global path switching.
  • the method further includes:
  • the target base station receives a first NH parameter that is sent by the mobility anchor point by using a first path switch request acknowledgement message; the first NH parameter is generated by the mobility anchor point;
  • the first NH parameter is the mobility anchor point according to the access management security entity key and the first peer input parameter
  • the obtained parameter includes: a first source base station key, a second NH parameter; the access management security entity key, the first source base station key, and the second
  • the NH parameter is sent by the MME received by the mobility anchor.
  • the first source base station key is the MME, according to the access management security entity key, and non-access Determined by the layer counter;
  • the second NH parameter is determined by the MME according to the access management security entity key and the second peer input parameter.
  • the first NH parameter is a parameter that is determined by the mobility anchor according to a second source base station key and a random number.
  • the second source base station key is configured by the MME according to an access management security entity key and a non-access stratum counter Determined; or The second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the method further includes:
  • the target base station If the target base station performs global path switching, the target base station sends a second path switch request message to the MME to trigger modification of the user plane path between the mobility anchor point and the SGW.
  • an embodiment of the present invention further provides a mobility anchor, including:
  • a receiving module configured to receive a path switch request message sent by the target base station
  • a maintaining module configured to keep a user plane path between the mobility anchor point and the SGW unchanged if local path switching is performed
  • a switching module configured to switch a user plane path between the mobility anchor point and the source base station to the target base station.
  • the moving anchor point further includes:
  • a sending module configured to send the path switch request message to the MME to trigger modification of a user plane path between the mobility anchor point and the SGW.
  • the moving anchor point further includes:
  • the determining module is configured to determine whether to perform global path switching or local path switching.
  • the determining module is further configured to determine whether to perform global path switching or a local path by comparing a number of switching times with a preset threshold value. Switching, if the number of times of switching is greater than or equal to the preset threshold, performing global path switching, and if the number of switching times is less than the preset threshold, performing local path switching.
  • the path switching request message includes: an access identifier of the UE, an access identifier of the UE, and the source An identifier assigned by the anchor device connected by the base station to the UE;
  • the determining module is further configured to: determine, by performing a global path switching or a local path switching, by performing an access identifier of the UE, and if the UE cannot be retrieved according to the access identifier of the UE, perform a global path. Switching, if the UE is retrieved according to the access identifier of the UE, Perform local path switching.
  • the moving anchor point further includes:
  • Generating a module configured to generate a first NH parameter
  • the sending module is further configured to send the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines a key used by the next base station according to the first NH parameter;
  • the next base station is a base station other than the source base station and the target base station.
  • the generating module is further configured to generate, according to the access management security entity key and the first peer input parameter An NH parameter; wherein the first peer input parameter comprises: a first source base station key and a second NH parameter.
  • the receiving module is further configured to receive, by the MME, the access management security entity key, the a source base station key, the second NH parameter;
  • the sending module is further configured to send the second NH parameter to the source base station, so that the source base station determines a key used by the target base station according to the second NH parameter.
  • the first source base station key is the MME according to the access management security entity key, and Determined by the non-access stratum counter;
  • the second NH parameter is determined by the MME according to the access management security real key and the second peer input parameter.
  • the generating module is further configured to generate the first NH parameter according to the second source base station key and the random number.
  • the receiving module is further configured to receive the second source base station key that is sent by the MME, where Determining, by the MME, the MME according to the access management security entity key and the non-access stratum counter; or
  • the second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the embodiment of the present invention further provides a base station, where the base station is a target base station, and the base station includes:
  • a determining module configured to determine to perform global path switching or local path switching
  • a sending module configured to send a first path switching request message to the mobility anchor point, so that the mobility anchor point keeps the user plane path between the mobility anchor point and the SGW unchanged, and causes the The mobility anchor will switch the user plane path between the source base station to the target base station.
  • the determining module is further configured to determine, by comparing the number of times of switching and the size of the preset threshold, to perform global path switching or local path switching. If the number of handovers is greater than or equal to the preset threshold, global path switching is performed. If the number of handovers is less than the preset threshold, local path switching is performed.
  • the base station further includes:
  • a receiving module configured to receive, before the determining module determines to perform global path switching or local path switching, a handover request message sent by the source base station;
  • the handover request message includes: an anchor point identifier that is connected by the source base station;
  • the determining module is further configured to: determine, by using an anchor point identifier that is connected to the source base station, and an identifier of the mobility anchor point, to perform a global path switch or a local path switch, if the anchor point identifier of the source base station is connected, If the identifier of the mobility anchor is the same, the local path is switched. If the anchor identifier of the source base station is different from the identifier of the mobility anchor, the global path is switched; or
  • the handover request message includes: an identifier of a base station cluster where the source base station is located;
  • the determining module is further configured to determine, by comparing the identifier of the base station cluster where the source base station is located, with the identifier of the base station cluster where the target base station is located, to perform global path switching or local path switching, where the source base station is located.
  • the identifier of the base station cluster is the same as the identifier of the base station cluster where the target base station is located, and the local path is switched. If the identifier of the base station cluster where the source base station is located is different from the identifier of the base station cluster where the target base station is located, the global path is performed. Switch.
  • the receiving module is further configured to receive, by using the first path switch request confirmation message, the first NH sent by the mobility anchor point a parameter; the first NH parameter is generated by the moving anchor point;
  • the base station further includes: And a determining module, configured to determine, according to the first NH parameter, a key used by the next base station, where the next base station is a base station other than the source base station and the target base station.
  • the first NH parameter is the mobility anchor point according to the access management security entity key and the first peer input parameter
  • the obtained parameter includes: a first source base station key, a second NH parameter; the access management security entity key, the first source base station key, and the second
  • the NH parameter is sent by the MME received by the mobility anchor.
  • the first source base station key is, the MME manages a security entity key according to the access, and is not accessing Determined by the layer counter;
  • the second NH parameter is determined by the MME according to the access management security entity key and the second peer input parameter.
  • the first NH parameter is a parameter that is determined by the mobility anchor according to a second source base station key and a random number.
  • the second source base station key is configured by the MME according to an access management security entity key and a non-access stratum counter Determined;
  • the second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the sending module is further configured to send a second to the MME if performing global path switching a path switch request message to trigger modification of a user plane path between the mobility anchor and the SGW.
  • an embodiment of the present invention further provides a mobility anchor, including: a receiver, a processor, and a transmitter;
  • the receiver is configured to receive a path switch request message sent by the target base station, where the processor is configured to keep the user plane path between the mobility anchor point and the SGW unchanged if local path switching is performed, and A user plane path between the mobility anchor and the source base station is switched to the target base station.
  • the transmitter is further configured to send the path switching request message to the MME to trigger modification of the mobility anchor if global path switching is performed. The user plane path between the point and the SGW.
  • the processor is further configured to determine to perform global path switching or local path switching.
  • the processor is further configured to determine whether to perform a global path switch or a local path by comparing a number of times of switching with a preset threshold Switching, if the number of times of switching is greater than or equal to the preset threshold, performing global path switching, and if the number of switching times is less than the preset threshold, performing local path switching.
  • the path switching request message includes: an access identifier of the UE, an access identifier of the UE, and the source An identifier assigned by the anchor device connected by the base station to the UE;
  • the processor is further configured to: perform a global path switch or a local path switch by performing a search on the access identifier of the UE, and if the UE cannot be retrieved according to the access identifier of the UE, perform global Path switching, if the UE is retrieved according to the access identifier of the UE, determining to perform local path switching.
  • the processor is further configured to generate a first next hop NH parameter
  • the transmitter is further configured to send the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines a key used by the next base station according to the first NH parameter;
  • the next base station is a base station other than the source base station and the target base station.
  • the processor is further configured to generate the foregoing according to an access management security entity key and a first peer input parameter An NH parameter; the first peer input parameter includes: a first source base station key, and a second NH parameter.
  • the receiver is further configured to receive the access management security entity key sent by the MME, the first source a base station key, the second NH parameter;
  • the transmitter is further configured to send the second NH parameter to the source base station, so that the The source base station determines a key used by the target base station according to the second NH parameter.
  • the first source base station key is the MME according to the access management security entity key, And determined by the non-access stratum counter;
  • the second NH parameter is determined by the MME according to the access management security real key and the second peer input parameter.
  • the processor is further configured to generate the first NH parameter according to the second source base station key and a random number.
  • the receiver is further configured to receive the second source base station key that is sent by the MME, where The two source base station key is determined by the MME according to the access management security entity key and the non-access stratum counter; or
  • the second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the embodiment of the present invention further provides a base station, where the base station is a target base station, where the base station includes: a receiver, a processor, and a transmitter;
  • the processor is configured to determine to perform global path switching or local path switching.
  • the transmitter is configured to send a first path switching request message to the mobility anchor point to perform the local path switching, so that the mobile anchor is The point keeps the user plane path between the mobility anchor and the SGW unchanged, and causes the mobility anchor to switch the user plane path between the source base station to the target base station.
  • the processor is further configured to determine to perform global path switching or local path switching by comparing a number of switching times with a preset threshold value, If the number of handovers is greater than or equal to the preset threshold, global path switching is performed. If the number of handovers is less than the preset threshold, local path switching is performed.
  • the receiver is configured to receive a handover sent by the source base station before the processor determines to perform global path switching or local path switching.
  • a request message includes: an anchor identifier of the source base station connection;
  • the processor is further configured to: determine, by comparing the anchor point identifier connected to the source base station, with the identifier of the mobility anchor point, perform global path switching or local path switching, if the source base station is connected
  • the anchor point identifier is the same as the identifier of the mobility anchor point, and the local path switch is performed. If the anchor point identifier of the source base station connection is different from the identifier of the mobility anchor point, the global path switch is performed; or
  • the handover request message includes: an identifier of a base station cluster where the source base station is located;
  • the processor is further configured to determine, by comparing the identifier of the base station cluster where the source base station is located, with the identifier of the base station cluster where the target base station is located, to perform global path switching or local path switching, where the source base station is located.
  • the identifier of the base station cluster is the same as the identifier of the base station cluster where the target base station is located, and the local path is switched. If the identifier of the base station cluster where the source base station is located is different from the identifier of the base station cluster where the target base station is located, the global path is performed. Switch.
  • the receiver is further configured to receive, by using the first path, the mobility anchor point Requesting a first NH parameter sent by the confirmation message; the first NH parameter is generated by the mobility anchor point;
  • the processor is further configured to determine, according to the first NH parameter, a key used by a next base station, where the next base station is a base station other than the source base station and the target base station.
  • the first NH parameter is the mobility anchor point according to the access management security entity key and the first peer input parameter
  • the obtained parameter includes: a first source base station key, a second NH parameter; the access management security entity key, the first source base station key, and the second
  • the NH parameter is sent by the MME received by the mobility anchor.
  • the first source base station key is the MME, according to the access management security entity key, and non-access Determined by the layer counter;
  • the second NH parameter is determined by the MME according to the access management security entity key and the second peer input parameter.
  • the first NH parameter is a parameter that is determined by the mobility anchor according to a second source base station key and a random number.
  • the second source base station key is the MME according to an access management security entity key and a non-access stratum Determined by the number;
  • the second source base station key is determined by the MME according to the access management security entity key and the identifier of the mobility anchor.
  • the transmitter is further configured to send a second to the MME if performing global path switching a path switch request message to trigger modification of a user plane path between the mobility anchor and the SGW.
  • the path switching method, the mobile anchor point, and the base station in the embodiment of the present invention perform user plane path switching with the access network device when performing local path switching by using the mobile anchor point, without performing user plane path switching with the core network device. Therefore, the multiple-switching of the path between the core network device and the core network device is avoided, and the dual-connection technology is not required, so that the solution is not limited by the UE characteristics and the macro station coverage, thereby better reducing the signaling of the core network. load.
  • FIG. 2 is a flowchart of a path switching method according to Embodiment 2 of the present invention.
  • FIG. 3 is a flowchart of a path switching method according to Embodiment 3 of the present invention.
  • FIG. 4 is a flowchart of a path switching method according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of a mobile anchor point according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of a base station according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic structural diagram of a mobile anchor point according to Embodiment 7 of the present invention.
  • FIG. 8 is a schematic structural diagram of a base station according to Embodiment 8 of the present invention. detailed description
  • FIG. 1 is a flowchart of a path switching method according to Embodiment 1 of the present invention.
  • the method in this embodiment is applicable to a case where a UE moves in a base station cluster to perform path switching.
  • the base station cluster is composed of at least one base station or a cell in a preset area range, and a base station or a cell in the same base station cluster is connected to the same mobility anchor point.
  • the mobility anchor is connected to the core network device Mobility Management Entity (MME) and the Serving Gateway (SGW).
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the base station may be an evolved base station (eNode B) or a micro base station (Pico).
  • the small cell Small Cell
  • the base station cluster can be a small cell cluster.
  • the method of this embodiment can be performed by a mobile anchor point.
  • the method of an embodiment comprises the following steps:
  • Step 101 The mobility anchor receives a path switch request message sent by the target base station.
  • the mobility anchor may be formed by hardware and/or software, exist as a separate device between the base station cluster and the core network device, and connect the base station cluster with the core network device, or may be located as a separate module in the base station cluster. Internal to any base station or core network device.
  • the core network device may be, for example, any one of a Mobility Management Entity (MME) and a Serving Gateway (SGW). If the mobility anchor is used as a standalone device, the base station cluster may be connected to the core network device by using the mobility anchor point, and specifically, the mobility anchor point is respectively connected to the base station in the base station cluster through the S1 interface, and the S1-C is adopted.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the interface is connected to the MME in the core network device, and is connected to the SGW in the core network device through the S1-U interface.
  • the interface between the mobile anchor point and the base station in the base station cluster, and the interface between the mobile anchor point and the core network device are all based on the S1 interface, but may also be other types of interfaces. The example is not limited to the S1 interface.
  • the mobility anchor point can be a local mobility anchor point, and can serve as a transmission bridge between user data between the access network device and the core network device, that is, a user data transmission bridge between the base station and the SGW, to implement termination of local user data. That is, in the network scenario with the mobility anchor point, the downlink user data sent by the SGW needs to reach the mobility anchor point first, and the mobile anchor point determines the downlink user data. Forwarded to the corresponding base station within the cluster of base stations.
  • the local user data terminated by the mobility anchor may be
  • any user data received by the mobility anchor when the UE moves within the base station cluster If the UE moves within the base station cluster.
  • the base station at the base station cluster sends the uplink data to the mobility anchor point, and the mobile anchor node sends the uplink data to the corresponding SGW.
  • the local path refers to a user data transmission channel between the base station and the mobility anchor;
  • the global path refers to a user data channel between the base station and the SGW.
  • the global path may include two parts: User data transmission channel between the mobile anchor point and the user data transmission channel between the mobile anchor point and the SGW.
  • the mobility anchor connects at least one or more complete base station clusters.
  • the source base station and the target base station are in the same base station cluster, perform global path switching or local path switching as needed; and when the source base station and the target base station are located in different base station clusters, it indicates that the UE moves across the UE. If the source base station is in the range of the base station cluster and moves to another base station cluster, global path switching needs to be performed.
  • Step 102 If the mobile anchor performs local path switching, the mobility anchor keeps the user plane path between the mobile anchor and the SGW unchanged.
  • the mobility anchor maintains the user plane path between the mobility anchor and the SGW unchanged, that is, there is no need to perform user plane path switching between the mobility anchor and the core network device, such as the SGW, that is, the mobility anchor is for the
  • the tunnel identifier and transport address allocated by the SGW for transmitting downlink data remain unchanged. That is to say, if the mobile anchor performs local path switching, the mobile node and the SGW use the original tunnel identifier and the transport address to transmit user plane data.
  • Step 103 The mobility anchor switches a user plane path between the source base station to the target base station. Specifically, the mobility anchor switches the user plane path with the source base station to the target base station, where the mobility anchor performs user plane path switching with the base station for the target base station and the mobility anchor point. User plane data transfer between. Specifically, the mobility anchor device may re-assign the tunnel identifier and the transport address for the uplink data transmission to the target base station, and associate the tunnel identifier and the transport address allocated to the target base station with the UE; The anchor point will be the source base station The assigned tunnel identifier and transport address are associated with the target base station. The mobility anchor saves the tunnel identifier and the transport address of the downlink data transmission sent by the target base station, and sends the downlink data received from the SGW to the target base station according to the tunnel identifier and the transport address of the downlink data transmission.
  • the downlink user data may be transmitted by the SGW to the mobility anchor, and then transmitted to the target base station corresponding to the UE through the mobile anchor.
  • the UE may be transmitted to the mobility anchor through the base station connected thereto, and then transmitted to the SGW by the mobility anchor point.
  • the S1 interface has two signaling procedures, a UE-associated signaling procedure and a non-UE associated signaling procedure.
  • the mobility anchor can receive the path switch request message sent by the target base station, determine the type of the path switch according to the path switch request message, and then perform the corresponding switch process according to the path switch of the corresponding type. That is to say, the mobility anchor can terminate the UE related signaling procedure, such as the signaling procedure of the path switch.
  • the user plane path switching with the access network device is performed without performing user plane path switching with the core network device, thereby avoiding multiple execution of the core network path switching. , reduce the signaling load of the core network.
  • the UE may be a UE with multiple transmitters and multiple receivers, or a single transmitter and a single receiver UE, and the area where the UE is located, There can be coverage of the macro station or no macro station. That is to say, the solution of the embodiment is not limited to the UE characteristics and the coverage of the macro station. Therefore, the solution of the embodiment is not limited by the scenario, and the signaling load of the core network can be better reduced.
  • the user plane path switching with the access network device is performed when the local path is switched by using the mobility anchor point, and the user plane path switching with the core network device is not required, thereby avoiding the core network path switching multiple times.
  • the implementation does not need to adopt the dual connectivity technology, so that the scheme is not limited by scenarios such as the UE characteristics and the macro station coverage, thereby better reducing the signaling load of the core network.
  • FIG. 2 is a flowchart of a path switching method according to Embodiment 2 of the present invention. As shown in FIG. 2, the method further includes: Step 201: If the mobility anchor performs global path switching, the mobility anchor sends the path switch request message to the MME to trigger modification of the user plane path between the mobility anchor and the SGW.
  • the mobility anchor performs global path switching, that is, not only the user plane path switching between the base station and the mobility anchor point but also the path switching between the core network device and the mobility anchor point is performed. And if the mobile anchor device determines to perform global path switching, sending the path switch request message to the MME, to indicate that the MME triggers execution of a core network device, such as a user plane path switch between the SGW and the mobility anchor.
  • the path switch request message may include: the mobile anchor point allocated for transmitting the downlink data tunnel identifier and the transport address.
  • the MME triggers the user plane path switching between the SGW and the mobility anchor, and specifically, the MME sends the downlink data tunnel identifier and transmission by using the bearer modification request message sent to the SGW.
  • the address is sent to the SGW to trigger the SGW to perform a path switch between the SGW and the mobile anchor device.
  • the SGW performs a path switch with the mobile anchor device, where the mobile anchor point is allocated for transmitting a downlink data tunnel identifier and a transport address, and is carried by a service related to the UE by the mobile anchor device.
  • the SGW sends the tunnel identifier and the transport address for the uplink data to the mobility anchor to be sent to the mobility anchor through the bearer modification response message, thereby completing the path for transmitting the uplink and downlink data between the SGW and the mobility anchor point. Switching, that is, completing the user plane path switching between the mobility anchor and the SGW.
  • the mobility anchor point may be re-allocated the tunnel identifier and the transport address for transmitting the downlink data, and the request message is modified by the bearer. Sent to the SGW.
  • the mobility anchor also needs to switch the user plane path with the source base station to the target base station.
  • the mobile anchor point is switched to the target base station with the user plane path of the source base station, and the specific implementation process is similar to that of the foregoing embodiment, and details are not described herein again.
  • the solution is based on the above, and the method further comprises:
  • Step 201a The mobility anchor determines to perform global path switching or local path switching.
  • the mobility anchor point may be determined by determining whether the target base station and the mobility anchor point are in the same base station cluster, may be determined according to the number of path switching in the same base station cluster, or may be according to the path switching request message.
  • the handover type indication message of the carried user plane path is determined, thereby determining whether to perform global path switching or local path switching. It should be noted that the step 201a may be performed before the step 201 and/or the step 102 above.
  • the mobility anchor point may perform corresponding path switching according to different path switching types, and trigger the path of the mobile anchor point and the core network device only when determining to perform global path switching. Switching, thereby reducing the number of core network path switching and reducing the signaling load of the core network.
  • This embodiment scheme also provides a method of determining two types of path switching, which is explained in the above-described embodiment.
  • the mobility anchor determines whether to perform global path switching or local path switching, which specifically includes:
  • the mobility anchor determines whether to perform global path switching or local path switching by comparing the number of switching times with the preset threshold value
  • the mobility anchor determines to perform global path switching
  • the mobility anchor determines to perform local path switching.
  • the number of handovers may be the number of times the UE moves within the cluster of the base station to perform local path switching; the number of handovers may also be that the UE performs inter-base station handover within the area corresponding to the base station cluster or the mobile anchor point. frequency.
  • the mobile anchor records and saves the foregoing switching times, and the initial value may be 0, and the switching times are cumulatively increased by 1 each time the path switching is performed; or the number of switching times is incremented by 1 every time the UE switches between the base stations.
  • the mobility anchor determines to perform global path switching, and resets the number of handovers to 0; if the UE switches in the base station cluster If the number of times is less than the preset threshold, the mobility anchor determines to perform local path switching, and the number of handovers is cumulatively increased by one.
  • the scheme 2 is based on the foregoing solution, where the path switch request message includes: an access identifier of the UE, and the access identifier of the UE is an identifier allocated by the anchor device connected to the source base station.
  • the access identifier of the UE may be an identifier of the access point of the UE (UE Access Point Identity, UE AP ID).
  • the access identifier of the UE may be a logical identifier assigned by the anchor device connected to the source base station to the UE.
  • the mobility anchor determines to perform global path switching or local Path switching can also include:
  • the mobility anchor determines whether to perform global path switching or local path switching by searching for the access identifier of the UE;
  • the mobility anchor determines to perform global path switching
  • the mobility anchor device retrieves the UE according to the access identifier of the UE, the mobility anchor determines to perform local path switching.
  • the mobile anchor determines whether to perform the global path switching or the local path switching by searching the access identifier of the UE, and actually determining whether to perform the global path switching or the local path by whether the source base station and the target base station are located in the same base station cluster.
  • the mobility anchor can retrieve the UE according to the access identifier of the UE, it indicates that the anchor device connected to the source base station and the mobility anchor are the same device, that is, the source base station and the target base station are both connected to the same device.
  • the mobile anchor point that is, the source base station and the target base station are located in the same base station cluster. In this embodiment, if the source base station is located in the same base station cluster, the mobility anchor determines to perform a local path switch message, and if located in a different base station cluster, the mobile anchor device determines to perform a global path. Switch.
  • the mobile anchor point determines whether to perform global path switching or local path switching, and may be implemented in other manners, such as according to the handover type identifier carried in the path switching request message or The indication message is used to determine that the embodiment of the present invention is not limited thereto.
  • the solution of the embodiment provides a specific solution based on the global path switching of the mobility anchor point on the basis of the foregoing solution, and optimizes the foregoing embodiment by using different path switching type determination schemes, thereby ensuring the mobility anchor.
  • the point can selectively trigger the global path switching according to the actual situation, thereby reducing the number of handovers of the core network and reducing the overall core network signaling load of the entire communication system.
  • FIG. 3 is a flowchart of a path switching method according to Embodiment 3 of the present invention. As shown in FIG. 3, the method further includes:
  • Step 301 The mobility anchor generates a first next hop NH parameter.
  • the step of generating the first next hop (NH) parameter may be performed after the step 102, the step 103 is performed, or after the step 103, the embodiment does not This is a limitation.
  • Step 302 The mobility anchor sends the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines a key used by the next base station according to the first NH parameter.
  • the next base station is a base station other than the source base station and the target base station.
  • the path switch request acknowledgement message may be a Path Switch Request Acknowledge message.
  • the target base station determines, according to the first NH parameter, a key used by the next base station, where the target base station obtains a Key Derivation Function (KDF) according to the first NH parameter.
  • KDF Key Derivation Function
  • the key used by the next base station may be the key used to derive integrity protection or / and data encryption keys.
  • the target base station determines the key used by the next base station according to the first NH parameter, gp, and the target base station obtains the longitudinal derivation of the security key, thereby ensuring the security of the masquerading base station to use the key for the legal base station after the handover.
  • the target base station determines, according to the first NH parameter, a key used by the next base station, and may be the target base station according to the first NH parameter, a physical layer cell identity (Physical-layer Cell Identity, PCI for short).
  • the parameters such as the Evolution of the Absolute Radio Frequency Channel Number (EARFCN) are acquired by KDF.
  • the EARFCN may be a downlink radio frequency number.
  • the target base station determines a parameter used by the key used by the next base station, that is, the first NH parameter is generated by the mobility anchor, the first NH parameter is unknown to the source base station, and thus, Even if the key used by the source base station is cracked by the attacker, or the source base station is a pseudo base station, the attacker cannot know the first NH parameter and the key used by the next base station. That is to say, the derivative scheme of the key used by the next base station provided by the solution in this embodiment is difficult to be known by an attacker.
  • the first NH parameter used by the next base station is determined to be generated by the mobility anchor, the first The NH parameter is unknown to the access network side of the UE, especially the source base station, so that the key used by the next base station is difficult to be known by the attacker, thereby ensuring the forward direction between the UE and the base station after handover. Security issues, better secure communication between the UE and the base station.
  • the step 301, the generating, by the mobile anchor device, the first next hop NH parameter includes:
  • the mobility anchor generates the first NH parameter according to the access management security entity key and the first peer input parameter.
  • the access management security entity key (Key Access Security Management
  • Kasme Entity, referred to as Kasme, may be used by the UE and the Home Subscriber Server (HSS) according to the encryption key (Cipher Key, CK for short) in the process of Authentication and Key Agreement (AKA).
  • Cipher Key CK for short
  • AKA Authentication and Key Agreement
  • IK Integrity Key
  • the first synchronous input (Synchronous-Input, SYNC-input) parameter may be generated by the mobile anchor point itself or sent to the mobile anchor point by other network element devices.
  • the SYNC-input parameter can include: a first source base station key, and the second NH parameter.
  • the first source base station key may be an initial key of the source base station, represented by KeNB.
  • the second NH parameter may be an initial NH parameter of the source base station within the base station cluster.
  • the method further includes:
  • the mobility anchor device receives the access management security entity key, the first source base station key, and the second NH parameter sent by the MME.
  • the 1 ⁇ may be sent by the MME to the HSS through the S6a interface.
  • the first source base station key and the second NH parameter are parameters generated by the MME itself.
  • the mobility anchor sends the second NH parameter to the source base station to cause the source base station to determine a key used by the target base station based on the second NH parameter.
  • the mobility anchor may save the received K asme , the first source base station key, and the second NH parameter, and associate the parameters with the corresponding identifier of the UE.
  • the mobile anchor device determines to perform local path switching, during or after switching the user plane path between the source base station to the target base station, regenerating the first NH parameter according to the parameters, and The second NH parameter is sent to the source base station.
  • the key used by the target base station may be a key used by the target base station to communicate with the UE after the user-side path between the mobile base station and the source base station is switched to the target base station, which may be represented as K eNB * .
  • the mobile anchor receiving the access management security entity key, the first source base station key, and the second NH parameter sent by the MME specifically:
  • the mobility anchor receives the access management security entity key, the first source base station key, and the second NH parameter sent by the MME through an initial context setup request message.
  • the initial uplink and downlink setup request message may be an Initial Context Setup Request message
  • the mobile anchor may receive the MME receiving the MME through the S1-C interface.
  • the mobile anchor point as described above, sending the second NH parameter to the source base station, may include:
  • the mobility anchor carries the second NH parameter in the initial context setup request message, and forwards the initial context setup request message to the source base station through the S1 interface.
  • the first source base station key is determined by the MME according to the access management security entity key and the non-access stratum counter.
  • the second NH parameter is determined by the MME according to the access management security real key and the second peer input parameter.
  • the non-access stratum counter may be a counter corresponding to the non-access stratum message, that is, the value of the access stratum counter may be the number of non-access stratum messages sent by the MME.
  • the second peer input parameter may be an initial peer input parameter, and the initial peer input parameter may be all 0s or all 1s or agreed values.
  • the solution of the embodiment is specifically explained by the mobility anchor point generating the first NH parameter according to the access management security entity key and the first peer input parameter, thereby better ensuring the mobility anchor point.
  • the security of the generated first NH parameter ensures forward security issues between the UE and the base station.
  • the method may further include:
  • the mobility anchor generates an initial next chain skip counter (NHCCing Counter, NCC for short).
  • NCCing Counter initial next chain skip counter
  • the value of the first NCC is in one-to-one correspondence with the first NH parameter.
  • the moving anchor point may be: when the first NH parameter is generated, that is, when the foregoing step 301 is performed, the step of generating the first NCC may be performed, or the generating the first NCC may be performed after the generating the first NH parameter. a step of obtaining the first NCC corresponding to the first NH parameter.
  • the value of the first NCC indicates the number of times the mobile anchor updates the NCC, and the NCC needs to be updated every time the UE performs a path switch.
  • the embodiment scheme may also indicate, by the first NCC, the number of handovers of the UE in the base station cluster.
  • the mobility anchor sends the first NCC to the target base station by using the path switch request acknowledgement message, so that the target base station sends the first NCC to the UE, and the UE determines the first NH according to the first NCC. And determining a key used by the next base station according to the first NH parameter.
  • the mobility anchor may be configured to carry the first NH parameter and the first NCC parameter in the path switch request acknowledgement message in step 302, and then send the signal to the target base station. Due to the problem of transmission security, the first NH parameter cannot be transmitted between the UE and the base station, and thus the first NCC can be sent to the UE through the target base station.
  • the UE may determine the first NH parameter according to the correspondence between the first NCC and the first NH parameter, and then determine a key used by the next base station according to the first NH parameter. .
  • the target base station and the UE side may determine a key used by the next base station according to the first NH parameter.
  • the target base station needs to determine the key used by the next base station to send the to-be-switched base station before the path switching is performed next time, and ensure that the UE performs the path switching again after the UE performs the path switching.
  • the base stations all have the same key, so as to better ensure the communication security between the UE and the base station.
  • the foregoing mobile anchor point generates the first next hop chain counter NCC in an incremental manner, and specifically includes:
  • the mobility anchor adds a second operation to the second NCC to generate the first NCC.
  • the method further includes:
  • the mobility anchor receives the second NCC sent by the MME through the initial context setup request message.
  • the mobility anchor may be the second NCC sent when the MME sends the access management security entity key, the first source base station key, and the second NH parameter by using the initial context setting request message. .
  • the embodiment further updates the NCC, and sends the updated NCC to the UE, to avoid air interface transmission of the key parameter, thereby better ensuring communication security between the UE and the base station after handover. .
  • the generating, by the mobility anchor, the first NH parameter specifically includes: the mobility anchor generating the first NH parameter according to the second source base station key and a random number.
  • the non-predictiveness of the random number may cause the mobile anchor to have an uncertainty according to the second source base station key and the first NH parameter generated by the random number, which is difficult to be known by the pseudo base station, and the better Forward security issues between the UE and the base station.
  • the method further includes:
  • the mobility anchor receives the second source base station key sent by the MME.
  • the second source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter;
  • the second source base station key may also be determined by the MME according to the access management security entity key and the identifier of the mobile anchor device.
  • access management security entity key and the non-access stratum counter in the solution of the embodiment may be as described in the foregoing embodiment 3, and details are not described herein again.
  • the solution for generating the first NH parameter according to the second source base station key and the random number, and how to obtain the second source base station key and the parameters themselves are specifically implemented by the mobility anchor point. It is explained that the uncertainty of the first NH parameter may be improved, thereby ensuring the security of the key used by the next base station determined by the first NH, and ensuring the forward security problem between the UE and the base station. .
  • FIG. 4 is a flowchart of a path switching method according to Embodiment 4 of the present invention. As shown in FIG. 4, the method specifically includes the following:
  • Step 401 The target base station determines to perform global path switching or local path switching.
  • Step 402 If the target base station performs local path switching, the target base station sends a first path switching request message to the mobility anchor point, so that the mobility anchor point keeps the user plane path between the mobility anchor device and the SGW unchanged. And the mobile anchor point will switch the user plane path between the source base station to the target base station.
  • the difference between the solution of the embodiment and the path switching method provided in the first embodiment is that the type of path switching, that is, the global path switching or the local path, can be determined by the target base station, and if local path switching is performed,
  • the mobility anchor sends a first path switch request message.
  • the first path switch request message may include an indication message corresponding to the local path switch.
  • the move After receiving the first path switching request message, the anchor point may perform a scheme for triggering local path switching without determining the type of the path switching.
  • the specific implementation process of the local path switching of the mobility anchor may be similar to that in the foregoing embodiment 1, and details are not described herein again.
  • the target base station determines the type of the path switch, and after determining to perform the local path switch, the first path switch request message may be sent to the mobile anchor point, where the message may include a local path switch indication,
  • the mobile anchor point is triggered to perform user plane path switching with the access network device without performing user plane path switching with the core network device, thereby avoiding multiple execution of the core network path switching, and eliminating the need for dual connectivity technology.
  • the scheme is not limited by scenarios such as the UE characteristics and macro station coverage, thereby better reducing the signaling load of the core network.
  • the target base station determines that the global path switching or the local path switching is performed by:
  • the target base station determines to perform global path switching or local path switching by comparing the number of switching times with the preset threshold.
  • the target base station determines to perform global path handover
  • the target base station determines to perform local path switching. Specifically, the target base station determines, according to the number of handovers and the preset threshold, a specific implementation process and an explanation of the global path switching or the local path switching.
  • the mobile anchor point determines according to the number of handovers and a preset threshold. The scheme is similar, and will not be described here. The difference is only in the difference of the execution subject.
  • the method may further include:
  • the target base station receives the handover request message sent by the source base station; the handover request message includes: an anchor identifier of the source base station connection.
  • the handover request message may specifically be a Handover Request message.
  • the target base station determines to perform global path switching or local path switching, and may further include:
  • the target base station determines to perform global path switching or local path switching by comparing the anchor point identifier of the source base station connection with the identifier of the mobility anchor point;
  • the target base station does Make local path switching
  • the target base station determines to perform global path switching.
  • the solution in this embodiment determines whether the source base station and the target base station are located in the same anchor point device by comparing whether the anchor point identifier of the source base station connection is the same as the identifier of the mobility anchor point, and then determining the source base station. Whether it is located in the same base station cluster as the target base station. If the anchor point identifier of the source base station is the same as the identifier of the mobility anchor point, and the target base station is located in the same base station cluster as the source base station, the target base station determines to perform local path switching. If the anchor point identifier of the source base station is different from the identifier of the mobility anchor point, and the target base station and the source base station are located in different base station clusters, the target base station determines to perform global path switching.
  • the foregoing handover request message may include: an identifier of a base station cluster where the source base station is located; correspondingly, the target base station determines, in the foregoing step 401, that the global path switch or the local path switch is performed, which may include:
  • the target base station determines to perform global path switching or local path switching by comparing the identifier of the base station cluster where the source base station is located with the identifier of the base station cluster where the target base station is located;
  • the target base station determines to perform local path switching
  • the target base station determines to perform global path switching.
  • the identifier of the cluster of the base station where the source base station is located may be represented by the location information of the area where the source base station is located, and the identifier of the base station cluster to which the mobility anchor point is connected may be represented by the location information of the area where the mobile anchor point is located.
  • the identifier of the base station cluster where the source base station is located is the same as the identifier of the base station cluster where the target base station is located, it indicates that the target base station and the source base station are located in the same base station cluster; if the identifier of the base station cluster where the source base station is located, and the target base station If the identifiers of the clusters of the base stations are different, it indicates that the target base station and the source base station are located in different base station clusters.
  • the solution of the embodiment also provides a plurality of implementable manners of the foregoing embodiment, and the path switching scheme provided by the embodiment is more applicable.
  • the solution of the embodiment optionally, further includes: Step 403: The target base station receives the mobility anchor through the first path switching request acknowledgement message The first NH parameter sent; the first NH parameter is generated by the moving anchor point.
  • Step 404 The target base station determines, according to the first NH parameter, a key used by the next base station, where the next base station is a base station other than the source base station and the target base station.
  • the first NH parameter may be a parameter obtained by the mobility anchor according to the access management security entity key and the first peer input parameter; the first peer input parameter includes: The source base station key, the second NH parameter; the access management security entity key, the first source base station key, and the second NH parameter are sent by the MME received by the mobility anchor.
  • the access management security entity key, the first source base station key, and the second NH parameter are sent by the MME received by the mobility anchor by using an initial context setup request message.
  • the first source base station key in the foregoing solution is determined by the MME according to the access management security entity key and the non-access stratum counter;
  • the second NH parameter is determined by the MME according to the access management security entity key and the second peer input parameter.
  • the method described in the foregoing solution further includes:
  • the target base station receives the first NCC sent by the mobility anchor through the first path switch request acknowledgement message; the first NCC is generated by the mobile anchor point in an incremental manner.
  • the target base station sends the first NCC to the UE, so that the UE determines the first NH parameter according to the first NCC, and determines a key used by the next base station according to the first NH parameter.
  • the step of the target base station receiving the first NCC may be performed simultaneously with the foregoing step 403, and the step of the target base station sending the first NCC to the UE may be performed simultaneously with the foregoing step 404 or This is done in succession, and this application is not intended to be limiting.
  • the first NCC in the foregoing solution is generated by adding, by the mobile anchor point, the second NCC.
  • the second NCC may be sent by the MME received by the mobility anchor through the initial context setup request message.
  • the first NH parameter in the foregoing solution may also be a parameter determined by the mobility anchor according to the second source base station key and the random number.
  • the second source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter;
  • the second source base station key is the MME according to the access management security entity key and the mobility anchor The identification of the point is determined.
  • the target base station may obtain the key used by the next base station according to the NH parameter of different format generated by the mobility anchor point, and ensure the use of the key by the next base station due to the unpredictability of the NH parameter to the pseudo base station. Security, thus ensuring forward security issues between the UE and the base station.
  • the method further includes: Step 405: If the target base station performs global path switching, the target base station sends a second path switch request message to the MME to trigger the modification.
  • the solution may further include:
  • the target base station receives a third NH parameter sent by the MME by using a second path switch request acknowledgement message; the third NH parameter is generated by the MME.
  • the target base station determines a key used by the next base station according to the third NH parameter; wherein the next base station is a base station other than the source base station and the target base station.
  • the third NH parameter is similar to the first NH parameter generated by the mobility anchor in the foregoing embodiment, and may be generated by the MME according to the access management security entity key and the first peer input parameter, or It is generated according to the second source base station key and the random number.
  • the access management security entity key, the first peer input parameter generation, the second source base station key, and the random number may be similar to the foregoing embodiment, and details are not described herein again.
  • the target base station determines the type of path switching, so that in the case of performing local path switching, the first path switching request message is sent to the mobility anchor to trigger the mobility anchor to perform interaction with the access network device.
  • User plane path switching without performing user plane path switching with the core network device, and in the case of global path switching, triggering global path switching by sending a second path switching request message to the mobility anchor point .
  • the solution of the embodiment can selectively perform the global path switching, so as to avoid multiple executions of the core network path switching, and does not need to adopt the dual connection technology, so that the solution is not limited by the UE characteristics and the macro station coverage. , thereby better reducing the signaling load of the core network.
  • Embodiment 5 of the present invention further provides a mobile anchor point.
  • FIG. 5 is a schematic structural diagram of a mobile anchor point according to Embodiment 5 of the present invention. As shown in FIG. 5, the mobile anchor point 500 includes:
  • the receiving module 501 is configured to receive a path switch request message sent by the target base station.
  • the maintaining module 502 is configured to maintain the mobility between the anchor point 500 and the SGW if local path switching is performed. The user plane path is unchanged.
  • the switching module 503 is configured to switch the user plane path between the mobility anchor 500 and the source base station to the target base station.
  • the mobile anchor point 500 further includes:
  • a sending module configured to send the path switch request message to the MME to trigger modification of the user plane path between the mobility anchor 500 and the SGW.
  • the mobile anchor point 500 may further include:
  • the determining module is configured to determine whether to perform global path switching or local path switching.
  • the determining module is specifically configured to determine whether to perform global path switching or local path switching by comparing the number of switching times with the preset threshold, if the number of switching times is greater than or equal to The preset threshold is used to perform global path switching. If the number of switching times is less than the preset threshold, local path switching is performed.
  • the path switch request message in the foregoing solution includes: an access identifier of the UE; the access identifier of the UE is an identifier allocated by the anchor device connected to the source base station to the UE.
  • the determining module is further configured to: perform a global path switch or a local path switch by performing a search on the access identifier of the UE, and if the UE cannot be retrieved according to the access identifier of the UE, perform a global path. Switching, if the UE is retrieved according to the access identifier of the UE, local path switching is performed.
  • the anchor point 500 is further moved, and further includes: a generating module, configured to generate a first NH parameter.
  • the sending module is further configured to send the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines, according to the first NH parameter, a key used by the next base station;
  • the base station is a base station other than the source base station and the target base station.
  • the generating module is further configured to generate the first NH parameter according to the access management security entity key and the first peer input parameter; wherein the first peer input parameter comprises: the first source base station key , the second NH parameter.
  • the receiving module 501 is further configured to receive the access management security entity key, the first source base station key, and the second NH parameter sent by the MME.
  • the sending module is further configured to send the second NH parameter to the source base station, so that the source base station determines a key used by the target base station according to the second NH parameter.
  • the first source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter.
  • the second NH parameter may be determined by the MME according to the access management security real key and the second peer input parameter.
  • the generating module is further configured to generate the first NH parameter according to the second source base station key and the random number.
  • the receiving module 501 is further configured to receive the second source base station key sent by the MME, where the second source base station key is the MME according to the access management security entity key and the non-access layer Determined by the counter; or
  • the second source base station key is determined by the MME according to the access management security entity key and the identity of the mobility anchor.
  • the mobility anchor provided by the solution in this embodiment can implement the path switching method performed by the mobility anchor provided by any of the foregoing embodiments.
  • the specific implementation process and the beneficial effects are similar to those in the foregoing embodiment, and details are not described herein again.
  • FIG. 6 is a schematic structural diagram of a base station according to Embodiment 6 of the present invention. As shown in FIG. 6, the base station 600 includes:
  • the determining module 601 is configured to determine whether to perform global path switching or local path switching.
  • the sending module 602 is configured to send a first path switching request message to the mobility anchor point if the local path switching is performed, so that the mobility anchor point keeps the user plane path between the mobility anchor point and the SGW unchanged, and the mobility anchor is The point switches the user plane path between the source base station to the target base station.
  • the base station 600 is the target base station.
  • the determining module 601 is further configured to determine, by comparing the number of switching times and the preset threshold, to perform global path switching or local path switching, and if the number of switching times is greater than or equal to the preset threshold, proceeding Global path switching. If the number of switching times is less than the preset threshold, local path switching is performed.
  • the base station 600 further includes:
  • the receiving module is configured to: before the determining module 601 determines to perform global path switching or local path switching, receive a handover request message sent by the source base station; the handover request message includes: an anchor point identifier that is connected by the source base station.
  • the determining module 601 is further configured to: determine, by comparing the anchor point identifier connected to the source base station, with the identifier of the mobility anchor point, perform global path switching or local path switching, if the source base station is connected
  • the anchor point identifier is the same as the identifier of the mobility anchor point, and the local path switch is performed. If the anchor point identifier of the source base station connection is different from the identifier of the mobility anchor point, the global path switch is performed. or,
  • the handover request message includes: an identifier of a base station cluster where the source base station is located.
  • the determining module 601 is further configured to: compare the identifier of the base station cluster where the source base station is located with the identifier of the base station cluster where the target base station is located, and determine whether to perform global path switching or local path switching, if the identifier of the base station cluster where the source base station is located If the identifier of the base station cluster where the target base station is located is the same, the local path switch is performed. If the identifier of the base station cluster where the source base station is located is different from the identifier of the base station cluster where the target base station is located, the global path switch is performed.
  • the receiving module is further configured to receive a first NH parameter sent by the mobility anchor through the first path switching request acknowledgement message; the first NH parameter may be generated by the mobility anchor.
  • Base station 600 also includes:
  • a determining module configured to determine, according to the first NH parameter, a key used by the next base station.
  • the next base station may be other base stations than the source base station and the target base station.
  • the first NH parameter may be a parameter obtained by the mobility anchor according to the access management security entity key and the first peer input parameter.
  • the first peer input parameter includes: a first source base station key, a second NH parameter; the access management security entity key, the first source base station key, and the second NH parameter are the mobility anchor The point is received by the MME.
  • the first source base station key may be determined by the MME according to the access management security entity key and a non-access stratum counter.
  • the second NH parameter may be determined by the MME according to the access management security entity key and the second peer input parameter.
  • the first NH parameter may be a parameter determined by the mobility anchor according to the second source base station key and the random number.
  • the second source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter;
  • the second source base station key may be determined by the MME according to the access management security entity key and the identifier of the mobility anchor. Further, the sending module 602 is further configured to: if the global path switching is performed, send a second path switching request message to the MME, to trigger modification of the user plane path between the mobility anchor point and the SGW.
  • the base station provided in this embodiment may implement the path switching method performed by the base station provided by the foregoing embodiment, and the specific implementation process and the beneficial effects are similar to those in the foregoing embodiment, and details are not described herein again.
  • Embodiment 7 of the present invention also provides a mobile anchor point.
  • FIG. 7 is a schematic structural diagram of a mobile anchor point according to Embodiment 7 of the present invention.
  • the mobile anchor 700 includes: a receiver 701, a processor 702, and a transmitter.
  • the receiver 701 is configured to receive a path switch request message sent by the target base station.
  • the processor 702 is configured to: if local path switching is performed, keep a user plane path between the mobility anchor and the SGW unchanged, and switch a user plane path between the mobility anchor and the source base station to the target base station.
  • the transmitter 703 is further configured to send the path switch request message to the MME to perform a global path switch to trigger modification of the user plane path between the mobility anchor and the SGW.
  • the processor 702 is further configured to determine to perform global path switching or local path switching.
  • the processor 702 in the solution is further configured to determine whether to perform global path switching or local path switching by comparing the number of switching times with the preset threshold, and if the number of switching times is greater than or equal to the preset threshold, Then, global path switching is performed. If the number of switching times is less than the preset threshold, local path switching is performed.
  • the path switch request message includes: an access identifier of the UE, where the access identifier of the UE is an identifier allocated by the anchor device connected to the source base station.
  • the processor 702 is further configured to: determine, by using the access identifier of the UE, to perform global path switching or local path switching, and if the UE cannot be retrieved according to the access identifier of the UE, perform global Path switching, if the UE is retrieved according to the access identifier of the UE, local path switching is performed.
  • the processor 702 is further configured to generate a first next hop NH parameter.
  • the transmitter 703 is further configured to send the first NH parameter to the target base station by using a path switch request acknowledgement message, so that the target base station determines a key used by the next base station according to the first NH parameter.
  • the next base station is a base station other than the source base station and the target base station.
  • the processor 702 is further configured to generate the first NH parameter according to the access management security entity key and the first peer input parameter; the first peer input parameter includes: a first source base station key, The second NH parameter.
  • the receiver 701 is further configured to receive the access management security entity key, the first source base station key, and the second NH parameter sent by the MME.
  • the transmitter 703 is further configured to send the second NH parameter to the source base station, so that the source base station determines a key used by the target base station according to the second NH parameter.
  • the first source base station key is determined by the MME according to the access management security entity key and the non-access stratum counter.
  • the second NH parameter is determined by the MME according to the access management security real key and the second peer input parameter.
  • the processor 702 in the foregoing embodiment is further configured to generate the first NH parameter according to the second source base station key and the random number.
  • the receiver 701 is further configured to receive the second source base station key sent by the MME, where the second source base station key is the MME according to the access management security entity key and the non-access stratum counter Determined; or
  • the second source base station key is determined by the MME according to the access management security entity key and the identity of the mobility anchor.
  • the mobility anchor provided by the solution in this embodiment can implement the path switching method performed by the mobility anchor provided by any of the foregoing embodiments.
  • the specific implementation process and the beneficial effects are similar to those in the foregoing embodiment, and details are not described herein again.
  • Embodiment 8 of the present invention further provides a base station.
  • FIG. 8 is a schematic structural diagram of a base station according to Embodiment 8 of the present invention.
  • the base station 800 includes: a receiver 801, a processor 802, and a transmitter 803.
  • the processor 802 is configured to determine to perform global path switching or local path switching.
  • the transmitter 803 is configured to send a first path switch request message to the mobility anchor point if the local path switch is performed, so that the mobility anchor point keeps the user plane path between the mobility anchor point and the SGW unchanged, and the mobile anchor is The point switches the user plane path between the source base station to the target base station.
  • Base station 800 is the Target base station.
  • the processor 803 in the solution of the foregoing embodiment is further configured to determine whether to perform global path switching or local path switching by comparing the number of switching times with the preset threshold, and if the number of switching times is greater than or equal to the preset threshold, Then, global path switching is performed. If the number of switching times is less than the preset threshold, local path switching is performed.
  • the receiver 801 is configured to: before the processor 802 determines to perform global path switching or local path switching, receive a handover request message sent by the source base station; the handover request message includes: an anchor identifier of the source base station connection.
  • the processor 802 is further configured to determine, by comparing the anchor identifier of the source base station connection with the identifier of the mobility anchor point, whether to perform global path switching or local path switching, if the anchor point identifier of the source base station is connected, and the mobility anchor If the identifiers of the points are the same, the local path switching is performed. If the anchor point identifier of the source base station is different from the identifier of the mobility anchor point, global path switching is performed. Or,
  • the handover request message includes: an identifier of a cluster of base stations where the source base station is located.
  • the processor 802 is further configured to: determine the global path switch or the local path switch by comparing the identifier of the base station cluster where the source base station is located with the identifier of the base station cluster where the target base station is located, if the identifier of the base station cluster where the source base station is located If the identifier of the base station cluster where the target base station is located is the same, the local path switch is performed. If the identifier of the base station cluster where the source base station is located is different from the identifier of the base station cluster where the target base station is located, the global path switch is performed.
  • the receiver 801 is further configured to receive the first NH parameter sent by the mobility anchor through the first path switching request acknowledgement message; the first NH parameter is the mobile The anchor is generated.
  • the processor 802 is further configured to determine, according to the first NH parameter, a key used by the next base station, where the next base station is a base station other than the source base station and the target base station.
  • the first NH parameter may be a parameter obtained by the mobility anchor according to the access management security entity key and the first peer input parameter; the first peer input parameter includes: the first source base station key , the second NH parameter.
  • the access management security entity key, the first source base station key, and the second NH parameter may be sent by the MME received by the mobility anchor.
  • the first source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter.
  • the second NH parameter is the MME inputting the security entity key according to the access, the second peer input Determined by the parameters.
  • the first NH parameter may be a parameter determined by the mobility anchor according to the second source base station key and the random number.
  • the second source base station key may be determined by the MME according to the access management security entity key and the non-access stratum counter.
  • the second source base station key may also be determined by the MME according to the access management security entity key and the identity of the mobility anchor.
  • the transmitter 803 is further configured to send a second path switch request message to the MME to trigger modification of the user plane path between the mobility anchor point and the SGW, if the global path switch is performed.
  • the base station provided by the solution in this embodiment can implement the path switching method performed by the base station provided by any of the foregoing embodiments.
  • the specific implementation process and the beneficial effects are similar to those in the foregoing embodiment, and are not described herein.

Landscapes

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

Abstract

本发明实施例提供一种路径切换方法、移动锚点及基站。本发明实施例所提供的路径切换方法,包括:移动锚点接收目标基站发送的路径切换请求消息;若所述移动锚点进行本地路径切换,所述移动锚点保持所述移动锚点和服务网关SGW间的用户面路径不变;所述移动锚点将与源基站间的用户面路径切换到所述目标基站。本发明实施例的方案不受限于该UE特性及宏站覆盖等场景的限制,从而更好地降低核心网的信令负荷。

Description

路径切换方法、 移动锚点及基站
技术领域
本发明实施例涉及通信技术, 尤其涉及一种路径切换方法、 移动锚点及 基站。 背景技术
数据统计显示, 20%的热点地区承担了运营商 80%的流量, 热点地区容 量瓶颈问题迫在眉睫, 小站以其低成本, 站址选方便, 部署简单而称为运营 商的新宠。 随着对业务量需求的增加, 小站的部署越来越密集。 小站的密集 部署使得用户设备 (User Equipment, 简称 UE) 在小站之间移动过程中, 路 径切换的频率增大。由于 UE的路径切换流程包括 UE与小站之间的路径切换, 小站与核心网设备之间的路径切换。 也就是说, UE每进行一次路径切换, 目 标基站均需向核心网设备发送切换请求消息。 随着小站部署数目的增加, 势 必造成对核心网信令负荷过大。
现有技术采用双连接 (Dual Connectivity)技术, 使得 UE同时从宏站和小站 接收数据, 通过宏站提供广覆盖减少切换次数, 通过小站分担热点地区的数 据容量。在该双连接技术中, 该 UE的用户面数据终结于宏站, 该 UE在小站 间移动过程中, 该 UE 的用户面数据对于核心网是透明的。 也就是说, 若该 UE在小站间的移动, 该 UE只需切换与小站之间的路径即可, 而无需执行核 心网侧的路径切换, 从而减少了核心网的信令负荷。 由于, 该双连接技术必 须是以该 UE至少具有双接收机和双发射机, 且必须有宏站的覆盖为前提的。 然而, 当前网络中, 还存在大量的单接收机或单发射机的 UE, 或是在某些场 景中, 并没有宏站的覆盖, 从而无法支持并执行基于该双连接技术的路径切 换。
由于现有技术中, 基于双连接技术的路径切换方案的执行场景受限, 并无 法解决所有场景中的核心网信令负荷大的问题。 发明内容 本发明实施例提供一种路径切换方法、 移动锚点及基站, 以解决现有技 术方案执行场景受限, 无法解决所有场景中的核心网信令负荷大的问题。
第一方面, 本发明实施例提供一种路径切换方法, 包括:
移动锚点接收目标基站发送的路径切换请求消息;
若所述移动锚点进行本地路径切换, 所述移动锚点保持所述移动锚点和 服务网关 SGW间的用户面路径不变;
所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
根据第一方面, 在第一方面的第一种可能实现的方式中, 所述方法还包 括:
若所述移动锚点进行全局路径切换,所述移动锚点向移动管理实体 MME 发送所述路径切换请求消息, 以触发修改所述移动锚点和所述 SGW 间的用 户面路径。
根据第一方面或第一方面的第一种可能实现的方式, 在第二种可能实现 的方式中, 所述方法还包括:
所述移动锚点判断进行全局路径切换或本地路径切换。
根据第一方面的第二种可能实现的方式, 在第三种可能实现的方式中, 所述移动锚点判断进行全局路径切换或本地路径切换, 包括:
所述移动锚点通过比较切换次数与预设阈值的大小, 判断进行全局路径 切换还是本地路径切换;
若所述切换次数大于或等于所述预设阈值, 则所述移动锚点确定进行全 局路径切换;
若所述切换次数小于所述预设阈值, 则所述移动锚点确定进行本地路径 切换。
根据第一方面的第二种可能实现的方式, 在第四种可能实现的方式中, 所述路径切换请求消息包括: UE的接入标识; 所述 UE的接入标识为, 与所 述源基站连接的锚点设备为所述 UE分配的标识;
所述移动锚点判断进行全局路径切换或本地路径切换, 包括:
所述移动锚点通过对所述 UE的接入标识进行检索, 判断进行全局路径 切换或本地路径切换;
若所述移动锚点根据所述 UE的接入标识, 无法检索到所述 UE, 则所述 移动锚点确定进行全局路径切换;
若所述移动锚点根据所述 UE的接入标识, 检索到所述 UE, 则所述移动 锚点确定进行本地路径切换。
根据第一方面至第一方面的第四种可能实现的方式中任意一种, 在第五 种可能实现的方式中, 所述方法, 还包括:
所述移动锚点生成第一下一跳 NH参数;
所述移动锚点通过路径切换请求确认消息将所述第一 NH参数发送至所 述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基站使用的 密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
根据第一方面的第五种可能实现的方式, 在第六种可能实现的方式中, 所述移动锚点生成第一 NH参数, 包括:
所述移动锚点根据接入管理安全实体密钥及第一同歩输入参数生成所述 第一 NH参数;
所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数。
根据第一方面的第六种可能实现的方式, 在第七种可能实现的方式中, 还包括:
所述移动锚点接收 MME发送的所述接入管理安全实体密钥、 所述第一 源基站密钥、 所述第二 NH参数;
所述移动锚点将所述第二 NH参数发送至所述源基站, 以使所述源基站 根据所述第二 NH参数确定所述目标基站使用的密钥。
根据第一方面的第六或第七种可能实现的方式, 在第八种可能实现的方 式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的;
所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
根据第一方面的第五种可能实现的方式, 在第九种可能实现的方式中, 所述移动锚点生成第一 NH参数, 包括:
所述移动锚点根据第二源基站密钥及随机数生成所述第一 NH参数。 根据第一方面的第九种可能实现的方式, 在第十种可能实现的方式中, 所述方法还包括: 所述移动锚点接收 MME所发送的所述第二源基站密钥; 其中, 所述第 二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计数器所 确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
第二方面, 本发明实施例提供还一种路径切换方法, 包括:
目标基站判断进行全局路径切换或本地路径切换;
若所述目标基站进行本地路径切换, 所述目标基站向移动锚点发送第一 路径切换请求消息, 以使所述移动锚点保持所述移动锚点和 SGW 间的用户 面路径不变, 并使所述移动锚点将与源基站间的用户面路径切换到所述目标 基站。
根据第二方面, 在第二方面的第一种可能实现的方式中, 所述目标基站 判断进行全局路径切换或本地路径切换, 包括:
所述目标基站通过比较切换次数与预设阈值的大小, 判断进行全局路径 切换或本地路径切换;
若所述切换次数大于或等于所述预设阈值, 则所述目标基站确定进行全 局路径切换;
若所述切换次数小于所述预设阈值, 则所述目标基站确定进行本地路径 切换。
根据第二方面, 在第二方面的第二种可能实现的方式中, 所述目标基站 判断进行全局路径切换或本地路径切换之前, 还包括:
所述目标基站接收所述源基站发送的切换请求消息; 所述切换请求消息 包括: 所述源基站连接的锚点标识;
所述目标基站判断进行全局路径切换或本地路径切换, 包括:
所述目标基站通过比较所述源基站连接的锚点标识, 与所述移动锚点的 标识, 判断进行全局路径切换或本地路径切换;
若所述源基站连接的锚点标识, 与所述移动锚点的标识相同, 所述目标 基站确定进行本地路径切换;
若所述源基站连接的锚点标识, 与所述移动锚点的标识不同, 所述目标 基站确定进行全局路径切换; 或者, 所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述目标基站判断进行全局路径切换或本地路径切换, 包括: 所述目标基站通过比较所述源基站所在基站簇的标识, 与所述目标基站 所在基站簇的标识, 判断进行全局路径切换或本地路径切换;
若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相 同, 所述目标基站确定进行本地路径切换;
若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识不 同, 所述目标基站确定进行全局路径切换。
根据第二方面至第二方面的第二种可能实现的方式中任意一种, 在第三 种可能实现的方式中, 所述方法, 还包括:
所述目标基站接收所述移动锚点通过第一路径切换请求确认消息发送的 第一 NH参数; 所述第一 NH参数为所述移动锚点所生成的;
所述目标基站根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
根据第二方面的第三种可能实现的方式, 在第四种可能实现的方式中, 所述第一 NH参数为所述移动锚点根据接入管理安全实体密钥及第一同歩输 入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管理安全实体密钥、 所述第一源基站密钥及所述第二 NH 参数为所述移动锚点接收的 MME发送的。
根据第二方面的第四种可能实现的方式, 在第五种可能实现的方式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接 入层计数器所确定的;
所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
根据第二方面的第三种可能实现的方式, 在第六种可能实现的方式中, 所述第一 NH参数为所述移动锚点根据第二源基站密钥及随机数所确定的参 数。
根据第二方面的第六种可能实现的方式, 在第七种可能实现的方式中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计 数器所确定的; 或者 所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
根据第二方面至第二方面的第七种可能实现的方式中任意一种, 在第八 种可能实现的方式中, 所述方法还包括:
若所述目标基站进行全局路径切换, 所述目标基站向 MME发送第二路 径切换请求消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
第三方面, 本发明实施例还提供一种移动锚点, 包括:
接收模块, 用于接收目标基站发送的路径切换请求消息;
保持模块, 用于若进行本地路径切换, 保持所述移动锚点和 SGW 间的 用户面路径不变;
切换模块, 用于将所述移动锚点与源基站间的用户面路径切换到所述目 标基站。
根据第三方面, 在第三方面的第一种可能实现的方式中, 所述移动锚点, 还包括:
发送模块, 用于若进行全局路径切换, 向 MME发送所述路径切换请求 消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
根据第三方面或第三方面的第一种可能实现的方式, 在第二种可能实现 的方式中, 所述移动锚点, 还包括:
判断模块, 用于判断进行全局路径切换或本地路径切换。
根据第三方面的第二种可能实现的方式, 在第三种可能实现的方式中, 所述判断模块, 还用于通过比较切换次数与预设阈值的大小, 判断进行全局 路径切换还是本地路径切换, 若所述切换次数大于或等于所述预设阈值, 则 进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径切 换。
根据第三方面的第二种可能实现的方式, 在第四种可能实现的方式中, 所述路径切换请求消息包括: UE的接入标识; 所述 UE的接入标识为, 与所 述源基站连接的锚点设备为所述 UE分配的标识;
所述判断模块, 还用于通过对所述 UE的接入标识进行检索, 判断进行 全局路径切换或本地路径切换, 若根据所述 UE的接入标识无法检索到所述 UE, 则进行全局路径切换, 若根据所述 UE的接入标识检索到所述 UE, 则 进行本地路径切换。
根据第三方面至第三方面的第四种可能实现的方式中任意一种, 在第五 种可能实现的方式中, 所述移动锚点, 还包括:
生成模块, 用于生成第一 NH参数;
所述发送模块, 还用于通过路径切换请求确认消息将所述第一 NH参数 发送至所述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基 站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的 其他基站。
根据第三方面的第五种可能实现的方式, 在第六种可能实现的方式中, 所述生成模块, 还用于根据接入管理安全实体密钥及第一同歩输入参数生成 所述第一 NH参数; 其中, 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数。
根据第三方面的第六种可能实现的方式, 在第七种可能实现的方式中, 所述接收模块, 还用于接收所述 MME发送的所述接入管理安全实体密钥、 所述第一源基站密钥、 所述第二 NH参数;
所述发送模块, 还用于将所述第二 NH参数发送至所述源基站, 以使所 述源基站根据所述第二 NH参数确定所述目标基站使用的密钥。
根据第三方面的第六或第七种可能实现的方式, 在第八种可能实现的方 式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的;
所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
根据第三方面的第五种可能实现的方式, 在第九种可能实现的方式中, 所述生成模块,还用于根据第二源基站密钥及随机数生成所述第一 NH参数。
根据第三方面的第九种可能实现的方式, 在第十种可能实现的方式中, 所述接收模块, 还用于接收所述 MME所发送的所述第二源基站密钥; 其中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计 数器所确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。 第四方面, 本发明实施例还提供一种基站, 所述基站为目标基站, 所述 基站包括:
判断模块, 用于判断进行全局路径切换或本地路径切换;
发送模块, 用于若进行本地路径切换, 向移动锚点发送第一路径切换请 求消息, 以使所述移动锚点保持所述移动锚点和 SGW间的用户面路径不变, 并使所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
根据第四方面, 在第四方面的第一种可能实现的方式中, 所述判断模块, 还用于通过比较切换次数与预设阈值的大小, 判断进行全局路径切换或本地 路径切换, 若所述切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径切换。
根据第四方面, 在第四方面的第二种可能实现的方式中, 所述基站, 还 包括:
接收模块, 用于在所述判断模块判断进行全局路径切换或本地路径切换 之前, 接收所述源基站发送的切换请求消息; 所述切换请求消息包括: 所述 源基站连接的锚点标识;
所述判断模块, 还用于通过比较所述源基站连接的锚点标识, 与所述移 动锚点的标识, 判断进行全局路径切换或本地路径切换, 若所述源基站连接 的锚点标识, 与所述移动锚点的标识相同, 则进行本地路径切换, 若所述源 基站连接的锚点标识, 与所述移动锚点的标识不同, 则进行全局路径切换; 或者,
所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述判断模块, 还用于通过比较所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识,判断进行全局路径切换或本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相同, 则进行本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所 在基站簇的标识不同, 则进行全局路径切换。
根据第四方面的第二种可能实现的方式, 在第三种可能实现的方式中, 所述接收模块, 还用于接收所述移动锚点通过第一路径切换请求确认消息发 送的第一 NH参数; 所述第一 NH参数为所述移动锚点所生成的;
所述基站还包括: 确定模块, 用于根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
根据第四方面的第三种可能实现的方式, 在第四种可能实现的方式中, 所述第一 NH参数为所述移动锚点根据接入管理安全实体密钥及第一同歩输 入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管理安全实体密钥、 所述第一源基站密钥及所述第二 NH 参数为所述移动锚点接收的 MME发送的。
根据第四方面的第四种可能实现的方式, 在第五种可能实现的方式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接 入层计数器所确定的;
所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
根据第四方面的第三种可能实现的方式, 在第六种可能实现的方式中, 所述第一 NH参数为所述移动锚点根据第二源基站密钥及随机数所确定的参 数。
根据第四方面的第六种可能实现的方式, 在第七种可能实现的方式中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计 数器所确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
根据第四方面至第四方面的第七种可能实现的方式中任意一种, 在第八 种可能实现的方式中, 所述发送模块, 还用于若进行全局路径切换, 向 MME 发送第二路径切换请求消息, 以触发修改所述移动锚点和所述 SGW 间的用 户面路径。
第五方面, 本发明实施例还提供一种移动锚点, 包括: 接收机、 处理器 及发射机;
其中, 所述接收机, 用于接收目标基站发送的路径切换请求消息; 所述处理器, 用于若进行本地路径切换, 保持所述移动锚点和 SGW 间 的用户面路径不变, 并将所述移动锚点与源基站间的用户面路径切换到所述 目标基站。 根据第五方面, 在第五方面的第一种可能实现的方式中, 所述发射机, 还用于若进行全局路径切换, 向 MME发送所述路径切换请求消息, 以触发 修改所述移动锚点和所述 SGW间的用户面路径。
根据第五方面, 在第五方面的第一种可能实现的方式, 在第二种可能实 现的方式中, 所述处理器, 还用于判断进行全局路径切换或本地路径切换。
根据第五方面的第二种可能实现的方式, 在第三种可能实现的方式中, 所述处理器, 还用于通过比较切换次数与预设阈值的大小, 判断进行全局路 径切换还是本地路径切换, 若所述切换次数大于或等于所述预设阈值, 则进 行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径切换。
根据第五方面的第二种可能实现的方式, 在第四种可能实现的方式中, 所述路径切换请求消息包括: UE的接入标识; 所述 UE的接入标识为, 与所 述源基站连接的锚点设备为所述 UE分配的标识;
所述处理器, 还用于通过对所述 UE的接入标识进行检索, 判断进行全 局路径切换或本地路径切换, 若根据所述 UE 的接入标识, 无法检索到所述 UE, 则进行全局路径切换, 若根据所述 UE的接入标识, 检索到所述 UE, 则确定进行本地路径切换。
根据第五方面至第五方面的第四种可能实现的方式中任意一种, 在第五 种可能实现的方式中, 所述处理器, 还用于生成第一下一跳 NH参数;
所述发射机, 还用于通过路径切换请求确认消息将所述第一 NH参数发 送至所述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基站 使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其 他基站。
根据第五方面的第五种可能实现的方式, 在第六种可能实现的方式中, 所述处理器, 还用于根据接入管理安全实体密钥及第一同歩输入参数生成所 述第一 NH参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH 参数。
根据第五方面的第六种可能实现的方式, 在第七种可能实现的方式中, 所述接收机, 还用于接收 MME发送的所述接入管理安全实体密钥、 所述第 一源基站密钥、 所述第二 NH参数;
所述发射机, 还用于将所述第二 NH参数发送至所述源基站, 以使所述 源基站根据所述第二 NH参数确定所述目标基站使用的密钥。
根据第五方面的第六种或第七种可能实现的方式, 在第八种可能实现的 方式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的;
所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
根据第五方面的第五种可能实现的方式, 在第九种可能实现的方式中, 所述处理器, 还用于根据第二源基站密钥及随机数生成所述第一 NH参数。
根据第五方面的第九种可能实现的方式, 在第十种可能实现的方式中, 所述接收机, 还用于接收 MME所发送的所述第二源基站密钥; 其中, 所述 第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计数器 所确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
第六方面, 本发明实施例还提供一种基站, 所述基站为目标基站, 所述 基站包括: 接收机、 处理器及发射机;
其中, 所述处理器, 用于判断进行全局路径切换或本地路径切换; 所述发射机, 用于若进行本地路径切换, 向移动锚点发送第一路径切换 请求消息, 以使所述移动锚点保持所述移动锚点和 SGW 间的用户面路径不 变, 并使所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
根据第六方面, 在第六方面的第一种可能实现的方式中, 所述处理器, 还用于通过比较切换次数与预设阈值的大小, 判断进行全局路径切换或本地 路径切换, 若所述切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径切换。
根据第六方面, 在第六方面的第二种可能实现的方式中, 所述接收机, 用于在所述处理器判断进行全局路径切换或本地路径切换之前, 接收所述源 基站发送的切换请求消息; 所述切换请求消息包括: 所述源基站连接的锚点 标识;
所述处理器, 还用于通过比较所述源基站连接的锚点标识, 与所述移动 锚点的标识, 判断进行全局路径切换或本地路径切换, 若所述源基站连接的 锚点标识, 与所述移动锚点的标识相同, 则进行本地路径切换, 若所述源基 站连接的锚点标识, 与所述移动锚点的标识不同, 则进行全局路径切换; 或 者,
所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述处理器, 还用于通过比较所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识,判断进行全局路径切换或本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相同, 则进行本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所 在基站簇的标识不同, 则进行全局路径切换。
根据第六方面至第六方面的第二种可能实现的方式中任意一种, 在第三 种可能实现的方式中, 所述接收机, 还用于接收所述移动锚点通过第一路径 切换请求确认消息发送的第一 NH参数; 所述第一 NH参数为所述移动锚点 所生成的;
所述处理器, 还用于根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
根据第六方面的第三种可能实现的方式, 在第四种可能实现的方式中, 所述第一 NH参数为所述移动锚点根据接入管理安全实体密钥及第一同歩输 入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管理安全实体密钥、 所述第一源基站密钥及所述第二 NH 参数为所述移动锚点接收的 MME发送的。
根据第六方面的第四种可能实现的方式, 在第五种可能实现的方式中, 所述第一源基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接 入层计数器所确定的;
所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
根据第六方面的第三种可能实现的方式, 在第六中可能实现的方式中, 所述第一 NH参数为所述移动锚点根据第二源基站密钥及随机数所确定的参 数。
根据第六方面的第六种可能实现的方式, 在第七种可能实现的方式中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计 数器所确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
根据第六方面至第六方面的第七种可能实现的方式中任意一种, 在第八 种可能实现的方式中, 所述发射机, 还用于若进行全局路径切换, 向 MME 发送第二路径切换请求消息, 以触发修改所述移动锚点和所述 SGW 间的用 户面路径。
本发明实施例的路径切换方法、 移动锚点及基站, 通过移动锚点在进行 本地路径切换时进行与接入网设备间的用户面路径切换而无需进行与核心网 设备间的用户面路径切换, 从而避免与核心网设备间路径的多次切换, 且无 需采用双连接技术, 使得该方案不受限于该 UE特性及宏站覆盖等场景的限 制, 从而更好地降低核心网的信令负荷。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见地, 下 面描述中的附图是本发明的一些实施例, 对于本领域普通技术人员来讲, 在 不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。 图 1为本发明实施例一所提供的路径切换方法的流程图;
图 2为本发明实施例二所提供的路径切换方法的流程图;
图 3为本发明实施例三所提供的路径切换方法的流程图;
图 4为本发明实施例四所提供的路径切换方法的流程图;
图 5为本发明实施例五所提供的移动锚点的结构示意图;
图 6为本发明实施例六所提供的基站的结构示意图;
图 7为本发明实施例七所提供的移动锚点的结构示意图;
图 8为本发明实施例八所提供的基站的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例, 都属于本发明保护的范围。
实施例一
图 1为本发明实施例一所提供的路径切换方法的流程图。 本实施例的方 法适用于 UE在基站簇内移动进行路径切换的情况, 该基站簇由预设区域范 围的至少一个基站或者小区组成, 处于同一基站簇的基站或者小区连接到同 一移动锚点, 并通过该移动锚点连接到核心网设备移动管理实体 (Mobility Management Entity, 简称 MME)及服务网关(Serving Gateway, 简称 SGW。 该基站具体可以为演进型基站 (eNode B ) 、 微基站 (Pico ) 、 小站 (Small Cell)等。若该基站为小站,该基站簇则可以为小站簇(Small Cell Cluster) 。 该实施例的方法可以由移动锚点执行。 如图 1所示, 本实施例的方法包括如 下歩骤:
歩骤 101、 移动锚点接收目标基站发送的路径切换请求消息。
该移动锚点可以通过硬件和 /或软件的形成, 作为独立设备存在于基站簇 与核心网设备之间, 并将该基站簇与该核心网设备进行连接, 也可以作为独 立模块位于该基站簇内的任一基站或核心网设备内部。 该核心网设备例如可 以为移动管理实体 (Mobility Management Entity, 简称 MME) 及服务网关 (Serving Gateway,简称 SGW)中的任意一个。若该移动锚点作为独立设备, 则该基站簇可通过该移动锚点与该核心网设备连接, 具体可以是该移动锚点 通过 S1接口分别与该基站簇内的基站连接, 通过 S1-C接口与该核心网设备 中的 MME连接, 通过 S1-U接口与该核心网设备中的 SGW连接。 本发明实 施例以该移动锚点和基站簇内的基站间的接口, 及该移动锚点和核心网设备 间的接口均以 S1接口为例, 但还可以为其他按类型的接口, 本实施例不限定 为 S1接口。
该移动锚点可以为本地移动锚点, 可作为接入网设备与核心网设备之间 的用户数据的传输桥梁, 即基站与 SGW之间的用户数据传输桥梁, 实现对 本地用户数据的终结。 也就是说, 在具有该移动锚点的网络场景中, SGW发 送的下行用户数据需先到达该移动锚点, 由该移动锚点决定该下行用户数据 转发到该基站簇内的对应基站。 该移动锚点所终结的本地用户数据可以为该
UE在基站簇内移动时, 该移动锚点所接收到的任一用户数据。 同理, 对于上 行数据, 处于该基站簇的基站将上行数据发送至移动锚点, 再由该移动锚点 将上行数据发送至相应的 SGW。
因而, 若该 UE在该基站簇内的基站间移动时, 只需进行本地路径切换, 也就是与 UE连接的原有基站, 即源基站和该移动锚点之间的用户面路径切 换为与 UE连接的新基站, 也就是目标基站和该移动锚点之间的用户面路径, 而无需进行全局路径切换, 即无需切换该移动锚点与 SGW之间的用户面路 径, 从而减少核心网信令。 该本地路径指基站和移动锚点间的用户数据传输 通道; 该全局路径指的是基站和 SGW 间的用户数据通道, 在有移动锚点部 署的场景中, 该全局路径可包含两部分: 基站和移动锚点间的用户数据传输 通道、 及移动锚点和 SGW间的用户数据传输通道。
移动锚点至少连接一个或者多个完整的基站簇。 当该源基站和该目标基 站位于同一基站簇时, 则根据需要执行全局路径切换或者本地路径切换; 而 当该源基站和该目标基站位于不同的基站簇时, 则表明该 UE 的移动跨越了 该源基站所在基站簇的范围, 且移动至另一基站簇, 则需要执行全局路径切 换。
歩骤 102、 若该移动锚点进行本地路径切换, 则该移动锚点保持该移动 锚点和 SGW间的用户面路径不变。
该移动锚点维持该移动锚点和 SGW 间的用户面路径不变, 即无需执行 该移动锚点与核心网设备, 如 SGW 间的用户面路径切换, 也就说该移动锚 点对于为该 SGW所分配的用于传输下行数据的隧道标识和传输地址, 维持 不变。也就是说, 若该移动锚点进行本地路径切换, 该移动锚点与该 SGW之 间采用原有的隧道标识及传输地址进行用户面数据的传递。
歩骤 103、 该移动锚点将与源基站间的用户面路径切换到该目标基站。 具体地, 该移动锚点将与源基站间的用户面路径切换到该目标基站, 指 的是该移动锚点进行与基站间的用户面路径切换, 以用于该目标基站和该移 动锚点之间的用户面数据传递。 具体可以为该移动锚点设备重新为该目标基 站分配用于上行数据传输的隧道标识和传输地址, 并将为该目标基站分配的 隧道标识和传输地址与该 UE进行关联; 还可以为该移动锚点将为该源基站 分配的隧道标识和传输地址, 关联至该目标基站。 该移动锚点保存目标基站 发送的下行数据传输的隧道标识和传输地址, 并将从 SGW接收到的下行数 据根据该下行数据传输的隧道标识和传输地址发送至目标基站。
需要说明的是, 采用该实施例方案的路径切换方案进行路径切换完成之 后, 对于下行用户数据可以是由该 SGW传输至该移动锚点, 继而通过该移 动锚点传输至 UE对应的目标基站。 对应的, 对于上行用户数据, 可以是该 UE 通过与之连接的基站传输至该移动锚点, 继而由该移动锚点传输至该 SGW。
在长期演进 (Long Term Evolution, 简称 LTE) 及以上系统中, S1接口 有两种信令流程, UE 相关 (UE-associated)信令流程和非 UE 相关 (non-UE associated)信令流程。 由于在该实施例方案中, 该移动锚点可接收该目标基站 发送的路径切换请求消息, 根据该路径切换请求消息确定路径切换的类型, 继而根据对应类型的路径切换执行对应的切换流程, 也就是说, 该移动锚点 可以终结 UE相关信令流程, 如路径切换的信令流程。
该实施例方案由于可通过移动锚点在进行本地路径切换时, 进行与接入 网设备的用户面路径切换而无需进行与核心网设备的用户面路径切换, 避免 核心网路径切换的多次执行, 降低核心网的信令负荷。
同时, 由于该实施例方案无需采用双连接技术, 因而该 UE可以为具有 多发射机和多接收机的 UE, 也可以为单发射机和单接收机的 UE, 且该 UE 所处的区域, 可以有宏站的覆盖也可以无宏站的覆盖。 也就是说, 该实施例 方案不受限于该 UE特性及宏站的覆盖范围, 因而, 该实施例方案不受场景 的限制, 可更好地降低核心网信令负荷。
本实施例方案, 通过移动锚点在进行本地路径切换时进行与接入网设备 间的用户面路径切换而无需进行与核心网设备间的用户面路径切换, 从而避 免核心网路径切换的多次执行, 且无需采用双连接技术, 使得该方案不受限 于该 UE特性及宏站覆盖等场景的限制, 从而更好地降低核心网的信令负荷。
实施例二
在上述实施例方案的基础上,本实施例方案还提供了一种路径切换方法。 图 2为本发明实施例二所提供的路径切换方法的流程图。 如图 2所示, 该方 法还包括: 歩骤 201、若该移动锚点进行全局路径切换,该移动锚点向 MME发送该 路径切换请求消息, 以触发修改该移动锚点和该 SGW间的用户面路径。
具体地, 若该移动锚点进行全局路径切换, 也就是说, 不仅要进行基站 与移动锚点的用户面路径切换, 还要进行核心网设备与该移动锚点的路径切 换。 若该移动锚点设备确定进行全局路径切换, 向 MME发送该路径切换请 求消息, 以指示该 MME触发执行核心网设备, 如 SGW与该移动锚点间的用 户面路径切换。 该路径切换请求消息可包括: 该移动锚点分配的用于传输下 行数据隧道标识及传输地址。该 MME触发执行该 SGW与该移动锚点间的用 户面路径切换,具体可以是该 MME通过向该 SGW发送的承载修改请求消息, 将该移动锚点分配的用于传输下行数据隧道标识及传输地址, 发送至该 SGW, 以触发该 SGW进行其与该移动锚点设备间的路径切换。该 SGW进行 与该移动锚点设备间的路径切换, 可以是将该移动锚点所分配的用于传输下 行数据隧道标识及传输地址, 与通过该移动锚点设备与该 UE相关的业务进 行承载关联并为该移动锚点分配用于上行数据的隧道标识和传输地址。 该 SGW将为该移动锚点分配的用于上行数据的隧道标识和传输地址通过承载 修改响应消息, 发送至该移动锚点, 从而完成该 SGW 与该移动锚点之间传 输上下行数据的路径切换, 即完成该移动锚点与该 SGW之间的用户面路径 切换。
需要说明的是,移动锚点还可以是在该 MME向该 SGW发送承载修改请 求消息之前, 重新为该 SGW分配该用于传输下行数据的隧道标识及传输地 址等, 并通过该承载修改请求消息发送至该 SGW。
该移动锚点还需将与该源基站间的用户面路径切换到该目标基站。 该移 动锚点将与该源基站间的用户面路径切换到该目标基站,其具体的实现过程, 与上述实施例类似, 在此不再赘述。
该方案在如上所述基础上, 该方法还包括:
歩骤 201a、 该移动锚点判断进行全局路径切换或本地路径切换。
具体地, 该移动锚点可通过判断该目标基站与该移动锚点是否处于同一 基站簇内进行判断, 可以根据在同一基站簇内路径切换的次数判断, 还可以 是根据该路径切换请求消息中携带的用户面路径的切换类型指示消息进行确 定, 从而决定进行全局路径切换或本地路径切换。 需要说明的是, 该歩骤 201a可以是在上述歩骤 201和 /或上述歩骤 102 之前执行。
本实施例方案在上述方案的基础上, 可使得该移动锚点可分别根据不同 的路径切换类型执行对应的路径切换, 仅在确定进行全局路径切换时触发该 移动锚点与核心网设备的路径切换, 从而减少核心网路径切换次数, 减轻核 心网的信令负荷。
该实施例方案还提供两种路径切换类型的判定方法对上述实施例方案进 行进一歩地解释说明。
可选的, 在该方案一中, 上述实施例方案的歩骤 201a中该移动锚点判断 进行全局路径切换或本地路径切换, 具体包括:
该移动锚点通过比较切换次数与预设阈值的大小, 判断进行全局路径切 换还是本地路径切换;
若该切换次数大于或等于该预设阈值, 则该移动锚点确定进行全局路径 切换;
若该切换次数小于该预设阈值, 则该移动锚点确定进行本地路径切换。 具体地, 该切换次数可以为该 UE在该基站簇内移动, 进行本地路径切 换的次数; 该切换次数也可为该 UE在该基站簇或者移动锚点对应的区域范 围内发生基站间切换的次数。 具体可以是, 移动锚点记录并保存上述切换次 数, 初始值可以为 0, 每进行一次路径切换则将切换次数累计加 1 ; 或者 UE 每发生一次基站间切换则将切换次数累计加 1。若该 UE在该基站簇内的切换 次数, 大于或等于该预设阈值, 则该移动锚点确定进行全局路径切换, 并将 该切换次数复位为 0; 若该 UE在该基站簇内的切换次数, 小于该预设阈值, 则该移动锚点确定进行本地路径切换, 切换次数累计加 1。
该方案二在如上所述方案的基础上, 其中该路径切换请求消息包括: UE 的接入标识; 该 UE的接入标识为,与该源基站连接的锚点设备为该 UE分配 的标识。
具体地,该 UE的接入标识可以是该 UE的接入点的标识(UE Access Point Identity, 简称 UE AP ID) 。 该 UE的接入标识可以为该与该源基站连接的锚 点设备为该 UE分配的逻辑标识。
可选的,上述方案歩骤 201a中该移动锚点判断进行全局路径切换或本地 路径切换, 还可以是包括:
该移动锚点通过对该 UE 的接入标识进行检索, 判断进行全局路径切换 还是本地路径切换;
若该移动锚点根据该 UE的接入标识, 无法检索到该 UE, 则该移动锚点 确定进行全局路径切换;
若该移动锚点设备根据该 UE的接入标识, 检索到该 UE, 则该移动锚点 确定进行本地路径切换。
该移动锚点通过对该 UE 的接入标识进行检索, 判断进行全局路径切换 还是本地路径切换, 实际是通过该源基站与该目标基站是否位于同一基站簇 内, 判断进行全局路径切换或本地路径切换。 若该移动锚点根据该 UE 的接 入标识可以检索到该 UE,则表明与该源基站连接的锚点设备与该移动锚点为 同一设备, 即该源基站与该目标基站均连接至同一移动锚点, 也就是说该源 基站与该目标基站位于同一基站簇内。 在本实施例方案中, 可以是, 若该源 基站位于同一基站簇内, 则该移动锚点确定进行本地路径切换消息, 若位于 不同的基站簇内, 则该移动锚点设备确定进行全局路径切换。
需要说明的是,本实施例方案中歩骤 201a中移动锚点确定进行全局路径 切换还是本地路径切换, 还可以通过其他的方式实现, 如根据该路径切换请 求消息中的携带的切换类型标识或是指示消息来确定, 本发明实施例不以此 作为限制。
本实施例方案在上述方案的基础上, 提供基于该移动锚点的全局路径切 换的具体方案, 同时还通过不同的路径切换类型的判断方案对上述实施例进 行优化说明, 从而可保证该移动锚点可根据实际情况选择性地触发全局路径 切换, 从而可减少该核心网的切换次数, 减轻整个通信系统总体的核心网信 令负荷。
实施例三
该实施例在上述实施例所述方案的基础上, 还提供一种路径切换方案。 该实施例方案中的移动锚点可以为上述实施例中任一所述的移动锚点。 图 3 为本发明实施例三所提供的路径切换方法的流程图。 如图 3所示, 该方法还 包括:
歩骤 301、 该移动锚点生成第一下一跳 NH参数。 具体地, 该移动锚点生成该第一下一跳(Next Hop, 简称 NH)参数可以 是在执行上述歩骤 102、 歩骤 103时, 也可以是在歩骤 103之后, 本实施例 不以此为限制。
歩骤 302、该移动锚点通过路径切换请求确认消息将该第一 NH参数发送 至该目标基站, 以使该目标基站根据该第一 NH参数确定下一基站使用的密 钥。
其中, 该下一基站为除该源基站及该目标基站之外的其他基站。
具体地, 该路径切换请求确认消息具体可以为 Path Switch Request Acknowledge消息。 该目标基站根据该第一 NH参数确定下一基站使用的密 钥, 具体可以为该目标基站根据该第一 NH参数, 采用密钥派生函数 (Key Derivation Function, 简称 KDF) 获取。 该下一基站使用的密钥, 可以为衍生 完整性保护或 /和数据加密密钥所使用的密钥。 该目标基站根据该第一 NH参 数确定该下一基站使用的密钥, gp, 该目标基站采用安全密钥的纵向衍生进 行获得, 从而保证伪装基站对切换后合法基站使用密钥的安全性。
需要说明的是, 该目标基站根据该第一 NH参数确定该下一基站使用的 密钥,可以为该目标基站根据该第一 NH参数、物理层小区标识(Physical-layer Cell Identity, 简称 PCI) 及演进的绝对无线频率信道号 (the Evolution of the Absolute Radio Frequency Channel Number, 简称 EARFCN) 等参数采用 KDF 进行获取。 具体地, 该 EARFCN可以为下行的无线频点号。
由于该目标基站确定该下一基站使用的密钥所使用的参数,即该第一 NH 参数为该移动锚点生成的,那么该第一 NH参数对于该源基站来说是未知的, 因而, 即便该源基站所使用的密钥被攻击者所破解, 或该源基站为伪基站, 攻击者也无法获知该第一 NH参数及该下一基站使用的密钥中。 也就是说, 本实施例方案所提供的该下一基站使用的密钥的衍生方案, 难以被攻击者所 获知。
本实施例方案在上述任一所述方案降低核心网信令负荷的基础上, 由于 确定下一基站使用的密钥所采用该第一 NH参数为该移动锚点所生成的, 则 该第一 NH参数对于该 UE的接入网侧, 特别是该源基站来说是未知, 从而 使得该下一基站使用的密钥难以被攻击者所获知, 从而保证该 UE与切换后 基站间的前向安全问题, 更好地保证 UE与基站间的空口的安全通信。 本实施例方案在上述实施例方案的基础上,可选的,上述方案中歩骤 301 该移动锚点设备生成第一下一跳 NH参数具体包括:
该移动锚点根据接入管理安全实体密钥及第一同歩输入参数生成该第一 NH参数。
具体地, 该接入管理安全实体密钥 ( Key Access Security Management
Entity, 简称 Kasme ) 具体可以为认证与密钥协商 (Authentication and Key Agreement,简称 AKA) 过程中由 UE及归属服务器 (Home Subscriber Server, 简称 HSS )根据加密密钥(Cipher Key,简称 CK)和完整性密钥(Integrity Key, 简称 IK) 生成的密钥。
该第一同歩输入(Synchronous-Input, 简称 SYNC-input)参数可以为该移 动锚点自身生成的, 也可以为其他网元设备发送至该移动锚点的。 该 SYNC-input参数可包括: 第一源基站密钥, 及该第二 NH参数。
该第一源基站密钥可以为该源基站的初始密钥, 通过 KeNB表示。 该第 二 NH参数可以为该源基站在该基站簇内的初始 NH参数。
进一歩地, 在上述方案歩骤 101 中该移动锚点设备接收该目标基站发送 的该路径切换请求消息之前, 该方法还包括:
该移动锚点设备接收 MME发送的该接入管理安全实体密钥、 该第一源 基站密钥、 该第二 NH参数。
其中,该1^^可以为 MME接收该 HSS通过 S6a接口所发送的。该第一 源基站密钥及该第二 NH参数为该 MME自身生成的参数。
该移动锚点将该第二 NH参数发送至该源基站, 以使该源基站根据该第 二 NH参数确定该目标基站使用的密钥。
具体地, 该移动锚点可将该接收到的该 Kasme、 该第一源基站密钥, 及该 第二 NH参数进行保存, 并将该些参数均与该 UE相应标识进行关联。 当该 移动锚点设备确定进行本地路径切换后, 将与该源基站间的用户面路径切换 到该目标基站的过程中或之后, 根据该些参数重新生成该第一 NH参数, 并 将该第二 NH参数发送至该源基站。
该目标基站使用的密钥可以为该移动锚点将与该源基站间的用户面路径 切换至该目标基站之后, 该目标基站与该 UE进行通信所使用的密钥, 可表 示为 KeNB*。 可选的, 上述方案中, 该移动锚点接收该 MME发送的该接入管理安全 实体密钥、 该第一源基站密钥、 该第二 NH参数, 具体包括:
该移动锚点接收该 MME通过初始上下文设置请求消息发送的该接入管 理安全实体密钥、 该第一源基站密钥、 该第二 NH参数。
具体地, 该初始上下行设置请求消息可以为 Initial Context Setup Request 消息, 可为该移动锚点接收该 MME通过 S1-C接口所接收的。
对应的, 如上所述的该移动锚点将该第二 NH参数发送至该源基站, 可 包括:
该移动锚点将该第二 NH参数携带在该初始上下文设置请求消息中, 并 通过 S1接口将该初始上下文设置请求消息转发至该源基站。
如上所述方案中, 该第一源基站密钥为该 MME根据该接入管理安全实 体密钥、 及非接入层计数器所确定的。
该第二 NH参数为该 MME根据该接入管理安全实密钥, 第二同歩输入 参数所确定的。
具体地, 该非接入层计数器可以为非接入层消息对应的计数器, 即该接 入层计数器的数值可以该 MME发送非接入层消息的条数。
该第二同歩输入参数可以为初始的同歩输入参数, 初始的同歩输入参数 可以为全 0或者全 1或者约定值。
该实施例方案, 通过该移动锚点根据该接入管理安全实体密钥及该第一 同歩输入参数生成该第一 NH参数的方案进行具体解释说明, 从而更好地保 证该移动锚点所生成的该第一 NH参数的安全性, 保证 UE与基站间的前向 安全问题。
在上述实施例方案的基础上, 可选的, 该方法还可包括:
该移动锚点通过递增方式生成第一下一跳链计数器 (NH Chaining Counter, 简称 NCC) 。
其中, 该第一 NCC的数值与该第一 NH参数一一对应。 该移动锚点可以 是在生成该第一 NH参数时, 也就是上述歩骤 301时, 执行生成该第一 NCC 的歩骤, 也可以是在生成该第一 NH参数之后执行生成该第一 NCC的歩骤, 从而获得该第一 NH参数对应的该第一 NCC。 该第一 NCC的数值表示该移 动锚点更新 NCC的次数, 由于该 UE每进行一次路径切换均需更新 NCC,本 实施例方案还可通过该第一 NCC表示该 UE在该基站簇内的切换次数。
该移动锚点通过该路径切换请求确认消息将该第一 NCC 发送至该目标 基站,以使该目标基站将该第一 NCC发送至 UE,并使该 UE根据该第一 NCC 确定该第一 NH参数, 继而根据该第一 NH参数确定该下一基站使用的密钥。
该移动锚点可以是通过上述歩骤 302中的路径切换请求确认消息中携带 该第一 NH参数及该第一 NCC参数, 继而发送至该目标基站。 由于考虑传输 安全的问题, 该第一 NH参数无法在 UE与基站间进行传输, 因而可通过该 目标基站将该第一 NCC发送至该 UE即可。 该 UE在接收到该第一 NCC之 后,可根据该第一 NCC与该第一 NH参数的对应关系,确定该第一 NH参数, 继而根据该第一 NH参数确定该下一基站使用的密钥。结合上述实施例方案, 该目标基站及 UE侧均可根据该第一 NH参数确定该下一基站使用的密钥。 需要说明的是, 上述方案中, 该目标基站还需在下次进行路径切换之前, 将 其确定该下一基站使用的密钥发送该待切换的基站, 保证该 UE再次进行路 径切换后, UE与基站均具有相同的密钥, 从而更好地保证该 UE与基站间通 信安全。
进一歩地, 上述该移动锚点通过递增方式生成第一下一跳链计数器 NCC 具体包括:
该移动锚点对第二 NCC进行加一操作, 生成该第一 NCC。
对应的, 上述歩骤 101 中该移动锚点接收该目标基站发送的该路径切换 请求消息之前, 还包括:
该移动锚点接收该 MME通过该初始上下文设置请求消息发送的该第二 NCC。
具体地, 该移动锚点可以是接收该 MME采用上述初始上下文设置请求 消息发送该接入管理安全实体密钥、该第一源基站密钥及该第二 NH参数时, 发送的该第二 NCC。
该实施例在上述方案的基础上, 具体还通过更新 NCC, 并将更新后的 NCC发送至该 UE, 避免密钥参数的空口传输, 从而更好地保证该 UE与切 换后基站间的通信安全。
可选的,上述方案中歩骤 301该移动锚点生成该第一 NH参数具体包括: 该移动锚点根据第二源基站密钥及随机数生成该第一 NH参数。 随机数的非预见性可使得该移动锚点根据该第二源基站密钥及该随机数 所生成的该第一 NH参数具有不确定性, 难以被伪基站所获知, 可更好地保 证该 UE与基站间的前向安全问题。
进一歩地, 在上述方案歩骤 101 中该移动锚点接收该目标基站发送的该 路径切换请求消息之前, 该方法还包括:
该移动锚点接收该 MME所发送的该第二源基站密钥。
可选的, 上述该第二源基站密钥可以为该 MME根据接入管理安全实体 密钥及非接入层计数器所确定的; 或者
该第二源基站密钥还可以为 MME根据该接入管理安全实体密钥及该移 动锚点设备的标识所确定的。
需要说明的是, 本实施例方案中的接入管理安全实体密钥及非接入层计 数器可如上述实施例三所述, 在此不再赘述。
本实施例方案, 具体通过该移动锚点根据该第二源基站密钥及该随机数 生成该第一 NH参数的方案, 及该第二源基站密钥具体如何获得及该些参数 本身进行具体解释说明, 可提高该第一 NH参数的不确定性, 从而更好地保 证基于该第一 NH所确定的该下一基站使用的密钥的安全性, 保证 UE与基 站间的前向安全问题。
实施例四
本实施例还提供一种路径切换方法。 该方法可以由目标基站来执行。 图 4为本发明实施例四所提供的路径切换方法的流程图。 如图 4所示, 该方法 具体包括如下:
歩骤 401、 目标基站判断进行全局路径切换或本地路径切换。
歩骤 402、 若该目标基站进行本地路径切换, 该目标基站向移动锚点发 送第一路径切换请求消息, 以使该移动锚点保持该移动锚点设备和 SGW 间 的用户面路径不变, 并使该移动锚点将与源基站间的用户面路径切换到该目 标基站。
该实施例方案与上述实施例一所提供的路径切换方法的区别在于, 该方 案中可以通过该目标基站判断进行路径切换的类型, 即全局路径切换或本地 路径, 若进行本地路径切换, 则向该移动锚点发送第一路径切换请求消息。 该第一路径切换请求消息中可以包含本地路径切换对应的指示消息。 该移动 锚点在接收该第一路径切换请求消息后, 可以无需再次判断进行路径切换的 类型, 执行触发进行本地路径切换的方案。 该移动锚点进行本地路径切换的 具体实现过程可以与上述实施例一中类似, 在此不再赘述。
该实施例方案具体通过该目标基站判断进行路径切换的类型, 从而在确 定进行本地路径切换后, 通过向该移动锚点发送第一路径切换请求消息, 该 消息中可包含本地路径切换指示, 以触发该移动锚点进行与接入网设备间的 用户面路径切换而无需进行与核心网设备间的用户面路径切换, 从而避免核 心网路径切换的多次执行, 且无需采用双连接技术, 使得该方案不受限于该 UE特性及宏站覆盖等场景的限制, 从而更好地降低核心网的信令负荷。
可选的, 上述歩骤 401 中该目标基站判断进行全局路径切换或本地路径 切换具体可以为:
该目标基站通过比较切换次数与预设阈值的大小, 判断进行全局路径切 换或本地路径切换;
若该切换次数大于或等于该预设阈值, 则该目标基站确定进行全局路径 切换;
若该切换次数小于该预设阈值, 则该目标基站确定进行本地路径切换。 具体地, 该目标基站根据切换次数与预设阈值, 判断进行全局路径切换 还是本地路径切换的具体实现过程及解释说明, 与上述实施例中该移动锚点 根据切换次数及预设阈值进行判断的方案类似, 在此不再赘述, 其区别仅在 执行主体的不同。
进一歩地, 上述方案歩骤 401中该目标基站判断进行全局路径切换或本 地路径切换之前, 还可以包括:
该目标基站接收该源基站发送的切换请求消息; 该切换请求消息包括: 所述源基站连接的锚点标识。
具体地, 该切换请求消息具体可以为 Handover Request消息。
可选的, 上述方案歩骤 401该目标基站判断进行全局路径切换或本地路 径切换, 还可以包括:
该目标基站通过比较该源基站连接的锚点标识, 与该移动锚点的标识, 判断进行全局路径切换或本地路径切换;
若该源基站连接的锚点标识, 与该移动锚点的标识相同, 该目标基站确 定进行本地路径切换;
若该源基站连接的锚点标识, 与该移动锚点的标识不同, 所述目标基站 确定进行全局路径切换。
具体地, 本实施例方案通过比较该源基站连接的锚点标识与该移动锚点 的标识是否相同, 确定该源基站与该目标基站是否位于连接与同一个锚点设 备, 继而确定该源基站与该目标基站是否位于同一基站簇内。 若该源基站连 接的锚点标识, 与该移动锚点的标识相同, 则该目标基站与该源基站位于同 一基站簇内, 则该目标基站确定进行本地路径切换。 若该源基站连接的锚点 标识, 与所述移动锚点的标识不同, 则该目标基站与该源基站位于不同的基 站簇内, 则该目标基站确定进行全局路径切换。
可选的, 上述切换请求消息可以包括: 该源基站所在基站簇的标识; 对应的, 上述方案歩骤 401 中该目标基站判断进行全局路径切换或本地 路径切换, 具体可包括:
该目标基站通过比较该源基站所在基站簇的标识, 与该目标基站所在基 站簇的标识, 判断进行全局路径切换或本地路径切换;
若该源基站所在基站簇的标识, 与该目标基站所在基站簇的标识相同, 该目标基站确定进行本地路径切换;
若该源基站所在基站簇的标识, 与该目标基站所在基站簇的标识不同, 该目标基站确定进行全局路径切换。
具体地, 该源基站所在基站簇的标识可以是通过该源基站所在区域的位 置信息表示, 该移动锚点所连接的基站簇的标识可以是通过该移动锚点所在 区域的位置信息表示。 若该源基站所在基站簇的标识, 与该目标基站所在基 站簇的标识相同, 则表明该目标基站与该源基站位于同一基站簇内; 若该源 基站所在基站簇的标识, 与该目标基站所在基站簇的标识不同, 则表明该目 标基站与该源基站位于不同的基站簇内。
本实施例方案还通过多种路径切换类型的判断方法, 提供了上述实施例 方案的多种可实现方式, 从而使得本实施例提供的路径切换方案其适用性更 广。
在上述实施例方案的基础上, 该实施例方案, 可选的, 还包括: 歩骤 403、 该目标基站接收该移动锚点通过第一路径切换请求确认消息 发送的第一 NH参数; 该第一 NH参数为该移动锚点所生成的。
歩骤 404、该目标基站根据该第一 NH参数确定下一基站使用的密钥;其 中, 该下一基站为除该源基站及该目标基站之外的其他基站。
可选的, 上述方案中, 该第一 NH参数可以为该移动锚点根据接入管理 安全实体密钥及第一同歩输入参数所获得的参数;该第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 该接入管理安全实体密钥、 该第一源基站 密钥及该第二 NH参数为该移动锚点接收的 MME发送的。
进一歩地, 该接入管理安全实体密钥、 该第一源基站密钥及该第二 NH 参数为该移动锚点接收到的该 MME通过初始上下文设置请求消息发送的。
上述方案中的该第一源基站密钥为该 MME根据该接入管理安全实体密 钥、 及非接入层计数器所确定的;
该第二 NH参数为该 MME根据该接入管理安全实体密钥, 第二同歩输 入参数所确定的。
可选的, 上述方案所述的方法还包括:
该目标基站接收该移动锚点通过该第一路径切换请求确认消息发送的第 一 NCC; 该第一 NCC为该移动锚点通过递增方式所生成的。
该目标基站将该第一 NCC发送至该 UE,以使该 UE根据该第一 NCC确 定该第一 NH参数, 根据该第一 NH参数确定该下一基站使用的密钥。
需要说明的是, 该目标基站接收该第一 NCC的歩骤可以与上述歩骤 403 可以同时执行, 该目标基站将该第一 NCC发送至该 UE的歩骤可以与上述歩 骤 404同时执行或先后执行, 本申请不以此作为限制。
可选的, 上述方案中的该第一 NCC为该移动锚点对第二 NCC进行加一 操作, 所生成的;
该第二 NCC可以为该移动锚点接收到的该 MME通过该初始上下文设置 请求消息发送的。
可替代地, 上述方案中的该第一 NH参数还可以为该移动锚点根据第二 源基站密钥及随机数所确定的参数。
在上述方案的基础上, 该第二源基站密钥可以为该 MME根据接入管理 安全实体密钥及非接入层计数器所确定的; 或者
该第二源基站密钥为该 MME根据该接入管理安全实体密钥及该移动锚 点的标识所确定的。
本实施例方案, 目标基站可根据移动锚点所生成的不同格式的 NH参数, 获得下一基站使用的密钥, 由于该 NH参数对于伪基站的不可预见性, 保证 下一基站使用密钥的安全, 从而保证 UE与基站间的前向安全问题。
在本实施例如上所述方案的基础上, 进一歩地, 该方法还包括: 歩骤 405、若该目标基站进行全局路径切换,该目标基站向 MME发送第 二路径切换请求消息, 以触发修改该移动锚点与该 SGW间的用户面路径。
可选的, 该方案还可包括:
该目标基站接收该 MME通过第二路径切换请求确认消息发送的第三 NH参数; 该第三 NH参数为该 MME所生成的。
该目标基站根据该第三 NH参数确定下一基站使用的密钥; 其中, 该下 一基站为除该源基站及该目标基站之外的其他基站。
需要说明的是, 该第三 NH参数与上述实施例方案中移动锚点所生成的 第一 NH参数类似, 可以为该 MME根据接入管理安全实体密钥及第一同歩 输入参数生成, 也可以是根据第二源基站密钥与随机数生成。 其中, 接入管 理安全实体密钥、 第一同歩输入参数生成、 第二源基站密钥及随机数均可以 与上述实施例类似, 在此不再赘述。
本实施例方案通过该目标基站判断进行路径切换的类型, 从而在进行本 地路径切换情况下, 通过向该移动锚点发送第一路径切换请求消息以触发该 移动锚点进行与接入网设备间的用户面路径切换而无需进行与核心网设备间 的用户面路径切换, 而在进行全局路径切换的情况下, 通过向该移动锚点发 送第二路径切换请求消息, 触发进行全局路径切换的切换。 该实施例方案可 有选择性的进行全局路径切换, 从而避免核心网路径切换的多次执行, 且无 需采用双连接技术, 使得该方案不受限于该 UE特性及宏站覆盖等场景的限 制, 从而更好地降低核心网的信令负荷。
实施例五
本发明实施例五还提供一种移动锚点。 图 5为本发明实施例五所提供的 移动锚点的结构示意图。 如图 5所示, 移动锚点 500, 包括:
接收模块 501, 用于接收目标基站发送的路径切换请求消息。
保持模块 502, 用于若进行本地路径切换, 保持移动锚点 500和 SGW间 的用户面路径不变。
切换模块 503, 用于将移动锚点 500与源基站间的用户面路径切换到该 目标基站。
进一歩地, 上述方案中, 移动锚点 500, 还包括:
发送模块, 用于若进行全局路径切换, 向 MME发送该路径切换请求消 息, 以触发修改移动锚点 500和该 SGW间的用户面路径。
可选的, 移动锚点 500, 还可包括:
判断模块, 用于判断进行全局路径切换或本地路径切换。
在如上所述实施例方案的基础上, 进一歩地, 该判断模块, 具体用于通 过比较切换次数与预设阈值的大小, 判断进行全局路径切换还是本地路径切 换, 若该切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若该切 换次数小于该预设阈值, 则进行本地路径切换。
进一歩地, 上述方案中的该路径切换请求消息包括: UE的接入标识; 该 UE的接入标识为, 与该源基站连接的锚点设备为该 UE分配的标识。
可替代地, 该判断模块, 还用于通过对该 UE的接入标识进行检索, 判 断进行全局路径切换或本地路径切换, 若根据该 UE的接入标识无法检索到 该 UE, 则进行全局路径切换, 若根据该 UE的接入标识检索到该 UE, 则进 行本地路径切换。
在如上所述实施例方案的基础上, 进一歩地, 移动锚点 500, 还包括: 生成模块, 用于生成第一 NH参数。
该发送模块, 还用于通过路径切换请求确认消息将该第一 NH参数发送 至该目标基站, 以使该目标基站根据该第一 NH参数确定下一基站使用的密 钥; 其中, 该下一基站为除该源基站及该目标基站之外的其他基站。
进一歩地, 该生成模块, 还用于根据接入管理安全实体密钥及第一同歩 输入参数生成该第一 NH参数; 其中, 该第一同歩输入参数包括: 第一源基 站密钥、 第二 NH参数。
可选的, 上述方案中, 接收模块 501, 还用于接收该 MME发送的该接入 管理安全实体密钥、 该第一源基站密钥、 该第二 NH参数。
该发送模块, 还用于将该第二 NH参数发送至该源基站, 以使该源基站 根据该第二 NH参数确定该目标基站使用的密钥。 在如上所述实施例方案中,进一歩地,该第一源基站密钥可以为该 MME 根据该接入管理安全实体密钥、 及非接入层计数器所确定的。
该第二 NH参数可以为该 MME根据该接入管理安全实密钥, 第二同歩 输入参数所确定的。
可替代地, 如上所述实施例方案中, 该生成模块, 还用于根据第二源基 站密钥及随机数生成该第一 NH参数。
可选的,接收模块 501,还用于接收该 MME所发送的该第二源基站密钥; 其中, 该第二源基站密钥为该 MME根据接入管理安全实体密钥及非接入层 计数器所确定的; 或者
该第二源基站密钥为该 MME根据该接入管理安全实体密钥及该移动锚 点的标识所确定的。
本实施例方案所提供的移动锚点可实施上述任一实施例所提供的移动锚 点执行的路径切换方法, 具体的实现过程及有益效果与上述实施例类似, 在 此不再赘述。
实施例六
本发明实施例还提供一种基站。 图 6为本发明实施例六所提供的基站的 结构示意图。 如图 6所示, 基站 600, 包括:
判断模块 601, 用于判断进行全局路径切换或本地路径切换。
发送模块 602, 用于若进行本地路径切换, 向移动锚点发送第一路径切 换请求消息, 以使该移动锚点保持该移动锚点和 SGW间的用户面路径不变, 并使该移动锚点将与源基站间的用户面路径切换到目标基站。其中,基站 600 为该目标基站。
进一歩地, 上述方案中, 判断模块 601, 还用于通过比较切换次数与预 设阈值的大小, 判断进行全局路径切换或本地路径切换, 若该切换次数大于 或等于该预设阈值, 则进行全局路径切换, 若该切换次数小于该预设阈值, 则进行本地路径切换。
可选的, 上述方案中, 基站 600, 还包括:
接收模块, 用于在判断模块 601判断进行全局路径切换或本地路径切换 之前, 接收该源基站发送的切换请求消息; 该切换请求消息包括: 该源基站 连接的锚点标识。 可替代地, 上述方案中, 判断模块 601, 还用于通过比较该源基站连接 的锚点标识, 与该移动锚点的标识, 判断进行全局路径切换或本地路径切换, 若该源基站连接的锚点标识, 与该移动锚点的标识相同, 则进行本地路径切 换, 若该源基站连接的锚点标识, 与该移动锚点的标识不同, 则进行全局路 径切换。 或者,
上述方案中, 该切换请求消息包括: 该源基站所在基站簇的标识。
对应的, 判断模块 601, 还用于通过比较该源基站所在基站簇的标识, 与该目标基站所在基站簇的标识, 判断进行全局路径切换或本地路径切换, 若该源基站所在基站簇的标识, 与该目标基站所在基站簇的标识相同, 则进 行本地路径切换, 若该源基站所在基站簇的标识, 与该目标基站所在基站簇 的标识不同, 则进行全局路径切换。
进一歩地, 该接收模块, 还用于接收该移动锚点通过第一路径切换请求 确认消息发送的第一 NH参数; 该第一 NH参数可以为该移动锚点所生成的。
基站 600还包括:
确定模块, 用于根据该第一 NH参数确定下一基站使用的密钥。
其中, 该下一基站可以为除该源基站及该目标基站之外的其他基站。 可选的, 该第一 NH参数可以为该移动锚点根据接入管理安全实体密钥 及第一同歩输入参数所获得的参数。 其中, 该第一同歩输入参数包括: 第一 源基站密钥、 第二 NH参数; 该接入管理安全实体密钥、 该第一源基站密钥 及所述第二 NH参数为该移动锚点接收的 MME发送的。
可选的, 该第一源基站密钥可以为该 MME根据该接入管理安全实体密 钥、 及非接入层计数器所确定的。
该第二 NH参数可以为 MME根据该接入管理安全实体密钥, 第二同歩 输入参数所确定的。
在如上实施例所述方案的基础上, 可替代地, 该第一 NH参数可以为该 移动锚点根据第二源基站密钥及随机数所确定的参数。
进一歩地, 该第二源基站密钥可以为该 MME根据接入管理安全实体密 钥及非接入层计数器所确定的; 或者
该第二源基站密钥可以为该 MME根据该接入管理安全实体密钥及该移 动锚点的标识所确定的。 进一歩地, 发送模块 602, 还用于若进行全局路径切换, 向 MME发送第 二路径切换请求消息, 以触发修改该移动锚点和该 SGW间的用户面路径。
本实施例所提供的基站可实施上述实施例所提供的基站执行的路径切换 方法, 其具体实现过程及有益效果与上述实施例类似, 再次不再赘述。
实施例七
本发明实施例七还提供一种移动锚点。 图 7为本发明实施例七所提供的 移动锚点的结构示意图。
如图 7所示, 移动锚点 700, 包括: 接收机 701、 处理器 702及发射机
703。
其中, 接收机 701, 用于接收目标基站发送的路径切换请求消息。
处理器 702, 用于若进行本地路径切换, 保持该移动锚点和 SGW间的用 户面路径不变,并将该移动锚点与源基站间的用户面路径切换到该目标基站。
进一歩地, 上述发射机 703, 还用于若进行全局路径切换, 向 MME发送 该路径切换请求消息, 以触发修改该移动锚点和该 SGW间的用户面路径。
可选的, 上述方案中, 处理器 702, 还用于判断进行全局路径切换或本 地路径切换。
进一歩地, 如上所述方案中的处理器 702, 还用于通过比较切换次数与 预设阈值的大小, 判断进行全局路径切换还是本地路径切换, 若该切换次数 大于或等于该预设阈值, 则进行全局路径切换, 若该切换次数小于该预设阈 值, 则进行本地路径切换。
可选的, 该路径切换请求消息包括: UE的接入标识; 该 UE的接入标识 为, 与该源基站连接的锚点设备为该 UE分配的标识。
可替代地, 处理器 702, 还用于通过对该 UE的接入标识进行检索, 判断 进行全局路径切换或本地路径切换, 若根据该 UE的接入标识, 无法检索到 该 UE, 则进行全局路径切换, 若根据该 UE的接入标识, 检索到该 UE, 则 进行本地路径切换。
在上述实施例方案的基础上, 进一歩地, 处理器 702, 还用于生成第一 下一跳 NH参数。
发射机 703,还用于通过路径切换请求确认消息将该第一 NH参数发送至 该目标基站, 以使该目标基站根据该第一 NH参数确定下一基站使用的密钥。 其中, 该下一基站为除该源基站及该目标基站之外的其他基站。
可选的, 上述处理器 702, 还用于根据接入管理安全实体密钥及第一同 歩输入参数生成该第一 NH参数; 该第一同歩输入参数包括: 第一源基站密 钥、 第二 NH参数。
进一歩地,接收机 701,还用于接收 MME发送的该接入管理安全实体密 钥、 该第一源基站密钥、 该第二 NH参数。
发射机 703,还用于将该第二 NH参数发送至该源基站, 以使该源基站根 据该第二 NH参数确定该目标基站使用的密钥。
上述方案中, 该第一源基站密钥为该 MME根据该接入管理安全实体密 钥、 及非接入层计数器所确定的。
该第二 NH参数为该 MME根据该接入管理安全实密钥, 第二同歩输入 参数所确定的。
可替代地, 上述实施例方案中的处理器 702, 还用于根据第二源基站密 钥及随机数生成该第一 NH参数。
进一歩地, 接收机 701, 还用于接收 MME所发送的该第二源基站密钥; 其中, 该第二源基站密钥为该 MME根据接入管理安全实体密钥及非接入层 计数器所确定的; 或者
该第二源基站密钥为该 MME根据该接入管理安全实体密钥及该移动锚 点的标识所确定的。
本实施例方案所提供的移动锚点可实施上述任一实施例所提供的移动锚 点执行的路径切换方法, 具体的实现过程及有益效果与上述实施例类似, 在 此不再赘述。
实施例八
本发明实施例八还提供一种基站。 图 8为本发明实施例八所提供的基站 的结构示意图。
如图 8所示, 基站 800, 包括: 接收机 801、 处理器 802及发射机 803。 其中, 处理器 802, 用于判断进行全局路径切换或本地路径切换。
发射机 803, 用于若进行本地路径切换, 向移动锚点发送第一路径切换 请求消息, 以使该移动锚点保持该移动锚点和 SGW 间的用户面路径不变, 并使该移动锚点将与源基站间的用户面路径切换到目标基站。 基站 800为该 目标基站。
进一歩地, 上述实施例方案中的处理器 803, 还用于通过比较切换次数 与预设阈值的大小, 判断进行全局路径切换或本地路径切换, 若该切换次数 大于或等于该预设阈值, 则进行全局路径切换, 若该切换次数小于该预设阈 值, 则进行本地路径切换。
可选的, 接收机 801, 用于在处理器 802判断进行全局路径切换或本地 路径切换之前, 接收该源基站发送的切换请求消息; 该切换请求消息包括: 该源基站连接的锚点标识。
处理器 802, 还用于通过比较该源基站连接的锚点标识, 与该移动锚点 的标识, 判断进行全局路径切换或本地路径切换, 若该源基站连接的锚点标 识, 与该移动锚点的标识相同, 则进行本地路径切换, 若该源基站连接的锚 点标识, 与该移动锚点的标识不同, 则进行全局路径切换。 或者,
该切换请求消息包括: 该源基站所在基站簇的标识。
对应的, 处理器 802, 还用于通过比较该源基站所在基站簇的标识, 与 该目标基站所在基站簇的标识, 判断进行全局路径切换或本地路径切换, 若 该源基站所在基站簇的标识, 与该目标基站所在基站簇的标识相同, 则进行 本地路径切换, 若该源基站所在基站簇的标识, 与该目标基站所在基站簇的 标识不同, 则进行全局路径切换。
在如上实施例所述方案的基础上, 进一歩地, 接收机 801, 还用于接收 该移动锚点通过第一路径切换请求确认消息发送的第一 NH参数;该第一 NH 参数为该移动锚点所生成的。
处理器 802,还用于根据该第一 NH参数确定下一基站使用的密钥;其中, 该下一基站为除该源基站及该目标基站之外的其他基站。
可选的, 该第一 NH参数可以为该移动锚点根据接入管理安全实体密钥 及第一同歩输入参数所获得的参数; 该第一同歩输入参数包括: 第一源基站 密钥、 第二 NH参数。 该接入管理安全实体密钥、 该第一源基站密钥及该第 二 NH参数可以为该移动锚点接收的 MME发送的。
进一歩地, 该第一源基站密钥可以为该 MME根据该接入管理安全实体 密钥、 及非接入层计数器所确定的。
该第二 NH参数为 MME根据该接入管理安全实体密钥, 第二同歩输入 参数所确定的。
可替代地, 该第一 NH参数可以为该移动锚点根据第二源基站密钥及随 机数所确定的参数。
可选的, 该第二源基站密钥可以为该 MME根据接入管理安全实体密钥 及非接入层计数器所确定的。 或者
该第二源基站密钥还可以为该 MME根据该接入管理安全实体密钥及该 移动锚点的标识所确定的。
在如上所示实施例方案的基础上, 发射机 803, 还用于若进行全局路径 切换,向 MME发送第二路径切换请求消息,以触发修改该移动锚点和该 SGW 间的用户面路径。
本实施例方案所提供的基站可实施上述任一实施例所提供的基站执行的 路径切换方法, 具体的实现过程及有益效果与上述实施例类似, 在此不再赘 述。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分歩骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的歩骤; 而前述 的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 质。
最后应说明的是: 以上各实施例仅用以说明本发明的技术方案, 而非对 其限制; 尽管参照前述各实施例对本发明进行了详细的说明, 本领域的普通 技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改, 或者对其中部分或者全部技术特征进行等同替换; 而这些修改或者替换, 并 不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims

权利 要 求 书
1、 一种路径切换方法, 其特征在于, 包括:
移动锚点接收目标基站发送的路径切换请求消息;
若所述移动锚点进行本地路径切换, 所述移动锚点保持所述移动锚点和 服务网关 SGW间的用户面路径不变;
所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
2、 根据权利要求 1所述的方法, 其特征在于, 所述方法还包括: 若所述移动锚点进行全局路径切换,所述移动锚点向移动管理实体 MME 发送所述路径切换请求消息, 以触发修改所述移动锚点和所述 SGW 间的用 户面路径。
3、 根据权利要求 1或 2所述的方法, 其特征在于, 所述方法还包括: 所述移动锚点判断进行全局路径切换或本地路径切换。
4、 根据权利要求 3所述的方法, 其特征在于, 所述移动锚点判断进行全 局路径切换或本地路径切换, 包括:
所述移动锚点通过比较切换次数与预设阈值的大小, 判断进行全局路径 切换还是本地路径切换;
若所述切换次数大于或等于所述预设阈值, 则所述移动锚点确定进行全 局路径切换;
若所述切换次数小于所述预设阈值, 则所述移动锚点确定进行本地路径 切换。
5、 根据权利要求 3所述的方法, 其特征在于, 所述路径切换请求消息包 括: UE的接入标识; 所述 UE的接入标识为, 与所述源基站连接的锚点设备 为所述 UE分配的标识;
所述移动锚点判断进行全局路径切换或本地路径切换, 包括:
所述移动锚点通过对所述 UE的接入标识进行检索, 判断进行全局路径 切换或本地路径切换;
若所述移动锚点根据所述 UE的接入标识, 无法检索到所述 UE, 则所述 移动锚点确定进行全局路径切换;
若所述移动锚点根据所述 UE的接入标识, 检索到所述 UE, 则所述移动 锚点确定进行本地路径切换。
6、 根据权利要求 1-5中任一项所述的方法, 其特征在于, 所述方法, 还 包括:
所述移动锚点生成第一下一跳 NH参数;
所述移动锚点通过路径切换请求确认消息将所述第一 NH参数发送至所 述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基站使用的 密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
7、 根据权利要求 6 所述的方法, 其特征在于, 所述移动锚点生成第一 NH参数, 包括:
所述移动锚点根据接入管理安全实体密钥及第一同歩输入参数生成所述 第一 NH参数;
所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数。
8、 根据权利要求 7所述的方法, 其特征在于, 所述方法, 还包括: 所述移动锚点接收 MME发送的所述接入管理安全实体密钥、 所述第一 源基站密钥、 所述第二 NH参数;
所述移动锚点将所述第二 NH参数发送至所述源基站, 以使所述源基站 根据所述第二 NH参数确定所述目标基站使用的密钥。
9、 根据权利要求 7或 8所述的方法, 其特征在于, 所述第一源基站密钥 为所述 MME根据所述接入管理安全实体密钥、及非接入层计数器所确定的; 所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
10、 根据权利要求 6所述的方法, 其特征在于, 所述移动锚点生成第一 NH参数, 包括:
所述移动锚点根据第二源基站密钥及随机数生成所述第一 NH参数。
11、 根据权利要求 10所述的方法, 其特征在于, 所述方法, 还包括: 所述移动锚点接收 MME所发送的所述第二源基站密钥; 其中, 所述第 二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计数器所 确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
12、 一种路径切换方法, 其特征在于, 包括: 目标基站判断进行全局路径切换或本地路径切换;
若所述目标基站进行本地路径切换, 所述目标基站向移动锚点发送第一 路径切换请求消息,以使所述移动锚点保持所述移动锚点和服务网关 SGW间 的用户面路径不变, 并使所述移动锚点将与源基站间的用户面路径切换到所 述目标基站。
13、 根据权利要求 12所述的方法, 其特征在于, 所述目标基站判断进行 全局路径切换或本地路径切换, 包括:
所述目标基站通过比较切换次数与预设阈值的大小, 判断进行全局路径 切换或本地路径切换;
若所述切换次数大于或等于所述预设阈值, 则所述目标基站确定进行全 局路径切换;
若所述切换次数小于所述预设阈值, 则所述目标基站确定进行本地路径 切换。
14、 根据权利要求 12所述的方法, 其特征在于, 所述目标基站判断进行 全局路径切换或本地路径切换之前, 还包括:
所述目标基站接收所述源基站发送的切换请求消息; 所述切换请求消息 包括: 所述源基站连接的锚点标识;
所述目标基站判断进行全局路径切换或本地路径切换, 包括:
所述目标基站通过比较所述源基站连接的锚点标识, 与所述移动锚点的 标识, 判断进行全局路径切换或本地路径切换;
若所述源基站连接的锚点标识, 与所述移动锚点的标识相同, 所述目标 基站确定进行本地路径切换;
若所述源基站连接的锚点标识, 与所述移动锚点的标识不同, 所述目标 基站确定进行全局路径切换; 或者,
所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述目标基站判断进行全局路径切换或本地路径切换, 包括: 所述目标基站通过比较所述源基站所在基站簇的标识, 与所述目标基站 所在基站簇的标识, 判断进行全局路径切换或本地路径切换;
若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相 同, 所述目标基站确定进行本地路径切换; 若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识不 同, 所述目标基站确定进行全局路径切换。
15、 根据权利要求 12-14中任一项所述的方法, 其特征在于, 所述方法, 还包括:
所述目标基站接收所述移动锚点通过第一路径切换请求确认消息发送的 第一 NH参数; 所述第一 NH参数为所述移动锚点所生成的;
所述目标基站根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
16、 根据权利要求 15所述的方法, 其特征在于, 所述第一 NH参数为所 述移动锚点根据接入管理安全实体密钥及第一同歩输入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管 理安全实体密钥、 所述第一源基站密钥及所述第二 NH参数为所述移动锚点 接收的 MME发送的。
17、 根据权利要求 16所述的方法, 其特征在于, 所述第一源基站密钥为 所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的; 所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
18、 根据权利要求 15所述的方法, 其特征在于, 所述第一 NH参数为所 述移动锚点根据第二源基站密钥及随机数所确定的参数。
19、 根据权利要求 18所述的方法, 其特征在于, 所述第二源基站密钥为 所述 MME根据接入管理安全实体密钥及非接入层计数器所确定的; 或者 所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
20、 根据权利要求 12-19 中任一项所述的方法, 其特征在于, 所述方法 还包括:
若所述目标基站进行全局路径切换, 所述目标基站向 MME发送第二路 径切换请求消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
21、 一种移动锚点, 其特征在于, 包括:
接收模块, 用于接收目标基站发送的路径切换请求消息;
保持模块, 用于若进行本地路径切换, 保持所述移动锚点和 SGW 间的 用户面路径不变;
切换模块, 用于将所述移动锚点与源基站间的用户面路径切换到所述目 标基站。
22、 根据权利要求 21所述的移动锚点, 其特征在于, 所述移动锚点, 还 包括:
发送模块, 用于若进行全局路径切换, 向 MME发送所述路径切换请求 消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
23、 根据权利要求 21或 22所述的移动锚点, 其特征在于, 所述移动锚 点, 还包括:
判断模块, 用于判断进行全局路径切换或本地路径切换。
24、 根据权利要求 23所述的移动锚点, 其特征在于,
所述判断模块, 还用于通过比较切换次数与预设阈值的大小, 判断进行 全局路径切换还是本地路径切换,若所述切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径 切换。
25、 根据权利要求 23所述的移动锚点, 其特征在于, 所述路径切换请求 消息包括: UE的接入标识; 所述 UE的接入标识为, 与所述源基站连接的锚 点设备为所述 UE分配的标识;
所述判断模块, 还用于通过对所述 UE的接入标识进行检索, 判断进行 全局路径切换或本地路径切换, 若根据所述 UE的接入标识无法检索到所述 UE, 则进行全局路径切换, 若根据所述 UE的接入标识检索到所述 UE, 则 进行本地路径切换。
26、 根据权利要求 22-25 中任一项所述的移动锚点, 其特征在于, 所述 移动锚点, 还包括:
生成模块, 用于生成第一 NH参数;
所述发送模块, 还用于通过路径切换请求确认消息将所述第一 NH参数 发送至所述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基 站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的 其他基站。
27、 根据权利要求 26所述的移动锚点, 其特征在于, 所述生成模块, 还用于根据接入管理安全实体密钥及第一同歩输入参数 生成所述第一 NH参数; 其中, 所述第一同歩输入参数包括: 第一源基站密 钥、 第二 NH参数。
28、 根据权利要求 27所述的移动锚点, 其特征在于,
所述接收模块, 还用于接收所述 MME发送的所述接入管理安全实体密 钥、 所述第一源基站密钥、 所述第二 NH参数;
所述发送模块, 还用于将所述第二 NH参数发送至所述源基站, 以使所 述源基站根据所述第二 NH参数确定所述目标基站使用的密钥。
29、 根据权利要求 27或 28所述的移动锚点, 其特征在于, 所述第一源 基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器 所确定的;
所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
30、 根据权利要求 26所述的移动锚点, 其特征在于,
所述生成模块, 还用于根据第二源基站密钥及随机数生成所述第一 NH 参数。
31、 根据权利要求 30所述的移动锚点, 其特征在于,
所述接收模块, 还用于接收所述 MME所发送的所述第二源基站密钥; 其中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及 非接入层计数器所确定的; 或者
所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
32、 一种基站, 所述基站为目标基站, 其特征在于, 包括:
判断模块, 用于判断进行全局路径切换或本地路径切换;
发送模块, 用于若进行本地路径切换, 向移动锚点发送第一路径切换请 求消息, 以使所述移动锚点保持所述移动锚点和 SGW间的用户面路径不变, 并使所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
33、 根据权利要求 32所述的基站, 其特征在于,
所述判断模块, 还用于通过比较切换次数与预设阈值的大小, 判断进行 全局路径切换或本地路径切换, 若所述切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径 切换。
34、 根据权利要求 32所述的基站, 其特征在于, 所述基站, 还包括: 接收模块, 用于在所述判断模块判断进行全局路径切换或本地路径切换 之前, 接收所述源基站发送的切换请求消息; 所述切换请求消息包括: 所述 源基站连接的锚点标识;
所述判断模块, 还用于通过比较所述源基站连接的锚点标识, 与所述移 动锚点的标识, 判断进行全局路径切换或本地路径切换, 若所述源基站连接 的锚点标识, 与所述移动锚点的标识相同, 则进行本地路径切换, 若所述源 基站连接的锚点标识, 与所述移动锚点的标识不同, 则进行全局路径切换; 或者,
所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述判断模块, 还用于通过比较所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识,判断进行全局路径切换或本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相同, 则进行本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所 在基站簇的标识不同, 则进行全局路径切换。
35、 根据权利要求 34所述的基站, 其特征在于,
所述接收模块, 还用于接收所述移动锚点通过第一路径切换请求确认消 息发送的第一 NH参数; 所述第一 NH参数为所述移动锚点所生成的;
所述基站还包括:
确定模块, 用于根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
36、 根据权利要求 35所述的基站, 其特征在于, 所述第一 NH参数为所 述移动锚点根据接入管理安全实体密钥及第一同歩输入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管 理安全实体密钥、 所述第一源基站密钥及所述第二 NH参数为所述移动锚点 接收的 MME发送的。
37、 根据权利要求 36所述的基站, 其特征在于, 所述第一源基站密钥为 所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的; 所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
38、 根据权利要求 35所述的基站, 其特征在于, 所述第一 NH参数为所 述移动锚点根据第二源基站密钥及随机数所确定的参数。
39、 根据权利要求 38所述的基站, 其特征在于, 所述第二源基站密钥为 所述 MME根据接入管理安全实体密钥及非接入层计数器所确定的; 或者 所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
40、 根据权利要求 32-39中任一项所述的基站, 其特征在于,
所述发送模块, 还用于若进行全局路径切换, 向 MME发送第二路径切 换请求消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
41、 一种移动锚点, 其特征在于, 包括: 接收机、 处理器及发射机; 其中, 所述接收机, 用于接收目标基站发送的路径切换请求消息; 所述处理器, 用于若进行本地路径切换, 保持所述移动锚点和 SGW 间 的用户面路径不变, 并将所述移动锚点与源基站间的用户面路径切换到所述 目标基站。
42、 根据权利要求 41所述的移动锚点, 其特征在于,
所述发射机, 还用于若进行全局路径切换, 向 MME发送所述路径切换 请求消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
43、 根据权利要求 41或 42所述的移动锚点, 其特征在于,
所述处理器, 还用于判断进行全局路径切换或本地路径切换。
44、 根据权利要求 43所述的移动锚点, 其特征在于,
所述处理器, 还用于通过比较切换次数与预设阈值的大小, 判断进行全 局路径切换还是本地路径切换, 若所述切换次数大于或等于所述预设阈值, 则进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径 切换。
45、 根据权利要求 43所述的移动锚点, 其特征在于, 所述路径切换请求 消息包括: UE的接入标识; 所述 UE的接入标识为, 与所述源基站连接的锚 点设备为所述 UE分配的标识;
所述处理器, 还用于通过对所述 UE的接入标识进行检索, 判断进行全 局路径切换或本地路径切换, 若根据所述 UE 的接入标识, 无法检索到所述 UE, 则进行全局路径切换, 若根据所述 UE的接入标识, 检索到所述 UE, 则确定进行本地路径切换。
46、 根据权利要求 41-45中任一项所述的移动锚点, 其特征在于, 所述处理器, 还用于生成第一下一跳 NH参数;
所述发射机, 还用于通过路径切换请求确认消息将所述第一 NH参数发 送至所述目标基站, 以使所述目标基站根据所述第一 NH参数确定下一基站 使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其 他基站。
47、 根据权利要求 46所述的移动锚点, 其特征在于,
所述处理器, 还用于根据接入管理安全实体密钥及第一同歩输入参数生 成所述第一 NH参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数。
48、 根据权利要求 47所述的移动锚点, 其特征在于,
所述接收机, 还用于接收 MME发送的所述接入管理安全实体密钥、 所 述第一源基站密钥、 所述第二 NH参数;
所述发射机, 还用于将所述第二 NH参数发送至所述源基站, 以使所述 源基站根据所述第二 NH参数确定所述目标基站使用的密钥。
49、 根据权利要求 47或 48所述的移动锚点, 其特征在于, 所述第一源 基站密钥为所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器 所确定的;
所述第二 NH参数为所述 MME根据所述接入管理安全实密钥, 第二同 歩输入参数所确定的。
50、 根据权利要去 46所述的移动锚点, 其特征在于,
所述处理器, 还用于根据第二源基站密钥及随机数生成所述第一 NH参 数。
51、 根据权利要求 50所述的移动锚点, 其特征在于,
所述接收机, 还用于接收 MME所发送的所述第二源基站密钥; 其中, 所述第二源基站密钥为所述 MME根据接入管理安全实体密钥及非接入层计 数器所确定的; 或者 所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
52、 一种基站, 所述基站为目标基站, 其特征在于, 包括: 接收机、 处 理器及发射机;
其中, 所述处理器, 用于判断进行全局路径切换或本地路径切换; 所述发射机, 用于若进行本地路径切换, 向移动锚点发送第一路径切换 请求消息, 以使所述移动锚点保持所述移动锚点和 SGW 间的用户面路径不 变, 并使所述移动锚点将与源基站间的用户面路径切换到所述目标基站。
53、 根据权利要求 52所述的基站, 其特征在于,
所述处理器, 还用于通过比较切换次数与预设阈值的大小, 判断进行全 局路径切换或本地路径切换, 若所述切换次数大于或等于所述预设阈值, 则 进行全局路径切换, 若所述切换次数小于所述预设阈值, 则进行本地路径切 换。
54、 根据权利要求 52所述的基站, 其特征在于,
所述接收机, 用于在所述处理器判断进行全局路径切换或本地路径切换 之前, 接收所述源基站发送的切换请求消息; 所述切换请求消息包括: 所述 源基站连接的锚点标识;
所述处理器, 还用于通过比较所述源基站连接的锚点标识, 与所述移动 锚点的标识, 判断进行全局路径切换或本地路径切换, 若所述源基站连接的 锚点标识, 与所述移动锚点的标识相同, 则进行本地路径切换, 若所述源基 站连接的锚点标识, 与所述移动锚点的标识不同, 则进行全局路径切换; 或 者,
所述切换请求消息包括: 所述源基站所在基站簇的标识;
对应的, 所述处理器, 还用于通过比较所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识,判断进行全局路径切换或本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所在基站簇的标识相同, 则进行本地路径切换, 若所述源基站所在基站簇的标识, 与所述目标基站所 在基站簇的标识不同, 则进行全局路径切换。
55、 根据权利要求 52-54中任一项所述的基站, 其特征在于,
所述接收机, 还用于接收所述移动锚点通过第一路径切换请求确认消息 发送的第一 NH参数; 所述第一 NH参数为所述移动锚点所生成的; 所述处理器, 还用于根据所述第一 NH参数确定下一基站使用的密钥; 其中, 所述下一基站为除所述源基站及所述目标基站之外的其他基站。
56、 根据权利要求 55所述的基站, 其特征在于, 所述第一 NH参数为所 述移动锚点根据接入管理安全实体密钥及第一同歩输入参数所获得的参数; 所述第一同歩输入参数包括: 第一源基站密钥、 第二 NH参数; 所述接入管 理安全实体密钥、 所述第一源基站密钥及所述第二 NH参数为所述移动锚点 接收的 MME发送的。
57、 根据权利要求 56所述的基站, 其特征在于, 所述第一源基站密钥为 所述 MME根据所述接入管理安全实体密钥、 及非接入层计数器所确定的; 所述第二 NH参数为 MME根据所述接入管理安全实体密钥, 第二同歩 输入参数所确定的。
58、 根据权利要求 55所述的基站, 其特征在于, 所述第一 NH参数为所 述移动锚点根据第二源基站密钥及随机数所确定的参数。
59、 根据权利要求 58所述的基站, 其特征在于, 所述第二源基站密钥为 所述 MME根据接入管理安全实体密钥及非接入层计数器所确定的; 或者 所述第二源基站密钥为所述 MME根据所述接入管理安全实体密钥及所 述移动锚点的标识所确定的。
60、 根据权利要求 52-59中任一项所述的基站, 其特征在于,
所述发射机, 还用于若进行全局路径切换, 向 MME发送第二路径切换 请求消息, 以触发修改所述移动锚点和所述 SGW间的用户面路径。
PCT/CN2014/084730 2014-08-19 2014-08-19 路径切换方法、移动锚点及基站 WO2016026088A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201480029180.4A CN105532035B (zh) 2014-08-19 2014-08-19 路径切换方法、移动锚点及基站
EP14900188.5A EP3171635B1 (en) 2014-08-19 2014-08-19 Path switching method, mobile anchor point and base station
PCT/CN2014/084730 WO2016026088A1 (zh) 2014-08-19 2014-08-19 路径切换方法、移动锚点及基站
US15/436,527 US20170164244A1 (en) 2014-08-19 2017-02-17 Path switching method, mobility anchor, and base station

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084730 WO2016026088A1 (zh) 2014-08-19 2014-08-19 路径切换方法、移动锚点及基站

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/436,527 Continuation US20170164244A1 (en) 2014-08-19 2017-02-17 Path switching method, mobility anchor, and base station

Publications (1)

Publication Number Publication Date
WO2016026088A1 true WO2016026088A1 (zh) 2016-02-25

Family

ID=55350081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084730 WO2016026088A1 (zh) 2014-08-19 2014-08-19 路径切换方法、移动锚点及基站

Country Status (4)

Country Link
US (1) US20170164244A1 (zh)
EP (1) EP3171635B1 (zh)
CN (1) CN105532035B (zh)
WO (1) WO2016026088A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105557029A (zh) * 2014-08-22 2016-05-04 华为技术有限公司 一种通信系统、本地移动节点及基站
WO2017198898A1 (en) * 2016-05-17 2017-11-23 Nokia Technologies Oy Path switch method between lte and 5g node
CN109644384A (zh) * 2016-08-26 2019-04-16 华为技术有限公司 一种网络管理方法和控制器

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108260126B (zh) * 2016-12-29 2021-02-19 中国移动通信集团浙江有限公司 一种伪基站识别定位方法和装置
CN109429285B (zh) * 2017-09-04 2021-03-30 中国移动通信有限公司研究院 一种数据处理方法、网络设备和计算机存储介质
CN110167082B (zh) * 2018-02-14 2021-11-30 中兴通讯股份有限公司 网络的切换方法、装置及系统,切换确定方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426252A (zh) * 2007-11-02 2009-05-06 华为技术有限公司 一种路径切换的处理方法、系统和装置
CN102223691A (zh) * 2010-04-15 2011-10-19 北京三星通信技术研究有限公司 移动通信系统中的切换方法
CN103636257A (zh) * 2011-07-01 2014-03-12 交互数字专利控股公司 用于支持本地ip接入lipa移动性的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101175017B1 (ko) * 2008-04-04 2012-08-17 노키아 코포레이션 핸드오버에 대하여 멀티-홉 암호 분리를 제공하는 방법, 장치 및 컴퓨터 판독 가능한 저장 매체
EP2688325B1 (en) * 2011-03-15 2018-08-01 NEC Corporation Mobility management system, mobility management method, access gateway device and mobility management control device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426252A (zh) * 2007-11-02 2009-05-06 华为技术有限公司 一种路径切换的处理方法、系统和装置
CN102223691A (zh) * 2010-04-15 2011-10-19 北京三星通信技术研究有限公司 移动通信系统中的切换方法
CN103636257A (zh) * 2011-07-01 2014-03-12 交互数字专利控股公司 用于支持本地ip接入lipa移动性的方法和装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105557029A (zh) * 2014-08-22 2016-05-04 华为技术有限公司 一种通信系统、本地移动节点及基站
WO2017198898A1 (en) * 2016-05-17 2017-11-23 Nokia Technologies Oy Path switch method between lte and 5g node
US11115880B2 (en) 2016-05-17 2021-09-07 Nokia Technologies Oy Path switch method between LTE and 5G node
CN109644384A (zh) * 2016-08-26 2019-04-16 华为技术有限公司 一种网络管理方法和控制器
CN109644384B (zh) * 2016-08-26 2021-02-05 华为技术有限公司 一种网络管理方法和控制器
US11064551B2 (en) 2016-08-26 2021-07-13 Huawei Technologies Co., Ltd. Network management method and controller

Also Published As

Publication number Publication date
CN105532035A (zh) 2016-04-27
US20170164244A1 (en) 2017-06-08
EP3171635A4 (en) 2017-08-09
EP3171635A1 (en) 2017-05-24
CN105532035B (zh) 2019-07-12
EP3171635B1 (en) 2020-11-11

Similar Documents

Publication Publication Date Title
US11050727B2 (en) Security key generation and management method of PDCP distributed structure for supporting dual connectivity
US10728757B2 (en) Security implementation method, related apparatus, and system
US10492214B2 (en) Communication of security key information
JP6292427B2 (ja) ハンドオーバー中の鍵導出に適合した通信システム
US11330670B2 (en) First radio network node (RNN), a second RNN and methods therein for establishing a communications interface between the first RNN and the second RNN
KR102057979B1 (ko) 핸드오버 장치 및 방법
WO2018201487A1 (en) Method and apparatus for carrying out a group handover
US20170359719A1 (en) Key generation method, device, and system
WO2015066406A2 (en) Method and apparatus to enable multiple wireless connections
WO2016026088A1 (zh) 路径切换方法、移动锚点及基站
CN102348206B (zh) 密钥隔离方法和装置
JP2014533908A (ja) 無線通信システムにおける端末との通信認証のためのセキュリティキーを管理する方法及び装置
CN104602307A (zh) 切换方法及系统
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2017193555A1 (zh) 小区切换的方法和系统
US20220377541A1 (en) Key Management Method and Communication Apparatus
WO2022082544A1 (zh) Iab节点的移植方法及装置
WO2017016450A1 (en) Ultra dense network security architecture and method
WO2024120500A1 (zh) 通信方法及相关装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201480029180.4

Country of ref document: CN

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

Ref document number: 14900188

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014900188

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014900188

Country of ref document: EP