WO2012167648A1 - 一种进行lipa承载接入控制的方法、系统和设备 - Google Patents

一种进行lipa承载接入控制的方法、系统和设备 Download PDF

Info

Publication number
WO2012167648A1
WO2012167648A1 PCT/CN2012/073054 CN2012073054W WO2012167648A1 WO 2012167648 A1 WO2012167648 A1 WO 2012167648A1 CN 2012073054 W CN2012073054 W CN 2012073054W WO 2012167648 A1 WO2012167648 A1 WO 2012167648A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
user equipment
target base
lgw
lipa
Prior art date
Application number
PCT/CN2012/073054
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 电信科学技术研究院
Publication of WO2012167648A1 publication Critical patent/WO2012167648A1/zh

Links

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
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a method, system and device for performing LIPA bearer access control. Background technique
  • the UE User Equipment
  • H(e)B (evolved) home base station) without transmitting user data through the carrier network.
  • FIG. 1A an architecture diagram of a UE accessing through a Local IP Access (LIP) mode is shown.
  • LIP Local IP Access
  • the L-GW (Local-Gateway) is located in the home or enterprise and connects to the home or enterprise IP network through the SGi interface.
  • the L-GW function is similar to the PGW (PDN GW, Packet Data Gateway).
  • PGW Packet Data Network
  • the MME Mobility Management Entity
  • the LGW returns a response message to the SGW, and the SGW returns a response message to the MME upon receipt.
  • the MME requests the HeNB to establish the S1 and air interface bearers of the default bearer of the LIPA PDN connection for the UE.
  • the HeNB establishes a direct tunnel between the HeNB and the L-GW.
  • the UE transmits LIPA data in the connected state
  • the data is transmitted from the UE to the HeNB, and is directly transmitted to the L-GW through the direct tunnel between the HeNB and the L-GW without passing through the SGW.
  • the L-GW also sends data to the HeNB through the direct tunnel between the L-GW and the HeNB without passing through the SGW.
  • the S5 interface established between the L-GW and the SGW is used only when the UE enters the idle state.
  • the direct tunnel between the HeNB and the L-GW will be removed, and the L-GW only reserves the S5 connection to the SGW.
  • the L-GW receives the downlink data of the LIPA PDN connection
  • the L-GW transmits the first data packet received to the SGW through the S5 interface, triggering the normal paging process, except for the first data packet. All packets outside will remain in the L-GW.
  • the direct tunnel between the HeNB and the L-GW will be re-established.
  • the SGW sends the first data packet sent from the L-GW to the HeNB, and the remaining other data packets are transmitted by the L-GW to the He B through a direct tunnel between the L-GW and the HeNB.
  • the 3GPP (3rd Generation Partnership Project) protocol proposes mobility requirements for LIPA connections, and requires UEs to maintain continuity of LIPA connections when moving between different HeNBs under the same local IP network. As shown in FIG. 1B, it is assumed that all the four HeNBs in the following figure belong to the same local network. If the UE activates the LIPA connection, when the UE moves between the following four HeNBs, whether it is idle or connected, the UE The LIPA connection cannot cause the LIPA connection to be released due to the UE's movement.
  • an X2 interface or an Iur interface is established between HeNBs that allow the same CSG (Close Subscriber Group), and HeNBs between different CSGs are not allowed to establish X2 interfaces and Iur interfaces between base stations. interface. Therefore, when the UE moves between different HeNBs in the same CSG, the source HeNB can initiate an X2 interface switch or an Iur interface switch, and when HeNBs move between different CSGs, the source HeNB can only initiate. S 1 interface switching.
  • the embodiments of the present invention provide a method, system, and device for performing LIPA bearer access control, which are used to process a LIPA connection when a UE moves in the same CSG cell in a handover process, but moves to a new local network. .
  • the method for performing the local IP access LIPA bearer access control includes: after receiving the notification message, the first network side device determines that the target base station after the user equipment is switched and establishes a LIPA connection for the user equipment. Whether there is an IP connection between the local gateways LGW;
  • the first network side device After determining that the target base station has an IP connection with the LGW, the first network side device performs an interface switching process
  • the source base station to which the user equipment belongs is the same as the closed and subscribed user group CSG of the target base station, and both support the same type of interface switching.
  • the second network side device determines the user equipment that performs interface switching
  • the second network side device sends a notification message to the first network side device, to notify the first network side device that when the target base station after the user equipment handover has an IP connection with the local gateway LGW that establishes the LIPA connection for the user equipment, Perform an interface switching process;
  • the source base station to which the user equipment belongs is the same as the closed and subscribed user group CSG of the target base station, and both support Switch the same interface.
  • a determining module configured to determine, after receiving the notification message, whether there is an IP connection between the target base station after the user equipment switching and the local gateway LGW that establishes a LIPA connection for the user equipment;
  • a processing module configured to perform an interface switching process after determining that an IP connection exists between the target base station and the LGW;
  • the source base station to which the user equipment belongs is the same as the closed and subscribed user group CSG of the target base station, and both support the same type of interface switching.
  • a determining module configured to determine a user equipment that performs interface switching
  • a notification module configured to send a notification message to the first network side device, to notify the first network side device to perform an interface when the target base station after the user equipment handover has an IP connection with the local gateway LGW that establishes the LIPA connection for the user equipment Switching process
  • the source base station to which the user equipment belongs is the same as the closed and subscribed user group CSG of the target base station, and both support the same type of interface switching.
  • the first network side device is configured to: after receiving the notification message, determine whether there is an IP connection between the target base station after the user equipment switching and the LGW that establishes the LIPA connection for the user equipment, and determine the target base station and the LGW. After the IP connection is established, the interface switching process is performed;
  • a second network side device configured to send a notification message to the first network side device after determining the user equipment that performs interface switching
  • the source base station to which the user equipment belongs is the same as the closed and subscribed user group CSG of the target base station, and both support the same type of interface switching.
  • the first network side device Perform the interface switching process. Since the embodiment of the present invention moves the UE to the same CSG cell during the handover process, but moves to the new local network, the LIPA connection can be processed, thereby improving network performance and expanding the processing capability of the network.
  • FIG. 1A is a schematic diagram of a UE accessing a LIPA architecture through a He B in the background art
  • FIG. 1B is a schematic diagram of multiple HeNBs belonging to the same local network in the background art
  • FIG. 2 is a schematic structural diagram of a system for performing LIPA bearer access control according to an embodiment of the present invention
  • 3 is a schematic structural diagram of a first network side device according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a second network side device according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for performing LIPA bearer access control according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for performing LIPA bearer access control according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of X2 interface switching according to an embodiment of the present invention. detailed description
  • the source base station to which the user equipment belongs and the CSG of the target base station are the same, both support the same type of interface switching, and the target base station after the user equipment is switched has an IP connection with the LGW that establishes the LIPA connection for the user equipment, A network side device performs an interface switching process. Since the embodiment of the present invention moves the same CSG cell in the handover process, but moves to a new local network, the LIPA connection can be processed, thereby improving network performance and expanding the processing capability of the network.
  • the interface switching in the embodiment of the present invention is an X2 interface switching.
  • the base station in the embodiment of the present invention is a home base station or an evolved home base station, and the core network in the embodiment of the present invention.
  • the control entity is an MME (Mobility Management Entity);
  • the interface switching in the embodiment of the present invention is an Iur interface switch.
  • the base station in the embodiment of the present invention is a home base station, and the core network control entity in the embodiment of the present invention is an SGSN ( Serving GPRS Support Node, Serving GPRS Service Node).
  • SGSN Serving GPRS Support Node, Serving GPRS Service Node
  • the LIPA bearer access control system includes: a first network side device 10 and a second network side device 20.
  • the first network side device 10 is configured to determine, after receiving the notification message from the second network side device 20, whether there is an IP connection between the target base station after the user equipment switching and the LGW that establishes the LIPA connection for the user equipment, and After determining that there is an IP connection between the target base station and the LGW, perform an interface switching process;
  • the second network side device 20 is configured to determine a user equipment that performs interface switching, and send a notification message to the first network side device 10;
  • the source base station to which the user equipment belongs and the CSG of the target base station are the same, and both support the same type of interface switching.
  • the second network side device is configured.
  • the device 20 is the source base station to which the user equipment belongs (ie, the base station before handover, the same below), and the notification message is a handover request message;
  • the first network side device 10 is an LGW that establishes a LIPA connection for the user equipment
  • the second network side device 20 is a source base station to which the user equipment belongs, and the notification message includes the target base station information;
  • the second network side device 20 is a target base station after the user equipment is switched, and the notification message is path switching information.
  • Case 1 The first network side device 10 is the target base station after the user equipment is switched, and the second network side device 20 is the source base station to which the user equipment belongs, and the notification message is a handover request message.
  • the source base station determines that the user equipment needs to perform the handover, and the source base station to which the user equipment belongs is the same as the CSG of the target base station, and both support the same type of interface switching, and check whether the user equipment that needs to be switched has the activated LIPA. ⁇
  • the source base station adds the information of the LGW that establishes the LIPA connection to the user equipment in the handover request message; otherwise, the information of the LGW that establishes the LIPA connection for the user equipment is not added in the handover request message.
  • the information of the LGW that establishes the LIPA connection for the user equipment may be an IP address of the LGW, a name of the LGW, or other information capable of uniquely identifying the LGW.
  • the handover request message further includes bearer information and context information activated by the user equipment.
  • the target base station after receiving the handover request message, the target base station establishes a handover request message for the user equipment.
  • the information about the LGW connected to the LIPA determines that the user equipment that performs the handover has an activated LIPA bearer. If the LGW information of the LIPA connection is not established for the user equipment in the handover request message, it is determined that the user equipment that performs the handover does not have the activated LIPA ⁇ I. Loaded.
  • the source base station stores the bearer in the context that contains the association identifier.
  • the correlation id is not included in the non-LIPA bearer.
  • the source base station includes the correlation id in the bearer context and sends it to the target base station.
  • the target base station determines whether the bearer is a LIPA bearer according to whether there is a correlation id in the bearer context.
  • the target base station determines that the user equipment that performs the handover does not have an activated LIPA bearer, the target base station does not need to determine whether there is an IP connection with the LGW according to the existing handover procedure, and directly performs the subsequent handover procedure. For details, refer to the protocol 3GPP TS 36.300.
  • the information of the LGW is transmitted in the handover request to notify the target base station of which LGW is connected to the LIPA, and the source base station informs the target base station LGW of information such as the LGW's IP address, LGW name, etc., and the target base station can query with this. Whether an LGW has an IP connection.
  • the target base station determines that the user equipment performing the handover has an activated LIPA bearer, further determining the user equipment Whether there is an IP connection between the switched target base station and the local gateway LGW that establishes the LIPA connection for the user equipment. If there is an IP connection, the interface switching process is performed.
  • the target base station when the IP connection is performed, performs the interface handover process, where the target base station performs an admission decision on all bearers received from the source base station including the LIPA bearer and returns a handover request response message to the source base station.
  • the message includes a list of bearers successfully received by the target base station and/or a list of bearers that the target base station fails to accept.
  • the target base station does not distinguish whether each bearer in the successfully accepted bearer list is a LIPA bearer, and operates according to the general bearer. That is, if the target base station successfully accepts the LIPA bearer, the LIPA bearer is included in the bearer list successfully received by the base station and returned to the source base station. If the target base station fails to accept the LIPA bearer, the LIPA bearer is returned to the source base station in the bearer list of the target base station admission failure. For details, see the protocol 3GPP TS 36.300.
  • the target base station refuses to accept the bearer associated with the LIPA connection, and returns a handover request response message including the failure to accept the LIPA connection to the source base station.
  • the bearer ID related to the LIPA connection is included in the bearer list of the target base station that fails to receive the request response message.
  • the bearer ID related to the LIPA connection may not be included in the bearer list successfully received by the target base station.
  • the target base station then operates according to the general bearer. For details, refer to the protocol 3GPP TS 36.300.
  • the source base station may delete all LIPA connections of the user equipment through the LGW before the user equipment handover, or the core network control entity passes the source SGW after the user equipment handover is completed (Serving GW, Serving Gateway) Deletes all LIPA connections of the user equipment.
  • All LIPA connections of the user equipment include: Source SGW, LGW, and LIPA connection related information allocated to the user equipment in the core network control entity.
  • the first network side device 10 is an LGW that establishes a LIPA connection for the user equipment, and the second network side device
  • the notification message includes target base station information.
  • the source base station sends a notification message including the target base station information to the LGW.
  • the target base station information may be a target cell identifier, a target base station IP address, a target base station name, or other information that can uniquely identify the target base station.
  • the LGW determines, according to the received target base station information from the source base station, whether the target base station determines whether there is an IP connection between the target base station after the user equipment handover and the local gateway LGW that establishes the LIPA connection for the user equipment, if any IP connection, perform interface switching process.
  • the LGW performs the interface switching process, which may be: notifying the source base station that the target base station has an IP connection with the LGW, for example, indicating that there is a target base station and the LGW in the response message returned to the source base station. IP connection.
  • the source base station After determining that the target base station has an IP connection with the LGW, the source base station initiates an interface switching process including the LIPA connection bearer handover.
  • the source base station initiates an interface handover procedure including the LIPA connection bearer handover, and may send a handover request message including the LIPA bearer information to the target base station; after receiving the handover request message, the target base station does not need to distinguish whether the LIPA bearer information is included. Operate according to the general bearer. The operation of the specific target base station can be found in the protocol 3GPP TS 36.300.
  • the LGW After there is no IP connection between the target base station and the LGW that establishes the LIPA connection for the user equipment, the LGW notifies the source base station that there is no IP connection between the target base station and the LGW, for example, indicating the target base station in the response message returned to the source base station. There is no IP connection between the LGW and the LGW.
  • the source base station After determining that there is no IP connection between the target base station and the LGW, the source base station initiates an interface switching process that does not include the LIPA connection bearer handover.
  • the source base station initiates an interface handover procedure that does not include a LIPA connection bearer handover, and may send a handover request message that does not include LIPA bearer information to the target base station; after receiving the handover request message, the target base station operates according to the general bearer.
  • the operation of the specific target base station can be found in the protocol 3GPP TS 36.300.
  • the source base station may delete all LIPA connections of the user equipment through the LGW before the user equipment handover, or the core network control entity deletes the user through the source SGW after the user equipment handover is completed. All LIPA connections for the device.
  • All LIPA connections of the user equipment include: Source SGW, LGW, and LIPA connection related information allocated to the user equipment in the core network control entity.
  • the first network side device 10 is a core network control entity
  • the second network side device 20 is a target base station after the user equipment is switched, and the notification message is path switching information.
  • the source base station initiates an interface switching process including LIPA bearer information; after the user equipment switches to the target base station, the target base station sends path switching information to the core network control entity;
  • the core network control entity After receiving the path switching information from the target base station, the core network control entity determines whether the user equipment that performs the handover has an activated LIPA bearer;
  • the core network control entity does not need to further determine whether there is an IP connection between the target base station and the LGW after the user equipment is switched, but continues to perform the subsequent handover process. For details, refer to the protocol 3GPP TS 36.300.
  • the core network control entity further determines whether there is an IP connection between the target base station after the user equipment handover and the local gateway LGW that establishes the LIPA connection for the user equipment. If there is an IP connection, the interface switching process is performed.
  • the core network control entity when the IP network is connected, performs the interface switching process: the core network performs a path switching process on all received bearers successfully received by the target base station, including the LIPA bearer. After the path switching process is performed, the core network control entity returns, to the target base station, a bearer list including the core network successfully performing path switching and/or path switching confirmation information of the bearer list that does not successfully perform the path switching. If the LIPA bearer successfully completes the path switching process on the core network, the LIPA bearer ID is included in the bearer list that successfully performs path switching, and if LIPA is If the bearer fails to be switched on the core network, the id of the LIPA bearer will be included in the bearer list that does not successfully perform the path switch. Then, the target base station does not need to distinguish whether each bearer in the successfully accepted bearer list is a LIPA bearer, and operates according to the general bearer. For details, refer to the protocol 3GPP TS 23.401.
  • the core network control entity After determining that there is no IP connection between the target base station and the LGW, the core network control entity returns a path switch confirmation message including the failure to accept the LIPA connection to the target base station.
  • the bearer ID of the LIPA connection is included in the bearer list of the path switch that does not successfully perform the path switch.
  • the bearer ID of the LIPA connection is not included in the bearer list that successfully performs path switch on the core network.
  • the target base station then operates according to the general bearer. For details, refer to the protocol 3GPP TS 23.401.
  • the core network control entity deletes all LIPA connections of the user equipment through the source SGW after the user equipment handover is completed.
  • All LIPA connections of the user equipment include: Source SGW, LGW, and LIPA connection related information allocated to the user equipment in the core network control entity.
  • two network side devices and two methods for performing LIPA bearer access control are also provided in the embodiment of the present invention.
  • the principle of solving the problem by these devices and methods is similar to the system for performing LIPA bearer access control. Therefore, the implementation of these devices and methods can be referred to the implementation of the system, and the repeated description will not be repeated.
  • the first network side device in the embodiment of the present invention includes: a determining module 300 and a processing module 310.
  • the determining module 300 is configured to: after receiving the notification message, determine whether there is an IP connection between the target base station after the user equipment switching and the local gateway LGW that establishes a LIPA connection for the user equipment;
  • the processing module 310 is configured to perform an interface switching process after determining that the target base station has an IP connection with the LGW; wherein the source base station to which the user equipment belongs and the closed and subscribed user group CSG of the target base station are the same, and both support the same interface. Switch.
  • the notification message is a handover request message; the determining module 300 determines, according to the received handover request message from the source base station, that the user equipment that performs the handover is activated. After the LIPA is carried, it is determined whether there is an IP connection between the target base station after the user equipment is switched and the local gateway LGW that establishes the LIPA connection for the user equipment.
  • the processing module 310 After determining that there is no IP connection between the target base station and the LGW, the processing module 310 returns a handover request response message including the failure to accept the LIPA connection to the source base station.
  • the notification message includes the target base station information
  • the determining module 300 determines, according to the received target base station information from the source base station, the corresponding target base station, and determines whether there is an IP connection between the target base station after the user equipment switching and the local gateway LGW that establishes the LIPA connection for the user equipment.
  • the processing module 310 notifies the source base station that there is an IP connection between the target base station and the LGW, indicating that the source base station initiates Interface switching process including LIPA connection bearer switching.
  • the processing module 310 after determining that there is no IP connection between the target base station and the LGW, notifies the source base station that there is no IP connection between the target base station and the LGW, and is used to indicate that the source base station initiates an interface switching process that does not include the LIPA connection bearer handover.
  • the notification message is path switching information
  • the determining module 300 receives the path switching information from the target base station, and determines that the user equipment that performs the handover has an activated LIPA bearer, and then determines Is there an IP connection between the target base station and the LGW?
  • the processing module 310 After determining that there is no IP connection between the target base station and the LGW, the processing module 310 returns a path switching response message including the information of accepting the LIPA connection failure to the target base station.
  • the processing module 310 deletes all LIPA connections of the user equipment through the source SGW after the user equipment handover is completed.
  • the second network side device of the embodiment of the present invention includes: a determining module 400 and a notification module 400.
  • a determining module 400 configured to determine a user equipment that performs interface switching;
  • the notification module 410 is configured to send a notification message to the first network side device, to notify the first network side device to perform an interface switching process when the target base station after the user equipment handover has an IP connection with the LGW that establishes the LIPA connection for the user equipment;
  • the source base station to which the user equipment belongs is the same as the CSG of the target base station, and both support the same type of interface switching.
  • the first network side device is the target base station after the user equipment is switched
  • the second network side device is the source base station to which the user equipment belongs
  • the notification message is a handover request message
  • the notification module 410 after determining that the user equipment performing the handover has an activated LIPA bearer, transmits a handover request message containing information of the LGW that establishes the LIPA connection for the user equipment to the target base station.
  • the first network side device is an LGW that establishes a LIPA connection for the user equipment
  • the second network side device is a source base station to which the user equipment belongs, and the notification message includes the target base station information
  • the notification module 410 sends a notification message including the target base station information to the LGW after determining that the user equipment performing the handover has the activated LIPA bearer.
  • the notification module 410 deletes all LIPA connections of the user equipment through the LGW.
  • the first network side device is a core network control entity
  • the second network side device is a target base station after the user equipment is switched
  • the notification message is path switching information
  • the first network side device or the second network side device is the target base station, and all the modules in FIG. 3 and FIG. 4 may all be in the target base station, and different modules are selected according to specific situations.
  • the method for the first LIPA bearer access control in the embodiment of the present invention includes the following steps: Step 501: After receiving the notification message, the first network side device determines that the target base station after the user equipment is switched is a user. Whether the device establishes an IP connection between the LGWs connected to the LIPA;
  • Step 502 After the first network side device determines that there is an IP connection between the target base station and the LGW, perform interface switching.
  • the source base station to which the user equipment belongs and the CSG of the target base station are the same, and both support the same type of interface switching.
  • the second network side device is the source base station to which the user equipment belongs, and the notification message is a handover request message;
  • the second network side device is a source base station to which the user equipment belongs, and the notification message includes the target base station information;
  • the second network side device is a target base station after the user equipment is switched, and the notification message is path switching information.
  • the first network side device is the target base station after the user equipment is switched, and the second network side device is the source base station to which the user equipment belongs, and the notification message is a handover request message.
  • the target base station After receiving the handover request message, the target base station establishes that the handover request message is established for the user equipment.
  • the information of the LGW connected to the LIPA determines that the user equipment that performs the handover has an activated LIPA bearer; if the LGW information of the LIPA connection is not established for the user equipment in the handover request message, it is determined that the user equipment that performs the handover does not have the activated LIPA ⁇ .
  • the context in which the source base station stores the bearer includes a correlation id, which is not included in the non-LIPA bearer.
  • the source base station includes the correlation id in the bearer context. Transmitted to the target base station. The target base station determines whether the bearer is a LIPA bearer based on whether there is a correlation id in the bearer context.
  • the target base station determines that the user equipment that performs the handover does not have an activated LIPA bearer, the target base station does not need to determine whether there is an IP connection with the LGW according to the existing handover procedure, and directly performs the subsequent handover procedure. For details, refer to the protocol 3GPP TS 36.300.
  • the information of the LGW is transmitted in the handover request to notify the target base station of which LGW is connected to the LIPA, and the source base station informs the target base station LGW of information such as the LGW's IP address, LGW name, etc., and the target base station can query with this. Whether an LGW has an IP connection.
  • the target base station determines that the user equipment that performs the handover has an activated LIPA bearer, further determining whether there is an IP connection between the target base station after the user equipment switching and the local gateway LGW establishing the LIPA connection for the user equipment, if there is an IP connection, the execution interface Switching process.
  • the target base station when the IP connection is performed, performs the interface handover process, where the target base station performs an admission decision on all the bearers received from the source base station, including the LIPA bearer, and returns a handover request response message to the source base station.
  • the message contains a list of bearers successfully received by the target base station (including the activated LIPA bearers) and/or the target base.
  • the station accepts the failed bearer list (which does not include the activated LIPA bearer), and then the target base station does not distinguish whether each bearer in the successfully accepted bearer list is a LIPA bearer, and operates according to the general bearer.
  • the LIPA bearer is returned to the source base station in the bearer list successfully received by the base station. If the target base station fails to accept the LIPA bearer, the LIPA bearer is returned to the source base station in the bearer list of the target base station acceptance failure. For details, see the protocol 3GPP TS 36.300.
  • the target base station refuses to accept the bearer associated with the LIPA connection, and returns a handover request response message including the failure to accept the LIPA connection to the source base station.
  • the bearer ID related to the LIPA connection is included in the bearer list of the target base station that fails to receive the request response message.
  • the bearer ID related to the LIPA connection may not be included in the bearer list successfully received by the target base station.
  • the target base station then operates according to the general bearer. For details, refer to the protocol 3GPP TS 36.300.
  • the source base station may delete all LIPA connections of the user equipment through the LGW before the user equipment handover, or the core network control entity deletes the user through the source SGW after the user equipment handover is completed. All LIPA connections for the device.
  • All LIPA connections of the user equipment include: The source SGW, the LGW, and the LIPA connection allocated to the user equipment in the core network control entity.
  • the first network side device is an LGW that establishes a LIPA connection for the user equipment
  • the second network side device is a source base station to which the user equipment belongs
  • the notification message includes the target base station information.
  • the LGW determines, according to the received target base station information from the source base station, whether the target base station determines whether there is an IP connection between the target base station after the user equipment handover and the local gateway LGW that establishes the LIPA connection for the user equipment, if There is an IP connection, and the interface switching process is performed.
  • the LGW performs the interface switching process, which may be: notifying the source base station that the target base station has an IP connection with the LGW, for example, indicating that there is a target base station and the LGW in the response message returned to the source base station. IP connection.
  • the source base station After determining that the target base station has an IP connection with the LGW, the source base station initiates an interface handover procedure including the LIPA connection bearer handover.
  • the source base station initiates an interface handover procedure including the LIPA connection bearer handover, and may send a handover request message including the LIPA bearer information to the target base station; after receiving the handover request message, the target base station does not need to distinguish whether the LIPA bearer information is included. Operate according to the general bearer. The operation of the specific target base station can be found in the protocol 3GPP TS 36.300.
  • the LGW After there is no IP connection between the target base station and the LGW that establishes the LIPA connection for the user equipment, the LGW notifies the source base station that there is no IP connection between the target base station and the LGW, for example, indicating the target base station in the response message returned to the source base station. There is no IP connection between the LGW and the LGW.
  • the source base station After determining that there is no IP connection between the target base station and the LGW, the source base station initiates a handover that does not include the LIPA connection bearer. Interface switching process.
  • the source base station initiates an interface handover procedure that does not include a LIPA connection bearer handover, and may send a handover request message that does not include LIPA bearer information to the target base station; after receiving the handover request message, the target base station operates according to the general bearer.
  • the operation of the specific target base station can be found in the protocol 3GPP TS 36.300.
  • the source base station may delete all LIPA connections of the user equipment through the LGW before the user equipment handover, or the core network control entity deletes the user through the source SGW after the user equipment handover is completed. All LIPA connections for the device.
  • All LIPA connections of the user equipment include: Source SGW, LGW, and LIPA connection related information allocated to the user equipment in the core network control entity.
  • the first network side device is a core network control entity
  • the second network side device is a target base station after the user equipment is switched
  • the notification message is path switching information.
  • the core network control entity determines whether the user equipment that performs the handover has an activated LIPA bearer
  • the core network control entity further determines whether there is an IP connection between the target base station after the user equipment handover and the local gateway LGW that establishes the LIPA connection for the user equipment. If there is an IP connection, the interface switching process is performed.
  • the core network control entity when the IP network is connected, performs the interface switching process: the core network performs a path switching process on all received bearers successfully received by the target base station, including the LIPA bearer. After performing the path switching process, the core network control entity returns to the target base station a bearer list including the core network successfully performing path switching and/or path switching confirmation information of the bearer list that has not successfully performed the path switching. If the LIPA bearer successfully completes the path switching process on the core network, the LIPA bearer ID is included in the bearer list that successfully performs the path switch. Otherwise, if the LIPA bearer fails to be switched on the core network path, the bearer list is not successfully executed. Will contain the id of the LIPA bearer. Then, the target base station does not need to distinguish whether each bearer in the successfully accepted bearer list is a LIPA bearer, and operates according to the general bearer. For details, refer to the protocol 3GPP TS 23.401.
  • the core network control entity After determining that there is no IP connection between the target base station and the LGW, the core network control entity returns a path switch confirmation message including the failure to accept the LIPA connection to the target base station.
  • the bearer ID of the LIPA connection is included in the bearer list of the path switch that does not successfully perform the path switch.
  • the bearer ID of the LIPA connection is not included in the bearer list that successfully performs path switch on the core network.
  • the target base station then operates according to the general bearer. For details, refer to the protocol TS 23.401.
  • the core network control entity deletes all LIPA connections of the user equipment through the source SGW after the user equipment handover is completed.
  • All LIPA connections of the user equipment include: Source SGW, LGW, and LIPA connection related information allocated to the user equipment in the core network control entity.
  • the second LIPA bearer access control method in the embodiment of the present invention includes the following steps: Step 601: The second network side device determines a user equipment that performs interface switching.
  • Step 602 The second network side device sends a notification message to the first network side device, to notify the first network side device to perform an interface switching process when the target base station after the user equipment handover has an IP connection with the LGW that establishes the LIPA connection for the user equipment.
  • the source base station to which the user equipment belongs and the CSG of the target base station are the same, and both support the same type of interface switching.
  • the first network side device is the target base station after the user equipment is switched
  • the second network side device is the source base station to which the user equipment belongs
  • the notification message is a handover request message.
  • the source base station determines that the user equipment needs to perform the handover, and the source station of the user equipment belongs to the same CSG as the target base station, and both support the same type of interface switching, and check whether the user equipment that needs to be switched has an activated LIPA bearer;
  • the source base station adds the information of the LGW that establishes the LIPA connection to the user equipment in the handover request message; otherwise, the information of the LGW that establishes the LIPA connection for the user equipment is not added in the handover request message.
  • the information of the LGW that establishes the LIPA connection for the user equipment may be an IP address of the LGW, a name of the LGW, or other information capable of uniquely identifying the LGW.
  • the handover request message further includes bearer information and context information activated by the user equipment.
  • the source base station can delete all LIPA connections of the user equipment through the LGW before the user equipment switches.
  • the second network side device is a source base station to which the user equipment belongs, and the notification message includes the target base station information.
  • the source base station After determining that the user equipment that performs handover has an activated LIPA bearer, the source base station sends a notification message including the target base station information to the LGW.
  • the target base station information may be a target cell identifier, a target base station IP address, a target base station name, or other information that can uniquely identify the target base station.
  • the source base station can delete all LIPA connections of the user equipment through the LGW before the user equipment switches.
  • the notification message is path switching information.
  • the source base station initiates an interface switching process. After the user equipment switches to the target base station, the target base station sends path switching information to the core network control entity.
  • a process may be synthesized to form another method for performing LIPA bearer access control, that is, step 601 and step 602 are performed first, and then steps 501 and 502 are performed.
  • the source base station decides to handover the UE to the target base station, the source base station generates a handover request message to the target base station, which
  • the message includes the context information of the UE in the source base station, and the context information includes the bearer list activated by the UE, the QoS information of each bearer, the TEID (Tunnel End Point Identifier) of the user plane, and the like;
  • the base station After receiving the handover request message, the base station performs admission control on the bearer included in the handover message, and returns a handover request response message, where the message may include the bearer list successfully received by the target base station and the bearer list that the target base station does not successfully accept (specific LIPA bearer) In which list, the schemes of Case 1 and Case 2 of the embodiment of the present invention can be used;
  • the source base station After receiving the handover request response message returned by the target base station, the source base station will initiate a handover command message to the UE, and the UE will establish a connection with the target base station after receiving the message;
  • a path switch request message is sent to the MME, where the bearer list established by the UE at the target base station is included;
  • the MME After the MME performs the path update process, the MME returns a path switch confirmation message to the target base station, and returns the TEID after the successful path switch and the bearer list that the network side does not successfully perform the path switch to the target base station.
  • the scheme of the third case of the embodiment of the present invention is used).
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can be embodied in the form of a computer program product embodied on one or more computer-usable storage interfaces (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer-usable storage interfaces including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • the LIPA connection can be processed, thereby improving network performance and expanding the processing capability of the network.

Abstract

本发明实施例涉及无线通信技术领域，特别涉及一种进行LIPA承载接入控制的方法、系统和设备，用以在切换过程中对于UE在相同CSG小区移动，但是移动到了新的本地网络时，能够实现对LIPA连接进行处理。本发明实施例的方法包括：第一网络侧设备在用户设备切换后的目标基站与为用户设备建立LIPA连接的LGW之间有IP连接后，执行接口切换过程；其中用户设备所属的源基站和目标基站的闭和签约用户组CSG相同，且都支持同一种接口切换。由于本发明实施例在切换过程中对于UE在相同CSG小区移动，但是移动到了新的本地网络时，能够对LIPA连接进行处理，从而提高了网络性能，扩展了网络的处理能力。

Description

一种进行 LIPA承载接入控制的方法、 系统和设备 本申请要求在 2011年 6月 8日提交中国专利局、 申请号为 201110152108.9、 发明名称 为"一种进行 LIPA承载接入控制的方法、 系统和设备"的中国专利申请的优先权， 其全部内 容通过引用结合在本申请中。 技术领域
本发明涉及无线通信技术领域， 特别涉及一种进行 LIPA承载接入控制的方法、 系统 和设备。 背景技术
在目前协议中支持 UE (用户设备 )通过 H(e) B ( (演进的） 家庭基站）接入到家庭 或者企业 IP网， 而不需要通过运营商网络传递用户数据。 如图 1A所示为 UE通过 LIPA ( Local IP Access, 本地 IP接入） 方式接入的架构图。
在 LIPA架构中， L-GW ( Local-Gateway, 本地网关）位于家庭或者企业内部， 通过 SGi接口连接家庭或者企业 IP网。 在 LIPAPDN ( Packet Data Network, 分组数据网 )连接 建立过程中， L-GW功能与 PGW ( PDN GW, 分组数据网关）类似。 当 UE请求建立 LIPA PDN连接时， MME ( Mobility Management Entity, 移动性管理实体 )为 UE选择到 L-GW, 并向 SGW以及 LGW发送请求信息。 LGW向 SGW返回响应消息， SGW收到后会向 MME 返回响应消息。 MME请求 HeNB为 UE建立这一 LIPA PDN连接缺省承载的 S 1和空口承 载。 HeNB除了建立 S1接口以及空口承载外， HeNB与 L-GW之间还会建立一条直接隧道。 当 UE在连接态传递 LIPA数据时， 数据会从 UE传递到 HeNB , 在通过 HeNB与 L-GW之 间的直接隧道传递到 L-GW, 而不经过 SGW。 当下行数据到达 L-GW时， L-GW也会通过 L-GW与 HeNB之间的直接隧道将数据发送到 HeNB而不需要经过 SGW的传递。 L-GW与 SGW之间建立的 S5接口只有在 UE进入到空闲态时才会使用。 当 UE进入空闲状态时， HeNB与 L-GW之间的直接隧道将被拆除， L-GW只保留到 SGW之间的 S5连接。当 L-GW 收到 LIPA PDN连接的下行数据时， L-GW将收到的第一个数据包通过 S5接口传递到 SGW, 触发正常的 paging (寻呼）过程， 而除了第一个数据包外的所有数据包都将保留在 L-GW。 当 UE收到寻呼并进入连接态后， HeNB与 L-GW之间的直接隧道将重新建立。 SGW将收 到从 L-GW发送的第一个数据包发送到 HeNB ,而剩下的其他数据包则由 L-GW通过 L-GW 与 HeNB之间的直接隧道传递给 He B。
目前有些大型企业可能需要部署 HeNB以及 L-GW用于支持企业员工通过 LIPA方式 访问企业内部网络。 然而由于 HeNB的容量和覆盖范围有限， 因此存在一个企业网中部署 多个 HeNB的场景。 UE通过这些 HeNB都可以连接到 L-GW从而访问企业内网。 目前 3GPP ( 3rd Generation Partnership Project, 第三代移动通信标准化组织）协议提 出对于 LIPA连接的移动性需求， 要求 UE在同一本地 IP网络下的不同 HeNB之间移动时 能够保持 LIPA连接的连续性。如图 1B所示，假设下图中四个 HeNB都属于同一个本地网 络， 若 UE激活了 LIPA连接， 当 UE在下面 4个 HeNB之间发生移动时， 无论是空闲态还 是连接态， UE的 LIPA连接不能因为 UE的移动而造成 LIPA连接释放。
目前协议中规定， 允许相同 CSG ( Close Subscriber Group, 闭和签约用户组）的 HeNB 之间建立 X2接口或 Iur接口， 而不同 CSG之间的 HeNB则不允许建立基站之间的 X2接 口和 Iur接口接口。 因此当 UE在同一 CSG下的不同 HeNB之间发生移动时， source (源） HeNB可以发起 X2接口切换或 Iur接口切换， 而在不同 CSG下的 HeNB之间发生移动时， source HeNB则只能发起 S 1接口切换。
但是对于本地 IP网络与 CSG之间的关系，可能存在一种情况是某一 CSG覆盖了多个 不同本地网络的场景， 当 UE在不同本地网络对应的家庭基站之间移动时， 虽然这些基站 都有相同的 CSG, 但是 UE的 LIPA连接仍然不能保持。
综上所述， 目前的切换过程中对于 UE在相同 CSG小区移动， 但是移动到了新的本地 网络时， 还没有一种处理 LIPA连接的方案。 发明内容
本发明实施例提供一种进行 LIPA承载接入控制的方法、 系统和设备， 用以在切换过 程中对于 UE在相同 CSG小区移动， 但是移动到了新的本地网络时， 能够实现对 LIPA连 接进行处理。
本发明实施例提供的一种进行本地 IP接入 LIPA承载接入控制的方法， 包括： 第一网络侧设备在收到通知消息后， 判断用户设备切换后的目标基站与为用户设备建 立 LIPA连接的本地网关 LGW之间是否有 IP连接；
所述第一网络侧设备在确定所述目标基站与所述 LGW之间有 IP连接后，执行接口切 换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
本发明实施例提供的一种进行 LIPA承载接入控制的方法， 包括：
第二网络侧设备确定进行接口切换的用户设备；
所述第二网络侧设备向第一网络侧设备发送通知消息， 用以通知所述第一网络侧设备 在用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW有 IP连接时 执行接口切换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
本发明实施例提供的一种进行 LIPA承载接入控制的设备， 包括：
判断模块， 用于在收到通知消息后， 判断用户设备切换后的目标基站与为用户设备建 立 LIPA连接的本地网关 LGW之间是否有 IP连接；
处理模块， 用于在确定所述目标基站与所述 LGW之间有 IP连接后， 执行接口切换过 程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
本发明实施例提供的一种进行 LIPA承载接入控制的设备， 包括：
确定模块， 用于确定进行接口切换的用户设备；
通知模块， 用于向第一网络侧设备发送通知消息， 用以通知所述第一网络侧设备在用 户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW有 IP连接时执行 接口切换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
本发明实施例提供的一种进行 LIPA承载接入控制的系统， 包括：
第一网络侧设备 , 用于在收到通知消息后， 判断用户设备切换后的目标基站与为用户 设备建立 LIPA连接的 LGW之间是否有 IP连接， 在确定所述目标基站与所述 LGW之间 有 IP连接后， 执行接口切换过程；
第二网络侧设备， 用于确定进行接口切换的用户设备后， 向第一网络侧设备发送通知 消息；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
若用户设备所属的源基站和目标基站的 CSG相同，且都支持同一种接口切换，且用户 设备切换后的目标基站与为用户设备建立 LIPA连接的 LGW之间有 IP连接， 第一网络侧 设备执行接口切换过程。 由于本发明实施例在切换过程中对于 UE在相同 CSG小区移动， 但是移动到了新的本地网络时， 能够对 LIPA连接进行处理， 从而提高了网络性能， 扩展 了网络的处理能力。 附图说明
图 1 A为背景技术中 UE通过 He B接入 LIPA架构图；
图 1B为背景技术中多个 HeNB属于同一个本地网络的示意图；
图 2为本发明实施例进行 LIPA承载接入控制的系统结构示意图； 图 3为本发明实施例第一网络侧设备结构示意图；
图 4为本发明实施例第二网络侧设备结构示意图；
图 5为本发明实施例第一种进行 LIPA承载接入控制的方法流程示意图；
图 6为本发明实施例第二种进行 LIPA承载接入控制的方法流程示意图；
图 7为本发明实施例 X2接口切换的示意图。 具体实施方式
本发明实施例若用户设备所属的源基站和目标基站的 CSG相同，且都支持同一种接口 切换，且用户设备切换后的目标基站与为用户设备建立 LIPA连接的 LGW之间有 IP连接， 第一网络侧设备执行接口切换过程。 由于本发明实施例在切换过程中对于用户设备在相同 CSG小区移动， 但是移动到了新的本地网络时， 能够对 LIPA连接进行处理， 从而提高了 网络性能， 扩展了网络的处理能力。
如果本发明实施例的方案应用在 LTE系统中， 本发明实施例中的接口切换是 X2接口 切换， 本发明实施例中的基站是家庭基站或演进的家庭基站， 本发明实施例中的核心网控 制实体是 MME ( Mobility Management Entity, 移动性管理实体）；
如果本发明实施例的方案应用在 3G系统中，本发明实施例中的接口切换是 Iur接口切 换， 本发明实施例中的基站是家庭基站， 本发明实施例中的核心网控制实体是 SGSN ( Serving GPRS Support Node, 服务 GPRS服务节点）。
在下面的说明过程中， 先从第一网络侧设备和第二网络侧设备的配合实施进行说明， 最后分别从第一网络侧设备与第二网络侧设备的实施进行说明， 但这并不意味着二者必须 配合实施， 实际上， 当第一网络侧设备与第二网络侧设备分开实施时， 也解决了分别在第 一网络侧设备、 第二网络侧设备所存在的问题， 只是二者结合使用时， 会获得更好的技术 效果。
下面结合说明书附图对本发明实施例作进一步详细描述。
如图 2所示， 本发明实施例 LIPA承载接入控制的系统包括： 第一网络侧设备 10和第 二网络侧设备 20。
第一网络侧设备 10 , 用于在收到来自第二网络侧设备 20的通知消息后， 判断用户设 备切换后的目标基站与为用户设备建立 LIPA连接的 LGW之间是否有 IP连接， 并在确定 目标基站与 LGW之间有 IP连接后， 执行接口切换过程；
第二网络侧设备 20, 用于确定进行接口切换的用户设备， 向第一网络侧设备 10发送 通知消息；
其中， 用户设备所属的源基站和目标基站的 CSG相同， 且都支持同一种接口切换。 在实施中， 如果第一网络侧设备 10是用户设备切换后的目标基站， 则第二网络侧设 备 20是用户设备所属的源基站（即切换之前的基站， 下同）， 通知消息是切换请求消息； 如果第一网络侧设备 10是为用户设备建立 LIPA连接的 LGW, 则第二网络侧设备 20 是用户设备所属的源基站， 通知消息包含目标基站信息；
如果第一网络侧设备 10是核心网控制实体， 则第二网络侧设备 20是用户设备切换后 的目标基站， 通知消息是路径倒换信息。
下面分别进行详细说明。
情况一、 第一网络侧设备 10是用户设备切换后的目标基站， 则第二网络侧设备 20是 用户设备所属的源基站， 通知消息是切换请求消息。
较佳地， 源基站在确定有用户设备需要进行切换， 并且用户设备所属的源基站和目标 基站的 CSG相同，且都支持同一种接口切换后，查看需要进行切换的用户设备是否有激活 的 LIPA^ 载；
如果有， 则源基站在切换请求消息中增加为用户设备建立 LIPA连接的 LGW的信息； 否则， 不在切换请求消息中增加为用户设备建立 LIPA连接的 LGW的信息。
较佳地， 为用户设备建立 LIPA连接的 LGW的信息可以是 LGW的 IP地址、 LGW的 名称或其他能够唯一标识该 LGW的信息。
较佳地， 切换请求消息中还包括用户设备激活的承载信息和上下文信息。
相应的， 目标基站在收到切换请求消息后， 如果切换请求消息中有为用户设备建立
LIPA连接的 LGW的信息， 则确定进行切换的用户设备有激活的 LIPA承载； 如果切换请 求消息中没有为用户设备建立 LIPA连接的 LGW的信息，则确定进行切换的用户设备没有 激活的 LIPA^I载。
当然，除了上述利用 LGW的信息判断进行切换的用户设备是否有激活的 LIPA承载之 夕卜， 还可以釆用下列方式确定：
如果某一承载是 LIPA 连接， 那么源基站保存这一承载的上下文中会包含关联标识
( correlation id ), 这一 correlation id是非 LIPA承载没有的， 在执行切换时， 源基站会将这 一 correlation id包含在承载上下文中发送给目标基站。 目标基站根据承载上下文中是否有 correlation id来判断这一承载是否是 LIPA承载。
如果目标基站确定进行切换的用户设备没有激活的 LIPA承载， 根据现有切换流程， 目标基站不需要判断是否与 LGW之间有 IP连接， 直接执行后续切换过程， 具体操作可以 参见协议 3GPP TS 36.300。
较佳地，在切换请求中传递 LGW的信息可以通知目标基站 LIPA连接的 LGW是哪一 个， 源基站告诉目标基站 LGW的信息， 如 LGW的 IP address, LGW name等信息， 目标 基站能够查询与这一 LGW是否有 IP连接。
如果目标基站确定进行切换的用户设备有激活的 LIPA承载， 则进一步判断用户设备 切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP连接， 如 果有 IP连接 , 执行接口切换过程。
较佳地， 在有 IP连接时， 目标基站执行接口切换过程可以是： 目标基站对包含 LIPA 承载在内的所有从源基站接收到的承载进行接纳判决并向源基站返回切换请求响应消息。 该消息中包含目标基站成功接纳的承载列表和 /或目标基站接纳失败的承载列表。 目标基 站不用区分成功接纳的承载列表中每个承载是否是 LIPA承载， 都按照一般承载进行操作。 即， 如果目标基站对 LIPA承载接纳成功， 则在基站成功接纳的承载列表中包含 LIPA承载 返回给源基站。 如果目标基站对 LIPA承载接纳不成功， 则在目标基站接纳失败的承载列 表中包含 LIPA承载返回给源基站。 具体操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则目标基站拒绝接纳 LIPA连接相 关的承载， 向源基站返回包含接纳 LIPA连接失败信息的切换请求响应消息。 比如在切换 请求响应消息的目标基站接纳失败的承载列表中包含 LIPA连接相关的承载 ID; 还可以在 目标基站成功接纳的承载列表中不包含 LIPA连接相关的承载 ID。 然后目标基站按照一般 承载进行操作 , 具体操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接，或者核心网控制实体在用户设备切换完成后通过 源 SGW ( Serving GW, 服务网关）删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接相关的信息。
情况二、 第一网络侧设备 10是为用户设备建立 LIPA连接的 LGW , 第二网络侧设备
20是用户设备所属的源基站， 通知消息包含目标基站信息。
较佳地， 源基站在确定进行切换的用户设备有激活的 LIPA承载后， 向 LGW发送包含 目标基站信息的通知消息。
其中， 目标基站信息可以是目标小区标识、 目标基站 IP地址、 目标基站名称或其他能 够唯一标识目标基站的信息。
相应的， LGW根据收到的来自源基站的目标基站信息， 确定对应的目标基站后判断 用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP 连接， 如果有 IP连接， 执行接口切换过程。
较佳地， 在有 IP连接时， LGW执行接口切换过程可以是： 通知源基站， 目标基站与 LGW之间有 IP连接， 比如在返回给源基站的响应消息中指示目标基站与 LGW之间有 IP 连接。
源基站在确定目标基站与 LGW之间有 IP连接后， 发起包含 LIPA连接承载切换的接 口切换过程。 较佳地， 源基站发起包含 LIPA连接承载切换的接口切换过程可以是向目标基站发送 包含 LIPA承载信息的切换请求消息； 目标基站在收到切换请求消息后， 不用区分是否含 有 LIPA承载信息，都按照一般承载进行操作。具体目标基站的操作可以参见协议 3GPP TS 36.300。
较佳地， 在目标基站与为用户设备建立 LIPA连接的 LGW之间没有 IP连接后， LGW 通知源基站目标基站与 LGW之间没有 IP连接， 比如在返回给源基站的响应消息中指示目 标基站与 LGW之间没有 IP连接。
源基站在确定目标基站与 LGW之间没有 IP连接后， 发起不包含 LIPA连接承载切换 的接口切换过程。
较佳地， 源基站发起不包含 LIPA连接承载切换的接口切换过程可以是向目标基站发 送不包含 LIPA承载信息的切换请求消息； 目标基站在收到切换请求消息后， 都按照一般 承载进行操作。 具体目标基站的操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接，或者核心网控制实体在用户设备切换完成后通过 源 SGW删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接相关的信息。
情况三、 第一网络侧设备 10是核心网控制实体， 第二网络侧设备 20是用户设备切换 后的目标基站， 通知消息是路径倒换信息。
较佳地， 源基站发起包含 LIPA承载信息的接口切换过程； 当用户设备切换到目标基 站后， 目标基站向核心网控制实体发送路径倒换信息；
核心网控制实体接收来自目标基站的路径倒换信息后， 判断进行切换的用户设备是否 有激活的 LIPA承载；
如果没有激活的 LIPA承载， 核心网控制实体不用进一步判断用户设备切换后的目标 基站与 LGW之间是否有 IP连接， 而是继续执行后面的切换过程， 具体操作可以参见协议 3GPP TS 36.300。
如果有， 核心网控制实体进一步判断用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP连接， 如果有 IP连接， 执行接口切换过程。
较佳地， 在有 IP 连接时， 核心网控制实体执行接口切换过程可以是： 核心网对包括 LIPA承载在内所有收到的在目标基站成功接纳的承载进行路径切换过程。执行完路径切换 过程后， 核心网控制实体向目标基站返回包含核心网成功执行路径切换的承载列表和 /或 没有成功执行路径切换的承载列表的路径切换确认信息。 如果 LIPA承载在核心网成功完 成路径切换过程，则在成功执行路径切换的承载列表中包含 LIPA承载 ID,反之，如果 LIPA 承载在核心网路径切换失败， 则在没有成功执行路径切换的承载列表中将包含 LIPA承载 的 id。 然后目标基站不用区分成功接纳的承载列表中每个承载是否是 LIPA承载， 都按照 一般承载进行操作 , 具体操作可以参见协议 3GPP TS 23.401。
较佳地， 核心网控制实体在确定目标基站与 LGW之间没有 IP连接后， 向目标基站返 回包含接纳 LIPA连接失败信息的路径倒换确认消息。 比如在路径倒换确认消息的核心网 没有成功执行路径切换的承载列表中包含 LIPA连接相关的承载 ID; 还可以在核心网成功 执行路径切换的承载列表中不包含 LIPA连接相关的承载 ID。 然后目标基站按照一般承载 进行操作， 具体操作可以参见协议 3GPP TS 23.401。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则核心网控制实体在用户设备切换 完成后通过源 SGW删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接相关信息。
基于同一发明构思， 本发明实施例中还提供了两种网络侧设备及两种进行 LIPA承载 接入控制的方法， 由于这些设备和方法解决问题的原理与进行 LIPA承载接入控制的系统 相似， 因此这些设备和方法的实施可以参见系统的实施， 重复之处不再赘述。
如图 3所示， 本发明实施例的第一网络侧设备包括： 判断模块 300和处理模块 310。 判断模块 300 , 用于在收到通知消息后， 判断用户设备切换后的目标基站与为用户设 备建立 LIPA连接的本地网关 LGW之间是否有 IP连接；
处理模块 310, 用于在确定目标基站与 LGW之间有 IP连接后， 执行接口切换过程； 其中，用户设备所属的源基站和目标基站的闭和签约用户组 CSG相同，且都支持同一 种接口切换。
较佳地，若第一网络侧设备是用户设备切换后的目标基站，通知消息是切换请求消息； 判断模块 300根据收到的来自源基站的切换请求消息， 确定进行切换的用户设备有激 活的 LIPA承载后，判断用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网 关 LGW之间是否有 IP连接。
较佳地， 处理模块 310在确定目标基站与 LGW之间没有 IP连接后， 向源基站返回包 含接纳 LIPA连接失败信息的切换请求响应消息。
较佳地， 若第一网络侧设备是为用户设备建立 LIPA连接的 LGW, 通知消息包含目标 基站信息；
判断模块 300根据收到的来自源基站的目标基站信息， 确定对应的目标基站后， 判断 用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP 连接。
较佳地， 处理模块 310通知源基站目标基站与 LGW之间有 IP连接， 指示源基站发起 包含 LIPA连接承载切换的接口切换过程。
较佳地， 处理模块 310在确定目标基站与 LGW之间没有 IP连接后， 通知源基站目标 基站与 LGW之间没有 IP连接， 用于指示源基站发起不包含 LIPA连接承载切换的接口切 换过程。
较佳地， 若第一网络侧设备是核心网控制实体， 通知消息是路径倒换信息； 判断模块 300接收来自目标基站的路径倒换信息， 且确定进行切换的用户设备有激活 的 LIPA承载后， 判断目标基站与 LGW之间是否有 IP连接。
较佳地， 处理模块 310在确定目标基站与 LGW之间没有 IP连接后， 向目标基站返回 包含接纳 LIPA连接失败信息的路径倒换响应消息。
较佳地，处理模块 310在用户设备切换完成后，通过源 SGW删除用户设备的所有 LIPA 连接。
如图 4所示， 本发明实施例的第二网络侧设备包括： 确定模块 400和通知模块 400。 确定模块 400 , 用于确定进行接口切换的用户设备；
通知模块 410, 用于向第一网络侧设备发送通知消息， 通知第一网络侧设备在用户设 备切换后的目标基站与为用户设备建立 LIPA连接的 LGW有 IP连接时执行接口切换过程； 其中， 用户设备所属的源基站和目标基站的 CSG相同， 且都支持同一种接口切换。 较佳地， 第一网络侧设备是用户设备切换后的目标基站， 第二网络侧设备是用户设备 所属的源基站， 通知消息是切换请求消息；
通知模块 410在确定进行切换的用户设备有激活的 LIPA承载后， 向目标基站发送包 含为用户设备建立 LIPA连接的 LGW的信息的切换请求消息。
较佳地， 第一网络侧设备是为用户设备建立 LIPA连接的 LGW, 第二网络侧设备是用 户设备所属的源基站， 通知消息包含目标基站信息；
通知模块 410在确定进行切换的用户设备有激活的 LIPA承载后，向 LGW发送包含目 标基站信息的通知消息。
较佳地， 通知模块 410通过 LGW删除用户设备的所有 LIPA连接。
较佳地， 第一网络侧设备是核心网控制实体， 第二网络侧设备是用户设备切换后的目 标基站， 通知消息是路径倒换信息。
在实施中， 第一网络侧设备或第二网络侧设备是目标基站， 则图 3和图 4中的所有模 块可以都在目标基站中， 根据具体的情况选择不同的模块使用。
如图 5所示， 本发明实施例第一种 LIPA承载接入控制的方法包括下列步骤： 步骤 501、 第一网络侧设备在收到通知消息后， 判断用户设备切换后的目标基站与为 用户设备建立 LIPA连接的 LGW之间是否有 IP连接；
步骤 502、 第一网络侧设备在确定目标基站与 LGW之间有 IP连接后， 执行接口切换 过程；
其中， 用户设备所属的源基站和目标基站的 CSG相同， 且都支持同一种接口切换。 在实施中， 如果第一网络侧设备是用户设备切换后的目标基站， 则第二网络侧设备是 用户设备所属的源基站， 通知消息是切换请求消息；
如果第一网络侧设备是为用户设备建立 LIPA连接的 LGW, 则第二网络侧设备是用户 设备所属的源基站， 通知消息中包含目标基站信息；
如果第一网络侧设备是核心网控制实体， 则第二网络侧设备是用户设备切换后的目标 基站， 通知消息是路径倒换信息。
下面分别进行详细说明。
情况一、 第一网络侧设备是用户设备切换后的目标基站， 则第二网络侧设备是用户设 备所属的源基站， 通知消息是切换请求消息。
较佳地， 目标基站在收到切换请求消息后， 如果切换请求消息中有为用户设备建立
LIPA连接的 LGW的信息， 则确定进行切换的用户设备有激活的 LIPA承载； 如果切换请 求消息中没有为用户设备建立 LIPA连接的 LGW的信息，则确定进行切换的用户设备没有 激活的 LIPA ^ 载。
当然，除了上述利用 LGW的信息判断进行切换的用户设备是否有激活的 LIPA承载之 夕卜， 还可以釆用下列方式确定：
如果某一承载是 LIPA连接，那么源基站保存这一承载的上下文中会包含 correlation id, 这一 correlation id是非 LIPA承载没有的，在执行切换时， 源基站会将这一 correlation id包 含在承载上下文中发送给目标基站。 目标基站根据承载上下文中是否有 correlation id来判 断这一承载是否是 LIPA承载。
如果目标基站确定进行切换的用户设备没有激活的 LIPA承载， 根据现有切换流程， 目标基站不需要判断是否与 LGW之间有 IP连接， 直接执行后续切换过程， 具体操作可以 参见协议 3GPP TS 36.300。
较佳地，在切换请求中传递 LGW的信息可以通知目标基站 LIPA连接的 LGW是哪一 个， 源基站告诉目标基站 LGW的信息， 如 LGW的 IP address, LGW name等信息， 目标 基站能够查询与这一 LGW是否有 IP连接。
如果目标基站确定进行切换的用户设备有激活的 LIPA承载， 则进一步判断用户设备 切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP连接， 如 果有 IP连接， 执行接口切换过程。
较佳地， 在有 IP连接时， 目标基站执行接口切换过程可以是： 目标基站对包含 LIPA 承载在内的所有从源基站接收到的承载进行接纳判决并向源基站返回切换请求响应消息， 该消息中包含目标基站成功接纳的承载列表（其中包括激活的 LIPA承载）和 /或目标基 站接纳失败的承载列表（其中不包括激活的 LIPA承载）， 然后目标基站不用区分成功接纳 的承载列表中每个承载是否是 LIPA承载， 都按照一般承载进行操作。 即， 如果目标基站 对 LIPA承载接纳成功， 则在基站成功接纳的承载列表中包含 LIPA承载返回给源基站。 如 果目标基站对 LIPA承载接纳不成功，则在目标基站接纳失败的承载列表中包含 LIPA承载 返回给源基站。 具体操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则目标基站拒绝接纳 LIPA连接相 关的承载， 向源基站返回包含接纳 LIPA连接失败信息的切换请求响应消息。 比如在切换 请求响应消息的目标基站接纳失败的承载列表中包含 LIPA连接相关的承载 ID; 还可以在 目标基站成功接纳的承载列表中不包含 LIPA连接相关的承载 ID。 然后目标基站按照一般 承载进行操作 , 具体操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接，或者核心网控制实体在用户设备切换完成后通过 源 SGW删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接。
情况二、 第一网络侧设备是为用户设备建立 LIPA连接的 LGW , 第二网络侧设备是用 户设备所属的源基站， 通知消息包含目标基站信息。
较佳地， LGW根据收到的来自源基站的目标基站信息， 确定对应的目标基站后判断 用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP 连接， 如果有 IP连接， 执行接口切换过程。
较佳地， 在有 IP连接时， LGW执行接口切换过程可以是： 通知源基站， 目标基站与 LGW之间有 IP连接， 比如在返回给源基站的响应消息中指示目标基站与 LGW之间有 IP 连接。
源基站在确定目标基站与 LGW之间有 IP连接后， 发起包含 LIPA连接承载切换的接 口切换过程。
较佳地， 源基站发起包含 LIPA连接承载切换的接口切换过程可以是向目标基站发送 包含 LIPA承载信息的切换请求消息； 目标基站在收到切换请求消息后， 不用区分是否含 有 LIPA承载信息，都按照一般承载进行操作。具体目标基站的操作可以参见协议 3GPP TS 36.300。
较佳地， 在目标基站与为用户设备建立 LIPA连接的 LGW之间没有 IP连接后， LGW 通知源基站目标基站与 LGW之间没有 IP连接， 比如在返回给源基站的响应消息中指示目 标基站与 LGW之间没有 IP连接。
源基站在确定目标基站与 LGW之间没有 IP连接后， 发起不包含 LIPA连接承载切换 的接口切换过程。
较佳地， 源基站发起不包含 LIPA连接承载切换的接口切换过程可以是向目标基站发 送不包含 LIPA承载信息的切换请求消息； 目标基站在收到切换请求消息后， 都按照一般 承载进行操作。 具体目标基站的操作可以参见协议 3GPP TS 36.300。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接，或者核心网控制实体在用户设备切换完成后通过 源 SGW删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接相关信息。
情况三、 第一网络侧设备是核心网控制实体， 第二网络侧设备是用户设备切换后的目 标基站， 通知消息是路径倒换信息。
较佳地， 核心网控制实体接收来自目标基站的路径倒换信息后， 判断进行切换的用户 设备是否有激活的 LIPA承载；
如果有， 核心网控制实体进一步判断用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP连接， 如果有 IP连接， 执行接口切换过程。
较佳地， 在有 IP 连接时， 核心网控制实体执行接口切换过程可以是： 核心网对包括 LIPA承载在内所有收到的在目标基站成功接纳的承载进行路径切换过程。执行完路径切换 过程后， 核心网控制实体向目标基站返回包含核心网成功执行路径切换的承载列表和 /或 没有成功执行路径切换的承载列表的路径切换确认信息。 如果 LIPA承载在核心网成功完 成路径切换过程，则在成功执行路径切换的承载列表中包含 LIPA承载 ID,反之，如果 LIPA 承载在核心网路径切换失败， 则在没有成功执行路径切换的承载列表中将包含 LIPA承载 的 id。 然后目标基站不用区分成功接纳的承载列表中每个承载是否是 LIPA承载， 都按照 一般承载进行操作 , 具体操作可以参见协议 3GPP TS23.401。
较佳地， 核心网控制实体在确定目标基站与 LGW之间没有 IP连接后， 向目标基站返 回包含接纳 LIPA连接失败信息的路径倒换确认消息。 比如在路径倒换确认消息的核心网 没有成功执行路径切换的承载列表中包含 LIPA连接相关的承载 ID; 还可以在核心网成功 执行路径切换的承载列表中不包含 LIPA连接相关的承载 ID。 然后目标基站按照一般承载 进行操作， 具体操作可以参见协议 TS 23.401。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则核心网控制实体在用户设备切换 完成后通过源 SGW删除用户设备的所有 LIPA连接。
用户设备的所有 LIPA连接包括： 源 SGW、 LGW以及核心网控制实体中为用户设备 分配的 LIPA连接相关信息。
如图 6所示， 本发明实施例第二种 LIPA承载接入控制的方法包括下列步骤： 步骤 601、 第二网络侧设备确定进行接口切换的用户设备；
步骤 602、 第二网络侧设备向第一网络侧设备发送通知消息， 通知第一网络侧设备在 用户设备切换后的目标基站与为用户设备建立 LIPA连接的 LGW有 IP连接时执行接口切 换过程；
其中， 用户设备所属的源基站和目标基站的 CSG相同， 且都支持同一种接口切换。 较佳地， 若第一网络侧设备是用户设备切换后的目标基站， 第二网络侧设备是用户设 备所属的源基站， 通知消息是切换请求消息。
源基站在确定有用户设备需要进行切换， 并且用户设备所属的源基站和目标基站的 CSG相同，且都支持同一种接口切换后，查看需要进行切换的用户设备是否有激活的 LIPA 承载；
如果有， 则源基站在切换请求消息中增加为用户设备建立 LIPA连接的 LGW的信息； 否则， 不在切换请求消息中增加为用户设备建立 LIPA连接的 LGW的信息。
较佳地， 为用户设备建立 LIPA连接的 LGW的信息可以是 LGW的 IP地址、 LGW的 名称或其他能够唯一标识该 LGW的信息。
较佳地， 切换请求消息中还包括用户设备激活的承载信息和上下文信息。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接。
较佳地， 若第一网络侧设备是为用户设备建立 LIPA连接的 LGW, 第二网络侧设备是 用户设备所属的源基站， 通知消息包含目标基站信息。
源基站在确定进行切换的用户设备有激活的 LIPA承载后，向 LGW发送包含目标基站 信息的通知消息。
其中， 目标基站信息可以是目标小区标识、 目标基站 IP地址、 目标基站名称或其他能 够唯一标识目标基站的信息。
较佳地， 如果目标基站与 LGW之间没有 IP连接， 则源基站可以在用户设备切换前通 过 LGW删除用户设备的所有 LIPA连接。
较佳地， 若第一网络侧设备是核心网控制实体， 第二网络侧设备是用户设备切换后的 目标基站， 通知消息是路径倒换信息。
源基站发起接口切换过程； 当用户设备切换到目标基站后， 目标基站向核心网控制实 体发送路径倒换信息。
其中， 图 5和图 6可以合成一个流程， 形成另一个的进行 LIPA承载接入控制的方法， 即先执行步骤 601和步骤 602 , 再执行步骤 501和步骤 502。
如图 7所示， 本发明实施例的 X2接口切换示意图中：
1、 当源基站决定将 UE切换到目标基站时， 源基站向目标基站发生切换请求消息， 这 一消息包含 UE在源基站的上下文信息， 上下文信息中包括 UE激活的承载列表， 每一承 载的 QoS信息， 用户面的 TEID ( Tunnel End Point Identifier, 隧道端点标识）等标识； 目标基站收到源基站的切换请求消息后将会对其中包含的承载进行接纳控制， 并返回 切换请求响应消息， 这一消息中可以包含目标基站成功接纳的承载列表和目标基站没有成 功接纳的承载列表（具体 LIPA承载在哪个列表中可以釆用本发明实施例情况一和请况二 的方案）；
2、 源基站收到目标基站返回的切换请求响应消息后将向 UE发起切换命令消息， UE 收到后将会与目标基站建立连接；
3、 目标基站与 UE之间的连接建立成功后， 向 MME发起路径切换请求消息， 其中包 括 UE在目标基站建立的承载列表；
4、 MME执行完路径更新过程后向目标基站返回路径切换确认消息， 向目标基站返回 成功执行路径切换后的 TEID以及网络侧没有成功执行路径切换的承载列表（具体 LIPA承 载在哪个列表中可以釆用本发明实施例情况三的方案）。
本领域内的技术人员应明白， 本发明的实施例可提供为方法、 系统、 或计算机程序产 品。 因此， 本发明可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且， 本发明可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 （包括但不限于磁盘存储器、 CD-ROM、 光学存储器等）上实施的计算机程 序产品的形式。
本发明是参照根据本发明实施例的方法、 设备（系统）、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器， 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中， 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品， 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理， 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。 尽管已描述了本发明的优选实施例， 但本领域内的技术人员一旦得知了基本创造性概 念， 则可对这些实施例作出另外的变更和修改。 所以， 所附权利要求意欲解释为包括优选 实施例以及落入本发明范围的所有变更和修改。
本发明实施例在切换过程中对于 UE在相同 CSG小区移动，但是移动到了新的本地网 络时， 能够对 LIPA连接进行处理， 从而提高了网络性能， 扩展了网络的处理能力。
显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和 范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种进行本地 IP接入 LIPA承载接入控制的方法， 其特征在于， 该方法包括： 第一网络侧设备在收到通知消息后， 判断用户设备切换后的目标基站与为用户设备建 立 LIPA连接的本地网关 LGW之间是否有 IP连接；
所述第一网络侧设备在确定所述目标基站与所述 LGW之间有 IP连接后，执行接口切 换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
2、 如权利要求 1 所述的方法， 其特征在于， 所述第一网络侧设备是用户设备切换后 的目标基站， 所述通知消息是切换请求消息；
在所述第一网络侧设备判断所述目标基站与所述 LGW之间是否有 IP连接之前，该方 法还包括：
所述目标基站根据收到的来自所述源基站的切换请求消息， 确定进行切换的用户设备 有激活的 LIPA承载。
3、 如权利要求 2所述的方法， 其特征在于， 所述切换请求消息中包含 LGW的信息， 在所述目标基站收到切换请求消息后， 该方法还包括：
所述目标基站根据收到的切换请求消息， 确定 LGW的信息；
其中， 所述 LGW的信息包括下列信息中的至少一种：
LGW的 IP地址、 LGW的名称。
4、 如权利要求 3所述的方法， 其特征在于， 该方法还包括：
所述目标基站在确定所述目标基站与所述 LGW之间没有 IP连接后， 向所述源基站返 回包含接纳 LIPA连接失败信息的切换请求响应消息。
5、 如权利要求 1 所述的方法， 其特征在于， 所述第一网络侧设备是为用户设备建立 LIPA连接的 LGW, 所述通知消息包含目标基站信息；
在所述第一网络侧设备判断所述目标基站与所述 LGW之间是否有 IP连接之前，该方 法还包括：
所述 LGW根据收到的来自所述源基站的目标基站信息， 确定目标基站。
6、 如权利要求 5 所述的方法， 其特征在于， 所述第一网络侧设备执行接口切换过程 包括：
所述 LGW通知所述源基站所述目标基站与所述 LGW之间有 IP连接；
在所述第一网络侧设备执行接口切换过程之后 , 该方法还包括：
所述源基站发起包含 LIPA连接承载切换的接口切换过程。
7、 如权利要求 5所述的方法， 其特征在于， 该方法还包括：
所述 LGW在确定所述目标基站与所述 LGW之间没有 IP连接后， 通知源基站目标基 站与所述 LGW之间没有 IP连接；
所述源基站发起不包含 LIPA连接承载切换的接口切换过程。
8、 如权利要求 4或 7所述的方法， 其特征在于， 该方法还包括：
源基站通过 LGW删除用户设备的所有 LIPA连接； 或
核心网控制实体在用户设备切换完成后， 通过源服务网关 SGW删除用户设备的所有 LIPA连接。
9、 如权利要求 1所述的方法， 其特征在于， 所述第一网络侧设备是核心网控制实体， 所述通知消息是路径倒换信息；
在所述第一网络侧设备判断所述目标基站与所述 LGW之间是否有 IP连接之前，该方 法还包括：
所述核心网控制实体接收来自目标基站的路径倒换信息， 且确定进行切换的用户设备 有激活的 LIPA承载。
10、 如权利要求 9所述的方法， 其特征在于， 该方法还包括：
所述核心网控制实体在确定所述目标基站与所述 LGW之间没有 IP连接后， 向目标基 站返回包含接纳 LIPA连接失败信息的路径倒换响应消息。
11、 如权利要求 10所述的方法， 其特征在于， 该方法还包括：
核心网控制实体在用户设备切换完成后， 通过源服务网关 SGW删除用户设备的所有 LIPA连接。
12、 一种进行本地 IP接入 LIPA承载接入控制的方法， 其特征在于， 该方法包括： 第二网络侧设备确定进行接口切换的用户设备；
所述第二网络侧设备向第一网络侧设备发送通知消息， 用以通知所述第一网络侧设备 在用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW有 IP连接时 执行接口切换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
13、 如权利要求 12 所述的方法， 其特征在于， 所述第一网络侧设备是用户设备切换 后的目标基站， 所述第二网络侧设备是用户设备所属的源基站， 所述通知消息是切换请求 消息；
所述第二网络侧设备发送通知消息包括：
所述源基站在确定进行切换的用户设备有激活的 LIPA承载后， 向目标基站发送包含 为用户设备建立 LIPA连接的 LGW的信息的切换请求消息； 其中， 所述 LGW的信息包括下列信息中的至少一种：
LGW的 IP地址、 LGW的名称。
14、 如权利要求 13 所述的方法， 其特征在于， 所述第一网络侧设备是为用户设备建 立 LIPA连接的 LGW, 所述第二网络侧设备是用户设备所属的源基站， 所述通知消息包含 目标基站信息；
所述第二网络侧设备发送通知消息包括：
所述源基站在确定进行切换的用户设备有激活的 LIPA承载后，向所述 LGW发送包含 目标基站信息的通知消息。
15、 如权利要求 13或 14所述的方法， 其特征在于， 所述第二网络侧设备确定进行接 口切换的用户设备之后还包括：
所述源基站通过 LGW删除用户设备的所有 LIPA连接。
16、 如权利要求 12 所述的方法， 其特征在于， 所述第一网络侧设备是核心网控制实 体， 所述第二网络侧设备是用户设备切换后的目标基站， 所述通知消息是路径倒换信息。
17、 一种进行 LIPA承载接入控制的设备， 其特征在于， 该设备包括：
判断模块， 用于在收到通知消息后， 判断用户设备切换后的目标基站与为用户设备建 立 LIPA连接的本地网关 LGW之间是否有 IP连接；
处理模块， 用于在确定所述目标基站与所述 LGW之间有 IP连接后， 执行接口切换过 程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
18、 如权利要求 17所述的设备， 其特征在于， 所述进行 LIPA承载接入控制的设备是 用户设备切换后的目标基站， 所述通知消息是切换请求消息；
所述判断模块具体用于：
根据收到的来自源基站的切换请求消息， 确定进行切换的用户设备有激活的 LIPA承 载后，判断用户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间 是否有 IP连接。
19、 如权利要求 18所述的设备， 其特征在于， 所述处理模块还用于：
在确定目标基站与所述 LGW之间没有 IP连接后， 向源基站返回包含接纳 LIPA连接 失败信息的切换请求响应消息。
20、 如权利要求 17所述的设备， 其特征在于， 所述进行 LIPA承载接入控制的设备是 为用户设备建立 LIPA连接的 LGW, 所述通知消息包含目标基站信息；
所述判断模块具体用于：
根据收到的来自所述源基站的目标基站信息， 确定目标基站后， 判断用户设备切换后 的目标基站与为用户设备建立 LIPA连接的本地网关 LGW之间是否有 IP连接。
21、 如权利要求 20所述的设备， 其特征在于， 所述处理模块具体用于：
通知源基站目标基站与所述 LGW之间有 IP连接， 指示源基站发起包含 LIPA连接承 载切换的接口切换过程。
22、 如权利要求 20或 21所述的设备， 其特征在于， 所述处理模块还用于： 在确定目标基站与所述 LGW之间没有 IP连接后， 通知源基站目标基站与所述 LGW 之间没有 IP连接， 用于指示源基站发起不包含 LIPA连接承载切换的接口切换过程。
23、 如权利要求 17所述的设备， 其特征在于， 所述进行 LIPA承载接入控制的设备是 核心网控制实体， 所述通知消息是路径倒换信息；
所述判断模块具体用于：
接收来自目标基站的路径倒换信息， 且确定进行切换的用户设备有激活的 LIPA承载 后， 判断目标基站与所述 LGW之间是否有 IP连接。
24、 如权利要求 23所述的设备， 其特征在于， 所述处理模块还用于：
在确定所述目标基站与所述 LGW之间没有 IP连接后， 向所述目标基站返回包含接纳 LIPA连接失败信息的路径倒换响应消息。
25、 如权利要求 24所述的设备， 其特征在于， 所述处理模块还用于：
在用户设备切换完成后， 通过源服务网关 SGW删除用户设备的所有 LIPA连接。
26、 一种进行 LIPA承载接入控制的设备， 其特征在于， 该设备包括：
确定模块， 用于确定进行接口切换的用户设备；
通知模块， 用于向第一网络侧设备发送通知消息， 用以通知所述第一网络侧设备在用 户设备切换后的目标基站与为用户设备建立 LIPA连接的本地网关 LGW有 IP连接时执行 接口切换过程；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
27、 如权利要求 26 所述的设备， 其特征在于， 所述第一网络侧设备是用户设备切换 后的目标基站， 所述进行 LIPA承载接入控制的设备是用户设备所属的源基站， 所述通知 消息是切换请求消息；
所述通知模块具体用于：
在确定进行切换的用户设备有激活的 LIPA承载后， 向目标基站发送包含为用户设备 建立 LIPA连接的 LGW的信息的切换请求消息。
28、 如权利要求 26 所述的设备， 其特征在于， 所述第一网络侧设备是为用户设备建 立 LIPA连接的 LGW, 所述进行 LIPA承载接入控制的设备是用户设备所属的源基站， 所 述通知消息包含目标基站信息； 所述通知模块具体用于：
在确定进行切换的用户设备有激活的 LIPA承载后，向所述 LGW发送包含目标基站信 息的通知消息。
29、 如权利要求 27或 28所述的设备， 其特征在于， 所述通知模块还用于： 通过 LGW删除用户设备的所有 LIPA连接。
30、 如权利要求 26 所述的设备， 其特征在于， 所述第一网络侧设备是核心网控制实 体， 所述进行 LIPA承载接入控制的设备是用户设备切换后的目标基站， 所述通知消息是 路径倒换信息。
31、 一种进行 LIPA承载接入控制的系统， 其特征在于， 该系统包括：
第一网络侧设备 , 用于在收到通知消息后， 判断用户设备切换后的目标基站与为用户 设备建立 LIPA连接的 LGW之间是否有 IP连接， 在确定所述目标基站与所述 LGW之间 有 IP连接后， 执行接口切换过程；
第二网络侧设备， 用于确定进行接口切换的用户设备后， 向第一网络侧设备发送通知 消息；
其中，用户设备所属的源基站和所述目标基站的闭和签约用户组 CSG相同，且都支持 同一种接口切换。
PCT/CN2012/073054 2011-06-08 2012-03-26 一种进行lipa承载接入控制的方法、系统和设备 WO2012167648A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110152108.9 2011-06-08
CN 201110152108 CN102202364B (zh) 2011-06-08 2011-06-08 一种进行lipa承载接入控制的方法、系统和设备

Publications (1)

Publication Number Publication Date
WO2012167648A1 true WO2012167648A1 (zh) 2012-12-13

Family

ID=44662673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073054 WO2012167648A1 (zh) 2011-06-08 2012-03-26 一种进行lipa承载接入控制的方法、系统和设备

Country Status (2)

Country Link
CN (1) CN102202364B (zh)
WO (1) WO2012167648A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102202364B (zh) * 2011-06-08 2013-09-04 电信科学技术研究院 一种进行lipa承载接入控制的方法、系统和设备
RU2630418C1 (ru) * 2014-03-13 2017-09-07 Интердиджитал Пэйтент Холдингз, Инк. Локальная разгрузка и архитектура малых сот (sca)
CN105578538A (zh) * 2014-10-16 2016-05-11 中兴通讯股份有限公司 承载处理方法及装置
CN105722156A (zh) * 2014-12-05 2016-06-29 中兴通讯股份有限公司 目标小区确定方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998367A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 本地网络协议访问连接的管理方法以及移动性管理实体
CN102045798A (zh) * 2011-01-11 2011-05-04 大唐移动通信设备有限公司 一种进行切换的方法、系统和设备
CN102076038A (zh) * 2011-01-17 2011-05-25 大唐移动通信设备有限公司 一种lipa连接切换准备过程的执行方法及装置
CN102202364A (zh) * 2011-06-08 2011-09-28 电信科学技术研究院 一种进行lipa承载接入控制的方法、系统和设备

Family Cites Families (3)

* 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
CN102026145B (zh) * 2009-09-10 2014-01-01 中兴通讯股份有限公司 一种本地ip访问方法及系统
CN102076036B (zh) * 2011-01-14 2013-04-24 大唐移动通信设备有限公司 核心网设备和家庭基站及其处理lipa连接的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998367A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 本地网络协议访问连接的管理方法以及移动性管理实体
CN102045798A (zh) * 2011-01-11 2011-05-04 大唐移动通信设备有限公司 一种进行切换的方法、系统和设备
CN102076038A (zh) * 2011-01-17 2011-05-25 大唐移动通信设备有限公司 一种lipa连接切换准备过程的执行方法及装置
CN102202364A (zh) * 2011-06-08 2011-09-28 电信科学技术研究院 一种进行lipa承载接入控制的方法、系统和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "LIPA mobility based on direct X2/lurh (doc. NO. S2-112321)", SAWG2 MEETING #85, 16 May 2011 (2011-05-16), XI'AN, P.R.CHINA, pages 2 *

Also Published As

Publication number Publication date
CN102202364B (zh) 2013-09-04
CN102202364A (zh) 2011-09-28

Similar Documents

Publication Publication Date Title
US10356665B2 (en) Source base station gateway (GW) for releasing resources associated with a mobile device
US10588071B2 (en) Wireless communication system, method of routing data in a wireless communication system, and method of handing over a wireless communication device, having an established data connection to a local network
TWI580239B (zh) 通用陸地無線電存取(utra)或演進型-utra目標家用節點b及執行 用於選擇的ip訊務卸載連接移動性的方法
US10779357B2 (en) Method for avoiding handover failure
EP2351417B1 (en) Network gateway configured to provide a handover, converting and routing function
WO2009006774A1 (en) Interior hangover method in a system
WO2008092408A1 (en) Method, device and system for establishing s1 signaling connection in evolved network
JP2012527133A (ja) ユーザ装置をページングするための方法、装置およびシステム
KR20130014398A (ko) 핸드오버 지원 장치 및 방법
WO2009046672A1 (fr) Procédé et équipement dans un réseau d'évolution
JP6345336B2 (ja) 閉鎖加入者グループ身元状態のアップデート方法、システム及び基地局
WO2013033883A1 (zh) 处理切换的方法、移动性管理网元、无线接入网元和系统
WO2013044668A1 (zh) 一种处理lipa承载的方法和设备
WO2011076063A1 (zh) Lipa或sipto管理方法、装置和系统
WO2012155713A1 (zh) 一种切换操作方法和系统
US9848366B2 (en) Method for determining relocation process and method for determining handover process
WO2012167648A1 (zh) 一种进行lipa承载接入控制的方法、系统和设备
JP2015008543A (ja) 無線通信ルーティング及びアクセスポイント基地局
WO2012103773A1 (zh) 中继系统的过载控制方法及系统
WO2012155705A1 (zh) 一种切换到家庭基站的切换方法及基站
WO2013086727A1 (zh) 切换处理方法、设备和系统
KR20120030952A (ko) 위치등록 갱신절차를 결정하는 방법 및 핸드오버 절차를 결정하는 방법
WO2012174981A1 (zh) Ip分流连接的处理方法及装置

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: 12797063

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: 12797063

Country of ref document: EP

Kind code of ref document: A1