Providing position information that is independent of a communications network

Abstract

A method for use in providing position information in a communications network, comprising: Obtaining first mobile unit position information, separate from any wireless network cell antenna position information, for a mobile unit; Providing, substantially at a call time, the first mobile unit position information to a call routing center, wherein the mobile unit is a data network device and the call routing center is a selective router configured to route wireless telephony network calls; and Operating the call forwarding center to forward a call between the mobile unit and an answering center using the first mobile unit position information, the step of providing comprising: functionally arranging a positioning center between a Voice over Internet Protocol (VoIP) interface associated with the mobile unit and the call routing center; and Operating the positioning center to obtain the first mobile unit position information and providing the first mobile unit position information to the relay center.

Description

RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 62 / 372,673, filed August 9, 2016, entitled "LOCATION PROVISIONING FOR CALL ROUTING." FIELD OF THE INVENTION

[0002] The present invention generally relates to the provision of position information for mobile units, such as wireless units and nomadic VoIP units. The invention enables the provision of call routing information at a call time based on the position of a mobile unit and provides a VoIP solution that utilizes existing cellular telephony resources. The technology can be used to handle emergency calls and other position-based service contexts. BACKGROUND

[0003] For many years, emergency call services have been implemented in Europe, North America, and other areas. Generally, these emergency call services provide a 3-digit emergency number (e.g., 9-1-1 in North America and 1-1-2 in Europe) that can be used to connect individuals making an emergency call with appropriate public resources, such as emergency personnel. The objectives of such systems generally include routing the emergency call to an appropriate call center (dispatch center ("PSAP") in North America) for the location of the call, providing a callback number to the call center, and providing an accurate location to the call center to assist in dispatch.

[0004] Emergency services were first used in wired networks. Because wired telephones were essentially immobile, the caller's telephone number could easily be used to locate the call's location. The location could be loaded into an automatic location information ("ALI") database by a local exchange carrier, a mobile switching organization ("MSO"), or other device. This location could be used to route the call to the appropriate call center and provide a location to the call center. In particular, the telephone number could be used both to query a routing database to obtain the appropriate call center's emergency services number ("ESN") and to route the call through a selective router to the appropriate PSAP over a telephony infrastructure (e.g., a time-division multiplexing ("TDM") trunk).The telephone number could also be used to query the ALI using a subscriber network equipment ("CPE") at the PSAP, typically using an E2 or PSAP-to-ALI message ("PAM") protocol. The ALI is generally retrieved after the call has been routed to the call center, and the resulting ALI record (e.g., including a caller's street address) can then be forwarded to the call center and can then be associated with the call answerer so that the location information from the ALI can be displayed at the CPE. In this regard, the address may not arrive at the call center until some time has passed after the call is answered, which can cause a delayed dispatch response.

[0005] As wireless telephones become more widespread, the Federal Communications Commission (FCC) has mandated emergency services for wireless networks. This has been addressed through a series of regulations addressing the speed and accuracy of location information required for emergency calls, both for call routing and for providing location information to call centers.

[0006] Various sources of position information may be available in this regard. These can be categorized, for example, as cell antenna position information (National Emergency Number Association (NENA) Phase I) and mobile unit position information (NENA Phase II). Cell antenna position information relates to the network device handling the call and includes cell identification and cell sector information. For example, if a cell tower includes a three-sector antenna, the sector handling the call can be identified, thereby assigning the mobile unit to an area roughly corresponding to one-third of the tower's geographic coverage area (ignoring geographic and radio interference issues). Mobile unit position information corresponds to determining the mobile unit's instantaneous position, generally as geographic coordinates or geocode.Methods for acquiring such Phase II data include network triangulation technologies (e.g., TDOA, AOA, signal strength, etc.), satellite technologies (GPS, GNSS, etc.), and others.

[0007] More recently, the FCC (in the United States) has mandated emergency services for VoIP, at least when two-way voice calls are supported. Such VoIP calls can be placed from a substantially immobile computer, a mobile data unit, or a VoIP phone. There are a number of challenges regarding the use of emergency services for VoIP, including unit location and call center compatibility. A number of technologies are available or being developed for locating a VoIP unit, including GPS, hotspot positioning, wireless triangulation, node mapping, and others. Call center compatibility remains a technological and practical constraint because many older call centers (i.e., older PSAPs, such as those equipped for enhanced 9-1-1 ("E911")) are not equipped to handle VoIP calls.

[0008] Emergency call routing also remains problematic for mobile units, including wireless units and nomadic VoIP units. As stated above, a location is generally used twice in the context of an emergency call: a coarse location (e.g., Phase I data) for routing and a specific location (e.g., Phase II data) for distribution. In VoIP contexts, it has been challenging to provide even a coarse location at call time for routing to the appropriate call center. Even in wireless networks, routing failures occur. In particular, call routing is generally performed based on communications network-based data, such as antenna position and cell sector information. Cell sector boundaries do not always coincide with call center boundaries, and for various reasons, a call is not always handled by the nearest call center.Furthermore, if the call is routed to the wrong call center, the actual mobile unit location information (which is later relayed to the correct call center) may never reach the dispatcher. Therefore, many challenges remain for handling a wireless and VoIP emergency services call.

