WO2011015124A1

WO2011015124A1 - Method, notification method and system for realizing control of local ip access

Info

Publication number: WO2011015124A1
Application number: PCT/CN2010/075637
Authority: WO
Inventors: 霍玉臻; 朱春晖; 周娜; 宗在峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-08-06
Filing date: 2010-08-02
Publication date: 2011-02-10
Also published as: WO2011015092A1; CN101990313A; CN101990313B

Abstract

A method, a notification method and a system for realizing the control of a local IP access (LIPA) are provided. A wireless side network element/a Home (e)NodeB gateway reports the capability information of an LIPA to Internet, and/or the capability information of an LIPA to home based network, and/or the information of an accessible and suitable local access gateway for the wireless side network element/the Home (e)NodeB gateway to a mobile management entity. According to the obtained capability information, the mobile management entity establishes the LIPA connection for a user, and determines that it is the LIPA connection to Internet or the LIPA connection to home based network. The present technical solution makes a reasonable choose for the user to establish which type of LIPA connection, and ensures the security of the LIPA access from a non-CSG (closed subscriber group) user.

Description

Method, notification method and system for realizing local IP access control

The present invention relates to a home base station system, and more particularly to a method, a notification method, and a system for implementing local operator network protocol (IP, Internet Protocol) access control. Background technique

The 3rd Generation Partnership Project (EPS) evolved packet system (EPS, Evolved Packet System), evolved by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW, also known as PDN GW), Home Subscriber Server (HSS, Home Subscriber Server), 3GPP's AAA, Authentication, Authorization and Accounting server, Policy and Charging Rules Function (PCRF) entity and other supporting nodes.

FIG. 1 is a schematic diagram of a composition of an existing EPS architecture. As shown in FIG. 1 , the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management. The access gateway includes S. - GW and P-GW, wherein the S-GW is an access gateway device connected to the E-UTRAN, configured to forward data between the E-UTRAN and the P-GW, and is responsible for buffering the paging waiting data; -GW is a border gateway between EPS and Packet Data Network (PDN), responsible for PDN access and forwarding data between EPS and PDN; authentication authorization server includes HSS, AAA server; PCRF is policy and meter The fee-based functional entity, the PCRF is connected to the IP service network through the Rx receiving interface to obtain service information. In addition, the PCRF is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the IP bearer. Establish, guarantee the quality of service (QoS) of service data, and perform charging control.

The home base station is a small, low-power base station deployed in indoor places such as homes and offices. The main purpose is to provide users with higher service rates and lower the cost of using high-speed services, while making up for existing distributed Insufficient coverage of cellular wireless communication systems. The advantages of a home base station are affordability, convenience, low power output, plug and play, and more.

The home base station can be directly connected to the core network, or can be accessed to the core network through the logical network element of the home base station gateway, as shown in FIG. 1 , wherein the home base station gateway is mainly used to verify the security of the home base station, and handle the home base station. Registration, operation and maintenance management of the home base station, configuration and control of the home base station according to the operator's requirements, responsible for exchanging data of the core network and the home base station. The access gateway may be an S-GW, a P-GW, a Serving GPRS Support Node (SGSN), or a Gateway GPRS Support Node (GGSN). The local access gateway may be a local SGW (L-SGW, Local SGW), a local PGW (L-PGW, Local PGW), a virtual SGW (V-SGW, Virtual SGW), a virtual PGW (V-PGW, Virtual PSGW), The local GGSN (L-GGSN, Local GGSN) may also be a data offload function entity.

In order to implement local IP access (LIPA), that is, the local access or other IP data offloading of the local IP access or Internet service of the other IP devices or the Internet in the home network, a local access gateway is added, such as Figure 1, Figure 2. The local access gateway can provide strong support for the local IP access technology. The local access gateway can be set up with the wireless side network element or set in the vicinity of the wireless side network element, or can be set up with the home base station gateway or set in the home base station gateway. nearby.

2 is a schematic diagram of a data flow path of local IP access and traditional core network IP access in a mobile communication network architecture. As shown in FIG. 2, a traditional core network IP access data path can be established for a user supporting local IP access. Local IP access data path. As shown in Figure 2, for this The IP access connection, the local IP access data path from the terminal to the wireless side network element/home base station gateway to the local access gateway (L-SGW, L-PGW), and the data transmission does not pass through the core network. In order to implement the LIPA function, two connections can be established. As shown in FIG. 2, the local IP access data path 1 directly accesses the Internet, and the local IP access data path 2 directly accesses other IP devices on the home network.

When the UE initiates an attach request, a PDN connection setup request, or a PDP context activation request, the mobility management entity needs to determine whether a local IP access connection can be established for this request, and which local IP access connection needs to be established, such as the Internet LIPA (LIPA) To Internet) connection, or LIPA (home to network based network) connection. In order to achieve the above judgment, the mobility management entity needs to have the capability of the LIPA to Internet or LIPA to home based network, and whether the different types of users have the capability of LIPA to Internet or LIPA to home based network. In general judgment, it is also necessary to consider whether there is a suitable local access gateway that the wireless side network element/home base station gateway can access. When the above capabilities change, the mobility management entity needs to determine whether the existing LIPA connection is valid based on the changed capabilities. The above operations are collectively referred to as LIPA access control.

Whether a closed user, ie, a CSG user, has LIPA to Internet capability or LIPA to home based network capability can be achieved by signing up. For non-CSG users, this capability cannot be reflected in the contract. If the LIPA access of non-CSG users is not restricted, security risks may occur, such as unidentified non-CSG users can access the home network arbitrarily; for some enterprises/publics The home base station and the macro station deployed at the site need non-CSG users to access the home network or the Internet through LIPA. Therefore, it is necessary for the wireless side network element/home base station gateway to set whether the non-CSG user has LIPA to Internet capability or LIPA to home based. The network capability needs to be reported to the core network for the mobility management entity to perform LIPA access control. At the same time, when the mobility management entity performs the access control of the LIPA, it is also necessary to consider whether there is a suitable local access gateway accessible by the wireless side network element/home base station gateway, for example, the wireless side network element/home base station gateway needs to be selected. A local access gateway nearby or with it. When the above-mentioned LIPA to Internet capability or LIPA to home based network capability changes (such as the wireless side network element/home base station gateway changes due to the change of the terminal mobility, or the capability of the wireless side network element/home base station gateway itself changes) The mobility management entity needs to determine whether the LIPA connection established by the user has expired according to the foregoing capability information, for example, the non-CSG user can no longer establish a LIPA to home based network connection, etc., so as to process the failed connection, such as release.

For the LIPA connection, the geographical coverage of the local access gateway is limited. Considering the route optimization, the terminal mobility may cause the local access gateway to change. At this time, the mobility management entity determines that the LIPA connection established by the user is invalid, and The failed connection is processed as released.

