WO2009097780A1

WO2009097780A1 - Processing method and device for static ip address

Info

Publication number: WO2009097780A1
Application number: PCT/CN2009/070187
Authority: WO
Inventors: Zhuo Chen; Ming Li; Xiaolong Guo; Wanqiang Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2008-02-04
Filing date: 2009-01-16
Publication date: 2009-08-13

Abstract

A processing method for static IP address is disclosed, and the method includes: detecting UE's static IP address which corresponds to an APN; establishing the UE's bearer context at the static IP address. The embodiments of the invention use different mechanisms to solve the problem that packet data gateway node can not process packet data, and the problem maybe appear when the UE is configured with a static IP address. In addition, an efficient processing method for the APN configured with a static IP address is provided. And the problem on processing data sent from network to UE when the UE is configured with a static IP address but without established bearer is also solved. The processing method of network for the static IP address is defined, and the performance of the system is enhanced.

Description

The invention relates to a method and a device for processing a static IP address. The application is filed on February 4, 2008, and the application number is 200810006213.X, and the invention name is "a method, system and device for processing a static IP address". Priority of Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The embodiments of the present invention relate to the field of network technologies, and in particular, to a method and a device for processing a static IP address. Background technique

A schematic diagram of an existing GPRS (General Packet Radio Service)/UMTS (Universal Mobile Telecommunication System) system is shown in FIG. 1 , where SGSN (Serving GPRS Support Node, Serving GPRS Support Node) There is an interface with the HLR (Home Location Register), and the Gc interface between the GGSN (Gateway GPRS Support Node) and the HLR is an optional interface. When the system deploys the Gc interface, the GGSN can obtain the location information and/or routing information of the UE directly from the HLR through the Gc interface.

In the GPRS/UMTS network, the case of assigning a static IP address to a user is applicable to a network-initiated PDP (Packet Data Protocol) context activation process. That is, when the PDN has a PDP PDU addressed to the user of the static IP address

When the GPRS/UMTS network arrives at the GGSN, the GGSN will query the HLR for the user's routing information, such as the SGSN address, and send a notification to the SGSN requesting the SGSN to process. If the SGSN can process, the requesting UE (User Equipment) initiates an activation PDP context procedure. The PDP context activation process that the GPRS/UMTS network will initiate the network request

(Network-Requested PDP Context Activation), as shown in Figure 2, including Next steps:

Step S201: After receiving the PDP PDU, the GGSN determines whether the PDP context activation process of the network request needs to be initiated. The GGSN can store the PDP PDIL that is subsequently sent to the same IP address.

Step S202: The GGSN may send Send Routing Information for to the HLR.

GPRS message. The message is sent to the HLR through the Gc interface, and the parameter carried is IMSL. If the HLR determines that the request can be served, the HLR replies to the GGSN via the Gc interface with a Send Routing Information for GPRS Ack message, which carries the IMSI (International Mobile Subscriber Identification Number, SGSN Address, Mobile Station Not Reachable Reason and other parameter information. If the MNRG (Mobile Station Not Reachable for GPRS flag) flag is set in the HLR, the Mobile Station Not Reachable Reason parameter is carried, and the Mobile Station Not Reachable Reason parameter indicates the reason for setting the MNRG flag. It is stored in the MNRR record. If the reason indicated by the MNRR record is not "No Paging Response", the HLR shall add the GGSN number to the GGSN list GGSN-list of the user.

If the HLR decides that the request cannot be serviced (eg, IMSI is not known in the HLR;), the B'HLR should reply to the Send Routing Information for GPRS Ack message, which carries the IMSI, MAP Error Cause parameter. Among them, the parameter MAP Error Cause indicates the reason for rejection.

Step S203: If the returned message has an SGSN address and there is no Mobile Station Not Reachable Reason parameter, or the Mobile Station Not Reachable Reason parameter indicates "No Paging Response", the GGSN shall send a PDU Notification Request message to the SGSN indicated by the HLR, the message Carry IMSI, PDP Type, PDP Address, APN parameters. Otherwise, the GGSN should set the MNRG flag for the UE. The SGSN returns a PDU Notification Response message to the GGSN, indicating that the SGSN should request the UE to deactivate the PDP context with the indicated PDP address.

Step S204: The SGSN sends a Request PDP Context Activation message to the UE, where the message carries the parameters TI, PDP Type, PDP Address, APN (Access Point Name, access point name) - APN is the logical name indicating the logical name of the packet data network PDN and / or the service that the user wants to access. For example, the APN used by China Mobile to connect to the Internet is CMNET (China Mobile Net, China Mobile Network) ) to request the UE to activate the indicated PDP context.

Step S205: The PDP context activation process is started.

After the PDP context is established, the network can transmit the PDP PDU to the user.

It can be seen from the above process that in the existing GPRS/UMTS network, the premise that the process is successfully executed includes at least: an interface (Gc) exists between the GGSN and the HLR, and the HLR stores the address information of the SGSN serving the UE. That is, the GGSN can directly obtain the routing information of the UE, such as the SGSN address, from the HLR through the Gc interface.

Under the current SAE (System Architecture Evolved) network architecture, the functions of the SGSN and GGSN in the GPRS/UMTS system core network are replaced by three new entities of the SAE system: SGSN (or with MME (Mobility Management Entity) , the mobility management entity), the following unified cylinder is called SGSN), SGW (Serving Gateway), and PGW (PDN Gateway, packet data network gateway). The HLR is replaced by HSS (Home Subscriber Server). . Moreover, there is no logical interface between the HSS and the SGW and the PGW, as shown in Figure 3.

In the SAE network, in order to realize the "always-on" IP connection, the UE will allocate the UE to the network as long as the UE accesses the network through the E-UTRAN (Evolved Universal Terrestrial Radio Access Network). A PDP address, such as a packet data network PDN address, is usually an IP address. The following describes an IP address as an example, and establishes a default context Default Bearer Context.

In the SAE, when the E-UTRAN accesses the network, the QoS information is transmitted through the establishment process of the attach and the default bearer, and the establishment of the control planes of the RAN~MME segment, the MME~SGW segment, and the SGW~PGW segment is implemented. And establishing the user plane bearer of the RAN~SGW segment and the SGW~PGW segment, and completing the establishment of the bearer between the UE and the RAN. At the same time, the SAE network supports UEs with 2G/3G and LTE (Long Term Evolved) access capabilities to access the network through GERAN/UTRAN, and the basic solution is that when the UE accesses GERAN/UTRAN, The original attach procedure of the GERAN/UTRAN system will be normally performed, that is, the UE is attached to the network, and when the UE needs an IP address, the bearer is established (or the PDP context is activated), and the IP address is assigned. Summary of the invention

The embodiment of the present invention provides a method and a device for processing a static IP address, so as to solve the problem that the static address is not processed in the prior art.

To achieve the above objective, an embodiment of the present invention provides a method for processing a static IP address, including the following steps:

Detecting a static IP address of the corresponding access point name APN of the user terminal UE; establishing a context in which the user is in the static IP address.

The embodiment of the present invention further provides a method for processing a static IP address to solve the problem that the PGW in the prior art processes a packet data message of a UE configured with a static IP address.

To achieve the above objective, an embodiment of the present invention provides a control entity, including a module for detecting a static IP address of a corresponding access point name APN of a user terminal UE;

And a module for establishing a bearer context of the user in the static IP address according to the static IP address detected by the detecting module.

The packet data gateway node receives a packet data message message about the user terminal having the static IP address, and determines that the bearer has not been established for the user terminal;

The packet data gateway node interacts with a user database and a routing device in the network to establish a load of the user terminal. The embodiment of the present invention further provides a processing method related to a static address to solve the problem in the prior art that the PGW establishes a route when processing packet data of a UE configured with a static IP address.

To achieve the above objective, an embodiment of the present invention further provides a method for processing a static IP address, including the following steps:

The core network node detects that the user terminal accesses the network or connects to multiple PDNs; the core network node acquires a user plane processing node address serving the user terminal, and sends the address to the user database to save the user plane processing node. address.

Compared with the prior art, the embodiment of the present invention provides a processing method when the APN is configured with a static IP address by using different mechanisms, and a packet data gateway node that may occur when the user configures a static IP address cannot process the packet data message. The problem is to get and update the user face processing node address in the user database. The embodiment of the present invention not only effectively solves the processing method for the APN configured with the static address, but also solves the problem of processing the data sent by the network to the user when the user configures the static IP address and does not establish the bearer, and also solves the problem in the user database. The problem of saving and updating user plane processing nodes.

These methods not only clarify the way the network handles static IP addresses, but also enhance system performance. DRAWINGS

1 is a schematic structural diagram of a GPRS/UMTS system in the prior art;

2 is a PDP context activation process of a network request in the prior art;

3 is a schematic structural diagram of a GPRS/UMTS system and a SAE system in the prior art; FIG. 4 is a process of establishing an attach and a default bearer when an E-UTRAN accesses a network in a scenario according to Embodiment 1 of the present invention;

5 is a flowchart of a processing method when an APN is configured with a static IP address in a scenario in Embodiment 1 of the present invention;

6 is a flowchart of a processing method when an APN is configured with a static IP address in a scenario in the first embodiment of the present invention; 7 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

8 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

9 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

10 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

11 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

12 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

13 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

14 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

15 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

16 is a flowchart of processing, by a PGW, a received PDP PDU in a scenario in Embodiment 2 of the present invention;

17 is a flowchart of obtaining an SGW address by an HSS in a scenario in Embodiment 3 of the present invention;

18 is a flowchart of obtaining an SGW address by an HSS in a scenario in Embodiment 3 of the present invention;

FIG. 19 is a flowchart of an HSS obtaining an SGW address in a scenario in Embodiment 3 of the present invention. detailed description In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems:

In the prior art, there is no logical interface between the HSS and the SGW and the PGW, and the SGW address of the user is not saved in the HSS. When a UE with a static IP address accesses the network through GERAN/UTRAN, the bearer may not be established yet, such as the bearer context Bearer Context or the PDP context PDP Context. At this time, if the PDP PDU sent to the static address of the network reaches the PGW, the PGW does not have the bearer and routing information of the user at this time, and there is no interface between the PGW and the HSS, and between the PGW and the SGSN/MME, so the PGW The routing information of the UE cannot be queried by directly accessing the HSS, and the routing information of the UE cannot be queried through the SGSN/MME. This causes the PGW to be unable to find the UE and thus cannot process the PDP PDU.

Similarly, when multiple APNs are supported, and multiple APNs have multiple PGWs, if the user has a static IP address configured on some of the APNs, and if the user does not establish a bearer or all bearers corresponding to the APN on the APNs. Have been deleted. At this time, if the PDP PDU sent to the static address reaches the PGW, the PGW cannot find the UE similarly to the above.

In these scenarios, because the PGW does not have the user's bearer information and cannot query the routing information, how the PGW processes the PDP PDU sent to the static address becomes a problem that must be solved.

Moreover, in SAE, there is no corresponding implementation for the processing of static addresses. In addition, the HSS does not store the SGW address information of the user, that is, even if the PGW can communicate with the HSS, the HSS cannot provide the PGW with routing information such as the SGW address. Therefore, how to let the HSS obtain or update the routing information of the UE is also a problem to be solved.

In the first embodiment of the present invention, a processing method for processing a static IP address when an APN is configured with a static IP address is provided.

In this embodiment, if the user has a static IP address for a certain or some APN (single PDN or multiple PDN) (bind with the user through subscription, SIM card or other means), the user passes GERAN and/or UTRAN. And/or E-UTRAN initiates an Attach access network When the network is used, the APN can be used as the default APN to establish the 7-load context of the static address. The APN configured with the static address can be saved in the subscription database or sent to the mobility management entity through the subscription database; or, if the user has a certain APN (that is, a single PDN or multiple PDN) A static IP address (bound to the user through a subscription, SIM card, or other means), when the user accesses the network, the APN can be provided to the mobility management entity as the default APN.

After the mobility management and/or control entity (such as the MME and/or the SGSN) obtains the APN of the user from the subscription database (such as the HSS) or from the APN information provided by the user, if the APN is configured with a static address, it may be established. The bearer context corresponding to the static address may also be the default bearer context.

This embodiment is exemplified by the user accessing the network through the E-UTRAN, but the same applies to the case where the user supporting the SAE accesses the network through the GERAN and/or the UTRAN, and the processing manners are essentially the same or similar.

The method of this embodiment will be described below with reference to the accompanying drawings and specific steps:

In the first scenario of the first embodiment, when accessing through the E-UTRAN, the APN configured with the static IP address is used as the default APN. Thus, when accessing the network through E-UTRAN, the attach and default bearer establishment process is as shown in Figure 4:

Step S401: The UE sends an attach request to the MME.

Step S402: After receiving the attach request, the MME triggers a series of processing (such as: authentication, location update, subscription data, etc.).

The subscription data obtained by the MME from the HSS includes an indication of all APNs (Access Point Names) and default APNs that the user is allowed to access, and a subscription QoS for each APN that is allowed to access.

Step S403: The MME sends a default bearer request to the SGW.

The MME selects a PGW according to the default APN and the PGW selection function. The MME also selects a suitable SGW. After the necessary control plane information is allocated and saved (such as the MME assigns downlink control plane information), the necessary information (such as the QoS derived from the subscription data) is created by creating a default bearer request message. Information, MME allocates downlink control plane information, lacks Provincial APN, etc.) is passed to the corresponding SGW.

Step S404: The SGW sends a default bearer request to the PGW.

Specifically, after receiving the message of creating a default bearer request, the SGW saves the necessary information (such as QoS information and MME allocating downlink control plane information). After the SGW allocates and saves the necessary resources (such as the SGW to allocate control plane information, the SGW allocates user plane information, etc.), the SGW sends a create default request message to the corresponding PGW. The message carries QoS information, SGW control plane information, SGW user plane information, and default APN.

Step S405: After receiving the request message of the SGW, the PGW establishes a corresponding context, and returns a default bearer response message to the corresponding SGW, and saves the necessary information.

Specifically, the necessary information includes QoS information, SGW control plane information, SGW user plane information, PGW control plane information, and PGW user plane information. The message carries PGW control plane information, PGW user plane information, and the like.

After receiving the response message, the SGW saves the PGW control plane information and the PGW user plane information carried in the information in the previously established bearer context. In this way, the interaction between the control plane information and the user plane information between the SGW and the PGW is completed through steps S404 and S405, thereby realizing the establishment of the control plane of the SGW to the PGW and the establishment of the user plane.

Step S406: The SGW allocates an uplink control plane corresponding to the SGW uplink control plane information and a user plane resource corresponding to the SGW uplink user plane information, and saves the information in the 7-load context, and then sends the creation defect to the corresponding MME. Province 7|load response message.

After receiving the response message, the MME stores the information carried in the information (such as SGW control plane information, SGW user plane information, and so on) in the previously established bearer context. After the steps S403 and S406 complete the interaction of the control plane information between the MME and the SGW, the establishment of the control plane is completed.

Step S407: The MME sends an attach accept message to the RAN, and transmits necessary information (such as QoS information, MME control plane information, SGW user plane information, default APN) to the RAN through an attach accept message. Step S408, the RAN saves the necessary information and performs radio bearer establishment. At the same time, through this step, the RAN also delivers the default APN to the UE, thereby notifying the UE which APN the APN associated with the activated default bearer is.

Step S409, the RAN allocates and saves necessary information (such as RAN control plane information, RAN user plane information), and transmits the information to the MME through an attach complete message.

