WO2013044668A1

WO2013044668A1 - Method and device for processing lipa bearer

Info

Publication number: WO2013044668A1
Application number: PCT/CN2012/078508
Authority: WO
Inventors: 周燕飞; 张娟
Original assignee: 电信科学技术研究院
Priority date: 2011-09-28
Filing date: 2012-07-11
Publication date: 2013-04-04
Also published as: CN102300336A; CN102300336B

Abstract

Embodiments of this application relate to the technical field of wireless communications, and more particularly to a method and device for processing a LIPA bearer, so as to deactivate the LIPA bearer when the LIPA mobility cannot be maintained. The method according to the embodiment of this application comprises: after receiving a handover request message from a source home base station and determining that a user equipment in need of a handover has already activated a LIPA bearer, a core network control node determining whether the LIPA bearer activated by the user equipment can be maintained after the handover; and after determining that the LIPA bearer cannot be maintained after the handover, the core network control node releasing the LIPA bearer. Since the LIPA bearer can be released during the handover after it is determined that the LIPA bearer activated by the user equipment cannot be maintained after the handover, the LIPA mobility is achieved, and the network performance and system efficiency are improved.

Description

The present invention claims the Chinese patent application filed on September 28, 2011, the Chinese Patent Application No. 201110294248.X, entitled "A Method and Apparatus for Handling LIPA Bearers" Priority is hereby incorporated by reference in its entirety.

Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and device for processing a LIPA bearer.

Background technique

Local IP Access (LIP) is a technology that allows user equipment to access a local network associated with the home base station through an (evolved) Home Base Station (Home (evolved) NodeB, H(e) B). . The user equipment accesses the local network through a local gateway (LGW), such as a home network or a corporate network. The advantage of LIPA technology is that the user equipment that activates LIPA can obtain a better data routing path without the user's core network passing through the carrier core network.

In the 3rd Generation Partnership Project (3GPP) RIO (version) phase, the home base station and the local gateway are implemented on the same physical entity, and the mobility of the LIPA connection is not supported, that is, when LIPA is activated. When the connected mode user equipment moves out of the home base station coverage, the home base station triggers the local gateway to initiate a connection release process by internal signaling to release the LIPA bearer, and then initiates the handover.

In the 3GPP R11 phase, the home base station and the local gateway may be separate physical entities and support the continuity of the LIPA connection within the local Home Base Station network (Local H(e)B Network, LHN). The local home base station network, as shown in Figure 1, where the Packet Data Network (PDN) is also the local network.

An LHN consists of a set of H(e) Bs that can obtain IP connectivity to the local network through one or more LGWs. A home base station can belong to only one LHN; one LGW can belong to only one LHN; when the user equipment moves between the same LHN home base station, the continuity of the LIPA connection needs to be supported, and the LGW of the LIPA connection does not change.

Due to the restricted access characteristics of the LIPA bearer, the mobility management process also needs to perform each access point name of each closed user group (per Close Subscriber Group, per CSG) for the user equipment activated with the LIPA bearer based on the subscription data. Per Access Point Name, per APN), that is, whether the CSG ID of the home base station is signed, and whether the LIPA APN is allowed to access through the CSG ID. When the per CSG per APN access control fails, the LIPA bearer must be deactivated.

LIPA mobility is not supported in current systems, that is, once a handover occurs, the LIPA bearer must be activated before the handover process begins. However, due to R11's support for LIPA mobility, there is a need for a solution that supports LIPA mobility.

In summary, there is currently no solution to support LIPA mobility. Summary of the invention

Embodiments of the present invention provide a method and a device for processing a LIPA bearer, to activate a LIPA bearer when LIPA mobility cannot be maintained.

A method for processing a local IP access LIPA bearer provided by the embodiment of the present invention includes:

When the core network control node receives the request handover message from the source home base station, and determines that the user equipment that needs to be switched has activated the LIPA bearer, it determines whether the LIPA bearer activated by the user equipment can be maintained after the handover;

The core network control node releases the LIPA bearer after determining that the LIPA bearer cannot be maintained after being switched.

An apparatus for processing a LIPA bearer provided by an embodiment of the present invention includes:

