DYNAMIC SELECTION OF PACKET DATA NETWORK GATEWAYS

• US 20120084449A1
• Filed: 10/05/2010
• Published: 04/05/2012
• Est. Priority Date: 10/05/2010
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: DELOS REYES, Emerando M., SHAIKH, Imtiyaz
• Granted Patent: US 8,554,933 B2
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: H04L 2101/375 Access point names [APN]
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

A device receives a PDN connection request from a UE, and exchanges, with a HSS, authentication and authorization information associated with the UE. The device also constructs an APN FQDN based on the authentication and authorization information, and sends a query, that includes the APN FQDN, to a DNS server. The device further receives, from the DNS server, PGW FQDNs that contain the APN FQDN, and compares the PGW FQDNs with a FQDN associated with a SGW. The device determines, based on the comparison, a PGW, associated with a PGW FQDN that is a closest match to the FQDN associated with the SGW, to be a primary PGW for the PDN connection request. The device also determines, based on the comparison, one or more PGWs, residing within a predetermined distance of the SGW, to be one or more backup PGWs for the PDN connection request.

Claims

1. A computing device-implemented method, comprising:

receiving, by the computing device, a packet data network (PDN) connection request from a user equipment (UE);

exchanging, by the computing device and with a home subscriber server (HSS), authentication and authorization information associated with the UE;

constructing, by the computing device, an access point name (APN) fully qualified domain name (FQDN) based on the authentication and authorization information;

sending, by the computing device, a query to a domain name system (DNS) server, where the query includes the APN FQDN;

receiving, by the computing device and from the DNS server, PDN gateway (PGW) FQDNs that contain the APN FQDN;

comparing, by the computing device, the PGW FQDNs with a FQDN associated with a serving gateway (SGW);

determining, by the computing device and based on the comparison, a PGW, associated with a PGW FQDN that is a closest match to the FQDN associated with the SGW, to be a primary PGW for the PDN connection request; and

determining, by the computing device and based on the comparison, one or more PGWs, residing within a predetermined distance of the SGW, to be one or more backup PGWs for the PDN connection request.

2. The computing device-implemented method of claim 1, further comprising:

sending, to the DNS server, queries based on FQDNs associated with the primary PGW and the one or more backup PGWs;

receiving, from the DNS server and based on the queries, Internet protocol (IP) addresses that match the FQDNs associated with the primary PGW and the one or more backup PGWs; and

storing the IP addresses in a memory of the computing device.

3. The computing device-implemented method of claim 2, further comprising:

providing, when the primary PGW is available, an IP address of the primary PGW to the UE, where the UE connects to the primary PGW based on the IP address of the primary PGW.

4. The computing device-implemented method of claim 3, further comprising:

providing, when the primary PGW is unavailable, an IP address of a backup PGW to the UE, where the UE connects to the backup PGW based on the IP address of the backup PGW.

5. The computing device-implemented method of claim 3, further comprising:

receiving an indication that the primary PGW is unavailable;

selecting one of the one or more backup PGWs to replace the primary PGW; and

providing an IP address of the selected backup PGW to the UE, where the UE connects to the selected backup PGW based on the IP address of the selected backup PGW.

6. The computing device-implemented method of claim 1, where the FQDN associated with the SGW is retrieved from a memory associated with the computing device.

7. The computing device-implemented method of claim 1, further comprising:

performing a SGW selection procedure; and

receiving the FQDN associated with the SGW based on the SGW selection procedure.

8. The computing device-implemented method of claim 1, where the computing device comprises a mobility management entity (MME).

9. The computing device-implemented method of claim 1, where the query includes a name authority pointer (NAPTR) query.

10. The computing device-implemented method of claim 1, where each of the PGW FQDNs includes information identifying a physical location of a particular PGW.

11. The computing device-implemented method of claim 10, where the physical location includes an area, a sub-area, and a mobile telephone switching office (MTSO) location of the particular PGW.

12. A device, comprising:

a memory to store a plurality of instructions; and

a processor to execute instructions in the memory to;

receive a packet data network (PDN) connection request from a user equipment (UE),

receive, from a home subscriber server (HSS), profile data associated with the UE,

create an access point name (APN) fully qualified domain name (FQDN) based on the profile data associated with the UE,

send a query, that includes the APN FQDN, to a domain name system (DNS) server,

receive, from the DNS server, PDN gateway (PGW) FQDNs that contain the APN FQDN,

determine a PGW, associated with a PGW FQDN that is a closest match to a FQDN associated with a serving gateway (SGW), to be a primary PGW for the PDN connection request, and

determine one or more PGWs, residing within a predetermined distance of the SGW, to be one or more backup PGWs for the PDN connection request.

13. The device of claim 12, where the processor is further to execute instructions in the memory to:

send, to the DNS server, queries based on FQDNs associated with the primary PGW and the one or more backup PGWs,

receive, from the DNS server and based on the queries, Internet protocol (IP) addresses that match the FQDNs associated with the primary PGW and the one or more backup PGWs, and

store the IP addresses in a memory of the device.

14. The device of claim 13, where the processor is further to execute instructions in the memory to:

provide, when the primary PGW is available, an IP address of the primary PGW to the UE, where the UE connects to the primary PGW based on the IP address of the primary PGW.

15. The device of claim 14, where the processor is further to execute instructions in the memory to:

provide, when the primary PGW is unavailable, an IP address of a backup PGW to the UE, where the UE connects to the backup PGW based on the IP address of the backup PGW.

16. The device of claim 14, where the processor is further to execute instructions in the memory to:

receive an indication that the primary PGW is unavailable,

select one of the one or more backup PGWs to replace the primary PGW, and

provide an IP address of the selected backup PGW to the UE, where the UE connects to the selected backup PGW based on the IP address of the selected backup PGW.

17. The device of claim 12, where the FQDN associated with the SGW is retrieved from a memory associated with the device.

18. The device of claim 12, where the processor is further to execute instructions in the memory to:

perform a SGW selection procedure, and

receive the FQDN associated with the SGW based on the SGW selection procedure.

19. The device of claim 12, where the device comprises a mobility management entity (MME).

20. The device of claim 12, where the query includes a name authority pointer (NAPTR) query.

21. The device of claim 12, where each of the PGW FQDNs includes information identifying a physical location of a particular PGW.

22. The device of claim 21, where the physical location includes an area, a sub-area, and a mobile telephone switching office (MTSO) location of the particular PGW.

23. A system comprising:

a home subscriber server (HSS);

a domain name system (DNS) server; and

a mobility management entity (MME) to;

receive a packet data network (PDN) connection request from a user equipment (UE),

receive, from the HSS, profile data associated with the UE and authentication and authorization information associated with the UE,

create an access point name (APN) fully qualified domain name (FQDN) based on at least one of the profile data associated with the UE or the authentication and authorization information associated with the UE,

send a query, that includes the APN FQDN, to the DNS server,

receive, from the DNS server, PDN gateway (PGW) FQDNs that contain the APN FQDN,

determine a PGW, associated with a PGW FQDN that is a closest match to a FQDN associated with a serving gateway (SGW), to be a primary PGW for the PDN connection request,

determine one or more PGWs, residing within a predetermined distance of the SGW, to be one or more backup PGWs for the PDN connection request,

send, to the DNS server, queries based on FQDNs associated with the primary PGW and the one or more backup PGWs,

receive, from the DNS server and based on the queries, Internet protocol (IP) addresses that match the FQDNs associated with the primary PGW and the one or more backup PGWs,

provide, when the primary PGW is available, an IP address of the primary PGW to the UE, where the UE connects to the primary PGW based on the IP address of the primary PGW, and

provide, when the primary PGW is unavailable, an IP address of a backup PGW to the UE, where the UE connects to the backup PGW based on the IP address of the backup PGW.