After receiving the message, the MME stores the necessary information (such as RAN control plane information and RAN user plane information). The communication between the control plane information between the MME and the RAN is implemented through steps S407 and S409, and the establishment of the control plane is completed.

Step S410: The MME transmits necessary information (such as RAN user plane information) to the SGW by using a bearer update request message, and the SGW saves the information. In this way, the user plane information interaction between the RAN and the SGW is implemented through the MME relay through the steps S406, S407, S409, and S410, thereby completing the establishment of the user plane bearer between the two.

In this way, the QoS information is transmitted through the above steps, and the establishment of the RAN ~ MME segment, the MME ~ SGW segment, the SGW ~ PGW segment control plane, and the user plane bearer of the RAN - SGW segment and the SGW - PGW segment are implemented. The establishment of the bearer between the UE and the RAN is completed in step S408.

Step S411: The MME sends an update location message to the HSS. After storing the APN and the PGW address, the HSS sends a response message to the MME.

After the MME receives the bearer update response message, if an EPS bearer is established, and the subscription data indicates that the user can perform handover to a non-3GPP (non-3GPP) access technology, and if the PG selected by the MME is different from the HSS in the subscription context In the PGW indicated, then the MME shall send an Update Location message to the HSS to support mobility to the non-3GPP access technology, the message containing the APN and PGW addresses. The HSS stores the APN and PGW addresses and sends a response message to the MME.

The changes that need to be made are shown in Figure 5:

Step S501: The user terminal sends an attach request to the RAN.

If the APN configured with the static address is bound to the user terminal (for example, the APN is written to the user terminal, or is bound to the SIM card or bound to the user by other means, etc.), or the user terminal knows its own static IP address (such as Address is written to the user terminal, or static IP address The APN and/or the static IP address configured with the static address may be carried in the attach request message initiated by the UE, or the static IP address is assigned to the user. If the user has multiple APNs and/or static IP addresses configured with static IP addresses, they may carry only one of the APNs and/or static IP addresses, or may carry multiple or all APNs and/or static IP addresses.

If the user terminal is not bound to an APN configured with a static IP address or does not know its own static IP address, the user terminal may not carry the above information in the attach request.

Step S502: After receiving the attach request, the MME may trigger a series of processes (such as authentication, location update, and subscription data, etc.), where the subscription data obtained by the MME from the HSS includes the user allowed access. An indication of all APNs and default APNs, and EPS subscription QoS for each APN allowed to access. If the static IP address or APN information of the user terminal is not included in the foregoing step S501, the MME needs to obtain information about the static IP address from the subscription data.

If the subscriber's subscription data has one or more APNs configured with a static IP address, the ASN may be selected as the default APN in the HSS and the indication is sent to the MME. The MME uses the APN as the default. APN; or when the default APN indicated by the HSS is not an APN configured with a static IP address, the MME may select an APN configured with a static IP address from the APN obtained by the HSS as the default APN. These choices may be random, based on a certain probability, or based on any factors and/or needs of a configuration strategy, contracted data, and/or operational management, depending on the specification and/or implementation.

For other APNs configured with static IP addresses, either as a normal APN according to the prior art, or after the attach process is in progress or after the attach process is completed, the existing UE requested PDN connectivity process or other process is invoked. A default bearer is established on the APN, and a bearer context for the static IP address is established.

If the subscription data provided by the HSS includes one or more static IP addresses corresponding to the APN, the MME may respectively transmit one or more static IP addresses to the SGW and the PGW through step S503 and step S504, and may also One or more of the PGW, the SGW, and the MME deliver the static IP address to the UE as the IP used by the UE. address.

Further, if the user terminal provides one or more static IP addresses in step S501, or in step s502, the MME obtains one or more static IP addresses corresponding to the APN from the HSS, then step S503 may be performed. And one or more static IP addresses are sequentially delivered to the SGW and the PGW, respectively, in step S504.

Further, if the MME obtains an APN from the attach request message sent by the UE, and the user has access to the APN (if the APN belongs to the APN subscribed by the user), it may also be based on a certain policy, and/or configuration, And/or implementation, selecting the APN as the default APN, without selecting or ignoring the indicated default APN obtained from the HSS. If the MME obtains multiple APNs from the UE and the user has access to these APNs (if the APN belongs to the APN subscribed by the subscriber), one of them may be selected as the default APN. These choices may be random, based on a certain probability, or based on any factor and/or need, such as a configuration strategy, contracted data, and/or operational management, depending on the specification and/or implementation.

After the MME performs the default setup (step S503 to step S510), the default APN can be used, and the bearer context of the default APN is established in the subsequent process. After the mobility management and/or control entity (such as MME and/or SGSN) obtains the APN of the user from the subscription database (such as HSS) or from the APN information provided by the user, if the APN is configured with a static IP address, The 7-load context of the static IP address is established, and the 7-load context corresponding to the static IP address can also be used as the default bearer context of the APN. In another scenario of the first embodiment, as shown in FIG. 6, when the E-UTRAN is accessed, the APN configuring the static IP address is not used as the default APN.

In this case, when the UE accesses the network through the E-UTRAN, whether the user reports the APN and/or the static IP address, the MME includes one or more static IP addresses configured in the subscription data received from the HSS. APN, and none of these APNs are the default APNs indicated by the HSS. The MME will follow the HSS indication and select the default APN indicated by the HSS to establish a bearer. At this time, the main steps of the attach and default bearer establishment process are substantially the same as those in the prior art as shown in FIG. Further, the MME may also send the received APN and/or static IP address configured with a static IP address to the UE through steps S607 and S608. After the attach process is in progress or the attach process is completed, the UE may invoke an existing UE requested PDN connectivity process or other process, activate the bearer to the APN, establish a payload for the static IP address, and may also set the static IP address. The corresponding payload context is used as the default 7-load context of the APN.

By using the method provided in the foregoing embodiment of the present invention, the embodiment of the present invention provides a processing method when the APN is configured with a static IP address through different mechanisms, and clarifies the processing manner of the static IP address of the network, and can also enhance the system performance. .

The second embodiment of the present invention provides a solution to the problem that the PGW cannot process the PDP PDU due to the configuration of the static IP address.

In an application scenario of the second embodiment, a new interface is introduced between the packet data gateway node PGW and the HSS, and corresponding processing is performed according to whether the address of the SGW serving the UE is previously stored in the HSS.

(1) The HSS holds the address of the SGW that provides services to the UE.

After a new interface is entered between the PGW and the HSS, when the UE accesses the network through GERAN, UTRAN or E-UTRAN, the HSS saves the SGW in addition to the address of the SGSN (and/or MME, the same below). the address of. Then, when the PDP PDU arrives at the PGW and the bearer has not been established for the user on the PGW, the PGW will query the HSS for the routing information of the user.

The HSS may return information such as the SGW address to the PGW, and then the PGW notifies the SGW to perform corresponding processing (such as initiating the bearer establishment process), or the PGW directly initiates the bearer establishment process to establish a load for the user. Thus, the PDP PDU can be transmitted to the user via 7-load (see description in 1.1 below).

The HSS may also directly notify the SGSN to process the trigger message of the PGW. (See description in 1.2 below).

(1.1) The HSS returns a message to the PGW.

When the PGW queries the HSS for the routing information of the user, the HSS returns information such as the SGW address to the PGW, and then the PGW notifies the downstream network node, that is, the SGW, to perform corresponding processing. For example, the bearer setup process is initiated, or the bearer setup process is initiated by the PGW to establish a bearer for the user.

(1.1.1) For the case where the PGW is notified by the PGW, the description is as follows: In this case, after receiving the PDP PDU sent to a static IP address, the PGW may be based on the static IP address and/or according to the static IP. The address resolution (such as, but not limited to: the PGW holds the static IP address and the user identity or identity mapping table, index table or some other correspondence) of the user's identity (such as IMSI, or Other similar identifiers), then the PGW queries the HSS with the static IP address and/or the user identifier as an index parameter, and queries the HSS through the interface between the PGW and the HSS, and/or the user's routing information such as the SGSN or the SGW address. . When the HSS can process normally, it will return the static IP address to the PGW, and/or the user's routing information such as SGSN and/or SGW address. After receiving the message, the PGW sends a notification to the SGW, which is determined by the SGW.

At this time, the SGW may continue to send a notification to the SGSN or the MME to notify the SGSN to perform processing, or the SGW directly requests the PGW to initiate the bearer establishment process.

The SGW notifies the SGSN to process, and the SGSN notifies the UE to handle the processing. In this case, as shown in Figure 7, after receiving the notification from the PGW, the SGW will notify the SGSN to process, and after receiving the message, the SGSN continues to notify the UE to process. The UE can initiate a bearer setup procedure. The process mainly includes the following steps:

Step S701: After receiving the PDP PDU, the PGW determines whether it is required to initiate a bearer setup process, such as a PDP context activation process that initiates a network request. The PGW can store subsequently received PDP PDUs destined for the same IP address.

Step S702: The PGW may send an inquiry message, such as a Send Routing Information for GPRS message, to the HSS, where the purpose of the message is to request the HSS to query related information such as the location and/or route of the user corresponding to the static IP address. The message is sent to the HSS through an interface between the PGW and the HSS, and the carried parameter may be the static IP address, and/or user identity (such as IMSI or other similar identifier), and/or other index that can be used as an HSS query. parameter. If the HSS determines that the request can be serviced, the HSS replies to the PGW with an interface to the PGW, such as Send Routing. The information for the GPRS Ack message carries at least the SGW address and/or the SGSN address information that can serve the user, and can also carry parameter information such as the IMSI.

If the HSS decides that the request cannot be serviced (eg, the user is not known in the HSS), the HSS should reply with a reject message, such as a Send Routing Information for GPRS Ack message, which may indicate the reason for the rejection.

Step S703: If the returned message carries the SGW address, the PGW may send a notification and/or a request message, such as a PDU Notification Request message, to the SGW indicated by the HSS, where the message may carry parameters such as IMSI, PDP Type, PDP Address, APN, and the like. The SGSN Address serving the UE may be carried. The SGW may also return a response message to the PGW, such as a PDU Notification Response message or any other response cancellation step S704, the SGW sends a notification message (such as a PDU Notification Request message) and/or a request message (such as requesting an activation bearer) to the SGSN serving the UE. Wait for the message), the message can carry parameters such as IMSI, PDP Type, PDP Address, APN. The SGSN may also return a response message to the SGW, such as a PDU Notification Response message, indicating that the SGSN will request the UE to deactivate the PDP context with the indicated PDP address. If the SGW has not previously saved the address of the SGSN serving the user, the SGSN Address is carried in the message of the foregoing step S702 and step S703, so that the SGW obtains the SGSN address serving the UE.

