Temporary Enum Gateway
Abstract
A temporary ENUM architecture assigns a temporary ENUM at call time. For an originated communication requiring routing to a party which needs a particular callback format not supported, the TempENUM provides consistency with the specific format required by the receiving party. The TempENUM is assigned for the duration of the call or communication, or for a given amount of time thereafter. The TempENUM service gateway includes a TempENUM database, a module that assigns a suitable TempENUM at the time of call routing, and a module that handles a lookup in the TempENUM database, and maps the assigned TempENUM to a calling party identifier (CgPID). The TempENUM database stores a TempENUM from a coordinator system and relates the actual calling party identifier (CgPID) for use in callback attempts. Either during the initial call or communication, or shortly thereafter, the receiving party uses the TempENUM number to return communication the initial caller.
Claims
exact text as granted — not AI-modified1 - 38 . (canceled)
39 . An electronic numbering (ENUM) gateway, comprising:
an ENUM coordinator system to receive an email message directed to an ENUM receiving entity and associated with a non-ENUM conforming email device identity information, said ENUM receiving entity mapping an ENUM with external resources associated with said ENUM; a temporary ENUM database to associate a temporary conforming ENUM with said non-ENUM conforming email device identity information; a module to assign said temporary conforming ENUM at a time of routing of said email message, said temporary conforming ENUM being an entry in said temporary ENUM database; and a lookup module to lookup said temporary conforming ENUM in said temporary ENUM database and retrieve said associated email device identity information.
40 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said entry in said temporary ENUM database is a temporary entry that expires after a given amount of time after routing of said email message.
41 . The electronic numbering (ENUM) gateway according to claim 39 , wherein said email device identity information comprises:
a phone number of an emailing device initiating said email message.
42 . The electronic numbering (ENUM) gateway according to claim 41 , wherein:
said phone number does not conform to a 10-digit North American Numbering Plan phone number.
43 . The electronic numbering (ENUM) gateway according to claim 39 , wherein said email device identity information comprises:
an email address associated with a user of an emailing device initiating said email message.
44 . The electronic numbering (ENUM) gateway according to claim 39 , wherein said email device identity information comprises:
an instant messaging address associated with a user of an emailing device initiating said email message.
45 . The electronic numbering (ENUM) gateway according to claim 39 , wherein said email device identity information comprises:
a vehicle ID.
46 . The electronic numbering (ENUM) gateway according to claim 39 , wherein said email device identity information comprises:
a mobile directory number (MDN).
47 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said temporary ENUM gateway forms a temporary ENUM service.
48 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said temporary conforming ENUM conforms to requirements of an addressed party relating to said email device identification information.
49 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said temporary conforming ENUM conforms to 10-digit North American Numbering Plan requirements.
50 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said email message includes video.
51 . The electronic numbering (ENUM) gateway according to claim 39 , wherein:
said email message includes voice.
52 . A method of associating an electronic number (ENUM) to a given email message communication, comprising:
receiving an email message directed to an ENUM receiving entity and associated with a non-ENUM conforming email device identity information, said ENUM receiving entity mapping an ENUM with external resources associated with said ENUM; associating a temporary conforming ENUM with said non-ENUM conforming email device identity information; assigning said temporary conforming ENUM at a time of routing of said email message, said temporary conforming ENUM being an entry in said temporary ENUM database; and retrieving said associated email device identity information based on a database lookup of said temporary conforming ENUM in a temporary ENUM database.
53 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein:
said entry in said temporary ENUM database is a temporary entry that expires after a given amount of time after routing of said email message.
54 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein said email device identity information comprises:
a phone number of an emailing device initiating said email message.
55 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein:
said phone number does not conform to a 10-digit North American Numbering Plan phone number.
56 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein said email device identity information comprises:
an email address associated with a user of an emailing device initiating said email message.
57 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein:
said temporary conforming ENUM conforms to 10-digit North American Numbering Plan requirements.
58 . The method of associating an electronic number (ENUM) to a given email message communication according to claim 52 , wherein:
said email message includes video.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.