[0009] Typically, VoIP calls are routed to a VoIP interface or call server, which sends a request to a VoIP positioning center ("VPC"). The VPC contains a database (e.g., a Line Location Database ("SLDB")) of known VoIP phone locations and associated Unique Resource Identifier ("URI") numbers, e.g., manually entered by a network administrator. The VPC can use the stored location information to determine an appropriate Random Resource Number ("CRN") and PSAP for routing the call, which are returned to the VoIP interface. The VPC stores the Automatic Number Identification ("ANI") and ALI for the VoIP phone and loads a shell record using pseudo-ANI ("p-ANI") into an ALI database, while also mapping the p-ANI to the corresponding ANI.The call is sent to an Emergency Services Interface ("ESGW") by the VPC using the CRN (or Emergency Services Routing Number ("ESRN")) with the p-ANI. The ESGW connects the call to the appropriate selective router using the CRN (or ESRN). The selective router uses the ESN to route the call to the PSAP. Using pseudo-automatic number identification (p-ANI), the PSAP can query the VPC to obtain the ANI and ALI information stored for the relevant VoIP phone.

[0010] Similarly, mobile 9-1-1 calls (e.g., those originating from cellular phones) are routed to a mobile switching center ("MSC"). The switching center may send the device's ANI to a mobile positioning center ("MPC"). The MPC uploads a shell record, using a p-ANI specific to a PSAP, into an ALI database. The shell record feeds the PSAP back to the MPC's dynamic ALI database (e.g., one maintained by the carrier) for a current address. The MPC or wireless provider may utilize a positioning device ("PDE") for use with antenna towers. At call time, the PDE may send sector information or other positioning data to the MPC. The MPC may then associate the p-ANI with the ANI and return an ESN to the MSC. Using the ESN, the MSC routes the call to a selective router with the p-ANI based on the sector information.The selective router forwards the call to the PSAP with the p-ANI information. The PSAP then queries a static ALI via an E2 or PAM protocol for the record associated with the p-ANI. Based on the shell record, the PSAP (or the static ALI) can query the MPC's dynamic ALI via E2 or PAM, allowing the MPC's dynamic ALI to return the sector information to the PSAP. Upon subsequent queries from the PSAP ("re-queries"), the MPC can return more accurate position information as it becomes available over time. This procedure may cause delays in obtaining accurate position information at the PSAP.

[0011] Furthermore, emergency call handling systems have difficulty adapting to new technologies. As mentioned above, VoIP devices are becoming more widespread, and some proposals for handling emergency calls for VoIP devices would require significant upgrades to call centers and other facilities. At the same time, many countries and operational areas are evolving toward next-generation ("NG911") systems, which may require modifications to older call centers. More generally, there is a need to consider text, images, videos, and universal callback number availability, as well as handling emergency calls from sensors and other automated systems, to improve call center functionality.All these competing opportunities and interests have the potential to lead to a standstill, as it is unclear how to proceed with the development of emergency call systems that meet the requirements of new technologies in a cost-effective manner.

[0012] US 2016 / 0227589 A1 describes a system having an emergency call routing element, wherein the emergency call routing element may be configured to provide a location key and routing information for an emergency call initiated by an end-user device used by a caller, the routing information identifying a Public Safety Answering Point (PSAP). SUMMARY

[0013] The claimed invention is defined by the independent claims, while preferred embodiments form the subject matter of the dependent claims.

[0014] The present invention relates to the provision of location information and improved emergency services for mobile units, VoIP units, and mobile VoIP units. For brevity, "mobile unit" as used herein may refer to any VoIP phone whose location can be changed, cellular phone, mobile device, etc. The invention enables the use of current unit location information (Phase II), rather than just cell antenna location information (Phase I), for call routing. In this way, misdirected calls can be reduced and mobile unit location information is reliably provided to dispatchers. The invention also provides a system in which mobile unit location information for VoIP calls can be provided to wireless routing centers.An existing infrastructure is thus used to facilitate VoIP emergency call handling and improve emergency call routing for all mobile units. The invention also provides a universal solution for supporting VoIP, NG911, and legacy wireless emergency call systems, as well as text, image, and video functionality in a cost-effective manner.

[0015] According to one aspect of the present invention, a method is provided for providing position information in a communications network. A communications network may include a plurality of networks with different physical structures (e.g., antennas, wiring, optical fibers, etc.) and utilizing different protocols (e.g., SIP, HLED, TDM, CDMA, etc.). The method includes obtaining mobile unit position information, separate from any antenna position information of a wireless network cell, for a mobile unit. In other words, the mobile unit may obtain position information from a source that is independent of the communications network used to route a 9-1-1 call from the mobile unit. In the case where the mobile unit is a data network entity, such asFor a VoIP device, the first mobile unit position information or mobile unit position information may be dynamically determined based on one or more of a hotspot location, a satellite-based positioning technology, a beacon, a local IP connection, node mapping, or any other suitable means of sensing a position without, for example, relying on a mobile antenna or a Wi-Fi antenna used to initiate an emergency call. In this regard, the present systems and methods may not be based on PDE, cell tower triangulation, etc.

[0016] The method may further comprise providing, substantially at call time, mobile unit location information to a call routing center, and operating the call routing center to route a call between the mobile unit and a call answering center (i.e., a PSAP) using the mobile unit location information obtained independently of the communications network infrastructure. Accordingly, mobile unit location information may be used for call routing (rather than just for subsequent distribution), thereby enhancing call routing.