Step S705: The SGSN requests the UE to initiate a bearer setup process. For example, the SGSN may send a Request PDP Context Activation message to the UE, where the message may carry parameters such as ΤΙ, PDP Type, PDP Address, APN, etc., to request the UE to activate the indicated PDP context. .

Step S706: Perform a bearer setup process, such as a PDP context activation process and/or a bearer setup process, according to the prior art. In the case of multiple PDNs, the UE requested PDN connectivity procedure may be invoked here to establish the payload.

The SGW is notified to the SGSN for processing, and the SGSN requests the SGW processing as an example. In this case, as shown in FIG. 8, after receiving the notification of the PGW, the SGW will notify the SGSN to process, and after receiving the message, the SGSN requests processing from the SGW. The process mainly includes the following steps: Steps S801 and S802 are the same as steps S701 and S702 shown in FIG. 7 above, and the PGW obtains an SGW address and/or an SGSN address for providing services (corresponding to its static IP address) for the UE from the HSS.

Step S803: If the returned message carries the SGW address, the PGW may send a notification and/or a request message, such as a PDU Notification Request message, to the SGW indicated by the HSS, where the message may carry parameters such as IMSI, PDP Type, PDP Address, APN, and the like. The SGSN Address serving the UE may be carried. The SGW may also return a response message to the PGW, such as a PDU Notification Response message or any other response cancellation step S804, the SGW sends a notification message (such as a PDU Notification Request message) and/or a request message (such as requesting an activation bearer) to the SGSN serving the UE. Wait for the message), the message can carry parameters such as IMSI, PDP Type, PDP Address, APN.

Step S805: The SGSN may return a notification response message, such as a PDU Notification Response message or any other response message, to the SGW as a response to the SGW, or the SGSN may send a Create Bearer Request message to the SGW, requesting the SGW to initiate a bearer setup procedure. The notification response message and the creation of the bearer request message here may be sent as two separate messages, or only one of them may be sent or the two may be combined into one message, as long as the corresponding action or effect is performed (ie, replying to the SGW) And / or request the SGW to initiate the bearer creation).

Step S806: The SGW may request the PGW to establish a bearer.

Step S807: Perform a bearer establishment process. For example, the SGW directly requests the PGW to initiate a bearer setup process. In this case, as shown in Figure 9, after receiving the notification from the PGW, the SGW will directly request the PGW to establish a bearer. The process mainly includes the following steps:

Step S901 and step S902 are the same as step S701 and step S702 shown in FIG. 7 above, and the PGW obtains an SGW address and/or an SGSN address for providing services (corresponding to its static IP address) for the UE from the HSS.

Step S903, if the returned message carries an SGW address, the PGW may send the HSS to the HSS. The instructed SGW sends a notification and/or a request message, such as a PDU Notification Request message, which may carry parameters such as IMSI, PDP Type, PDP Address, and APN, and may or may not carry the SGSN Address serving the UE.

Step S904: The SGW may return a notification response message, such as a PDU Notification Response message or any other response message, to the PGW as a response to the PGW, or the SGW may send a Create Bearer Request message to the PGW, requesting the PGW to initiate a bearer setup process. The notification response message and the create bearer request message here can be sent as two separate messages, or only one of them can be sent or the two can be combined into one message, as long as the corresponding action or effect is played (ie, the PGW is replied to) And / or request the PGW to initiate the bearer creation).

Step S905: Perform a bearer establishment process. For the PGW, the default bearer (default Bearer) of the static IP address is first established. The PDP PDU may be transmitted through the default bearer, or the PGW may initiate a dedicated bearer setup process by using the existing technology, and the PDP PDU is transmitted by using a dedicated bearer.

(1.1.2) For the case where the bearer is directly initiated by the PGW, the description is as follows: As shown in Figure 10, in this case, after receiving the PDP PDU sent to a static IP address, the PGW can be based on the static IP address. Parsing out (such a possible way of parsing includes but not limited to: the PGW holds the identity of the user (such as IMSI, or other similar identifier) corresponding to the static IP address and the mapping table, index table or other correspondence of the user identity or identity) Then, the PGW queries the HSS for the static IP address and/or the user's routing information (such as SGSN and/or SGW address, etc.) through the interface between the PGW and the HSS. When the HSS can process normally, it will return the static IP address and/or user's routing information (such as SGSN and/or SGW address, etc.) to the PGW. After receiving the message, the PGW directly initiates the bearer establishment process.

The process mainly includes the following steps

Step S1001 and step S1002 are the same as step S701 and step S702 shown in FIG. 7 above, and the PGW obtains an SGW address and/or an SGSN address for providing services (corresponding to its static IP address) for the UE from the HSS. Step S1003: Perform a bearer establishment process initiated by the PGW. For the PGW, the dedicated 7-load of the static IP address can be established here, and the PDP PDU can be transmitted by using a dedicated payload.

(1.2) The HSS directly informs the SGSN for processing.

In this case, the HSS may directly notify the SGSN serving the UE under the trigger of the PGW query message.