For the processing of the failed LIPA connection by the core network, the terminal needs to be aware, so as to perform appropriate operations, such as rebuilding the released LIPA connection, and the current architecture and process cannot implement the terminal's perception, thereby affecting the user experience.

In the current architecture and process, the above information is not distinguished and reported. Therefore, the prior art has a great limitation, and it is not possible for the user to reasonably choose which type of LIPA connection to create or retain. Summary of the invention

In view of this, the main object of the present invention is to provide two methods for implementing local IP access control, which can reasonably select which type of LIPA connection to create or retain.

Another object of the present invention is to provide two systems for implementing local IP access control, which can reasonably select which type of LIPA connection to create or retain.

It is still another object of the present invention to provide a notification method for implementing local IP access control, which enables the terminal to obtain the cause of the connection failure, so that the terminal can perform reasonable processing, such as reestablishing the LIPA connection or not processing.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for implementing local IP access control, the method comprising:

The wireless side network element/home base station gateway reports the Internet local IP access to the mobility management entity. Functional LIPA capability information, and/or home network LIPA capability information, and/or appropriate local access gateway information accessible by the wireless side network element/home base station gateway;

The mobility management entity determines whether to establish LIPA for the user according to the obtained Internet LIPA capability information, and/or the home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway. connection.

When the Internet LIPA capability information, and/or the home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway are changed, the method further includes:

The wireless side network element/home base station gateway reports the changed capability information to the mobility management entity, and the mobility management entity determines, according to the obtained changed capability information, whether the LIPA connection established by the user has expired and is released. Invalid connection.

The method further includes: the mobility management entity sending a specific cause value to the terminal, or sending an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or a corporate network local network LIPA connection, or an Internet service A split operation connection, or a specific IP data offload connection failure indication, is used to indicate that the terminal LIPA connection is invalid, that is, a specific cause/indication for indicating the terminal LIPA connection reactivation or connection failure.

According to the operator policy or the local policy, the mobility management entity directly converts the LIPA connection that cannot be created into a core network connection, and creates a core network connection for the user.

The method of reporting the changed capability information to the mobility management entity is: the radio side network element/home base station gateway reports the changed capability information to the mobility management entity by configuring an update request or a registration request.

In the LTE system, the mobility management entity is a mobility management unit MME, and the mobility management entity releases the invalid LIPA connection, including:

Sending, by the MME, a session deletion request to the local packet data network gateway L-PGW, the L-PGW triggers release of the bearer of the local IP connection, and returns a session deletion response to the MME. Interest rate

The MME initiates a bearer deactivation request to the radio side network element, where the bearer deactivation request message carries a specific cause value, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection. Or enterprise network local network LIPA connection failure indication, used to indicate terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, or enterprise network local network LIPA connection, or Internet service diversion operation connection, or specific IP The data offload connection is invalid;

The radio side network element performs an RRC connection configuration process, and sends an RRC connection configuration message to the terminal, where the RRC connection configuration message carries a specific cause value, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local Network LIPA connection, or enterprise network local network LIPA connection, or Internet service traffic distribution connection, or specific IP data offload connection failure indication, used to indicate terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, Or the enterprise network local network LIPA connection, or the offload operation connection of the Internet service, or the specific IP data offload connection is invalid;

The terminal replies to the radio side network element with an RRC connection configuration complete message, and the radio side network element sends a bearer deactivation response message to the mobility management entity.

When there is a local serving gateway L-SGW, the information interaction between the mobility management entity and the L-PGW is forwarded by the L-SGW.

The L-SGW is set in the radio side network element/home base station gateway; or the L-SGW is located in the core network.

In the UTRAN system, the mobility management entity is a serving GPRS support node SGSN, and the mobility management entity releases the failed LIPA connection including:

The SGSN sends a PDP context deletion request to the local gateway GPRS support node GGSN; the L-GGSN triggers the release of the bearer of the local IP connection primary connection, and returns a PDP context deletion response to the SGSN; The SGSN sends a PDP context deactivation request to the terminal via the radio side network element, and carries a specific cause value in the PDP context deactivation request, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection. , or enterprise network local network LIPA connection, or Internet service shunt operation connection, or specific IP data offload connection failure indication, used to indicate terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, or enterprise network Local network LIPA connection, or offload operation connection of Internet service, or specific IP data offload connection failure;

The terminal returns a PDP context deactivation accept message to the SGSN via the radio side network element, and performs a radio access bearer release procedure.

The reported method includes:

When the user initiates an attach request, or a packet data network PDN connection setup request, or a service request, or a PDP context activation, the wireless side network element/home base station gateway carries the Internet LIPA capability information in the Sl/Iu initialization connection message, and The home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, is reported to the mobility management entity.

The Internet LIPA capabilities include Internet LIPA connectivity, and/or Internet traffic offload capabilities, and/or specific IP data offload capabilities;

The Internet LIPA connection capability information is a capability of a non-closed CSG user Internet LIPA connection, or a capability of a CSG user Internet LIPA connection, or a capability of a wireless side network element/home base station gateway, or any combination of the capability information;

The home network LIPA capability includes a home network LIPA connection capability, and/or a user local network LIPA connection capability, and/or an enterprise network local network LIPA connection capability;

The home network LIPA connection capability information is a capability of a non-CSG user home network LIPA connection, or a CSG user home network LIPA connection capability, or a non-CSG user local network LIPA connection capability, or a non-CSG user enterprise network local network LIPA connection capability. , CSG users Local network LIPA connection capability, or non-CSG user enterprise network local network LIPA connection capability, or wireless side network element/home base station gateway capability, or any combination of the capability information.

The wireless side network element is a base station, or a home base station, or a radio network controller RNC;

The mobility management entity is a mobility management unit MME, or a mobile switching center MSC, or a serving GPRS support node SGSN.

A method for implementing local IP access control, when a home base station gateway is not deployed or in a macro cell, the method includes:

When the wireless side network element is registered, the Internet local IP access function LIPA capability information, and/or the home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway are reported. To the mobility management entity;

The Internet LIPA capability information, and/or the home network LIPA capability information, and/or the appropriate local access gateway information that the wireless side network element/home base station gateway can access are carried in the S1 interface setup request message.

The wireless side network element reports the changed capability information to the mobility management entity, and the mobility management entity determines, according to the obtained changed capability information, whether the LIPA connection that the user has established has expired, and releases the failed connection.

The Internet LIPA connection capability information is for a non-closed CSG user Internet LIPA connection Capabilities, or capabilities of the CSG user's Internet LIPA connection, or the capabilities of the wireless side network element/home base station gateway, or any combination of the capability information;

