[go: up one dir, main page]

WO2016101468A1 - 移动性管理方法及装置 - Google Patents

移动性管理方法及装置 Download PDF

Info

Publication number
WO2016101468A1
WO2016101468A1 PCT/CN2015/077531 CN2015077531W WO2016101468A1 WO 2016101468 A1 WO2016101468 A1 WO 2016101468A1 CN 2015077531 W CN2015077531 W CN 2015077531W WO 2016101468 A1 WO2016101468 A1 WO 2016101468A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
gateway
message
secondary base
established
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/077531
Other languages
English (en)
French (fr)
Inventor
黄莹
高音
和峰
谢峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2016101468A1 publication Critical patent/WO2016101468A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/08—Mobility data transfer

Definitions

  • the present invention relates to the field of communications, and in particular to a mobility management method and apparatus.
  • LTE Long Term Evolution
  • UE User Equipment
  • 3GPP 3rd Generation Partnership Project
  • LPN low power node
  • the LPN has the features of low-cost, low-power, and easy-to-deploy. It can include hotspot deployment and enhanced coverage.
  • the LPN may also be referred to as a small base station, which may include, but is not limited to, a home base station (HeNB), a pico base station (pico), a radio remote unit/head (RRU/RRH), and a relay node (RN).
  • HeNB home base station
  • pico pico
  • RRU/RRH radio remote unit/head
  • RN relay node
  • FIG. 1 is a schematic diagram of a dual connectivity architecture according to the related art. As shown in FIG.
  • a UE maintains a connection with at least two base stations and uses radio resources under two base stations, so that radio resource aggregation across nodes can be implemented.
  • This architecture is usually called a dual connectivity architecture.
  • the two base stations connected to the UE have a certain management control capability and are generally referred to as a master base station (MeNB).
  • the other base station is called a secondary base station (Secondary eNB, SeNB for short).
  • SeNB secondary base station
  • the dual connection can be implemented through the SeNB adding procedure.
  • the SeNB can perform a series of management, for example, SeNB modification, SeNB deletion, and SeNB modification.
  • the user plane in the dual connectivity architecture There are two possible architectures for the user plane in the dual connectivity architecture, namely the 1A architecture in the architecture option1 or the 3C architecture in the architecture option3, where the S1-U terminates in the MeNB and the SeNB in the architecture option 1, in the architecture option 3
  • the S1-U is terminated by the MeNB, and the bearer is separated on the RAN side.
  • the downlink data in the EPS bearer arrives at the MeNB, part of the data in one bearer can be separated into the SeNB, and then sent by the SeNB to the UE.
  • Pick The architecture option1 is used, and the user plane protocol stack on the SeNB has independent PDCP and the following protocol layers, and no bearer separation.
  • the HeNB is likely to be deployed as an MeNB or SeNB.
  • the home base station in the LTE system is called a home eNB.
  • the functions supported by the HeNB are basically the same as those of the eNB.
  • the process between the HeNB and the evolved packet core network (Evolved Packet Core, EPC for short) is basically the same as that between the eNB and the EPC. Since the deployment of the HeNB is usually not planned by the mobile operator's network, the coverage is small and numerous.
  • a new network element home base station gateway (Home eNB Gateway) is introduced between the HeNB and the EPC S1 connection under the E-UTRAN (Evolved UTRAN) architecture.
  • HeNB GW may be connected to the mobility management entity (Mobility Management Entity, MME for short) through the HeNB GW as an S1 proxy.
  • MME Mobility Management Entity
  • the S1 data between the HeNB and the SGW optionally terminates at the HeNB GW.
  • the MeNB needs to add a new SeNB to the UE or replace it with the SeNB served by the UE.
  • the S1 user plane data is sent by the SGW to the MeNB and the SeNB respectively, that is, the mobility anchor point of the S1 user plane is located in the core network element SGW.
  • the MeNB needs to initiate a path update process. Update the S1 bearer information of the SGW.
  • the SeNB is a small base station, and the coverage of the small base station is small and is densely deployed in the hotspot area.
  • the core network element is required to be added/changed each time the SeNB is added/changed. Participating in the interaction will result in a large core network signaling load and cause a delay in the SeNB management process.
  • a mobility management method for improving the above-mentioned problems in the dual connectivity architecture in the related art.
  • the embodiment of the present invention provides a mobility management method and apparatus to solve at least the problem that the UE mobility management process in the dual connectivity architecture increases the core network signaling load in the related art.
  • a mobility management method is provided.
  • the mobility management method includes: the secondary base station sends a first message for requesting the path update to the gateway, where the first message for requesting the path update carries the self-allocated need to be established on itself.
  • the first message for requesting the path update carries the self-allocated need to be established on itself.
  • the secondary base station receives the first acknowledgement message replied by the gateway, where The first acknowledgment message carries the uplink and downlink GTP information of the bearer that the gateway needs to establish on itself for the secondary base station and the SGW.
  • GTP general packet radio service tunneling protocol
  • the method further includes: the secondary base station receiving, by the primary base station, a message for requesting the addition of the secondary base station, where the message for requesting the secondary base station addition is requested.
  • the bearer carries the uplink GTP information of the bearer that needs to be established on the SGW.
  • the method further includes: the secondary eNB replies with the second acknowledgment message to the primary eNB, where the second acknowledgment message carries the need for the SGW to be established on the SGW.
  • the method further includes: the primary base station sends a second message for requesting the path update to the mobility management entity (MME), and the second message is used for requesting the path update message.
  • MME mobility management entity
  • the gateway is one of the following: a home base station gateway, a mobile anchor point, a dual connectivity gateway, and a new gateway network element.
  • the GTP information includes at least one of the following: Internet Protocol (IP) address information, GTP Tunnel Endpoint Identity (TEID).
  • IP Internet Protocol
  • TEID GTP Tunnel Endpoint Identity
  • the secondary base station is a home base station.
  • the mobility management method includes: the secondary base station sends a message for requesting the path update to the gateway, where the message for requesting the path update carries the downlink generalization of the bearer that needs to be established on itself.
  • the packet is configured to receive the acknowledgment message replied by the gateway, where the acknowledgment message carries the uplink GTP information of the bearer that the gateway needs to establish on the eNB.
  • the method further includes: the secondary base station receiving the message that the X2 interface from the primary base station is used to indicate that the secondary base station is reconfigured, and the secondary base station has been associated with the user equipment (UE) establishes a connection.
  • the secondary base station receiving the message that the X2 interface from the primary base station is used to indicate that the secondary base station is reconfigured, and the secondary base station has been associated with the user equipment (UE) establishes a connection.
  • the gateway is one of the following: a home base station gateway, a mobile anchor point, a dual connectivity gateway, and a new gateway network element.
  • the mobility management method includes: the primary base station sends a message for requesting a path update to the gateway, where the message for requesting the path update carries the received requirement allocated by the secondary base station on the secondary base station.
  • the primary base station receives the first acknowledgement of the gateway reply The message, where the first acknowledgment message carries the uplink GTP information of the bearer that the gateway needs to establish on the secondary base station and the downlink GTP information that needs to be established on the secondary base station for the SGW.
  • GTP general packet radio service tunneling protocol
  • the method further includes: the primary base station sending a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the gateway
  • the uplink GTP information of the bearer that needs to be established on the secondary base station is allocated; the primary base station receives the second acknowledgement message replied by the secondary base station, where the second acknowledgement message carries the downlink of the bearer allocated by the secondary base station and needs to be established on the secondary base station GTP information.
  • the method further includes: the primary base station transmitting, to the mobility management entity (MME), the downlink GTP information of the bearer allocated by the gateway for the SGW to be established on the secondary base station.
  • MME mobility management entity
  • the gateway is one of the following: a home base station gateway, a mobile anchor point, a dual connectivity gateway, and a new gateway network element.
  • the mobility management method includes: the primary base station sends a message for requesting a path update to the gateway, where the message for requesting the path update carries the received requirement allocated by the secondary base station on the secondary base station.
  • the bearer downlink general packet radio service tunneling protocol (GTP) information is set up; the master base station receives the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the bearer allocated by the gateway for the secondary base station and needs to be established on the secondary base station Uplink GTP information.
  • GTP general packet radio service tunneling protocol
  • the method further includes: the primary base station sending a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the gateway Assigning the uplink GTP information of the bearer that needs to be established on the secondary base station; the primary base station receives the second acknowledgement message from the secondary base station, where the second acknowledgement message carries the bearer that needs to be established on the secondary base station by the secondary base station Downstream GTP information.
  • the gateway is one of the following: a home base station gateway, a mobile anchor point, a dual connectivity gateway, and a new gateway network element.
  • a mobility management apparatus is provided.
  • the mobility management apparatus includes: a sending module, configured to send a first message for requesting a path update to the gateway, where the first message for requesting the path update carries the need for self-allocation in itself
  • the first receiving module is configured as a receiving gateway
  • the first acknowledgment message of the acknowledgment wherein the first acknowledgment message carries the uplink and downlink GTP information of the bearer that the gateway needs to establish on itself for the secondary base station and the SGW.
  • the apparatus further includes: a second receiving module, configured to receive a message from the primary base station for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station carries the need for the SGW to be allocated on itself Established uplink GTP information of the bearer.
  • a second receiving module configured to receive a message from the primary base station for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station carries the need for the SGW to be allocated on itself Established uplink GTP information of the bearer.
  • the apparatus further includes: a replying module, configured to reply to the primary base station with a second acknowledgement message, where the second acknowledgement message carries the downlink GTP information of the bearer allocated by the gateway for the SGW to be established on itself.
  • a replying module configured to reply to the primary base station with a second acknowledgement message, where the second acknowledgement message carries the downlink GTP information of the bearer allocated by the gateway for the SGW to be established on itself.
  • another mobility management apparatus is provided.
  • the mobility management apparatus includes: a sending module, configured to send a message for requesting a path update to the gateway, where the message for requesting the path update carries a bearer that needs to be established on itself Downlink General Packet Radio Service Tunneling Protocol (GTP) information; the first receiving module is configured to receive an acknowledgment message replied by the gateway, where the acknowledgment message carries the uplink GTP of the bearer allocated by the gateway for the secondary base station to be established on itself information.
  • GTP General Packet Radio Service Tunneling Protocol
  • the apparatus further includes: a second receiving module, configured to receive a message from the X2 interface of the primary base station to indicate completion of reconfiguration of the secondary base station, and establish a connection with the user equipment (UE) by itself.
  • a second receiving module configured to receive a message from the X2 interface of the primary base station to indicate completion of reconfiguration of the secondary base station, and establish a connection with the user equipment (UE) by itself.
  • another mobility management apparatus is provided.
  • the mobility management apparatus includes: a first sending module, configured to send a message for requesting a path update to a gateway, where the message for requesting the path update carries the received information allocated by the secondary base station
  • the first receiving module The first acknowledgment message is set to receive the reply from the gateway, where the first acknowledgment message carries the uplink GTP information that the gateway needs to allocate on the secondary base station and needs to be allocated on the secondary base station, and the need for the SGW to be allocated on the secondary base station Established bearer downlink GTP information.
  • the foregoing apparatus further includes: a second sending module, configured to send a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the need for the gateway to be established on the secondary base station
  • the second receiving module is configured to receive the second acknowledgment message replied by the secondary eNB, where the second acknowledgment message carries the downlink GTP information of the bearer that needs to be established on the secondary eNB.
  • the foregoing apparatus further includes: a third sending module, configured to send, to the mobility management entity (MME), the downlink GTP information of the bearer that needs to be established on the secondary base station allocated by the gateway for the SGW.
  • MME mobility management entity
  • another mobility management apparatus is provided.
  • the mobility management apparatus includes: a first sending module, configured to send a message for requesting a path update to a gateway, where the message for requesting the path update carries the received information allocated by the secondary base station
  • the first receiving module is configured to receive the first acknowledgement message replied by the gateway, where the first acknowledgement message carries the gateway for the secondary base station
  • GTP general packet radio service tunneling protocol
  • the foregoing apparatus further includes: a second sending module, configured to send a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the need for the gateway to be established on the secondary base station
  • the second receiving module is configured to receive the second acknowledgment message from the secondary base station, where the second acknowledgment message carries the downlink GTP that is allocated by the secondary base station and needs to be established on the secondary base station. information.
  • the secondary base station sends the first message for requesting the path update to the gateway, where the first message for requesting the path update carries the downlink GTP information of the bearer that needs to be established on itself. And the received uplink GTP information that is allocated by the SGW and needs to be established on the bearer; the secondary eNB receives the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the need for the gateway to allocate the secondary base station and the SGW respectively.
  • the uplink and downlink GTP information of the bearer established on the self-solving system solves the problem that the UE mobility management process in the dual-connection architecture increases the signaling load of the core network in the related art, thereby effectively reducing the SeNB management process in the UE.
  • the S1 signaling load between the RAN and the core network reduces the delay of the SeNB management process, improves the quality of service, and improves the user experience.
  • FIG. 1 is a schematic diagram of a dual connectivity architecture according to the related art
  • FIG. 2 is a flowchart of a mobility management method according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of another mobility management method according to an embodiment of the present invention.
  • FIG. 4 is a flow chart of another mobility management method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of another mobility management method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a scenario in which a first SeNB is added by a MeNB to a UE according to a preferred embodiment of the present invention
  • FIG. 7 is a flowchart of adding a first SeNB to a UE by an MeNB according to a preferred embodiment of the present invention
  • FIG. 8 is a schematic diagram of a scenario of a mobility management method in a scenario in which a UE's MeNB is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention
  • FIG. 9 is a flowchart of a mobility management method in a scenario in which a UE's MeNB is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention
  • FIG. 10 is a schematic diagram of another scenario in which a MeNB adds a first SeNB to a UE according to a preferred embodiment of the present invention.
  • FIG. 11 is a flowchart of another method for adding a first SeNB by a MeNB to a UE according to a preferred embodiment of the present invention
  • FIG. 12 is a schematic diagram of a scenario of a mobility management method in a scenario in which a UE of an UE is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention
  • FIG. 13 is a flowchart of a mobility management method in a scenario in which a UE of an UE is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention
  • FIG. 14 is a structural block diagram of a mobility management apparatus according to an embodiment of the present invention.
  • Figure 15 is a block diagram showing the structure of a mobility management apparatus in accordance with a preferred embodiment of the present invention.
  • 16 is a block diagram showing the structure of another mobility management apparatus according to an embodiment of the present invention.
  • 17 is a block diagram showing the structure of another mobility management apparatus according to a preferred embodiment of the present invention.
  • FIG. 18 is a structural block diagram of another mobility management apparatus according to an embodiment of the present invention.
  • FIG. 19 is a block diagram showing the structure of another mobility management apparatus according to a preferred embodiment of the present invention.
  • FIG. 20 is a structural block diagram of another mobility management apparatus according to an embodiment of the present invention.
  • 21 is a block diagram showing the structure of another mobility management apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 2 is a flow chart of a mobility management method in accordance with an embodiment of the present invention. As shown in FIG. 2, the method may include the following processing steps:
  • Step S202 The secondary base station sends a first message for requesting the path update to the gateway, where the first message for requesting the path update carries the downlink GTP information of the bearer that needs to be established on itself and the received message.
  • Step S204 The secondary eNB receives the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the uplink and downlink GTP information of the bearer that the gateway needs to establish on the eNB and the SGW.
  • the UE mobility management process under the dual connectivity architecture increases the core network signaling load.
  • the secondary base station uses the method shown in FIG. 2, the secondary base station transmits to the gateway the downlink general packet radio service tunneling protocol GTP information carrying the bearer that needs to be established on itself, and the received requirement allocated by the signaling gateway SGW.
  • the message for requesting the path update is carried in the uplink GTP information of the bearer that is set up on the device, so as to obtain the uplink and downlink GTP information of the bearer that the gateway needs to establish on the slave base station and the SGW respectively, and avoid the core network element.
  • the S1 signaling load reduces the delay of the SeNB management process, improves the quality of service, and improves the user experience.
  • the gateway is only described in detail by taking the HeNB GW as an example, but it does not constitute an undue limitation to the present invention.
  • the gateway can also be a mobility anchor, a dual connectivity gateway (DC GW), or other new gateway network element.
  • the HeNB of the MeNB or the SeNB identity may be connected to the MME through the HeNB GW, and the S1 message exchanged between the MME and the MeNB/SeNB may be forwarded by the HeNB GW.
  • the HeNB that is the MeNB or SeNB identity can be connected to other base stations through the X2 GW. Then, the X2 message exchanged between the MeNB/SeNB and other base stations, and the X2 message exchanged between the MeNB and the SeNB can be forwarded by the X2 GW.
  • the foregoing secondary base station is a home base station
  • the foregoing GTP information may include, but is not limited to, at least one of the following:
  • IP Internet Protocol
  • the following operations may be included in the step S202:
  • Step S1 The secondary base station receives the message from the primary base station for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station carries the uplink GTP information of the bearer allocated by the SGW and needs to be established on itself.
  • the secondary base station may further include the following steps:
  • Step S2 The secondary base station replies to the primary eNB with the second acknowledgment message, where the second acknowledgment message carries the downlink GTP information of the bearer that the gateway needs to establish on the SGW.
  • the secondary base station may further include the following operations:
  • Step S3 The primary base station sends a second message for requesting the path update to the MME, and the second message for requesting the path update carries the received downlink GTP that is allocated by the gateway to the SGW and needs to be established on the secondary base station. information.
  • first and “second” in the message for requesting the path update and the second message for requesting the path update are only used to indicate the execution of the message for requesting the path update.
  • the main body is different, and the information carried in the message is different, and does not mean that the types of the two messages are different, which are messages with the request path update function.
  • the “first” and “second” in the first acknowledgement message and the second acknowledgement message are only used to indicate that the execution subject of the acknowledgement message is different, and the information carried in the message is different, instead of indicating two types of messages. Different types are messages with confirmation function.
  • the first message for requesting a path update or the second message for requesting a path update may be one of the following types:
  • FIG. 3 is a flow chart of another mobility management method in accordance with an embodiment of the present invention. As shown in FIG. 3, the method may include the following processing steps:
  • Step S302 The secondary base station sends a message for requesting the path update to the gateway, where the message for requesting the path update carries the downlink GTP information of the bearer that needs to be established on itself.
  • Step S304 The secondary base station receives an acknowledgment message replied by the gateway, where the acknowledgment message carries the uplink GTP information of the bearer allocated by the gateway for the secondary base station to be established on itself.
  • the following operations may also be included:
  • Step S4 The secondary base station receives the message that the X2 interface from the primary base station is used to indicate that the secondary base station is reconfigured, and the secondary base station has established a connection with the UE.
  • the above message for requesting a path update may be one of the following types:
  • FIG. 4 is a flow chart of another mobility management method in accordance with an embodiment of the present invention. As shown in FIG. 4, the method may include the following processing steps:
  • Step S402 The primary base station sends a message for requesting the path update to the gateway, where the message for requesting the path update carries the received downlink GTP information of the bearer that needs to be established on the secondary base station and is received by the secondary base station.
  • Step S404 The primary base station receives the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the uplink GTP information of the bearer allocated by the gateway to the secondary base station and needs to be established on the secondary base station, and the need for the SGW to be allocated The downlink GTP information of the bearer established on the base station.
  • the above message for requesting a path update may be one of the following types:
  • the method may further include:
  • Step S5 The primary base station sends a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the uplink GTP information of the bearer allocated by the gateway and needs to be established on the secondary base station;
  • Step S6 The primary base station receives the second acknowledgment message replied by the secondary base station, where the second acknowledgment message carries the downlink GTP information of the bearer that needs to be established on the secondary base station. That is, the MeNB may send the downlink GTP information to the SeNB through the SeNB reconfiguration complete message.
  • the primary base station may further include the following steps:
  • Step S7 The primary base station sends the downlink GTP information of the bearer that the gateway needs to establish on the secondary base station to the MME. That is, the MeNB may send the downlink GTP information to the MME through the S1 interface E-RAB modification indication message, the S1 interface path transfer message, or other S1 interface message.
  • FIG. 5 is a flowchart of another mobility management method according to an embodiment of the present invention. As shown in FIG. 5, the method may include the following processing steps:
  • Step S502 The primary base station sends a message for requesting the path update to the gateway, where the message for requesting the path update carries the received downlink GTP information of the bearer allocated by the secondary base station and needs to be established on the secondary base station;
  • Step S504 The primary base station receives the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the uplink GTP information of the bearer that the gateway needs to establish on the secondary base station.
  • the following operations may be included in the step S502:
  • Step S8 The primary base station sends a message for requesting the addition of the secondary base station to the secondary base station, where the message for requesting the addition of the secondary base station carries the uplink GTP information of the bearer allocated by the gateway and needs to be established on the secondary base station;
  • Step S9 The primary base station receives the second acknowledgment message from the secondary base station, where the second acknowledgment message carries the downlink GTP information of the bearer that needs to be established on the secondary base station and is allocated by the secondary base station.
  • FIG. 6 is a schematic diagram of a scenario in which a first SeNB is added by a MeNB to a UE according to a preferred embodiment of the present invention.
  • the SeNB is an HeNB
  • the S1 interface exists between the SeNB and the HeNB GW, and may include: a user plane and a control plane, where the S1-C interface is mainly used for the S1 user plane path update of the UE.
  • 7 is a flow diagram of adding a first SeNB to a UE by a MeNB in accordance with a preferred embodiment of the present invention. As shown in FIG. 7, the process may include the following processing steps:
  • the MeNB reports the measurement report, and the MeNB determines, according to the measurement report, the SeNB adding procedure for the UE.
  • the MeNB sends an SeNB Add Request message to the SeNB, where the SeNB Add Request message carries the GTP information of the bearer allocated by the SGW and needs to be established on the SeNB.
  • Step S704 The SeNB sends a path update request message to the HeNB GW.
  • the path update request message carries the GTP information of the bearer that needs to be established on the SeNB and the GTP information of the bearer that needs to be established on the SeNB.
  • the path update request message may be an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • Step S706 The HeNB GW replies to the SeNB with a path update acknowledgement message, where the path update acknowledgement message carries the GTP information of the bearer that needs to be established on the SeNB, which is allocated by the HeNB GW to the SeNB and the SGW respectively.
  • the path update acknowledgement message may be an S1 interface E-RAB modification acknowledgement message, an S1 interface path transfer request acknowledgement message, or other S1 interface message.
  • Step S708 The SeNB returns an SeNB Add Request Acknowledgement message to the MeNB, where the SeNB Add Request Acknowledgement message carries the GTP information of the bearer that needs to be established on the SeNB allocated by the HeNB GW for the SGW.
  • Step S710 The MeNB initiates an RRC reconfiguration message procedure to the UE, and after the UE reconfiguration is completed, the MeNB sends an SeNB reconfiguration complete message to the SeNB.
  • Step S712 The MeNB sends a path update request message to the MME, where the path update request message carries the GTP information of the bearer that needs to be established on the SeNB, which is allocated by the received HeNB GW for the SGW.
  • the path update request message is an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • the applicable scenario of the preferred embodiment is a mobility management method in a scenario where the MeNB of the UE is unchanged and the UE moves between the SeNBs.
  • the MeNB needs to perform a SeNB replacement procedure for the UE to add a new SeNB and delete the old SeNB.
  • FIG. 8 is a schematic diagram of a scenario of a mobility management method in a scenario in which a UE's MeNB is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention. As shown in FIG.
  • the SeNB1 and the SeNB2 are HeNBs, and the UE moves from the coverage area of the SeNB1 to the coverage area of the SeNB2, and the S1 interface exists between the SeNB1/SeNB2 and the HeNBGW, where the user plane and the control plane may be included.
  • the C interface is mainly used for the S1 user plane path update of the UE.
  • FIG. 9 is a flowchart of a mobility management method in a scenario in which a UE's MeNB is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention. As shown in FIG. 9, the process may include the following processing steps:
  • the MeNB reports a measurement report to the MeNB, and the MeNB determines, according to the measurement report, that the SeNB performs a change procedure to add a new SeNB2. Delete the original SeNB1.
  • the MeNB sends an SeNB Add Request message to the SeNB2, where the SeNB Add Request message carries the GTP information of the bearer that needs to be established on the SeNB2, which is allocated by the SGW.
  • Step S904 SeNB2 returns an SeNB addition request acknowledgement message to the MeNB.
  • the MeNB initiates an SeNB release procedure to the SeNB1 to release the context of the UE on the SeNB1.
  • Step S906 The MeNB initiates an RRC reconfiguration message procedure to the UE. After the UE reconfiguration is completed, the MeNB sends an SeNB reconfiguration complete message to the SeNB2.
  • Step S908 After the SeNB2 receives the SeNB reconfiguration complete message sent by the MeNB, and the UE has accessed the SeNB2, the SeNB2 sends a path update request message to the HeNB GW, where the path update request message carries the self-allocated need in the SeNB.
  • the GTP information carried on the bearer is not limited to the SeNB.
  • the path update request message may be an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • Step S910 The HeNB GW replies to the SeNB2 with a path update acknowledgement message, where the path update acknowledgement message carries the GTP information of the bearer allocated by the HeNB GW for the SeNB and needs to be established on the SeNB2.
  • the path update confirmation message may be an S1 interface E-RAB modification confirmation message, an S1 interface path transfer request response message, or other S1 interface message.
  • FIG. 10 is a schematic diagram of another scenario in which a MeNB adds a first SeNB to a UE according to a preferred embodiment of the present invention.
  • the SeNB is a HeNB
  • a user plane S1 interface (S1-U) exists between the SeNB and the HeNB GW
  • a user plane S1 interface (S1-U) exists between the HeNB GW and the SGW.
  • 11 is a flow chart of another method of adding a first SeNB to a UE by an MeNB according to a preferred embodiment of the present invention. As shown in FIG. 11, the process may include the following processing steps:
  • Step S1102 During the mobile process of the UE, if the UE moves into the SeNB range and detects the SeNB cell, the measurement report is reported to the MeNB. The MeNB determines to perform an SeNB addition procedure for the UE according to the measurement report. The MeNB transmits an SeNB Add Request message to the SeNB.
  • Step S1104 The SeNB sends an SeNB Add Request Acknowledgement message to the MeNB, where the SeNB Add Request Acknowledgement message carries the GTP information of the bearer allocated by the SeNB and needs to be established on the SeNB.
  • Step S1106 The MeNB initiates a path update procedure to the HeNB GW.
  • the MeNB sends a path update request message to the HeNB GW, where the path update request message carries the received GTP information of the bearer allocated by the SeNB and the SGW allocated to be established on the SeNB.
  • the path update request message may be an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • Step S1108 The HeNB GW sends a path update acknowledgement message to the MeNB, where the path update acknowledgement message carries the GTP information of the bearer that needs to be established on the SeNB, which is allocated by the HeNB GW for the SeNB and the SGW respectively.
  • Step S1110 The MeNB sends the GTP information of the bearer allocated by the HeNB GW to the SeNB that needs to be established on the SeNB to the SeNB.
  • the MeNB may send the GTP information to the SeNB through an SeNB reconfiguration complete message.
  • Step S1112 The MeNB sends the GTP information of the bearer that needs to be established on the SeNB allocated by the HeNB GW to the SGW to the MME.
  • the MeNB may send the GTP information to the MME through an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • the MME and the SGW are configured to send the GTP information that the HeNB GW allocates to the SGW to the SGW, and the SGW receives the S1 interface downlink GTP tunnel information of the UE, and the information may include: an IP address and a GTP TEID.
  • the applicable scenario of the preferred embodiment is a mobility management method in which the MeNB of the UE is unchanged and the UE moves between the SeNBs.
  • the MeNB needs to perform a SeNB replacement procedure for the UE to add a new SeNB and delete the original SeNB.
  • FIG. 12 is a schematic diagram of a scenario of a mobility management method in a scenario in which a UE of a UE is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention.
  • SeNB1 and SeNB2 are HeNBs
  • the UE moves from the coverage area of SeNB1 to the SeNB2 coverage area, and there is a user plane S1 interface (S1-U) between SeNB1/SeNB2 and HeNB GW.
  • S1-U user plane S1 interface
  • FIG. 13 is a flowchart of a mobility management method in a scenario in which a UE of an UE is unchanged and a UE moves between SeNBs according to a preferred embodiment of the present invention. As shown in FIG. 13, the process may include the following processing steps:
  • Step S1302 During the movement of the UE, if the UE moves from SeNB1 to SeNB2 and detects the SeNB2 cell, the measurement report is reported to the MeNB.
  • the MeNB determines to perform a SeNB change procedure for the UE according to the measurement report to add a new SeNB2 and delete the original SeNB1.
  • the MeNB sends an SeNB Add Request message to the SeNB2, where the SeNB Add Request message carries the GTP information of the bearer allocated by the HeNB GW for the SeNB that needs to be established on the SeNB.
  • Step S1304 SeNB2 replies to the MeNB with an SeNB Add Request Acknowledgment message, where the SeNB adds an acknowledgment message carrying the GTP information of the bearer allocated by the SeNB2 and required to be established on the SeNB2.
  • Step S1306 The MeNB initiates an RRC reconfiguration message procedure to the UE, and after the UE reconfiguration is completed, the MeNB sends an SeNB reconfiguration complete message to the SeNB2.
  • Step S1308 The MeNB sends a path update request message to the HeNB GW, where the path update request message carries the GTP information of the bearer that needs to be established on the SeNB2, which is allocated by the received SeNB2.
  • the path update request message may be an S1 interface E-RAB modification indication message, an S1 interface path transfer, or other S1 interface message.
  • Step S1310 The HeNB GW returns a path update confirmation message to the MeNB.
  • the path update confirmation message may be an S1 interface E-RAB modification confirmation message, an S1 interface path transfer confirmation message, or other S1 interface message.
  • FIG. 14 is a block diagram showing the structure of a mobility management apparatus according to an embodiment of the present invention.
  • the device is applied to the secondary base station.
  • the mobility management apparatus may include: a sending module 100, configured to send, to the gateway, a first message for requesting a path update, where the first is used to request a path update.
  • the message carries the downlink GTP information of the bearer that needs to be established on itself and the received uplink GTP information of the bearer that needs to be established on the SGW.
  • the first receiving module 102 is configured to receive the reply from the gateway.
  • the first acknowledgment message where the first acknowledgment message carries the uplink and downlink GTP information of the bearer that the gateway needs to establish on itself for the secondary base station and the SGW.
  • the device shown in FIG. 14 solves the problem that the UE mobility management process in the dual connectivity architecture increases the signaling load of the core network in the related art, thereby effectively reducing the RAN and the core in the SeNB management process of the UE.
  • the S1 signaling load between the networks reduces the delay of the SeNB management process, improves the quality of service, and improves the user experience.
  • the apparatus may further include: a second receiving module 104, configured to receive a message from the primary base station for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station is carried There is an uplink GTP information of the bearer that needs to be established on the SGW.
  • a second receiving module 104 configured to receive a message from the primary base station for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station is carried There is an uplink GTP information of the bearer that needs to be established on the SGW.
  • the foregoing apparatus may further include: a replying module 106, configured to reply to the primary base station with a second acknowledgement message, where the second acknowledgement message carries a gateway that needs to be established on the SGW for the needs allocated by the SGW.
  • FIG. 16 is a block diagram showing the structure of another mobility management apparatus according to an embodiment of the present invention.
  • the device is applied to the secondary base station.
  • the mobility management apparatus may include: a sending module 200, configured to send a message for requesting a path update to the gateway, where the message for requesting the path update carries The self-distributed downlink general packet radio service tunneling protocol (GTP) information that is required to be established on the self; the first receiving module 202 is configured to receive an acknowledgment message replied by the gateway, where the acknowledgment message carries the need for the gateway to allocate the secondary base station The uplink GTP information of the bearer established on itself.
  • GTP general packet radio service tunneling protocol
  • the apparatus may further include: a second receiving module 204, configured to receive a message from the X2 interface of the primary base station to indicate completion of reconfiguration of the secondary base station, and establish a connection with the UE by itself.
  • a second receiving module 204 configured to receive a message from the X2 interface of the primary base station to indicate completion of reconfiguration of the secondary base station, and establish a connection with the UE by itself.
  • FIG. 18 is a block diagram showing the structure of another mobility management apparatus according to an embodiment of the present invention.
  • the device is applied to the primary base station.
  • the mobility management apparatus may include: a first sending module 300, configured to send a message for requesting a path update to the gateway, where the message for requesting the path update is used.
  • the first receiving module 302 Setting a first acknowledgment message replied to the receiving gateway, where the first acknowledgment message carries the uplink GTP information of the bearer that the gateway needs to establish on the secondary base station, and the need for the SGW to be established on the secondary base station
  • the foregoing apparatus may further include: a second sending module 304, configured to send, to the secondary base station, a message for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station carries the gateway Assigning the uplink GTP information of the bearer that needs to be established on the secondary base station; the second receiving module 306 is configured to receive the second acknowledgement message replied by the secondary base station, where the second acknowledgement message carries the need for the secondary base station to be allocated in the secondary base station The downlink GTP information carried on the bearer.
  • a second sending module 304 configured to send, to the secondary base station, a message for requesting the addition of the secondary base station, where the message for requesting the addition of the secondary base station carries the gateway Assigning the uplink GTP information of the bearer that needs to be established on the secondary base station
  • the second receiving module 306 is configured to receive the second acknowledgement message replied by the secondary base station, where the second acknowledgement message carries the need for the secondary base station to be allocated
  • the foregoing apparatus may further include: a third sending module 308, configured to send, to the MME, downlink GTP information that is required by the gateway for the SGW to be configured on the secondary base station.
  • a third sending module 308 configured to send, to the MME, downlink GTP information that is required by the gateway for the SGW to be configured on the secondary base station.
  • the mobility management apparatus may include: a first sending module 400, configured to send a message for requesting a path update to the gateway, where the message for requesting the path update is used. Carrying the received downlink GTP information of the bearer that needs to be established on the secondary base station, and the first receiving module 402 is configured to receive the first acknowledgment message replied by the gateway, where the first acknowledgment message carries the gateway.
  • a first sending module 400 configured to send a message for requesting a path update to the gateway, where the message for requesting the path update is used.
  • the foregoing apparatus may further include: the foregoing apparatus may further include: a second sending module 404, configured to send, to the secondary base station, a message for requesting the addition of the secondary base station, where The added message carries the uplink GTP information of the bearer that needs to be established on the secondary base station, and the second receiving module 406 is configured to receive the second acknowledgement message from the secondary base station, where the second acknowledgement message carries The downlink GTP information of the bearer to be established on the secondary base station and allocated by the secondary base station.
  • a second sending module 404 configured to send, to the secondary base station, a message for requesting the addition of the secondary base station, where The added message carries the uplink GTP information of the bearer that needs to be established on the secondary base station
  • the second receiving module 406 is configured to receive the second acknowledgement message from the secondary base station, where the second acknowledgement message carries The downlink GTP information of the bearer to be established on the secondary base station and allocated by the secondary base station.
  • the technical solutions provided by the embodiments of the present invention can be effectively
  • the S1 signaling load between the RAN and the core network in the SeNB management process of the UE is reduced, the delay of the SeNB management process is reduced, the service quality is improved, and the user experience is improved.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the mobility management method and apparatus have the following beneficial effects: the S1 signaling load between the RAN and the core network in the SeNB management process of the UE can be effectively reduced, and the SeNB management process is reduced. Delays, improve service quality and enhance user experience.