a determining module, configured to: when receiving the request handover message of the source home base station, and determining that the user equipment that needs to be switched has activated the LIPA bearer, determining whether the LIPA bearer activated by the user equipment can be maintained after performing the handover;

And a releasing module, configured to release the LIPA bearer after determining that the LIPA bearer cannot be maintained after performing the handover. When the handover occurs, it is determined that the LIPA bearer activated by the user equipment cannot be maintained after the handover, and the LIPA bearer can be released, thereby realizing LIPA mobility, improving network performance and system efficiency.

DRAWINGS

1 is a schematic diagram of a local home base station network in the background art;

2 is a schematic flowchart of a method for processing a LIPA bearer according to an embodiment of the present invention;

3 is a schematic flowchart of a method for operating a control node of a core network according to an embodiment of the present invention;

4 is a schematic flowchart of a method for a target base station to be a home base station in an LTE system according to an embodiment of the present invention;

5 is a schematic flowchart of a method for a target base station to be a macro base station in an LTE system according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a method for a target base station to be a home base station in a UMTS system according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a device for processing a LIPA bearer according to an embodiment of the present invention.

detailed description

For the solution that supports the LIPA mobility, the core network control node of the embodiment of the present invention receives the request handover message from the source home base station, and determines that the user equipment activates the LIPA bearer, and if it is determined that the user equipment activates the LIPA bearer in the handover After it cannot be maintained, the LIPA bearer is released. When the handover occurs, it is determined that the LIPA bearer activated by the user equipment cannot be maintained after the handover, and the LIPA bearer can be released, thereby realizing LIPA mobility, improving network performance and system efficiency.

The request handover message in the embodiment of the present invention includes context information carried by the LIPA. Preferably, the context information carried by the LIPA in the request handover message is included in an additional container in the request handover message.

The additional container is used to avoid the impact on the Radio Access Network (RAN) node of the Pre-Rll in the 3GPP GPP SA2 conference, and avoids the source-to-target side transparent capacity received by the target RAN node. Number of Radio Access Bearers (RABs) in the Source to Target Transparent Container and requested by the core network side

The number of RABs is inconsistent, and the specifics are:

The source home base station uses two Radio Resource Control (RRC) containers in the handover request message, where the original Source to Target Transparent Container encapsulates the non-LIPA bearer and adds an RRC container (ie, an additional container). ) Encapsulate the LIPA bearer.

In an implementation, the core network control node of the embodiment of the present invention includes, but is not limited to, one of the following nodes: a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN) General Packet Radio Service, GPRS).

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings.

As shown in FIG. 2, the method for processing a LIPA bearer according to an embodiment of the present invention includes the following steps:

Step 201: The core network control node receives the request handover message from the source home base station, and determines that the user equipment that needs to be switched has activated the LIPA bearer, and determines whether the LIPA bearer activated by the user equipment can be maintained after the handover; The core network control node releases the LIPA bearer after determining that the LIPA bearer cannot be maintained after the handover.

In the implementation, the request handover message includes context information of the LIPA bearer, and the context information may uniquely correspond to the LIPA bearer activated by the user equipment.

Among them, the way in which the core network control node determines whether the LIPA bearer can be maintained depends on different situations. The following are several cases:

Case 1: The core network control node performs access control of the per CSG and per APN based on the subscription data to the target base station, and after access control through the per CSG, but does not pass the access control of the per APN, it is determined that the LIPA bearer is in the Cannot be held after switching.

Specifically, when the core network control node performs the access control based on the subscription data per CSG per APN to the target base station, if the CSG ID of the target side is not signed or signed but expired, it indicates that the subscription data per CSG fails, the core network The control node will return a handover reject message to the source home base station;

If the core network control node continues to perform per APN access control based on the subscription data per CSG: If the APN of the LIPA connection is not included in the APN list allowed by the CSG ID, that is, the per APN access control fails, the core network The control node determines that the LIPA bearer cannot be maintained after the handover.

Preferably, after the per APN access control fails, it is determined that the LIPA bearer cannot be maintained after the handover is performed. In step 202, the core network control node does not transmit the LIPA information corresponding to the LIPA bearer to the target side.

