WO2013004121A1

WO2013004121A1 - Method and device for processing local gateway information

Info

Publication number: WO2013004121A1
Application number: PCT/CN2012/076802
Authority: WO
Inventors: 雷小燕; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-07-06
Filing date: 2012-06-12
Publication date: 2013-01-10
Also published as: CN102868997A; CN102868997B

Abstract

Disclosed in the present invention are a method and device for processing local gateway information, and the method comprises: network side sends a inquiring request to local network inquiring system; network side receives the returned response message from the local network inquiring system, wherein, the response message carries information of one or multiple local gateway. The invention solves the problem produced by how the network side gets local gateway information when remote access local network connection and remote access that don't be disclosed by the prior art, and then the normal use of the remote access to local network function can be ensured.

Description

The present invention relates to the field of communications, and in particular to a local gateway information processing method and apparatus. 1 is a schematic structural diagram of an Evolved Packet System (EPS) according to the prior art. As shown in FIG. 1, the entire EPS is divided into two parts: a radio access network and a core network. In the core network, a Home Subscriber Server (HSS), a mobility management unit (for example, a Mobility Management Entity (MME), a Serving GPRS Support Node (Serving GPRS Support Node) SGSN), Policy and Charging Rule Function (PCRF), Serving Gateway (S-GW), Packet Data Gateway (PDN Gateway, P-GW for short), and packet data network (Packet Data Network, abbreviated as PDN.) The following describes the network element in Figure 1. The home subscriber server is located in the home network that the user subscribes to, and is used to permanently store user subscription data. The mobile management unit is used to store the current network. User subscription data, and is responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging management functions, and bearer management. Service GPRS support node , is the Global System for Mobile Communications (G) SM), Enhanced Data Rate for GSM Evolution (EDGE), GSM EDGE Radio Access Network (GERAN), and Universal Mobile Telecommunications System (UMTS) ), the UMTS Terrestrial Radio Access Network (UTRAN), the service support point for users accessing the core network, which is similar in function to the mobility management unit, and is responsible for user location update, paging management, and bearer management. The service gateway is the gateway of the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function; The service gateway is also responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDRs of the terminal using the wireless network, and transmits the CDRs to the charging gateway. The packet data gateway is a gateway of the evolved system and the external packet data network of the system, and is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering, and And policy control, etc. The packet data network is the operator's IP service network, and the packet data network provides IP services to users through the operator's core network. The policy charging rule function entity is a server in the evolution system responsible for providing charging control, online credit control, threshold control, and quality of service (QoS) policy rules. The radio access network is composed of an evolved base station (Evolved NodeB, eB for short) and a 3G radio network controller (Radio Network Controllor, RNC for short). It is mainly responsible for receiving and receiving wireless signals, and is connected through the air interface and the terminal. Radio resources, resource scheduling, and access control for the air interface. The service GPRS support node is an upgraded SGSN, which can support the S4 interface with the service gateway, and communicates with the mobility management unit by using GPRS Tunneling Protocol version 2 (GTPv2). For the SGSN supporting the 3G core network, the packet switching (PS) domain network architecture is different from that of Figure 1. In this case, the SGSN and the MME are connected by Gn interface, and the interworking uses the GPRS tunneling protocol version 1 (GPRS Tunneling). Protocol version 1, referred to as GTPvl); The SGSN cannot be connected to the serving gateway. It needs to connect to the Gateway GPRS Support Node (GGSN) through the Gn interface to directly access the packet data network. A Home NodeB (HNB for short) or an evolved Home eNodeB (He B for short) is a small, low-power base station that is deployed as a dedicated resource for some users in a home, group, company, or The use of private places such as schools is mainly used to provide users with higher service rates and lower the cost of using high-rate services, while at the same time making up for the shortage of existing distributed cellular wireless communication systems. 2a to 2c are schematic diagrams of accessing a core network by a radio side network element according to the prior art. As shown in Figure 2a, the home base station can be directly connected to the core network. As shown in FIG. 2b and FIG. 2c, the home base station can also access the core network through the logical network element of the home base station gateway. The main function of the home base station gateway is to verify the security of the home base station, handle the registration of the home base station, perform operation and maintenance management on the home base station, configure and control the home base station according to the operator's requirements, and exchange data of the core network and the home base station. As shown in FIG. 2a, 2b, and 2c, in order to implement local access functions (including Local IP Access (LIPA) or Selective IP Traffic Offload (SIPTO)), the terminal pair A local gateway (Local Gateway, LGW for short) is added to other IP devices in the home network, IP devices in the enterprise network, or local access to the Internet. The addition of a local access gateway provides local access technology With the strong support of the technology, the local gateway can be set up with the wireless side network element or in the vicinity of the wireless side network element (ie, external), or can be set up with the home base station gateway or near the home base station gateway (ie, external); Local gateway includes local