Landscapes

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

Abstract

提供一种移动性管理方法及装置，该方法包括：辅基站向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议(GTP)信息以及接收到的由信令网关(SGW)分配的需要在自身上建立的承载的上行GTP信息（S202）；辅基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息（S204）。利用本发明能够有效地减少在UE的辅基站(SeNB)管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量。

Description

移动性管理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种移动性管理方法及装置。
背景技术
随着无线多媒体业务的飞速发展，人们对高数据速率和用户体验的需求日益增长，从而对传统蜂窝网络的系统容量和覆盖提出了较高要求。在传统的长期演进(LTE)蜂窝网络中，宏基站作为唯一的接入侧网元为用户设备(UE)提供接入服务。而为了满足用户对较高数据速率的需求并提高蜂窝网络频谱效率，第三代合作伙伴计划(3GPP)引入了低功率节点(LPN)作为宏基站的补充为UE提供接入服务。LPN具有低成本、低功率以及方便部署等特点，通常可以包括热点部署和增强覆盖两种部署场景，能够有效地提高室内或室外热点区域高速率数据业务的数据速率，改善边远地区或小区边缘覆盖。通常LPN也可称为小基站，其可以包括但不限于：家庭基站(HeNB)、微微基站(pico)、射频拉远单元/头(RRU/RRH)、中继节点(RN)。在热点部署场景下，为了达到较高的数据速率和频谱效率，需要在区域内密集大量部署小基站。但是，由于小基站下小小区(small cell)的覆盖范围较小，中高速移动UE穿过小基站时发生切换失败的概率增大，从而影响UE服务连续性。为了提升引入small cell后的UE移动性能，业内提出由某个基站(例如：宏基站)保证基本覆盖，UE总是与该基站保持无线资源控制(RRC)连接，而small cell只作为传输节点(transmission point，简称为TP)以提供更高数据率并满足用户的节电需求。图1是根据相关技术的双连接架构示意图。如图1所示，在这种系统架构下，UE至少与两个基站保持连接并使用两个基站下的无线资源，从而可以实现跨节点的无线资源聚合，这种架构通常称为双连接架构。UE连接的两个基站中具有一定管理控制能力的通常称为主基站(master eNB，简称为MeNB)，另一个基站则称为辅基站(Secondary eNB，简称为SeNB)。当UE接入MeNB后，可以通过SeNB添加流程实现双连接，在SeNB添加成功后可以对该SeNB进行一系列的管理，例如：SeNB修改、SeNB删除、SeNB更改。
双连接架构下用户面有两种可能的架构，即架构option1中的1A架构，或者，架构option3中的3C架构，其中，在架构option 1中S1-U终止于MeNB和SeNB，在架构option 3中，S1-U终止于MeNB，RAN侧有承载分离，例如：EPS承载中的下行数据到达MeNB后可将一个承载中的部分数据分离至SeNB，再由SeNB发送给UE。采 用了架构option1，并且SeNB上的用户面协议栈有独立的PDCP及以下协议层，无承载分离。
另一方面，在双连接架构下，HeNB很有可能部署为MeNB或SeNB。LTE系统中家庭基站被称为HeNB(home eNB)。HeNB所支持的功能与eNB基本一致，HeNB与演进的分组核心网(Evolved Packet Core，简称为EPC)之间的进程和eNB与EPC之间基本一致。由于HeNB的布署通常没有经过移动运营商的网络规划、覆盖范围小且数量众多。为了更方便地管理并且为了支持更多数量的HeNB，在E-UTRAN(Evolved UTRAN)架构下，在HeNB与EPC的S1连接之间引入一个新的网元家庭基站网关(Home eNB Gateway，简称为HeNB GW)。HeNB可以通过HeNB GW作为S1代理连接移动管理实体(Mobility Management Entity，简称为MME)。HeNB与SGW之间的S1数据可选的终止于HeNB GW。HeNB之间存在X2直接接口可以进行负荷均衡，切换优化，信息交互等。
在采用双连接用户面架构1A情况下，在UE的移动过程中，MeNB需要为UE添加新的SeNB，或者更换为该UE服务的SeNB。由于S1用户面数据由SGW分别发送至MeNB和SeNB，即S1用户面的移动锚点位于核心网网元SGW，在SeNB添加或更改的过程中，需要由MeNB发起路径更新(path update)过程以更新SGW的S1承载信息。通常SeNB为小基站，小基站覆盖范围较小且在热点区域密集部署，UE在这种小基站大量密集部署区域内移动的场景下，若每次SeNB添加/更改过程都需要由核心网网元参与交互，将导致较大的核心网信令负荷，并造成SeNB管理过程的时延。而相关技术中尚缺乏改善双连接架构中所提出的上述问题的移动性管理方法。
发明内容
本发明实施例提供了一种移动性管理方法及装置，以至少解决相关技术中在双连接架构下的UE移动性管理流程会增加核心网信令负荷的问题。
根据本发明实施例的一个方面，提供了一种移动性管理方法。
根据本发明实施例的移动性管理方法包括：辅基站向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议(GTP)信息以及接收到的由信令网关(SGW)分配的需要在自身上建立的承载的上行GTP信息；辅基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
优选地，在辅基站向网关发送第一用于请求路径更新的消息之前，还包括：辅基站接收来自于主基站的用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有SGW分配的需要在自身上建立的承载的上行GTP信息。
优选地，在辅基站接收网关回复的第一确认消息之后，还包括：辅基站向主基站回复第二确认消息，其中，第二确认消息中携带有网关针对SGW分配的需要在自身上建立的承载的下行GTP信息。
优选地，在辅基站接收网关回复的第一确认消息之后，还包括：主基站向移动管理实体(MME)发送第二用于请求路径更新的消息，第二用于请求路径更新的消息中携带有接收到的由网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，网关为以下之一：家庭基站网关、移动锚点、双连接网关、新增网关网元。
优选地，GTP信息包括以下至少之一：互联网协议(IP)地址信息、GTP隧道端点标识(TEID)。
优选地，辅基站为家庭基站。
根据本发明实施例的另一方面，提供了另一种移动性管理方法。
根据本发明实施例的移动性管理方法包括：辅基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议(GTP)信息；辅基站接收网关回复的确认消息，其中，确认消息中携带有网关针对辅基站分配的需要在自身上建立的承载的上行GTP信息。
优选地，在辅基站向网关发送用于请求路径更新的消息之前，还包括：辅基站接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且辅基站已经与用户设备(UE)建立连接。
优选地，网关为以下之一：家庭基站网关、移动锚点、双连接网关、新增网关网元。
根据本发明实施例的又一方面，提供了另一种移动性管理方法。
根据本发明实施例的移动性管理方法包括：主基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行通用分组无线业务隧道协议(GTP)信息以及接收到的由信令网关(SGW)分配的需要在辅基站上建立的承载的上行GTP信息；主基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息以及针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，在主基站向网关发送用于请求路径更新的消息之前，还包括：主基站向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；主基站接收辅基站回复的第二确认消息，其中，第二确认消息中携带有辅基站分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，在主基站接收网关回复的第一确认消息之后，还包括：主基站将网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息发送至移动管理实体(MME)。
优选地，网关为以下之一：家庭基站网关、移动锚点、双连接网关、新增网关网元。
根据本发明实施例的再一方面，提供了另一种移动性管理方法。
根据本发明实施例的移动性管理方法包括：主基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行通用分组无线业务隧道协议(GTP)信息；主基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息。
优选地，在主基站向网关发送用于请求路径更新的消息之前，还包括：主基站向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；主基站接收来自于辅基站的第二确认消息，其中，第二确认消息中携带有由辅基站分配的需在辅基站上建立的承载的下行GTP信息。
优选地，网关为以下之一：家庭基站网关、移动锚点、双连接网关、新增网关网元。
根据本发明实施例的再一方面，提供了一种移动性管理装置。
根据本发明实施例的移动性管理装置包括：发送模块，设置为向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议(GTP)信息以及接收到的由信令网关(SGW)分配的需要在自身上建立的承载的上行GTP信息；第一接收模块，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
优选地，上述装置还包括：第二接收模块，设置为接收来自于主基站的用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有SGW分配的需要在自身上建立的承载的上行GTP信息。
优选地，上述装置还包括：回复模块，设置为向主基站回复第二确认消息，其中，第二确认消息中携带有网关针对SGW分配的需要在自身上建立的承载的下行GTP信息。
根据本发明实施例的再一方面，提供了另一种移动性管理装置。
根据本发明实施例的移动性管理装置包括：发送模块，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议(GTP)信息；第一接收模块，设置为接收网关回复的确认消息，其中，确认消息中携带有网关针对辅基站分配的需要在自身上建立的承载的上行GTP信息。
优选地，上述装置还包括：第二接收模块，设置为接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且自身已经与用户设备(UE)建立连接。
根据本发明实施例的再一方面，提供了另一种移动性管理装置。
根据本发明实施例的移动性管理装置包括：第一发送模块，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行通用分组无线业务隧道协议(GTP)信息以及接收到的由信令网关(SGW)分配的需要在辅基站上建立的承载的上行GTP信息；第一接收模块，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息以及针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，上述装置还包括：第二发送模块，设置为向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；第二接收模块，设置为接收辅基站回复的第二确认消息，其中，第二确认消息中携带有辅基站分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，上述装置还包括：第三发送模块，设置为将网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息发送至移动管理实体(MME)。
根据本发明实施例的再一方面，提供了另一种移动性管理装置。
根据本发明实施例的移动性管理装置包括：第一发送模块，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行通用分组无线业务隧道协议(GTP)信息；第一接收模块，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息。
优选地，上述装置还包括：第二发送模块，设置为向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；第二接收模块，设置为接收来自于辅基站的第二确认消息，其中，第二确认消息中携带有由辅基站分配的需在辅基站上建立的承载的下行GTP信息。
通过本发明实施例，采用辅基站向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行GTP信息以及接收到的由SGW分配的需要在自身上建立的承载的上行GTP信息；辅基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息，解决了相关技术中在双连接架构下的UE移动性管理流程会增加核心网信令负荷的问题，进而能够有效地减少在UE的SeNB管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量，提升用户体验。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的双连接架构示意图；
图2是根据本发明实施例的移动性管理方法的流程图；
图3是根据本发明实施例的另一种移动性管理方法的流程图；
图4是根据本发明实施例的另一种移动性管理方法的流程图；
图5是根据本发明实施例的另一种移动性管理方法的流程图；
图6是根据本发明优选实施例的由MeNB为UE添加首个SeNB的场景示意图；
图7是根据本发明优选实施例的由MeNB为UE添加首个SeNB的流程图；
图8是根据本发明优选本实施例的UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的场景示意图；
图9是根据本发明优选本实施例的UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的流程图；
图10是根据本发明优选实施例的另一种由MeNB为UE添加首个SeNB的场景示意图；
图11是根据本发明优选实施例的另一种由MeNB为UE添加首个SeNB的流程图；
图12是根据本发明优选本实施例的另一种UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的场景示意图；
图13是根据本发明优选本实施例的另一种UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的流程图；
图14是根据本发明实施例的移动性管理装置的结构框图；
图15是根据本发明优选实施例的移动性管理装置的结构框图；
图16是根据本发明实施例的另一种移动性管理装置的结构框图；
图17是根据本发明优选实施例的另一种移动性管理装置的结构框图；
图18是根据本发明实施例的另一种移动性管理装置的结构框图；
图19是根据本发明优选实施例的另一种移动性管理装置的结构框图；
图20是根据本发明实施例的另一种移动性管理装置的结构框图；
图21是根据本发明优选实施例的另一种移动性管理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图2是根据本发明实施例的移动性管理方法的流程图。如图2所示，该方法可以包括以下处理步骤：
步骤S202：辅基站向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行GTP信息以及接收到的由SGW分配的需要在自身上建立的承载的上行GTP信息；
步骤S204：辅基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
相关技术中，在双连接架构下的UE移动性管理流程会增加核心网信令负荷。采用如图2所示的方法，通过辅基站向网关发送携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息以及接收到的由信令网关SGW分配的需要在自身上建立的承载的上行GTP信息的用于请求路径更新的消息，以获取网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息，而避免由核心网网元直接参与交互，由此解决了相关技术中在双连接架构下的UE移动性管理流程会增加核心网信令负荷的问题，进而能够有效地减少在UE的SeNB管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量，提升用户体验。
需要说明的是，以下优选实施例适用于双连接用户面架构1A。而在下述优选实施例中网关仅以HeNB GW为例进行详细说明，但是其并不构成对本发明的不当限制。该网关还可以为移动锚点(mobility anchor)、双连接网关(DC GW)或者其它新增网关网元。MeNB或SeNB身份的HeNB可以通过HeNB GW与MME相连接，则MME与MeNB/SeNB之间交互的S1消息可以通过HeNB GW进行转发。作为MeNB或SeNB身份的HeNB可以通过X2 GW与其它基站相连接，则该MeNB/SeNB与其它基站之间交互的X2消息，该MeNB与SeNB之间交互的X2消息可以通过X2 GW转发。
在优选实施过程中，上述辅基站为家庭基站，上述GTP信息可以包括但不限于以下至少之一：
(1)互联网协议(IP)地址信息；
(2)GTP隧道端点标识(TEID)。
优选地，在步骤S202，辅基站向网关发送第一用于请求路径更新的消息之前，还可以包括以下操作：
步骤S1：辅基站接收来自于主基站的用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有SGW分配的需要在自身上建立的承载的上行GTP信息。
优选地，在步骤S204，辅基站接收网关回复的第一确认消息之后，还可以包括以下步骤：
步骤S2：辅基站向主基站回复第二确认消息，其中，第二确认消息中携带有网关针对SGW分配的需要在自身上建立的承载的下行GTP信息。
优选地，在步骤S204，辅基站接收网关回复的第一确认消息之后，还可以包括以下操作：
步骤S3：主基站向MME发送第二用于请求路径更新的消息，第二用于请求路径更新的消息中携带有接收到的由网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
需要说明的是，上述第一用于请求路径更新的消息与第二用于请求路径更新的消息中的“第一”和“第二”仅用于表示发送用于请求路径更新的消息的执行主体不同，以及消息中携带的信息不同，而并非表示两种消息的类型不同，其均为具有请求路径更新功能的消息。同理，上述第一确认消息和第二确认消息中的“第一”和“第二”仅用于表示发送确认消息的执行主体不同，以及消息中携带的信息不同，而并非表示两种消息的类型不同，其均为具有确认功能的消息。
在优选实施过程中，第一用于请求路径更新的消息或第二用于请求路径更新的消息可以为以下类型之一：
(1)S1接口E-RAB修改指示消息；
(2)S1接口路径转移消息；
(3)其它S1接口消息。
图3是根据本发明实施例的另一种移动性管理方法的流程图。如图3所示，该方法可以包括以下处理步骤：
步骤S302：辅基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行GTP信息；
步骤S304：辅基站接收网关回复的确认消息，其中，确认消息中携带有网关针对辅基站分配的需要在自身上建立的承载的上行GTP信息。
优选地，在辅基站向网关发送用于请求路径更新的消息之前，还可以包括以下操作：
步骤S4：辅基站接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且辅基站已经与UE建立连接。
在优选实施过程中，上述用于请求路径更新的消息可以为以下类型之一：
(1)S1接口E-RAB修改指示消息；
(2)S1接口路径转移消息；
(3)其它S1接口消息。
图4是根据本发明实施例的另一种移动性管理方法的流程图。如图4所示，该方法可以包括以下处理步骤：
步骤S402：主基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行GTP信息以及接收到的由SGW分配的需要在辅基站上建立的承载的上行GTP信息；
步骤S404：主基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息以及针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
在优选实施过程中，上述用于请求路径更新的消息可以为以下类型之一：
(1)S1接口E-RAB修改指示消息；
(2)S1接口路径转移消息；
(3)其它S1接口消息。
优选地，在步骤S402，主基站向网关发送用于请求路径更新的消息之前，还可以包括：
步骤S5：主基站向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；
步骤S6：主基站接收辅基站回复的第二确认消息，其中，第二确认消息中携带有辅基站分配的需要在辅基站上建立的承载的下行GTP信息。即MeNB可以通过SeNB重配置完成消息将下行GTP信息发送至SeNB。
优选地，在步骤S404，主基站接收网关回复的第一确认消息之后，还可以包括以下步骤：
步骤S7：主基站将网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息发送至MME。即MeNB可以通过S1接口E-RAB修改指示消息、S1接口路径转移消息、或者其它S1接口消息将下行GTP信息发送至MME。
图5是根据本发明实施例的另一种移动性管理方法的流程图。如图5所示，该方法可以包括以下处理步骤：
步骤S502：主基站向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行GTP信息；
步骤S504：主基站接收网关回复的第一确认消息，其中，第一确认消息中携带有网关针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息。
优选地，在步骤S502，主基站向网关发送用于请求路径更新的消息之前，还可以包括以下操作：
步骤S8：主基站向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；
步骤S9：主基站接收来自于辅基站的第二确认消息，其中，第二确认消息中携带有由辅基站分配的需在辅基站上建立的承载的下行GTP信息。
下面将结合以下几个优选实施方式对上述优选实施过程作进一步的说明。
优选实施例一
该优选实施例所适用场景是由MeNB为UE添加首个SeNB。图6是根据本发明优选实施例的由MeNB为UE添加首个SeNB的场景示意图。如图6所示，SeNB为HeNB，且SeNB与HeNB GW之间存在S1接口，其中，可以包括：用户面和控制面，该S1-C接口主要用于UE的S1用户面路径更新。而HeNB GW与MME之间不存在UE相关的S1连接，HeNB GW与SGW之间存在S1用户面接口。图7是根据本发明优选实施例的由MeNB为UE添加首个SeNB的流程图。如图7所示，该流程可以包括以下处理步骤：
步骤S702：在UE的移动过程中，若UE移动到SeNB范围内并检测到SeNB小区，则向MeNB上报测量报告，MeNB根据测量报告确定为UE执行SeNB添加流程。MeNB向SeNB发送SeNB添加请求消息，其中，该SeNB添加请求消息中携带有SGW分配的需要在SeNB上建立的承载的GTP信息。
步骤S704：SeNB向HeNB GW发送路径更新请求消息。该路径更新请求消息中携带有自身分配的需要在SeNB上建立的承载的GTP信息以及接收到的SGW分配的需在SeNB上建立的承载的GTP信息。
在该优选实施例中，上述路径更新请求消息可以为S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息。
步骤S706：HeNB GW向SeNB回复路径更新确认消息，其中，该路径更新确认消息中携带有HeNB GW分别针对SeNB与SGW分配的需要在SeNB上建立的承载的GTP信息。
在该优选实施例中，上述路径更新确认消息可以为S1接口E-RAB修改确认消息、S1接口路径转移请求确认消息、或者其它S1接口消息。
步骤S708：SeNB向MeNB回复SeNB添加请求确认消息，其中，该SeNB添加请求确认消息中携带有HeNB GW针对SGW分配的需要在SeNB上建立的承载的GTP信息。
步骤S710：MeNB向UE发起RRC重配置消息过程，并在UE重配置完成后，MeNB向SeNB发送SeNB重配置完成消息。
步骤S712：MeNB向MME发送路径更新请求消息，其中，该路径更新请求消息中携带有接收到的HeNB GW针对SGW分配的需要在SeNB上建立的承载的GTP信息。
在该优选实施例中，上述路径更新请求消息为S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息。
优选实施例二
该优选实施例的适用场景是UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法，MeNB需为UE执行SeNB更换流程，以添加新的SeNB，删除旧的SeNB。图8是根据本发明优选本实施例的UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的场景示意图。如图8所示，SeNB1和SeNB2为HeNB，UE从SeNB1的覆盖区域移动到SeNB2覆盖区域，SeNB1/SeNB2与HeNB GW之间存在S1接口，其中，可以包括：用户面和控制面，该S1-C接口主要用于UE的S1用户面路径更新。而HeNB GW与MME之间不存在UE相关的S1连接，HeNB GW与SGW之间存在S1用户面接口。图9是根据本发明优选本实施例的UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的流程图。如图9所示，该流程可以包括以下处理步骤：
步骤S902：在UE的移动过程中，若UE从SeNB1移动到SeNB2范围内并检测到SeNB2小区，则向MeNB上报测量报告，MeNB根据测量报告确定为UE执行SeNB更改流程，以添加新的SeNB2并删除原有的SeNB1。MeNB向SeNB2发送SeNB添加请求消息，其中，该SeNB添加请求消息中携带有SGW分配的需要在SeNB2上建立的承载的GTP信息。
步骤S904：SeNB2向MeNB回复SeNB添加请求确认消息。另外，MeNB接收到SeNB添加请求确认消息后向SeNB1发起SeNB释放流程，以释放SeNB1上该UE的上下文。
步骤S906：MeNB向UE发起RRC重配置消息过程，在UE重配置完成后，MeNB向SeNB2发送SeNB重配置完成消息。
步骤S908：在SeNB2接收到MeNB发送的SeNB重配置完成消息，且UE已经接入SeNB2后，SeNB2向HeNB GW发送路径更新请求消息，其中，该路径更新请求消息中携带有自身分配的需要在SeNB上建立的承载的GTP信息。
在该优选实施例中，上述路径更新请求消息可以为S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息。
步骤S910：HeNB GW向SeNB2回复路径更新确认消息，其中，该路径更新确认消息中携带有HeNB GW针对SeNB分配的需要在该SeNB2上建立的承载的GTP信息。
在该优选实施例中，上述路径更新确认消息可以为S1接口E-RAB修改确认消息、S1接口路径转移请求响应消息、或者其它S1接口消息。
优选实施例三
该本实施例的适用场景是由MeNB为UE添加首个SeNB场景。图10是根据本发明优选实施例的另一种由MeNB为UE添加首个SeNB的场景示意图。如图10所示，SeNB为HeNB，SeNB与HeNB GW之间存在用户面S1接口(S1-U)，且HeNB GW与SGW之间存在用户面S1接口(S1-U)。MeNB与HeNB GW之间存在控制面S1接口(S1-C)。图11是根据本发明优选实施例的另一种由MeNB为UE添加首个SeNB的流程图。如图11所示，该流程可以包括以下处理步骤：
步骤S1102：在UE的移动过程中，若UE移动到SeNB范围内并检测到SeNB小区，则向MeNB上报测量报告。MeNB根据测量报告确定为UE执行SeNB添加流程。MeNB向SeNB发送SeNB添加请求消息。
步骤S1104：SeNB向MeNB发送SeNB添加请求确认消息，其中，该SeNB添加请求确认消息中携带有SeNB分配的需要在SeNB上建立的承载的GTP信息。
步骤S1106：MeNB向HeNB GW发起路径更新过程。MeNB向HeNB GW发送路径更新请求消息，其中，该路径更新请求消息中携带有接收到的SeNB分配的以及SGW分配的需要在SeNB上建立的承载的GTP信息。
在该优选实施例中，上述路径更新请求消息可以为S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息。
步骤S1108：HeNB GW向MeNB发送路径更新确认消息，其中，该路径更新确认消息中携带有HeNB GW分别针对SeNB以及SGW分配的需要在SeNB上建立的承载的GTP信息。
步骤S1110：MeNB将HeNB GW针对SeNB分配的需要在SeNB上建立的承载的GTP信息发送至SeNB。
在优选实施过程中，MeNB可以通过SeNB重配置完成消息将该GTP信息发送至SeNB。
步骤S1112：MeNB将HeNB GW针对SGW分配的需要在SeNB上建立的承载的GTP信息发送至MME。MeNB可以通过S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息将所述GTP信息发送至MME。然后通过MME与SGW交互将HeNB GW针对SGW分配的GTP信息发送至SGW，SGW接收后更新该UE的S1接口下行GTP隧道信息，其中，可以包括：IP地址及GTP TEID。
需要说明的是，上述步骤S1110与上述步骤S1112之间并没有明确限定其先后顺序。
优选实施例四
该优选实施例的适用场景是UE的MeNB不变，UE在SeNB之间移动的移动性管理方法。MeNB需为UE执行SeNB更换流程，以添加新的SeNB并删除原有的SeNB。图12是根据本发明优选本实施例的另一种UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的场景示意图。如图12所示，SeNB1和SeNB2为HeNB，UE从SeNB1的覆盖区域移动到SeNB2覆盖区域，SeNB1/SeNB2与HeNB GW之间存在用户面S1接口(S1-U)。HeNB GW与SGW之间也存在S1用户面接口。MeNB与HeNB GW之间存在控制面S1接口，主要用于S1-U用户面路径更新。图13是根据本发明优选本实施例的另一种UE的MeNB不变，UE在SeNB之间移动的场景下的移动性管理方法的流程图。如图13所示，该流程可以包括以下处理步骤：
步骤S1302：在UE的移动过程中，若UE从SeNB1移动到SeNB2范围内并检测到SeNB2小区，则向MeNB上报测量报告。MeNB根据测量报告确定为UE执行SeNB更改流程，以添加新的SeNB2并删除原有的SeNB1。MeNB向SeNB2发送SeNB添加请求消息，其中，该SeNB添加请求消息中携带有HeNB GW针对SeNB分配的需要在SeNB上建立的承载的GTP信息。
步骤S1304：SeNB2向MeNB回复SeNB添加请求确认消息，其中，该SeNB添加确认消息中携带有SeNB2分配的需要在SeNB2上建立的承载的GTP信息。
步骤S1306：MeNB向UE发起RRC重配置消息过程，在UE重配置完成后MeNB向SeNB2发送SeNB重配置完成消息。
步骤S1308：MeNB向HeNB GW发送路径更新请求消息，其中，该路径更新请求消息中携带有接收到的SeNB2分配的需要在SeNB2上建立的承载的GTP信息。
在该优选实施例中，上述路径更新请求消息可以为S1接口E-RAB修改指示消息、S1接口路径转移、或者其它S1接口消息。
步骤S1310：HeNB GW向MeNB回复路径更新确认消息。
在该优选实施例中，上述路径更新确认消息可以为S1接口E-RAB修改确认消息、S1接口路径转移确认消息、或者其它S1接口消息。
图14是根据本发明实施例的移动性管理装置的结构框图。该装置应用于辅基站，如图14所示，该移动性管理装置可以包括：发送模块100，设置为向网关发送第一用于请求路径更新的消息，其中，第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行GTP信息以及接收到的由SGW分配的需要在自身上建立的承载的上行GTP信息；第一接收模块102，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站与SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
采用如图14所示的装置，解决了相关技术中在双连接架构下的UE移动性管理流程会增加核心网信令负荷的问题，进而能够有效地减少在UE的SeNB管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量，提升用户体验。
优选地，如图15所示，上述装置还可以包括：第二接收模块104，设置为接收来自于主基站的用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有SGW分配的需要在自身上建立的承载的上行GTP信息。
优选地，如图15所示，上述装置还可以包括：回复模块106，设置为向主基站回复第二确认消息，其中，第二确认消息中携带有网关针对SGW分配的需要在自身上建立的承载的下行GTP信息。
图16是根据本发明实施例的另一种移动性管理装置的结构框图。该装置应用于辅基站，如图16所示，该移动性管理装置可以包括：发送模块200，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息；第一接收模块202，设置为接收网关回复的确认消息，其中，确认消息中携带有网关针对辅基站分配的需要在自身上建立的承载的上行GTP信息。
优选地，如图17所示，上述装置还可以包括：第二接收模块204，设置为接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且自身已经与UE建立连接。
图18是根据本发明实施例的另一种移动性管理装置的结构框图。该装置应用于主基站，如图18所示，该移动性管理装置可以包括：第一发送模块300，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行GTP信息以及接收到的由SGW分配的需要在辅基站上建立的承载的上行GTP信息；第一接收模块302，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关分别针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息以及针对SGW分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，如图19所示，上述装置还可以包括：第二发送模块304，设置为向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；第二接收模块306，设置为接收辅基站回复的第二确认消息，其中，第二确认消息中携带有辅基站分配的需要在辅基站上建立的承载的下行GTP信息。
优选地，如图19所示，上述装置还可以包括：第三发送模块308，设置为将网关针对SGW分配的需要在辅基站上建立的承载的下行GTP信息发送至MME。
图20是根据本发明实施例的另一种移动性管理装置的结构框图。该装置应用于主基站，如图20所示，该移动性管理装置可以包括：第一发送模块400，设置为向网关发送用于请求路径更新的消息，其中，用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在辅基站上建立的承载的下行GTP信息；第一接收模块402，设置为接收网关回复的第一确认消息，其中，第一确认消息中携带有网关针对辅基站分配的需要在辅基站上建立的承载的上行GTP信息。
优选地，如图21所示，上述装置还可以包括：上述装置还可以包括：第二发送模块404，设置为向辅基站发送用于请求辅基站添加的消息，其中，用于请求辅基站添 加的消息中携带有网关分配的需要在辅基站上建立的承载的上行GTP信息；第二接收模块406，设置为接收来自于辅基站的第二确认消息，其中，第二确认消息中携带有由辅基站分配的需在辅基站上建立的承载的下行GTP信息。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，能够有效地减少在UE的SeNB管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量，提升用户体验。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种移动性管理方法及装置具有以下有益效果：能够有效地减少在UE的SeNB管理流程中RAN与核心网之间的S1信令负荷，降低SeNB管理流程的延时，提高服务质量，提升用户体验。