[0017] In one implementation, the mobile unit may be a data network entity, and the call routing center may be used, for example, to route emergency calls (or other calls) of other modalities, such as wireless telephony network calls. The call routing center may be any system adapted for such call routing. For example, protocols may be maintained to enable VoIP emergency call handling by legacy wireless network selection routers, so that existing resources can be used and immediate PSAP capability for VoIP calls and IP-based messaging is achieved. Providing the mobile unit position information may then involve arranging a VoIP positioning center between a VoIP interface connected to the mobile unit.mobile unit, and the call routing center, and operating the VoIP positioning center to obtain the first mobile unit location information and provide the location information to the routing center. In particular, a first path may be provided between the VoIP interface and the routing center for communicating the call, and a second path may be provided for communicating the mobile unit location information. At least a portion of the first path may implement TDM, whereas the second path may be a data network path. The method may further comprise transmitting a text message, a video message, or a data message between the mobile unit and the answering center.

[0018] According to a further aspect of the present invention, certain functionality of emergency call handling systems, as well as location-based non-emergency call services, is abstracted from underlying modalities and network topologies. In particular, position provisioning may be handled using universal (e.g., for VoIP, NG911, legacy wireless, etc.) platforms on a geographical basis that is independent of local regulations and network divisions, e.g., on a nationwide basis. Such functionality may include the functionality of conventional emergency call routing functions ("ECRF") and emergency service routing proxies ("ESRP"), as well as additional functionality. Position information may be obtained, e.g., from the device, from networks, or from a third-party position provider.The location can then be provided to call routing centers (including legacy wireless), call centers, location-based service applications, and the like. This allows for support of emergency and non-emergency calls across various networks, architectures, and protocols, including NG911, legacy wireless, OTT, IP, TDM, hybrid IP / TDM, E2, PAM, SIP, LIS, REST, etc. This provides some degree of insulation for various stakeholders from the complexities of technology evolution.

[0019] According to a further aspect of the present invention, a method for providing position information for a VoIP unit in a communications network is provided. The method comprises obtaining first mobile VoIP unit position information for a mobile VoIP unit and providing the mobile VoIP unit position information to a call routing center. In this regard, a VoIP positioning center may be arranged between a VoIP interface and the call routing center so that the mobile unit position information is obtained and provided to the routing center. The position information may be used for forwarding and / or distribution.In this way, an existing wireless telephony network structure is used to facilitate the provision of emergency services to VoIP units.

[0020] According to a further aspect of the present invention, a system for providing position information in a communications network is provided. The system comprises a positioning center, a call routing center, and a data network path connecting the positioning center and the call routing center. The positioning center obtains mobile unit position information, e.g., based on a hotspot position, a satellite-based positioning technology, or node mapping in the case of mobile data network units, or a satellite-based positioning technology or network triangulation technology in the case of wireless network units. This position information may be provided to the call routing center substantially at call time via a data network path.The position information can then be used for call forwarding and / or distribution in the event of emergency calls.

[0021] According to one embodiment of the present invention, a method for use in providing position information in a communications network is disclosed. The method may comprise obtaining first mobile unit position information, separate from any wireless network cell antenna position information, for a mobile unit. In this regard, mobile unit position information may be obtained from any suitable source, excluding cell sector information, such as may be provided by a PDE.The method may further comprise providing, substantially at call time, the first mobile unit location information to a call routing center and operating the call routing center to route a call between the mobile unit and an answering center using the first mobile unit location information.

[0022] In one aspect, the mobile unit may be a Commercial Mobile Radio Service (CMRS) compatible unit, and the first mobile unit position information may be based on one or more of a network triangulation technology and a satellite-based position technology.

[0023] In another aspect, the mobile unit may be a data network unit, and the first mobile unit position information may be based on one or more of a hotspot position, a satellite-based positioning technology, and node mapping.

[0024] In another aspect, the mobile unit may be a data network unit and the call routing center may be a selective router adapted to route wireless telephony network calls, and wherein the step of providing may comprise operatively disposing a positioning center between a Voice over Internet Protocol (VoIP) interface associated with the mobile unit and the call routing center and operating the positioning center to obtain the first mobile unit position information and providing the first mobile unit position information to the routing center.

[0025] In another aspect, the method may include providing a first path between the VoIP interface and the forwarding center for communicating the call (the first path may include at least a first portion implementing TDM, another telephony protocol, a SIP channel, etc.), and a second path separate from the first portion of the first path between the VoIP interface and the forwarding center for communicating the first mobile unit location information.

[0026] In another aspect, the call routing center may be associated with a plurality of call answering centers, and the step of operating may include matching the first mobile unit location information with a zone of one of the call answering centers and establishing a call channel between the first mobile unit and the one of the call answering centers.

[0027] In another aspect, the method may include providing second mobile unit location information for the first mobile unit that is identical to or different from the first mobile unit location information to one of the answering centers.

[0028] In another aspect, the method may include transmitting a text message, a video message, and a data message between the first mobile unit and the answering center.

[0029] According to a further embodiment of the present invention, a method for providing positioning information in a communications network is described. The method may comprise obtaining first mobile unit positioning information for a VoIP mobile unit, providing the first mobile unit positioning information to a call routing center, wherein the mobile unit may be a data network entity and the call routing center may be adapted to route wireless telephony network calls. The providing step may comprise operatively arranging a positioning center between a VoIP interface associated with the VoIP mobile unit and the call routing center.The method may further comprise operating the positioning center to obtain the first mobile unit position information and providing the first mobile unit position information to the relay center.