The S-GW (Local SGW, abbreviated as L-SGW), the local PGW (Local PGW, abbreviated as L-PGW), the local GGSN (Local GGSN, abbreviated as L-GGSN), and the external local GW. In the mobile communication network architecture, for users who support local access, the data path of the local access and the data path accessed by the traditional core network can be established at the same time. 3 is a schematic diagram of a data path according to local access and traditional core network access in the prior art. As shown in FIG. 3, for a locally accessed connection (also referred to as a local connection), the local access data path is from the terminal to the wireless side. The network element to the local access gateway (for example, L-SGW, L-PGW, L-GGSN), the data transmission does not go through the core network. In order to achieve local access of the terminal to other IP devices or the Internet of the home network, two connections can be established. The first local access data path is used for direct access to the Internet (Internet IP connection, ie SIPTO connection), and the second local access The data path is used to directly access other IP devices on the home network (home network IP connection, ie LIPA connection). In the mobile communication network architecture, the network not only provides local access but also provides remote access to home based network (MRA). Remote access The local network function means that the terminal accesses from the wireless side network element outside the local network, and accesses the IP equipment in the home network and the IP equipment in the enterprise network. For users who support remote access to the local network, the data path of traditional core network access and the data path of remote access to the local network can be established at the same time. In order to achieve remote access to the local network function, that is, the terminal accesses from the wireless side network element outside the local network, and wants to access the IP device in the local network or the IP device in the enterprise network, a local access gateway is added (or called Local gateways), the addition of local access gateways provides strong support for remote access to local network technologies. The local gateway can be set up with the local wireless side network element or near the local wireless side network element (ie, externally), or can be set up with the local home base station gateway or near the local home base station gateway (ie, external); The gateway may include a local S-GW (L-SGW), a local PGW (L-PGW), a local GGSN (Local GGSN), an external local GW (L-GW), and the like. The local gateway function added for remote access to local network functions is similar to the local gateway function in local access. In order to support remote access to local network functions, the local network owner is required to support remote access, and the remote access to the local network function is enabled, that is, the local network has MRA capability and the MRA function is enabled. When the terminal accesses the local network service from the wireless side network element outside the local network, the network side needs to select a local gateway for the connection established by the terminal to remotely access the local network. The local gateway terminal can access IP devices in the local network. If the network side cannot select a suitable local gateway, the terminal cannot implement the remote access service, which may cause the user to complain to the operator due to the inability to use the service, thereby causing the loss of the customer. In the prior art, it is only proposed to select a local gateway when accessing the connection locally, but for remote access to the local network. The information on how the network side obtains the set local gateway when connecting and remote access is not disclosed, which makes it impossible to select a suitable local gateway. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a local gateway information processing method and apparatus to solve at least the above problems. According to an aspect of the present invention, a local gateway information processing method is provided, including the following steps: the network side sends a query request to a local network query system; the network side receives a response message returned by the local network query system, where The response message carries information of one or more local gateways. Preferably, the query request carries at least one of the following: an access point name, a local network identifier where the wireless side network element is located, and a base station identifier of the wireless side network element. Preferably, the information of the local gateway includes at least one of: address information of the local gateway, a remote access local network function MRA capability of the local gateway, a local network identifier where the local gateway is located, the local The base station ID supported by the gateway. Preferably, the network side sends a query request to the local network query system, where the query message carries the MRA capability, and the network side receives the response message returned by the local network query system, where the response message carries the support message. Information about one or more local gateways of the MRA capability. Preferably, the network side comprises a mobility management unit. Preferably, the sending, by the mobility management unit, the query request to the local network query system comprises: the mobile management unit querying the local network after receiving a packet data network PDN connection setup request message or an attach request message The system sends the query request. Preferably, after the mobile management unit receives the response message returned by the local network query system, the method further includes: the PDN connection setup request message or the attach request message requesting to establish an MRA connection, The mobility management unit selects a local gateway supporting the MRA capability to establish a connection; and/or, the PDN connection setup request message or the attach request message requests to establish a local IP access connection, and the subscription of the user equipment or the mobility management The unit configuration allows the user equipment to remotely access the local network, and the mobility management unit selects the local gateway supporting the MRA capability to establish a local IP access connection. Preferably, in a case that the mobility management unit receives the attach request message, the method further includes: the mobility management unit sending at least one of the following to the authentication authorization server at the end of the attaching process: the access point Name, address information of the local gateway, MRA capability; the authentication authority server saves information received from the mobility management unit. Preferably, the sending, by the mobility management unit, the query request to the local network query system comprises: the source mobility management unit receiving the handover request message; the source mobility management unit sending the query request to the local network query system The query request carries at least one of the following: an access point name, a local network identifier where the target radio side network element is located, and a base station identifier of the target radio side network element. Preferably, after the source mobility management unit receives the response message that carries the address information of the local gateway returned by the local network query system, the method further includes: the source mobility management unit comparing the received local gateway The address information and the address information of the local gateway of the locally stored source radio side network element are determined to be consistent with each other. If the information is inconsistent, the local connection is deactivated. Preferably, the method further includes: if the local network identifier where the target radio side network element is located is inconsistent with the established local connection local network identifier, the source mobility management unit is configured from the local network according to establishing a local connection The MRA capability of the query in the query system determines whether the continuity of the local connection is maintained. If the local gateway supports the MRA capability, it is determined that the continuity of the local connection can be maintained, and the local connection is converted into an MRA connection. Otherwise, the local device is deactivated. connection. Preferably, the sending, by the mobility management unit, the query request to the local network query system comprises: the target mobility management unit receiving the tracking area update request message; the target mobility management unit sending the to the local network query system Query request, where the query request carries at least one of the following: an access point name, a local network identifier where the target radio side network element is located, and a base station identifier of the target radio side network element. Preferably, after the target mobility management unit receives the response message that carries the address information of the local gateway returned by the local network query system, the method further includes: the target mobility management unit comparing the location carried in the response message If the address information of the local gateway and the address information of the local gateway obtained from the source mobility management unit are consistent, it is determined that the continuity of the local connection can be maintained, otherwise it is determined that the continuity of the local connection cannot be supported. Preferably, the method further includes: the target mobility management unit acquires an MRA capability and a local network identifier of the source radio side network element from the source mobility management unit; the target mobility management unit compares the local network of the target radio side network element Determining, and in the case of inconsistency, the target mobility management unit determines whether to maintain the continuity of the local connection according to the MRA capability, where the local network identifier of the source radio side network element obtained from the source mobility management unit is inconsistent, Wherein, if the local gateway supports the MRA capability, it is determined that the continuity of the local connection can be maintained, and the local connection is converted into an MRA connection, otherwise the local mobility management unit deactivates the local connection. Preferably, before the network side sends the query request to the local network query system, the method further includes: the local network query system receiving a registration request message from the local gateway carrying information of the local gateway And/or update request message. Preferably, the information of the local gateway that is carried includes at least one of the following: an IP address of the local gateway, an access point name supported by the local gateway, a local network identifier where the local gateway is located, and a base station identifier supported by the local gateway. , the MRA capability of the local gateway. Preferably, the local network query system is: a domain name system, a wireless side network element management system, or a new logical entity preset. According to another aspect of the present invention, a local gateway information processing apparatus is provided, including: a sending module, configured to send a query request to a local network query system; and a receiving module configured to receive a response returned by the local network query system The message, wherein the response message carries information of one or more local gateways. Preferably, the query request carries at least one of the following: an access point name, a local network identifier where the wireless side network element is located, and a base station identifier of the wireless side network element. Preferably, the information of the local gateway includes at least one of: address information of the local gateway, a remote access local network function MRA capability of the local gateway, a local network identifier where the local gateway is located, the local The base station ID supported by the gateway. Preferably, the sending module is configured to send a query request to the local network query system, where the query message carries an MRA capability, and the receiving module is configured to receive a response message returned by the local network query system, where The response message carries information of one or more local gateways that support MRA capabilities. The invention solves the problems caused by the prior art that the remote network access is not disclosed and the network side obtains the information of the local gateway when the remote access is obtained, thereby ensuring the normal use of the remote access local network function. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic structural diagram of an evolved packet system according to prior art; 2a is a schematic diagram 1 of a wireless side network element accessing a core network according to the prior art; FIG. 2b is a schematic diagram 2 of a wireless side network element accessing a core network according to the prior art; FIG. 2c is a schematic diagram according to the prior art; FIG. 3 is a schematic diagram of a data path of a local access and a traditional core network access according to the prior art; FIG. 4 is a schematic diagram of a local gateway information processing method according to an embodiment of the present invention; FIG. 5 is a structural block diagram of a local gateway information processing apparatus according to an embodiment of the present invention; FIG. 6 is a flowchart of dynamic registration and update of a local gateway according to an embodiment of the present invention; FIG. 7 is a PDN according to an embodiment of the present invention. FIG. 8 is a flowchart of selecting a local gateway in a handover procedure according to an embodiment of the present invention; FIG. 9 is a flowchart of selecting a local gateway in a tracking area update process according to an embodiment of the present invention; And, FIG. 10 is a flowchart of selecting a local gateway and saving a local gateway when a user initially attaches according to an embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. In this embodiment, a local gateway information processing method is provided. FIG. 4 is a flowchart of a local gateway information processing method according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps: Step S402: Network The local local network query system sends a query request. Step S404: The network side receives the response message returned by the local network query system, where the response message carries information of one or more local gateways. Through the above steps, a local network query system is set in the network, and the network side that needs the local gateway information can query the system through the query system, thereby obtaining the information of the local gateway, and providing a suitable local gateway. basis. Preferably, the network side can select the information carried in the query request according to the actual situation. For example, the query request can carry at least one of the following: an access point name, a wireless side network element (for example, a base station, a home Base station) The local network identifier where the base station is located and the base station identifier of the wireless side network element. Similarly, for the local network query system, the information of the local gateway provided by the local network query system may also be various. For example, the information of the local gateway may include at least one of the following: address information of the local gateway, and remote access of the local gateway. Local network function MRA capability, local network identifier where the local gateway is located, base station identifier supported by the local gateway. For the local network query system, there are many ways to obtain the information of the local gateway, and a most straightforward way is obtained in this embodiment. That is, the local network query system receives a registration request message and/or an update request message from the local gateway carrying the information of the local gateway. Preferably, the information of the carried local gateway includes at least one of the following: an IP address of the local gateway, a supported access point name, a local network identifier where the local gateway is located, a base station identifier supported by the local gateway, and an MRA of the local gateway. ability. In a preferred implementation, if the MRA capability is to be queried, the MRA capability can be carried in the query request. In this case, the local network query system can only carry the MRA-capable local gateway information in the response message returned by the local network query system. It is a multiple local gateway and can be carried in a response message in a list manner. The local network query system in this embodiment may be set in the core network or in the access network. The network location where the local network query system is located does not affect the implementation of this embodiment, as long as the network side can be associated with the local The network query system can communicate. The local network query system can also be implemented by using an existing network element, such as a Domain Name System (DNS) or a H (e) B Management System (HMS). It is of course also possible to use a new logical entity (ie one or more logical entities are preset to implement this function). After the local network query system is set up on the network, the network elements on the network side can interact with it. You can use the existing interface or add a new interface. In the following preferred embodiments of the present embodiment, the mobility management unit on the network side is taken as an example (three examples are described below), and the manner in which other network side network elements interact with the local network query system and the mobility management unit are described. The same or similar, and will not be described here. Example 1 The mobility management unit may send a query request to the local network query system after receiving the packet data network PDN connection setup request message or the attach request message. Preferably, the PDN connection establishment request message or the attachment request message requests to establish an MRA connection, and the mobility management unit selects the local gateway supporting the MRA capability to establish a connection; and/or, the PDN connection establishment request message or the attachment request message request is established. Local IP access connection, and subscription or mobility management of user equipment The unit configuration allows the user equipment to remotely access the local network, and the mobility management unit selects the local gateway that supports the MRA capability to establish a connection. In this example, in order for the user to select the corresponding local gateway when requesting the MRA connection or the local access link from the non-3GPP access, the mobility management unit may send at least one of the following to the authentication authority server: access point name, local gateway Address information, MRA capabilities, and then, the authentication authority server saves the information received from the mobility management unit. In this way, the information of the local gateway can be obtained through the authentication authorization server. The example two source mobility management unit may also send a query request to the local network query system after receiving the handover request message, where the query request carries at least one of the following: an access point name, and a local network where the target wireless side network element is located. Identification, base station identity of the target radio side network element. In this example, after obtaining the address information of the local gateway, the source mobility management unit can be used to determine whether the continuity of the local connection can be maintained (of course, the information of the local gateway can also be used for other processing), that is, source mobility management. The unit compares the received address information of the local gateway with the address information of the local gateway of the locally stored source wireless side network element. If they are consistent, it is determined that the continuity of the local connection can be maintained. If not, the local connection is deactivated. Of course, it is not only this type of determining whether the local connection can be maintained continuously. For example, the source network identifier of the local wireless network element may be inconsistent with the local network identifier of the established local connection. The management unit determines whether to maintain the continuity of the local connection according to the MRA capability that is queried from the local network query system when establishing the local connection. If the local gateway supports the MRA capability, it is determined that the continuity of the local connection can be maintained, and the local connection is converted into MRA is connected, otherwise, the local connection is deactivated. The example three-target mobility management unit may send a query request to the local network query system after receiving the tracking area update request message, where the query request carries at least one of the following: an access point name, where the target wireless side network element is located Local network identifier, base station identifier of the target radio side network element. In this example, after obtaining the address information of the local gateway, the target mobility management unit can also be used to determine whether the continuity of the local connection can be maintained. That is, the target mobility management unit compares the address information of the local gateway carried in the response message with the address information of the local gateway obtained from the source mobility management unit. If they are consistent, it is determined that the continuity of the local connection can be maintained, otherwise it is determined that the local connection cannot be supported. Continuity. As in the second example, determining whether the continuity of the local connection can be maintained may also be: the target mobility management unit acquires the MRA capability and the local network identifier from the source mobility management unit; and the target mobility management unit compares the local network of the target wireless side network element. The network identifier and the local network identifier obtained from the source mobility management unit, in case of inconsistency, the target mobility management unit determines whether to maintain the continuity of the local connection according to the MRA capability, wherein if the local gateway supports the MRA capability, it is determined to be able to maintain The continuity of the local connection, transforming the local connection into an MRA connection, otherwise the local mobility management unit deactivates the local connection. The interaction between the mobility management entity and the local network query system is illustrated by the above three examples, but is not limited thereto, and may be extended to other network elements or types of interaction according to the above three examples. In this embodiment, a local gateway information processing apparatus is further provided, which is configured to implement the above-mentioned embodiments and preferred embodiments thereof, which have been described herein, and are not described herein again. The module is explained. The apparatus is arranged to implement the above-described embodiments and preferred embodiments, and has not been described again. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. FIG. 5 is a structural block diagram of a local gateway information processing apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes: a transmitting module 52 and a receiving module 54, and the structure will be described below. The sending module 52 is configured to send a query request to the local network query system. The receiving module 54 is connected to the sending module 52, and is configured to receive a response message returned by the local network query system, where the response message carries one or more local gateways. Information. Preferably, the query request carries at least one of the following: an access point name, a local network identifier where the wireless side network element is located, and a base station identifier of the wireless side network element. Preferably, the information of the local gateway includes at least one of the following: address information of the local gateway, remote access local network function of the local gateway, MRA capability, a local network identifier where the local gateway is located, and a base station identifier supported by the local gateway. Preferably, the sending module 52 is configured to send a query request to the local network query system, where the query message carries the MRA capability, and the receiving module 54 is configured to receive a response message returned by the local network query system, where the response message carries the support Information about one or more local gateways of the MRA capability. The following description will be made in conjunction with several preferred embodiments, which are combined with the above-described embodiments and preferred embodiments. In the following preferred embodiment, when the terminal accesses from the wireless side network element outside the local network, and establishes a remote access local network connection, the network side goes to the local network query system to query the local gateway address information; When the network access establishes a local access connection, the network side uses the APN and the local network identifier or the home base station identifier to go to the local network query system to query the local gateway address information. The wireless side network element may be a home base station or a base station. Preferred Embodiment 1 FIG. 6 is a flowchart of dynamic registration and update of a local gateway according to an embodiment of the present invention. As shown in FIG. 6, in the preferred embodiment, a dynamic registration and/or a dynamic update request may be sent, and a local network query may be performed. After receiving the registration request message and/or configuration update request message of the local gateway, the system saves the information contained in the request message. At the same time, return to the local gateway registration response or configure the update response message. This will be explained separately below. The local gateway (for example, after power-on and power-on) queries the local network for dynamic registration of the system, and carries the registration gateway request message with the local gateway IP address, the APN, the local network identifier where the local gateway is located, and/or the local gateway support. The base station identity, the MRA capability of the local gateway. After the configuration information is changed, the local gateway may query the local network for dynamic update of the system, and the configuration update request message sent by the local gateway carries the local gateway IP address, the APN, the local network identifier where the local gateway is located, and/or the base station supported by the local gateway. Identification, MRA capabilities of the local gateway. The local network query system in the preferred embodiment may be a DNS, a wireless side network element management system (HMS, H(e) B Management System) or a new logical entity. If the local network query system is DNS, the existing interface and protocol can be used between the network side and the local network query system to implement the local gateway query and response; if the local network query system is an HMS or a new logical entity, the network A new interface needs to be added between the side and the local network query system. The communication between the two sides needs to be implemented by using a new protocol. The newly added interfaces and protocols can be similar to the interfaces and protocols used between the network side and the DNS. If the local gateway has the MRA capability, the local gateway carries the MRA capability in the request message, indicating that the network owner where the local gateway is located can provide the MRA service, and the MRA function is enabled. The MRA capability can be a new parameter, such as a new indication, or a new flag, or a combination of existing parameters. Therefore, the MRA capability can be implemented by adding IE or by using a combination of existing IEs. If the local gateway does not have the MRA capability, or the local gateway has the MRA capability but does not enable the MRA function, the local gateway does not need to carry the MRA capability of the local gateway in the request message. If the local network where the local gateway is located has a local network identifier, the local gateway carries the local network identifier (for example, LHN-ID, LHN name) where the local gateway is located in the request message; the local gateway may also carry in the request message. Home base station identity supported by the local gateway (eg, HCe) NB-ID, H(e) B name)₀ Preferred Embodiment 2 In the preferred embodiment, the terminal accesses from a base station or a home base station outside the local network, and desires to remotely access the local network to request to establish an MRA connection; or the terminal accesses from the local network, and hopes to establish a LIPA connection: The preferred embodiment is suitable for a terminal to access an EPC network or a GPRS network from GERAN/UTRAN/E-UTRAN. If the UE accesses from GERAN/UTRAN, the home base station is an HNB, the base station is a BSS or a NodeB/RNC, and the mobility management unit is an SGSN. At this time, the connection establishment request message between the UE and the SGSN is an activation PDP context request message. If the UE accesses from the E-UTRAN, the home base station is He B, the base station is e B, and the mobility management unit is the MME. There may be a home base station gateway in the network. If there is a home base station gateway, the message between the home base station and the mobility management unit needs to pass through the home base station gateway. Further messages between the home base station and the local gateway may be through the home base station gateway or not through the home base station gateway. For the scenario in which the home base station gateway forwards the message, the home base station gateway transparently transmits the received message, and the transparent transmission process has nothing to do with the embodiment, and details are not described herein. FIG. 7 is a flowchart of selecting a local gateway when a PDN connection is established according to an embodiment of the present invention. As shown in FIG. 7, the process includes the following steps: Step S702: A user terminal initiates a PDN connection establishment request, requesting to establish an MRA connection or LIPA. connection. Step S704, after receiving the PDN connection setup request message, the mobility management unit uses one of the following parameters, or a combination thereof: APN, the local network identifier where the current access base station is located, the base station identifier of the current access base station, and the local network. The query system queries the address information of the local gateway in the local network. Step S706, the local network query system returns a query response message to the mobility management unit. The local network query system queries the corresponding LGW address information in the locally saved information according to the parameters included in the received query request message, and the local network query system returns the LGW address information, the MRA capability, and the local gateway to the mobility management unit according to the query result. The local network identifier at the location and/or the base station identity supported by the local gateway. The LGW address information returned by the local network query system to the mobility management unit may be an LGW address information, or may be a list containing multiple LGW address information. If the local network query system returns an LGW list, the mobility management unit You can arbitrarily select an LGW address in the returned LGW list. The mobility management unit saves the LGW address information received by the query, the MRA capability, the local network identity where the local gateway is located, and/or the base station identity supported by the local gateway. The mobility management unit may also not save the LGW address information received by the query, the MRA capability, the local network identifier where the local gateway is located, and/or the base station identifier supported by the local gateway, but actively take the parameters and then go to the local network query when needed. System query. In addition, in step S704, the query message sent by the mobility management unit to the local network query system may further include an MRA capability. In the step S706, the LGW address information returned by the local network query system includes only the LGW that supports the MRA capability, or the LGW list. If the UE requests an MRA connection, the mobility management unit selects the MGW capable of supporting the MRA to establish a connection for the terminal. If the UE requests a LIPA connection, and the UE's subscription or mobility management unit configuration allows the UE to remotely access the local network, the mobility management unit selects the MRA capable MGW to establish a connection for the terminal. Step S708, the subsequent process of establishing the PDN connection is performed, and the subsequent process is similar to the prior art, and is not described herein. Preferred Embodiment 3 The preferred embodiment is applicable to a user moving to another base station or a home base station after the local connection is established from the source base station (e.g., the home base station, but not limited to this). This embodiment is applicable to a terminal accessing an EPC network or a GPRS network from GERAN/UTRAN/E-UTRAN. If the UE accesses from the GERAN/UTRAN, the home base station is the HNB, the base station is the B S S or the NodeB/RNC, and the mobility management unit is the SGSN. If the UE accesses from the E-UTRAN, the home base station is the HeNB, the base station is the eNB, and the mobility management unit is the MME. There may be a home base station gateway in the network. If there is a home base station gateway, then all the messages between the home base station and the mobility management unit need to pass through the home base station gateway. Further messages between the home base station and the local gateway may or may not be through the home base station gateway or the home base station gateway. For the scenario in which the home base station gateway forwards the message, the home base station gateway transparently transmits the received message, and the transparent transmission process is not related to the embodiment, and details are not described herein. If it is a UMTS/GERAN access, and the mobility management unit is a Gn/Gp SGSN, there is no SGW in this process, and all the messages passing through the SGW do not need to pass through the SGW, but the mobility management unit sends the message directly to the local gateway. FIG. 8 is a flowchart of selecting a local gateway in a handover procedure according to an embodiment of the present invention. As shown in FIG. 8, the process includes the following steps: Step S802: A source home base station acquires measurement information of a neighboring cell according to information in a measurement report. Select the appropriate target cell. Step S804: The source home base station sends a handover request message to the source mobility management unit. The target base station identifier is included, and optionally includes a local network identifier where the target base station is located, if the source home base station knows the local network identifier of the target base station. Step S806: The source mobility management unit queries the local network for the supported LGW address information according to one of the following parameters, or a combination thereof: the APN, the local network identifier of the target base station, and the base station identifier of the target base station. Step S808: The local network query system returns, to the source mobility management unit, the LGW address information supported by the target base station, the MRA capability, the local network identifier where the local gateway is located, or the base station identifier supported by the local gateway. The source mobility management unit compares the received LGW address information with the locally stored LGW address information supported by the source home base station to see if they are consistent. If they are consistent, the target base station and the source home base station are considered to be in the same local network. If the local access connection is inconsistent, the target base station and the source home base station are not in the same local network, and the continuity of the local access connection cannot be maintained. The source mobility management unit deactivates the local access connection. If the local network identifier where the target base station is located is inconsistent with the local network identifier of the established local connection (if the target base station does not belong to any local network, it is considered to be inconsistent), then the mobility management unit may also perform the MRA of the LGW according to the query when establishing the local connection. The ability to determine whether to maintain the continuity of the local access connection. If the LGW supports MRA, the local connection continuity is maintained, and the local access connection is converted into an MRA connection, otherwise the source mobility management unit deactivates the local access connection. The process of deactivating the local connection is a technique well known to those skilled in the art and will not be described here. If the local access connection needs to be deactivated, the source mobility management unit performs subsequent steps after completing the local connection deactivation. Step S810, performing a subsequent process of the handover, and the subsequent process is similar to the prior art, and details are not described herein. Preferred Embodiment 4 This preferred embodiment is applicable to a user moving to another base station or a home base station after the local connection is established, because the location changes. This embodiment is applicable to a terminal accessing an EPC network or a GPRS network from GERAN/UTRAN/E-UTRAN. If the UE accesses from the GERAN/UTRAN, the home base station is the HNB, the base station is the B S S or the NodeB/RNC, and the mobility management unit is the SGSN. If the UE accesses from the E-UTRAN, the home base station is the HeNB, the base station is the eNB, and the mobility management unit is the MME. There may be a home base station gateway in the network. If there is a home base station gateway, then All messages between the home base station and the mobility management unit need to pass through the home base station gateway. Further messages between the home base station and the local gateway may or may not be through the home base station gateway or the home base station gateway. For the scenario in which the home base station gateway forwards the message, the home base station gateway transparently transmits the passed message, and the transparent transmission process has nothing to do with the present invention, and details are not described herein. If it is UMTS/GERAN access, and the mobility management unit is Gn/Gp SGSN, there is no SGW in this process, and all messages passing through the SGW do not need to pass through the SGW, but the mobile management unit sends the message directly to the local gateway. FIG. 9 is a flowchart of selecting a local gateway in a tracking area update process according to an embodiment of the present invention. As shown in FIG. 9, the process includes the following steps: Step S902: A terminal sends a tracking to a target mobility management unit by a target wireless side network element. a region update request message; step S904, the target mobility management unit sends a context request message to the source mobility management unit; step S906, the source mobility management unit sends a context response message to the target mobility management unit, carrying user context information, where the local access connection is carried The LGW address, optionally including the MRA capability of the LGW and the local network identifier where the LGW is located; Step S908, optionally, the terminal, the mobility management unit, and the authentication authorization server perform an authentication process; Step S910, the target mobility management unit is configured according to One of the following parameters, or a combination thereof: APN, the local network identifier of the target radio side network element, and the base station identifier of the target radio side network element, query the local network query system for the LGW address information supported by the target radio side network element. Step S912: The local network query system returns the LGW address information supported by the target radio side network element of the target mobility management unit, the MRA capability, the local network identifier where the local gateway is located, or the base station identifier supported by the local gateway. The target mobility management unit compares the LGW address information received from the source mobility management unit with the LGW address information queried from the local network query system to see if the two LGW addresses are consistent. If they are consistent, the target mobility management unit considers the target radio side. The network element and the source base station can maintain the continuity of the local access connection in the same local network. Otherwise, it is considered that the continuity of the local access connection cannot be supported. If the context in step S906 includes the MRA capability and the local network identity, the target mobility management unit matches the local network identity of the target wireless side network element. If the local network identifier of the target wireless side network element is inconsistent with the local network identifier of the established local access connection (if the target wireless side network element is not If it belongs to any local network, it is considered to be inconsistent. Then, the target mobility management unit can also judge whether to maintain the continuity of the local access connection according to the MRA capability of the LGW that is queried when establishing the local connection. If the LGW supports MRA, the local connection continuity is maintained, and the local access connection is converted to an MRA connection, otherwise the source mobility management unit deactivates the local access connection. Step S914: The target mobility management unit sends a context confirmation message to the source mobility management unit, carrying the determination result. If the determination result indicates that the continuity of the local access connection is not supported, the source mobility management unit deactivates the local access connection. The process of deactivating the local connection is a technique well known to those skilled in the art and will not be described here. Step S916: Perform a subsequent process of updating the tracking area, and the subsequent process is similar to the prior art, and is not described herein. Embodiment 5 FIG. 10 is a flowchart of selecting a local gateway and saving a local gateway when a user initially attaches according to an embodiment of the present invention. As shown in FIG. 10, the process includes the following steps: Step S1002: A user terminal needs to establish before performing communication. A Radio Resource Control (RRC) connection is used as a bearer for signaling messages or service data. Step S1004: The user terminal sends a message of initializing a non-access stratum (Non-Access-Stratum, referred to as NAS) to perform an attach operation. Step S1006: The radio side network element sends an initial user message to the mobility management unit. If there is a home base station gateway, it is forwarded to the home base station gateway, and then the home base station gateway sends the message to the mobility management unit. Step S1008, optionally, the terminal, the mobility management unit, and the authentication authority server perform an authentication process. Step S1010: After receiving the attach request message, the mobility management unit uses one of the following parameters, or a combination thereof: APN, the local network identifier of the current access base station, and the base station identifier of the current base station, and queries the local network query system for the address of the local gateway. Information mobility management unit. Step S1012: The local network query system returns a query response message to the mobility management unit. The local network query system queries the corresponding LGW address information in the locally saved information according to the received query request message, and the local network query system returns the local gateway LGW address information, the MRA capability, and the local gateway according to the query result to the mobile management unit. Local network identity and/or base station identity supported by the local gateway. The LGW address information returned by the local network query system to the mobility management unit may be an LGW address information, or may be a list containing multiple LGW address information, if the local network query system returns Is an LGW list, then the mobility management unit can arbitrarily select an LGW address in the returned LGW list. The mobility management unit saves the LGW address information received by the query, the MRA capability, the local network identity where the local gateway is located, and/or the base station identity supported by the local gateway. In addition, if the terminal requests to establish an MRA connection, in step S1010, the query message sent by the mobility management unit to the local network query system may further include an MRA capability. In the step S1012, the LGW address information returned by the local network query system includes only the LGW that supports the MRA capability, or the LGW list. If the UE requests an MRA connection, the mobility management unit selects the MGW capable of supporting the MRA to establish a connection for the terminal. If the UE requests a LIPA connection, and the UE's subscription or mobility management unit configuration allows the UE to remotely access the local network, the mobility management unit selects the MRA capable MGW to establish a connection for the terminal. In step S1014, the subsequent process of the attach process is performed until step S1016, and the subsequent process is similar to the prior art, and details are not described herein. Step S1016, at the end of the attaching process, the mobility management unit sends a notification request message to the authentication authority server, carries the APN and LGW addresses, and the MRA capability, and requests to save the APN, the LGW address, and the LGW MRA capability in the authentication authorization server. In order for the user to request an MRA connection or a local access connection from a non-3GPP access, the corresponding local gateway address is selected. Step S1018: The authentication authorization server saves the received APN, LGW address, and LGW MRA capability, and returns a mobility management unit notify response message. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

