CN102348193B

CN102348193B - The method and system that a kind of gateway identification reports

Info

Publication number: CN102348193B
Application number: CN201010242073.3A
Authority: CN
Inventors: 毕以峰; 朱春晖
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2010-07-28
Filing date: 2010-07-28
Publication date: 2016-06-15
Anticipated expiration: 2030-07-28
Also published as: CN102348193A; WO2012013103A1

Abstract

The invention discloses a kind of method that gateway identification reports, the packet data gateway (ePDG) of evolution reports grouped data network gateway (P-GW) to identify to home subscriber server (HSS)/authentication and authorization charging server (AAA). The invention also discloses the system that a kind of gateway identification reports, this system includes reporting unit, reports P-GW to identify to HSS/AAA for ePDG. Adopt the method and system of the present invention, can access and unified operation flow process and simplification operation under the different scenes of non-3 GPP access at 3GPP.

Description

Method and system for reporting gateway identifier

Technical Field

The present invention relates to the field of communications, and in particular, to a method and system for reporting a gateway identifier in a communication network.

Background

The Evolved Packet System (EPS) of the third generation partnership project (3GPP, 3rd generation partnership project) is, as shown in fig. 1, composed of an evolved universal mobile telecommunications system terrestrial radio access network (E-UTRAN), an evolved universal mobile telecommunications system terrestrial radio access network (evolved universal terrestrial radio access network), a mobility management unit (MME), mobility management entity (mobility), a serving gateway (S-GW), a packet data network gateway (P-GW or PDNGW), a packet data network gateway (packet data network gateway), a Home Subscriber Server (HSS), a 3GPP authentication authorization accounting server (AAA), a Policy and Charging Rules Function (PCRF) entity and other support nodes. Wherein, the MME is responsible for the related work of control planes such as mobility management, the processing of non-access stratum signaling, the management of the mobility management context of a user and the like; the S-GW is an access gateway device connected to the E-UTRAN, forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data. The P-GW is a border gateway between the 3gpp ps and a Packet Data Network (PDN), and is responsible for accessing the PDN, forwarding data between the EPS and the PDN, and the like. An S6a interface is provided between the MME and the HSS, and the interface is used for operations such as user access authentication, subscription information acquisition, and context storage.

In addition to accessing to the P-GW of the EPS through the access network defined by 3GPP (e.g., the above-mentioned E-UTRAN), the User Equipment (UE) may also access through the non-3 GPP access network, that is, the P-GW is a shared gateway between the 3GPP access and the non-3 GPP access, and is an anchor point for handover of the UE between networks. Non-3 GPP access networks can be divided into trusted non-3 GPP access and untrusted non-3 GPP access, and when untrusted non-3 GPP access is performed, it must be transferred to P-GW through network element, evolved packet data gateway (ePDG), where the interface of ePDG and P-GW is called S2b interface, and the protocol that can be used by the interface includes proxy mobile IP version 6(PMIPv6, proxy mobile IP version6) protocol or general packet radio service tunneling protocol (GTP). An S6b interface is arranged between the P-GW and the AAA Server (Server)/AAA Proxy (Proxy), and the S6b interface is used for the P-GW to obtain the context information and other operations from the AAA/AAAPproxy; between the ePDG and AAAServer/AAAPproxy is SWm interface, which is used for user access authentication and other operations.

According to the prior art, whether the terminal accesses the EPS through a 3GPP access network (e.g. EUTRAN) or an untrusted non-3 GPP access network, the terminal first establishes a PDN connection through an attach operation, which is called default PDN connection, and then may also establish an Additional (Additional) PDN connection. For each PDN connection, the terminal acquires one or a pair of internet protocol version four (IPv 4)/internet protocol version six (IPv6) addresses, and the terminal visits a specific PDN through the acquired IP address. Taking the terminal accessing EPS through the untrusted non-3 GPP as an example, the following describes the operation of establishing attach/PDN connection by using a flow, as shown in fig. 2, where the flow includes the following steps:

step 201: and user UE access authentication and authorization.

Here, the ePDG, the 3gpp sss/AAA completes the authentication of the UE, and an IPsec tunnel is established between the UE and the ePDG, and the tunnel is used to protect signaling and data between the UE and the ePDG.