[0030] In one aspect, the method may include operating the call routing center to route a call between the mobile unit and an answering center using the first mobile unit location information.

[0031] In another aspect, the first mobile unit's position information may be obtained from a source external to a communications network through which an emergency call is routed from the mobile VoIP unit. For example, position information may be based on one or more of a hotspot location, satellite-based positioning technology, a location beacon, and node mapping.

[0032] In another aspect, the method may include providing a first path between the VoIP mobile unit and the forwarding center for communicating a call (the first path may include at least a first portion implementing time division multiplexing (TDM)), and a second path separate from the first portion of the first path between the VoIP interface and the forwarding center for communicating the first mobile unit location information.

[0033] In another aspect, the call routing center may be associated with a plurality of call answering centers, and the step of operating may include matching the first mobile unit location information with a zone of one of the call answering centers and establishing a call channel between the first mobile VoIP unit and the one of the call answering centers.

[0034] In another aspect, the method may include providing second mobile VoIP unit location information for the first mobile VoIP unit that is identical to or different from the first mobile unit location information to the one of the call answering centers.

[0035] In another aspect, the method may include transmitting a text message, a video message, and a data message between the first mobile VoIP unit and the answering center.

[0036] According to another embodiment of the present invention, a system for use in providing location information in a communications network is described. The system may include a positioning center for obtaining first mobile unit location information, separate from any wireless network cell antenna location information, for a mobile unit, a call routing center for routing a call between the mobile unit and an answering center using the first mobile unit location information, and a data network path for providing, substantially at call time, the first mobile unit location information to the call routing center.

[0037] In one aspect, the mobile unit may be a Commercial Mobile Radio Service (CMRS) compatible unit, and the positioning center may be operable to obtain first mobile unit position information based on one or more of a network triangulation technology and a satellite-based positioning technology.

[0038] In another aspect, the mobile unit may be a data network unit and the positioning center may be operable to obtain first mobile unit position information based on one or more of a hotspot position, a satellite-based positioning technology, and node mapping.

[0039] In another aspect, the mobile unit may be a data network unit and the call routing center may be a selective router adapted to route wireless telephony network calls, and the positioning center may be operatively located between a VoIP interface associated with the mobile unit and the call routing center, wherein the positioning center is operable to obtain the first mobile unit position information and to provide the first mobile unit position information to the routing center.

[0040] In another aspect, the system may include a first path between the VoIP interface and the call routing center for communicating the call, the first path including at least a first portion implementing a TDM, and a second path separate from the first portion of the first path between the VoIP interface and the routing center for communicating the first mobile unit location information.

[0041] In another aspect, the call routing center may be associated with a plurality of call answering centers and operable to match the first mobile unit location information with a zone of one of the call answering centers and establish a call channel between the first mobile unit and the one of the call answering centers.

[0042] In another aspect, the call forwarding center may be further operable to provide second mobile unit location information for the first mobile unit that is identical to or different from the first mobile unit location information to the one of the call answering centers.

[0043] In another aspect, the data network path may be further operable to transmit one of a text message, a video message, and a data message between the first mobile unit and the answering center. SHORT DESCRIPTION OF THE CHARACTERS Fig. 1 shows a system for providing location information associated with an IP device to a PSAP. Fig. Figure 2 shows a system architecture for providing emergency calls according to an embodiment of the present invention. Fig. Figure 3 shows a system for providing position information from a plurality of modalities to a central facility. Fig. 4 is a block diagram of a system for providing position information from a wireless device to a PSAP. Fig. 5 is a block diagram of a system for providing position information from a VoIP device to a PSAP. Fig. Figure 6a is a block diagram of a system for providing position information from a mobile VoIP device to a PSAP. Fig. Figure 6b is a block diagram of a system for providing position information from a mobile VoIP device to a PSAP. Fig. Figure 7 is a block diagram illustrating the routing of information, including text messages, images, and other voice and non-voice data, from a mobile device to a PSAP. Fig. Figure 8 is a block diagram showing the routing of information from a mobile device to a PSAP during transition to a nationwide ESRP. Fig. Figure 9 is a block diagram showing the forwarding of information from a mobile device to an NG911 PSAP during the transition of a legacy PSAP. DETAILED DESCRIPTION

[0044] While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the invention is not intended to be limited to the specific form disclosed, but rather, the invention is intended to include all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the claims.