A local gateway information processing method, including:

The network side sends a query request to the local network query system;

The network side receives the response message returned by the local network query system, where the response message carries information of one or more local gateways.

The method according to claim 1, wherein the query request carries at least one of the following: an access point name, a local network identifier where the wireless side network element is located, and a base station identifier of the wireless side network element.

The method according to claim 1 or 2, wherein the information of the local gateway comprises at least one of: address information of the local gateway, remote access local network function MRA capability of the local gateway, The local network identifier where the local gateway is located, and the base station identifier supported by the local gateway.

4. The method according to claim 1, wherein

The network side sends a query request to the local network query system, where the query message carries the MRA capability;

The network side receives the response message returned by the local network query system, where the response message carries information of one or more local gateways that support the MRA capability.

The method according to any one of claims 1 to 4, wherein the network side comprises a mobility management unit.

The method according to claim 5, wherein the sending, by the mobility management unit, the query request to the local network query system comprises:

After receiving the packet data network PDN connection setup request message or the attach request message, the mobility management unit sends the query request to the local network query system.

The method according to claim 6, wherein, after the mobile management unit receives the response message returned by the local network query system, the method further includes:

The PDN connection establishment request message or the attach request message requests to establish an MRA connection, and the mobility management unit selects an MRA capable local gateway to establish a connection; and/or the PDN connection establishment request message or the The attach request message requests to establish a local IP access connection, and the subscription of the user equipment or the mobility management unit configuration allows the Remote access to the local network, then the mobility management unit selects the local gateway supporting the MRA capability to establish a local IP access connection.