Here, it should be noted that: prior to step 201, the UE has completed the access operation of the non-3 GPP access network through the existing steps of the untrusted non-3 GPP access network.

Step 202: the ePDG sends a GTP: a session request message is created requesting establishment of a GTP tunnel.

Here, in fig. 2, the tunnel is established between the ePDG and the P-GW using GTP protocol, as mentioned in the description for fig. 1: the tunnel may also be established between the ePDG and the P-GW using PMIPv6 protocol, and when PMIPv6 protocol is used, the message used in step 202 to create the session request is a proxy binding update (PBU, PMIPv6binding update) message.

Step 203: if Policy and Charging Control (PCC) technology is adopted in the network to uniformly manage resources and charging, the P-GW establishes an IP-CAN session with the PCRF and obtains a PCC policy from the PCRF.

Step 204: and the P-GW reports a P-GW identification updating message to the 3 GPPHSS/AAA.

Here, the P-GW id update message carries "APN + P-GW id" corresponding to the PDN connection, and HSS/AAA stores APN + P-GW id. The "APN + P-GW identification" herein means: the APN and the P-GW identity are bound and stored in the HSS/AAA in pairs, and it can also be understood that the selected P-GW identity and the APN are correspondingly stored in the HSS/AAA, which is not described in detail.

Step 205: in response to the request signaling of step 202, the P-GW sends a "GTP: and creating a session response message to inform the ePDGGTP tunnel of successful establishment.

Here, when the tunnel is established between the ePDG and the P-GW using the PMIPv6 protocol, the reply message of step 205 is a proxy binding acknowledgement (PBA, PMIPv6binding ack) message.

Step 206: the internet protocol security (IPsec) tunnel establishment between the UE and the ePDG is complete.

Step 207: after the P-GW accepts the tunnel establishment request of the ePDG, the P-GW allocates an IP address to the UE and carries it to the ePDG through the message of step 205. In this step 207, the ePDG brings the IP address to the UE via an internet key exchange version 2(IKEv2, internet key exchange 2) message.

The user attachment is complete. After the attachment is completed, if the UE wants to establish an additional PDN connection, the above steps 201 to 207 may be performed again to establish additional PDN connections such as second and third.

In summary, the UE may establish one or more PDN connections, visiting different PDNs. However, when visiting different PDNs, the P-GW gateway selected by the EPC is different, that is, in the process of establishing a PDN connection, the ePDG selects a different P-GW (the selection mechanism is prior art) according to an Access Point Name (APN) sent by the UE or an APN returned by the HSS/AAA, so that when executing step 202 in fig. 2, the ePDG sends a tunnel binding message to the selected P-GW. Once the P-GW is selected, the identity of the P-GW and the APN need to be stored correspondingly in HSS/AAA, that is: in figure 2 the storage of the APN + P-GW identity at the HSS/AAA is achieved by step 204. The purpose of storing APN + P-GW identification is as follows: the P-GW is kept unchanged for the handover procedure. For example, after the UE is switched to the EUTRAN access from the non-3 GPP access network, the EUTRAN access does not know which P-GW the UE selects during the non-3 GPP access, so the EUTRAN access does not know which P-GW the UE should establish the tunnel binding relationship with. When UE is initially accessed through non-3 GPP, the corresponding relation between the selected P-GW identification and the APN is stored in HSS/AAA, and after the UE is switched to EUTRAN access, the EUTRAN access acquires the stored APN + P-GW identification information from the HSS/AAA through the access authentication operation of a user, so that the EUTRAN knows that the tunnel binding relation is established with the P-GW, the P-GW selected before and after switching is ensured to be the same P-GW, the P-GW of an anchor point gateway is ensured to be unchanged in the switching process, and the continuity of the service is ensured.

Analyzing the flow of fig. 2, when non-3 GPP accesses, the APN + P-GW id storage is reported from P-GW to HSS/AAA through S6b interface. Unlike the operation of UE accessing through EUTRAN, the P-GW does not need to perform the operation when accessing EUTRAN, and the storage of APN + P-GW identification is reported to HSS/AAA by other network elements, such as MME. That is, under different scenarios of 3GPP access and non-3 GPP access, different requirements are put forward on the behavior of P-GW, and when the APN + P-GW identifier is reported to HSS/AAA for storage, different network elements are used to perform reporting, so that the operation flow is chaotic and non-uniform.

