Verizon Patent and Licensing Inc.

Cellco Partnership

Brian Libonate

Paul H Prehn

Gaurav Gupta

Raymond C Counterman

Guanqun Bao

Stephen D Morrison

Thomas W Haynes

Sethumadhav Bendi

Praveen Atreya

Amol Tuli

Siddhartha Kumar Arya

Chandrashekhar Yeleswarapu

A user device may request access to a service provided by an application server. The application server may request that an identity server authenticate the user device. The identity server may have a network authentication system assist with the authentication of the user device. Once authenticated by the network authentication system, the application server may be informed and may grant the user device access to the requested service. Additionally, the identity server may help determine whether the user device is a security threat by comparing user information from the network authentication system with user information from the application server. Additionally, the network authentication system may provide the application server with user information to enable the application server to automatically register the user device for a particular service.

Network-based authentication and security services

A system may receive a content request associated with a user device. The content request may include information that identifies a subscriber associated with the user device and information that identifies a content provider associated with the content request. The system may determine a unique identification header (UIDH), associated with the subscriber, based on the content request. The system may determine randomized information associated with encrypting the UIDH. The system may encrypt the UIDH to create a transactional identifier. The UIDH may be encrypted based on the randomized information and a shared key. The system may insert the transactional identifier and the randomized information in the content request to create a modified content request. The system may provide the modified content request including the transactional identifier and the randomized information.

Encrypting a unique identification header to create different transactional identifiers

A device may receive an identifier for a subscriber of a first network. The subscriber may be associated with the device. The device may store the identifier and receive a request for content. The device may generate a modified request by adding the identifier to the request. The device may send the modified request using a network communication. The network communication may communicate via a second network without using the first network, and the first network may be different than the second network. The device may receive the content and targeted content based on the modified request. The targeted content may be targeted to the subscriber based on the identifier.

Adding a unique identification header to non-operator network communication

A multimedia messaging service (MMS) center (MMSC) receives an MMS message associated with forwarding multimedia content, associated with a source device, to a recipient device. The multimedia content is tagged with tagging data that is generated based on a numerical key. The MMSC parses the modified MMS message to determine the source device and the tagging data. MMSC uses the tagging data to determine the sending device using the tagging data. For example, the MMSC may access an identifier for the sending device, as stored by a subscriber profile controller, using the tagging data and/or a Lightweight Directory Access Protocol (LDAP) interface. The MMSC determines whether the source device associated with the MMS message corresponds to the sending device (e.g., whether the MMS message correctly identifies the sending device), and the MMSC discards the MMS message when the source device and the sending device differ.

Multimedia messaging service (MMS) originator authentication

A system is configured to receive, from a user device, a request for content; obtain, based on receiving the request, an identifier for a subscriber associated with the system and a key; encode the identifier and the key to create a unique identifier; store the unique identifier in the request to create a modified request; provide the modified request to a content provider identified by the request; receive, from the content provider, the content and targeted content, the targeted content being associated with the unique identifier and conforming to an attribute of the subscriber; and provide, to the user device, the content and the targeted content.

Obtaining targeted services using a unique identification header (UIDH)

A data source may be configured to provide usage data including subscriber identifiers and associated information indicative of subscriber device locations and usage. A data warehouse server may be configured to perform operations including: decrypting subscriber identifiers included in usage data received from the data source using a two-way rolling key groups algorithm; re-encrypting the subscriber identifiers decrypted from the usage data to create secure encrypted identifiers using a one-way secured encryption algorithm; and correlating the subscriber identifiers in the decrypted usage data with the corresponding re-encrypted identifiers.

Enhancing data security using re-encryption

A user device is configured to receive a request to obtain a service, an application, or content from a provider; obtain, based on receiving the request, a token that may correspond to a user of the user device and may obfuscate an identity of the user to the provider; modify the request to include the token and to form a modified request; provide the modified request to the provider; receive, based on providing the modified request, information regarding the service, the application, or the content from the provider; and present the information for display on a display screen.

Growing community of inventors

Walnut Creek, CA, United States of America

Brian Libonate