[0045] Fig. 1 shows a system 100 for use in providing location information in a communications network serving as a VoIP device. A user may access a workstation 101 to enter location information (e.g., a street address) associated with the VoIP phone 106. The location information may be transmitted through channel 102 to the provisioning server 103. It should be noted that the term "channel," as used herein, may refer to any path, medium, protocol, etc., operable to provide the described functionality. Although some channels may be described, by way of example, as utilizing a particular protocol, any suitable protocol may be utilized.The provisioning server 103 may transmit the location information via channel 104 to a VPC's access line database ("SLDB") 105, where the location information may be stored in memory. After dialing an emergency services number (e.g., 9-1-1) from a VoIP phone 106, the call may be forwarded to the call server 108 via a Session Initiated Protocol ("SIP") channel 107. The call server 108 may send a Uniform Resource Identifier ("URI"), such as an ANI, associated with the VoIP phone 106 to the VPC's proxy server 110. The proxy server 110 may then send a request to the SLDB 105 via channel 111, in response to which the SLDB 105 may send the location information associated with the URI to the proxy server 110.The proxy server 110 or another component of the VPC may reference the location information against an emergency routing database ("ERDB") 121 to determine an appropriate random routing number ("CRN"), e.g., an ESRN. The CRN may then be returned to the call server 108 (which may be the same as or different from channel 109) via channel 112. The call server 108 may transmit the call and CRN via channel 113 to an ESGW 114 of a VoIP carrier. The ESGW 114 may transmit the call via channel 115 to a public switched telephone network ("PSTN") for transfer to an operator routing support service ("ORSS") 116 of an emergency services network. The ORSS 116 may transfer the call via channel 117 to a local agent 118, such as a dispatcher or emergency response switch.The local agent 118 or the associated PSAP CPE can send a request for the location information via channel 119 to a local ALI 120, which in turn can transmit a request to the VPC's ALI link 122. In response, the local ALI 120 can receive the location information. This system architecture can be particularly applicable in the case of a stationary VoIP device, but is very problematic in the case of a mobile VoIP device due to the reliance on manually entered and stored location information.

[0046] The Fig. 2 shows a system 200 for use in providing position information in a communications network. An ALI / Local Connection Service ("LIS") database 201 (e.g., an NG911 ALI / LIS database) may be coupled to a legacy ALI 202 via an HTTP channel 203. The ALI / LIS database 201 may also be coupled to an Emergency Call Routing Function ("ECRF") 204 via an HTTP channel 205 and an NG911 PSAP 206 via an HTTP channel 207. The ECRF 204 may be coupled to an Operations Support System ("OSS") 208 via an HTTP channel 209 and a VoIP Session Border Controller ("SBC") NG911 Emergency Service Routing Proxy ("ESRP") 210 via a SIP channel 211. The ESRP 210 may be coupled to a TDM interface 212 via a Real-Time Transport Protocol (“RTP”) channel 213.The ESRP 210 may also be coupled to a plurality of service networks 214, 216, 218 (including, but not limited to, VoIP service providers ("VSPs"), over-the-top ("OTTs"), and mobile network operators ("MNOs"), as shown) via RTP channels 215, 217, and 219, respectively. The ESRP 210 may also be coupled to the NG911 PSAP 206 via RTP channel 220. The TDM interface may be coupled to a legacy selective router 221 via a TDM trunk 222, and the selective router may be coupled to at least one legacy PSAP 223 via a TDM trunk 224. The OSS 208 can be coupled to the service networks 214, 216, 218 via SIP channels 225, 226, and 227, respectively.

[0047] The ECRF 204, which may be publicly available, can provide routing instructions, and the VoIP-SBC-NG911-ESRP 210 can replace selective routers. The ESRP 210 can transition to mobile 911 functionality on a per-call basis for PSAPs that are not NG911-compliant. This architecture is designed to support voice, text, video, and other enriched data.

[0048] The Fig. 3 shows a system 300 for providing location information from a plurality of originating communication systems. A workstation 301 and a VoIP phone 302 may be operatively connected to a VoIP provisioning system 303. The VoIP provisioning system 303 may be operatively connected to the VPC 304, which in turn is operatively connected to the central 9-1-1 system service provider ("SSP") facility 306. In particular, the VPC 304 may be operatively connected to the ALI 305 of the central 9-1-1 SSP facility 306 for transmitting data (e.g., voice calls or location information) thereto. It should also be noted that although the central facility is described here as being related to a 9-1-1 SSP, this relationship is for illustrative purposes only and a facility that has a selective router and / or an ALI database may be related to an emergency services provider (e.g., 9-1-1).

[0049] A wireless outside station ("OSP") provisioning system 307 may be operatively connected to an MPC 308, which in turn is operatively connected to the ALL 305, and the mobile VoIP provisioning system 309 may be operatively connected to the M-VPC 310, which in turn is operatively connected to the ALI 305. One or more p-ANIs may be used to establish a connection between each positioning center and the ALI 305 (or the associated selective router) so that positioning information from the various provisioning centers 304, 308, 310 can be stored at the ALI 305.

[0050] The system architecture of Fig. 3 enables the implementation of 911 location services by a mobile system, a VoIP system, and a mobile VoIP system using a common infrastructure. A further explanation of the communication between the provisioning systems, positioning centers, ALI, and the selective router is provided below with respect to the Fig. 4 to 6 are indicated.

[0051] The Fig. 4 shows a system 400 for providing position information in a wireless network. An MPC may load a shell record with a p-ANI into the ALI 407. The mobile unit 401 may initiate an emergency call using an antenna mast 402. The antenna mast 402 may relay the call to a mobile switching center ("MSC") 404. The antenna 402 may be connected to the PDE 403 for jointly determining position information 410 associated with the mobile unit 401. It should be noted that although the PDE 403 is shown as being directly connected to the antenna mast 402, it is contemplated that the PDE, such as the PDE 403, may be located at any suitable location within the system. For example, the PDE 403 may be located adjacent to and / or in functional communication with the MPC.The PDE 403 may also be in functional communication with the MSC 404 regarding location information for selecting the appropriate selective router 408 to route an emergency call. The PDE 403 may transmit location information to the MPC's dynamic ALI 405. The MPC may reference a database 406 to determine a PSAP associated with the location information. A CRN associated with the PSAP may be returned to the MSC 404 for forwarding the call 411 to the appropriate selective router 408. In some cases, an emergency call may be forwarded by the MPC before being received at the selective router 408. Either the MPC or the PDE 403 itself may convert the location information from SIP or REST API and deliver it in the same manner as in Phase II. The position information can in turn be forwarded to the ALI 407 of a central 9-1-1 SSP facility.The call and position information can be forwarded to the PSAP 409a-n based on the position information. Subsequent position updates to the ALI 407 can occur via SIP updates, customer-updated LIS, or REST API. Certain PSAPs can support voice, text, and video.