Disclosure of Invention

In view of this, the main objective of the present invention is to provide a method and a system for reporting a gateway identifier, which can unify operation flows and simplify operations in different scenarios of 3GPP access and non-3 GPP access.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

a method for reporting gateway identification includes:

an evolved packet data gateway (ePDG) reports a packet data network gateway (P-GW) identifier to a Home Subscriber Server (HSS)/authentication authorization accounting server (AAA).

Wherein, when a user initial attach/Packet Data Network (PDN) connection is established, the method further comprises:

the ePDG reports a P-GW identification updating message to the HSS/AAA, and the HSS/AAA stores the P-GW identification after receiving the P-GW identification; wherein, the P-GW id update message carries the P-GW id.

Wherein the condition for triggering the ePDG to report includes any one of the following conditions:

condition 1: initiating User Equipment (UE) access authentication and authorization, in the process of UE access authentication and authorization, or after the UE access authentication and authorization is completed, the ePDG reporting the P-GW identification update message;

condition 2: initiating a P-GW to inform an ePDG of establishment of a general packet radio service tunneling protocol (GTP) tunnel, informing the P-GW of establishment of the ePDGGTP tunnel, or informing the P-GW of completion of establishment of the ePDGGTP tunnel, and reporting the P-GW identification update message by the ePDG;

condition 3: initiating internet protocol security (IPsec) tunnel establishment between the UE and the ePDG, in the IPsec tunnel establishment process between the UE and the ePDG, or after the IPsec tunnel establishment between the UE and the ePDG is completed, the ePDG reports the P-GW identification update message.

Wherein, when the user switches to the access network where the ePDG is located, the method further comprises: and when the ePDG executes the user access authentication operation, the ePDG requests to acquire the P-GW identification stored by the HSS/AAA before the switching from the HSS/AAA.

When the user detach/PDN connection is released, the method further comprises the following steps: and the ePDG reports a P-GW identification updating message to the HSS/AAA, and the HSS/AAA deletes the stored P-GW identification after receiving the P-GW identification updating message.

When the UE/non-3 GPP access network/ePDG initiates the detach, the condition for triggering the ePDG to report includes any one of the following conditions:

condition 1: initiating the release of an internet key exchange version 2(IKEv2) tunnel, the release process of an IKEv2 tunnel or the release of an IKEv2 tunnel, and reporting the P-GW identification updating message by the ePDG;

condition 2: initiating a P-GW to inform an ePDG to release a GTP tunnel, in the process of informing the ePDG to release the GTP tunnel by the P-GW, or after informing the ePDG to release the GTP tunnel by the P-GW, reporting the P-GW identification updating message by the ePDG;

condition 3: and initiating a non-3 GPP access network to release resources through the existing resource release operation, and after the non-3 GPP access network releases the resources through the existing resource release operation or the non-3 GPP access network releases the resources through the existing resource release operation, the ePDG reports the P-GW identification update message.

Wherein the P-GW identification update message comprises: the P-GW identification storage request message, the P-GW identification acquisition request message or the P-GW identification deletion request message.

A system for reporting gateway identification comprises a reporting unit, which is used for ePDG to report P-GW identification to HSS/AAA.

The reporting unit is further configured to, when a user initial attach/PDN connection is established, report a P-GW identifier update message to the HSS/AAA by the ePDG, where the P-GW identifier update message carries a P-GW identifier;

the system also comprises a storage unit used for storing the P-GW identification after the HSS/AAA receives the P-GW identification.

The system further comprises an obtaining unit, configured to, when the user is handed over to the access network where the ePDG is located, the ePDG performs a user access authentication operation to request to obtain, from the HSS/AAA, the P-GW identity stored by the HSS/AAA before the handover.

The reporting unit is further configured to report, by the ePDG, a P-GW identifier update message to the HSS/AAA when the user detach/PDN connection is released;

the system also comprises a deleting unit used for deleting the P-GW identification stored by the HSS/AAA after the HSS/AAA receives the P-GW identification updating message.

