Abstract: Systems and methods for providing called devices with sets of context data associated with communication sessions are disclosed. In one implementation, a method for generating context data associated with a communications session may include receiving, from a calling device at a first subsystem, a request to establish a communications session. The request may include a first identifier associated with the calling device. The method may further include receiving, at a second subsystem, activities data associated with the calling device that transmitted the request to establish the communications session. The activities data may include a second identifier associated with the calling device and may be indicative of device activities of the calling device.

Abstract: A method for disabling a device associated with a virtual identity may include receiving, from the device, a request to use the virtual identity, where the request that may include a passcode guess and a device identifier. The method may also include determining that the passcode guess does not authorize use of the virtual identity and incrementing a number of incorrect passcode guesses received within a time interval. The method may additionally include determining that the number of incorrect passcode guesses received within the time interval is greater than or equal to a threshold. The method may further include storing an indication that subsequent requests associated with the device identifier should not authorize use of the virtual identity.

Abstract: A contact information system provides an independent network authority for providing contact information in connection with incoming calls or messages. The contact information system utilizes a database of communication identifiers to provide contact information for end user devices that receive incoming communications which specify communication identifiers that are stored in the database.

Abstract: Examples described herein relate to a data aggregation system for enabling query operations on restricted data that originates from multiple independent sources.

Abstract: Systems and methods are described that enable trusted communications between two entities. In one implementation, a controller of a vehicle may include one or more processors configured to receive data and a controller signature from a second controller of the vehicle. The controller signature may be generated based on at least a first portion of the data. The one or more processors may be further configured to transmit the data and the controller signature to a gateway of the vehicle and receive a gateway signature from the gateway. The gateway signature may be generated based on at least a second portion of the data and transmitted to the controller after the gateway verified the controller signature. In addition, the one or more processors may be configured to verify the gateway signature and process the data.

Abstract: A method for disabling a device associated with a virtual identity may include receiving, from the device, a request to use the virtual identity, where the request that may include a passcode guess and a device identifier. The method may also include determining that the passcode guess does not authorize use of the virtual identity and incrementing a number of incorrect passcode guesses received within a time interval. The method may additionally include determining that the number of incorrect passcode guesses received within the time interval is greater than or equal to a threshold. The method may further include storing an indication that subsequent requests associated with the device identifier should not authorize use of the virtual identity.

Abstract: Systems and methods are described that enable trusted communications between two entities. In one implementation, a controller of a vehicle may include one or more processors configured to receive data and a controller signature from a second controller of the vehicle. The controller signature may be generated based on at least a first portion of the data. The one or more processors may be further configured to transmit the data and the controller signature to a gateway of the vehicle and receive a gateway signature from the gateway. The gateway signature may be generated based on at least a second portion of the data and transmitted to the controller after the gateway verified the controller signature. In addition, the one or more processors may be configured to verify the gateway signature and process the data.

Abstract: Systems and methods for locking databases during database operation, such a logical mechanisms for locking a local number portability (LNP) database associated with the Number Portability Administration Center (NPAC), are described. For example, the systems and methods may utilize various logical constructs, such as parameters that identify items or records within a database (e.g., object type and value information). and lock records that include such paramters.

Abstract: Computer systems and methods for verifying a route taken by a communication are disclosed. In one implementation, a device for verifying a route taken by a communication may include one or more processors configured to obtain a communication transmitted by a source entity. The communication may include data and digital signatures, and each of the digital signatures may be generated based on at least the data. Further, the digital signatures may include a digital signature associated with the source entity, and a set of digital signatures associated with at least a subset of intermediate entities on a route taken by the communication. The one or more processors may be further configured to verify the digital signatures included in the communication, verify whether the entities associated with the digital signatures form an expected route for the communication, and process the data.

Abstract: Disclosed herein are systems and methods for providing mobile call authentication. For instance, a token indicative of a call request can be received from a calling party. The token can include a called party number and a time of the request. A subscriber database can be accessed to determine identifying information associated with the calling party based at least in part on the token. The token can be authenticated based at least in part on the identifying information and using one or more predefined authentication protocols. The token can be stored in a call session registry storing data indicative of a plurality of active telephone call events. A verification request for the call request can be received from the called party. The call request can be verified based at least in part on the token. The called party can be notified that the call request has been verified.