[0052] It should be noted that in the Fig. 4 to 6b, certain communication channels are indicated with an "L" for "position" information, while other channels are indicated with a "C" for "call." It should be noted that these indications are intended only to generally indicate the paths of voice data relative to position information. In some cases, other data may be transmitted through these channels, such as CRNs, ESRNs, PSAP numbers, etc.

[0053] The Fig. 5 shows a system 500 for providing location information in a VoIP network. The VoIP phone 501 can initiate an emergency call using a VoIP interface 504, operated, for example, by a VoIP service provider. The VoIP interface 504 can transmit location information 510 to the database 505 of a VPC. The VPC can return an ESRN or CRN to the VoIP interface 504 to forward the call 511 to the selective router 508. The location information can also be forwarded to the ALI 507 of a central 9-1-1 SSP facility, and the call can be forwarded to a selective router 508 of the central 9-1-1 SSP facility. The call and location information can be forwarded to a PSAP 509a-n according to the location.

[0054] The Fig. 6a shows one embodiment of a system 600 for providing location information in a wireless VoIP network. The mobile unit 601a may initiate an emergency call 611 using an antenna 602 (e.g., a mobile network tower, a WiFi antenna, a hotspot, etc.). The antenna 602 may relay the call to the MSC 604 and send location information 610a obtained from the mobile unit 601a to the database 605a of an M-VPC. It is also contemplated that the M-VPC may return location information to the MSC 604 to route the call. For example, the M-VPC may contain shape files that are compared with the location information to identify an appropriate selective router or PSAP. Additionally or alternatively, the M-VPC may send a p-ANI to the MSC 604 to associate the call with a PSAP.

[0055] The MSC 604 may, in some cases, forward the call to the selective router 608, or in other cases, forward the call to the M-VPC's server 606 (this path is not shown). In the latter case, location information and the call (which may be voice, text, video, etc.) may follow the same path through the network, even though they are split across different channels. For example, in certain protocols (such as VoLTE), a single call path may comprise multiple carrier signals, such as a signaling carrier and a voice carrier. In this regard, the voice call, text message, video, photo, etc., may be transmitted in the voice carrier, while the location information is transmitted in the signaling carrier, or vice versa.Alternatively, a call may be transmitted using both the signaling carrier and the voice carrier, while the position information is transmitted using an additional, separate channel.

[0056] The position information 610a may be obtained at the mobile unit 601a through a channel independent of the communications network to which the antenna 602 is associated. For example, the mobile unit 601a may be located within range of a beacon that transmits position information associated with a particular area. As an example, each floor of an office building may have a beacon that broadcasts the building address and floor. In this regard, the mobile unit 601a may obtain position information from a beacon within range (e.g., the beacon with the highest perceived signal strength) and relay this position information to the network antenna.As further non-limiting examples of sources of position information, the mobile unit 601a may obtain position information from a global positioning system, through a WiFi hotspot, an IP connection, node mapping, or any other source external to the antenna 602 and devices that may be associated therewith (e.g., a PDE).

[0057] The location information may be forwarded from the M-VPC to the ALI 607 of a central 9-1-1 SSP facility, and the call may be forwarded to a selective router 608 of the central 9-1-1 SSP facility. The call and location information may be forwarded to a PSAP 609 according to the location information. It is contemplated that, in some embodiments, a national (or other regional) central 9-1-1 SSP facility may be implemented such that all emergency calls are forwarded from the MSC 604 to a single selective router 608. In this regard, the call 611 and the location information 610a may be transmitted via separate paths to the central 9-1-1 SSP facility, at which point they are paired by the selective router 608 and / or the ALI 607 before being transmitted to the appropriate PSAP via individual or separate channels.

[0058] The Fig. Figure 6a shows a system similar to that of Fig. 6b. However, the mobile unit 601b may transmit position information 610b to the database 605b of the M-VPC through a channel that omits the antenna 602. In this regard, a call (e.g., a voice call, text, photo, video, etc.) may be relayed through the antenna 602, while the position information is relayed through another medium. For example, the mobile device 601b may be located in an office building with access to a WiFi connection. The mobile device 601b may also have access to a mobile data network (e.g., LTE) associated with the antenna 602. The call 611 may be relayed through the antenna 602 and the mobile data network, while the position information 610b is relayed through the WiFi connection to the M-VPC.