The ePDG reports the P-GW identification to the HSS/AAA.

By adopting the invention, the ePDG reports the P-GW identification to the HSS/AAA uniformly, and the operation flow can be unified and the operation can be simplified under different scenes of 3GPP access and non-3 GPP access.

Drawings

Fig. 1 is a schematic diagram of an untrusted non-3 GPP access network accessing EPS in the prior art;

fig. 2 is a schematic attachment flow diagram of P-GW id storage in the prior art;

FIG. 3 is a schematic flow chart of a first implementation of the method of the present invention;

FIG. 4 is a schematic flow chart of a second implementation of the method of the present invention;

fig. 5 is a schematic flow chart of the third implementation of the method of the present invention.

Detailed Description

The basic idea of the invention is: and the ePDG reports the P-GW identification to the HSS/AAA.

The following describes the embodiments in further detail with reference to the accompanying drawings.

The scheme of the invention is suitable for the scene of non-3 GPP access, and the ePDG reports the P-GW identification to the HSS/AAA. The subsequent HSS/AAA stores the received P-GW identification, the ePDG acquires the stored P-GW identification from the HSS/AAA, or the HSS/AAA deletes the stored P-GW identification under the request of the ePDG.

A method for reporting gateway identification mainly comprises the following steps:

and uniformly reporting the P-GW identification to the HSS/AAA by the ePDG.

Further, when the user initial attach/PDN connection is established, the ePDG may report a P-GW identifier update message to the HSS/AAA via the SWm interface, request the HSS/AAA to store the P-GW identifier, and the HSS/AAA may store the received P-GW identifier during the lifetime of the PDN connection. Wherein, the P-GW identification update message carries the P-GW identification.

Further, when the user is switched, the ePDG obtains the P-GW identification stored by the HSS/AAA before the switching from the HSS/AAA through the user access authentication operation.

Further, when the user detach/PDN connection is released, the ePDG requests the HSS/AAA to delete the P-GW identification, and the HSS/AAA deletes the P-GW identification.

Here, it should be noted that: and when the PDN connection deletion/resource deactivation initiated by the P-GW for the switching reason is carried out, the ePDG does not request the HSS/AAA to delete the P-GW identification.

The invention is illustrated below.

Description of the drawings: in the following embodiments, the "P-GW id update message" used is a general message name, which may specifically include: the P-GW identification storage request message, the P-GW identification acquisition request message or the P-GW identification deletion request message. The message may be assumed by a special indication carried by the Diameter signaling, as long as the HSS/AAA can analyze the parameters carried by the message and can execute the operation (storing/deleting/acquiring the P-GW id) according to the operation indicated by the message, and the message name is not specifically limited.

The first embodiment of the method comprises the following steps: the P-GW identifies the stored attach/PDN connection establishment procedure.

In this embodiment, according to the present invention, a terminal is attached to an EPS core network through an untrusted non-3 GPP access network; or after the attach, the procedure of attaching the PDN connection is established, and in the attach/PDN connection establishment procedure, the ePDG sends a P-GW identifier update message to the HSS/AAA, where the message carries the P-GW identifier, and the HSS/AAA stores the P-GW identifier, as shown in fig. 3. Fig. 3 shows a non-roaming scenario, which differs from fig. 3 in that: the interaction between the P-GW and the policy and charging rules function (hPCRF) of the home location is transferred through the policy and charging rules function (vPCRF) of the visited location of the visited network; the interaction of the ePDG and home HSS/AAA is transferred through AAAPproxy of the visiting network. The differences here do not affect the invention.

The process shown in fig. 3 includes the following steps:

step 301: and user UE access authentication and authorization.

Here, it should be noted that: prior to step 301, the UE has completed access operations to the non-3 GPP access network through existing steps of the untrusted non-3 GPP access network.

Step 302: in the IPsec tunnel establishment process, the UE may carry the APN to the ePDG, or the AAA may issue the APN for subscription to the ePDG during authentication. And the ePDG selects the P-GW to be accessed for establishing the PDN connection according to the APN through the existing mechanism (such as DNS query). The ePDG sends a P-GW identification updating message to the HSS/AAA through the SWm interface, and requests the HSS/AAA to store the P-GW identification.

