PROACTIVE TELEPHONE NUMBER MAPPING CONFIGURATION MANAGEMENT

• US 20100232592A1
• Filed: 05/18/2009
• Published: 09/16/2010
• Est. Priority Date: 03/12/2009
• Status: Active Grant

• 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
• Granted Patent: US 8,363,815 B2
• Time in Patent Office: Days
• US Class Current: 379/220.10
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 2213/097 Numbering
• CPC Class Codes: H04Q 2213/102 Common translator
• CPC Class Codes: H04Q 3/76 Translation from the called subscriber's number to the outgoing or incoming control information
• CPC Class Codes: H04W 40/00 Communication routing or communication path finding

Abstract

Methods and apparatus for enabling efficient telephone number mapping (ENUM) based call routing during area code splits are presented herein. An ENUM domain management component can associate an ENUM domain name with multiple records when a numbering plan area code split links an old area code of a telephone number corresponding to the ENUM domain name with a new area code. An ENUM provisioning component can perform permissive dialing of the old and new area code during ENUM based call routing by utilizing the multiple records.

Claims

1. A system comprising:

at least one processor that executes the following computer executable components;

a telephone number mapping (ENUM) domain management component that associates an ENUM domain name with multiple records when a numbering plan area (NPA) code split links an old area code of a telephone number corresponding to the ENUM domain name to a new area code; and

an ENUM provisioning component that performs permissive dialing of the old area code and the new area code during ENUM based call routing based on the multiple records.

2. The system of claim 1, wherein the ENUM domain management component:

creates a first ENUM domain name record, wherein the first ENUM domain name record is associated with the old area code; and

creates a second ENUM domain name record, wherein the second ENUM domain name record is associated with the new area code;

wherein the second ENUM domain name record is different than the first ENUM domain name record.

3. The system of claim 1, wherein the ENUM domain management component associates the ENUM domain name with multiple records at least one of:

prior to a time when the NPA code split relates the new area code to the old area code;

or

at the time when the NPA code split relates the new area code to the old area code.

4. The system of claim 3, wherein the ENUM domain management component:

disassociates the ENUM domain name from a record associated with the old area code when a permissive dialing period associated with permissive dialing ends.

5. The system of claim 4, further comprising:

a data store component that stores the multiple records in a data store;

wherein the ENUM domain management component disassociates the ENUM domain name from the record associated with the old area code by removing the record from the data store.

6. The system of claim 5, wherein the ENUM provisioning component:

prevents storage of records related to telephone numbers associated with the new area code before the permissive dialing period begins.

7. The system of claim 6, wherein the ENUM provisioning component:

prevents storage of records related to telephone numbers associated with the old area code after the permissive dialing period begins.

8. The system of claim 7, wherein the ENUM provisioning component:

prevents at least one of creation, modification, or removal of the ENUM domain name during the permissive dialing period.

9. The system of claim 8, wherein the ENUM domain management component:

deletes records in the data store that are related to telephone numbers associated with the old area code.

10. The system of claim 1, further comprising an artificial intelligence component that automatically:

links the ENUM domain name to a distinct record associated with a telephone number affected by the NPA code split; and

permits dialing of an old and new area code of the telephone number during an interval of time to enable connection to an equivalent ENUM communication termination point.

11. The system of claim 10, wherein the artificial intelligence component automatically relates the ENUM domain name to the distinct record based on the interval of time.

12. The system of claim 11, wherein the artificial intelligence component:

prevents storage of the distinct record before the interval of time when the telephone number includes the new area code; and

prevents storage of the distinct record within the interval of time when the telephone number includes the old area code.

13. The system of claim 12, wherein the artificial intelligence component:

prevents adjustment of the ENUM domain name during the interval of time.

14. The system of claim 13, wherein the artificial intelligence component automatically:

eliminates the distinct record after the interval of time if the telephone number includes the old area code.

15. The system of claim 1, further comprising an ENUM routing component that performs at least one of the following during the ENUM based call routing:

routes ENUM based calls via an internet protocol (IP) Multimedia Subsystem (IMS);

routes ENUM based calls to a voice protocol endpoint;

routes ENUM based calls to an instant messenger (IM) endpoint;

routes ENUM based calls to an email;

routes ENUM based calls to a web site;

routes ENUM based calls to a public switched telephone network (PSTN) endpoint;

routes ENUM based calls to a wireless endpoint;

or

routes ENUM based calls to a cellular based endpoint.

16. The system of claim 1, wherein the ENUM domain name is associated with a domain name system (DNS) data base.

17. The system of claim 5, wherein the data store comprises a domain name system (DNS) data base.

18. The system of claim 1, wherein the ENUM domain name is compatible with the E.164 telephone numbering system.

19. A method comprising:

employing at least one processor to execute computer executable instructions stored on at least one computer readable medium to perform the following acts;

duplicating a record associated with a telephone number mapping (ENUM) domain name to create other records;

converting the other records into distinct records;

relating each distinct record to a different area code assigned to a telephone number associated with the ENUM domain name; and

linking different area codes assigned to the telephone number to equivalent ENUM communication endpoints based on, at least in part, the distinct records.

20. A computer readable storage medium having stored thereon computer executable instructions that, if executed by a system, cause the system to perform a method comprising:

copying a record related to a telephone number mapping (ENUM) domain name to create one or more other records;

translating the created records into unique records;

associating each translated record to a unique area code assigned to a telephone number related to the ENUM domain name; and

connecting different area codes assigned to the telephone number with equivalent ENUM communication endpoints based on, at least in part, the unique records.