The method according to claim 6, wherein, when the mobility management unit receives the attach request message, the method further includes:

The mobility management unit sends at least one of the following to the authentication and authorization server at the end of the attaching process: an access point name, address information of the local gateway, and an MRA capability;

The authentication authority server saves information received from the mobility management unit.

9. The method according to claim 5, wherein the sending, by the mobility management unit, the query request to the local network query system comprises:

The source mobility management unit receives the handover request message;

The source mobility management unit sends the query request to the local network query system, where the query request carries at least one of the following: an access point name, a local network identifier where the target wireless side network element is located, and a target wireless Base station identifier of the side network element.

The method according to claim 9, wherein, after receiving the response message that is returned by the local network query system and carrying the address information of the local gateway, the source mobility management unit further includes:

The source mobility management unit compares the received address information of the local gateway with the address information of the local gateway of the locally stored source wireless side network element. If they are consistent, it is determined that the continuity of the local connection can be maintained. If not, the activity is deactivated. local connection.

The method according to claim 9, further comprising: if the local network identifier where the target wireless side network element is located is inconsistent with the established local connection local network identifier, the source mobility management unit establishes a local The MRA capability queried from the local network query system determines whether to maintain the continuity of the local connection, wherein if the local gateway supports the MRA capability, it is determined that the continuity of the local connection can be maintained, and the local connection is converted into the MRA. Connect, otherwise, deactivate the local connection.