The P-GW identity update message trigger condition or execution opportunity of step 302 may be any one of the following:

condition 1: triggered by step 301, i.e. step 302 occurs after step 301, as shown in fig. 3;

condition 2: triggered by step 305, i.e. step 302 occurs after step 305, not disclosed in fig. 3;

condition 3: triggered by step 306, i.e., step 302 occurs after step 306, not disclosed in fig. 3.

Of course, as a processing of failure exception, if the P-GW identity update is executed after step 301 and step 305, and the subsequent attach/PDN connection establishment fails, the ePDG sends a P-GW identity update request to the HSS/AAA, requesting the HSS/AAA to delete the stored P-GW identity.

Because different APNs identify different PDNs, and different PDNs need to be accessed through different P-GWs (which may be the same P-GW in some scenarios), when the ePDG sends a P-GW identity update message to the HSS/AAA, the APN and the P-GW identity are sent in pairs, and the HSS/AAA stores the message in pairs.

Step 303: the ePDG sends "GTP: a session request message is created requesting establishment of a GTP tunnel.

Here, the tunnel is established between the ePDG and the P-GW in fig. 3 using GTP protocol, as mentioned in the description for fig. 1: the tunnel may also be established between the ePDG and the P-GW using PMIPv6 protocol, and when PMIPv6 protocol is used, the message used in step 303 to create the session request is a PBU message.

Step 304: if the PCC technology is adopted in the network to uniformly manage resources and charge, the P-GW establishes an IP-CAN session with the PCRF and acquires a PCC policy from the PCRF.

Step 305: in response to the request signaling of step 303, the P-GW sends a "GTP: and creating a session response message to inform the ePDGGTP tunnel of successful establishment.

Here, when the tunnel is established between the ePDG and the P-GW using the PMIPv6 protocol, the reply message of step 305 is a PBA message.

Step 306: and the IPsec tunnel establishment between the UE and the ePDG is completed.

Step 307: after the P-GW accepts the tunnel establishment request of the ePDG, the P-GW allocates an IP address to the UE and carries it to the ePDG through the message of step 305. In this step 307, the ePDG brings the IP address to the UE by IKEv2 message.

The user attachment is complete. Likewise, when the user completes the attachment, if an additional PDN connection needs to be established, the above steps 301 to 307 may be performed again to establish additional PDN connections such as second, third.

The second method embodiment: and the P-GW identifies the deleted PDN connection release/detachment flow initiated by the UE/ePDG/non-3 GPP access network.

In this embodiment, according to the present invention, after a terminal attaches to an EPS core network through an untrusted non-3 GPP access network (after the attachment, one or several additional PDN connections may be established, or none may be established), a procedure of detach/PDN connection release is initiated by a UE, an ePDG, or a non-3 GPP access network. The PDN connection release refers to that the UE has multiple PDN connections, one or several of the PDN connections need to be disconnected, but the UE maintains the remaining PDN connections, so the UE does not detach from the network. In the detach/PDN connection release process, the ePDG sends a P-GW identity update message to the HSS/AAA, and after receiving the message, the HSS/AAA deletes the P-GW identity, as shown in fig. 4. Fig. 4 shows a non-roaming scenario, which differs from fig. 4 in that: the interaction between the P-GW and the hPCRF is transferred through the vPCRF of the visited network; the interaction of the ePDG and home HSS/AAA is transferred through AAAPproxy of the visiting network. The differences here do not affect the invention.

The process shown in fig. 4 includes the following steps:

step 401: the user UE initiates a detach operation, either the non-3 GPP access network or the ePDG, triggering the release of the IKEv2 tunnel.

Step 402: in this embodiment, the ePDG sends a P-GW id update message to the HSS/AAA through the SWm interface, requesting the HSS/AAA to delete the P-GW id, and the HSS/AAA is triggered to delete the P-GW id.

The trigger condition or execution timing of step 402 may be any one of the following:

condition 1: triggered by step 401, i.e. step 402 occurs after step 401, as shown in fig. 4;

condition 2: triggered by step 405, i.e. step 402 occurs after step 405, not disclosed in fig. 4;

condition 3: triggered by step 406, i.e., step 402 occurs after step 406, not disclosed in fig. 4.

