IP carrier peering

• US 10,116,802 B2
• Filed: 10/12/2017
• Issued: 10/30/2018
• Est. Priority Date: 06/30/2015
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Ku, Bernard S., Naidu, Lakshminarashimhan, Forsyth, James W.
• Primary Examiner(s): Abelson, Ronald B
• Application Number:
  US15/782,565
• Publication Number:
  US 20180084115A1
• Time in Patent Office: 383 Days
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04M 7/0075 Details of addressing, directories or routing tables

Abstract

Aspects of the subject disclosure may include, for example, a method and system to interconnect a first communications carrier to a second communications carrier by receiving a request to connect a communication from a first carrier to a second carrier; modifying a private ENUM (tElephone NUmber Mapping) domain of the request to include an intercarrier ENUM apex based domain; retrieving a routing record using a domain name server (DNS) indicated by the intercarrier ENUM apex based domain; and routing the communication to the second carrier using the routing record. Other embodiments are disclosed.

Claims

1. A system to interconnect carrier communication systems, the system comprises:

a communication client, the communication client configured to;

receive a request, including an e.164 number, to connect an IP (Internet protocol) call from equipment of a first carrier to equipment of a second carrier;

modify a query to a private ENUM (tElephone NUmber Mapping) to include an intercarrier ENUM apex-based domain with an associated DNS (domain name server) forwarding zone, wherein the associated DNS forwarding zone includes a primary internet address of a tier 2 ENUM of the second carrier;

automatically forward the modified query to the equipment of the second carrier to retrieve a routing record from the second carrier; and

route the IP call to the equipment of the second carrier using the routing record.

2. The system of claim 1, wherein the associated DNS forwarding zone is included as an entry to a first carrier ENUM BIND (Berkeley Internet Name Domain) DNS server.

3. The system of claim 1, wherein the associated DNS forwarding zone further includes a secondary internet address of the tier 2 ENUM of the second carrier.

4. The system of claim 1, wherein the automatically forwarding of the modified query to the equipment of the second carrier includes e164enum.net queries to at least one of:

a specific partner carrier or a specific higher tier ENUM.

5. The system of claim 1, wherein the automatically forwarding of the modified query to the equipment of the second carrier includes e164enum.net queries to the tier 2 ENUM.

6. The system of claim 1, wherein the request includes IP services comprising any of:

VoLTE (voice over long-term evolution), video calling, capability exchange or RCS (rich communication services) messaging.

7. The system of claim 1 further comprising an BGCF (Breakout Gateway Control Function) to perform the modification of the query and the automatic forwarding of the modified query.

8. The system of claim 1, wherein the intercarrier ENUM apex-based domain comprises e164enum.net.

9. A method to interconnect a first communications carrier to a second communications carrier, the method comprising:

receiving a request to connect an IP (Internet protocol) communication from equipment of a first communications carrier to equipment of a second communications carrier;

querying, using a first query, a private ENUM (tElephone NUmber Mapping) of the first communications carrier;

modifying the first query to include an intercarrier ENUM apex-based domain with a DNS (domain name server) forwarding zone, wherein the DNS forwarding zone includes a primary internet address of a tier 2 ENUM of the second communications carrier;

automatically forwarding the modified query to equipment of the second communications carrier to retrieve a routing record from the second communications carrier; and

routing the IP communication to the equipment of the second communications carrier using the routing record.

10. The method of claim 9, wherein the DNS forwarding zone is included as an entry to a first carrier ENUM BIND (Berkeley Internet Name Domain) DNS server.

11. The method of claim 9, wherein the DNS forwarding zone further includes a secondary internet address of the tier 2 ENUM of the second communications carrier.

12. The method of claim 9, wherein the automatically forwarding of the modified query to the equipment of the second communications carrier includes e164enum.net queries to at least one of:

a specific partner carrier or a specific higher tier ENUM.

13. The method of claim 9, wherein the automatically forwarding of the modified query to the equipment of the second communications carrier includes e164enum.net queries to the tier 2 ENUM.

14. The method of claim 9 further comprising an BGCF (Breakout Gateway Control Function) to perform the modification of the first query and the automatic forwarding of the modified first query.

15. The method of claim 9, wherein the intercarrier ENUM apex-based domain comprises e164enum.net.

16. A communication processing device comprises:

an interface;

memory; and

a processing unit operably coupled to the interface and the memory, wherein the processing unit functions to;

receive a request to connect an IP (Internet protocol) communication from equipment of a first carrier to equipment of a second carrier;

query, using a first query, a private ENUM (tElephone NUmber Mapping) of the first carrier;

when the first query does not return a routing record to complete the request, create a second query with an intercarrier ENUM apex-based domain with DNS (domain name server) forwarding zone;

automatically forward the second query to the equipment of the second carrier to retrieve the routing record from the second carrier; and

route the IP communication to the equipment of the second carrier using the routing record.

17. The communication processing device of claim 16, wherein the private ENUM of the first carrier acts as a proxy agent.

18. The communication processing device of claim 16, wherein the DNS forwarding zone is included as an entry to a first carrier ENUM BIND (Berkeley Internet Name Domain) DNS server, wherein the entry includes a primary internet address of a tier 2 ENUM of the second carrier.