Specifically, in step 202, if the core network control node needs to be changed after the handover, the forward relocation request message transmitted by the core network control node to the target core network control node does not include the LIPA information;

If the core network control node does not need to be changed after the handover, the core network control node transmits the handover request to the target base station. The LIPA information is not included in the message.

In the implementation, the Forward Relocation Request message sent by the core network control node to the target core network control node does not include the LIPA information. The core network control node does not include the additional container containing the LIPA bearer in the Forward Relocation Request message, and is in Forward. The bearer list to be established in the Relocation Request message does not include the context information of the LIPA bearer.

The LIPA information that is not included in the handover request message transmitted by the core network control node to the target base station may be: The core network control node does not include the additional container containing the LIPA bearer in the handover request message, and the bearer list to be established in the handover request message. Does not include LIPA bearer context information.

Case 2: After the target base station passes the access control of the per CSG and the per APN, the core network control node sends a handover request message including the context information of the LIPA bearer to the target base station, and determines the target base station according to the received target base station return information. After the LIPA bearer is not accepted, it is determined that the LIPA bearer cannot be maintained after the handover, and the context information of the LIPA bearer in the handover request message includes the context information included in the request handover message.

Specifically, in the foregoing case 2, if the core network control node determines that the LIPA bearer can be maintained after the handover, the handover request message including the context information of the LIPA bearer is sent to the target base station, and the core network control node returns according to the target side. The message determines if the LIPA bearer is accepted by the target side, if accepted. Then, the core network control node determines that the LIPA bearer can be maintained after the handover; if not, the core network control node determines that the LIPA bearer cannot be maintained after the handover.

In the implementation, there are two ways to determine whether the target side accepts the LIPA bearer:

1) If the accepted bearer list contains LIPA bearer context information, the target side accepts the LIPA bearer; otherwise, the LIPA bearer is not accepted;

2) If the bearer list that fails to be established contains the LIPA bearer context information, the target side does not accept the LIPA bearer, otherwise it indicates that the LIPA bearer is accepted.

Preferably, in step 201, after receiving the request handover message from the source home base station, the core network control node may determine whether the target base station is a macro base station, and if so, directly determine that the LIPA bearer cannot be maintained after the handover; , continue to judge according to the above judgment method.

Preferably, in step 201, after receiving the request handover message from the source home base station, the core network control node may determine whether the target base station is a closed or mixed mode home base station, and if yes, continue to determine whether the user equipment activates the LIPA bearer. If the home base station is not in the closed or mixed mode, the home base station may be processed according to the processing manner of the macro base station, for example, directly determining that the LIPA bearer cannot be maintained after the handover.

In the implementation, determining the type of the target base station and determining whether the user equipment activates the LIPA bearer, the timing of the two determinations is not necessarily related, and a specific judgment timing may be selected as needed. Preferably, the order of the two steps is: first determine whether to activate LIPA, and if so, continue to determine the target base station type, there are only two possibilities: first, macro base station or open mode home base station; second, closed Or mixed mode home base station; the first type does not need to do per CSG per APN access control, and LIPA can not be maintained; the second need to do per CSG per APN access control, and subsequent need to continue to determine whether LIPA can be maintained.

In step 202, the core network control node notifies the gateway node to release the LIPA bearer after determining that the LIPA bearer cannot be maintained (including the case 1 and/or the case 2 cannot be maintained).

If the core network control node needs to send a handover command, preferably, the core network control node notifies the gateway node to release the LIPA bearer before transmitting the handover command after determining that the LIPA bearer cannot be maintained after the handover.

Specifically, in a Long Term Evolution (LTE) system, a core network control node releases a LIPA bearer through a PDN Disconnection process; in a Universal Mobile Telecommunication System (UMTS) system, a core The network control node releases the LIPA bearer through a packet data protocol context deactivation (PDP context Deactivation) procedure.

Preferably, in the PDN Disconnection process or the PDP Context Deactivation process, the core network control node only deletes the LIPA bearer at the gateway node, and does not notify the source home base station to release the LIPA bearer.

Preferably, if the core network control node needs to send a handover command, in step 202, the core network control node releases the LIPA bearer after determining that the LIPA bearer cannot be maintained after the handover is performed, before sending the handover command.