12. The method according to claim 5, wherein the sending, by the mobility management unit, the query request to the local network query system comprises:

The target mobility management unit receives the tracking area update request message; The target mobility management unit sends the query request to the local network query system, where the query request carries at least one of the following: an access point name, a local network identifier where the target wireless side network element is located, and a target wireless Base station identifier of the side network element.

The method of claim 12, after the target mobility management unit receives the response message of the address information of the local gateway returned by the local network query system, the method further includes:

The target mobility management unit compares the address information of the local gateway carried in the response message with the address information of the local gateway acquired from the source mobility management unit. If they are consistent, it is determined that the continuity of the local connection can be maintained. Otherwise, Make sure that the continuity of the local connection cannot be supported.

The method according to claim 12, further comprising: the target mobility management unit acquiring, from the source mobility management unit, an MRA capability and a local network identifier of the source radio side network element;

The target mobility management unit compares the local network identifier of the target radio side network element with the local network identifier of the source radio side network element obtained from the source mobility management unit, and in case of inconsistency, the target mobility management The unit determines whether to maintain the continuity of the local connection according to the MRA capability, wherein if the local gateway supports the MRA capability, it is determined that the continuity of the local connection can be maintained, and the local connection is converted into an MRA connection, otherwise, by the source The mobility management unit deactivates the local connection.