Of course, as a processing of failure exception, if the P-GW identity update (deletion) is executed after steps 401 and 405 and the subsequent detach operation fails, the ePDG will send a P-GW identity update (storage) request to the HSS/AAA again, requesting the HSS/AAA to store the P-GW identity again.

Step 403: the ePDG sends "GTP: and deleting the session request message to request to tear down the GTP tunnel.

Here, the tunnel is established between the ePDG and the P-GW in fig. 4 using GTP protocol, as mentioned in the description for fig. 1: the tunnel may also be established between the ePDG and the P-GW by using PMIPv6 protocol, and when PMIPv6 protocol is used, the message of step 402 is a PBU message for creating a session request, and the lifetime is set to zero, specifically, "PMIPv 6binding update (lifetime is 0)".

Step 404: if PCC technology is adopted in the network to uniformly manage resources and charging, the P-GW and the PCRF terminate the IP-CAN session.

Step 405: in response to the request signaling of step 403, the P-GW sends "GTP: and deleting the session response message to inform the ePDG to release the GTP tunnel.

Here, when the tunnel is established between the ePDG and the P-GW using the PMIPv6 protocol, the reply message of step 405 is a PBA message.

Step 406: the non-3 GPP access network releases resources through the existing resource release operation steps.

As above for detach, also when the user initiates the PDN connection release, the procedure is similar to the above steps 401 ~ 406.

The third method embodiment: and the P-GW identifies the deleted PDN connection release/resource deactivation flow initiated by the P-GW/PCRF.

In this embodiment, according to the present invention, after a terminal attaches to an EPS core network through an untrusted non-3 GPP access network, one or more additional PDN connections are established, and a PCRF or a P-GW initiates a resource deactivation/PDN connection release procedure. In the process of resource deactivation/PDN connection release, the ePDG sends a P-GW identity update message to the HSS/AAA, and after receiving the message, the HSS/AAA deletes the P-GW identity, as shown in fig. 5. Fig. 5 shows a non-roaming scenario, which differs from fig. 5 in that: the interaction between the P-GW and the hPCRF is transferred through the vPCRF of the visited network; the interaction of the ePDG and home HSS/AAA is transferred through AAAPproxy of the visiting network. The differences here do not affect the invention.

The process shown in fig. 5 includes the following steps:

step 501: the PCRF will initiate termination/modification operation of the IP-CAN session and inform the P-GW to delete/deactivate the resources of a certain PDN connection.

Here, this step is an optional step.

Step 502: the P-GW sends "GTP: delete bearer request message requesting to tear down the relevant bearer.

In fig. 5, the ePDG and the P-GW establish a tunnel using GTP protocol, as mentioned in the description for fig. 1: a tunnel may also be established between the ePDG and the P-GW by using a PMIPv6 protocol, and when a PMIPv6 protocol is used, the message used in step 502 for deleting the bearer request is a Binding Revocation Indication (BRI) message.

Step 503: the non-3 GPP access network releases related resources, and if all resources of the PDN connection are triggered to be released, IKEv2 tunnel release between the UE and the ePDG is also triggered to be released.

Step 504: when the PDN connection is released due to resource deactivation, the ePDG sends a P-GW identification updating message to the HSS/AAA through the SWm interface, requests the HSS/AAA to delete the P-GW identification, and the HSS/AAA is triggered to delete the P-GW identification.

The trigger condition or execution timing of step 504 may be any one of the following:

condition 1: triggered by step 502, i.e., step 504 occurs after step 502, not disclosed in FIG. 5;

condition 2: triggered by step 503, i.e. step 504 occurs after step 503, as shown in fig. 5.

Of course, as a processing of failure exception, if the P-GW identity update (deletion) is performed after step 502, and the subsequent resource deactivation/PDN connection release operation fails, the ePDG will send a P-GW identity update (storage) request to the HSS/AAA again, requesting the HSS/AAA to store the P-GW identity again.

Step 505: in response to the step 502 request signaling, the ePDG sends a "GTP: the bearer reply message is deleted.

Here, when the tunnel is established between the ePDG and the P-GW using the PMIPv6 protocol, the message used in step 505 for deleting the bearer response is a binding withdrawal acknowledgement (BRA) message.

