Systems and methods for providing ENUM in an LNP environment
First Claim
Patent Images
1. A system for providing an ENUM specification in an LNP environment, said system comprising:
- an originating office of a first service provider which receives a dialed call from an originating device;
a terminating office of a second service provider to which the dialed call is directed by the originating office;
a combined LNP and ENUM database in communication with both said originating office and said terminating office;
an originating means, located at said originating office, for looking up and using LNP and ENUM information from said combined database; and
a terminating means, located at said terminating office, for looking up and using LNP and ENUM information from said combined database,wherein the combined LNP and ENUM database receives a single LNP query based upon dialed digits from the originating means, the combined LNP and ENUM database returns an LNP response containing an LRN of the terminating office to the originating means, the LRN indicating that a terminating device has either a POTS format or an IP format such that a POTS format initiates a POTS routing and an IP format initiates the return of ENUM information to the originating means in an ENUM response with the LNP response, and the originating means receives the ENUM response and analyzes the ENUM response to determine what information format is necessary for the terminating device.
3 Assignments
0 Petitions
Accused Products
Abstract
A system, computer-readable medium system, and method which provide a ENUM specification in an LNP environment where an originating device of a first service provider dials a dialed call for forwarding to a terminating device of a second service provider. There is provided a combined LNP and ENUM database having a central location which is in communication with both an originating office and a terminating office. Both the originating office and the terminating office can look up and use LNP and ENUM information from the combined database.
-
Citations
27 Claims
-
1. A system for providing an ENUM specification in an LNP environment, said system comprising:
-
an originating office of a first service provider which receives a dialed call from an originating device; a terminating office of a second service provider to which the dialed call is directed by the originating office; a combined LNP and ENUM database in communication with both said originating office and said terminating office; an originating means, located at said originating office, for looking up and using LNP and ENUM information from said combined database; and a terminating means, located at said terminating office, for looking up and using LNP and ENUM information from said combined database, wherein the combined LNP and ENUM database receives a single LNP query based upon dialed digits from the originating means, the combined LNP and ENUM database returns an LNP response containing an LRN of the terminating office to the originating means, the LRN indicating that a terminating device has either a POTS format or an IP format such that a POTS format initiates a POTS routing and an IP format initiates the return of ENUM information to the originating means in an ENUM response with the LNP response, and the originating means receives the ENUM response and analyzes the ENUM response to determine what information format is necessary for the terminating device. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A system for providing an ENUM specification in an LNP environment where an originating device of a first service provider dials a dialed call for forwarding to a terminating device of a second service provider, said system comprising:
-
an originating office of the first local service provider which receives the dialed call from the originating device; a terminating office of the second local service provider which is separate from the first local service provider of the originating office and to which the dialed call is directed by the originating office for connection to the terminating device which is connected to said terminating office; a combined LNP and ENUM database in communication with both said originating office and said terminating office; an originating means, located at said originating office, for looking up and using LNP and ENUM information from said combined database; and a terminating means, located at said terminating office, for looking up and using LNP and ENUM information from said combined database, wherein the combined LNP and ENUM database receives a single LNP query based upon dialed digits from the originating means, the combined LNP and ENUM database returns an LNP response containing an LRN of the terminating office to the originating means, the LRN indicating that a terminating device has either a POTS format or an IP format such that a POTS format initiates a POTS routing and an IP format initiates the return of ENUM information to the originating means in an ENUM response with the LNP response, and the originating office receives the ENUM response and analyzes the ENUM response to determine what information format is necessary for the terminating device. - View Dependent Claims (8, 9, 10)
-
-
11. A method for utilizing local number portability features to implement telephone number mapping comprising the steps of:
-
providing a combined LNP and ENUM database in communication with a first service provider and a second service provider for ready access by both the first or second service providers; receiving dialed digits of a dialed call having IP type call data from an originating telephone of the first service provider for forwarding to the second service provider associated with a terminating exchange of the dialed call; performing a digit analysis of the dialed digits to determine that the dialed call is directed to an IP device and that the terminating exchange of the dialed call is marked portable; sending a single query to the LNP and ENUM database based on the dialed digits to determine an LRN for the terminating exchange and ENUM information for the IP device; and routing of the dialed call to the IP device in accordance with the LRN and ENUM information obtained from the LNP and ENUM database, wherein the combined LNP and ENUM database receives the single query based upon dialed digits from an originating exchange, the combined LNP and ENUM database returns an LNP response containing the LRN of the terminating exchange to the originating exchange, and the originating exchange receives the ENUM information and analyzes the ENUM information to determine what information format is necessary for the IP device. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A method for utilizing local number portability features to implement telephone number mapping comprising the steps of:
-
providing a combined LNP and ENUM database in communication with a first service provider and a second service provider for ready access by both the first or second service providers; receiving dialed digits, including a terminating exchange of the second provider, of a dialed call having IP type call data from an originating telephone at an originating office of the first service provider for forwarding to a terminating office of the second service provider associated with the terminating exchange; performing a digit analysis of the dialed digits to determine that the dialed call is directed to an IP device and that the terminating exchange of the dialed call is marked portable; sending a single query to the LNP and ENUM database based on the dialed digits to determine an LRN for the terminating exchange and ENUM information for the IP device; and routing of the dialed call to the IP device in accordance with the LRN and ENUM information obtained from the LNP and ENUM database, wherein the combined LNP and ENUM database receives the single query based upon dialed digits from an originating office, the combined LNP and ENUM database returns an LNP response containing the LRN of the terminating exchange to the originating office, and the originating means receives the ENUM information and analyzes the ENUM information to determine what information format is necessary for the IP device. - View Dependent Claims (21, 22, 23, 24, 25, 26, 27)
-
Specification