Preferably, in step 202, after the core network control node releases the LIPA bearer, the source home base station is instructed to release the LIPA bearer in the handover command message.

Specifically, the core network control node adds the context information carried by the LIPA to the bearer list that needs to be released in the handover command message.

As shown in FIG. 3, the method for operating a core network control node according to an embodiment of the present invention includes the following steps: Step 301: A core network control node receives a request handover message from a source home base station, and the user equipment activates the LIPA bearer.

Step 302: The core network control node determines whether the target home base station is a closed or mixed mode home base station, if yes, step 303 is performed, otherwise, step 309 is performed;

Step 303: The core network control node performs per-CSG access control based on the subscription data to the target base station, and determines whether the per CSG access control is passed. If yes, step 304 is performed; otherwise, step 308 is performed;

Step 304: The core network control node performs per-PN access control based on the subscription data to the target base station, and determines whether the per APN access control is passed. If yes, step 305 is performed; otherwise, step 309 is performed;

Step 305: The core network control node sends, to the target base station, a handover request message that includes context information of the LIPA bearer.

Step 306: The core network control node determines, according to the received target base station return information, whether the target base station can accept the LIPA bearer, if yes, step 307 is performed; otherwise, step 310 is performed;

Step 307: The core network control node sends a handover command to the source home base station, and subsequently follows the subsequent process of the S1 handover procedure in the protocol TS 23.401, or the service radio network subsystem relocation of the protocol TS 23.060 (Serving RNS) Relocation) The subsequent process of the process is performed.

Step 308: The core network control node returns a handover rejection message to the source home base station, and the process ends.

Step 309: The core network control node does not transmit the LIPA information corresponding to the LIPA bearer to the target side.

Step 310: The core network control node deactivates the LIPA bearer on the core network side before the handover command is sent, and instructs the source base station to release the LIPA bearer in the sending handover command (where the deactivation operation and the subsequent operation of the handover may be performed in parallel), ending the present Process.

The scheme of the present invention will be further described below with three examples. See FIG. 4 to FIG. 6 for details.

It should be noted that, in the following example, it is assumed that the context information of the LIPA bearer is included in the additional container in the request switching message, and the scheme not included in the additional container is similar to the scheme included in the additional container. Let me repeat.

As shown in FIG. 4, the method for the target base station to be the home base station in the LTE system according to the embodiment of the present invention includes the following steps: Assume that the target base station is a home base station in the LTE system, and the CSG ID is signed, but the LIPAAPN cannot be used by the CSG according to the subscription data. Cell access; the core network control node remains unchanged after handover.

Step 401: The source home base station sends a handover request (HO Required) message to the MME, where the additional container is included;

Step 402: After determining that the terminal activates the LIPA bearer in the HO Required message, and the target base station is a closed or mixed home base station, the MME performs per CSG per APN access control on the target base station, and according to the subscription, the LIPA APN cannot be used by the The CSG cell accesses, the MME will not deliver the LIPA bearer and the additional container to the target base station; Step 403: The MME sends a handover request (HO Request) message to the target home base station, which does not include an additional container, and the evolved radio access bearer (Evolved) The RAPA, ERAB) ERABs to be Setup List does not include the LIPA bearer;

Step 404: The target home base station returns a handover request acknowledgement (HO Request ACK) message.

Step 405: The MME initiates a LIPA core network bearer deletion process.

The step operation may be performed at any time before the start of step 406, and there is no inevitable sequence with step 403 and step 404;

Step 406: The MME sends a handover command (HO Command) message to the source base station, and includes a LIPA bearer in the bearer list (ERABs to Release List) in which the access radio bearer needs to be released.

In summary, since the MME does not transmit any LIPA bearer related information to the target side base station, the target side base station does not allocate resources for the LIPA bearer. After the switchover, the user equipment releases the LIPA bearer, and the source side LIPA bearer is initiated and deleted by the MME during the switching process.