Step 506: IP-CAN session termination/modify response.

A system for reporting gateway identification comprises a reporting unit, wherein the reporting unit is used for an ePDG to report a P-GW identification to an HSS/AAA.

Here, in the case of requesting to store the P-GW identifier, the reporting unit is further configured to, when the initial attach/PDN connection of the user is established, report the P-GW identifier update message to the HSS/AAA by the ePDG, and request the HSS/AAA to store the P-GW identifier; wherein, the P-GW identification updating message carries the P-GW identification.

The system also comprises a storage unit, wherein the storage unit is used for storing the P-GW identification after the HSS/AAA receives the P-GW identification.

Here, in the case of requesting to acquire the P-GW identifier, the system further includes an acquiring unit, configured to, when the user is handed over to the access network where the ePDG is located, the ePDG performs a user access authentication operation to request to acquire, from the HSS/AAA, the P-GW identifier stored by the HSS/AAA before the handover.

Here, when the reporting unit is further used for user detach/PDN connection release when requesting to delete the P-GW identifier, the ePDG reports a P-GW identifier update message to the HSS/AAA, requesting the HSS/AAA to delete the stored P-GW identifier.

The system also comprises a deleting unit which deletes the P-GW identification stored by the HSS/AAA after the HSS/AAA receives the P-GW identification updating message.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method for reporting a gateway identifier is characterized in that the method comprises the following steps:

when a user initial attachment/Packet Data Network (PDN) connection is established, an evolved packet data gateway (ePDG) reports a packet data network gateway (P-GW) identifier update message to a Home Subscriber Server (HSS)/an authentication authorization accounting server (AAA), and the HSS/AAA stores the P-GW identifier after receiving the P-GW identifier; the P-GW identification updating message carries the P-GW identification;

2. The method of claim 1, wherein when a user switches to an access network in which the ePDG is located, the method further comprises: and when the ePDG executes the user access authentication operation, the ePDG requests to acquire the P-GW identification stored by the HSS/AAA before the switching from the HSS/AAA.

3. The method of claim 1, wherein when the user detach/PDN connection is released, the method further comprises: and the ePDG reports a P-GW identification updating message to the HSS/AAA, and the HSS/AAA deletes the stored P-GW identification after receiving the P-GW identification updating message.

4. The method of claim 3, wherein the condition for triggering the ePDG report when the UE/non-3 GPP access network/ePDG initiates the detach includes any one of the following conditions:

5. The method of claim 3 or 4, wherein the P-GW identification update message comprises: the P-GW identification storage request message, the P-GW identification acquisition request message or the P-GW identification deletion request message.

6. A gateway identification reporting system is characterized in that the system comprises a reporting unit and a storage unit; wherein,

the reporting unit is used for reporting a packet data network gateway P-GW identification updating message to a Home Subscriber Server (HSS)/an authentication authorization accounting server (AAA) by an evolved packet data gateway (ePDG) when a user initial attachment/Packet Data Network (PDN) connection is established, wherein the P-GW identification updating message carries a P-GW identification;

the storage unit is configured to store the P-GW id after the HSS/AAA receives the P-GW id;

condition 1: initiating UE access authentication and authorization, and reporting the P-GW identification updating message by the ePDG in the process of UE access authentication and authorization or after the UE access authentication and authorization is completed;

condition 2: initiating a P-GW to inform ePDGGTP tunnel establishment, informing the P-GW to inform the ePDGGTP tunnel establishment, or informing the P-GW to report the P-GW identification updating message after the ePDGGTP tunnel establishment is completed;

condition 3: initiating IPsec tunnel establishment between UE and the ePDG, in the process of establishing the IPsec tunnel between the UE and the ePDG, or after the IPsec tunnel establishment between the UE and the ePDG is completed, the ePDG reports the P-GW identification update message.

7. The system of claim 6, further comprising an obtaining unit, configured to, when the user is handed over to an access network where the ePDG is located, perform a user access authentication operation by the ePDG, and request to obtain, from the HSS/AAA, a P-GW identity stored by the HSS/AAA before the handover.

8. The system of claim 6, wherein the reporting unit is further configured to report, when the user detach/PDN connection is released, the ePDG reports a P-GW identity update message to the HSS/AAA;