Abstract: Methods for ERL Correction are provided including receiving a VoIP emergency call from an emergency caller. The VoIP emergency call is identified by a unique ELIN. The ERL data associated with the unique ELIN is retrieved from a LIS using the unique ELIN. A notification is intercepted at the LIS. The notification contains both an original extension number or a DID number and the ERL data. The ERL data is matched using the ELIN to the ERL data to locate one of the original extension number and the DID number. A correct physical address is located using the original extension number or the DID number. Address data is corrected in the ERL to include the correct physical address of the emergency caller to provide a corrected ERL. The notification is reissued including the corrected ERL and the VoIP emergency call is routed to a PSAP with the corrected ERL.

Abstract: Techniques for providing SOS call routing for emergency calls are disclosed. One example system includes a first computing device that receives a message including identification information from a telephony endpoint; and retrieves location information for an IoT device based on the message. The system includes a second computing device that receives a call from the telephony endpoint that includes call information. The first computing device receives a notification of the call from the second computing device that includes the call information; verifies the call is associated with the message based on the identification information and call information; and generates instructions for the second computing device that includes forwarding the call using the location and callback information to a public safety answering point (PSAP).

Abstract: Disclosed are techniques for enabling an emergency call routing system. The system comprises a Voice-over Internet Protocol (VoIP) position center (VPC) server and a location information server (LIS). The VPC server may be configured to receive a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server. The VPC may also respond to the source of the SIP INVITE message with a SIP redirect response that includes routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP. The LIS server may be configured to receive and store telephone number provisioning information from a TSP, the information including registered address data for the telephone number. The LIS may also receive and store PSAP capability data, the PSAP capability data indicative of the PSAP being i2 capable or i3 capable.

Abstract: Disclosed are techniques for enabling an emergency call routing system. The system comprises a Voice-over Internet Protocol (VoIP) position center (VPC) server and a location information server (LIS). The VPC server may be configured to receive a session initiation protocol (SIP) INVITE for an emergency call intended for a destination public safety answering point (PSAP) from a telecommunication service provider (TSP) SIP call server. The VPC may also respond to the source of the SIP INVITE message with a SIP redirect response that includes routing data compatible with and capable of enabling the TSP SIP call server to route the emergency call to the destination PSAP. The LIS server may be configured to receive and store telephone number provisioning information from a TSP, the information including registered address data for the telephone number. The LIS may also receive and store PSAP capability data, the PSAP capability data indicative of the PSAP being i2 capable or i3 capable.

Abstract: Device independent access to stored caller data during an emergency communications event. A call server intercepts an emergency call and determines the capabilities of a calling device. Based on calling device capability, the call server uses one or more of the following device independent methods to ascertain a caller identity, independent of a calling device: interactive voice response redirect, HTTP authentication, SIP INFO method, biometric recognition, human interaction, and alternate number dialing. A caller identity is then used to query a subscriber database for a unique caller profile database key (CPDBK) assigned to the caller (unless a CPDBK is already determined). A call server uses a CPDBK to query a caller profile database (CPDB) for relevant caller data. Relevant caller data and the intercepted emergency communications event are then passed to an emergency call processing system, whereby relevant caller data may be used to more effectively address an emergency situation.

Abstract: 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.

Abstract: Device independent access to stored caller data during an emergency communications event. A call server intercepts an emergency call and determines the capabilities of a calling device. Based on calling device capability, the call server uses one or more of the following device independent methods to ascertain a caller identity, independent of a calling device: interactive voice response redirect, HTTP authentication, SIP INFO method, biometric recognition, human interaction, and alternate number dialing. A caller identity is then used to query a subscriber database for a unique caller profile database key (CPDBK) assigned to the caller (unless a CPDBK is already determined). A call server uses a CPDBK to query a caller profile database (CPDB) for relevant caller data. Relevant caller data and the intercepted emergency communications event are then passed to an emergency call processing system, whereby relevant caller data may be used to more effectively address an emergency situation.

Abstract: Device independent access to stored caller data during an emergency communications event. A call server intercepts an emergency call and determines the capabilities of a calling device. Based on calling device capability, the call server uses one or more of the following device independent methods to ascertain a caller identity, independent of a calling device: interactive voice response redirect, HTTP authentication, SIP INFO method, biometric recognition, human interaction, and alternate number dialing. A caller identity is then used to query a subscriber database for a unique caller profile database key (CPDBK) assigned to the caller (unless a CPDBK is already determined). A call server uses a CPDBK to query a caller profile database (CPDB) for relevant caller data. Relevant caller data and the intercepted emergency communications event are then passed to an emergency call processing system, whereby relevant caller data may be used to more effectively address an emergency situation.

Abstract: iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications.

Abstract: 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.

Abstract: iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications.

Abstract: iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications.

