WO2007011861A2 - Integrated services user part (isup)/session initiation protocol (sip) gateway for unlicensed mobile access (uma) emergency services call flow - Google Patents
Integrated services user part (isup)/session initiation protocol (sip) gateway for unlicensed mobile access (uma) emergency services call flow Download PDFInfo
- Publication number
- WO2007011861A2 WO2007011861A2 PCT/US2006/027658 US2006027658W WO2007011861A2 WO 2007011861 A2 WO2007011861 A2 WO 2007011861A2 US 2006027658 W US2006027658 W US 2006027658W WO 2007011861 A2 WO2007011861 A2 WO 2007011861A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- encapsulated
- uma
- made via
- isup
- party number
- Prior art date
Links
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
- G01S5/0009—Transmission of position information to remote stations
- G01S5/0018—Transmission from mobile station to base station
-
- 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/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
-
- 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/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/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- 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/42348—Location-based services which utilize the location information of a target
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1225—Details of core network interconnection arrangements
- H04M7/123—Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/025—Services making use of location information using location based information parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/04—Special services or facilities for emergency applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/14—Special services or facilities with services dependent on location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- This invention relates generally to wireless telecommunication. More particularly, it relates to Voice Over Internet Protocol (VoIP) E9-1-1 call flows supporting unlicensed mobile access (UMA).
- VoIP Voice Over Internet Protocol
- UMA unlicensed mobile access
- Unlicensed Mobile Access is the Third Generation Partnership (3GPP) standard for cellular and wireless fidelity (WiFi) convergence.
- 3GPP Third Generation Partnership
- WiFi wireless fidelity
- the UMA specifications are publicly available, e.g., from the UMA Technology web site (www.umatechnology.org) as well as from the 3GPP web site (www.3gpp.org).
- the UMA effort was initiated by leading operators and vendors in the wireless industry, with a goal of developing a set of technical specifications for extending mobile voice, data and IP Multimedia Subsystem (IMS) services over broadband IP and Wi-Fi access networks.
- IMS IP Multimedia Subsystem
- the specifications were officially incorporated into 3GPP Release 6, making UMA the true global standard for cellular/Wi-Fi convergence.
- the UMA effort has been a tremendous success, having developed a new global communications standard in a period of less than 15 months.
- UMA provides a secure, managed IP connection established between a mobile handset and the operator's core network.
- all of an operator's mobile services (voice, data, and IMS) are available to the subscriber when connected via Wi-Fi.
- active voice calls and data sessions are automatically handed over between networks as subscribers come in and out of range of WLANs.
- Wi-Fi no longer poses a threat to mobile operators because they maintain control of their subscribers and services even when connected via Wi-Fi.
- Some GSM carriers have followed different implementations of the UMA E9-1-1 call flow.
- at least one carrier e.g., T-MobileTM
- T-MobileTM has implemented an approach utilizing a serving mobile location center (SMLC).
- SMLC serving mobile location center
- disadvantages with such conventional solutions include the fact that switching E9-1-1 calls back to a time division multiplexed (TDM) system may cause those calls to drop in houses having poor cellular coverage.
- TDM time division multiplexed
- a method and apparatus for providing location based support to a call made via a UMA network comprises encapsulating a location request with respect to a call from a UMA phone.
- the location request is received by an ISUP/SIP gateway and encapsulated in a SIP message.
- the SIP encapsulated location request is passed to a VoIP positioning center.
- an architecture link between a mobile switching center (MSC) and a VoIP positioning center (VPC) to support location based services comprises an SS7 based ISUP/SIP gateway.
- the ISUP/SIP gateway is operable to encapsulate a received location request into an Internet Protocol message.
- FIG. 1 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow through an ISUP/SIP gateway implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC), in accordance with the principles of the present invention.
- MSC mobile switching center
- VPC VoIP positioning center
- Fig. 2 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from an ISUP/SIP gateway using inband or out of band access point MAC address to address lookup, in accordance with the principles of the present invention.
- Fig. 3 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an E5+ position determination entity (PDE) lookup, in accordance with the principles of the present invention.
- PDE position determination entity
- Fig. 4 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an Lg PSL for location lookup, in accordance with the principles of the present invention.
- Fig. 5 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or a WiFi location query, in accordance with the principles of the present invention.
- Fig. 6 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or MPC Lg interface to the MSC lookup, in accordance with the principles of the present invention.
- Fig. 7 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or E5+, or Lg interface to the MSC lookup, in accordance with the principles of the present invention.
- Fig. 8 shows exemplary call flow between a wireless mobile station, a UMA network controller (UNC)/mobile switching center (MSC), an ISUP/SIP gateway in accordance with the present invention, a VoIP positioning center
- VPC public safety answering point
- PSAP public safety answering point
- ESNE electronic mail network equipment
- An ISUP/SIP gateway is implemented to encapsulate SS7 location requests from a switched telephone network into an Internet protocol SIP message including one or more location objects.
- the ISUP/SIP gateway is implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC) to provide support of unlicensed mobile access (UMA) voice over Internet Protocol (VoIP) call routing, e.g., for E9-1-1 , 4-1-1 , 2-1-1 , etc.
- UMA unlicensed mobile access
- VoIP voice over Internet Protocol
- the disclosed location objects that are encapsulated into a SIP message includes calling party number, called party number, CGI, International Mobile Subscriber Identity (IMSI), mobility indicator, and/or access point MAC address.
- IMSI International Mobile Subscriber Identity
- IMSI International Mobile Subscriber Identity
- the SIP encapsulated location request message is then routed over the Internet to a destination VoIP positioning center (VPC).
- Session Initiation Protocol is an application-layer control protocol that is conventionally used to establish, modify and terminate multimedia sessions or calls over the Internet. These multimedia sessions include multimedia conferences, Internet telephony and similar applications. SIP is one of the key protocols used to implement Voice over IP (VoIP).
- VoIP Voice over IP
- SIP-ISUP gateways that interwork between the public switched telephone network (PSTN) and SIP networks has motivated the publication of a set of common practices that can assure consistent behavior across implementations.
- An important basic requirement of these common practices is that the SIP telephone network be feature transparent with respect to the PSTN.
- signaling system number 7 (SS7) integrated services user part (ISUP) messages consistent with the PSTN are encapsulated within SIP in such a way as to not discard in the SIP request information necessary for services.
- the encapsulated message is then routed over the Internet to a destination VoIP device.
- SS7 signaling system number 7
- ISUP integrated services user part
- SIP headers to indicate how the SIP request is to be routed.
- the present invention implements an ISUP/SIP gateway, but not in a conventional manner to pass SS7 signaling from a switched telephone network over the Internet. Rather, the present invention implements an ISUP/SIP gateway between a mobile switching center (MSC) and a VoIP positioning center (VPC) to provide support of unlicensed mobile access (UMA) voice over Internet Protocol (VoIP) call routing, e.g., for E9-1-1 , 4-1-1 , 2-1-1 , etc.
- MSC mobile switching center
- VPC VoIP positioning center
- UMA unlicensed mobile access
- VoIP voice over Internet Protocol
- Fig. 1 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow through an ISUP/SIP gateway implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC), in accordance with the principles of the present invention.
- MSC mobile switching center
- VPC VoIP positioning center
- a dual-mode phone user makes use of a wireless device including a dual-mode phone user agent 110.
- Wireless communication is established with a UMA network controller (UNC) 114 via a WiFi access point 112.
- UDC UMA network controller
- An emergency call is routed to a mobile switching center (MSC) 102, which in turn routes the emergency call to a public safety answering point (PSAP) 118 via a selective router 116.
- the dual-mode phone user provisions the dual-mode phone via a suitable user provisioning system 128.
- Location based services are provided by a VoIP positioning center (VPC) 104, an automated location identification (ALI)
- VDB validation database
- MSAG master street address guide
- LIS/SLDB location information server/subscriber line database
- an SS7 based ISUP/SIP gateway 100 is implemented between the MSC 102 and the VoIP positioning center 104.
- the ISUP/SIP gateway 100 in accordance with the present invention converts ISUP IAM parameters to SIP V6 parameters, the V6 interface being per NENA i2 definitions.
- the ISUP/SIP gateway 100 converts from V4 parameters to ISUP signaling, the V4 interface being per NENA ⁇ 2 definitions.
- a WiFi access point hexadecimal MAC address is converted into decimal format and transmitted in an ISUP initial address message (IAM) parameter.
- IAM ISUP initial address message
- a flag is included to indicate locateability of the handset or softphone.
- a wireless carrier Using the ISUP/Session Initiation Protocol (SIP) gateway 100, a wireless carrier is able to integrate their message servicing center (MSC) 102 across an SS7 network using standardized V6/V4 i2 call flows via ISUP signaling from ISUP loop-back trunks to a switching control point (SCP).
- SCP switching control point
- the MSC 102 implements translations that support i2 emergency services query key (ESQK)/emergency services routing number (ESRN) based call flows to an emergency services routing key (ESRK)/Trunk Select type call flow.
- the MSC 102 also preferably supports last routing option (LRO) i1 based call flows.
- the MSC 102 also preferably supports modified LRO to an operator routing support service (ORSS) (i.e., a private call center) i1 call flow.
- ORSS operator routing support service
- a wireless carrier offering dual-mode (WiFi/TDM) handsets can integrate their WLAN based E9-1-1 call flows from a standard MSC platform to a VoIP E9-1-1 VoIP positioning center (VPC) 104. This enables a wireless carrier to support civic/metro street address guide (MSAG)-quality address data with respect to the PSAP 118.
- MSAG civic/metro street address guide
- the wireless carrier may also implement mobility/nomadic support for their WiFi based call flows by implementing delivery of an access point MAC address across ISUP loop trunks, and by implementing software in the relevant wireless handsets to collect WiFi access points for an out-of-band location calculation.
- the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 2 the user location and phone identity data are transmitted to a database via an intern etworked connection, and stored there.
- the connection between the user provisioning system 128 and the location information server (LIS)/subscriber line database (SLDB) is referred to herein as a business-to-business (B2B) interface (generally XML).
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network, the call progresses from their dual-mode UMA phone 110 to the UMA network controller 114 over VPN on the Internet.
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN).
- step 5 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- the interface between the VoIP positioning center 104 and the ALI 120 may be, e.g., E2+, NENA or PAM compliant.
- E2+ is an ALI mobile positioning center (MPC) interface defined in the 3GPP2 J-STD-036 standard.
- NENA and PAM are two other existing industry standard ALI-MPC interfaces.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g.
- the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- step 9 the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- VDB validation database
- Fig. 2 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from an ISUP/SIP gateway using inband or out of band access point MAC address to address lookup, in accordance with the principles of the present invention.
- the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 1a the user location and phone identity are transmitted to a database via an internetworked connection, and stored there.
- step 2 the user provisions their current location address connected with their access point MAC address.
- step 2a if not already transmitted in step 1 a, the user location and phone identity data are again transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 2, inband delivery of the access point MAC address in decimal is added to inband delivery using the generic digits parameter (GDP).
- GDP generic digits parameter
- step 5 the access point MAC address is converted from hexadecimal to decimal. This is passed as a 15-digit emergency services routing digit (ESRD) in the ISUP IAM Leg1 parameter.
- ESRD emergency services routing digit
- step 6 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- a routing key e.g., ESQK
- ESRN trunk select code
- LRO last routing option
- step 9 the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- the PSAP customer premises equipment CPE
- CPE customer premises equipment
- the ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- the validation database VDB validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
- Fig. 3 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an E5+ position determination entity (PDE) lookup, in accordance with the principles of the present invention.
- the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 2 the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 3, inband delivery of the CGI (or equivalent) is added to inband delivery using the generic digits parameter (GDP).
- CgPN calling party number
- CPN called party number
- step 5 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- step 6 the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- step 6a the LIS/SLDB 126 sends a GPOSREQ over an E5+ interface to the position determination entity (PDE) 302.
- PDE position determination entity
- SCP switching control point assigns an E.164 by lookup on SS7 point code.
- CGI will also be passed. This assumes that the GSM radio is on near call initiation.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
- Fig. 4 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an Lg PSL for location lookup, in accordance with the principles of the present invention.
- step 1 of Fig. 4 the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 2 the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- UDC UMA network controller
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1.
- CGI calling party number
- CPN called party number
- GDP generic digits parameter
- IMSI international mobile subscriber identity
- step 5 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- step 6 the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- the LIS/SLDB 126 sends a location request to the MSC 102 over Lg.
- the communication (Lg provide subscriber location (PSL) (3GPP)) needs international mobile subscriber identity (IMSI) & mobile station international ISDN number (MSISDN).
- PSL subscriber location
- IMSI international mobile subscriber identity
- MSISDN mobile station international ISDN number
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- a routing key e.g., ESQK
- a trunk select code e.g. ESRN
- LRO last routing option
- step 8 the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- step 9 the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- the validation database validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
- Fig. 5 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or a WiFi location query, in accordance with the principles of the present invention.
- the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 2 the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- UDC UMA network controller
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1.
- the embodiment of Fig. 5 includes inband delivery of the mobile indicator, and optionally the AP MAC address.
- the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- step 6 the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- step 6a the LIS/SLDB 126 sends a location request to the WiFi positioning system server 502.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- a routing key e.g., ESQK
- ESRN trunk select code
- LRO last routing option
- step 9 the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- VDB validation database
- Fig. 6 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA ⁇ 2 call flow from ISUP/SIP gateway access point MAC address and/or MPC Lg interface to the MSC lookup, in accordance with the principles of the present invention.
- the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 2 the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- UDC UMA network controller
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1.
- CGI calling party number
- CPN called party number
- GDP generic digits parameter
- IMSI international mobile subscriber identity
- step 5 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- step 6 the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- step 6a the VPC 104 sends a location request via E2+ to the GMLC/MSC 102.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
- Fig. 7 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or E5+, or Lg interface to the MSC lookup, in accordance with the principles of the present invention.
- step 1 of Fig. 7 the user provisions their current location address connected to their phone number or identity via a networked connection.
- step 1a the user location and phone identity are transmitted to a database via an internetworked connection, and stored there.
- step 2 the user provisions their current location address connected with their access point MAC address.
- step 2a if not already transmitted in step 1a, the user location and phone identity data are again transmitted to a database via an internetworked connection, and stored there.
- step 3 when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
- UDC UMA network controller
- step 4 calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk.
- the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 7, the required delivery technique is dependent upon the location technique used.
- the access point MAC address is converted from hexadecimal to decimal. This is passed as a 15-digit emergency services routing digit (ESRD) in the ISUP IAM Leg1 parameter.
- ESRD emergency services routing digit
- step 6 the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
- step 6a the LIS/SLDB 126 sends a location request to the MSC
- the switching control point assigns an E.164 by lookup on SS7 point code.
- a BSIC or CGI will also be passed. This assumes that the GSM radio is on near call initiation.
- step 6b alternatively, the VPC 104 sends an E2+ request to the GMLC .
- the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
- the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
- a routing key e.g., ESQK
- ESRN trunk select code
- LRO last routing option
- step 9 the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
- step 10 the PSAP customer premises equipment (CPE) then forms a query to the ALI 120.
- the ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables.
- the VoIP positioning center (VPC) 104 responds with location (address) information.
- Fig. 8 shows exemplary call flow between a wireless mobile station
- a call invoke message is passed from the MS 110 to the UNC 114/MSC 102.
- an initial address message IAM
- CgPN calling party number
- step 3 an invite message including the calling party number (CgPN) is passed from the ISUP/SIP gateway 100 to the VoIP positioning center (VPC) 104.
- CgPN calling party number
- step 4 an invite message is passed with the ESRN(TS) and ESQK from the VPC 104 to the ISUP/SIP gateway 100.
- an initial address message (IAM) is sent with GDP(ESQK or last routing option (LRO)), calling party number (CgPN)(callback number) from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
- IAM initial address message
- CgPN calling party number
- step 6 a call setup message IAM [GDP(ESRK), CgPN(Callback#)] is sent from the UNC 114/MSC 102 to the PSAP 118.
- step 7 an ACM message is sent from the PSAP 118 to the UNC 114/MSC 102.
- step 8 an ACM message is sent from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
- step 9 a 180 ringing message is sent from the ISUP/SIP gateway 100 to the VoIP positioning center 104.
- a 180 ringing message is sent from the VPC 104 to the
- step 11 an ACM message is sent from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
- step 12 an ANM message is sent from the PSAP 118 to the UNC 114/MSC 102.
- step 13 an ANM message is sent from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
- steps 14 and 15 a 200 Ok message is exchanged between the ISUP/SIP gateway 100 and the VPC 104.
- step 16 an ANM message is sent from the ISUP/SIP gateway
- step 17 the call is established between the mobile device 110 and the PSAP 118.
- step 18 an ESPOSREQ[ESRK, POSREQTYPE] message is passed from the PSAP 118 to the VPC 104.
- step 19 an esposreq[POSINFO, POSRESULT] message is passed back from the VPC 104 to the requesting PSAP 118.
- step 20 the call is released.
- step 21 to effect the release of the call, an ISUP REL message is passed from the mobile device 110 to the PSAP 118.
- step 22 an ISUP REL[...] message is passed from the UNC
- steps 23 and 24 a Bye message is exchanged between the ISUP/SIP gateway 100 and the VPC 104.
- step 25 an ISUP REL[...] message is passed from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
- step 26 call releasing is performed.
- step 27 an ISUP RLC 9 message is passed from the UNC 114/MSC 102 to the PSAP 118.
- step 28 an ISUP RLC[...] message is passed from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
- steps 29 and 30 a 200 Ok message is exchanged between the ISUP/SIP gateway 100 and the VPC 104.
- step 31 an ISUP RLC[...] message is sent from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
- step 32 release of the call between the mobile device 110 and the PSAP 118 is complete.
- Benefits of the invention include lower cost of integration of VoIP E9-1-1 into a carriers existing wireless infrastructure.
- the invention has particular application with consumers using UMA enabled dual-mode (e.g., WiFi/GSM/CDMA) handsets. It also has applicability in the development of ISUP/SIP Gateways, and is non-application specific. 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.
- UMA enabled dual-mode e.g., WiFi/GSM/CDMA
Abstract
An ISUP/SIP gateway is implemented to encapsulate SS7 location requests from a switched telephone network into an Internet protocol SIP message including one or more location objects. The ISUP/SIP gateway is implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC) to provide support of unlicensed mobile access (UMA) voice over Internet Protocol (VoIP) call routing, e.g., for E9-1-1 , 4-1-1 , 2-1-1 , etc. The disclosed location objects that are encapsulated into a SIP message includes calling party number, called party number, CGI, International Mobile Subscriber Identity (IMSI), mobility indicator, and/or access point MAC address. At the SIP/ISUP gateway, SS7 integrated services user part (ISUP) location request messages are encapsulated within SIP. The SIP encapsulated location request message is then routed over the Internet to a destination VoIP positioning center (VPC).
Description
INTEGRATED SERVICES USER PART (ISUP)/SESSION
INITIATION PROTOCOL (SIP) GATEWAY FOR UNLICENSED
MOBILE ACCESS (UMA) EMERGENCY SERVICES CALL FLOW
The present application claims priority from U.S. Provisional Patent
Application No. 60/699,862, filed July 18, 2005, entitled "Integrated Services User Part (ISUP)/Session Initiation Protocol (SIP) Gateway For Unlicensed Mobile Access (UMA) Emergency Services Call Flow", to Don Mitchell, the entirety of which is explicitly incorporated herein by reference.
BACKGROUND OF THE INVENTION
1. Field of the Invention
This invention relates generally to wireless telecommunication. More particularly, it relates to Voice Over Internet Protocol (VoIP) E9-1-1 call flows supporting unlicensed mobile access (UMA).
2. Background of the Related Art
Unlicensed Mobile Access (UMA) is the Third Generation Partnership (3GPP) standard for cellular and wireless fidelity (WiFi) convergence. The UMA specifications are publicly available, e.g., from the UMA Technology web site (www.umatechnology.org) as well as from the 3GPP web site (www.3gpp.org).
The UMA effort was initiated by leading operators and vendors in the wireless industry, with a goal of developing a set of technical specifications for extending mobile voice, data and IP Multimedia Subsystem (IMS) services over broadband IP and Wi-Fi access networks. On April 8th 2005, the specifications were officially incorporated into 3GPP Release 6, making UMA the true global standard for cellular/Wi-Fi convergence. The UMA effort has been a tremendous success, having developed a new global communications standard in a period of less than 15 months.
For mobile operators, Wi-Fi had been viewed as somewhat of a threat. Now, UMA provides a secure, managed IP connection established
between a mobile handset and the operator's core network. Thus all of an operator's mobile services (voice, data, and IMS) are available to the subscriber when connected via Wi-Fi. In addition, with UMA, active voice calls and data sessions are automatically handed over between networks as subscribers come in and out of range of WLANs. Thus, with the use of UMA, Wi-Fi no longer poses a threat to mobile operators because they maintain control of their subscribers and services even when connected via Wi-Fi.
The current UMA E9-1-1 standard calls for E9-1-1 calls NOT to be processed over the IP network but instead to be transitioned to a GSM TDM call flow. However, the present inventors have realized that this is a problem because of the high potential for such a transitioned E9-1-1 call to be dropped. Needless to say, a significant number of dropped emergency calls are problematic and the source of potential liabilities to an operator.
Some GSM carriers have followed different implementations of the UMA E9-1-1 call flow. For instance, at least one carrier (e.g., T-Mobile™) has implemented an approach utilizing a serving mobile location center (SMLC). Unfortunately, disadvantages with such conventional solutions include the fact that switching E9-1-1 calls back to a time division multiplexed (TDM) system may cause those calls to drop in houses having poor cellular coverage. There is a need for a more reliable handling of emergency calls that use UMA.
SUMMARY OF THE INVENTION
In accordance with the principles of the present invention, a method and apparatus for providing location based support to a call made via a UMA network comprises encapsulating a location request with respect to a call from a UMA phone. The location request is received by an ISUP/SIP gateway and encapsulated in a SIP message. The SIP encapsulated location request is passed to a VoIP positioning center. In accordance with another aspect of the present invention, an architecture link between a mobile switching center (MSC) and a VoIP
positioning center (VPC) to support location based services comprises an SS7 based ISUP/SIP gateway. The ISUP/SIP gateway is operable to encapsulate a received location request into an Internet Protocol message.
BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow through an ISUP/SIP gateway implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC), in accordance with the principles of the present invention.
Fig. 2 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from an ISUP/SIP gateway using inband or out of band access point MAC address to address lookup, in accordance with the principles of the present invention.
Fig. 3 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an E5+ position determination entity (PDE) lookup, in accordance with the principles of the present invention.
Fig. 4 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an Lg PSL for location lookup, in accordance with the principles of the present invention.
Fig. 5 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or a WiFi location query, in accordance with the principles of the present invention. Fig. 6 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or MPC Lg interface to the MSC lookup, in accordance with the principles of the present invention.
Fig. 7 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access
point MAC address and/or E5+, or Lg interface to the MSC lookup, in accordance with the principles of the present invention.
Fig. 8 shows exemplary call flow between a wireless mobile station, a UMA network controller (UNC)/mobile switching center (MSC), an ISUP/SIP gateway in accordance with the present invention, a VoIP positioning center
(VPC), and a public safety answering point (PSAP)/emergency services network equipment (ESNE).
DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS An ISUP/SIP gateway is implemented to encapsulate SS7 location requests from a switched telephone network into an Internet protocol SIP message including one or more location objects. The ISUP/SIP gateway is implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC) to provide support of unlicensed mobile access (UMA) voice over Internet Protocol (VoIP) call routing, e.g., for E9-1-1 , 4-1-1 , 2-1-1 , etc. The disclosed location objects that are encapsulated into a SIP message includes calling party number, called party number, CGI, International Mobile Subscriber Identity (IMSI), mobility indicator, and/or access point MAC address. At the SIP/ISUP gateway, SS7 integrated services user part (ISUP) location request messages are encapsulated within SIP. The SIP encapsulated location request message is then routed over the Internet to a destination VoIP positioning center (VPC).
Session Initiation Protocol (SIP) is an application-layer control protocol that is conventionally used to establish, modify and terminate multimedia sessions or calls over the Internet. These multimedia sessions include multimedia conferences, Internet telephony and similar applications. SIP is one of the key protocols used to implement Voice over IP (VoIP).
The popularity of SIP-ISUP gateways that interwork between the public switched telephone network (PSTN) and SIP networks has motivated the publication of a set of common practices that can assure consistent behavior across implementations. An important basic requirement of these common
practices is that the SIP telephone network be feature transparent with respect to the PSTN.
At a SIP-ISUP gateway, signaling system number 7 (SS7) integrated services user part (ISUP) messages consistent with the PSTN are encapsulated within SIP in such a way as to not discard in the SIP request information necessary for services. The encapsulated message is then routed over the Internet to a destination VoIP device.
However, after the service information is encapsulated within the
SIP request, intermediaries like proxy servers that make routing decisions for SIP requests cannot be expected to understand ISUP. So simultaneously, some critical information is translated from an ISUP message into the corresponding
SIP headers to indicate how the SIP request is to be routed.
The present invention implements an ISUP/SIP gateway, but not in a conventional manner to pass SS7 signaling from a switched telephone network over the Internet. Rather, the present invention implements an ISUP/SIP gateway between a mobile switching center (MSC) and a VoIP positioning center (VPC) to provide support of unlicensed mobile access (UMA) voice over Internet Protocol (VoIP) call routing, e.g., for E9-1-1 , 4-1-1 , 2-1-1 , etc.
While disclosed with respect to embodiments providing an E9-1-1 solution, the principles of the present invention are equally applicable to applications outside of emergency services, e.g., 4-1-1 , 2-1-1 , etc.
Fig. 1 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow through an ISUP/SIP gateway implemented between a mobile switching center (MSC) and a VoIP positioning center (VPC), in accordance with the principles of the present invention.
In particular, as shown in Fig. 1 , a dual-mode phone user makes use of a wireless device including a dual-mode phone user agent 110. Wireless communication is established with a UMA network controller (UNC) 114 via a WiFi access point 112. An emergency call is routed to a mobile switching center (MSC) 102, which in turn routes the emergency call to a public safety answering point (PSAP) 118 via a selective router 116.
The dual-mode phone user provisions the dual-mode phone via a suitable user provisioning system 128. Location based services are provided by a VoIP positioning center (VPC) 104, an automated location identification (ALI)
120, a validation database (VDB) 122, master street address guide (MSAG) 124, and location information server/subscriber line database (LIS/SLDB) 126.
Importantly, an SS7 based ISUP/SIP gateway 100 is implemented between the MSC 102 and the VoIP positioning center 104. The ISUP/SIP gateway 100 in accordance with the present invention converts ISUP IAM parameters to SIP V6 parameters, the V6 interface being per NENA i2 definitions. In the opposite communication direction the ISUP/SIP gateway 100 converts from V4 parameters to ISUP signaling, the V4 interface being per NENA \2 definitions.
In the ISUP/SIP gateway 100, a WiFi access point hexadecimal MAC address is converted into decimal format and transmitted in an ISUP initial address message (IAM) parameter. In a preferred embodiment, a flag is included to indicate locateability of the handset or softphone.
Using the ISUP/Session Initiation Protocol (SIP) gateway 100, a wireless carrier is able to integrate their message servicing center (MSC) 102 across an SS7 network using standardized V6/V4 i2 call flows via ISUP signaling from ISUP loop-back trunks to a switching control point (SCP).
The MSC 102 implements translations that support i2 emergency services query key (ESQK)/emergency services routing number (ESRN) based call flows to an emergency services routing key (ESRK)/Trunk Select type call flow. The MSC 102 also preferably supports last routing option (LRO) i1 based call flows. The MSC 102 also preferably supports modified LRO to an operator routing support service (ORSS) (i.e., a private call center) i1 call flow.
This combination of ISUP (per ANSI) loop-trunks with V6/V4 standardized call flows provides a reliable solution to the UMA E9-1-1 problem otherwise incurred with conventional systems. A wireless carrier offering dual-mode (WiFi/TDM) handsets can integrate their WLAN based E9-1-1 call flows from a standard MSC platform to a
VoIP E9-1-1 VoIP positioning center (VPC) 104. This enables a wireless carrier to support civic/metro street address guide (MSAG)-quality address data with respect to the PSAP 118.
The wireless carrier may also implement mobility/nomadic support for their WiFi based call flows by implementing delivery of an access point MAC address across ISUP loop trunks, and by implementing software in the relevant wireless handsets to collect WiFi access points for an out-of-band location calculation.
As shown in step 1 of Fig. 1 , the user provisions their current location address connected to their phone number or identity via a networked connection.
In step 2, the user location and phone identity data are transmitted to a database via an intern etworked connection, and stored there. The connection between the user provisioning system 128 and the location information server (LIS)/subscriber line database (SLDB) is referred to herein as a business-to-business (B2B) interface (generally XML).
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network, the call progresses from their dual-mode UMA phone 110 to the UMA network controller 114 over VPN on the Internet. In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 1 , the IAM outbound message contains the calling party number (CgPN) and called party number (CPN).
In step 5, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126. The interface between the VoIP positioning center 104 and the ALI 120 may be, e.g., E2+, NENA or PAM compliant. E2+ is an ALI mobile positioning center (MPC) interface defined in the 3GPP2 J-STD-036 standard. NENA and PAM are two other existing industry standard ALI-MPC interfaces.
In step 7, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback. In step 8, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 9, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information.
In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
Fig. 2 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from an ISUP/SIP gateway using inband or out of band access point MAC address to address lookup, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 2, the user provisions their current location address connected to their phone number or identity via a networked connection.
In step 1a, the user location and phone identity are transmitted to a database via an internetworked connection, and stored there.
In step 2, the user provisions their current location address connected with their access point MAC address. In step 2a, if not already transmitted in step 1 a, the user location and phone identity data are again transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 2, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 2, inband delivery of the access point MAC address in decimal is added to inband delivery using the generic digits parameter (GDP).
In step 5, the access point MAC address is converted from hexadecimal to decimal. This is passed as a 15-digit emergency services routing digit (ESRD) in the ISUP IAM Leg1 parameter.
In step 6, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 7, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126. In step 8, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
In step 9, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 10, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information. In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
Fig. 3 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an E5+ position determination entity (PDE) lookup, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 3, the user provisions their current location address connected to their phone number or identity via a networked connection.
In step 2, the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet. In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 3, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 3, inband delivery of the CGI (or equivalent) is added to inband delivery using the generic digits parameter (GDP).
In step 5, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
In step 6a, the LIS/SLDB 126 sends a GPOSREQ over an E5+ interface to the position determination entity (PDE) 302. With E5+, the switching control point (SCP) assigns an E.164 by lookup on SS7 point code. A BSIC or
CGI will also be passed. This assumes that the GSM radio is on near call initiation.
In step 7, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback. In step 8, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 9, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information. In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
Fig. 4 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or an Lg PSL for location lookup, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 4, the user provisions their current location address connected to their phone number or identity via a networked connection. In step 2, the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 4, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 4, inband delivery of the CGI (or equivalent) is added to inband delivery using the generic digits parameter (GDP) and international mobile subscriber identity (IMSI).
In step 5, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
In step 6a, the LIS/SLDB 126 sends a location request to the MSC 102 over Lg. The communication (Lg provide subscriber location (PSL) (3GPP)) needs international mobile subscriber identity (IMSI) & mobile station international ISDN number (MSISDN).
In step 7, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
In step 8, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 9, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information.
In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query. Fig. 5 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or a WiFi location query, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 5, the user provisions their current location address connected to their phone number or identity via a networked connection.
In step 2, the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual-
mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 5, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, the embodiment of Fig. 5 includes inband delivery of the mobile indicator, and optionally the AP MAC address. In step 5, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
In step 6a, the LIS/SLDB 126 sends a location request to the WiFi positioning system server 502.
In step 7, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback. In step 8, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 9, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information.
In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
Fig. 6 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA \2 call flow from ISUP/SIP gateway access
point MAC address and/or MPC Lg interface to the MSC lookup, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 6, the user provisions their current location address connected to their phone number or identity via a networked connection.
In step 2, the user location and phone identity data are transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 6, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 6, inband delivery of the CGI (or equivalent) is added to inband delivery using the generic digits parameter (GDP) and international mobile subscriber identity (IMSI). In step 5, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126.
In step 6a, the VPC 104 sends a location request via E2+ to the GMLC/MSC 102.
In step 7, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback. In step 8, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 9, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information. In another embodiment, the validation database (VDB) validates the subscriber location address and assigns an MSAG address for delivery to the PSAP 118 to support the ALI query.
Fig. 7 shows an example location based UMA VoIP E9-1-1 basic call flow architecture using NENA i2 call flow from ISUP/SIP gateway access point MAC address and/or E5+, or Lg interface to the MSC lookup, in accordance with the principles of the present invention.
In particular, as shown in step 1 of Fig. 7, the user provisions their current location address connected to their phone number or identity via a networked connection. In step 1a, the user location and phone identity are transmitted to a database via an internetworked connection, and stored there.
In step 2, the user provisions their current location address connected with their access point MAC address.
In step 2a, if not already transmitted in step 1a, the user location and phone identity data are again transmitted to a database via an internetworked connection, and stored there.
In step 3, when the user makes a call that needs location based routing (like 9-1-1 ) from a WiFi network 112, the call progresses from their dual- mode UMA phone 110 to the UMA network controller (UNC) 114 over VPN on the Internet.
In step 4, calls from UMA subscribers on a WiFi network that require location based routing are translated to an assigned ISUP loop-trunk. In the embodiment of Fig. 7, the IAM outbound message contains the calling party number (CgPN) and called party number (CPN). This is the same as with respect to the embodiment of Fig. 1. However, in the embodiment of Fig. 7, the required delivery technique is dependent upon the location technique used.
In step 5, the access point MAC address is converted from hexadecimal to decimal. This is passed as a 15-digit emergency services routing digit (ESRD) in the ISUP IAM Leg1 parameter.
In step 6, the ISUP/SIP gateway 100 translates the ISUP IAM parameters into SIP Invite parameters.
In step 6a, the LIS/SLDB 126 sends a location request to the MSC
102 over Lg or over an E5+ interface to the position determination entity (PDE)
302 (PDE). With E5+, the switching control point (SCP) assigns an E.164 by lookup on SS7 point code. A BSIC or CGI will also be passed. This assumes that the GSM radio is on near call initiation.
In step 6b, alternatively, the VPC 104 sends an E2+ request to the GMLC .
In step 7, the VoIP positioning center (VPC) 104 assigns routing based upon the location retrieved from the LIS/SLDB 126. In step 8, the ISUP/SIP gateway 100 receives routing instruction from the VoIP positioning center (VPC) 104 and sends a routing key (e.g., ESQK) and a trunk select code (e.g. ESRN); or sends last routing option (LRO) as a fallback.
In step 9, the MSC 102 egresses the call based upon ESRN and sends ESQK to the selective router 116, which then routes to the PSAP 118.
In step 10, the PSAP customer premises equipment (CPE) then forms a query to the ALI 120. The ALI 120 then steers that query to the VoIP positioning center 104 based upon the ESQK and its steering tables. The VoIP positioning center (VPC) 104 responds with location (address) information. Fig. 8 shows exemplary call flow between a wireless mobile station
110, a UMA network controller (UNC) 114/mobile switching center (MSC) 102, an ISUP/SIP gateway 100 in accordance with the present invention, a VoIP positioning center (VPC) 104, and a public safety answering point (PSAP) 118/emergency services network equipment (ESNE). In particular, as shown in step 1 of Fig. 8, a call invoke message is passed from the MS 110 to the UNC 114/MSC 102.
In step 2, an initial address message (IAM) with the calling party number (CgPN) is transmitted from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
In step 3, an invite message including the calling party number (CgPN) is passed from the ISUP/SIP gateway 100 to the VoIP positioning center (VPC) 104.
In step 4, an invite message is passed with the ESRN(TS) and ESQK from the VPC 104 to the ISUP/SIP gateway 100.
In step 5, an initial address message (IAM) is sent with GDP(ESQK or last routing option (LRO)), calling party number (CgPN)(callback number) from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
In step 6, a call setup message IAM [GDP(ESRK), CgPN(Callback#)] is sent from the UNC 114/MSC 102 to the PSAP 118.
In step 7, an ACM message is sent from the PSAP 118 to the UNC 114/MSC 102.
In step 8, an ACM message is sent from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
In step 9, a 180 ringing message is sent from the ISUP/SIP gateway 100 to the VoIP positioning center 104. In step 10, a 180 ringing message is sent from the VPC 104 to the
ISUP/SIP gateway 100.
In step 11 , an ACM message is sent from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
In step 12, an ANM message is sent from the PSAP 118 to the UNC 114/MSC 102.
In step 13, an ANM message is sent from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
In steps 14 and 15, a 200 Ok message is exchanged between the ISUP/SIP gateway 100 and the VPC 104. In step 16, an ANM message is sent from the ISUP/SIP gateway
100 to the UNC 114/MSC 102.
In step 17, the call is established between the mobile device 110 and the PSAP 118.
In step 18, an ESPOSREQ[ESRK, POSREQTYPE] message is passed from the PSAP 118 to the VPC 104. In step 19, an esposreq[POSINFO, POSRESULT] message is passed back from the VPC 104 to the requesting PSAP 118.
In step 20, the call is released.
In step 21, to effect the release of the call, an ISUP REL message is passed from the mobile device 110 to the PSAP 118. In step 22, an ISUP REL[...] message is passed from the UNC
114/MSC 102 to the ISUP/SIP gateway 100.
In steps 23 and 24, a Bye message is exchanged between the ISUP/SIP gateway 100 and the VPC 104.
In step 25, an ISUP REL[...] message is passed from the ISUP/SIP gateway 100 to the UNC 114/MSC 102.
In step 26, call releasing is performed.
In step 27, an ISUP RLC [...] message is passed from the UNC 114/MSC 102 to the PSAP 118.
In step 28, an ISUP RLC[...] message is passed from the UNC 114/MSC 102 to the ISUP/SIP gateway 100.
In steps 29 and 30, a 200 Ok message is exchanged between the ISUP/SIP gateway 100 and the VPC 104.
In step 31, an ISUP RLC[...] message is sent from the ISUP/SIP gateway 100 to the UNC 114/MSC 102. In step 32, release of the call between the mobile device 110 and the PSAP 118 is complete.
Benefits of the invention include lower cost of integration of VoIP E9-1-1 into a carriers existing wireless infrastructure.
The invention has particular application with consumers using UMA enabled dual-mode (e.g., WiFi/GSM/CDMA) handsets. It also has applicability in the development of ISUP/SIP Gateways, and is non-application specific.
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
1. A method of providing location based support to a call made via a UMA network, comprising: encapsulating a location request with respect to a call from an unlicensed mobile access (UMA) phone, said location request being received by an ISUP/SIP gateway and encapsulated in a SIP message; and passing said SIP encapsulated location request to a voice over Internet protocol (VoIP) positioning center.
2. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein: said UMA phone is a dual-mode phone.
3. The method of providing location based support to a call made via a UMA network according to claim 2, wherein: said dual-mode phone is capable of initiating said call via a WiFi network.
4. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: a calling party number.
5. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: a calling party number; and a called party number.
6. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: an access point MAC address.
7. The method of providing location based support to a call made via a UMA network according to claim 1, wherein said encapsulated location request comprises: calling party number; called party number; and access point MAC address.
8. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: calling party number; called party number; and CGI.
t 9. The method of providing location based support to a call made via a UMA network according to claim 8, wherein said encapsulated location request further comprises: access point MAC address.
10. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: calling party number; called party number; CGI; and
International Mobile Subscriber Identity (IMSI).
11. The method of providing location based support to a call made via a UMA network according to claim 1 , wherein said encapsulated location request comprises: calling party number; and mobility indicator.
12. The method of providing location based support to a call made via a UMA network according to claim 11 , wherein said encapsulated location request further comprises: access point MAC address.
13. The method of providing location based support to a call made via a UMA network according to claim 1, wherein said encapsulated location request comprises: calling party number;
CGI; and International Mobile Subscriber Identity (IMSI).
14. An architecture link between a mobile switching center (MSC) and a VoIP positioning center (VPC) to support location based services, comprising: an SS7 based ISUP/SIP gateway, said ISUP/SIP gateway operable to encapsulate a received location request into an Internet Protocol message.
15. Apparatus for providing location based support to a call made via a UMA network, comprising: means for encapsulating a location request with respect to a call from an unlicensed mobile access (UMA) phone, said location request being received by an ISUP/SIP gateway and encapsulated in a SIP message; and means for passing said SIP encapsulated location request to a voice over Internet protocol (VoIP) positioning center.
16. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein: said UMA phone is a dual-mode phone.
17. The apparatus for providing location based support to a call made via a UMA network according to claim 16, wherein: said dual-mode phone is capable of initiating said call via a WiFi network.
18. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: a calling party number.
19. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: a calling party number; and a called party number.
20. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: an access point MAC address.
21. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: calling party number; called party number; and access point MAC address.
22. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: calling party number; called party number; and CGI.
23. The apparatus for providing location based support to a call made via a UMA network according to claim 22, wherein said encapsulated location request further comprises: access point MAC address.
24. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: calling party number; called party number; CGI; and International Mobile Subscriber Identity (IMSI).
25. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: calling party number; and mobility indicator.
26. The apparatus for providing location based support to a call made via a UMA network according to claim 25, wherein said encapsulated location request further comprises: access point MAC address.
27. The apparatus for providing location based support to a call made via a UMA network according to claim 15, wherein said encapsulated location request comprises: calling party number;
CGI; and International Mobile Subscriber Identity (IMSI).
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US69986205P | 2005-07-18 | 2005-07-18 | |
US60/699,862 | 2005-07-18 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007011861A2 true WO2007011861A2 (en) | 2007-01-25 |
WO2007011861A3 WO2007011861A3 (en) | 2007-06-07 |
Family
ID=37669464
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2006/027658 WO2007011861A2 (en) | 2005-07-18 | 2006-07-17 | Integrated services user part (isup)/session initiation protocol (sip) gateway for unlicensed mobile access (uma) emergency services call flow |
Country Status (2)
Country | Link |
---|---|
US (4) | US8090341B2 (en) |
WO (1) | WO2007011861A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2116029A1 (en) * | 2007-02-06 | 2009-11-11 | Telecommunication Systems, Inc. | Voice over internet protocol (voip) location based commercial prospect conferencing |
CN109150799A (en) * | 2017-06-16 | 2019-01-04 | 中国移动通信集团公司 | A kind of method and device obtaining called location information |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8918073B2 (en) | 2002-03-28 | 2014-12-23 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US8290505B2 (en) | 2006-08-29 | 2012-10-16 | Telecommunications Systems, Inc. | Consequential location derived information |
US8666397B2 (en) | 2002-12-13 | 2014-03-04 | Telecommunication Systems, Inc. | Area event handling when current network does not cover target area |
US20070298765A1 (en) * | 2006-06-27 | 2007-12-27 | Richard Dickinson | Public services access point (PSAP) designation of preferred emergency call routing method via internet or public switched telephone network (PSTN) |
US20080090546A1 (en) | 2006-10-17 | 2008-04-17 | Richard Dickinson | Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging |
US20080126535A1 (en) | 2006-11-28 | 2008-05-29 | Yinjun Zhu | User plane location services over session initiation protocol (SIP) |
US7933385B2 (en) * | 2005-08-26 | 2011-04-26 | Telecommunication Systems, Inc. | Emergency alert for voice over internet protocol (VoIP) |
US9282451B2 (en) * | 2005-09-26 | 2016-03-08 | Telecommunication Systems, Inc. | Automatic location identification (ALI) service requests steering, connection sharing and protocol translation |
US7907551B2 (en) * | 2005-10-06 | 2011-03-15 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) location based 911 conferencing |
US8467320B2 (en) * | 2005-10-06 | 2013-06-18 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) multi-user conferencing |
US7626951B2 (en) * | 2005-10-06 | 2009-12-01 | Telecommunication Systems, Inc. | Voice Over Internet Protocol (VoIP) location based conferencing |
US20070081452A1 (en) * | 2005-10-06 | 2007-04-12 | Edward Walter | Access port centralized management |
US20070121798A1 (en) * | 2005-10-20 | 2007-05-31 | Jon Croy | Public service answering point (PSAP) proxy |
WO2007061790A2 (en) * | 2005-11-18 | 2007-05-31 | Telecommunication Systems, Inc. | Voice over internet protocol (voip) mobility detection |
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) |
US8208605B2 (en) | 2006-05-04 | 2012-06-26 | Telecommunication Systems, Inc. | Extended efficient usage of emergency services keys |
US9252981B2 (en) * | 2006-06-13 | 2016-02-02 | At&T Intellectual Property I, L.P. | Method and apparatus for processing a communication request from a roaming voice over IP terminal |
JP2008092230A (en) * | 2006-09-29 | 2008-04-17 | Toshiba Corp | Broadcast receiver and decoding method of broadcast receiver |
WO2008039469A2 (en) * | 2006-09-26 | 2008-04-03 | Telecommunication Systems, Inc. | Location object proxy |
US20090109979A1 (en) * | 2006-09-27 | 2009-04-30 | Leon Tong | System and method for a mobile access femtocell |
US8045532B2 (en) * | 2006-11-09 | 2011-10-25 | Cisco Technology, Inc. | Location architecture for large scale networks |
US7869827B2 (en) * | 2006-11-28 | 2011-01-11 | Sprint Spectrum L.P. | Encapsulating upper layers of CDMA signaling between a multi-mode device and a signaling gateway |
US8165561B2 (en) * | 2007-03-27 | 2012-04-24 | Alcatel Lucent | IMS networks providing business-related content to wireless devices |
EP2186276B1 (en) * | 2007-08-21 | 2013-10-02 | Redknee Inc. | Method and system for call routing |
US8660574B2 (en) | 2008-04-02 | 2014-02-25 | Qualcomm Incorporated | Generic positioning protocol |
US8462768B2 (en) * | 2008-06-11 | 2013-06-11 | Verizon Patent And Licensing Inc. | Providing session initiation protocol (SIP) call control functions to public switched telephone network (PSTN)-based call controller |
US20100080216A1 (en) * | 2008-09-29 | 2010-04-01 | Jonathan Alan Croy | Real-time communication blocking for Dot Not Call" registered information |
US9435874B2 (en) | 2009-04-21 | 2016-09-06 | Qualcomm Incorporated | Method and apparatus for supporting positioning for terminals in a wireless network |
US8660540B2 (en) * | 2009-04-21 | 2014-02-25 | Qualcomm Incorporated | Supporting version negotiation for positioning for terminals in a wireless network |
US8682321B2 (en) | 2011-02-25 | 2014-03-25 | Telecommunication Systems, Inc. | Mobile internet protocol (IP) location |
US9363782B2 (en) | 2011-06-22 | 2016-06-07 | Qualcomm Incorporated | Methods and apparatus for wireless device positioning in multicarrier configurations |
WO2013048551A1 (en) | 2011-09-30 | 2013-04-04 | Telecommunication Systems, Inc. | Unique global identifier for minimizing prank 911 calls |
US9313637B2 (en) | 2011-12-05 | 2016-04-12 | Telecommunication Systems, Inc. | Wireless emergency caller profile data delivery over a legacy interface |
US9544260B2 (en) | 2012-03-26 | 2017-01-10 | Telecommunication Systems, Inc. | Rapid assignment dynamic ownership queue |
US9307372B2 (en) | 2012-03-26 | 2016-04-05 | Telecommunication Systems, Inc. | No responders online |
WO2014028712A1 (en) | 2012-08-15 | 2014-02-20 | Telecommunication Systems, Inc. | Device independent caller data access for emergency calls |
US9456301B2 (en) | 2012-12-11 | 2016-09-27 | Telecommunication Systems, Inc. | Efficient prisoner tracking |
US8983047B2 (en) | 2013-03-20 | 2015-03-17 | Telecommunication Systems, Inc. | Index of suspicion determination for communications request |
US9408034B2 (en) | 2013-09-09 | 2016-08-02 | Telecommunication Systems, Inc. | Extended area event for network based proximity discovery |
US9516104B2 (en) | 2013-09-11 | 2016-12-06 | Telecommunication Systems, Inc. | Intelligent load balancer enhanced routing |
CN105981345B (en) * | 2013-09-27 | 2019-06-18 | 瑞典爱立信有限公司 | The Lawful intercept of WI-FI/ packet-based core networks access |
US9479897B2 (en) | 2013-10-03 | 2016-10-25 | Telecommunication Systems, Inc. | SUPL-WiFi access point controller location based services for WiFi enabled mobile devices |
US9549419B2 (en) * | 2015-01-30 | 2017-01-17 | Telecommunication Systems, Inc. | Trigger mechanism |
JP6165794B2 (en) * | 2015-03-05 | 2017-07-19 | 日本精密測器株式会社 | Slave device and connection establishment method |
US9264944B1 (en) | 2015-07-06 | 2016-02-16 | Peerless Network, Inc. | SBC-localized handoff |
US10028121B2 (en) * | 2016-04-07 | 2018-07-17 | T-Mobile Usa, Inc. | Determining device locations for emergency service calls |
CN107517456A (en) * | 2016-06-16 | 2017-12-26 | 中国电信股份有限公司 | Method, user terminal and the system of positioning application are realized based on WiFi |
US10231285B1 (en) * | 2018-03-12 | 2019-03-12 | International Business Machines Corporation | Cognitive massage dynamic response optimization |
CN110971573B (en) * | 2018-09-29 | 2022-05-13 | 中兴通讯股份有限公司 | Method, device, system and storage medium for playing and IP (Internet protocol) of narrow-band service |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003039009A2 (en) * | 2001-11-01 | 2003-05-08 | Nokia Corporation | Local service handover |
US20030115261A1 (en) * | 2001-02-26 | 2003-06-19 | Jahangir Mohammed | Apparatus and method for integrating an unlicensed wireless communications system and a licensed wireless communications system |
US20030125021A1 (en) * | 2001-12-28 | 2003-07-03 | Tell Daniel Francis | Method and apparatus for transmitting wired data voice over IP data and wireless data through a common IP core network |
WO2005060292A1 (en) * | 2003-12-16 | 2005-06-30 | Kineto Wireless, Inc. | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
US20050148353A1 (en) * | 2003-06-06 | 2005-07-07 | Hicks John A.Iii | System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed spectrum and wired access with licensed spectrum |
Family Cites Families (110)
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 |
US6438226B1 (en) * | 1997-10-06 | 2002-08-20 | Ccs Holdings, Inc. | XDSL splitter assembly for main distribution frame |
JPH11199320A (en) * | 1997-11-06 | 1999-07-27 | Ngk Spark Plug Co Ltd | Microwave dielectric porcelain composition |
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 |
US6317722B1 (en) | 1998-09-18 | 2001-11-13 | Amazon.Com, Inc. | Use of electronic shopping carts to generate personal recommendations |
US6438223B1 (en) | 1999-03-03 | 2002-08-20 | Open Telephone Network, Inc. | System and method for local number portability for telecommunication networks |
EP1246494B1 (en) | 1999-08-30 | 2005-02-02 | Swisscom Mobile AG | Emergency call in a telecommunications network |
AU2001230955A1 (en) | 2000-01-18 | 2001-07-31 | 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 |
WO2002004436A1 (en) | 2000-07-12 | 2002-01-17 | Sumitomo Chemical Company, Limited | Processes for the preparation of pyrone compounds |
US8996698B1 (en) * | 2000-11-03 | 2015-03-31 | Truphone Limited | Cooperative network for mobile internet access |
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 |
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 |
US7272575B2 (en) | 2001-07-13 | 2007-09-18 | Lilly Mae Vega | Method and system for facilitating service transactions |
US6678357B2 (en) * | 2001-09-26 | 2004-01-13 | Siemens Information And Communication Networks, Inc. | Internet protocol (IP) emergency connections (ITEC) telephony |
JP4160506B2 (en) | 2001-09-28 | 2008-10-01 | レヴェル 3 シーディーエヌ インターナショナル インコーポレーテッド. | Configurable adaptive wide area traffic control and management |
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 |
US7233781B2 (en) * | 2001-10-10 | 2007-06-19 | Ochoa Optics Llc | System and method for emergency notification content delivery |
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 |
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 |
US20030135493A1 (en) | 2002-01-15 | 2003-07-17 | Jeffrey Phelan | Method and apparatus for consuming information based on a geographic location profile of a user |
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 |
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 |
US20060184617A1 (en) * | 2005-02-11 | 2006-08-17 | Nicholas Frank C | Method and system for the creating, managing, and delivery of feed formatted content |
US20040203568A1 (en) * | 2002-07-20 | 2004-10-14 | Kirtland Kenneth P. | Computerized warning system interface and method |
WO2004021726A1 (en) | 2002-08-14 | 2004-03-11 | Siemens Aktiengesellschaft | 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 |
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 |
WO2004042456A1 (en) | 2002-11-05 | 2004-05-21 | Safilo Societa' Azionaria Fabbrica Italiana Lavorazione Occhiali S.P.A | A device having auxiliary lenses for spectacles, and spectacles including said device |
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 |
WO2004066656A1 (en) * | 2003-01-21 | 2004-08-05 | Research In Motion Limited | Method and apparatus to enhance the probability of successful emergency call completion in a mobile station |
US8050281B2 (en) * | 2003-01-31 | 2011-11-01 | Qwest Communications International Inc. | Alert gateway, systems and methods |
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 |
US7797459B1 (en) * | 2003-02-11 | 2010-09-14 | At&T Intellectual Property Ii, L.P. | Access independent common architecture for real-time communications services for networking environments |
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 |
US7895263B1 (en) * | 2003-06-25 | 2011-02-22 | Everbridge, Inc. | Emergency and non-emergency telecommunications geo-notification system |
WO2005015884A2 (en) * | 2003-08-07 | 2005-02-17 | Telcordia Technologies,Inc. | Dial-out voice notification system |
US20060236258A1 (en) | 2003-08-11 | 2006-10-19 | Core Mobility, Inc. | Scheduling of rendering of 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 |
US7526563B2 (en) * | 2004-02-27 | 2009-04-28 | Nokia Corporation | 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 |
WO2005089286A2 (en) | 2004-03-15 | 2005-09-29 | America Online, Inc. | Sharing social network information |
US7242923B2 (en) | 2004-03-23 | 2007-07-10 | Motorola, Inc. | System and method for authenticating wireless device with fixed station |
US7957348B1 (en) * | 2004-04-21 | 2011-06-07 | Kineto Wireless, Inc. | Method and system for signaling traffic and media types within a communications network switching system |
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 |
EP1794980A1 (en) * | 2004-09-22 | 2007-06-13 | Siemens Communications, Inc. | Pseudo number portability in fixed-mobile convergence with one number |
US7957723B2 (en) | 2004-10-01 | 2011-06-07 | Nokia Corporation | Sharing information feed data |
GB0424052D0 (en) * | 2004-10-29 | 2004-12-01 | Nortel Networks Ltd | Improvements in or relating to internet protocol (IP) location, privacy and presence |
US20060106774A1 (en) | 2004-11-16 | 2006-05-18 | Cohen Peter D | Using qualifications of users to facilitate user performance of tasks |
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 |
WO2006078202A1 (en) * | 2005-01-19 | 2006-07-27 | Telefonktiebolaget Lm Ericsson (Publ) | A method and apparatus for handling emergency calls |
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 |
US7684782B2 (en) * | 2005-04-13 | 2010-03-23 | Wirelesswerx International, Inc. | Method and system for initiating and handling an emergency call utilizing geographical zones |
US7496182B2 (en) * | 2005-04-15 | 2009-02-24 | Verizon Business Global Llc | Handling emergency service calls originating from internet telephony |
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 |
US20060268902A1 (en) * | 2005-05-24 | 2006-11-30 | Cingular Wireless Ii, Llc | Dynamic dual-mode service access control, location-based billing, and e911 mechanisms |
WO2007002725A1 (en) * | 2005-06-28 | 2007-01-04 | Mavenir Systems, Inc. | System and method for switching peer-to-peer multimedia in an enterprise network |
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 |
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 |
US8417285B2 (en) * | 2006-03-17 | 2013-04-09 | At&T Mobility Ii Llc | Mobility management message analysis |
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 |
US20080208671A1 (en) | 2007-02-28 | 2008-08-28 | Kate Ehrlich | System and method for matching people and jobs using social network metrics |
US8060451B2 (en) | 2007-06-15 | 2011-11-15 | International Business Machines Corporation | System and method for facilitating skill gap analysis and remediation based on tag analytics |
US8336708B2 (en) | 2007-07-20 | 2012-12-25 | Battenfeld Technologies, Inc. | System and container for organizing and carrying tools and tool sets |
US20090198733A1 (en) | 2008-02-01 | 2009-08-06 | Microsoft Corporation | Healthcare resource locator |
US8306921B2 (en) | 2008-02-13 | 2012-11-06 | Toyota Motor Engineering & Manufacturing North America, Inc. | Mobile recommendation and reservation system |
US20100010860A1 (en) | 2008-07-14 | 2010-01-14 | International Business Machines Corporation | System and method for social network routing for request matching in enterprise environments |
US8484352B2 (en) | 2009-03-30 | 2013-07-09 | Rave Wireless, Inc. | Emergency information services |
-
2006
- 2006-07-17 WO PCT/US2006/027658 patent/WO2007011861A2/en active Application Filing
- 2006-07-17 US US11/487,334 patent/US8090341B2/en not_active Expired - Fee Related
-
2011
- 2011-12-30 US US13/341,461 patent/US8489064B2/en not_active Expired - Fee Related
-
2013
- 2013-07-15 US US13/942,029 patent/US8954029B2/en not_active Expired - Fee Related
-
2015
- 2015-01-07 US US14/591,530 patent/US20150124657A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030115261A1 (en) * | 2001-02-26 | 2003-06-19 | Jahangir Mohammed | Apparatus and method for integrating an unlicensed wireless communications system and a licensed wireless communications system |
WO2003039009A2 (en) * | 2001-11-01 | 2003-05-08 | Nokia Corporation | Local service handover |
US20030125021A1 (en) * | 2001-12-28 | 2003-07-03 | Tell Daniel Francis | Method and apparatus for transmitting wired data voice over IP data and wireless data through a common IP core network |
US20050148353A1 (en) * | 2003-06-06 | 2005-07-07 | Hicks John A.Iii | System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed spectrum and wired access with licensed spectrum |
WO2005060292A1 (en) * | 2003-12-16 | 2005-06-30 | Kineto Wireless, Inc. | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2116029A1 (en) * | 2007-02-06 | 2009-11-11 | Telecommunication Systems, Inc. | Voice over internet protocol (voip) location based commercial prospect conferencing |
EP2116029A4 (en) * | 2007-02-06 | 2012-04-25 | Telecomm Systems Inc | Voice over internet protocol (voip) location based commercial prospect conferencing |
CN109150799A (en) * | 2017-06-16 | 2019-01-04 | 中国移动通信集团公司 | A kind of method and device obtaining called location information |
Also Published As
Publication number | Publication date |
---|---|
US8489064B2 (en) | 2013-07-16 |
US20150124657A1 (en) | 2015-05-07 |
US8090341B2 (en) | 2012-01-03 |
US8954029B2 (en) | 2015-02-10 |
WO2007011861A3 (en) | 2007-06-07 |
US20120100826A1 (en) | 2012-04-26 |
US20130303196A1 (en) | 2013-11-14 |
US20070014282A1 (en) | 2007-01-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8954029B2 (en) | Integrated services user part (ISUP)/ session initiation protocol (SIP) gateway for unlicensed mobile access (UMA) emergency services call flow | |
US9357078B2 (en) | SS7 ISUP to SIP based call signaling conversion gateway for wireless VolP E911 | |
US9197450B2 (en) | SS7 MAP/Lg+ to sip based call signaling conversion gateway for wireless VoIP | |
US9344578B2 (en) | SS7 ANSI-41 to SIP based call signaling conversion gateway for wireless VoIP E911 | |
US9544429B2 (en) | Solutions for voice over internet protocol (VoIP) 911 location services | |
US9374455B2 (en) | Systems and methods for providing emergency callback procedures | |
CA2561201A1 (en) | Method and apparatus for providing enhanced 911 for nomadic users | |
US20070201622A1 (en) | Method and apparatus for providing E911 services for nomadic users | |
WO2007100860A2 (en) | Method and apparatus for providing e911 services via network announcements | |
US9167403B2 (en) | Wireless emergency services protocols translator between ANSI-41 and VoIP emergency services protocols | |
US20100074419A1 (en) | Protocol converting 9-1-1 emergency messaging center | |
US8600009B1 (en) | Method and apparatus for mapping media access control addresses to service addresses |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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) | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06787550 Country of ref document: EP Kind code of ref document: A2 |