The home network LIPA connection capability includes a home network LIPA connection capability, and/or a user local network LIPA connection capability, and/or an enterprise network local network LIPA connection capability;

The home network LIPA connection capability information is a capability of a non-CSG user home network LIPA connection, or a CSG user home network LIPA connection capability, or a non-CSG user local network LIPA connection capability, or a non-CSG user enterprise network local network LIPA connection capability. , CSG user local network LIPA connection capability, or CSG user enterprise network local network LIPA connection capability, or wireless side network element / home base station gateway capability, or any combination of the capability information.

A system for implementing local IP access control, including a wireless side network element/home base station gateway, a mobility management entity, wherein

The wireless side network element/home base station gateway is configured to report the Internet local IP access function LIPA capability information to the mobility management entity, and/or the home network LIPA capability information, and/or the wireless side network element/home base station gateway can access Suitable local access gateway information;

a mobility management entity, configured to determine, according to received Internet LIPA capability information, and/or home network LIPA capability information, and/or suitable local access gateway information accessible by the wireless side network element/home base station gateway Establish a LIPA connection for the user.

When the Internet LIPA capability information, and/or home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway are changed, the wireless side network element/ The home base station gateway is further configured to report the changed capability information to the mobility management entity;

The mobility management entity is further configured to determine, according to the obtained changed capability information, whether the LIPA connection established by the user has expired, and release the failed connection.

The mobility management entity is further configured to send a specific cause value to the terminal, or send an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or The enterprise network local network LIPA connection, or the offload operation connection of the Internet service, or the specific IP data offload connection failure indication, is used to indicate that the terminal LIPA connection is invalid, that is, a specific reason/indication for indicating that the terminal LIPA connection is reactivated or the connection is invalid.

The mobility management entity is further configured to directly convert a LIPA connection that cannot be created into a core network connection according to an operator policy or a local policy, and create a core network connection for the user.

The home network LIPA connection capability includes a home network LIPA connection capability, and/or a user local network LIPA connection capability, and/or an enterprise network local network LIPA connection capability.

A system for implementing local IP access control, when a home base station gateway is not deployed or in a macro cell, including a wireless side network element, a mobility management entity, where

When the wireless side network element is registered, the Internet local IP access function LIPA capability information, and/or home network LIPA capability information, and/or the appropriate local access accessible by the wireless side network element/home base station gateway The gateway information is reported to the mobility management entity;

A notification method for implementing local IP access control, when the mobility management entity determines the local The gateway relocation or Internet local IP access function changes the LIPA capability information, or the home network LIPA capability information changes, or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway changes, and is released. When LIPA is connected,

The mobility management entity sends a specific cause value to the terminal in the release process, or sends an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or a corporate network local network LIPA connection, or a traffic offload of the Internet service. An operational connection, or a specific IP data offload connection failure indication, is used to indicate a specific cause/indication of the LIPA connection reactivation or connection failure of the terminal.

After receiving the specific cause value or the failure indication, the terminal initiates a LIPA connection re-establishment process or ignores.

The specific cause value includes one or more of the following reasons: reactivation, capability change.

The specific cause/indication of the connection failure includes but one or more of the following reasons/indications: capability change, relocation.

In the LTE system, the mobility management entity is a mobility management unit MME, and the release process includes:

Sending, by the MME, a session deletion request to the local packet data network gateway L-PGW, the L-PGW triggers release of the bearer of the local IP connection, and returns a session deletion response message to the MME;

The wireless side network element performs an RRC connection configuration process, and sends an RRC connection configuration to the terminal. The RRC connection configuration message carries a specific cause value, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or a corporate network local network LIPA connection, or a traffic offload operation of the Internet service. Connection, or specific IP data offload connection failure indication, used to indicate the terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, or enterprise network local network LIPA connection, or Internet service diversion operation connection, or specific The IP data offload connection is invalid;

In the UTRAN system, the mobility management entity is a serving GPRS support node SGSN; the release process includes:

The SGSN sends a PDP context deletion request to the local gateway GPRS support node GGSN; the L-GGSN triggers the release of the bearer of the local IP connection primary connection, and returns a PDP context deletion response to the SGSN;

The SGSN sends a PDP context deactivation request to the terminal via the radio side network element, and carries a specific cause value in the PDP context deactivation request, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection. , or enterprise network local network LIPA connection, or Internet service shunt operation connection, or specific IP data offload connection failure indication, used to indicate terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, or enterprise network Local network LIPA connection, or offload operation connection of Internet service, or specific IP data offload connection failure;

It can be seen from the technical solution provided by the present invention that the wireless side network element/home base station gateway only needs LIPA to Internet capability, and/or LIPA to home based network capability, and/or wireless side network element to the mobility management entity. / appropriate local access gateway information accessible by the home base station gateway, The mobility management entity establishes a LIPA connection for the user according to the obtained capability information, and determines whether it is an Internet LIPA connection or a home network LIPA connection. Through the method of the invention, it is reasonable to select which type of LIPA connection is created for the user, and the security of the LIPA access of the non-CSG user is guaranteed.

Further, when the capability changes, the wireless side network element/home base station gateway reports the changed capability information to the mobility management entity, and the mobility management entity determines, according to the obtained changed capability information, whether the LIPA connection established by the user is established. It has expired, and the failed connection is released, and the user is notified of the specific cause value/indication for the user to handle (such as the user re-initiating the creation or non-processing of the LIPA connection). It is reasonable to choose which type of LIPA connection to keep for the user. DRAWINGS

Figure 1 is a schematic diagram of the composition of an existing EPS architecture;

2 is a schematic diagram of a data flow path of local IP access and traditional core network IP access in a mobile communication network architecture;

3 is a flowchart of a method for implementing local IP access control according to the present invention;

4 is a flow chart showing an embodiment of LIPA access control when a user connection is established in a mobile communication system according to the present invention;

5 is a flowchart of an embodiment of a capability change after access control in a mobile communication system according to the present invention; FIG. 6 is a flowchart of an embodiment of a LTE system in which a capability change causes a local IP connection bearer to be released;

7 is a flow chart of an embodiment of a UTRAN system in the UTRAN system in which a change in capability causes a local IP connection bearer to be released;

8 is a flowchart of an embodiment of LIPA access control when a user registers in a mobile communication system; FIG. 9a is a first schematic diagram of a component structure of a system for implementing local IP access control according to the present invention; FIG. 9b is a local IP access according to the present invention; A second schematic diagram of the composition of the controlled system. detailed description

In the present invention, the local IP access connection (LIPA connection) includes the Internet LIPA connection, the home network LIPA connection, the user local network LIPA connection, the enterprise network local network LIPA connection, the Internet service shunt operation connection, and the specific IP data offload connection.