[0059] The Fig. 7 shows a system architecture 700 for forwarding information, including text messages, images, precise location information, and other voice and non-voice data, from a mobile device to a PSAP. This architecture may enable non-voice data, such as images, text messages, videos, etc., to be transmitted to a PSAP equipped for legacy 9-1-1 (e.g., phone voice data only) or enhanced 9-1-1 (e.g., phone voice and location only). The location information for a device may be retrieved from an underlying operating system. This information may come from a GPS receiver, a Wi-Fi connection, or any other integrated or separate device. In some cases where a device is mobile, the location information may be automatically stored for retrieval at regular intervals if necessary.For convenience, a pre-formed SIP header may be available for insertion into the SIP client for communication using the 710 protocol. A direct HTTPS REST API may be used for location information, and a simple API may be available for sending emergency text messages.

[0060] An application 701 operating on a mobile device may utilize a plurality of communication protocols 708, 709, 710 to establish communication with a positioning center 702 (e.g., MPC, VPC, M-VPC, etc.). Protocol 708 may be Short Message Peer-to-Peer ("SMPP"), which may be operated to transmit short messages. Protocol 709 may be HTTPS, which may be operated to transmit photographs, videos, documents, location information, etc. Protocol 710 may be SIP, which may be operated to transmit voice calls, video phone calls, instant messages, etc. It should be noted that the functionality of these various protocols may overlap, and fewer or more protocols may be used to provide the functionality of transmitting enriched data (i.e., more than just voice, phone number, and location) as needed.The positioning center 702 may access a database 704 to query a shape file or other data suitable for selecting an appropriate PSAP. Any enriched data that the PSAP is not equipped to receive through the selective router 705 (e.g., Phase II position information, photos, videos, etc.) may be transmitted to the dynamic ALI 703. A telephone call or other communication may be forwarded from the positioning center 702 to the selective router 711 via the trunk 711 (e.g., Centralized Automated Message Accounting ("CAMA"), Signaling System No. 7 ("SS7")). The telephone call may be forwarded with basic position information and / or the telephone number associated with the mobile unit. The selective router 705 may forward the telephone call via the trunk 712 (e.g.,CAMA, SS7) to the appropriate PSAP 706 as identified by the positioning center 702. The PSAP may access the ALI 707 via the Frame / IP channel 713. In response, the ALI 707 may send a request to the dynamic ALI 703 via the Frame / IP channel 714 to retrieve the enriched data deposited by the positioning center 702. In this regard, the agent at the PSAP 706 may have access to the enriched data (sent by the caller) substantially simultaneously with receiving the call.

[0061] Alternatively, a telephone call need not be placed by the mobile unit user. Rather, a text message or other emergency indication may be sent using application 701. In response, positioning center 702 may simulate a telephone call to selective router 705 to initiate an emergency response from PSAP 706 as if a call had been placed. In this regard, the simulated telephone call may prompt PSAP 706 to retrieve the text message or other enriched data from dynamic ALI 703. In this manner, a PSAP equipped only for E911 operation may operate in a manner similar to NG911.

[0062] The Fig. 8 shows a system architecture 800 for forwarding information from a mobile device to a PSAP, e.g., during transition to a nationwide ESRP. The OSP 801 may transmit data to the ECRF / Location Validation Function ("LVF") 802 using a Location-to-Service Translation ("LOST") protocol 812. The OSP 801 may communicate with a legacy ESRP 805 using an SMPP protocol 813, an HTTPS protocol 814, and SIP 815. The legacy ESRP 805, in turn, may transmit data to the Emergency Call Routing Function / Location Validation Function (ECRF / LVF) module 802 using the LOST protocol 816. The ECRF / LVF module 802 may be in functional communication with the shape file database 803 and the address information database 804. The legacy ESRP 805 can establish communication with a national / state / regional ESRP 806 and NG911 PSAP 807, both connected via SIP 817, 818.The ESRP 806 and NG911 PSAP 807 can query enriched data from the LIS dynamic ALI 811 via HLED 819, 820. The legacy ESRP 805 can be operated to update the LIS dynamic ALI 811 with enriched data and position information. The legacy ESRP 805 can also be in functional communication with the selective router 808 via trunk 821 (e.g., CAMA, SS7). The selective router 808 can, in turn, be in functional communication with the legacy PSAP 809 via trunk 822, which in turn can query information from the legacy ALI 810 via frame / IP 823. The legacy ALI 810 can query enriched data from the LIS dynamic ALI 811 via frame / IP 824.

[0063] The Fig. 9 shows a system architecture 900 for forwarding information from a mobile device to an NG911 PSAP in a transition state, e.g., during migration from a legacy PSAP. The OSP 901 may transmit data to the ECRF / LVF module 902 using a LOST protocol 912. The OSP 901 may also communicate with the ESRP 905 using an SMPP protocol 913, an HTTPS protocol 914, and SIP 915. The ESRP 905, in turn, may transmit data to the ECRF / LVF module 902 using the LOST protocol 916. The ECRF / LVF module 902 may be in functional communication with the shape file database 903 and the address information database 904. The ESRP 905 may establish communication with the NG911 PSAP 906 using SIP 917. The NG911-PSAP 906 can query enriched data from the LIS dynamic ALI 911 using HLED 919.The ESRP 905 can be operated to update the LIS dynamic ALI 911 with enriched data and position information. The ESRP 905 can be in functional communication with the selective router 908 via trunk 921a (e.g., CAMA, SS7) and / or 921b. The selective router 908 can, in turn, be in functional communication with the legacy PSAP 909 via trunk 922, which in turn can request information from the legacy ALI 910 via frame / IP 923. The legacy ALI 910 can request enriched data from the LIS dynamic ALI 911 via frame / IP 924.

