WO2006110620A9 - Temporary enum gateway - Google Patents

Temporary enum gateway

Info

Publication number
WO2006110620A9
WO2006110620A9 PCT/US2006/013233 US2006013233W WO2006110620A9 WO 2006110620 A9 WO2006110620 A9 WO 2006110620A9 US 2006013233 W US2006013233 W US 2006013233W WO 2006110620 A9 WO2006110620 A9 WO 2006110620A9
Authority
WO
WIPO (PCT)
Prior art keywords
enum
given communication
temporary
electronic
transmission
Prior art date
Application number
PCT/US2006/013233
Other languages
French (fr)
Other versions
WO2006110620A2 (en
WO2006110620A3 (en
Inventor
Don Mitchell
Original Assignee
Telecomm Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telecomm Systems Inc filed Critical Telecomm Systems Inc
Priority to MX2007012683A priority Critical patent/MX2007012683A/en
Priority to BRPI0610718-4A priority patent/BRPI0610718A2/en
Priority to CN2006800190298A priority patent/CN101518042B/en
Priority to EP06769809A priority patent/EP1932330A4/en
Priority to CA2604211A priority patent/CA2604211C/en
Priority to JP2008506561A priority patent/JP5155151B2/en
Priority to AU2006235297A priority patent/AU2006235297B2/en
Publication of WO2006110620A2 publication Critical patent/WO2006110620A2/en
Publication of WO2006110620A9 publication Critical patent/WO2006110620A9/en
Publication of WO2006110620A3 publication Critical patent/WO2006110620A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0075—Details of addressing, directories or routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42008—Systems for anonymous communication between parties, e.g. by use of disposal contact identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it

Definitions

  • VoIP Internet Protocol
  • ENUM is a protocol for mapping a telephone number to a Uniform Resource Identifier (URI) which can be used to contact a resource associated with that number.
  • URI Uniform Resource Identifier
  • ENUM in this scenario therefore gives access to a wide range of a person's (communication) identifiers by looking up a specific domain associated with that person's telephone number.
  • an ENUM service receives a dialed (or addressed) phone number, and uses a mathematical formula and lookup table(s) to resolve it to an Internet Uniform Resource Identifier (URI) for the subscriber's ENUM Naming Authority Pointer (NAPTR) record, a repository of communications access information.
  • URI Internet Uniform Resource Identifier
  • NAPTR ENUM Naming Authority Pointer
  • the service then routes the call or communication to a service provider based on the type of request, e.g., voice, fax, email, etc., and any preferences established by the subscriber.
  • VoIP service providers and IP network managers can avoid the costs and any applicable regulatory hassles associated with having to assign public switched telephone network (PSTN) numbers and use PSTN networks to route calls when both parties are using voice over Internet Protocol (VoIP).
  • PSTN public switched telephone network
  • VoIP voice over Internet Protocol
  • ENUM For VoIP users, ENUM makes IP communications easier and ultimately less expensive. It gives subscribers control of the way that they're contacted by providing them with customized configuration of their own NAPTR, e.g., using a simple web interface. Others can contact a subscriber even when they don't know where the person is or how they want to be contacted, simply using their ENUM. With ENUM, users can dial Internet-based communications services even from numeric-only devices, including non-IP mobile and wireline phones.
  • ENUM technology in general helps ease the transition from circuit- switched to voice over Internet protocol (VoIP) communications.
  • VoIP voice over Internet protocol
  • ENUM services with respect to international callers.
  • an international caller using ENUM services in the US might dial 9- 1-1.
  • conventional ENUM services cannot successfully deliver a full callback phone number of the international caller to a 9-1-1 answering agency such as a public safety answering point (PSAP).
  • PSAP public safety answering point
  • NANP North American Numbering Plan
  • the NANP requires use of 10-digit fields to transmit information.
  • an originator of communication voice, text or video
  • an electronic numbering (ENUM) gateway comprises a temporary ENUM database associating a plurality of ENUMs with respective caller identity information.
  • a module assigns a temporary ENUM at a time of routing a given communication.
  • the temporary ENUM is an entry in the temporary ENUM database.
  • a module looks up in the temporary ENUM database a given temporary ENUM, and retrieves associated caller identity information.
  • a method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of the given communication comprises receiving a request for a temporary ENUM relating to a given communication.
  • the temporary ENUM conforms to a format for calling party identity information as required by a called party.
  • a temporary ENUM is associated with caller identity information relating to a caller initiating the given communication.
  • the associated temporary ENUM is stored as an entry in a temporary ENUM database.
  • Fig. 1 shows exemplary basic message flow relating to a Temp ENUM Gateway, in accordance with the principles of the present invention.
  • Fig. 2 shows exemplary message flow relating to a temporary ENUM service gateway in use with a roadside assistance/emergency relay center, in accordance with the principles of the present invention.
  • Fig. 3 shows exemplary message flow relating to a temporary ENUM service gateway in use with Instant Messaging services, in accordance with the principles of the present invention.
  • Fig. 4 shows exemplary message flow relating to a temporary ENUM service gateway in use with Peer-To-Peer voice provider services, in accordance with the principles of the present invention.
  • Fig. 5 shows exemplary message flow relating to a temporary ENUM service gateway in use with wireless E9-1-1 services, in accordance with the principles of the present invention.
  • ENUM Current electronic numbering
  • NANP North American Numbering Plan
  • the present invention provides a temporary ENUM, or "TempENUM", architecture that assigns a temporary ENUM number at call time.
  • the ENUM number in the disclosed embodiments is assigned substantially only for the duration of the call or communication.
  • TempENUM service in accordance with the principles of the present invention assigns a callback identifier (ID) in a format consistent with that required by the receiving party.
  • ID callback identifier
  • Fig. 1 shows exemplary basic message flow relating to a Temp ENUM Gateway, in accordance with the principles of the present invention.
  • FIG. 1 shows a communicating party or originating entity 110 that places a call to a contacted entity or receiving party 120.
  • the call is processed through an appropriate gateway provisioned to be a coordinator system 130.
  • a temporary ENUM (TempENUM) service gateway 100 is implemented, including a TempENUM database 101, a module 102 that assigns a suitable TempENUM at the time of call routing, and a module 103 that handles a lookup in the TempENUM database 101 , and maps the assigned
  • TempENUM to a calling party identifier (CgPID).
  • the TempENUM database 101 stores a TempENUM assignment from the coordinator system 130 and relates the actual calling party identifier (CgPID) for use in callback attempts.
  • CgPID calling party identifier
  • the originating party 110 attempts communication to a receiving party 120 that preferably receives the communication with an identifying ID used for re-contact, but the originating party's communication method is unable to provide that specific ID format.
  • the communication is routed to an appropriate temporary
  • the temporary ENUM numbering service i.e., to the TempENUM service gateway 100.
  • the temporary ENUM numbering service, or TempENUM service gateway 100 receives a temporary ID (Temp ENUM) from an appropriate module 102 that assigns a suitable TempENUM at the time of call routing, and routes the call.
  • the module 102 is preferably part of a temporary ENUM service.
  • the temporary ID (or TempENUM) is consistent with the specific format required by the receiving party 120.
  • step 3 the communication is routed to the receiving party 120 with an appropriate Temp ENUM specific to the format requirements of the receiving party 120.
  • step 4 the receiving party 120 communicates with the originating party 110 substantially immediately after termination of a session.
  • the receiving party 120 uses the received TempENUM number to callback or re-initiate communication with the originating party 110 as required, e.g., within a predetermined time.
  • the callback communication attempt is directed to the TempENUM service gateway 100.
  • the TempENUM service gateway 100 performs an appropriate authorization process intended to verify validity of the callback communication attempt back to the originating party 110. Validity may be based upon, e.g., the location of the communication attempt, date and time, etc.
  • the TempENUM service gateway 100 correlates the TempENUM (i.e., temporary identifier) with the actual callback number or other communication identifier of the originating party 110. In step 5, the callback communication attempt by the receiving party 120 is completed back to the originating party 110.
  • Fig. 2 shows exemplary message flow relating to a temporary ENLJM service gateway in use with a roadside assistance/emergency relay center, in accordance with the principles of the present invention.
  • FIG. 2 shows interaction between an automobile equipped with a telematics system 210, its servicing telematics operations center 270, a coordinator system gateway 230, and a TempENUM service gateway 100. Otherwise conventional location elements are also accessed, including an emergency services gateway 250, a public safety access point 220, and an automatic location identifier (ALI) database 260.
  • ALI automatic location identifier
  • the automobile 210 equipped with a suitable telematics system 210 attempts to contact a public safety access point (PSAP) 220.
  • PSAP public safety access point
  • the PSAP 220 is provided with a callback mechanism to reinitiate contact with the emergency caller 210 should the initial call be accidentally or unintentionally dropped.
  • An emergency relay center (e.g., ONSTARTM telematics service center) 270 provides service to the automobile 210.
  • the emergency relay center 270 passes an emergency call from the automobile 210 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 230.
  • the emergency call is passed to the coordinator system 230 together with a calling party identifier (CgPID) such as an agent ID, vehicle ID, etc., together with appropriate X, Y (latitude/longitude) positional information.
  • CgPID calling party identifier
  • the coordinator system 230 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID).
  • the TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 230.
  • Location of the automobile 210 is provided through the use of an emergency services routing number (ESRN) (e.g., in a switched network) or emergency services query key (ESQK) (e.g., in a voice over Internet Protocol (VoIP) network).
  • An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 230, and either passes the ESQK on to the PSAP 220 (if in a VoIP network), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network).
  • the PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency caller 210.
  • the ALI database 260 is updated with location information using an ESQK request to the coordinator system 230.
  • the coordinator system 230 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the automobile 210, and the assigned TempENUM relating to the relevant emergency call.
  • the receiving party in this case the PSAP 220 attempts a callback communication to the originating party (in this case the automobile 210).
  • This callback attempt is directed towards the TempENUM service gateway 100.
  • the TempENUM service gateway 100 performs a lookup in the TempENUM database , and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM.
  • the callback communications routed using the retrieved calling party identifier, which in this case directs the callback communication to the emergency relay center 270, which in turn passes the callback communication to the automobile 210.
  • Fig. 3 shows exemplary message flow relating to a temporary ENUM service gateway in use with Instant Messaging services, in accordance with the principles of the present invention.
  • Fig. 3 shows interaction between an instant messaging user 310, their servicing emergency services instant messaging (ESIM) user instance(s) 370, a coordinator system gateway 330, and a TempENUM service gateway 100.
  • ESIM emergency services instant messaging
  • a coordinator system gateway 330 e.g., a coordinator system gateway 330
  • a TempENUM service gateway 100 e.g., a TempENUM service gateway 100.
  • conventional location elements are also accessed, including an emergency services gateway 250, a public safety access point 220, and an automatic location identifier (ALI) database 260.
  • the PSAP 220 is able to access relevant text and/or video from the instant messaging user 310 via an appropriate web portal 360.
  • the instant messaging user 310 sends an instant message with text, video or voice to an appropriate PSAP 220.
  • the PSAP 220 is provided with a callback mechanism to reply to the instant messaging user 310.
  • ESIM emergency services instant messaging
  • the ESIM gateway 370 passes the instant message from the instant messaging user 310 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 330.
  • the emergency instant message is passed to the coordinator system 330 using a SIP INVITE command, together with a calling party identifier (CgPID) with LO.
  • CgPID calling party identifier
  • the coordinator system 330 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID).
  • the TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 330.
  • Location of the instant messaging user 310 is provided through the use of an emergency services routing number (ESRN) (e.g., in a switched network) or emergency services query key (ESQK) (e.g., over the Internet).
  • An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 330, and either passes the ESQK on to the PSAP 220 (if over the Internet), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network).
  • the PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency calling instant messaging user 310.
  • the ALI database 260 is updated with location information using an ESQK request to the coordinator system 330.
  • the coordinator system 330 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the instant messaging user 310, and the assigned TempENUM relating to the relevant emergency instant message.
  • the receiving party in this case the PSAP 220 attempts a callback communication to the originating party (in this case a return instant message to the instant messaging user 310).
  • This return instant message is directed towards the TempENUM service gateway 100.
  • the TempENUM service gateway 100 performs a lookup in the TempENUM database, and maps the provided TempENUM to the temporarily stored calling party identifier (in this case an instant messaging user identifier) associated with that TempENUM.
  • the return communication is routed using the retrieved calling party identifier, which in this case directs the return instant message to the emergency services instant messaging (ESIM) user instance(s) 370, and in turn passes the return instant message to the instant messaging user 310.
  • ESIM emergency services instant messaging
  • Fig. 4 shows exemplary message flow relating to a temporary
  • ENUM service gateway in use with Peer-To-Peer voice provider services, in accordance with the principles of the present invention.
  • FIG. 4 shows interaction between a personal computer (PC) based VoIP application (e.g., SkypeTM) user 410, their servicing emergency services SkypeTM (ESS) gateway including user instance(s) 470, a coordinator system gateway 430, and a TempENUM service gateway 100.
  • PC personal computer
  • ESS emergency services SkypeTM
  • ESS emergency services SkypeTM
  • ALI automatic location identifier
  • PSAP 220 is provided with a callback mechanism to reply to the PC based VoIP application user 410.
  • a relevant user instance (IN, OUT and NORM) is established in the PC hosting the VoIP application, as well as in an appropriate Emergency Services Skype (ESS) gateway 470.
  • ESS Emergency Services Skype
  • the ESS gateway 470 passes the VoIP call from the SkypeTM user 410 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 430.
  • the emergency VoIP call is passed to the coordinator system 430 using a SIP INVITE command, together with a calling party identifier (CgPID) with LO.
  • CgPID calling party identifier
  • SkypeTM users pass their North American Numbering Plan (NANP) calling party number (CgPN) to the coordinator system 430.
  • NANP North American Numbering Plan
  • CgPN North American Numbering Plan
  • the coordinator system 430 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID).
  • the TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 430.
  • ESRN emergency services routing number
  • ESQK emergency services query key
  • An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 330, and either passes the ESQK on to the PSAP 220 (if over the internet), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network).
  • the PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency calling PC based VoIP application user 410.
  • ALI automatic location identifier
  • the ALI database 260 is updated with location information using an ESQK request to the coordinator system 430.
  • the coordinator system 430 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the PC based VoIP application user 410, and the assigned TempENUM relating to the relevant emergency VoIP call.
  • the receiving party in this case the PSAP 220
  • attempts a callback call to the originating party in this case PC based VoIP application user 410.
  • This callback call is directed towards the TempENUM service gateway 100.
  • the TempENUM service gateway 100 performs a lookup in the TempENUM database, and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM.
  • the return communication is routed using the retrieved calling party identifier, which in this case directs the return call to the emergency services instant messaging (ESIM) user instance(s) 370, and in turn to the PC based VoIP application user 410.
  • ESIM emergency services instant messaging
  • Fig. 5 shows exemplary message flow relating to a temporary ENUM service gateway in use with wireless E9-1-1 services, in accordance with the principles of the present invention.
  • Fig. 5 shows interaction between an international wireless caller 510 (e.g., a caller with a callback number that is larger or otherwise non-conforming to NANP 10-digit format), a servicing mobile switching center (MSC) 580, a coordinator system gateway 530, and a TempENUM service gateway 100.
  • MSC mobile switching center
  • a coordinator system gateway 530 e.g., a coordinator system gateway 530, and a TempENUM service gateway 100.
  • conventional location elements are also accessed, including a public safety access point 220, and an automatic location identifier (ALI) database 260.
  • ALI automatic location identifier
  • the international wireless caller 510 attempts to contact the appropriate public safety access point (PSAP) 220.
  • PSAP public safety access point
  • the PSAP 220 is provided with a callback mechanism to re-initiate contact with the international wireless caller 510 as necessary or desired (e.g., should the initial call be accidentally or unintentionally dropped).
  • the mobile switching center (MSC) 580 provides service to the international wireless caller 510.
  • the MSC 580 passes an emergency call from the international wireless cajler 510 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 530.
  • the emergency call is passed from the MSC 580 to the coordinator system 530 together with a calling party identifier (CgPID) such as a mobile directory number (MDN), together with appropriate X, Y (latitude/longitude) positional information.
  • CgPID calling party identifier
  • MDN mobile directory number
  • the coordinator system 530 initiates a TempENUM request to the TempENUM service gateway
  • the TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 530.
  • the coordinator system 530 requests assignment of the TempENUM from the TempENUM services gateway 100, and then passes the emergency call through to the PSAP 220 indicated by a query to the ALI database 260.
  • the ALI database 260 provides the appropriate emergency services routing key (ESRK) to the PSAP 220.
  • ESRK emergency services routing key
  • the coordinator system 530 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the international wireless caller 510, and the assigned TempENUM relating to the relevant emergency call. Finally, as necessary (or desired), the receiving party (in this case the PSAP 220) attempts a callback communication to the originating party (in this case the wireless international caller 510). This callback attempt is directed towards the TempENUM service gateway 100.
  • the TempENUM service gateway 100 performs a lookup in the TempENUM database , and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM.
  • the callback communications are routed using the retrieved calling party identifier, which in this case means that the callback communication is directed to the MSC 580 servicing the international wireless caller 510, and ultimately to the international wireless caller 510.
  • the present invention has particular applicability in the wireless E9- 1-1 market, including any US GSM carrier that supports PCS frequencies used by foreign markets. Other applications include roadside assistance/emergency relay centers, instant messaging providers, and peer-to-peer voice providers. There is also particular applicability with VoIP operators, particularly VoIP operators that support Mobile/Nomadic International subscribers, VoIP operators wishing to market International numbers for North American subscribers, and VoIP operators with subscribers that don't want to sign up in the ENUM directory.

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.