FIG. 3 is a flowchart of a method for implementing local IP access control according to the present invention. As shown in FIG. 3, the following steps are included:

Step 300: The wireless side network element/home base station gateway reports the Internet local IP access function (LIPA to Internet) capability information set on the wireless side network element/home base station gateway to the mobility management entity, and/or the home network LIPA (LIPA) To the home based network, the capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway.

Among them, LIPA to Internet capabilities include Internet LIP Α connectivity, and / or Internet traffic offload capabilities, and / or specific IP data offload capabilities. The capabilities of LIPA to home based network include home network LIPA connectivity, and/or user local network LIP A connectivity, and/or corporate network local network LIPA connectivity.

Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, and/or Internet service offload capability information, and/or Or the specific IP data offload capability information is set in the radio side network element/home base station gateway according to the intention of the radio side network element/home base station gateway owner. The appropriate local access gateway information accessible by the wireless side network element/home base station gateway can be set in the wireless side network element/home base station gateway.

The capability of LIPA to Internet can be the capability of non-CSG user LIPA to Internet, the capability of CSG user LIPA to Internet, and the capability of wireless side network element/home base station gateway. The above three capability information can be arbitrarily combined. It is also possible to transmit only certain capability information; the capability of LIPA to home based network may be the capability of non-CSG user LIPA to home based network, or the capability of CSG user LIPA to home based network Force, or non-CSG user local network LIPA connection capability, or non-CSG user enterprise network local network LIPA connection capability, CSG user local network LIPA connection capability, or CSG user enterprise network local network LIPA connection capability, or wireless side network element / The ability of a home base station gateway. The above capability information can be arbitrarily combined. It is also possible to send only certain capability information.

Whether the CSG user and the non-CSG user can have the LIPA to Internet capability or the LIPA to home based network capability can be set by the wireless side network element/home base station gateway. Whether a CSG user can have LIPA to Internet capability or LIPA to home based network capability can also be achieved by signing up.

The wireless side network element may be a base station, a home base station, or a radio network controller (RNC). The mobility management entity may be an MME, a Mobile Switching Centre (MSC), a serving GPRS support node (SGSN, Serving). GPRS Support Node).

In this step, when the user initiates an attach request, a PDN connection establishment request, a service request, or a PDP context activation, the wireless side network element/home base station gateway carries the foregoing Internet LIPA connection capability information in the Sl/Iu initialization connection message, and/or Home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, and/or Internet traffic offload capability information, and/or specific IP data offload capability information, and / or the appropriate local access gateway information that the wireless side network element/home base station gateway can access, and reported to the mobility management entity. In particular, when the home base station gateway is not deployed or in the macro cell, the wireless side network element registers its capability to the mobility management entity.

When the capability information is reported, in addition to the capability information carrying the support, the capability information may be supported or not supported by the capability information.

Step 301: The mobility management entity determines, according to the obtained Internet LIPA capability information, and/or the home network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway. The user establishes a LIP A connection. The mobility management entity determines whether to establish an Internet for the user according to the received capability information.

LIPA connection or home network LIPA connection. For example, when the user needs to create an Internet LIPA connection, it is necessary to determine whether the LIPA to Internet capability of the wireless side network element/home base station gateway is supported. For non-CSG users, it is also necessary to determine whether the non-CSG user LIPA to Internet capability is supported; It is necessary to determine whether there is a suitable local access gateway according to the appropriate local access gateway information accessible by the wireless side network element/home base station gateway. Only when the above capabilities are supported, the mobility management entity can initiate the Internet LIPA for the user. The creation of a connection. For example, when a user needs to create a home network LIPA connection, it is necessary to determine whether the LIPA to home based network capability of the wireless side network element/home base station gateway is supported. For non-CSG users, it is also necessary to determine the non-CSG user LIPA to home based network. Whether the capability is supported; in addition, it is necessary to determine whether there is a suitable local access gateway according to the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, and only when the above capabilities are supported, the mobility management entity can Create a home network LIPA connection for the user.

In this embodiment, the process of creating an Internet LIPA connection and a home network LIPA connection is used as an example for process description, and other types of LIPA connection establishment are the same, and will not be described in detail.

It should be noted that the creation of the Internet LIPA connection or the creation of the home network LIPA connection may be initiated for the user, depending on the conditions set in the mobility management entity, which is merely illustrative and is not intended to limit the scope of the present invention. .

Through the method of the invention, it is reasonable to select which type of LIPA connection is created for the user, and the security of the LIPA access of the non-CSG user is guaranteed.

Further, when the Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, and/or Internet traffic offload capability The information, and/or the specific IP data offload capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, the method further includes: the wireless side network element/home Base station gateway through configuration update Request or register the request, and send the changed capability information to the mobility management entity. Further, when the Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, and/or Internet traffic offload capability The information, and/or the specific IP data offloading capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, when the change occurs, the mobility management entity determines that the user has been determined according to the foregoing capability information. Whether the established LIPA connection has expired and releases the failed connection. It is reasonable to choose which type of LIPA connection to keep for the user.

Corresponding to the method shown in Fig. 3, the present invention also provides a system for implementing local IP access control. FIG. 9 is a first schematic diagram of a component structure of a system for implementing local IP access control according to the present invention. As shown in FIG. 9a, a wireless side network element/home base station gateway, a mobility management entity, where

The wireless side network element/home base station gateway is configured to report the Internet local IP access function LIPA connection capability information, and/or the home network LIPA connection capability information, and/or the user local network LIPA connection capability information to the mobility management entity, and/or Or enterprise network local network LIPA connection capability information, and/or Internet service offload capability information, and/or specific IP data offload capability information, and/or a suitable local access gateway accessible by the wireless side network element/home base station gateway Information

a mobility management entity, configured to receive, according to received Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, And/or Internet service offload capability information, and/or specific IP data offload capability information, and/or appropriate local access gateway information accessible by the radio side network element/home base station gateway, to determine whether to establish a LIPA connection for the user.

When the Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, and/or Internet service offload capability information And/or specific IP data offload capability information, and/or suitable local access gateway information accessible by the radio side network element/home base station gateway, When the change occurs, the wireless side network element/home base station gateway is further configured to report the changed capability information to the mobility management entity;

The mobility management entity is further configured to send a specific cause value to the terminal, or send an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or an enterprise network local network LIPA connection failure indication, for indicating The terminal Internet LIPA connection or home network LIPA connection is disabled for the user to handle (such as the user re-initiating the creation of the LIPA connection or not creating the LIPA connection).

The mobility management entity is further configured to directly convert an Internet LIPA connection or a home network LIPA connection that cannot be created into a core network connection according to an operator policy or a local policy, and create a core network connection for the user.

