Abstract:
A server device may receive a message from a first user device, the message being destined for a second user device; determine a call session control function (CSCF) server device associated with the second user device; and output, based on the determining, the message to the CSCF server device.
Abstract:
A first server device may receive a group identifier, a first list including one or more first user device identifiers, and an instruction to archive messages associated with the one or more first user device identifiers; receive a second list including one or more second user device identifiers that are associated with the group identifier; and generate a third list including one or more third user device identifiers that are in the first list and the second list. The first server device may receive a message associated with a user device identifier; determine that the message is to be archived when the user device identifier associated with the message is included in the third list; and provide the message to a second server device based on the determination that the message is to be archived.
Abstract:
A server device may receive a message from a first user device, the message being destined for a second user device; determine a call session control function (CSCF) server device associated with the second user device; and output, based on the determining, the message to the CSCF server device.
Abstract:
A server device may receive information identifying property features relating to for-sale properties; identify a plurality of properties having one or more of the property features; identify particular properties, of the plurality of properties, having the one or more of the property features; receive location information for the particular properties; and generate, based on the location information, a trip plan identifying the particular properties. The trip plan may identify a sequence in which the particular properties should be visited and a route that should be taken when traveling between the particular properties. The server device may store or output the trip plan.
Abstract:
A user may have real-time control over whether accessing a network service account implements two-factor authentication. When a username and password is provided to log into the network service account, a determination may be made about whether the login attempt is a potential security threat. When the login attempt does not appear to be a threat, the login attempt may be processed based on the username and password. When the login attempt is a potential security threat, the actual user corresponding to the network service account may be notified and asked to confirm whether the login attempt is a security threat. When the user confirms that the login attempt is not a security threat, the user may be logged in based on the username and password. When the user confirms that the login attempt is a security threat, two-factor authentication may be implemented for accessing the network service account.
Abstract:
Credit card fraud prevention techniques are disclosed in which the authorization of a payment card may be performed using information obtained from a mobile device (e.g., a smart phone) associated with a user who initiates a point-of-sale payment card transaction. In one implementation, a device may receive a request for authorization of a payment associated with a payment card; and obtain location information relating to a location of a mobile device associated with a user of the payment card. The device may determine, based at least on a location of the point-of-sale terminal and the location of the mobile device, whether to authorize the request for authorization of the payment.
Abstract:
A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.
Abstract:
A user may have real-time control over whether accessing a network service account implements two-factor authentication. When a username and password is provided to log into the network service account, a determination may be made about whether the login attempt is a potential security threat. When the login attempt does not appear to be a threat, the login attempt may be processed based on the username and password. When the login attempt is a potential security threat, the actual user corresponding to the network service account may be notified and asked to confirm whether the login attempt is a security threat. When the user confirms that the login attempt is not a security threat, the user may be logged in based on the username and password. When the user confirms that the login attempt is a security threat, two-factor authentication may be implemented for accessing the network service account.
Abstract:
A system may use optical character recognition (“OCR”) techniques to identify license plates or other textual information associated with vehicles. Based on this OCR information, the system may determine additional information, such as users associated with the vehicles. The system may further obtain other information, such as history information associated with the vehicles and/or the users (e.g., via an “opt-in” data collection service). Ad content may be selected based on trends associated with the users and/or vehicles, and may be presented via “smart” billboards (e.g., billboards that may dynamically display different content).
Abstract:
Credit card fraud prevention techniques are disclosed in which the authorization of a payment card may be performed using information obtained from a mobile device (e.g., a smart phone) associated with a user who initiates a point-of-sale payment card transaction. In one implementation, a device may receive a request for authorization of a payment associated with a payment card; and obtain location information relating to a location of a mobile device associated with a user of the payment card. The device may determine, based at least on a location of the point-of-sale terminal and the location of the mobile device, whether to authorize the request for authorization of the payment.