Abstract:
A system may be configured to receive an indication that a call has been placed (e.g., to a call center), and may provide a customized visual interface. The customized visual interface may include information that is potentially relevant to a user who has placed the call, and may be based on, for example, a user profile or history information, a purchase history of goods or services offered by an entity associated with the called party. The customized visual interface may allow the user to more quickly satisfy the purposes of his or her call than through traditional audio or touchtone menus.
Abstract:
Information, called context information, relating to a current state of a user may be aggregated. In one implementation, the context information may include information that is automatically generated by communication devices of the user and information, submitted by the user, that relates to the user's state. The context information may be used to provide personalized advertisements for the user.
Abstract:
A device may receive a connection request including a digital certificate from an endpoint for establishing a secure connection for a communication, the digital certificate including a digital certificate chain identifying one or more certificate authorities associated with the digital certificate. The device may determine whether the digital certificate is valid based on the digital certificate chain identifying one or more certificate authorities trusted by the device. The device may determine whether the connection request includes a valid token. The device may generate a token based on the digital certificate being valid and an absence of a valid token included in the connection request. The device may associate the token with the digital certificate. The device may distribute the token to the endpoint. The device may establish the secure connection with the endpoint using the token associated with the digital certificate.
Abstract:
An approach for enabling multi-factor biometric authentication of a user based on different data capture modalities of a mobile device is described. A biometric enabler receives a request for authentication of a user via a network at a mobile device of the user. The biometric authentication further initiates a capture of media associated with the user at the mobile device based on the request, wherein the capture is based on a capture condition. The biometric enabler also determines, in response to the request, whether the media is associated with different types of biometric information of the user as maintained in association with a resource that requires authentication of the user.
Abstract:
A system may be configured to request, from a user device, consent for an application server to output one or more messages to the user device. When requesting the consent, the system may output a consent message associated with the application server. The system may receive, from the user device, an indication of consent, the indication being sent by the user device based on the consent message; and enforce, by the consent gateway device, the consent indicated by the user device. When enforcing the consent, the system may allow or disallow application traffic, from the application server, based on the indication of consent. The application traffic may be associated with the user device.
Abstract:
A method includes identifying a data volume allocation associated with a user account from a shared data volume allocation, identifying previous data consumption corresponding to the data volume allocation by the user account, and identifying a current data usage rate associated with the user account. The method also includes identifying a data usage threshold associated with the user account. A projected data usage is determined based on the current data usage rate and the previous data consumption. The method includes determining whether the projected data usage exceeds the data usage threshold, and, if the projected data usage exceeds the data usage threshold, sending a notification indicating that the data usage is projected to exceed the data usage threshold to at least one account associated with the shared data plan. The method further includes performing an action to limit data consumption below the data usage threshold.
Abstract:
Techniques described herein may provide for affiliation and disaffiliation of devices, such as office communication devices, associated with a user. The affiliation/disaffiliation may be performed using a mobile device (e.g., a smart phone). In one implementation, a method may include receiving a request to affiliate a user with one or more office devices; and receiving context data, from a mobile device, relating to a current context of the mobile device. The method may further include determining, based on the context data, to authorize the affiliation of the user with the one or more office devices; and provisioning, based on the determination to authorize the affiliation, the one or more office devices to customize the one or more office devices for the user.
Abstract:
Techniques described herein may provide for affiliation and disaffiliation of devices, such as office communication devices, associated with a user. The affiliation/disaffiliation may be performed using a mobile device (e.g., a smart phone). In one implementation, a method may include receiving a request to affiliate a user with one or more office devices; and receiving context data, from a mobile device, relating to a current context of the mobile device. The method may further include determining, based on the context data, to authorize the affiliation of the user with the one or more office devices; and provisioning, based on the determination to authorize the affiliation, the one or more office devices to customize the one or more office devices for the user.
Abstract:
A method may include performing secure device configuration, via a configuration service manager device, for a SIP user device. The method includes monitoring, via the configuration service manager device, the SIP user device for device authentication problems, configuration file download problems, device registration problems and device third party registration problems. The method may also include detecting the device authentication problems, and logging and reporting the detected device authentication problems. The method may also include automated testing of the device and logging and reporting of detected device test problems. The method further includes resolving the detected device authentication, registration or testing problems.
Abstract:
An approach for multi-sensor multi-factor identity verification. An identity verification platform determines biometric data associated with a user from one or more sources. The one or more sources are associated with one or more respective network sessions. The platform generates one or more respective trust scores for the one or more sources, the one or more respective network sessions, or a combination thereof based on one or more contextual parameters associated with the user, the one or more sources, the one or more respective network sessions, or a combination thereof. Then the platform verifies an identity of the user based on the biometric data and the one or more respective trust scores.