# US 2015/0089621 A1 · Secure login for subscriber devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0089621 A1
- Document ID: US20150089621A1
- Status: Published application
- Kind: A1
- Application number: 14/035,301
- Filed: 2013-09-24
- Published: 2015-03-26
- Earliest claimed: 2013-09-24
- Assignees: Cellco Partnership d/b/a Verizon Wireless
- Applicants: Cellco Partnership (d/b/a Verizon Wireless)
- Inventors: Mohammad Raheel Khalid; Ansar Kassim
- Web page: https://patentgrep.com/patent/US20150089621A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network service may receive an authentication request from a subscriber device, the authentication request including a user credential and a device identifier of the subscriber device. The service may validate the authentication request based at least in part on the included user credential, and when the authentication request is validated, provide an authentication reply to the subscriber device indicative of allowance of the subscriber device to access the service, the authentication reply including a hash token keyed to the device identifier of the subscriber device for use in validation of subsequent authentication requests. The service may further generate a second hash token based on the device identifier of a subsequent authentication request; validate a subsequent authentication request according to the hash token and the second hash token; and when the subsequent authentication request is validated, allowing the subscriber device to access the service.

## Claims

### Claim 1

A computing device configured to execute a software program on a processor of the computing device to provide operations comprising:
receiving an authentication request from a subscriber device, the authentication request including a user credential and a device identifier of the subscriber device;
validating the authentication request based at least in part on the included user credential;
when the authentication request is validated, providing an authentication reply to the subscriber device indicative of allowance of the subscriber device to access the network service, the authentication reply including a hash token generated based on the device identifier of the subscriber device for use in validation of subsequent authentication requests.

### Claim 2 (depends on 1)

The computing device of claim 1, further configured to execute the software program to perform operations comprising:
receiving a subsequent authentication request from the subscriber device, the subsequent authentication request including the device identifier of the subscriber device and the hash token;
generating a second hash token based on the device identifier of the subsequent authentication request;
validating the subsequent authentication request according to the hash token and the second hash token; and
when the subsequent authentication request is validated, allowing the subscriber device to access the network service without requiring reentry of the user credential.

### Claim 3 (depends on 1)

The computing device of claim 1, further configured to execute the software program to perform operations comprising generating the hash token further based on a periodically-updated salt value maintained by the network service.

### Claim 4 (depends on 3)

The computing device of claim 3, further configured to execute the software program to perform operations comprising applying an updated salt value to generate hash tokens, thereby invalidating the hash token generated based on the device identifier.

### Claim 5 (depends on 1)

The computing device of claim 1, wherein validating the authentication request includes confirming that at least one of the user credential and the device identifier of the authentication request does not exceed a maximum use count in authentication requests during a constrained period of time.

### Claim 6 (depends on 1)

The computing device of claim 1, wherein the user credential includes a passphrase, and wherein validating the authentication request includes validating the passphrase using user information in a subscriber database.

### Claim 7 (depends on 1)

The computing device of claim 1, wherein the device identifier to be hashed includes a combination of at least one of a mobile device number of the subscriber device, an Internet protocol address of the subscriber device, and an element of information included on a subscriber identity module utilized by the subscriber device, and the user credential includes at least one element of information entered into the subscriber device by a user of the device when creating the authentication request.

### Claim 8

A method, comprising:
receiving an authentication request from a subscriber device by a network service, the authentication request including a user credential and a device identifier of the subscriber device;
validating the authentication request based at least in part on the included user credential;
when the authentication request is validated, providing an authentication reply to the subscriber device indicative of allowance of the subscriber device to access the network service, the authentication reply including a hash token generated based on the device identifier of the subscriber device for use in validation of subsequent authentication requests.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving a subsequent authentication request from the subscriber device, the subsequent authentication request including the device identifier of the subscriber device and the hash token;
generating a second hash token based on the device identifier of the subsequent authentication request;
validating the subsequent authentication request according to the hash token and the second hash token; and
when the subsequent authentication request is validated, allowing the subscriber device to access the network service without requiring reentry of the user credential.

### Claim 10 (depends on 8)

The method of claim 8, further comprising generating the hash token further based on a periodically-updated salt value maintained by the network service.

### Claim 11 (depends on 10)

The method of claim 10, further comprising applying an updated salt value to generate hash tokens, thereby invalidating the hash token generated based on the device identifier.

### Claim 12 (depends on 8)

The method of claim 8, wherein validating the authentication request includes confirming that at least one of the user credential and the device identifier of the authentication request does not exceed a maximum use count in authentication requests during a constrained period of time.

### Claim 13 (depends on 8)

The method of claim 8, wherein the user credential includes a passphrase, and wherein validating the authentication request includes validating the passphrase using user information in a subscriber database.

### Claim 14 (depends on 8)

The method of claim 8, wherein the device identifier to be hashed includes a combination of at least one of a mobile device number of the subscriber device, an Internet protocol address of the subscriber device, and an element of information included on a subscriber identity module utilized by the subscriber device, and the user credential includes at least one element of information entered into the subscriber device by a user of the device when creating the authentication request.

### Claim 15

A non-transitory computer-readable medium tangibly embodying computer-executable instructions of a software program, the software program being executable by a processor of a computing device to provide operations comprising:
receiving an authentication request from a subscriber device, the authentication request including a user credential and a device identifier of the subscriber device;
validating the authentication request based at least in part on the included user credential;
when the authentication request is validated, providing an authentication reply to the subscriber device indicative of allowance of the subscriber device to access the network service, the authentication reply including a hash token generated based on the device identifier of the subscriber device for use in validation of subsequent authentication requests.

### Claim 16 (depends on 15)

The computer-readable medium of claim 15, further executable by the computing device to perform operations comprising:
receiving a subsequent authentication request from the subscriber device, the subsequent authentication request including the device identifier of the subscriber device and the hash token;
generating a second hash token based on the device identifier of the subsequent authentication request;
validating the subsequent authentication request according to the hash token and the second hash token; and
when the subsequent authentication request is validated, allowing the subscriber device to access the network service without requiring reentry of the user credential.

### Claim 17 (depends on 15)

The computer-readable medium of claim 15, further executable by the computing device to perform operations comprising generating the hash token further based on a periodically-updated salt value maintained by the network service.

### Claim 18 (depends on 17)

The computer-readable medium of claim 17, further executable by the computing device to perform operations comprising applying a new salt value to generate the hash token, thereby invalidating the hash token generated based on the device identifier.

### Claim 19 (depends on 15)

The computer-readable medium of claim 15, wherein validating the authentication request includes confirming that at least one of the user credential and the device identifier of the authentication request does not exceed a maximum use count in authentication requests during a constrained period of time.

### Claim 20 (depends on 15)

The computer-readable medium of claim 15, wherein the user credential includes a passphrase, and wherein validating the authentication request includes validating the passphrase using user information in a subscriber database.

### Claim 21 (depends on 15)

The computer-readable medium of claim 15, wherein the device identifier to be hashed includes a combination of at least one of a mobile device number of the subscriber device, an Internet protocol address of the subscriber device, and an element of information included on a subscriber identity module utilized by the subscriber device, and the user credential includes at least one element of information entered into the subscriber device by a user of the device when creating the authentication request.