Description

TEMPORARY ENUM GATEWAY
The present application claims priority from U.S. Provisional Application No. 60/670,279, entitled "Temporary ENUM Gateway", filed April 12, 2005, to Mitchell, the entirety of which is expressly incorporated herein by reference.
BACKGROUND OF THE INVENTION
1. Field of the Invention This invention relates generally to wireless devices and voice over
Internet Protocol (VoIP) technologies. More particularly, it relates to ENUM services.
2. Background of the Related Art Electronic numbering (ENUM) services have been called implementation of a 'phone number for life'. Just like a social security number follows a person for life, ENUM envisions use of a single simple telephone number to access a person over any applicable medium (e.g., telephone network, FAX, Internet, etc.) Thus, as currently envisioned, electronic numbering (ENUM) services give subscribers a single telephone number that can be used to access any of their communications services or devices via an Internet Protocol (IP) network, e.g., voice, fax, email, short message service (SMS), etc.
For use in the Internet world, ENUM is a protocol for mapping a telephone number to a Uniform Resource Identifier (URI) which can be used to contact a resource associated with that number. ENUM in this scenario therefore gives access to a wide range of a person's (communication) identifiers by looking up a specific domain associated with that person's telephone number.
In operation, an ENUM service receives a dialed (or addressed) phone number, and uses a mathematical formula and lookup table(s) to resolve it to an Internet Uniform Resource Identifier (URI) for the subscriber's ENUM Naming Authority Pointer (NAPTR) record, a repository of communications access information. The service then routes the call or communication to a service provider based on the type of request, e.g., voice, fax, email, etc., and any preferences established by the subscriber.
Thus, VoIP service providers and IP network managers can avoid the costs and any applicable regulatory hassles associated with having to assign public switched telephone network (PSTN) numbers and use PSTN networks to route calls when both parties are using voice over Internet Protocol (VoIP).
For VoIP users, ENUM makes IP communications easier and ultimately less expensive. It gives subscribers control of the way that they're contacted by providing them with customized configuration of their own NAPTR, e.g., using a simple web interface. Others can contact a subscriber even when they don't know where the person is or how they want to be contacted, simply using their ENUM. With ENUM, users can dial Internet-based communications services even from numeric-only devices, including non-IP mobile and wireline phones.
ENUM technology in general helps ease the transition from circuit- switched to voice over Internet protocol (VoIP) communications. However, there are particular problems using ENUM services with respect to international callers. For example, an international caller using ENUM services in the US might dial 9- 1-1. However, conventional ENUM services cannot successfully deliver a full callback phone number of the international caller to a 9-1-1 answering agency such as a public safety answering point (PSAP). This is because of restrictions caused by the North American Numbering Plan (NANP). In particular, the NANP requires use of 10-digit fields to transmit information. In this type case, an originator of communication (voice, text or video) cannot pass the required re- contact information to the end point because the international caller's number may not fit within the confines of the NANP 10-digit information field.
There is a need for a suitable method and apparatus for reliably providing callback number information for all callers from all sources within an electronic numbering (ENUM) architecture. SUMMARY OF THE INVENTION
In accordance with the principles of the present invention, an electronic numbering (ENUM) gateway comprises a temporary ENUM database associating a plurality of ENUMs with respective caller identity information. A module assigns a temporary ENUM at a time of routing a given communication. The temporary ENUM is an entry in the temporary ENUM database. A module looks up in the temporary ENUM database a given temporary ENUM, and retrieves associated caller identity information.
A method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of the given communication in accordance with another aspect of the invention comprises receiving a request for a temporary ENUM relating to a given communication. The temporary ENUM conforms to a format for calling party identity information as required by a called party. A temporary ENUM is associated with caller identity information relating to a caller initiating the given communication. The associated temporary ENUM is stored as an entry in a temporary ENUM database.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows exemplary basic message flow relating to a Temp ENUM Gateway, in accordance with the principles of the present invention.
Fig. 2 shows exemplary message flow relating to a temporary ENUM service gateway in use with a roadside assistance/emergency relay center, in accordance with the principles of the present invention.
Fig. 3 shows exemplary message flow relating to a temporary ENUM service gateway in use with Instant Messaging services, in accordance with the principles of the present invention.
Fig. 4 shows exemplary message flow relating to a temporary ENUM service gateway in use with Peer-To-Peer voice provider services, in accordance with the principles of the present invention. Fig. 5 shows exemplary message flow relating to a temporary ENUM service gateway in use with wireless E9-1-1 services, in accordance with the principles of the present invention.
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
Current electronic numbering (ENUM) technology requires the user to apply for a permanent DNS assigned 10-digit North American Numbering Plan (NANP) number in the US. The present invention provides a temporary ENUM, or "TempENUM", architecture that assigns a temporary ENUM number at call time. The ENUM number in the disclosed embodiments is assigned substantially only for the duration of the call or communication.
For an originated communication requiring routing to a party which needs a particular callback format not supported, e.g., by the originator, a
TempENUM service in accordance with the principles of the present invention assigns a callback identifier (ID) in a format consistent with that required by the receiving party.
Fig. 1 shows exemplary basic message flow relating to a Temp ENUM Gateway, in accordance with the principles of the present invention.
In particular, Fig. 1 shows a communicating party or originating entity 110 that places a call to a contacted entity or receiving party 120. The call is processed through an appropriate gateway provisioned to be a coordinator system 130.
Importantly, a temporary ENUM (TempENUM) service gateway 100 is implemented, including a TempENUM database 101, a module 102 that assigns a suitable TempENUM at the time of call routing, and a module 103 that handles a lookup in the TempENUM database 101 , and maps the assigned
TempENUM to a calling party identifier (CgPID).
The TempENUM database 101 stores a TempENUM assignment from the coordinator system 130 and relates the actual calling party identifier (CgPID) for use in callback attempts. In step 1 shown in Fig.1 , the originating party 110 attempts communication to a receiving party 120 that preferably receives the communication with an identifying ID used for re-contact, but the originating party's communication method is unable to provide that specific ID format. In step 2, the communication is routed to an appropriate temporary
ENUM numbering service, i.e., to the TempENUM service gateway 100. The temporary ENUM numbering service, or TempENUM service gateway 100, receives a temporary ID (Temp ENUM) from an appropriate module 102 that assigns a suitable TempENUM at the time of call routing, and routes the call. As shown in Fig. 1 , the module 102 is preferably part of a temporary ENUM service. Importantly, the temporary ID (or TempENUM) is consistent with the specific format required by the receiving party 120.
In step 3, the communication is routed to the receiving party 120 with an appropriate Temp ENUM specific to the format requirements of the receiving party 120.
In step 4, the receiving party 120 communicates with the originating party 110 substantially immediately after termination of a session. The receiving party 120 then uses the received TempENUM number to callback or re-initiate communication with the originating party 110 as required, e.g., within a predetermined time.
The callback communication attempt is directed to the TempENUM service gateway 100. In the given embodiments, the TempENUM service gateway 100 performs an appropriate authorization process intended to verify validity of the callback communication attempt back to the originating party 110. Validity may be based upon, e.g., the location of the communication attempt, date and time, etc.
If the re-initiated callback communication attempt is valid and authorized, then the TempENUM service gateway 100 correlates the TempENUM (i.e., temporary identifier) with the actual callback number or other communication identifier of the originating party 110. In step 5, the callback communication attempt by the receiving party 120 is completed back to the originating party 110.
Fig. 2 shows exemplary message flow relating to a temporary ENLJM service gateway in use with a roadside assistance/emergency relay center, in accordance with the principles of the present invention.
In particular, Fig. 2 shows interaction between an automobile equipped with a telematics system 210, its servicing telematics operations center 270, a coordinator system gateway 230, and a TempENUM service gateway 100. Otherwise conventional location elements are also accessed, including an emergency services gateway 250, a public safety access point 220, and an automatic location identifier (ALI) database 260.
The automobile 210 equipped with a suitable telematics system 210 (e.g., ONSTAR™ from General Motors™, TeleAID™ from Mercedes- Benz™, etc.) attempts to contact a public safety access point (PSAP) 220. In the given embodiment, the PSAP 220 is provided with a callback mechanism to reinitiate contact with the emergency caller 210 should the initial call be accidentally or unintentionally dropped.
An emergency relay center (e.g., ONSTAR™ telematics service center) 270 provides service to the automobile 210. The emergency relay center 270 passes an emergency call from the automobile 210 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 230. In the disclosed embodiment, the emergency call is passed to the coordinator system 230 together with a calling party identifier (CgPID) such as an agent ID, vehicle ID, etc., together with appropriate X, Y (latitude/longitude) positional information. As described with respect to the basic flow of Fig. 1 , the coordinator system 230 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID). The TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 230. Location of the automobile 210 is provided through the use of an emergency services routing number (ESRN) (e.g., in a switched network) or emergency services query key (ESQK) (e.g., in a voice over Internet Protocol (VoIP) network). An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 230, and either passes the ESQK on to the PSAP 220 (if in a VoIP network), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network).
The PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency caller 210. The ALI database 260 is updated with location information using an ESQK request to the coordinator system 230. The coordinator system 230 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the automobile 210, and the assigned TempENUM relating to the relevant emergency call.
Finally, as necessary (or desired), the receiving party (in this case the PSAP 220) attempts a callback communication to the originating party (in this case the automobile 210). This callback attempt is directed towards the TempENUM service gateway 100. The TempENUM service gateway 100 performs a lookup in the TempENUM database , and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM. The callback communications routed using the retrieved calling party identifier, which in this case directs the callback communication to the emergency relay center 270, which in turn passes the callback communication to the automobile 210.
Fig. 3 shows exemplary message flow relating to a temporary ENUM service gateway in use with Instant Messaging services, in accordance with the principles of the present invention.
In particular, Fig. 3 shows interaction between an instant messaging user 310, their servicing emergency services instant messaging (ESIM) user instance(s) 370, a coordinator system gateway 330, and a TempENUM service gateway 100. Otherwise conventional location elements are also accessed, including an emergency services gateway 250, a public safety access point 220, and an automatic location identifier (ALI) database 260. In the disclosed embodiment, the PSAP 220 is able to access relevant text and/or video from the instant messaging user 310 via an appropriate web portal 360.
The instant messaging user 310 sends an instant message with text, video or voice to an appropriate PSAP 220. In the given embodiment, the PSAP 220 is provided with a callback mechanism to reply to the instant messaging user 310.
Upon messaging, a relevant user instance (text, video or voice) is established in an appropriate emergency services instant messaging (ESIM) gateway 370. The text, video or voice instant message sent by the instant messaging user 310, or to the instant messaging user 310 from a suitable Internet host (e.g., a web portal 360), is also established in the emergency services instant messaging (ESIM) gateway 370.
The ESIM gateway 370 passes the instant message from the instant messaging user 310 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 330. In the disclosed embodiment, the emergency instant message is passed to the coordinator system 330 using a SIP INVITE command, together with a calling party identifier (CgPID) with LO.
As described with respect to the basic flow of Fig. 1 , the coordinator system 330 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID). The TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 330.
Location of the instant messaging user 310 is provided through the use of an emergency services routing number (ESRN) (e.g., in a switched network) or emergency services query key (ESQK) (e.g., over the Internet). An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 330, and either passes the ESQK on to the PSAP 220 (if over the Internet), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network). The PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency calling instant messaging user 310. The ALI database 260 is updated with location information using an ESQK request to the coordinator system 330. The coordinator system 330 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the instant messaging user 310, and the assigned TempENUM relating to the relevant emergency instant message.
Finally, as necessary (or desired), the receiving party (in this case the PSAP 220) attempts a callback communication to the originating party (in this case a return instant message to the instant messaging user 310). This return instant message is directed towards the TempENUM service gateway 100. The TempENUM service gateway 100 performs a lookup in the TempENUM database, and maps the provided TempENUM to the temporarily stored calling party identifier (in this case an instant messaging user identifier) associated with that TempENUM.
The return communication is routed using the retrieved calling party identifier, which in this case directs the return instant message to the emergency services instant messaging (ESIM) user instance(s) 370, and in turn passes the return instant message to the instant messaging user 310. Fig. 4 shows exemplary message flow relating to a temporary
ENUM service gateway in use with Peer-To-Peer voice provider services, in accordance with the principles of the present invention.
In particular, Fig. 4 shows interaction between a personal computer (PC) based VoIP application (e.g., Skype™) user 410, their servicing emergency services Skype™ (ESS) gateway including user instance(s) 470, a coordinator system gateway 430, and a TempENUM service gateway 100. Otherwise conventional location elements are also accessed, including an emergency services gateway 250, a public safety access point 220, and an automatic location identifier (ALI) database 260. The PC based VoIP application user 410 attempts to call via the
Internet an appropriate PSAP 220. In the given embodiment, the PSAP 220 is provided with a callback mechanism to reply to the PC based VoIP application user 410.
Upon initiation of a VoIP call, a relevant user instance (IN, OUT and NORM) is established in the PC hosting the VoIP application, as well as in an appropriate Emergency Services Skype (ESS) gateway 470.
The ESS gateway 470 passes the VoIP call from the Skype™ user 410 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 430. In the disclosed embodiment, the emergency VoIP call is passed to the coordinator system 430 using a SIP INVITE command, together with a calling party identifier (CgPID) with LO. Note that Skype™ users pass their North American Numbering Plan (NANP) calling party number (CgPN) to the coordinator system 430.
As described with respect to the basic flow of Fig. 1 , the coordinator system 430 initiates a TempENUM request to the TempENUM service gateway 100 including the calling party callback identifier (CgPID). The TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 430.
Location of the PC based VoIP application user 410 is provided through the use of an emergency services routing number (ESRN) (e.g., in a switched network) or emergency services query key (ESQK) (e.g., over the Internet). An emergency services gateway (ESGW) 250 receives the ESRN (or ESQK) from the coordinator system 330, and either passes the ESQK on to the PSAP 220 (if over the internet), or preferably converts the ESRN to an ESQK for passage to the PSAP 220 (in a switched network). The PSAP 220 queries an automatic location identifier (ALI) database 260 for the location of the emergency calling PC based VoIP application user 410. The ALI database 260 is updated with location information using an ESQK request to the coordinator system 430. The coordinator system 430 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the PC based VoIP application user 410, and the assigned TempENUM relating to the relevant emergency VoIP call. Finally, as necessary (or desired), the receiving party (in this case the PSAP 220) attempts a callback call to the originating party (in this case PC based VoIP application user 410). This callback call is directed towards the TempENUM service gateway 100. The TempENUM service gateway 100 performs a lookup in the TempENUM database, and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM.
The return communication is routed using the retrieved calling party identifier, which in this case directs the return call to the emergency services instant messaging (ESIM) user instance(s) 370, and in turn to the PC based VoIP application user 410.
Fig. 5 shows exemplary message flow relating to a temporary ENUM service gateway in use with wireless E9-1-1 services, in accordance with the principles of the present invention. In particular, Fig. 5 shows interaction between an international wireless caller 510 (e.g., a caller with a callback number that is larger or otherwise non-conforming to NANP 10-digit format), a servicing mobile switching center (MSC) 580, a coordinator system gateway 530, and a TempENUM service gateway 100. Otherwise conventional location elements are also accessed, including a public safety access point 220, and an automatic location identifier (ALI) database 260.
The international wireless caller 510 attempts to contact the appropriate public safety access point (PSAP) 220. In the given embodiment, the PSAP 220 is provided with a callback mechanism to re-initiate contact with the international wireless caller 510 as necessary or desired (e.g., should the initial call be accidentally or unintentionally dropped).
The mobile switching center (MSC) 580 provides service to the international wireless caller 510. The MSC 580 passes an emergency call from the international wireless cajler 510 to the appropriate PSAP 220 via an appropriate gateway provisioned as a coordinator system 530. In the disclosed embodiment, the emergency call is passed from the MSC 580 to the coordinator system 530 together with a calling party identifier (CgPID) such as a mobile directory number (MDN), together with appropriate X, Y (latitude/longitude) positional information.
As described with respect to the basic flow of Fig. 1 , the coordinator system 530 initiates a TempENUM request to the TempENUM service gateway
100 including the calling party callback identifier (CgPID). The TempENUM service gateway 100 assigns an appropriate TempENUM, which it passes back to the coordinator system 530.
Location of the international wireless caller 510 is provided through the use of an emergency services query key (ESQK). The coordinator system 530 requests assignment of the TempENUM from the TempENUM services gateway 100, and then passes the emergency call through to the PSAP 220 indicated by a query to the ALI database 260. The ALI database 260 provides the appropriate emergency services routing key (ESRK) to the PSAP 220. The ALI database 260 is updated with location information using an
ESQK request to the coordinator system 530. The coordinator system 530 responds to the PSAP 220 (via the ALI database 260) with current location information relating to the international wireless caller 510, and the assigned TempENUM relating to the relevant emergency call. Finally, as necessary (or desired), the receiving party (in this case the PSAP 220) attempts a callback communication to the originating party (in this case the wireless international caller 510). This callback attempt is directed towards the TempENUM service gateway 100. The TempENUM service gateway 100 performs a lookup in the TempENUM database , and maps the provided TempENUM to the temporarily stored calling party identifier associated with that TempENUM.
The callback communications are routed using the retrieved calling party identifier, which in this case means that the callback communication is directed to the MSC 580 servicing the international wireless caller 510, and ultimately to the international wireless caller 510. The present invention has particular applicability in the wireless E9- 1-1 market, including any US GSM carrier that supports PCS frequencies used by foreign markets. Other applications include roadside assistance/emergency relay centers, instant messaging providers, and peer-to-peer voice providers. There is also particular applicability with VoIP operators, particularly VoIP operators that support Mobile/Nomadic International subscribers, VoIP operators wishing to market International numbers for North American subscribers, and VoIP operators with subscribers that don't want to sign up in the ENUM directory.
While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims

CLAIMSWhat is claimed is:
1. An electronic numbering (ENUM) gateway, comprising: a temporary ENUM database associating a plurality of ENUMs with respective caller identity information; a module to assign a temporary ENUM at a time of routing a given communication, said temporary ENUM being an entry in said temporary ENUM database; and a module to lookup in said temporary ENUM database a given temporary ENUM and retrieve associated caller identity information.
2. The electronic numbering (ENUM) gateway according to claim 1 , wherein: said entry in said temporary ENUM database is a temporary entry that expires after a given amount of time after termination of said given communication.
3. The electronic numbering (ENUM) gateway according to claim 1 , wherein said caller identity information comprises: a phone number of a user initiating said given communication.
4. The electronic numbering (ENUM) gateway according to claim 3, wherein: said phone number does not conform to a 10-digit North American Numbering Plan phone number.
5. The electronic numbering (ENUM) gateway according to claim 3, wherein: said phone number includes a country code.
6. The electronic numbering (ENUM) gateway according to claim 1 , wherein said caller identity information comprises: an email address of a user initiating said given communication.
7. The electronic numbering (ENUM) gateway according to claim
1 , wherein said caller identity information comprises: an instant messaging address of a user initiating said given communication.
8. The electronic numbering (ENUM) gateway according to claim
1 , wherein said caller identity information comprises: a vehicle ID.
9. The electronic numbering (ENUM) gateway according to claim 1 , wherein said caller identity information comprises: a mobile directory number (MDN).
10. The electronic numbering (ENUM) gateway according to claim 1 , wherein: said temporary ENUM gateway forms a temporary ENUM service.
11. The electronic numbering (ENUM) gateway according to claim
I , wherein: said temporary ENUM conforms to requirements of a called party relating to calling party identification information.
12. The electronic numbering (ENUM) gateway according to claim
I I , wherein: said temporary ENUM conforms to 10-digit North American Numbering Plan requirements.
13. The electronic numbering (ENUM) gateway according to claim 1 , wherein: said given communication is an instant message.
14. The electronic numbering (ENUM) gateway according to claim
1 , wherein: said given communication is a phone call.
15. The electronic numbering (ENUM) gateway according to claim 14, wherein: said phone call is a wireless phone call.
16. The electronic numbering (ENUM) gateway according to claim 14, wherein: said phone call is a voice over Internet Protocol (VoIP) phone call.
17. A method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication, comprising: receiving a request for a temporary ENUM relating to a given communication, said temporary ENUM conforming to a format for calling party identity information as required by a called party; associating a temporary ENUM with caller identity information relating to a caller initiating said given communication; and storing said associated temporary ENUM as an entry in a temporary ENUM database.
18. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 17, further comprising: receiving a request to lookup a given temporary ENUM; and retrieving from said temporary ENUM database said caller identity information associated with said given temporary ENUM.
19. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 17, further comprising: routing a return communication from said called party back to said caller.
20. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 17, wherein: said temporary ENUM conforms to requirements of a called party relating to calling party identification information.
21. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 20, wherein: said temporary ENUM conforms to 10-digit North American
Numbering Plan requirements.
22. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 17, wherein: said received request includes calling party information
23. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 22, wherein said calling party information includes: a phone number.
24. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 22, wherein said calling party information includes: an instant message IP address.
25. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 22, wherein said calling party information includes: a phone number.
26. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 22, wherein said calling party information includes: a mobile directory number (MDN).
27. The method of temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 22, wherein said calling party information includes: an email address.
28. Apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication, comprising: means for receiving a request for a temporary ENUM relating to a given communication, said temporary ENUM conforming to a format for calling party identity information as required by a called party; means for associating a temporary ENUM with caller identity information relating to a caller initiating said given communication; and means for storing said associated temporary ENUM as an entry in a temporary ENUM database.
29. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 28, further comprising: means for receiving a request to lookup a given temporary ENUM; and means for retrieving from said temporary ENUM database said caller identity information associated with said given temporary ENUM.
30. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 28, further comprising: means for routing a return communication from said called party back to said caller.
31. The apparatus for temporarily associating an electronic number (ENLJM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 28, wherein: said temporary ENLJM conforms to requirements of a called party relating to calling party identification information.
32. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 31 , wherein: said temporary ENUM conforms to 10-digit North American Numbering Plan requirements.
33. The apparatus for temporarily associating an electronic number
(ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 28, wherein: said received request includes calling party information
34. The apparatus for temporarily associating an electronic number
(ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 33, wherein said calling party information includes: a phone number.
35. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 33, wherein said calling party information includes: an instant message IP address.
36. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 33, wherein said calling party information includes: a phone number.
37. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 33, wherein said calling party information includes: a mobile directory number (MDN).
38. The apparatus for temporarily associating an electronic number (ENUM) to a given communication for a short period of time contemporaneous with transmission of said given communication according to claim 33, wherein said calling party information includes: an email address.
PCT/US2006/013233 2005-04-12 2006-04-10 Temporary enum gateway WO2006110620A2 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
MX2007012683A MX2007012683A (en) 2005-04-12 2006-04-10 Temporary enum gateway.
BRPI0610718-4A BRPI0610718A2 (en) 2005-04-12 2006-04-10 electronic numbering port and method and to temporarily associate an electronic numbering with a given communication
CN2006800190298A CN101518042B (en) 2005-04-12 2006-04-10 Temporary enum gateway
EP06769809A EP1932330A4 (en) 2005-04-12 2006-04-10 Temporary enum gateway
CA2604211A CA2604211C (en) 2005-04-12 2006-04-10 Temporary enum gateway
JP2008506561A JP5155151B2 (en) 2005-04-12 2006-04-10 Temporary ENUM gateway
AU2006235297A AU2006235297B2 (en) 2005-04-12 2006-04-10 Temporary ENUM gateway

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US67027905P 2005-04-12 2005-04-12
US60/670,279 2005-04-12

Publications (3)

Publication Number Publication Date
WO2006110620A2 WO2006110620A2 (en) 2006-10-19
WO2006110620A9 true WO2006110620A9 (en) 2007-01-11
WO2006110620A3 WO2006110620A3 (en) 2007-07-19

Family

ID=37087581

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/013233 WO2006110620A2 (en) 2005-04-12 2006-04-10 Temporary enum gateway

Country Status (10)

Country Link
US (4) US7852834B2 (en)
EP (1) EP1932330A4 (en)
JP (1) JP5155151B2 (en)
CN (1) CN101518042B (en)
AU (1) AU2006235297B2 (en)
BR (1) BRPI0610718A2 (en)
CA (1) CA2604211C (en)
MX (1) MX2007012683A (en)
RU (1) RU2412552C2 (en)
WO (1) WO2006110620A2 (en)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101518042B (en) 2005-04-12 2013-06-12 电信系统有限公司 Temporary enum gateway
US7400876B2 (en) * 2005-08-01 2008-07-15 General Motors Corporation Method and system for providing telematics unit information
US8537974B2 (en) * 2005-10-05 2013-09-17 Intrado, Inc. System and method for facilitating emergency calling from a remote terminal
US8009808B2 (en) * 2005-10-05 2011-08-30 Intrado Inc. System and method for maintaining a translations database to effect call control at a remote terminal
US8190196B2 (en) * 2005-12-29 2012-05-29 Patent Navigation Inc. Generation and use of temporary phone numbers
GB2443889A (en) 2006-11-20 2008-05-21 Skype Ltd Method and system for anonymous communication
GB0623622D0 (en) * 2006-11-27 2007-01-03 Skype Ltd Communication system
GB0623621D0 (en) * 2006-11-27 2007-01-03 Skype Ltd Communication system
GB2448689A (en) * 2007-04-23 2008-10-29 Tyntec Ltd Unified reception and processing of multi-protocol communication services
US9049209B2 (en) * 2007-05-08 2015-06-02 At&T Intellectual Property I, L.P. Methods and apparatus to route a communication session in an internet protocol (IP) multimedia subsystem (IMS) network
US8830987B2 (en) * 2007-06-07 2014-09-09 Solacom Technologies Inc. IP-based call answering point selection and routing
US10027805B2 (en) * 2007-11-26 2018-07-17 General Motors Llc Connection management for a vehicle telematics unit
US20090149205A1 (en) * 2007-12-10 2009-06-11 Zipit Wireless Inc. System And Method For Regulating Data Messaging Between A Wireless Device And A Mobile Communication Device Using Short Message Service
US8737948B2 (en) * 2008-04-04 2014-05-27 West Corporation Providing temporary callback number for emergency calls
CN101635691B (en) * 2008-07-21 2012-02-15 中国电信股份有限公司 Network faxing method, interface equipment and service system
US8693976B2 (en) * 2008-08-28 2014-04-08 At&T Mobility Ii Llc Preferential treatment for emergency callback
DE202010008028U1 (en) 2009-07-18 2010-12-30 Weidmüller Interface GmbH & Co. KG Connection device for conductors
US20120157795A1 (en) * 2010-12-15 2012-06-21 Ross Medical Corporation Patient Emergency Response System
US8369488B2 (en) 2011-03-15 2013-02-05 At&T Mobility Ii Llc Triggering a 911 voice call from a non-voice message
CN105847295B (en) * 2011-04-20 2019-05-17 瑞典爱立信有限公司 For establishing the method and server of the communication for not providing caller identity in the telecommunication system
US20130254830A1 (en) * 2012-03-22 2013-09-26 Madhav Moganti Apparatus and method for assuring communications of corporate users
JP2013211686A (en) * 2012-03-30 2013-10-10 Brother Ind Ltd Server device, program, and information processing method
US10097979B2 (en) 2014-11-24 2018-10-09 Qualcomm Incorporated Location by reference for an over-the-top emergency call
US9756664B2 (en) * 2014-11-24 2017-09-05 Qualcomm Incorporated Methods of supporting location and emergency calls for an over-the-top service provider
GB2542823A (en) * 2015-09-30 2017-04-05 British Telecomm Data communications
EP3357211B1 (en) 2015-09-30 2019-08-14 British Telecommunications public limited company Data communications
US10863025B2 (en) * 2017-05-25 2020-12-08 T-Mobile Usa, Inc. Efficient robocall/scam identification with verification function
CN109788148B (en) * 2017-11-10 2021-08-17 中国电信股份有限公司 Communication method, device and service platform
RU2754606C1 (en) * 2020-08-13 2021-09-03 Алексей Олегович Пташный Method for identifying the service in the enum structure

Family Cites Families (117)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4625081A (en) * 1982-11-30 1986-11-25 Lotito Lawrence A Automated telephone voice service system
US5712900A (en) * 1996-05-21 1998-01-27 Ericsson, Inc. Emergency call back for roaming mobile subscribers
US6038437A (en) * 1997-02-13 2000-03-14 Gte Mobilnet Service Corp. Call-back method in response to emergency call originating from cellular radiotelephone
US6275937B1 (en) * 1997-11-06 2001-08-14 International Business Machines Corporation Collaborative server processing of content and meta-information with application to virus checking in a server network
US6535743B1 (en) * 1998-07-29 2003-03-18 Minorplanet Systems Usa, Inc. System and method for providing directions using a communication network
US6438223B1 (en) * 1999-03-03 2002-08-20 Open Telephone Network, Inc. System and method for local number portability for telecommunication networks
WO2001017302A1 (en) * 1999-08-30 2001-03-08 Swisscom Mobile Ag Emergency call system within a telecommunication network
WO2001054021A1 (en) * 2000-01-18 2001-07-26 Richard Liming System and method providing a spatial location context
US6556816B1 (en) * 2000-01-31 2003-04-29 Lucent Technologies Inc. Method and apparatus for re-establishing a call in a communication system
US6415018B1 (en) * 2000-02-08 2002-07-02 Lucent Technologies Inc. Telecommunication system and method for handling special number calls having geographic sensitivity
CA2303739C (en) * 2000-04-04 2009-06-30 Webhancer Corporation Method and system for managing performance of data transfers for a data access system
US6675017B1 (en) 2000-06-30 2004-01-06 Bellsouth Intellectual Property Corporation Location blocking service for wireless networks
US20020113797A1 (en) * 2000-11-17 2002-08-22 Potter Scott T. Systems and methods for representing and displaying graphics
US20020099802A1 (en) * 2000-11-29 2002-07-25 Marsh Thomas Gerard Computer based training system and method
CN1156751C (en) * 2001-02-02 2004-07-07 国际商业机器公司 Method and system for automatic generating speech XML file
US6571092B2 (en) * 2001-02-15 2003-05-27 Nokia Networks Oy Technique for enabling emergency call callback of a terminal without a valid subscriber identity
US20030119490A1 (en) * 2001-02-26 2003-06-26 Jahangir Mohammed Wireless communications handset for facilitating licensed and unlicensed wireless communications, and method of operation
US6757359B2 (en) * 2001-03-23 2004-06-29 Siemens Information And Communication Networks, Inc. Methods and apparatus for transmitting accurate emergency location identification numbers (ELINs) from behind a multi-line telephone system (MLTS) utilizing port equipment numbers
US20020141386A1 (en) * 2001-03-29 2002-10-03 Minert Brian D. System, apparatus and method for voice over internet protocol telephone calling using enhanced signaling packets and localized time slot interchanging
JP2002320115A (en) * 2001-04-24 2002-10-31 Olympus Optical Co Ltd Digital camera and digital imaging system
US7340438B2 (en) 2001-05-21 2008-03-04 Nokia Corporation Method and apparatus for managing and enforcing user privacy
US6678357B2 (en) * 2001-09-26 2004-01-13 Siemens Information And Communication Networks, Inc. Internet protocol (IP) emergency connections (ITEC) telephony
US7269249B2 (en) 2001-09-28 2007-09-11 At&T Bls Intellectual Property, Inc. Systems and methods for providing user profile information in conjunction with an enhanced caller information system
JP4160506B2 (en) * 2001-09-28 2008-10-01 レヴェル ３ シーディーエヌ インターナショナル インコーポレーテッド． Configurable adaptive wide area traffic control and management
US7233781B2 (en) * 2001-10-10 2007-06-19 Ochoa Optics Llc System and method for emergency notification content delivery
US20030125493A1 (en) * 2001-10-26 2003-07-03 Harris Stephen H. (Meth)acrylates of oxyalkylated phenolic resins and their use as adhesion promoters
US6839421B2 (en) * 2001-10-29 2005-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus to carry out resolution of entity identifier in circuit-switched networks by using a domain name system
US7516198B1 (en) 2001-10-30 2009-04-07 Cisco Technology, Inc. Arrangement for providing content-based quality of service for a service flow based on parsing XML tags detected from a server response to a client request
US6879677B2 (en) * 2001-11-01 2005-04-12 Callwave, Inc. Methods and systems for telephony call completion
US8705710B2 (en) * 2001-11-01 2014-04-22 Callwave Communications, Llc Methods and systems for telephony call completion
US6771742B2 (en) * 2001-11-05 2004-08-03 Intrado Inc. Geographic routing of emergency service call center emergency calls
US20040064500A1 (en) * 2001-11-20 2004-04-01 Kolar Jennifer Lynn System and method for unified extraction of media objects
US7380022B2 (en) * 2001-12-28 2008-05-27 Motorola, Inc. Method and apparatus for transmitting wired data voice over IP data and wireless data through a common IP core network
US6865266B1 (en) * 2002-01-16 2005-03-08 Verizon Services Corp. Methods and apparatus for transferring from a PSTN to a VOIP telephone network
US6925504B1 (en) * 2002-01-31 2005-08-02 Cisco Technology, Inc. Methods and apparatus for obtaining content from a content-originating device within a computerized network
US20030163483A1 (en) 2002-02-19 2003-08-28 Abraham Zingher Method and system for a data service to control access to personal information
US8126889B2 (en) 2002-03-28 2012-02-28 Telecommunication Systems, Inc. Location fidelity adjustment based on mobile subscriber privacy profile
US6922565B2 (en) * 2002-03-28 2005-07-26 Telecommunication Systems, Inc. Public safety access point (PSAP) selection for E911 wireless callers in a GSM type system
US20030222901A1 (en) * 2002-05-28 2003-12-04 Todd Houck uPrime uClient environment
FR2841072A1 (en) * 2002-06-14 2003-12-19 France Telecom System for consulting and updating DNS servers and LDAP directories, includes using protocol management unit for searching IP address of server hosting first database and transmitting request for reading and updating record to server
US20060184617A1 (en) * 2005-02-11 2006-08-17 Nicholas Frank C Method and system for the creating, managing, and delivery of feed formatted content
US7203502B2 (en) * 2002-06-14 2007-04-10 Cingular Wireless Ii, Llc System for providing location-based services in a wireless network, such as locating individuals and coordinating meetings
US6721396B2 (en) 2002-06-26 2004-04-13 Lucent Technologies Inc. Method and system of enhancing emergency call services
EP1522198B1 (en) * 2002-07-16 2010-08-25 Nokia Corporation Optimized routing between communication networks
US20040203568A1 (en) * 2002-07-20 2004-10-14 Kirtland Kenneth P. Computerized warning system interface and method
US7668543B2 (en) 2002-08-14 2010-02-23 Nokia Siemens GmbH & Co. KG Treatment of a location request by a first location request treatment device (a gateway mobile location centre) in a home register (HLR) for retransmission to a second location request treatment device
US7953423B2 (en) * 2002-10-18 2011-05-31 Kineto Wireless, Inc. Messaging in an unlicensed mobile access telecommunications system
US7873015B2 (en) * 2002-10-18 2011-01-18 Kineto Wireless, Inc. Method and system for registering an unlicensed mobile access subscriber with a network controller
US7640008B2 (en) * 2002-10-18 2009-12-29 Kineto Wireless, Inc. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7349698B2 (en) * 2002-10-18 2008-03-25 Kineto Wireless, Inc. Registration messaging in an unlicensed mobile access telecommunications system
US7885644B2 (en) * 2002-10-18 2011-02-08 Kineto Wireless, Inc. Method and system of providing landline equivalent location information over an integrated communication system
US7369859B2 (en) * 2003-10-17 2008-05-06 Kineto Wireless, Inc. Method and system for determining the location of an unlicensed mobile access subscriber
US7332265B2 (en) * 2002-11-08 2008-02-19 Fujifilm Corporation Silver halide color photographic light-sensitive material, and image-forming method
US7617287B2 (en) * 2002-11-27 2009-11-10 Rga Intl, Inc. Cellular messaging alert method and system
US20040107143A1 (en) * 2002-11-29 2004-06-03 Aki Niemi Method for authorizing indirect content download
US7296295B2 (en) * 2002-12-11 2007-11-13 Broadcom Corporation Media processing system supporting different media formats via server-based transcoding
ATE350874T1 (en) * 2003-01-21 2007-01-15 Research In Motion Ltd METHOD AND DEVICE FOR INCREASE THE PROBABILITY OF SUCCESSFULLY ESTABLISHING EMERGENCY CALL CONNECTIONS IN A MOBILE STATION
US8050281B2 (en) * 2003-01-31 2011-11-01 Qwest Communications International Inc. Alert gateway, systems and methods
US8490129B2 (en) * 2003-01-31 2013-07-16 Qwest Communications International Inc. Methods, systems and apparatus for selectively distributing urgent public information
US7194249B2 (en) * 2003-01-31 2007-03-20 Qwest Communications International Inc. Methods, systems and apparatus for providing urgent public information
US20040156394A1 (en) * 2003-02-10 2004-08-12 Ilkka Westman Handling of user identity
US7945511B2 (en) * 2004-02-26 2011-05-17 Payment Pathways, Inc. Methods and systems for identity authentication
US7031724B2 (en) * 2003-03-12 2006-04-18 General Motors Corporation Location-based services for a telematics service subscriber
US6963557B2 (en) * 2003-03-29 2005-11-08 Intrado Inc. System and method for routing telephone calls involving internet protocol network
US20040247090A1 (en) * 2003-06-05 2004-12-09 Nurmela Wayne Denis Process for providing alert notification to communication devices
US7627338B2 (en) * 2003-06-06 2009-12-01 At&T Intellectual Property I, L.P. System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed spectrum and wired access with licensed spectrum
US7664233B1 (en) * 2003-06-25 2010-02-16 Everbridge, Inc. Emergency and non-emergency telecommunications notification system
US7177623B2 (en) * 2003-07-02 2007-02-13 The United States Of America As Represented By The Secretary Of The Army Localized cellular awareness and tracking of emergencies
US7174149B2 (en) * 2003-07-14 2007-02-06 Lucent Technologies Inc. Method and system for indirectly establishing a call
JP4842814B2 (en) * 2003-08-07 2011-12-21 テルコーディア ライセンシング カンパニー， リミテッド ライアビリティ カンパニー Dial-out voice notification system
US7441203B2 (en) * 2003-08-11 2008-10-21 Core Mobility, Inc. Interactive user interface presentation attributes for location-based content
US20050039135A1 (en) * 2003-08-11 2005-02-17 Konstantin Othmer Systems and methods for navigating content in an interactive ticker
KR100703264B1 (en) * 2003-08-29 2007-04-03 삼성전자주식회사 Method and system for providing voice and data services in mobile communication system overlaped by various access networks
US7780692B2 (en) * 2003-12-05 2010-08-24 Onset Medical Corporation Expandable percutaneous sheath
JP4279135B2 (en) * 2003-12-26 2009-06-17 パナソニック株式会社 Home gateway device
US7542558B2 (en) * 2004-02-20 2009-06-02 Avaya Inc. Informing caller of callee activity mode
US20050188078A1 (en) * 2004-02-23 2005-08-25 Kotzin Michael D. System and method for managing and associating dynamic containers of a content providing device
US7177399B2 (en) * 2004-02-27 2007-02-13 Nortel Network Limited Determining the geographical location from which an emergency call originates in a packet-based communications network
CA2498641C (en) * 2004-02-27 2012-10-30 Oz Communications Interworking gateway and method
US7702308B2 (en) * 2004-03-11 2010-04-20 Alcatel-Lucent Usa Inc. Method of associating data with a call to a call center
US20050201358A1 (en) * 2004-03-13 2005-09-15 Intrado Inc. Rotating media channels between resources of an emergency services network and conforming emergency systems
US7242923B2 (en) * 2004-03-23 2007-07-10 Motorola, Inc. System and method for authenticating wireless device with fixed station
US7450696B2 (en) * 2004-05-11 2008-11-11 At&T Intellectual Property I, L.P. Knowledge management, capture and modeling tool for multi-modal communications
US7764944B2 (en) * 2004-06-24 2010-07-27 Alcatel-Lucent Usa Inc. Method of providing a unique call back number for wireless 9-1-1 calls
US7424282B2 (en) * 2004-08-26 2008-09-09 Sprint Spectrum L.P. Method and system for delivering photos to called destinations
JP2008515282A (en) * 2004-09-22 2008-05-08 シーメンス コミュニケイションズ インコーポレイテッド Pseudo number portability in FMC with one number
US20060072547A1 (en) * 2004-09-29 2006-04-06 Lucent Technologies Inc. Systems and methods for serving VolP emergency calls
US7957723B2 (en) * 2004-10-01 2011-06-07 Nokia Corporation Sharing information feed data
US7627108B1 (en) * 2004-10-25 2009-12-01 At&T Mobility Ii Llc Systems and methods for providing ENUM in an LNP environment
GB0424052D0 (en) * 2004-10-29 2004-12-01 Nortel Networks Ltd Improvements in or relating to internet protocol (IP) location, privacy and presence
US8804653B2 (en) * 2005-01-13 2014-08-12 Telefonaktiebolaget Lm Ericsson (Publ) System and method for call handoff between circuit switched and packet data wireless networks
EP1839420B1 (en) * 2005-01-19 2018-04-04 Telefonaktiebolaget LM Ericsson (publ) A method and apparatus for handling emergency calls
US8700729B2 (en) * 2005-01-21 2014-04-15 Robin Dua Method and apparatus for managing credentials through a wireless network
US7715821B2 (en) * 2005-02-18 2010-05-11 Alcatel-Lucent Usa Inc. Method of updating a unique call back number for a wireless emergency call
US7565131B2 (en) * 2005-03-08 2009-07-21 Alcatel-Lucent Usa Inc. Emergency call back through intersystem paging
US20060206610A1 (en) * 2005-03-09 2006-09-14 Yibei Ling Method, system and apparatus for location-aware content push service and location-based dynamic attachment
CN101518042B (en) * 2005-04-12 2013-06-12 电信系统有限公司 Temporary enum gateway
US7684782B2 (en) * 2005-04-13 2010-03-23 Wirelesswerx International, Inc. Method and system for initiating and handling an emergency call utilizing geographical zones
US7864673B2 (en) * 2005-05-24 2011-01-04 At&T Mobility Ii Llc Dynamic dual-mode service access control, location-based billing, and E911 mechanisms
US20060293024A1 (en) * 2005-06-23 2006-12-28 Lucent Technologies Inc. Methods and apparatus for improved 911 support for VoIP service
US7822391B1 (en) 2005-06-30 2010-10-26 Sprint Spectrum L.P. Mobile station emergency beacon system
US20070027997A1 (en) * 2005-07-29 2007-02-01 Cisco Technology, Inc. Technique for translating location information
US10178522B2 (en) * 2005-08-02 2019-01-08 Qualcomm Incorporated VoIP emergency call support
WO2007025227A2 (en) 2005-08-25 2007-03-01 Tele-Guia Talking Yellow Pages, Inc Enhanced 911 system and method for operating the same
US7843903B2 (en) * 2005-11-04 2010-11-30 Broadsoft M6, Llc Methods, systems, and computer program products for emergency 911 (E911) registration assistance for subscribers using portable internet protocol (IP) communications devices
US8150363B2 (en) * 2006-02-16 2012-04-03 Telecommunication Systems, Inc. Enhanced E911 network access for call centers
US8059789B2 (en) 2006-02-24 2011-11-15 Telecommunication Systems, Inc. Automatic location identification (ALI) emergency services pseudo key (ESPK)
US8417285B2 (en) * 2006-03-17 2013-04-09 At&T Mobility Ii Llc Mobility management message analysis
US8442482B2 (en) 2006-05-16 2013-05-14 RedSky Technologies, Inc. Method and system for an emergency location information service (E-LIS)
US8204520B2 (en) * 2006-06-02 2012-06-19 West Corporation System and method for routing short message service special number messages to local special number answering points
US7719414B1 (en) * 2006-08-16 2010-05-18 Cingular Wireless Ii, Llc Electronic medic alert
US20080080488A1 (en) * 2006-09-28 2008-04-03 Tekelec Methods, systems, and computer program products for enabling short code dialing in an ENUM environment
US8050386B2 (en) 2007-02-12 2011-11-01 Telecommunication Systems, Inc. Mobile automatic location identification (ALI) for first responders
US8269607B2 (en) 2008-03-18 2012-09-18 West Corporation Proximity location system and method thereof for locating a communications device
US9143611B2 (en) * 2008-09-30 2015-09-22 International Business Machines Corporation System and method for routing calls
US8396445B2 (en) 2009-03-12 2013-03-12 At&T Intellectual Property I, L.P. Method to implement E911 services in IMS (IP Multimedia Subsystem)
CA2697986C (en) 2009-03-30 2018-05-15 Rave Wireless, Inc. Emergency information services

Also Published As

Publication number Publication date
US20060227959A1 (en) 2006-10-12
US9407774B2 (en) 2016-08-02
RU2007141703A (en) 2009-05-20
BRPI0610718A2 (en) 2010-07-20
EP1932330A4 (en) 2011-05-04
EP1932330A2 (en) 2008-06-18
AU2006235297B2 (en) 2010-05-27
CN101518042A (en) 2009-08-26
WO2006110620A2 (en) 2006-10-19
JP5155151B2 (en) 2013-02-27
US20110081010A1 (en) 2011-04-07
CA2604211C (en) 2013-12-03
MX2007012683A (en) 2008-01-11
WO2006110620A3 (en) 2007-07-19
US8644302B2 (en) 2014-02-04
CA2604211A1 (en) 2006-10-19
RU2412552C2 (en) 2011-02-20
JP2008536455A (en) 2008-09-04
CN101518042B (en) 2013-06-12
US20160182730A1 (en) 2016-06-23
US20140140248A1 (en) 2014-05-22
US7852834B2 (en) 2010-12-14
AU2006235297A1 (en) 2006-10-19

Similar Documents

Publication Publication Date Title
US9407774B2 (en) Temporary enum gateway
US7522931B2 (en) Method and apparatus for accessing a network computer to establish a push-to-talk session
JP4886727B2 (en) Providing routing information in communication systems
US20060153172A1 (en) Emergency call system and emergency call method
WO2007056186A2 (en) Emergency services directory number registartion assistance for subscribers using portable internet protocol (ip) communications devices
JP2013513278A (en) System and method for multimedia emergency access in a wireless network
EP1908320B1 (en) Private routing control numbers
US20080267167A1 (en) System and method for set up of an ip communication to the origin of a circuit switched call
CN102144379A (en) TEL URI handling method and apparatus
EP3329457B1 (en) Conveying device information to application server servicing computing device associated with a communication
US7813737B1 (en) Integrated digital enhanced network migrated subscriber mapping
CN110267360B (en) International roaming communication method, international gateway and communication system for group service
CN110324812B (en) International roaming communication method, international gateway, application server and communication system
KR101129838B1 (en) Apparatus and method for performing video communication
KR20020086993A (en) A method for terminating call of a subscribed mobile having a plurality of ID in next generations mobile telecommunication network

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680019029.8

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
REEP Request for entry into the european phase

Ref document number: 2006769809

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006769809

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2604211

Country of ref document: CA

Ref document number: 2008506561

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2006235297

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: MX/a/2007/012683

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 8061/DELNP/2007

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2006235297

Country of ref document: AU

Date of ref document: 20060410

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2007141703

Country of ref document: RU

ENP Entry into the national phase

Ref document number: PI0610718

Country of ref document: BR

Kind code of ref document: A2

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)