[0064] During the transition of a legacy PSAP to NG911, the existing selective router network can be used. Telephone call routing from a selective router 908 to a PSAP 909 can be based on a pre-transition ESN. During the transition, the PSAP 909 can interoperate with the ESRP 905 and the LIS dynamic ALI 911 through an NG911 CPE. After testing is complete, the ESN can be rerouted to a selective router trunk. Calls from legacy OSPs can be routed through their existing selective router access, but the call can be forwarded to the ESRP 905. The ESRP 905 can then query the LIS dynamic ALI 911. As a fallback, the PSAP 909 can query the static ALI 910. The ESRP can forward the call to the PSAP 906 via SIP 917.

[0065] During the migration of an OSP to NG911, the OSP can be operated to forward NG911 data to the ESRP 905 via SIP 915 or through NENA i3. The selective router 908 can operate in parallel with the ESRP 905. The older ALI 910 can be supported until the OSP migration is completed. By leveraging the architecture that is related to the Fig. 9, a single PSAP can be migrated to NG911 on any selective router with MPC connectivity.

[0066] While the invention has been shown and described in detail in the drawings and the foregoing description, such illustration and description are to be considered as illustrative and not restrictive. For example, certain embodiments described hereinabove may be combined with other described embodiments and / or arranged in a different manner (e.g., method elements may be performed in different sequences). Accordingly, it should be understood that only a preferred embodiment and variations thereof have been shown and described, and modifications that come within the spirit of the invention are intended to be protected.

Claims

[1] A method for use in providing position information in a communications network, comprising: Obtaining first mobile unit position information, separate from any wireless network cell antenna position information, for a mobile unit; Providing, substantially at a call time, the first mobile unit position information to a call routing center, wherein the mobile unit is a data network device and the call routing center is a selective router configured to route wireless telephony network calls; and Operating the call forwarding center to forward a call between the mobile unit and an answering center using the first mobile unit position information, the step of providing comprising: functionally arranging a positioning center between a Voice over Internet Protocol (VoIP) interface associated with the mobile unit and the call routing center; and Operating the positioning center to obtain the first mobile unit position information and providing the first mobile unit position information to the relay center. [2] The method of claim 1, wherein the mobile unit is a Commercial Mobile Radio Service (CMRS) compatible unit and the first mobile unit position information is based on one or more of a network triangulation technology and a satellite-based positioning technology. [3] A method according to claim 1, wherein the first mobile unit position information is obtained from a source external to a communications network through which the call is routed from the mobile unit. [4] The method of claim 3, wherein the mobile unit is a data network unit and the first mobile unit position information is based on one or more of a hotspot position, a satellite-based positioning technology, a position beacon, and node mapping. [5] The method of claim 1, further comprising: Providing a first path between the VoIP interface and the routing center for communicating the call, the first path comprising at least a first portion implementing TDM, and a second path, separate from the first portion of the first path, between the VoIP interface and the routing center for communicating the first mobile unit position information. [6] The method of claim 1, wherein the call forwarding center is associated with a plurality of call answering centers and the step of operating comprises matching the first mobile unit position information with a zone of the call answering center and establishing a call channel between the first mobile unit and the one of the call answering centers. [7] The method of claim 6, further comprising providing second mobile unit position information for the first mobile unit, which is identical to or different from the first mobile unit position information, to the one of the call answering centers. [8] The method of claim 1, further comprising: Transmitting one of a text message, a video message and a data message between the first mobile unit and the answering center. [9] A system for use in providing position information in a communications network, comprising: a positioning center for obtaining first mobile unit position information, separate from any antenna position information of a wireless network cell, for a mobile unit; a call routing center for routing a call between the mobile unit and an answering center using the first mobile unit location information, wherein the mobile unit is a data network device and the call routing center is a selective router configured to route wireless telephony network calls; and a data network path for providing, substantially at a call time, the first mobile unit position information to the call routing center, and the positioning center is operatively located between a VoIP interface associated with the mobile unit and the call routing center; wherein the positioning center is operable to obtain the first mobile unit position information and provide the first mobile unit position information to the routing center. [10] The system of claim 9, wherein the mobile unit is a Commercial Mobile Radio Service (CMRS) compatible unit and the positioning center is operable to obtain the first mobile unit position information based on one or more of a network triangulation technology and a satellite-based positioning technology. [11] The system of claim 9, wherein the mobile unit is a data network unit and the positioning center is operable to obtain the first mobile unit position information based on one or more of a hotspot position, a satellite-based positioning technology, and node mapping. [12] The system of claim 9, further comprising: a first path between the VoIP interface and the routing center for communicating the call, the first path comprising at least a first portion implementing TDM, and a second path, separate from the first portion of the first path, between the VoIP interface and the routing center for communicating the first mobile unit position information. [13] The system of claim 9, wherein the call forwarding center is associated with a plurality of call answering centers and is operable to match the first mobile unit position information with a zone of the call answering center and establish a call channel between the first mobile unit and the one of the call answering centers. [14] The system of claim 13, wherein the call forwarding center is further operable to provide second mobile unit position information for the first mobile unit, identical to or different from the first mobile unit position information, to the one of the call answering centers. [15] The system of claim 9, wherein the data network path is further operable to transmit one of a text message, a video message, and a data message between the first mobile unit and the answering center.

Images