As shown in FIG. 5, the method for the target base station to be a macro base station in the LTE system according to the embodiment of the present invention includes the following steps: Assume that the target base station is a macro base station in the LTE system; the core network control node changes after the handover, and the source core network node is used. Optimized method. Step 501: The source home base station sends an HO Required message to the MME, which includes an additional container. Step 502: Since the target base station is a macro base station, that is, the LIPA bearer cannot be maintained after the handover, the MME does not target the Forward Relocation Request message. The MME delivers the LIPA bearer and the additional container. Step 503: The target MME sends a handover request (HO Request) message to the target base station, where the additional container is not included, and the LIPA bearer is not included in the ERABs to be Setup List.

Step 504: The target home base station returns a handover request acknowledgement (HO Request ACK) message.

Step 505: The target MME sends a Forward Relocation Response message to the source MME.

Step 506: The MME sends a handover command (HO Command) message to the source base station, and includes a LIPA bearer in the ERABs to Release List.

The source MME may initiate a LIPA bearer deactivation process between steps 502 and 506, and there is no necessary timing relationship between the steps 503 and 505.

In summary, since the source MME does not transmit any LIPA bearer related information to the target MME, the target side base station does not allocate resources for the LIPA bearer. After the switchover, the user device releases the LIPA bearer.

As shown in FIG. 6, the method for the target base station to be a home base station in the UMTS system according to the embodiment of the present invention includes the following steps: Assume that in the UMTS system, the target base station is a home base station; the target base station can access control through per CSG per APN, but with the source The base stations belong to different LHNs; after switching, the core network control node SGSN is unchanged.

Step 601: The source home base station sends a Relocation Required message to the SGSN, where the additional container is included;

Step 602: The SGSN performs per CSG per APN access control, and the access control is successful according to the subscription data. Step 603: The SGSN sends a relocation request (Relocation Request) to the target base station, where the access control is successful, including the additional container and the LIPA. Carry

Step 604: After receiving the additional container, the target home base station determines that the target home base station treats the LIPA bearer as an unacceptable bearer process, and returns a relocation request ACK. The message does not contain an additional container, and the LIPA bearer is included in the RABs Fail to Setup list.

Step 605: The SGSN releases the core network side LIPA bearer because the LIPA bearer is not accepted by the target side, and the operation is completed before the relocation command message is sent.

The step operation may be performed at any time before the start of step 606, and there is no necessary sequence with step 603 and step 604;

Step 606: The SGSN sends a Relocation Command message to the source home base station, where the LIPA bearer is included in the RABs to be Released list.

In summary, when the LIPA access control passes, because the target side judges that the LIPA bearer cannot be maintained, the core network control section The point is informed by the message returned by the target side that the LIPA bearer needs to be released and the release is initiated before the user equipment switches to the target side.

Based on the same inventive concept, an embodiment of the present invention further provides a device for processing a LIPA bearer. Since the principle of solving the problem is similar to the method for processing the LIPA bearer, the implementation of the device can refer to the implementation of the method. No longer.

As shown in FIG. 7, the device for processing a LIPA bearer according to an embodiment of the present invention includes: a determining module 70 and a releasing module 71. The determining module 70 is configured to: when receiving the request handover message of the source home base station, and determining that the user equipment that needs to be switched has activated the LIPA bearer, determining whether the LIPA bearer activated by the user equipment can be maintained after performing the handover;

The release module 71 is configured to release the LIPA bearer after determining that the LIPA bearer cannot be maintained after the handover is performed. Preferably, the determining module 70 performs access control of the per CSG and the per APN based on the subscription data to the target base station, and determines that the LIPA bearer is after the access control through the per CSG but not through the access control of the per APN. After the handover is performed, the handover is not performed; and/or after the target base station passes the access control of the per CSG and the per APN, the handover request message including the context information of the LIPA bearer is sent to the target base station, and the information is returned according to the received target base station. After the target base station cannot accept the LIPA bearer, it is determined that the LIPA bearer cannot be maintained after the handover, and the context information of the LIPA bearer includes the context information included in the request handover message.

Preferably, the determining module 70 performs access control of the per CSG and per APN based on the subscription data to the target base station after determining that the target base station is not the macro base station.

Preferably, the determining module 70 performs access control of the per CSG and per APN based on the subscription data to the target base station after determining that the target base station is a closed or mixed mode home base station.