(1.2.1) A case where the SGSN notifies the UE to process. In this case, as shown in Figure 11, after receiving the HSS message, the SGSN notifies the UE to process. The process mainly includes the following steps:

Step S1101: After receiving the PDP PDU, the PGW determines whether a bearer setup process needs to be initiated, such as a PDP context activation process that initiates a network request. The PGW can store subsequently received PDP PDUs destined for the same IP address.

Step S1102: The PGW may send a query message, such as a Send Routing Information for GPRS message, to the HSS, the purpose of the message is to request and/or notify the HSS to query related information about the location and/or route of the user corresponding to the static IP address, and trigger The HSS sends a notification and/or request message to a control plane node that serves the user.

Step S1103: The HSS sends a message such as a notification and/or a request to the SGSN, so that the SGSN initiates bearer establishment. The parameter carried by the message may be the static IP address and/or the user identity (such as IMSI) and/or other index parameters that can be used as an HSS query, and may also carry the address of the PGW of the cached PDP PDU, PDP Type, PDP Address , APN and other parameter information. The SGSN can return a message such as a notification response or any other response message to the HSS.

Step S1104: The SGSN requests the UE to initiate a bearer setup process. For example, the SGSN may send a Request PDP Context Activation message to the UE, where the message may carry some parameters, such as a PDP Type, a PDP Address, an APN, etc., to request the UE to activate the indicated PDP context.

Step S1105: Perform a bearer setup process, such as a PDP context, according to the prior art. Activation process. In the case of multiple PDNs, the UE requested PDN connectivity procedure may be invoked here to establish a bearer.

( 1.2.2 ) The case where the SGSN requests the SGW to process. As shown in Figure 12, in this case, after receiving the message, the SGSN requests processing from the SGW. The process mainly includes the following steps:

Step S1201: After receiving the PDP PDU, the PGW determines whether a bearer setup process needs to be initiated, such as a PDP context activation process that initiates a network request. The PGW can store subsequently received PDP PDUs destined for the same IP address.

Step S1202: The PGW may send an inquiry message, such as a Send Routing Information for GPRS message, to the HSS, the purpose of the message is to request and/or notify the HSS to query related information such as the location or route of the user corresponding to the static IP address, and trigger the HSS to The control plane node serving the user sends a notification and/or request message.

Step S1203: The HSS sends a message such as a notification or a request to the SGSN, so that the SGSN initiates bearer establishment. The parameter carried by the message may be a static IP address, a user identity, such as an IMSI or any other index parameter that can be used as an HSS query, and may also carry the address of the PGW of the cached PDP PDU, SGW address, PDP Type, PDP Address, Parameter information such as APN. The SGSN may return a message such as a notification response or any other response message to the HSS.

Step S1204: The SGSN sends a message to the SGW to request to establish a bearer, and the message may carry some parameters, such as a PDP Type, a PDP Address, an APN, an address of the PGW, and the like.

Step S1205: The SGW initiates a message requesting to establish a bearer to the PGW.

Step S1206: The bearer establishment process can be performed according to the prior art. In the case of multiple PDNs, the UE requested PDN connectivity procedure may be invoked here to establish the bearer.

(2) The HSS only stores the address of the SGSN serving the UE without the SGW address.

Introducing a new interface between the PGW and the HSS; the UE passes the GERAN, When the UTRAN or E-UTRAN accesses the network, the HSS stores at least the address of the SGSN (or MME, the same below) serving the UE; when the PDP PDU arrives at the PGW and the carrier has not been established on the PGW, the PGW will Query the routing information of the user to the HSS.

The HSS may return information such as the SGSN address to the PGW. In addition, a new interface is introduced between the PGW and the SGSN (or MME, the same below). Then, the PGW notifies the downstream network node that the SGSN processes (for example, initiates a bearer setup process), or the PGW directly initiates a bearer setup process to establish a bearer for the user. Thus, the PDP PDU can be transmitted to the user via the bearer. (see 2.1 below)

The HSS may also directly notify the SGSN to process the trigger message of the PGW. (see 2.2 below)

(2.1) The HSS returns the SGSN address to the PGW.

In this case, when the PDP PDU arrives at the PGW and the user has not yet established a load on the PGW, the PGW will query the HSS for the routing information of the user. After receiving the reply message of the HSS, the PGW will notify the SGSN to process, for example, initiate a bearer setup process, or the PGW directly initiates a bearer setup process to establish a bearer for the user. Thus, the PDP PDU can be transmitted to the user via the bearer.

( 2.1.1 ) The situation notified by the PGW to the SGSN.