Abstract: A method and system for predicting the geographic location of a network entity are described. Examples include predicting the geographic location of a network entity by directing the network entity to transmit one or more data packets to a number of predetermined network identifiers, such as IP addresses, where data corresponding to each of the network identifiers is part of a geographic location prediction model. In examples, a dataset that represents transit times for the data packets transmitted from the network entity to the hosts identified by the IP addresses is determined, and a geographic location for the network entity is predicted by applying the geographic location prediction model to the dataset.

Abstract: A contact information system provides an independent network authority for providing contact information in connection with incoming calls or messages. The contact information system utilizes a database of communication identifiers to provide contact information for end user devices that receive incoming communications which specify communication identifiers that are stored in the database.

Abstract: Systems and methods for locking databases during database operations, such as logical mechanisms for locking a local number portability (LNP) database associated with the Number Portability Administration Center (NPAC), are described. For example, the systems and methods may utilize various logical constructs, such as parameters that identify items or records within a database (e.g., object type and value information), and lock records that include such parameters.

Abstract: Systems and methods are described that enable trusted communications between two entities. In one implementation, a controller of a vehicle may include one or more processors configured to receive data and a controller signature from a second controller of the vehicle. The controller signature may be generated based on at least a first portion of the data. The one or more processors may be further configured to transmit the data and the controller signature to a gateway of the vehicle and receive a gateway signature from the gateway. The gateway signature may be generated based on at least a second portion of the data and transmitted to the controller after the gateway verified the controller signature. In addition, the one or more processors may be configured to verify the gateway signature and process the data.

Abstract: System and methods for providing calling party information are disclosed. In one implementation, a server for providing calling party information includes one or more processors configured to receive a query for calling party information from a carrier. The query includes an identifier associated with the calling party. The processors are further configured to determine a score based on one or more previously obtained queries, generate the calling party information based on the score, and transmit the calling party information to the carrier. The carrier transmits the calling party information to a device associated with the called party as a Caller ID Name (CNAM).

Abstract: Systems and methods are described that mitigates and/or prevents distributed denial-of-service (DDOS) attacks. In one implementation, a gateway include one or more processors configured to obtain network data from one or more entities associated with the gateway, provide the network data to a server, and obtain a set of entity identifiers from the server. The set of entity identifiers may be generated based on at least the network data. The one or more processors may be further configured to filter communications based on the set of entity identifiers.

Abstract: Disclosed herein are systems and methods for providing mobile call authentication. For instance, a token indicative of a call request can be received from a calling party. The token can include a called party number and a time of the request. A subscriber database can be accessed to determine identifying information associated with the calling party based at least in part on the token. The token can be authenticated based at least in part on the identifying information and using one or more predefined authentication protocols. The token can be stored in a call session registry storing data indicative of a plurality of active telephone call events. A verification request for the call request can be received from the called party. The call request can be verified based at least in part on the token. The called party can be notified that the call request has been verified.

Abstract: A method and system for predicting the geographic location of a network entity are described. Examples include predicting the geographic location of a network entity by directing the network entity to transmit one or more data packets to a number of predetermined network identifiers, such as IP addresses, where data corresponding to each of the network identifiers is part of a geographic location prediction model. In examples, a dataset that represents transit times for the data packets transmitted from the network entity to the hosts identified by the IP addresses is determined, and a geographic location for the network entity is predicted by applying the geographic location prediction model to the dataset.

Abstract: System and methods for providing calling party information are disclosed. In one implementation, a server for providing calling party information includes one or more processors configured to receive a query for calling party information from a carrier. The query includes an identifier associated with the calling party. The processors are further configured to determine a score based on one or more previously obtained queries, generate the calling party information based on the score, and transmit the calling party information to the carrier. The carrier transmits the calling party information to a device associated with the called party as a Caller ID Name (CNAM).

Abstract: An approach is described for facilitating an outbound call from a calling party and a called party by displaying specific information on the communication device of the called party. The displayed specific information is based on a communication characteristic of the called party, where the communication characteristic includes a language characteristic of the called party. Based on language characteristic of the called party, customized display content is provided to the communications device of the called party, on or prior to the called party being alerted to the requested communication. The customized display content improves the answer rate and the conversion rate of the outbound call.