Preferably, the determining module 70 determines that the target base station is a macro base station or a home base station in a non-closed mode or a non-hybrid mode home base station, and determines that the LIPA bearer cannot be maintained after the handover.

Preferably, the release module 71 does not pass the LIPA information corresponding to the LIPA bearer to the target side after determining that the target base station passes the access control of the per CSG but does not pass the access control of the per APN.

Preferably, the release module 71 passes the per CSG per APN control, but after the target base station does not accept the LIPA bearer, it determines that the LIPA bearer cannot be maintained, and notifies the gateway node to release the LIPA bearer before transmitting the handover command.

Preferably, if the core network control node needs to be changed after the handover, the release module 71 does not include the LIPA information in the Forward Relocation Request message transmitted to the target core network control node.

If the core network control node does not need to be changed after the handover, the release request message transmitted by the release module 71 to the target base station does not include the LIPA information.

Preferably, the release module 71 does not send the additional container containing the LIPA bearer, and does not include the LIPA bearer context information in the bearer list that needs to be established.

Preferably, the release module 71 fails to maintain after determining that the LIPA bearer cannot be maintained (including the access control by the target base station through the per CSG, but not through the access control of the per APN; and/or due to the per CSG per The APN control passes, but the target base station does not accept the LIPA bearer to determine that it cannot be maintained. The gateway node is notified to release the LIPA bearer before sending the handover command.

Preferably, the release module 71 notifies the gateway node to release the LIPA bearer through the PDN Disconnection process or the PDP Context Deactivation process after determining that the LIPA bearer cannot be maintained after the handover.

Preferably, the release module 71 does not notify the source home base station to release the LIPA bearer during the PDN Disconnection process or the PDP Context Deactivation process after determining that the LIPA bearer corresponding to the context information of the LIPA bearer cannot be maintained after the handover.

Preferably, after releasing the LIPA bearer, the release module 71 instructs the source home base station to release the LIPA bearer in the handover command message.

Preferably, the release module 71 adds the context information carried by the LIPA to the list of bearers that need to be released in the handover command message.

When the handover occurs, it is determined that the LIPA bearer activated by the user equipment cannot be maintained after the handover, and the LIPA bearer can be released, thereby realizing LIPA mobility, improving network performance and system efficiency.

Those skilled in the art will appreciate that 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 is in the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) in which computer usable program code is embodied.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each process and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

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.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram. It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

Rights request

A method for processing a local IP access LIPA bearer, the method comprising:

2. The method according to claim 1, wherein the core network control node determines whether the LIPA bearer can be maintained to include:

The core network control node performs access control for each closed subscriber group per CSG and per access point name per APN based on the subscription data to the target base station, and is controlled by access through the per CSG, but fails to pass per APN After the access control, determining that the LIPA bearer cannot be maintained after switching; and/or

After the target base station passes the access control of the per CSG and the per APN, the core network control node sends a handover request message including the context information of the LIPA bearer to the target base station, and according to the received target base station return information, After determining that the target base station cannot accept the LIPA bearer, determining that the LIPA bearer cannot be maintained after performing handover, where the context information of the LIPA bearer includes context information included in the request handover message.

The method according to claim 2, wherein before the core network control node performs the access control of the per CSG and the per APN based on the subscription data to the target base station, the method further includes:

The core network control node determines that the target base station is a closed or hybrid mode home base station.

The method according to claim 2, wherein the core network control node determines whether the LIPA bearer can be maintained to include:

If the target base station is a macro base station or a home base station in a non-closed mode or a home base station in a non-mixed mode, the core network control node determines that the LIPA bearer cannot be maintained after performing handover.

The method according to any one of claims 2 to 4, wherein the context information carried by the LIPA in the request handover message is in an additional container information element.

The method according to claim 2, wherein the core network control node determines that the target base station passes the per CSG access control, but does not pass the per APN access control;

The releasing, by the core network control node, the LIPA bearer includes:

The core network control node does not transmit the LIPA information corresponding to the LIPA bearer to the target side.

The method according to claim 6, wherein the core network control node does not transmit LIPA information to the target side, including:

If the core network control node needs to be changed after the handover, the forward relocation request transmitted by the core network control node to the target core network control node does not include the LIPA information;

