Background
Currently, the standardization work group of the third Generation Partnership Project (3rd Generation Partnership Project, abbreviated as 3GPP) is working on the next Generation Evolved Core network system to be an Evolved Packet Core (EPC), which aims to provide users with higher transmission rate and shorter transmission delay.
The EPC system supports access of a non-3GPP (non-3GPP) radio access network. Fig. 1 is a schematic diagram of a non-3GPP radio access Network accessing a Home public land Mobile Network (Home PLMN, abbreviated as HPLMN) through a Visited Public Land Mobile Network (VPLMN), as shown in fig. 1, where the Network elements included therein include: a Packet Data Network Gateway (P-GW), which is responsible for a Gateway function of a User Equipment (UE) accessing a PDN (Packet Data Network); and the Home Subscriber Server (HSS) is positioned in a Home network of the user and is used for permanently storing the subscription data and the security data of the user.
In order to support the non-3GPP access network to access the EPC, the system also comprises an Authentication, Authorization and Accounting (AAA Server) and an AAA Proxy (AAA Proxy).
The non-3GPP access network is not a 3GPP standardized access technology, wherein the non-3GPP access network comprises: wireless Local Area Network (WLAN), Worldwide Interoperability for Microwave Access (WIMAX), Code Division Multiple Access (CDMA), and fixed broadband Access. Specifically, non-3GPP access networks can be classified into the following two types:
a Trusted non-3GPP Access network (Trusted non 3GPP Access) has a trust relationship between a 3GPP network and the non-3GPP Access system, and the non-3GPP Access system can directly Access a P-GW through S2 a.
An Untrusted non-3GPP Access (untrunted non 3GPP Access), there is no trust relationship between the 3GPP network and the non-3GPP Access network, and the non-3GPP Access system must first Access an Evolved packet data Gateway (ePDG for short) of the 3GPP network, and then Access the P-GW through an interface S2b between the ePDG and the P-GW (S2b is an interface between the ePDG and the P-GW). In this case, a secure tunnel is established between the UE and the ePDG, so that data transmission between the UE and the 3GPP network can be secured.
The chained connection mode is a connection mode in which the UE is connected to a P-GW of the HPLMN through a non 3GPP Access and then through a Serving Gateway (S-GW) in the VPLMN when roaming. Specifically, fig. 2 is a flowchart of a chain connection method, as shown in fig. 2, which mainly includes the following steps:
step 201: AAA Proxy decides to adopt chain connection mode when user access authentication and authorization, when AAA Proxy decides to adopt the connection mode, AAAPproxy selects an S-GW in VPLMN and a P-GW in HPLMN, and sends the S-GW and P-GW addresses selected by AAA Proxy to a trusted non 3GPP access network or ePDG in the authentication process, and the trusted non 3GPP access network or ePDG stores the addresses;
step 202: the trusted non 3GPP Access network or ePDG has a Mobile Access Gateway (MAG) function, and sends Proxy Binding Update message (PBU) to the S-GW, wherein the address of the P-GW is contained in the reasonable Binding Update message;
steps 203 and 204: after receiving the message, the S-GW establishes a GPRS Tunnel Protocol (GTP) Tunnel connection with the P-GW, wherein the Tunnel connection comprises a Tunnel of a user plane (GTP-U) and a Tunnel of a control plane (GTP-C);
step 205: after the GTP tunnel connection between the S-GW and the P-GW is established, the S-GW sends Proxy Binding Acknowledgement (PBA) to the MAG to complete the establishment of a Proxy Mobile IP sixth edition (Proxy Mobile IPv6, PMIPv6) tunnel between the MAG and the S-GW;
step 206: the MAG informs the UE of the configuration information required by the UE.
In the PMIPv6 protocol, in order to prevent the UE from colliding with a link Local address (link address) of the MAG, a Local Mobility Anchor (LMA) allocates an Interface identifier (Interface ID) to the UE, and the UE generates the link Local address by using the Interface identifier; the MAG uses the link-local address assigned to it by the LMA. The UE interface identification and the MAG link local address are both sent to the MAG by the LMA in a proxy binding acknowledgement message (PBA), and the UE interface identification is sent to the UE by the MAG.
The link local address refers to an address used for communication between nodes on the local connection, and cannot be used on a link other than the local connection, and in the above procedure, the link is a link between the UE and the P-GW (when only a GTP tunnel is used between the UE and the P-GW, and no PMIPv6 tunnel is used) or between the UE and the MAG (PMIPv 6). And the user address is an IPv6 global address, can be globally unique or site unique, and can be used for global communication or intra-site communication, wherein the site refers to an operator network.
In a GTP protocol, in order to prevent conflict with a link local address of UE, the P-GW allocates an interface identifier for the UE and sends the interface identifier to the UE when the process that the UE initially accesses a network is completed, and the UE generates the link local address by using the interface identifier; the P-GW informs the UE of the IPv6 address prefix allocated to the P-GW by using a route advertisement (Router advertisement), wherein the source address of the route advertisement is the link local address of the P-GW. Because the link local address of the P-GW and the interface identification of the UE are generated by the P-GW allocation, the link local addresses of the P-GW and the UE can be ensured not to conflict.
In the prior art, when using a chained connection, as shown in fig. 2, the P-GW sends its link local address to the S-GW in a GTP-C message in step 204, and the S-GW sends the link address to the MAG (which may be a trusted non-3GPP access gateway or ePDG) in a PBA, and the MAG uses the link local address on the local connection with the UE. Since the method needs to extend the GTP-C message in step 204 and needs to have an interface between the S-GW and the P-GW to support the GTP-C message, the existing interface needs to be extended, thereby increasing the requirements for the interfaces of the S-GW and the P-GW, increasing the cost and complexity of implementation.
Detailed Description
Overview of the function
The embodiment of the invention aims at the problems that when the chain connection mode is adopted in the prior art, the local address of the link needs to be sent to the S-GW through the GTP-C message, thereby causing a problem of large influence on the S-GW and P-GW interfaces, an improved chain connection establishment scheme is proposed, in the embodiment of the invention, after receiving the request for establishing the default bearer sent by the S-GW, P-GW sends route advertisement through built GTP-U, S-GW receives the route advertisement, resolves and acquires source link local address of the route advertisement, and then the S-GW sends the source link local address to a trusted non-3GPP access gateway or an ePDG in a proxy binding confirmation message, and the trusted non-3GPP access gateway or the ePDG takes the source link local address as the link local address of the trusted non-3GPP access gateway or the ePDG to carry out local link communication with the UE.
The embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
According to the embodiment of the invention, firstly, a chain connection establishment method is provided, and the method is used for connecting the UE to the P-GW of the HPLMN through the trusted non-3GPP access network or ePDG and then through the S-GW of the VPLMN when the UE roams.
Fig. 3 is a flowchart of a method for establishing a chain connection according to an embodiment of the present invention, and as shown in fig. 3, the method for establishing a chain connection according to an embodiment of the present invention mainly includes (step S301-step S303):
step S301: S-GW receives the route announcement of the route announcement sent by P-GW through the built GTP-U, analyzes and acquires the source link local address of the route announcement;
step S303: and the S-GW carries the source link local address in a proxy binding confirmation message and sends the proxy binding confirmation message to a trusted non-3GPP access gateway or ePDG so that the trusted non-3GPP access gateway or ePDG uses the source link local address to carry out local link communication with the UE on a local link between the trusted non-3GPP access gateway and the UE.
Details of each of the above-described processes are further described below.
Step S301
In the specific implementation process, when a UE accesses an IP service provided by an HPLMN through a trusted non-3GPP access network or an ePDG, an AAA Proxy determines whether to adopt a chain connection mode when the UE accesses authentication and authorization, if the AAA Proxy determines to adopt the chain connection mode, the AAA Proxy selects an S-GW in a VPLMN and a P-GW in the HPLMN, and sends addresses of the selected S-GW and the P-GW to the trusted non-3GPP access network or the ePDG in the authentication process, the trusted non-3GPP access network or the ePDG stores the addresses, and because the trusted non-3GPP access network or the ePDG has a MAG function, the trusted non-3GPP access network or the ePDG is used as a MAG to send a binding update message to the selected S-GW, the Proxy binding update message carries the address of the selected P-GW, and after the S-GW receives the Proxy binding update message, and sending a request for establishing the default bearer to the P-GW.
After receiving the request for establishing the default bearer, the P-GW establishes a downlink GTP tunnel (comprising GTP-C and GTP-U) (from the P-GW to the S-GW), and after establishing the downlink GTP tunnel, the P-GW sends a route notification to the S-GW in the established GTP-U tunnel and replies an S-GW response for establishing the default bearer in the GTP-C tunnel.
In the implementation, after the GTP-C and GTP-U tunnels are established, sending the route advertisement to the S-GW includes, but is not limited to, the following two methods:
the first method comprises the following steps: after establishing the GTP tunnel, the P-GW periodically sends a route notification to the S-GW;
and the second method comprises the following steps: after receiving a route request (Routersolicitation) sent by the S-GW, the P-GW sends the route advertisement to the S-GW.
These two methods are described separately below.
First method
In the method, after receiving a request for establishing a default bearer from an S-GW, a P-GW periodically sends a route passing to the S-GW through an established downlink GTP tunnel, and the periodic route announcement and the sending of the response for establishing the default bearer have no time sequence.
After receiving the route advertisement, the S-GW may have the following two cases according to the different receiving order of the default bearer establishment response and the periodic route advertisement:
in the first situation, S-GW receives the response of establishing default load from P-GW, then waits for the periodic route announcement sent by P-GW, and when receiving the periodic route announcement, analyzes and acquires the source link local address in the periodic route announcement;
in the second case, the S-GW receives the periodic route advertisement first, and the S-GW parses and acquires the source link local address in the periodic route advertisement, and waits to receive a response for establishing a default bearer.
Second method
In the method, after establishing a downlink GTP tunnel, a P-GW sends a response for establishing a default bearer to an S-GW through a GTP-C, the response for establishing the default bearer carries an interface identifier of UE, the S-GW generates a source link address according to the interface identifier and sends a routing request to the P-GW according to the source link address, and after receiving the routing request, the P-GW sends the routing notification to the S-GW through the established GTP-U tunnel.
In this method, if the S-GW does not receive the route advertisement sent by the P-GW within a preset time period after sending the route request, the S-GW may send the route request to the P-GW again, and the P-GW sends the route request to the S-GW again through the established GTP-U tunnel after receiving the route request, so that unnecessary route advertisements caused by the P-GW periodically sending the route advertisement may be reduced.
In order to avoid the influence of the route advertisement on the UE, and because the MAG is an access router of the UE and is responsible for communication of a local link between the UE and the network, the IP address and other parameters of the UE are configured, and the S-GW does not need to send a route advertisement message to the MAG, corresponding to the two route advertisement sending methods, after receiving the route advertisement, the S-GW may have the following two optimization processing methods:
a first mode, corresponding to the first method, where the S-GW intercepts the received route advertisement, and discards the route advertisement packet without sending the route advertisement packet to the MAG after acquiring the source link local address, and the S-GW may continue to detect the route advertisement sent by the P-GW through the GTP-U tunnel, and no longer acquire the source link local address of the route advertisement and discard the route advertisement packet at the same time, or the S-GW no longer detects the route advertisement periodically sent by the P-GW after acquiring the source link local address.
In a second manner, corresponding to the second method, the S-GW intercepts the received route advertisement, discards the packet of the route advertisement after acquiring the source link local address, and does not send the route request to the P-GW any more, so that the P-GW does not send the route advertisement to the S-GW any more.
(II) step S303
In a specific implementation process, after acquiring a source link local address of a route advertisement sent by a P-GW, an S-GW carries the source link local address in a proxy binding acknowledgement message and sends the proxy binding acknowledgement message to a trusted non-3GPP access gateway or ePDG (i.e., MAG).
And after receiving the proxy binding confirmation message, the trusted non-3GPP access gateway or ePDG (namely MAG) performs local link communication with the UE on a local link between the UE and the trusted non-3GPP access gateway or ePDG by using the source link local address as the own link local address.
For further understanding of the above-mentioned chain connection establishing method provided in the embodiment of the present invention, a specific implementation process of the chain connection establishing method provided in the embodiment of the present invention is described below by taking the first method as an example to send the route advertisement.
Fig. 4 is a flowchart of a specific implementation of a method for establishing a chained connection according to an embodiment of the present invention, and as shown in fig. 4, the method for establishing a chained connection according to an embodiment of the present invention may be implemented by the following steps:
step 401, the UE accesses to a trusted non-3GPP Access network or ePDG, when authenticating and authorizing the UE, the AAA Proxy decides to use a chain connection, the AAA Proxy selects an S-GW in a VPLMN and a P-GW in an HPLMN, and sends the addresses of the S-GW and the P-GW selected by the AAA Proxy to a trusted non 3GPP Access or ePDG during the authentication process, and the trusted non 3GPP Access or ePDG stores the addresses;
step 402, trusted non 3GPP Access or ePDG (as MAG specified in PMIPv6 protocol) sends proxy binding update message (PBU) to S-GW, where the proxy binding update message carries the address of P-GW and an indication of GTP usage between S-GW and P-GW;
step 403, after receiving the proxy binding update message sent by the trusted Non 3GPP Access or ePDG, the S-GW sends a request for establishing a default bearer to the P-GW;
step 404, the P-GW replies to the S-GW in the GTP-C tunnel to establish a default bearer response, and the P-GW sends a periodic route advertisement in the established downlink GTP-U tunnel, where the route advertisement is sent periodically, for example, once every 10 seconds;
step 405, the S-GW has two processing conditions according to the different receiving sequence of the default bearer establishment response and the periodic route advertisement:
in the first situation, S-GW receives the response of establishing the default load first, then waits for the periodic route announcement sent by P-GW, receives and analyzes the data packet in GTP-U, and acquires the source link local address in the periodic route announcement after receiving and analyzing the periodic route announcement;
in the second case, the S-GW receives and analyzes the data packet in the GTP-U at the moment, acquires the source link local address in the periodic route advertisement after receiving and analyzing the periodic route advertisement, and waits for receiving and establishing a default bearer response message;
when the default bearer establishing response and the periodic routing notification are received and a source link local address in the periodic routing notification is obtained, the S-GW sends the source link local address to a trusted non-3GPP access gateway or an ePDG in an agent binding confirmation message;
optionally, in this step, the S-GW intercepts the received route advertisement, and after obtaining the source link local address, discards the route advertisement packet and does not send it to the MAG;
preferably, after the S-GW acquires the source link local address, the route advertisement sent by the P-GW is not analyzed, or the route advertisement packet is directly discarded after the route advertisement is analyzed.
Step 406, after completing the tunnel establishment, the trusted non 3GPP Access or ePDG notifies the UE of the information about the Access network, the configuration information (such as IP address or IP address prefix, interface identifier) required by the UE, and completes the IP Access process of the UE.
In the subsequent Access process, the UE generates a link local address on the local link by using the interface identifier acquired from the MAG, and the MAG (i.e., the trusted Non 3GPP Access or ePDG) uses the source link local address sent by the S-GW as its own link local address on the local link with the UE, so that the link local address between the UE and the MAG will not collide.
For sending the route advertisement by the second method, the basic flow is similar to the above-mentioned flow, and the main difference is that if the route advertisement is sent by the second method, in the above-mentioned step S404, the P-GW replies only the setup default bearer response to the S-GW, but not sends the route advertisement to the S-GW, the S-GW sends a route request to the P-GW after receiving the setup default bearer response sent by the P-GW, the source link address in the route request is generated by the UE interface id in the setup default bearer response message, the P-GW replies the route advertisement after receiving the route request, and if the S-GW does not receive the route advertisement within the predetermined time period, the S-GW can continue sending the route request to the P-GW; the S-GW does not send the route request after receiving the route advertisement, and the P-GW does not send the route advertisement because the P-GW sends the route advertisement according to the route request of the S-GW. And after the S-GW acquires the source link local address from the route advertisement sent by the P-GW, the route advertisement data packet is discarded and is not sent to the MAG, and the S-GW does not send a route request to the P-GW, so that the P-GW does not send the route advertisement.
According to the embodiment of the invention, the invention also provides a service gateway.
Fig. 5 is a schematic structural diagram of a service gateway according to an embodiment of the present invention, and as shown in fig. 5, the service gateway according to the embodiment of the present invention mainly includes: a receivingmodule 51, ananalysis module 53 and a sending module 55. The receivingmodule 51 is configured to receive a data packet from a packet data network gateway, where the data packet includes a route advertisement; the analyzingmodule 53 is connected to the receivingmodule 51, and is configured to analyze the route advertisement in the data packet received by the receivingmodule 51, and obtain a source link local address of the route advertisement; the sending module 55 is connected to theparsing module 53, and is configured to send the obtained source link local address to a trusted non-3GPP access gateway or ePDG as a link local address of the trusted non-3GPP access network or ePDG, which is carried in the proxy binding acknowledgement message.
Further, the receivingmodule 51 is further configured to receive a response for establishing a default bearer from the data network gateway.
Further, the sending module 55 may be further configured to send a routing request to the P-GW to request the P-GW to send the routing advertisement.
Preferably, as shown in fig. 6, the service gateway may further include: and the interception module 57 is configured to intercept the route advertisement received by the receivingmodule 51, and discard a packet of the route advertisement after theparsing module 53 obtains the source link local address.
The embodiment of the invention also provides a packet data network gateway.
Fig. 7 is a schematic structural diagram of a packet data network gateway according to an embodiment of the present invention, and as shown in fig. 7, the packet data network gateway according to the embodiment of the present invention mainly includes: a receiving module 71, abuilding module 73 and a sendingmodule 75. The receiving module 71 is configured to receive a request for establishing a default bearer sent by a serving gateway or receive a routing request from an S-GW; the establishingmodule 73 is connected with the receiving module 71 and is used for establishing a GTP-U tunnel and a GTP-C tunnel from the packet data network gateway to the service gateway; the sendingmodule 75 is connected to the establishingmodule 73, and is configured to send the route advertisement periodically through the GTP-U tunnel, or send the route advertisement according to the received route request, and send a default bearer establishing response through the GTP-C tunnel.
As described above, with the technical solution provided in the embodiment of the present invention, after receiving the request for establishing the default bearer, the P-GW does not need to send a GTC-C message to the S-GW, but sends a periodic route advertisement to the S-GW, and the S-GW can obtain a link local address on a local link between the MAG (including a trusted non-3GPP access network or ePDG) and the UE by analyzing a source link local address of the periodic route advertisement, without extending an interface between the P-GW and the S-GW, thereby reducing requirements on interfaces of the P-GW and the S-GW, and reducing cost and implementation complexity. In addition, in the embodiment of the present invention, after receiving the default bearer establishment response sent by the P-GW, the S-GW sends a routing request to the P-GW, where a source link address in the routing request is generated by a UE interface identifier in the default bearer establishment response message, and the P-GW replies a routing advertisement after receiving the routing request, and if the S-GW does not receive the routing advertisement, may continue to send the routing request to the P-GW; the S-GW does not send the routing request after receiving the routing advertisement, and the P-GW does not need to send the routing advertisement, thereby reducing unnecessary routing advertisement caused by the P-GW periodically sending the routing advertisement.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.