The radio side network element is a base station, or a home base station, or an RNC; the mobility management entity is an MME, or an MSC, or an SGSN.

FIG. 9b is a second schematic diagram of a component structure of a system for implementing local IP access control according to the present invention. When a home base station gateway or a macro cell is not deployed, as shown in FIG. 9b, a wireless side network element, a mobility management entity, where ,

When the wireless side network element is registered, the information about the Internet local IP access function LIPA connection capability, and/or the home network LIPA connection capability information, and/or the user local network LIPA connection capability information, and/or the enterprise network local network LIPA connection capability information, and/or Internet traffic offload capability information, and/or specific IP data offload capability information, and/or appropriate local access gateway information accessible by the radio side network element/home base station gateway, reported to the mobile Sexual management entity;

a mobility management entity, configured to receive, according to received Internet LIPA connection capability information, and/or home network LIPA connection capability information, and/or user local network LIPA connection capability information, and/or enterprise network local network LIPA connection capability information, And/or Internet traffic distribution capability information, And/or specific IP data offload capability information, and/or appropriate local access gateway information accessible by the radio side network element/home base station gateway, to determine whether to establish a LIPA connection for the user.

The method of the present invention will be described in detail below with reference to the embodiments.

4 is a flowchart of an embodiment of LIPA access control when a user connection is established in a mobile communication system according to the present invention. As shown in FIG. 4, the method includes:

Step 400: The terminal needs to establish a radio resource control (RRC, Radio Resource Control) connection as a bearer of signaling messages or service data before performing communication.

Step 401: The terminal sends an initialization non-access stratum (NAS, Non-Access-Stratum) message to perform an attach operation.

The user's operation at this time can be an Attach Request and a PDN Connectivity Request. In the UTRAN system, the PDN connection establishment is implemented through the PDP context activation procedure. Therefore, in the UTRAN system, the operation initiated by the user at this time may also be a PDP context activation.

Step 402: The radio side network element sends an initial UE message to the mobility management entity, and forwards the NAS message/PDP context activation request to the mobility management entity.

In this step, if there is a home base station gateway, the wireless side network element first forwards the initial UE message to the home base station gateway, and then the home base station gateway sends the message to the mobility management entity.

In this step, the wireless side network element/home base station gateway will set the LIPA to Internet capability and/or LIPA to home based network capability on the wireless side network element/home base station gateway, and/or the wireless side network element/home base station gateway. Appropriate local access gateway information that can be accessed, carried in the initial

The UE message (i.e., the Sl/Iu message) is sent to the mobility management entity.

Among them, LIPA to Internet capabilities include Internet LIPA connectivity, Internet traffic offload capabilities, and specific IP data offload capabilities. The capability of LIPA to Internet can be the capability of non-CSG user LIPA to Internet, the capability of CSG user LIPA to Internet, and the capability of wireless side network element/home base station gateway. The above capability information can be combined arbitrarily, Can only send some kind of capability information;

The capabilities of LIPA to home based network include LIPA connectivity for home networks, LIPA connectivity for users' local networks, and LIPA connectivity for enterprise networks. The capability of LIPA to home based network may be the capability of non-CSG user LIPA to home based network, or the capability of CSG user LIPA to home based network, or the non-CSG user local network LIPA connection capability, or the non-CSG user enterprise network local network. The LIPA connection capability, the LIPA connection capability of the CSG user's local network, or the LIPA connection capability of the CSG user enterprise network local network, or the capability of the wireless side network element/home base station gateway. The above capability information can be combined in two. It is also possible to send only certain capability information.

In the LTE system, the mobility management entity is the MME; in the UMTS system, the mobility management entity is the SGSN.

Step 403: The mobility management entity may initiate authentication and security procedures to authenticate the user. This step belongs to the existing process and can be implemented by using existing methods, and will not be described here.

Step 404: The mobility management entity finds that a local IP connection needs to be established according to an access point name (APN, Access Point Name) or a local access identifier (the identifiers can be carried in the message in step 402). The mobility management entity determines which LIPA connection can be created for the user according to the capability information reported by the wireless side network element/home base station gateway in step 402.

When the user needs to create an Internet LIPA connection, it is necessary to determine whether the LIPA to Internet capability of the wireless side network element/home base station gateway is supported. If it is a non-CSG user, it is also necessary to determine whether the non-CSG user LIPA to Internet capability is supported; The appropriate local access gateway information that the side network element/home base station gateway can access determines whether there is a suitable local access gateway. Only when the above capabilities are supported, the mobility management entity can initiate the creation of the Internet LIPA connection for the user. When you need to create a home network LIPA connection, you need to determine whether the LIPA to home based network capability of the wireless side network element/home base station gateway is supported. If it is a non-CSG user, you also need to determine whether the non-CSG user LIPA to home based network capability is supported. In addition, it is also necessary to determine whether there is a suitable local access gateway according to the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, and the mobility management entity can only be the user when the above capabilities are supported. Initiate the creation of a home network LIPA connection.

In this embodiment, only the capability information reported in step 402 is the capability of the wireless side network element/home base station gateway and the capability of the non-CSG user, and the judgment behavior of the mobility management entity is described.

Step 405: According to the judgment result of step 404, if the mobility management entity decides that an Internet LIPA connection or a home network LIPA connection can be created for the user, the existing process of user access is continued. According to the process initiated by the user in step 401, the process that the user continues may be an attach process, a PDN connection establishment process, or a PDP context activation process.

Step 406 to step 407: According to the judgment result of step 404, if the mobility management entity decides that the Internet LIPA connection or the home network LIPA connection cannot be created for the user, the NAS reject message is sent, and the access is rejected. At the same time, in the reject message, a specific cause value can be carried in order to indicate that the user cannot establish an Internet LIPA connection or a home network LIPA connection. According to the process initiated by the user in step 401, the process that the user rejects at this time may be an attach process, a PDN connection establishment process, or a PDP context activation process.

In this step, the denial message may not be sent according to the operator policy or the local policy, and the mobility management entity directly converts the Internet LIPA connection/home network LIPA connection that cannot be created into the core network connection. The mobility management entity leverages existing processes to create core network connections for users.

5 is a flowchart of an embodiment of access control after capability change in a mobile communication system according to the present invention. As shown in FIG. 5, when the LIPA to Internet capability is set on the wireless side network element/home base station gateway, and/or LIPA to The home based network capability, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, includes the following steps:

Step 500: The wireless side network element sends the changed capability information to the mobility management entity of the core network. In the LTE system, the radio side network element will change the LIPA to Internet capability and/or LIPA to home based network capability, and/or the appropriate local access gateway information accessible by the radio side network element/home base station gateway, It is carried in the configuration update request message and sent to the mobility management entity. If there is a home base station gateway, the wireless side network element first sends a configuration update message to the home base station gateway, and then the home base station gateway forwards the information to the mobility management entity.