If the core network control node does not need to be changed after the handover, the core network control node transmits the handover to the target base station. The request message does not contain LIPA information.

The method of claim 7, wherein the transmitting, by the core network control node, the LIPA information to the target side comprises:

The core network control node does not send the additional container containing the LIPA bearer, and does not include the LIPA bearer context information in the bearer list that needs to be established.

The method of claim 1, wherein the releasing, by the core network control node, the LIPA bearer comprises:

The core network control node notifies the gateway node to release the LIPA bearer before transmitting the handover command.

The method of claim 9, wherein the core network control node notifying the gateway node to release the LIPA bearer includes:

The core network control node disconnects the PDN Disconnection process or the packet data protocol context deactivation through the packet data network to notify the gateway node to release the LIPA bearer.

The method of claim 10, wherein: after determining that the LIPA bearer cannot be maintained, the core network control node further includes:

The core network control node does not notify the source home base station to release the LIPA bearer during the PDN Disconnection process or the PDP Context Deactivation process.

The method of any one of claims 1 to 4, 9 to 11, wherein the core network control node further comprises: after releasing the LIPA bearer:

The core network control node instructs the source home base station to release the LIPA bearer in a handover command message.

The method according to claim 12, wherein the core network control node instructing the source home base station to release the LIPA bearer comprises:

The core network control node adds context information of the LIPA bearer to the list of bearers to be released in the handover command message.

14. A device for processing a LIPA bearer, the device comprising:

And a releasing module, configured to release the LIPA bearer after determining that the LIPA bearer cannot be maintained after performing the handover.

The device of claim 14, wherein the determining module is specifically configured to:

Performing access control of the per CSG and per APN based on the subscription data to the target base station, and after access control through the per CSG, but not through the access control of the per APN, determining that the LIPA bearer cannot be maintained after the handover is performed. And/or after the target base station passes the access control of the per CSG and the per APN, sends a handover request message including the context information of the LIPA bearer to the target base station, and according to the received target base station return information, in determining the location After the target base station cannot accept the LIPA bearer, it is determined that the LIPA bearer cannot be maintained after performing handover, where The context information carried by the LIPA includes context information included in the request handover message.

The device of claim 15, wherein the determining module is further configured to:

After determining that the target base station is a closed or mixed mode home base station, the target base station performs access control of the per CSG and per APN based on the subscription data.

If the target base station is a macro base station or a home base station in a non-closed mode or a home base station in a non-mixed mode, it is determined that the LIPA bearer cannot be maintained after the handover.

The device according to claim 15, wherein the release module is specifically configured to:

After determining that the target base station passes the access control of the per CSG, but does not pass the access control of the per APN, the LIPA information corresponding to the LIPA 7 is not transmitted to the target side.

The device of claim 18, wherein the release module is further configured to:

After determining that the LIPA bearer cannot be maintained, if the core network control node needs to be changed after the handover, the Forward Relocation Request message transmitted to the target core network control node does not include the LIPA information;

If the core network control node does not need to be changed after the handover, the handover request message transmitted to the target base station does not include the LIPA information.

The device of claim 19, wherein the release module is further configured to:

After determining that the LIPA bearer cannot be maintained, the additional container containing the LIPA bearer is not sent, and the LIPA bearer context information is not included in the bearer list that needs to be established.

The device according to claim 14, wherein the release module is specifically configured to:

After determining that the LIPA bearer cannot be maintained, the gateway node is notified to release the LIPA bearer before sending the handover command.

The device of claim 21, wherein the release module is further configured to:

The gateway node is notified to release the LIPA bearer through a PDN Disconnection procedure or a PDP Context Deactivation procedure.

The device of claim 22, wherein the release module is further configured to:

After determining that the LIPA bearer cannot be maintained after the handover, the source home base station is not notified to release the LIPA bearer during the PDN Disconnection process or the PDP Context Deactivation process.

The device according to any one of claims 14-17, 20-23, wherein the release module is further configured to:

After releasing the LIPA bearer, the source home base station is instructed to release the LIPA bearer in a handover command message.

The device of claim 24, wherein the release module is further configured to:

The context information carried by the LIPA is added to the list of bearers that need to be released in the handover command message.