Claims (27)

  1. 一种移动性管理方法，包括：
    辅基站向网关发送第一用于请求路径更新的消息，其中，所述第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息以及接收到的由信令网关SGW分配的需要在自身上建立的承载的上行GTP信息；
    所述辅基站接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关分别针对所述辅基站与所述SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
  2. 根据权利要求1所述的方法，其中，在所述辅基站向所述网关发送所述第一用于请求路径更新的消息之前，还包括：
    所述辅基站接收来自于主基站的用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述SGW分配的需要在自身上建立的承载的上行GTP信息。
  3. 根据权利要求1所述的方法，其中，在所述辅基站接收所述网关回复的所述第一确认消息之后，还包括：
    所述辅基站向主基站回复第二确认消息，其中，所述第二确认消息中携带有所述网关针对所述SGW分配的需要在自身上建立的承载的下行GTP信息。
  4. 根据权利要求1所述的方法，其中，在所述辅基站接收所述网关回复的所述第一确认消息之后，还包括：
    主基站向移动管理实体MME发送第二用于请求路径更新的消息，所述第二用于请求路径更新的消息中携带有接收到的由所述网关针对所述SGW分配的需要在所述辅基站上建立的承载的下行GTP信息。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述网关为以下之一：
    家庭基站网关、移动锚点、双连接网关、新增网关网元。
  6. 根据权利要求1至4中任一项所述的方法，其中，GTP信息包括以下至少之一：互联网协议IP地址信息、GTP隧道端点标识TEID。
  7. 根据权利要求1至4中任一项所述的方法，其中，所述辅基站为家庭基站。
  8. 一种移动性管理方法，包括：
    辅基站向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息；
    所述辅基站接收所述网关回复的确认消息，其中，所述确认消息中携带有所述网关针对所述辅基站分配的需要在自身上建立的承载的上行GTP信息。
  9. 根据权利要求8所述的方法，其中，在所述辅基站向所述网关发送所述用于请求路径更新的消息之前，还包括：
    所述辅基站接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且所述辅基站已经与用户设备UE建立连接。
  10. 根据权利要求8或9所述的方法，其中，所述网关为以下之一：
    家庭基站网关、移动锚点、双连接网关、新增网关网元。
  11. 一种移动性管理方法，包括：
    主基站向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在所述辅基站上建立的承载的下行通用分组无线业务隧道协议GTP信息以及接收到的由信令网关SGW分配的需要在所述辅基站上建立的承载的上行GTP信息；
    所述主基站接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关分别针对所述辅基站分配的需要在所述辅基站上建立的承载的上行GTP信息以及针对所述SGW分配的需要在所述辅基站上建立的承载的下行GTP信息。
  12. 根据权利要求11所述的方法，其中，在所述主基站向所述网关发送所述用于请求路径更新的消息之前，还包括：
    所述主基站向所述辅基站发送用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述网关分配的需要在所述辅基站上建立的承载的上行GTP信息；
    所述主基站接收所述辅基站回复的第二确认消息，其中，所述第二确认消息中携带有所述辅基站分配的需要在所述辅基站上建立的承载的下行GTP信息。
  13. 根据权利要求11所述的方法，其中，在所述主基站接收所述网关回复的所述第一确认消息之后，还包括：
    所述主基站将所述网关针对所述SGW分配的需要在所述辅基站上建立的承载的下行GTP信息发送至移动管理实体MME。
  14. 根据权利要求11至13中任一项所述的方法，其中，所述网关为以下之一：
    家庭基站网关、移动锚点、双连接网关、新增网关网元。
  15. 一种移动性管理方法，包括：
    主基站向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在所述辅基站上建立的承载的下行通用分组无线业务隧道协议GTP信息；
    所述主基站接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关针对所述辅基站分配的需要在所述辅基站上建立的承载的上行GTP信息。
  16. 根据权利要求15所述的方法，其中，在所述主基站向所述网关发送所述用于请求路径更新的消息之前，还包括：
    所述主基站向所述辅基站发送用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述网关分配的需要在所述辅基站上建立的承载的上行GTP信息；
    所述主基站接收来自于所述辅基站的第二确认消息，其中，所述第二确认消息中携带有由所述辅基站分配的需在所述辅基站上建立的承载的下行GTP信息。
  17. 根据权利要求15或16所述的方法，其中，所述网关为以下之一：
    家庭基站网关、移动锚点、双连接网关、新增网关网元。
  18. 一种移动性管理装置，所述装置应用于辅基站，包括：
    发送模块，设置为向网关发送第一用于请求路径更新的消息，其中，所述第一用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息以及接收到的由信令网关SGW分配的需要在自身上建立的承载的上行GTP信息；
    第一接收模块，设置为接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关分别针对所述辅基站与所述SGW分配的需要在自身上建立的承载的上行及下行GTP信息。
  19. 根据权利要求18所述的装置，其中，所述装置还包括：
    第二接收模块，设置为接收来自于主基站的用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述SGW分配的需要在自身上建立的承载的上行GTP信息。
  20. 根据权利要求18所述的装置，其中，所述装置还包括：
    回复模块，设置为向主基站回复第二确认消息，其中，所述第二确认消息中携带有所述网关针对所述SGW分配的需要在自身上建立的承载的下行GTP信息。
  21. 一种移动性管理装置，所述装置应用于辅基站，包括：
    发送模块，设置为向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有自身分配的需要在自身上建立的承载的下行通用分组无线业务隧道协议GTP信息；
    第一接收模块，设置为接收所述网关回复的确认消息，其中，所述确认消息中携带有所述网关针对所述辅基站分配的需要在自身上建立的承载的上行GTP信息。
  22. 根据权利要求21所述的装置，其中，所述装置还包括：
    第二接收模块，设置为接收来自于主基站的X2接口用于指示辅基站重配置完成的消息，且自身已经与用户设备UE建立连接。
  23. 一种移动性管理装置，所述装置应用于主基站，包括：
    第一发送模块，设置为向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在所述辅基站 上建立的承载的下行通用分组无线业务隧道协议GTP信息以及接收到的由信令网关SGW分配的需要在所述辅基站上建立的承载的上行GTP信息；
    第一接收模块，设置为接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关分别针对所述辅基站分配的需要在所述辅基站上建立的承载的上行GTP信息以及针对所述SGW分配的需要在所述辅基站上建立的承载的下行GTP信息。
  24. 根据权利要求23所述的装置，其中，所述装置还包括：
    第二发送模块，设置为向所述辅基站发送用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述网关分配的需要在所述辅基站上建立的承载的上行GTP信息；
    第二接收模块，设置为接收所述辅基站回复的第二确认消息，其中，所述第二确认消息中携带有所述辅基站分配的需要在所述辅基站上建立的承载的下行GTP信息。
  25. 根据权利要求23所述的装置，其中，所述装置还包括：
    第三发送模块，设置为将所述网关针对所述SGW分配的需要在所述辅基站上建立的承载的下行GTP信息发送至移动管理实体MME。
  26. 一种移动性管理装置，所述装置应用于主基站，包括：
    第一发送模块，设置为向网关发送用于请求路径更新的消息，其中，所述用于请求路径更新的消息中携带有接收到的由辅基站分配的需要在所述辅基站上建立的承载的下行通用分组无线业务隧道协议GTP信息；
    第一接收模块，设置为接收所述网关回复的第一确认消息，其中，所述第一确认消息中携带有所述网关针对所述辅基站分配的需要在所述辅基站上建立的承载的上行GTP信息。
  27. 根据权利要求26所述的装置，其中，所述装置还包括：
    第二发送模块，设置为向所述辅基站发送用于请求辅基站添加的消息，其中，所述用于请求辅基站添加的消息中携带有所述网关分配的需要在所述辅基站上建立的承载的上行GTP信息；
    第二接收模块，设置为接收来自于所述辅基站的第二确认消息，其中，所述第二确认消息中携带有由所述辅基站分配的需在所述辅基站上建立的承载的下行GTP信息。
