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

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

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

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

Abstract: ESQK and/or ESRK (ESxK) number pool exhaustion and reuse errors are eliminated by replacing the ESxK identifier with an emergency services pseudo key (ESPK) identifier. A positioning center (MPC/VPC) replaces an ESxK received with a query with a ESPK in a return message. The ESPK is either a unique 10-digit number or unique alpha-numeric identifier that can be used to re-query the source of dynamic ALI data. The ESPK may be generated using, e.g., unique prefixing, suffixing, or randomizing. The ESPK is a non-constrained, unique identifier that preferably remains unique for the call instance over an extended period of time. The ESPK is used for any subsequent ALI request for the call. Each time a positioning center receives a query with ESPK, it is directly associated with, and returns, the updated location for the original emergency call, regardless of whether or not the original ESxK was reallocated to another emergency call.

Abstract: ESQK and/or ESRK (ESxK) number pool exhaustion and reuse errors are eliminated by replacing the ESxK identifier with an emergency services pseudo key (ESPK) identifier. A positioning center (MPC/VPC) replaces an ESxK received with a query with a ESPK in a return message. The ESPK is either a unique 10-digit number or unique alpha-numeric identifier that can be used to re-query the source of dynamic ALI data. The ESPK may be generated using, e.g., unique prefixing, suffixing, or randomizing. The ESPK is a non-constrained, unique identifier that preferably remains unique for the call instance over an extended period of time. The ESPK is used for any subsequent ALI request for the call. Each time a positioning center receives a query with ESPK, it is directly associated with, and returns, the updated location for the original emergency call, regardless of whether or not the original ESxK was reallocated to another emergency call.