Abstract: An internet-protocol (IP) based distributed emergency text message architecture for providing reliable text to 911 services. The distributed emergency text message architecture distributes call routing and media transportation functionalities implemented in a conventional text to 911 solution over the following network entities: an emedia aggregation gateway, an emedia message broker, and an emedia distribution server. An emedia aggregation gateway, emedia message broker, and emedia distribution server each interconnect over an IP network to deliver emergency text messages directly to legacy public safety answering points (PSAPs). Uncoupling emergency services call routing and media transportation functionalities into multiple distributed elements absolves scaling issues associated with the conventional text to 911 solution.

Abstract: An N-dimensional affinity confluencer comprises an affinity table to maintain a plurality of affinities for each of a plurality of wireless devices. A sphere of influence (SPIN) table provides an influence for determination of a confluence between affinities maintained in the affinity table. An affinity confluence determination module determines an affinity confluence between the plurality of wireless devices and an influence parameter associated with the sphere of influence (SPIN) table. An affinity confluence is determined from among a plurality of wireless devices by determining a confluence of at least two predefined affinities from among a plurality of wireless devices. A sphere of influence parameter is applied to the confluence to determine those of the plurality of wireless devices defined by an affinity confluence. The plurality of wireless devices need not be within a common communication network.

Abstract: Device independent access to stored caller data during an emergency communications event. A call server intercepts an emergency call and determines the capabilities of a calling device. Based on calling device capability, the call server uses one or more of the following device independent methods to ascertain a caller identity, independent of a calling device: interactive voice response redirect, HTTP authentication, SIP INFO method, biometric recognition, human interaction, and alternate number dialing. A caller identity is then used to query a subscriber database for a unique caller profile database key (CPDBK) assigned to the caller (unless a CPDBK is already determined). A call server uses a CPDBK to query a caller profile database (CPDB) for relevant caller data. Relevant caller data and the intercepted emergency communications event are then passed to an emergency call processing system, whereby relevant caller data may be used to more effectively address an emergency situation.

Abstract: A method and apparatus to facilitate the secure storage of multimedia content (i.e. video with optional audio) on an internet cloud, and to grant the release of stored multimedia content to pre-authorized users and pre-authorized emergency dispatch personnel, only. A subscriber entity uses a secure user interface component to store a multimedia package containing important/relevant navigation and/or location information on a cloud database. In addition, the subscriber entity specifies whether or not emergency personnel are authorized to access the multimedia package during an emergency event, and whether or not a predefined highly trusted network of users may access the multimedia package following a conventional authorization procedure.

Abstract: A resource selection server that performs crowd-sourced resource selection over a social networking service, absent a central ratings database. A device subscribed to a social networking service implementing the inventive resource selection server, may register as a resource offering a particular skill. Additionally, any device subscribed to a relevant social networking service may transmit a skill request to the inventive resource selection server, to request a best-fit resource be returned for a particular skill of interest. The resource selection server queries a subscriber account database to identify resources on a social networking service, registered to offer a requested skill. The resource selection server additionally prompts subscriber devices within ‘n’ degrees of separation of a requesting device, to submit real-time trust ratings for resources complying with a particular skill request.

Abstract: An N-dimensional affinity confluencer comprises an affinity table to maintain a plurality of affinities for each of a plurality of wireless devices. A sphere of influence (SPIN) table provides an influence for determination of a confluence between affinities maintained in the affinity table. An affinity confluence determination module determines an affinity confluence between the plurality of wireless devices and an influence parameter associated with the sphere of influence (SPIN) table. An affinity confluence is determined from among a plurality of wireless devices by determining a confluence of at least two predefined affinities from among a plurality of wireless devices. A sphere of influence parameter is applied to the confluence to determine those of the plurality of wireless devices defined by an affinity confluence. The plurality of wireless devices need not be within a common communication network.

Abstract: iAlert_Enhanced_Alert_Manager enables a user to register an interest in their current location, as well as persons, places and/or things in which the user holds some regard. The iAlert_Enhanced_Alert_Manager provides notification and clarifying information to user's devices concerning events/happenstance that have occurred or are likely to occur within a proximity of registered persons, places, and/or things. The iAlert_Enhanced_Alert_Manager comprises data structures (e.g. an Affinity Table, a SPIN table, a SPIN-List Table, an Affinity-List Table, and a Keyword-List Table) to manage affinities, Spheres of Influence (SPINs), and relationships therebetween that may positively or negatively induce a person. Timely notification of events/happenstance to a user comprises the computation of iEvent-vectors and iAlert-vectors. An iEvent-vector contains fields pertaining to events/happenstance whereas an iAlert-vector comprises information pertaining to notifications.

Abstract: An Applications Processor (14) including a centralized database system is used in a wireless location system (WLS). The APs 14 may be used to manage resources in the WLS, including signal collection systems (SCSs 10) and TDOA location processors (TLPs 12). Each AP 14 contains a database containing triggers for the WLS. The WLS can be programmed to locate only certain pre-determined types of transmissions. When a transmission of a pre-determined type occurs, then the WLS is triggered to begin location processing. Each AP 14 also contains applications interfaces that permit a variety of applications to securely access the WLS. These applications may access location records in real time or non-real time, create or delete certain types of triggers, or cause the WLS to take other actions. Each AP 14 is also capable of certain post-processing functions.