PCT/CN2015/077531 2014-12-25 2015-04-27 移动性管理方法及装置 Ceased WO2016101468A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410830879.2A CN105792175A (zh) 2014-12-25 2014-12-25 移动性管理方法及装置
CN201410830879.2 2014-12-25

Publications (1)

Publication Number Publication Date
WO2016101468A1 true WO2016101468A1 (zh) 2016-06-30

Family

ID=56149071

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/077531 Ceased WO2016101468A1 (zh) 2014-12-25 2015-04-27 移动性管理方法及装置

Country Status (2)

Country Link
CN (1) CN105792175A (zh)
WO (1) WO2016101468A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101287294A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 移动管理实体、终端转移方法和系统
CN101325592A (zh) * 2007-06-14 2008-12-17 华为技术有限公司 一种建立承载连接的方法、装置及系统
CN101534495A (zh) * 2008-03-10 2009-09-16 大唐移动通信设备有限公司 一种用户设备的业务承载建立方法及装置
CN102083051A (zh) * 2010-03-15 2011-06-01 大唐移动通信设备有限公司 一种业务通路切换方法及其装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10893556B2 (en) * 2009-04-30 2021-01-12 Samsung Electronics Co., Ltd Method and apparatus for supporting local IP access in a femto cell of a wireless communication system
CN102905329A (zh) * 2011-07-29 2013-01-30 北京三星通信技术研究有限公司 一种支持切换的方法
US10575228B2 (en) * 2012-12-28 2020-02-25 Nec Corporation Radio communication system, base station, mobile station, communication control method, and computer readable medium
CN104185227B (zh) * 2014-04-14 2020-05-15 中兴通讯股份有限公司 一种双连接架构下的csg接入控制方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101325592A (zh) * 2007-06-14 2008-12-17 华为技术有限公司 一种建立承载连接的方法、装置及系统
CN101534495A (zh) * 2008-03-10 2009-09-16 大唐移动通信设备有限公司 一种用户设备的业务承载建立方法及装置
CN101287294A (zh) * 2008-06-11 2008-10-15 中兴通讯股份有限公司 移动管理实体、终端转移方法和系统
CN102083051A (zh) * 2010-03-15 2011-06-01 大唐移动通信设备有限公司 一种业务通路切换方法及其装置