In the UTRAN system, the wireless side network element will change the LIPA to Internet capability, and/or the LIPA to home based network capability, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway. It is carried in the registration request message, sent to the home base station gateway, and then forwarded to the mobility management entity by the home base station gateway.

The mobility management entity is ΜΜΕ in the LTE system, and the mobility management entity is the SGSN in the UTRAN system.

Step 501: The mobility management entity responds to the wireless side network element, and configures an update response in the LTE system, and registers a response message in the UTRAN system.

Step 502: The mobility management entity checks if the user has a LIPA connection. If yes, according to the changed capability reported by the wireless side network element/home base station gateway in step 500, it is determined whether the LIPA connection of the user is invalid.

When the user has an Internet LIPA connection, it is necessary to determine whether the LIPA to Internet capability of the wireless side network element/home base station gateway is supported. If it is a non-CSG user, it is also necessary to determine whether the non-CSG user LIPA to Internet capability is supported, only when the above capabilities are supported. The mobility management entity can determine that the user's Internet LIPA connection is valid. If the user has a home network LIPA connection, you need to determine whether the LIPA to home based network capability of the wireless network element/home base station gateway is supported. If it is a non-CSG user, you need to determine whether the non-CSG user LIPA to home based network capability is supported. When the above capabilities are supported, the mobility management entity can determine that the user's home network LIPA connection is valid. If the information of the appropriate local access gateway accessible by the wireless side network element/home base station gateway changes, the LIPA connection existing by the user is caused. If the local access gateway used changes, it is determined that the LIPA connection is invalid.

In this embodiment, only the capability information reported in step 500 is the capability of the wireless side network element/home base station gateway and the capability of the non-CSG user as an example.

Step 503: According to the determination of the mobility management entity in step 502, if the LIPA connection existing by the user continues to be valid, no operation is performed and the process ends. If the user's existing LIPA connection fails, the mobility management entity releases the failed LIPA connection. The specific release process is described in detail below with respect to Figures 6 and 7.

In this embodiment, the capability change information of the radio side network element/home base station gateway that triggers the mobility management entity to release the LIPA connection is reported by the radio side network element/home base station gateway to the mobility management entity by using a configuration update request or a registration request. However, the information may also be obtained by the mobility management entity by other means. At this time, the mobility management entity determines whether the LIPA connection is invalid and the processing after the failure remains unchanged, that is, the manner in which the mobility management entity acquires the information. Does not affect the mobility management entity to determine whether the LIPA connection is invalid, and the processing after the failure.

In this embodiment, the condition for triggering the mobility management entity to determine whether the LIPA connection is invalid is the capability change of the wireless side network element/home base station gateway. In addition, for the LIPA connection, the geographical coverage of the local access gateway is limited. Considering the route optimization, the terminal mobility may cause the local access gateway to change. At this time, the mobility management entity also considers that the user has established the LIPA connection. Failure, and processing of the failed connection, such as release, in accordance with the description of this embodiment.

In this embodiment, the mobility management entity is an MME in the LTE system, and an SGSN in the UTRAN system.

FIG. 6 is a flowchart of an embodiment of a LTE system in which a capability change causes a local IP connection bearer to be released. In this embodiment, an L-SGW is located in a radio side network element/home base station gateway as an example, and the mobility management entity is used. For the MME, as shown in Figure 6, the following steps are included:

Step 600: When the user has attached to the network and has a local IP connection, as described in FIG. 5, the MME determines the mutual user according to the changed capability reported by the wireless side network element/home base station gateway. The networked LIPA connection/home network LIPA connection fails, and the MME releases the failed LIPA connection. Step 601: The MME sends a session deletion request message to the L-SGW.

Step 602: Receive a message sent by the MME, and the L-SGW sends a session deletion request message to the L-PGW.

Step 603: After receiving the session deletion request message, the L-PGW triggers the release of the bearer of the local IP connection. The L-PGW sends a session deletion response message to the L-SGW.

Step 604: The L-SGW forwards the session deletion response message to the MME.

Step 605: The MME initiates a bearer deactivation request to the radio side network element. The bearer deactivation request message carries a specific cause value, or an Internet LIPA connection or a home network LIPA connection or a user local network LIPA connection or a corporate network local network LIPA connection or an Internet service diversion operation connection or a specific IP data offload connection failure indication , the shunt operation connection or the specific IP data offload connection for indicating the terminal Internet LIPA connection or the home network LIPA connection or the user local network LIPA connection or the enterprise network local network LIPA connection or the Internet service is invalid, that is, used to indicate the terminal LIPA connection reactivation Or the specific cause/indication of the connection failure.

Step 606: The radio side network element performs an RRC connection configuration process, and sends an RRC connection configuration message to the terminal, where the RRC connection configuration message carries a specific cause value, or an Internet LIPA connection or a home network LIPA connection or a user local network LIPA connection or Enterprise network local network LIPA connection, or Internet service shunt operation connection, or specific IP data offload connection failure indication, used to indicate terminal Internet LIPA connection or home network LIPA connection or user local network LIPA connection or enterprise network local network LIPA connection or The offloading operation connection or the specific IP data offload connection of the Internet service is invalid, that is, a specific reason/indication for indicating that the terminal LIPA connection is reactivated or the connection is invalid.

The above specific cause value or failure indication may be a reactivation cause value/indication, or may be a specific cause/indication of connection failure, such as capability change, relocation, and the like.

Step 607: The terminal returns an RRC connection configuration complete message to the radio side network element. Terminal reception After the specific cause value or the LIPA connection failure indication in the RRC connection configuration message, the LIPA connection re-establishment process may be initiated or may not be processed.

Step 608: The radio side network element sends a bearer deactivation response message to the MME.

In this embodiment, the MME determines, according to the changed capability of the wireless side network element/home base station gateway, the user's Internet LIPA connection/home network LIPA connection failure as an example, and describes the processing of the MME releasing the invalid LIPA connection. However, the modification of the wireless side network element/home base station gateway capability information determines whether the LIPA connection fails and the processing after the failure remains unchanged, that is, the manner in which the mobility management entity acquires the wireless side network element/home base station gateway capability change information does not affect. The mobility management entity determines whether the LIPA connection is invalid and the post-failure processing.

In this embodiment, the condition for triggering the mobility management entity to determine whether the LIPA connection is invalid is the capability change of the wireless side network element/home base station gateway. In addition, for the LIAP connection, the geographical coverage of the local access gateway is limited. Considering the route optimization, the terminal mobility may cause the local access gateway to change. At this time, the mobility management entity also considers that the user has established the LIPA connection. Failure, and processing of the failed connection, such as release, in accordance with the description of this embodiment.