In this case, after the PGW receives the PDP PDU sent to a static IP address, it can be parsed according to the static IP address or according to the static IP address. (The possible ways of this analysis include but are not limited to: PGW is saved The identifier of the user corresponding to the static IP address and the mapping table, index table or other correspondence of the user identity or identifier, such as IMSI, or other such identifier, and then the PGW uses the static IP address and/or the user identifier as index parameters. The HSS (through the interface between the PGW and the HSS) queries the static IP address, and/or the user's routing information, such as the SGSN and/or SGW address. When the HSS can process normally, it will return the static IP address, and/or the user's routing information, such as the SGSN and/or SGW address, to the PGW. After receiving the message, the PGW sends a notification to the SGSN (or MME, the same below), and the SGSN decides to process it. At this time, the SGSN may continue to send a notification to the UE, requesting the UE to process, or the SGSN sends a request to the SGW or the PGW, requesting Establish a bearer.

In the case of (2.1.1), the PGW notifies the SGSN to process, and the SGSN notifies the UE of the UE as an example. As shown in Figure 13, after receiving the response message from the HSS, the PGW will notify the SGSN to process. If the SGSN can serve the UE normally, the SGSN continues to notify the UE to perform processing. The process mainly includes the following steps:

Step S1301: After receiving the PDP PDU, the PGW determines whether a bearer setup needs to be initiated, such as a PDP context activation process requested by the network. The PGW can store subsequent received PDP PDUs addressed to the same IP address.

Step S1302: The PGW may send a query message, such as a Send Routing Information for GPRS message, to the HSS, and the purpose of the message is to request the HSS to query related information about the location and/or route of the user corresponding to the static IP address. The message is sent to the HSS through the interface between the PGW and the HSS, and the parameters carried may be static IP addresses and/or user identifiers such as IMSI or any other index that can be used as an HSS query. If the HSS determines that the request can be served, the HSS replies with a response message to the GGSN through an interface between the PGW and the HSS, such as a Send Routing Information for GPRS Ack message, the message carrying at least the SGW address information that can serve the user, and It can carry parameter information such as IMSI. If the HSS holds the SGW address of the serving user, the response message may also carry the SGW address.

If the HLR decides that the request cannot be serviced, such as the user in the HSS is agnostic, the HSS should reply with a reject message, such as a Send Routing Information for GPRS Ack message, which may indicate the reason for the rejection.

Step S1303: If the returned message carries the SGSN address, the PGW may send a notification message to the SGSN indicated by the HSS, such as a PDU Notification Request message and/or a request message, such as a request to activate the message, the message may carry the IMSI, PDP Type , PDP Address, APN and other parameters. The SGSN may also return a response message to the PGW, such as a PDU Notification Response message or any other response message, indicating that the SGW will request the UE to establish a payload.

Step S1304: The SGSN requests the UE to initiate a bearer setup process, such as initiating a PDP context activation process, for example, the SGSN may send a Request PDP Context to the UE. An Activation message, which may carry parameters such as Ή, PDP Type, PDP Address, APN, etc., to request the UE to activate the indicated PDP context.

Step S1305: The bearer setup process, such as the PDP context activation process, may be performed according to the prior art. At this time, if the SGW address is carried in step S1301, the SGSN selects the SGW. In the case of multiple PDNs, the UE requested PDN connectivity procedure may be invoked here to establish a bearer. In the case of (2.1.1), the PGW notifies the SGSN to process, and the SGSN requests the PGW to process as an example. As shown in Figure 14, in this case, after receiving the response message from the HSS, the PGW will notify the SGSN to process. If the SGSN is able to provide normal service to the UE, then

The SGSN requests the PGW to process it. The process mainly includes the following steps:

Step S1401 and step S1402 are the same as steps S1301 and S1302 in FIG. 13 above, and the PGW obtains the SGSN address serving the UE from the HSS, and the SGSN corresponds to its static IP address.

Step S1403: If the returned message has an SGSN address, the PGW may send a notification and/or a request message to the SGSN indicated by the HSS, such as a PDU Notification.

The Request message and/or the request message, such as a request to activate a message, can be carried.

IMSI, PDP Type, PDP Address, APN and other parameters.

51404. The SGSN may return a notification response message, such as a PDU Notification Response message or any other response message, to the PGW as a response to the PGW, or the SGW may send a Create Bearer Request message to the PGW, requesting the PGW to initiate a bearer setup process. The notification response message and the creation of the bearer request message here can be sent as two separate messages, or only one of them can be sent or the two can be combined into one message, as long as it plays a corresponding role or effect - that is, reply The PGW also requests the PGW to initiate a create request.

51405. Perform a bearer setup process. For the PGW, the default bearer of the static IP address is first established. The PDP PDU can be transmitted through the default bearer, or the PGW can initiate a dedicated bearer setup process by using the existing technology, and the PDP PDU is transmitted by using a dedicated bearer. If it is a multi-PDN situation, it may be called here. The UE requested the PDN connectivity procedure to establish the payload. In the case of (2.1.1), the SGSN is notified by the PGW, and the SGSN requests the SGW process as an example. As shown in Figure 15, in this case, after receiving the response message from the HSS, the PGW will notify the SGSN to process. If the SGSN can serve the UE normally, the SGSN requests the SGW to process. The process mainly includes the following steps:

Step S1501 and step S1502 are the same as steps S1301 and S1302 in FIG. 13 above, and the PGW obtains the SGSN address serving the UE from the HSS, and the SGSN corresponds to the static IP address of the UE. In addition, if the HSS holds an SGW address, the HSS may also provide the SGW address to the PGW.

Step S1503: If the returned message carries the SGSN address, the PGW may send a notification message to the SGSN indicated by the HSS, such as a PDU Notification Request message and/or a request message, such as a request to activate the message, the message may carry the IMSI, PDP Type , PDP Address, APN and other parameters. If the PGW obtains the SGW address, the message may also carry the SGW address. The SGSN may return a notification response message, such as a PDU Notification Response message or any other response message, to the PGW as a response to the PGW.

Step S1504: The SGSN may send a create request message to the SGW, requesting the SGW to initiate a bearer setup process, where the message may carry parameters such as a PGW address. If the SGSN does not have the address information of the SGW before, the SGSN uses the SGW selection function and can select a suitable SGW in combination with the PGW address. If the SGSN has previously obtained the SGW address, the SGW address is applied.

Step S1505: The SGW may send a create bearer request to the PGW.

Step S1506: Perform a bearer establishment process. For the PGW, the default 7-load default Bearer for the static IP address is first established. The PDP PDU may be transmitted through the default bearer, or the PGW may initiate a dedicated bearer setup process by using the prior art, and the PDP PDU is transmitted by using a dedicated bearer. In the case of multiple PDNs, the UE requested PDN connectivity procedure may be invoked here to establish a bearer. (2.2) The HSS notifies the SGSN to process. That is, after receiving the inquiry/notification message of the PGW, the HSS will notify the SGSN to perform corresponding processing, such as initiating a bearer establishment process.

(2.2.1) The SGSN informs the UE to perform processing.

In this case, after receiving the message sent by the HSS, the SGSN notifies the UE to perform the processing. The processing at this time is similar to that described in (1.2.1) above. The difference is that the SGW address is not saved in the HSS. Therefore, when establishing a bearer, the SGSN needs to select an SGW based on the PGW address and the SGW selection principle.

( 2.2.2 ) The SGSN requests the SGW to process.

In this case, after receiving the message from the HSS, the SGSN notifies the SGW to process. The processing at this time is similar to that described in (1.2.2) above. The difference is that the SGW address is not saved in the HSS. Therefore, when establishing a bearer, the SGSN needs to select an SGW based on the PGW address and the SGW selection principle.

( 2.2.3 ) SGSN selects an SGW and informs HSS

In this case, after receiving the message sent by the HSS, the SGSN selects an SGW based on the PGW address and the SGW selection principle, and returns the address of the selected SGW to the HSS, and then returns it to the PGW by the HSS. In another application scenario of the second embodiment, no interface is introduced between the PGW and the HSS.

If a new interface is not introduced between the PGW and the HSS, when the PDP PDU sent to the static IP address reaches the PGW and the bearer has not been established for the user on the PGW, the PGW will be based on certain principles, such as network topology and/or Or route optimization and or load balancing and / or minimize migration and / or network management and / or a certain strategy, or randomly choose an SGW, and can correspond to the user's identity information (such as IMSI) and / or IP address Information is passed to the SGW. The SGW then finds the SGSN (or MME) serving the user based on the above information. Thereafter, there is sufficient context information between the UE and the network to establish the bearer.

In the above case, the PGW searches for information such as the route of the UE to the SGW and/or the SGSN as an example. As shown in Figure 16, in this case, after receiving the PDP PDU, the PGW actively searches for one or more SGW nodes if it has not yet established a load for the user, including the following steps: Steps S1601, S1602, and PGW receive After the PDP PDU, if there is no bearer for the user or no bearer information of the UE, one or more SGW nodes are actively sought. At this point, the PGW's choice of SGW may be based on certain principles such as network topology and/or route optimization and or load balancing and/or minimizing migration and/or network management and/or certain policies, etc., and/or random selection. If the SGW and the PGW are set in one, the PGW may prefer the unified SGW. In addition, the PGW may select only one or more SGWs connected thereto, or may select all SGWs connected thereto to issue notification and/or query information.

Step S1603: After receiving the foregoing search message of the PGW, the SGW directly notifies the SGSN (and/or the MME, the same below) to process; if the SGW has information about the related route of the UE, the SGW can directly inform the PGW related information (as shown in the figure). Step S 1604b)

Step S1604: After receiving the SGW notification, the SGSN continues to process the foregoing search message, and sends a bearer setup request.

Step S1605: When the SGSN continues processing, the following steps can be performed:

The SGSN notifies the UE to initiate bearer establishment;

Or the SGSN requests the SGW/PGW to establish a bearer (step S1604a in Fig. 16). If the SGW that receives the above-mentioned search message does not have the relevant information of the UE, it may continue to send a seek message and/or a notification message to the SGSN and/or the MME. At this time, the selection of the SGSN/MME by the SGW may be based on certain principles such as network topology and/or route optimization and or load balancing and/or minimizing migration and/or network management and/or a certain strategy, etc., and / or randomly selected. In addition, the SGW may select only one or more SGSNs connected to it, or may select all SGSNs/MMEs connected thereto to send notifications and/or query information.

After receiving the lookup message and/or the notification message, the SGSN and/or the MME determine whether it is the node serving the UE. If yes, continue to notify the UE to initiate the bearer setup process (such as step S1604), or directly initiate the bearer setup process, or request the SGW and/or PGW to process, such as forwarding the routing information of the UE, and/or creating a bearer, etc. S1604a). If not, the SGSN may also obtain the relevant information of the UE by querying the HSS (for the sake of simplification, the step is not marked in the figure), and continue to notify the downstream processing, such as initiating the bearer establishment process, or initiating the bearer establishment process by itself, or Request upstream (SGW and / or PGW processing, such as routing information to the UE, etc. and / or create a bearer, etc.).

Once the network has information such as the user's route, the bearer setup process will be performed (step S1605a).

