Telecommunication Systems, Inc.

Other

Telecommunications Systems, Inc.

Roger Stuart Marshall

Yinjun Zhu

Richard Lee Dickinson

Steven P Helme

Donald LeRoy Mitchell, Jr

Gordon John Hines

Victor C Burton

Myron D'Souza

Todd Poremba

Fei Yang

Andrew M Singer

Firdaus Aryana

Robert Ehrlich

Mark Titus

Don P Mitchell

John Gordon Hines

Thomas S Ginter

Jonathan Alan Croy

Jeffrey Thomas Martin

Drew Morin

Kent A Hellebust

Thomas Woodrow Nesmith

Stephen Lee Harrison

Matthew B Davis

An emergency gateway can receive carrier location information from a carrier location server for an end-user device that initiated an emergency services call. The emergency gateway can also receive supplemental location information for the end-user device from a supplemental location server and select one of the carrier location information and the supplemental location information. The emergency gateway can generate routing information for the emergency services call based on the selected location information, wherein the routing information identifies a given Public Safety Answering Point (PSAP) for the emergency services call. Further, the emergency gateway can route the emergency services call to the given PSAP based on the routing information.

Supplemental location information for an emergency services call

Network devices in an Ad-Hoc wireless network self-survey themselves as necessary for approximate location or precise position information, based on methods employed, particularly useful for a non-open-sky environment. A WiFi Access Point (AP) with or without an internal GPS receiver and location conveyance support may utilize the mesh technique. If an Ad-Hoc network device is unable to contact a suitable location server, or a position request has otherwise failed to deliver a precise position, a WiFi AP is manually configured with appropriate location information, and then offers itself as if it were a location server (thereby becoming an 'internal' server', containing either the determined or provisioned location of itself, for use by other APs or devices). A location server (either internal to the AP needing location, or external), performs a 'mesh&#x2019; location determination by selecting position information from 3 or more location determined APs for subsequent processing.

Automated location determination to support VoIP E911 using self-surveying techniques for ad hoc wireless networks

An Automatic Location Identifier (ALI) trigger mechanism can include a data tap configured to detect an ALI location request for an emergency services call. The data tap can also be configured to output a trigger signal in response to detecting the ALI location request. The ALI trigger mechanism can also include a metadata router configured to receive the trigger signal and output an enhanced caller information request to a metadata server in response to the trigger signal.

Trigger mechanism

An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a mobile VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Mid-call updating of location of a moving VoIP terminal is provided to a PSAP. The location of the VoIP is validated using HTTP based protocol by pushing location information to a VoIP location server, and comparing it against a geographic location database to confirm that a contained street address is valid.

Solutions for voice over internet protocol (VoIP) 911 location services

A SIP ancillary data server provides host to auxiliary data for an emergency SIP session (call) uniquely referred to in a transported SIP header. In a manner similar to how location is represented in an emergency call, a SIP header is extended. The extended SIP Header contains one of two possible types of content elements: either (a) a content pointer element to a SIP Message body part (a 'cid:', or content identifier); or (b) an &#x3c;information_URI&#x3e; (a.k.a, 'info_URI' in this document).

Ancillary data support in session initiation protocol (SIP) messaging

A system can include an emergency call routing element comprising one or more computing devices. The emergency call routing element can be configured to provide locator key and routing information for an emergency services call initiated by an end-user device employed by a caller, wherein the routing information identifies a Public Safety Answering Point (PSAP). The emergency call routing element can also be configured to provide a notification of the emergency services call. The system can also include an ancillary data server comprising one or more computing devices. The ancillary data server can be configured to receive the notification of the emergency services call and query an information source for information related to at least one of the end-user device and the caller in response to the notification. The ancillary data server can further be configured to provide a web service interface that outputs ancillary information that characterizes ancillary data.

Ancillary data for an emergency services call

A data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location.

Emergency 911 data messaging

An E-9-1-1 voice-over-IP (VoIP) solution is provided wherein a 911 call from a wireless VoIP device is routed directly to the correct Public Safety Answer Point (PSAP) via dedicated trunks, together with correct location information and call-back number. VoIP gateways are implemented locally, at least one per LATA, and accept VoIP packetized data inbound, and convert it to standard wireline voice calls. Calls are routed to an IP address at the VoIP gateway, which then egresses the call to a voice port at a selective router. Dedicated voice trunks (CAMA, SS7, FG-D) are installed between each local VoIP gateway and appropriate selective routers. An Automatic Location Identification (ALI) database is provisioned with ESRKs dedicated for VoIP use. TCP/IP circuits may be established between some or all of the various local VoIP gateways.

Enhanced E911 location information using voice over internet protocol (VoIP)

A gateway can be configured to receive an emergency event message in a predefined format via a network. The emergency event message can characterize a location and a nature of an emergency event. The gateway can also be configured to identify a particular Public Safety Answering Point (PSAP) customer premise equipment (CPE) to service the emergency event. The gateway can further be configured determine a format of messages employable by the particular PSAP. The gateway can still further be configured to provide the particular PSAP CPE with an output message in the format employable by the particular PSAP CPE. The output message can characterize the nature and the location of the emergency event.

Emergency event message

A method and mechanism to allow a location server to initiate a user plane location service (e.g., SUPL defined by OMA) procedure to a user plane enabled device via Instant Messaging, or alternatively, via an existing SIP session if a multimedia session is already established. The location request is signaled to the user plane enabled device via a SIP INFO message. The location request uses SIP messaging to overcome firewall and other network security issues. Location using SUPL over SIP may be provided about a caller making an E911 emergency call. An Instant Message may be sent to the user plane enabled device, e.g., a VoIP wireless phone.

User plane location services over session initiation protocol (SIP)

A short messaging system (SMS) emergency services 911 system (SMS E911). Excess non-voice capacity is used to establish a Short Message Service (SMS) capability for generating an emergency 911 'equivalent' call, together with location information required by emergency services and to meet Federal 911 requirements. 911 requests for emergency assistance are delivered using non-voice centric sources such as SMS, email, and/or autonomous data/message generation devices. SMS 911 capability enables SMS savvy consumers to generate requests for emergency assistance to the local Public Safety Answering Point (PSAP). The SMS 911 emergency services request can be understood by an otherwise conventional PSAP, including provision of location information, and translated to provide first responders with the emergency services information they need to offer timely assistance.

911 data messaging

Automatic Location Information (ALI) data that is representative of a landline address is digitally retrieved, and automatically transferred to an emergency call taker over a wireless system emergency network. Importantly, the ALI information is determined based on association to a proximate location. Before an emergency call is initiated, additional environmental information, such as a RFID tag, location beacon, WiFi access point, Bluetooth device, or other communication signal with a known location, is included in the wireless session data exchange, used to match one or more location inputs to a fixed civic location (street address) which is used to dispatch emergency responders. Alternatively, the mechanism matches to a precise geodetic location (e.g., where no civic location is available).

Automated proximate location association mechanism for wireless emergency services

Dynamically selecting and facilitating stored caller information to a communications recipient device with a communications event, based on communication recipient credentials (e.g. MDN, etc.), preferences outlined in a subscriber profile associated with a relevant calling device, and other variables, e.g., time of day, etc. A subscriber provisions subscriber preferences and subscriber information associated with users of a subscribing communications device in to a subscriber profile, for use during a communications event. Subscriber preferences place restrictive conditions on stored subscriber information that may be transmitted with a communications event initiated by a corresponding communications device. A content collection node dynamically selects customized caller information via a subscriber information content collection process. Customized caller information is transmitted to appropriate recipient devices with a corresponding communications event. In the event of a 911 communications event, customized caller information may be transmitted to emergency dispatch personnel via the legacy E2 query interface.

Wireless emergency caller profile data delivery over a legacy interface

The risk that an incoming emergency call is a prank call is presented in real-time to the called party, in the form of, e.g., an index of suspicion. An index of suspicion aggregation server quantifies, qualifies, and aggregates risks, suspicions, and/or threats relevant to a call center to formulate a scale of suspicion. Metrics are acquired (e.g., calling device location information, device configuration information, caller information, etc.) relevant to each communications request made to a call center and uses acquired metrics to rate communications requests based on a known scale of suspicion. Once a suspicion rating is determined for a communications request, the communications request is routed to a relevant call-taker terminal, as is the index of suspicion for that incoming call. Real time presentation of the index of suspicion enables call-takers to make better call-handling decisions based on risk analysis and historical call data associated with a given caller.

Growing community of inventors

Auburn, WA, United States of America

Roger Stuart Marshall