In this embodiment, the local access gateway is an L-PGW and an L-SGW, and the L-SGW is set in the radio side network element/home base station gateway.

The process of releasing the LIPA connection in the absence of the L-SGW is similar to the process shown in Figure 6. The MME needs to directly interact with the L-PGW. The L-SGW does not participate in the process. . The process of releasing the LIPA connection when the L-SGW is located in the core network is the same as that shown in Figure 6. However, the MME needs to perform message interaction with the L-SGW located in the core network, and details are not described herein.

FIG. 7 is a flowchart of an embodiment of a UTRAN system in which a capability change causes a local IP connection bearer to be released. As shown in FIG. 7, the method includes:

Step 700: When the user has attached to the network and has a local IP connection, as shown in FIG. 5 The SGSN determines the user's Internet LIPA connection/home network LIPA connection/user local network LIPA connection/enterprise network local network LIPA connection/network service shunt operation connection/specific according to the changed capability reported by the radio side network element/home base station gateway. The IP data offload connection fails, and the SGSN initiates the release of the failed LIPA connection.

Step 701: The SGSN sends a PDP context delete request to the L-GGSN.

Step 702: The L-GGSN receives the message sent by the SGSN, and triggers the release of the bearer of the primary IP connection primary connection. The L-GGSN responds to the SGSN with a PDP Context Delete Response.

Step 703: The SGSN sends a PDP context deactivation request to the terminal via the radio side network element, where the PDP context deactivation request carries a specific cause value, or an Internet LIPA connection or a home network LIPA connection or a user local network LIPA connection or a corporate network local. A network LIPA connection or a traffic offload connection for the Internet service or a specific IP data offload connection failure indication for indicating a terminal Internet LIPA connection or a home network LIPA connection or a user local network LIPA connection or a corporate network local network LIPA connection or an offload operation of the Internet service The connection or specific IP data offload connection is invalid, that is, the specific cause/indication for indicating the terminal LIPA connection reactivation or connection failure.

Step 704: The terminal returns a PDP context deactivation accept message to the SGSN via the radio side network element. After receiving the specific cause value or the LIPA connection failure indication in the PDP context deactivation message, the terminal may initiate the LIPA connection re-establishment process, or may not process.

Step 705: Perform a radio access bearer release procedure.

In this embodiment, the SGSN determines, according to the changed capability of the wireless side network element/home base station gateway, the user's Internet LIPA connection/home network LIPA connection failure as an example, and describes the processing of the SGSN releasing the failed LIPA connection. However, the wireless side network element/home base station gateway capability information is determined to determine whether the LIPA connection is invalid and the processing after the failure remains unchanged, that is, the mobility management entity The manner of obtaining the wireless side network element/home base station gateway capability change information does not affect whether the mobility management entity determines whether the LIPA connection is invalid or not, and the processing after the failure.

When the home base station gateway is not deployed or in the case of a macro station, its capability is reported to the mobility management entity when the radio side network element registers, and the mobility management entity retains its capabilities. In this way, when the user creates a connection, it is no longer necessary to carry the capability to the mobility management entity as shown in FIG. 4, and the mobility management entity can use the capability information saved during registration to determine. 8 is a flow chart of an embodiment of LIPA access control when a user registers in a mobile communication system. As shown in FIG. 8, the method includes the following steps:

Step 800: The radio side network element sends an S1 interface setup request message to the mobility management entity to request to establish an S1 connection. The wireless side network element carries the set LIPA to Internet capability information, and/or LIPA to home based network capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway. The S1 interface setup request message is sent to the mobility management entity.

Among them, LIPA to Internet capabilities include Internet LIPA connectivity, Internet traffic offload capabilities, and specific IP data offload capabilities. The capability of LIPA to Internet can be the capability of non-CSG users LIPA to Internet, the ability of CSG users LIPA to Internet, and the capability of wireless side network element/home base station gateway. The above three kinds of capability information may be arbitrarily combined, or only some capability information may be transmitted.

The capabilities of LIPA to home based network include LIPA connection capability for home network, LIPA connection capability for user local network, and LIPA connection capability for enterprise network local network. LIPA to home The ability of the based network can be the capability of the non-CSG user LIPA to the home based network, or the capability of the CSG user LIPA to home based network, or the non-CSG user local network LIPA connection capability, or the non-CSG user enterprise network local network LIPA connection capability. The CSG user local network LIPA connection capability, or the CSG user enterprise network local network LIPA connection capability, and may also be the capability of the wireless side network element/home base station gateway. The above three capability information can be arbitrarily combined. It is also possible to send only certain capability information.

In the LTE system, the mobility management entity is the MME.

Step 801: The mobility management entity sends a response message to the radio side network element to the S1 interface. Step 802: The mobility management entity saves the LIPA to Internet capability information and/or LIPA to home based network capability information obtained by the copper through step 800.

In this way, when the UE initiates the connection establishment process, the mobility management entity determines which LIPA connection can be created for the user according to the capability of the wireless side network element saved in step 802.

If you need to create an Internet LIPA connection, you need to determine whether the LIPA to Internet capability of the wireless network element is supported. If the non-CSG user needs to determine whether the non-CSG user LIPA to Internet capability is supported, you need to use the wireless side network element/ The appropriate local access gateway information accessible by the home base station gateway determines whether there is a suitable local access gateway. Only when the above capabilities are supported, the mobility management entity can initiate the creation of an Internet LIPA connection for the user. If you need to create a home network LIPA connection, you need to determine whether the LIPA to home based network capability of the wireless network element/home base station gateway is supported. If it is a non-CSG user, you need to determine whether the non-CSG user LIPA to home based network capability is supported. In addition, it is also required to determine whether there is a suitable local access gateway according to the appropriate local access gateway information accessible by the wireless side network element/home base station gateway, and the mobility management entity can initiate the user for the user only when the above capabilities are supported. Creation of a network LIPA connection.

In this embodiment, only the capability information reported in step 800 is the capability of the wireless side network element/home base station gateway and the capability of the non-CSG user as an example. Other ability combination The formula is similar to this and will not be described in detail.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A method for implementing local IP access control, the method comprising: a wireless side network element/home base station gateway, reporting an Internet local IP access function LIPA capability information to a mobility management entity, and/or a home network LIPA Capability information, and/or appropriate local access gateway information accessible by the wireless side network element/home base station gateway;

2. The method of claim 1, wherein the Internet LIPA capability information, and/or home network LIPA capability information, and/or the wireless side network element/home base station gateway are accessible When the local access gateway information changes, the method further includes:

3. The method according to claim 2, wherein the method further comprises: the mobility management entity sending a specific cause value to the terminal, or sending an Internet LIPA connection, or a home network LIPA connection, or a user local network The LIPA connection, or the enterprise network local network LIPA connection, or the offload operation connection of the Internet service, or the specific IP data offload connection failure indication, is used to indicate that the terminal LIPA connection is invalid.

The method according to claim 1, wherein the mobility management entity directly converts the LIPA connection that cannot be created into a core network connection according to an operator policy or a local policy, and creates a core network connection for the user. .

The method according to claim 2, wherein the method for reporting the changed capability information to the mobility management entity is: the wireless side network element/home base station gateway configuring the update request or the registration request, The changed capability information is reported to the mobility management entity.

The method according to claim 2, wherein, in the LTE system, the mobility management entity is a mobility management unit MME, and the mobility management entity releases the invalid LIPA connection, including:

The method according to claim 6, wherein when there is a local serving gateway L-SGW, the information interaction between the mobility management entity and the L-PGW is forwarded by the L-SGW.

The method according to claim 7, wherein the L-SGW is set in the radio side network element/home base station gateway; or the L-SGW is located in a core network.

The method according to claim 2, wherein in the UTRAN system, the mobility management entity is a serving GPRS support node SGSN, and the mobility management entity releases the expired LIPA connection, including:

The method according to claim 1 or 2, wherein the reporting method comprises:

11. A method according to claim 1 or 2, characterized in that

The Internet LIPA capabilities include Internet LIPA connectivity, and/or Internet traffic offload capabilities, and/or specific IP data offload capabilities; The Internet LIPA connection capability information is a capability of a non-closed CSG user Internet LIPA connection, or a capability of a CSG user Internet LIPA connection, or a capability of a wireless side network element/home base station gateway, or any combination of the capability information;

The home network LIPA connection capability information is a capability of a non-CSG user home network LIPA connection, or a CSG user home network LIPA connection capability, or a non-CSG user local network LIPA connection capability, or a non-CSG user enterprise network local network LIPA connection capability. , CSG user local network LIPA connection capability, or non-CSG user enterprise network local network LIPA connection capability, or wireless side network element / home base station gateway capability, or any combination of the capability information.

The method according to claim 1 or 2, wherein the radio side network element is a base station, or a home base station, or a radio network controller RNC;

13. A method for implementing local IP access control, characterized in that, when a home base station gateway is not deployed or in a macrocell, the method comprises:

14. The method according to claim 13, wherein the Internet LIPA capability information, and/or home network LIPA capability information, and/or a suitable local connection accessible by the wireless side network element/home base station gateway The inbound gateway information is carried in the S1 interface setup request message.

15. The method according to claim 13, wherein when the Internet LIPA capability information, and/or home network LIPA capability information, and/or the wireless side network element/home base station gateway is accessible, suitable local When the access gateway information changes, the method further includes:

16. A method according to any one of claims 13 to 15, characterized in that

A system for implementing local IP access control, comprising: a wireless side network element/home base station gateway, a mobility management entity, wherein

Mobility management entity, based on received Internet LIPA capability information, and/or home Whether to establish a LIPA connection for the user is determined by the network LIPA capability information, and/or the appropriate local access gateway information accessible by the wireless side network element/home base station gateway.

18. The system according to claim 17, wherein: the Internet LIPA capability information, and/or home network LIPA capability information, and/or a suitable local access accessible by the wireless side network element/home base station gateway When the access gateway information changes,

The wireless side network element/home base station gateway is further configured to report the changed capability information to the mobility management entity;

The system according to claim 18, wherein the mobility management entity is further configured to send a specific cause value to the terminal, or send an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA. Connection, or enterprise network local network LIPA connection, or offload operation connection of Internet service, or specific IP data offload connection failure indication, used to indicate that the terminal LIPA connection is invalid.

The system according to claim 17, wherein the mobility management entity is further configured to directly convert the LIPA connection that cannot be created into a core network connection according to an operator policy or a local policy, and create the same for the user. Core network connection.

The system according to claim 17, wherein the wireless side network element is a base station, or a home base station, or a radio network controller RNC;

The system according to any one of claims 17 to 21, wherein the Internet LIPA capability comprises an Internet LIPA connection capability, and/or an Internet service offload capability, and/or a specific IP data offload capability;

The home network LIPA connection capability includes a home network LIPA connection capability, and/or a user Local network LIPA connectivity, and/or corporate network local network LIPA connectivity.

A system for implementing local IP access control, characterized in that, when a home base station gateway is not deployed or in a macro cell, a wireless side network element, a mobility management entity,

24. The system of claim 23, wherein the Internet LIPA capabilities include Internet LIPA connectivity, and/or Internet traffic offload capabilities, and/or specific IP data offload capabilities;

25 . A notification method for implementing local IP access control, wherein when the mobility management entity determines that the local gateway relocation or the Internet local IP access function LIPA capability information changes, or the home network LIPA capability information changes, Or when the information of the appropriate local access gateway accessible by the wireless side network element/home base station gateway is changed, and the LIPA connection is released,

The mobility management entity sends a specific cause value to the terminal in the release process; or, sends an Internet LIPA connection, or a home network LIPA connection, or a user local network LIPA connection, or a corporate network local network LIPA connection, or a traffic offload of the Internet service Operational connection, or specific IP data offload connection failure indication, respectively, corresponding to indicating terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, or enterprise network local network LIPA connection, or Internet service Shunt operation connection, or specific IP data offload The specific cause/indication of the reactivation of the connection or the failure of the connection.

26. The method of claim 25, wherein

The specific cause/indication of the connection failure includes one or more of the following reasons/indications: capability change, relocation.

The method according to claim 25, wherein, in the LTE system, the mobility management entity is a mobility management unit MME, and the release process includes:

The radio side network element performs an RRC connection configuration process, and sends an RRC connection configuration message to the terminal, where the RRC connection configuration message carries a specific cause value, or carries an Internet LIPA connection, or a home network LIPA connection, or a user local Network LIPA connection, or enterprise network local network LIPA connection, or Internet service traffic distribution connection, or specific IP data offload connection failure indication, used to indicate terminal Internet LIPA connection, or home network LIPA connection, or user local network LIPA connection, Or the enterprise network local network LIPA connection, or the offload operation connection of the Internet service, or the specific IP data offload connection is invalid; The terminal returns an RRC connection configuration complete message to the radio side network element, and the radio side network element sends a bearer deactivation response message to the mobility management entity.

The method according to claim 25, wherein in the UTRAN system, the mobility management entity is a serving GPRS support node SGSN; the release procedure comprises: sending, by the SGSN, a local gateway GPRS support node GGSN PDP context delete request; L-GGSN triggers the release of the bearer of the local IP connection primary connection, and returns a PDP context delete response to the SGSN;