Also Published As

Publication number Publication date
CN105792175A (zh) 2016-07-20

Similar Documents

Publication Publication Date Title
US11076334B2 (en) Data forwarding method, device, and communications system
US10595239B2 (en) Data transmission method and device
CN106100816B (zh) 实现载波聚合的方法、基站和用户设备
EP2787763B1 (en) Methods and devices for providing simultaneous connectivity between multiple E-NodeBs and user equipment
CN104255056B (zh) 切换方法和设备
WO2018188613A1 (zh) 一种移动性管理方法、接入网设备和终端设备
CN105453643B (zh) 用于数据流的设置或修改的方法和系统、主节点、辅节点、ue以及计算机程序产品
CN108184249B (zh) 回程链路的信息传输方法及系统、代理设备、接入设备
WO2016119109A1 (zh) 一种切换装置及方法
EP3425947B1 (en) Method and apparatus for managing wireless resources
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
CN104640165B (zh) 一种数据传输方法、设备和系统
KR20120000859A (ko) 무선 통신 시스템 및 그 시스템에서 핸드오버 수행 방법
JP6290413B2 (ja) 接続管理方法及びアクセスネットワークエレメント
EP3267724A1 (en) Data transmission method for use during base station handover, user device and base station, and storage medium
CN116235543A (zh) 群组切换的方法、装置和系统
WO2023108354A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2016101586A1 (zh) 一种基站切换方法、系统及相关装置、存储介质
WO2020078220A1 (zh) 一种数据处理方法及装置、网络设备
WO2016161785A1 (zh) 跨MeNB切换方法、装置及基站
CN107810658A (zh) 多连接性
WO2016155481A1 (zh) 用户数据的传输处理方法、装置、系统及计算机存储介质
WO2016107144A1 (zh) 用户面路径的更新方法、装置及系统
CN112868253B (zh) 条件触发的配置方法及相关产品

Legal Events

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

Ref document number: 15871544

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15871544

Country of ref document: EP

Kind code of ref document: A1