In another application scenario of the second embodiment, when a UE with a static IP address has not established a bearer, if a PDP PDU corresponding to a static IP address reaches the PGW, the PGW may treat the PDP as an exception, and/or error. , or discard the PDP PDU directly.

By using the method provided by the embodiment of the present invention, the problem that the PGW cannot process the PDP PDU that may occur when the static IP address is configured is solved by using different mechanisms; Enhance system performance. In the third embodiment of the present invention, a method for obtaining and updating an SGW address by an HSS is provided.

(3.1) When the UE accesses the network - for example by attach, TAU/RAU or handover, the HSS will save the address of the SGW serving the UE.

The specific implementation may include, but is not limited to, an address update (such as update location) message carrying the address of the SGW; and a location update (such as update location) message carrying the address of the SGW in the RAU/TAU; in the attach process, the last There is update location information to the HSS for non-3GPP mobility, this message can also be used to carry the SGW's address information; or create a new message to achieve this.

For example, when the UE is attached to the network, it is sent to the HSS by the MME (or SGSN, the same below).

When the UE is attached to the network (for example, the flow shown in FIG. 4), the MME may be based on certain principles and/or manners (such as random selection, load balancing, network topology and routing, policy-based or configuration, network-based management, Select an SGW based on the APN/PGW corresponding to the static IP address, and so on. The MME passes the location update message, or any other similar The address is sent to the HSS (step S402), or by inserting a subscription data response message, or any other similar message (such as step S402), or creating a new message. The message carries the SGW address to the HSS, which will save and/or update the address.

Or, after the default bearer is established, after the MME receives the bearer update response message (step S410), if an EPS bearer is established, the MME should or if necessary (if the APN is configured with a static IP address) The HSS sends an update location message and/or any other similar message, or creates a new message containing at least the SGW address. The HSS stores and/or updates the SGW address and can send a response message to the MME (step S411).

When the UE performs TAU/RAU, the MME (and/or SGSN, the same below) sends the HSS as an example. When the UE performs the TAU/RAU, if the SGW is changed, the (new) MME (and/or the SGSN, the same below) notifies the HSS of the new SGW address, and the HSS will save the SGW address.

Take the TAU process shown in Figure 17 as an example. When a TAU occurs, if the SGW changes, the MME (if the MME changes, the new MME; if the MME has not changed, the original MME remains), the SGW address is notified to the HSS (eg, through the location update message and / or any other similar message, such as by notifying the HSS via step S1712 in Fig. 17; or by inserting a subscription data response message and/or any other similar message, i.e., notifying the HSS via step S1715 in Fig. 17, or creating another new message). The HSS will save and/or update the SGW address.

The MME (or SGSN, the same below) is sent to the HSS as an example when the handover is performed by the UE. When the UE performs Handover (whether Inter-RAT or Intra-RAT handover), if the SGW is changed, the new SGW address is notified to the HSS by the (new) MME (or SGSN, the same below), and the HSS will save the SGW address. . Or, when the UE performs TAU/RAU after the handover is completed, the SGW address is notified to the HSS by the location update procedure and the message and/or any other similar message, or another new message is created, and the HSS saves and/or updates the SGW address. .

Take the Inter-eNodeB handover procedure accompanying the SGW change as shown in FIG. 18 as an example. When a handover occurs, if the SGW changes, it is sent by the MME (if the MME sends If the change occurs, the new MME is used; if the MME has not changed, the original MME still informs the HSS of the SGW address (for example, by the location update message, that is, through step S1707 in FIG. 17 (this step is a newly created message). Notify the HSS; either by inserting the subscription data response message HSS) or by creating a new message. The HSS will save the SGW address.

(3.2) When supporting multiple PDNs, when the UE accesses multiple PDN networks, the HSS will save the address of the SGW serving the UE.

For example, when the UE is attached to the network, it is sent to the HSS by the MME (and/or SGSN, the same below). Figure 19 shows the PDN connectivity procedure requested by the UE. When connecting to multiple PDNs, the MME (if the MME changes, the new MME; if the MME has not changed, it is still the original MME) informs the HSS of the SGW address - such as by the location update message and / Or any other similar message, such as by notifying the HSS through steps S1913/S1914 in Figure 19; or by inserting a subscription data response message and/or any other similar message, or creating another new message, to the HSS. The HSS will save and/or update the SGW address.

The embodiment of the present invention provides a processing method when the APN is configured with a static IP address and a problem that the packet data gateway node may not process the packet data message when the user configures the static IP address by using different mechanisms, including the user. The method of obtaining and updating the user plane processing node address in the database. The embodiment of the present invention not only effectively solves the processing method for the APN configured with the static IP address, but also solves the problem of processing the data sent by the network to the user when the user configures the static IP address and does not establish the bearer, and also solves the problem in the user. The problem of saving and updating user plane processing nodes in the database. These not only clarify the way the network handles static IP addresses, but also enhance system performance. Embodiments of the present invention provide methods for obtaining and updating user plane processing node addresses in a user database through different mechanisms; this not only clarifies how the network handles static IP addresses, but also enhances system performance.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. Software products The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), and includes a number of instructions for making a computer device (which can be a personal computer, The server, or network device, etc.) performs the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of 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

Rights request

A method for processing a static IP address in an evolved network, comprising the steps of:

2. The method for processing a static IP address in an evolved network according to claim 1, wherein the detecting the static IP address of the corresponding access point name APN of the user includes: the static IP of the corresponding APN of the UE detected by the control entity Address, specifically:

The control entity obtains the subscription data of the UE from the user database, where the subscription data includes one or more APNs and/or one or more static IP addresses configured to allow the UE to access the static IP address; and/or

Receiving, by the control entity, a message sent by the UE, where the UE carries one or more APNs configured with a static IP address that are selected and/or bound to itself, and/or carry one or more Static IP address.

The method for processing a static IP address in an evolved network according to claim 2, wherein the control entity establishes a bearer context of the static IP address of the UE in the APN, and specifically includes:

When the default APN in the subscription data of the UE is an APN configured with a static IP address, the default APN is used to establish a default bearer; or

When the default APN in the subscription data of the UE is not an APN configured with a static IP address, an APN configured with a static IP address is selected as the default APN for default 7-carrier establishment.

The method for processing a static IP address in an evolved network according to claim 2, wherein the control entity detects that the UE has a static IP address on the APN, and further includes:

When the UE has a static IP address on the APN, the static IP address is used as an address of the default 7-load context of the APN established by the UE; or

When the UE has multiple static IP addresses on the APN, the UE may arbitrarily select or One of the static IP addresses is selected as the address of the default bearer context in which the UE establishes the APN based on a specific factor.

The method for processing a static IP address in an evolved network according to claim 2, wherein the control entity establishes a host context of the static IP address of the UE, which specifically includes:

Initiating establishment of a bearer context of the static IP address as a default bearer context; or

The bearer context for establishing the static IP address is initiated as a dedicated bearer context.

The method for processing a static IP address in an evolved network according to claim 2, wherein after the control entity detects the static IP address of the APN corresponding to the UE, the method further includes the following steps:

When the UE has a static IP address and one or more dynamic addresses corresponding to the APN, the static IP address is arbitrarily selected as the address of the UE to establish the default bearer context of the APN; or

When the UE has multiple static IP addresses and one or more dynamic addresses on the APN, the UE may arbitrarily select or select one of the static IP addresses as the default 7-load context of the APN by the UE. the address of.

The method for processing a static IP address in an evolved network according to claim 6, wherein the control entity selects a static IP address as the address of the default bearer context in which the UE establishes the APN, and specifically includes:

The control entity determines whether to use the static IP address as the lack of establishing the APN based on the UE's preference, and/or the indication of the UE, and/or the subscription information of the UE, and/or the configuration of the network, and/or the factors of the network's operational policy. The address of the saved context.

The method for processing a static IP address in an evolved network according to claim 2, wherein after the control entity detects the static IP address of the corresponding APN of the UE, the method further includes:

When the UE has a static IP address and one or more dynamic addresses, the UE selects a dynamic address as an address for establishing a default bearer context of the APN; or When the UE corresponds to the APN having multiple static IP addresses and one or more dynamic addresses, the dynamic address is selected as the address of the default bearer context of the APN.

The method for processing a static IP address in an evolved network according to claim 8, wherein the control entity selects a dynamic address as an address of a default bearer context in which the UE establishes the APN, and specifically includes:

The controlling entity determines to adopt the dynamic address as the default for establishing the APN based on the UE's preference, and/or the UE's indication, and/or the UE's subscription information, and/or the configuration of the network, and/or the factors of the network's operational policy. The address of the context.

The method for processing a static IP address in an evolved network according to claim 2, wherein the controlling entity establishes the host after the bearer context of the static IP address, and further includes:

The controlling entity sends the APN, and/or a static IP address, which is a static IP address of the default APN, to the UE; or

The controlling entity sends an APN, and/or a static IP address that is not the static IP address of the default APN to the UE.

The method for processing a static IP address in an evolved network according to claim 10, wherein the control entity sends an APN, and/or a static IP address, which is a static IP address of the default APN, to the UE. After that, it also includes:

The UE establishes a new 7-borne context using the APN and the static IP address.

12. A control entity, characterized in that

a module for detecting a static IP address of a corresponding access point name APN of the user terminal UE;

The control entity according to claim 12, wherein the module for establishing a bearer context of the user at the static IP address according to the static IP address detected by the detecting module comprises:

When the detecting module detects that the UE has one or one on the APN a plurality of static IP addresses, and/or one or more dynamic address times, arbitrarily selecting or selecting one of the static IP addresses or dynamic addresses based on a specific factor as a submodule of the UE establishing an address of the default bearer context of the APN. ;

Sending an APN, and/or a static IP address as a configuration static IP address of the default APN to the UE; or, an APN, and/or a static IP for configuring a static IP address that is not the default APN The address is sent to the sub-module of the UE.

The control entity according to claim 12, wherein the control entity is specifically:

MME and / or SGSN.

A method for processing a static IP address, comprising the steps of: receiving, by a packet data gateway node, a packet data message of a UE having a static IP address, and determining that a bearer has not been established for the UE;

The packet data gateway node interacts with a user database and a routing device in the network to establish a bearer of the UE.

The method for processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the user database stores at least an address of the user plane processing node, The step of establishing a bearer of the UE specifically includes:

The packet data gateway node queries the user database for routing information for providing services to the UE through an interface with the user database, where the routing information includes a user plane processing node address and a control plane processing node address;

Receiving, by the packet data gateway node, routing information returned by the user database, where the routing information includes a user plane processing node address and a control plane processing node;

The packet data gateway node notifies the user plane processing node to perform processing according to the routing information.

The method for processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the user database stores at least an address of the user plane processing node, , the establishment of the UE The steps included include:

The packet data gateway node obtains information from the user database through an interface with the user database.

18. The method of processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the user database stores at least an address of the user plane processing node, The step of establishing a bearer of the UE specifically includes:

And the packet data gateway node queries the user database for the user plane processing node address serving the UE and the routing information of the UE by using an interface with the user database;

Receiving, by the packet data gateway node, a user plane processing node address and routing information returned by the user database;

And the packet data gateway node notifies the user plane processing node to perform processing according to the routing information of the UE;

The user plane processing node requests the packet data gateway node to initiate a bearer setup procedure, and establishes a bearer for the UE.

19. The method of processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the user database stores at least an address of the user plane processing node, The step of establishing a bearer of the UE specifically includes:

The packet data gateway node initiates a bearer setup procedure with the UE, and establishes a bearer for the UE.

20. The method of processing a static IP address according to claim 15, wherein: When the packet data gateway node has an interface with the user database in the network, and the user database stores at least the address of the user plane processing node, the step of establishing the bearer of the UE specifically includes:

The user database sends a notification message to the UE according to the routing information of the UE; the UE requests the UE to initiate a bearer setup procedure with the packet data gateway node, and establish a bearer for the UE.

The packet data gateway node provides information to the user database through an interface with the user database;

The user database sends a notification message to the control plane processing node according to the routing information of the UE;

The control plane processing node requests a user plane processing node that provides a service for the UE to initiate a bearer setup procedure with the packet data gateway node, and establishes a bearer for the UE;

The method for processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the routing device has an interface with the packet data gateway node, The step of establishing a bearer of the UE specifically includes:

The packet data gateway node communicates with the user database to the user database Querying routing information of the UE;

The packet data gateway node receives the routing information returned by the user database; the packet data gateway node sends a notification message to the routing device through an interface with the routing device according to the routing device corresponding to the routing information;

The routing device requests the UE to initiate a bearer setup procedure with the packet data gateway node to establish a bearer for the UE.

The packet data gateway node queries the user database for routing information of the UE through an interface with the user database;

The routing device requests the packet data gateway node to initiate a bearer setup procedure, and establishes a bearer for the UE.

24. The method of processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, and the routing device has an interface with the packet data gateway node, The step of establishing a bearer of the UE specifically includes:

The routing device node selects a user plane processing node and requests the user face The node initiates the load establishment process;

The user database sends a notification message to the routing device through an interface with the routing device according to the routing device corresponding to the routing information;

The routing device requests the UE to initiate a bearer setup procedure with the packet data gateway node, and establishes a bearer for the UE.

The routing device selects a user plane processing node, and requests the user plane to process the node to initiate a bearer establishment process;

The method for processing a static IP address according to claim 15, wherein when the packet data gateway node has an interface with a user database in the network, The step of establishing a bearer of the UE, where the routing device has an interface with the packet data gateway node, specifically includes:

The routing device selects a user plane processing node, and sends information of the user plane processing node to the user database;

Sending, by the user database, information of the user plane processing node to a packet data gateway node;

The method for processing a static IP address according to claim 15, wherein when the packet data gateway node does not have an interface with a user database in the network, the step of establishing a bearer of the UE specifically includes:

The packet data gateway node selects a user plane processing node, and sends the information of the UE to the user plane processing node;

The user plane processing node acquires, according to the information of the UE, a routing device that provides services for the UE, and provides the routing device to the packet data gateway node;

A method for processing a static IP address, comprising: the following steps: the core network node detects that the UE accesses the network or connects to multiple packet data networks PDN; and the core network node obtains services for the UE The user plane processes the node address and sends it to the user database to save the user plane processing node address.

The method for processing a static IP address according to claim 29, wherein when the UE is attached to a network, the core network node acquires a service for the UE. The steps for the user plane to process the node address and send it to the user database are as follows:

Selecting a user plane processing node that provides service for the UE according to a preset policy;

The user database is notified of the address of the user plane processing node by creating a new message, or an existing message.

The method for processing a static IP address according to claim 29, wherein, when the UE performs a registration area update, the core network node acquires a user plane processing node address serving the UE and sends the address to the user. The steps of the database are specifically as follows:

During the registration area update process, it is detected that the user plane processing node serving the UE changes;

The user database is notified of the address of the new user plane processing node by creating a new message, or an existing message.

The method for processing a static IP address according to claim 29, wherein, when the UE performs handover, the core network node acquires a user plane processing node address serving the UE and sends the address to the user database. The steps are specifically as follows:

Notifying the user database of the address of the new user plane processing node by creating a new message, or an existing message; or by creating a new message, or an existing message, during the registration area update process after the switchover The address of the new user plane processing node notifies the user database.

The method for processing a static IP address according to claim 29, wherein when the UE accesses a plurality of packet data networks, the core network node acquires a user plane processing node address serving the UE. And the steps sent to the user database specifically include:

Obtaining an address of a user plane processing node that provides the service to the UE;