The method according to claim 1, wherein before the sending, by the network side, the query request to the local network query system, the method further includes:

The local network query system receives a registration request message and/or an update request message from the local gateway carrying information of the local gateway.

16. The method of claim 15, wherein the information of the local gateway carried comprises at least one of the following:

The IP address of the local gateway, the name of the access point supported by the local gateway, the local network identifier where the local gateway is located, the base station identifier supported by the local gateway, and the MRA capability of the local gateway.

The method according to claim 1, wherein the local network query system is: a domain name system, a wireless side network element management system, or a preset new logical entity.

18. A local gateway information processing apparatus, comprising:

a sending module, configured to send a query request to a local network query system; The receiving module is configured to receive a response message returned by the local network query system, where the response message carries information of one or more local gateways.

The device according to claim 18, wherein the query request carries at least one of the following: an access point name, a local network identifier where the wireless side network element is located, and a base station identifier of the wireless side network element.

The device according to claim 18 or 19, wherein the information of the local gateway comprises at least one of: address information of the local gateway, remote access local network function MRA capability of the local gateway, The local network identifier where the local gateway is located, and the base station identifier supported by the local gateway.

21. The device according to claim 18, wherein

The sending module is configured to send a query request to the local network query system, where the query message carries an MRA capability, and the receiving module is configured to receive a response message returned by the local network query system, where the response The message carries information about one or more local gateways that support MRA capabilities.