# US 2021/0067341 A1 · Method and apparatus for secure token generation

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

- Number: US 2021/0067341 A1
- Document ID: US20210067341A1
- Status: Published application
- Kind: A1
- Application number: 16/557,508
- Filed: 2019-08-30
- Published: 2021-03-04
- Earliest claimed: 2019-08-30
- Assignees: Comcast Cable Communications, LLC
- Applicants: Comcast Cable Communications, LLC
- Inventors: Asad HAQUE; Ahmad AL TAMIMI; Liesheng LONG; Thomas HUGHES, III
- Web page: https://patentgrep.com/patent/US20210067341A1

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/3247: {involving digital signatures}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 2463/062: applying encryption of the keys
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and apparatuses are described herein for improved communications between a service and end devices via a gateway. A token may be in a signed encrypted state when sent to untrusted devices and may be signed, but not encrypted, when used by trusted devices. Untrusted devices may receive the encrypted token and may use it to access services. An untrusted device may send the received encrypted token to the gateway, which may then send the token to its issuer so that the token issuer may decrypt the data payload. The token may then be sent back to the gateway, which may then read the decrypted data and verify whether the untrusted device is permitted to access the requested service. The gateway may then send, within the trusted domain, the request and token to the service provider so that the untrusted device can obtain access to the requested service.

## Claims

### Claim 1

A method comprising:
receiving, from a first computing device communicating in an untrusted system, information comprising:
a request for a service; and
a token comprising a signature and encrypted data;
validating, based on the signature, the token;
determining, based on the validated token, a second computing device that generated the token and that communicates in a trusted system;
sending, to the second computing device, the validated token;
receiving, from the second computing device, the validated token, wherein the encrypted data has been decrypted by the second computing device;
determining, based on the decrypted data, whether the first computing device has permission to access the service; and
sending, based on the determining whether the first computing device has permission to access the service and to a third computing device communicating in the trusted system, the request for the service.

### Claim 2 (depends on 1)

The method of claim 1, wherein the second computing device is associated with a service provider providing network access and security to the first computing device and the third computing device.

### Claim 3 (depends on 1)

The method of claim 1, wherein third computing device is associated with a third party service or cloud platform.

### Claim 4 (depends on 1)

The method of claim 1, wherein the encrypted data was encrypted using a first key, and wherein the first key is encrypted using a second key to generate an encrypted first key.

### Claim 5 (depends on 4)

The method of claim 4, wherein the token further comprises a header comprising the encrypted first key.

### Claim 6 (depends on 4)

The method of claim 4, wherein the first key is a random content encryption key (CEK).

### Claim 7 (depends on 4)

The method of claim 4, wherein the encrypted first key comprises an encrypted content encryption key (eCEK).

### Claim 8 (depends on 4)

The method of claim 4, wherein the second key is a public key.

### Claim 9 (depends on 4)

The method of claim 4, wherein the token further comprises a Uniform Resource Locator (URL) providing a link to a public key certificate associated with the signature.

### Claim 10 (depends on 1)

The method of claim 1, wherein the encrypted data comprises information indicating at least one of:
permissions of the first computing device,
account information of the first computing device, or
capabilities of the first computing device.

### Claim 11

A device, comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the device to:
receive, from a first computing device communicating in an untrusted system, information comprising:
a request for a service; and
a token comprising a signature and encrypted data;
validate, based on the signature, the token;
determine, based on the validated token, a second computing device that generated the token and that communicates in a trusted system;
send, to the second computing device, the validated token;
receive, from the second computing device, the validated token, wherein the encrypted data has been decrypted by the second computing device;
determine, based on the decrypted data, whether the first computing device has permission to access the service; and
send, based on the determining whether the first computing device has permission to access the service and to a third computing device communicating in the trusted system, the request for the service.

### Claim 12 (depends on 11)

The device of claim 11, wherein the second computing device is associated with a service provider providing network access and security to the first computing device and the third computing device.

### Claim 13 (depends on 11)

The device of claim 11, wherein third computing device is associated with a third party service or cloud platform.

### Claim 14 (depends on 11)

The device of claim 11, wherein the encrypted data was encrypted using a first key, and wherein the first key is encrypted using a second key to generate an encrypted first key, wherein the token further comprises a header comprising the encrypted first key.

### Claim 15 (depends on 14)

The device of claim 14, wherein the token further comprises a Uniform Resource Locator (URL) providing a link to a public key certificate associated with the signature.

### Claim 16 (depends on 11)

The device of claim 11, wherein the encrypted data comprises information indicating at least one of:
permissions of the first computing device,
account information of the first computing device, or
capabilities of the first computing device.

### Claim 17

A method comprising:
receiving, from a computing device over a trust boundary, a request for a token;
generating a first key, wherein the first key comprises a random content encryption key (CEK);
encrypting, using the first key, data comprising information associated with the computing device;
encrypting, using a second key, the first key to generate an encrypted first key;
generating a token comprising the encrypted first key, the encrypted data, and a signature signed using a third key; and
sending, to the computing device over the trust boundary, the generated token.

### Claim 18 (depends on 17)

The method of claim 17, wherein the token further comprises a Uniform Resource Locator (URL) providing a link to a public key certificate associated with the signature.

### Claim 19 (depends on 17)

The method of claim 17, wherein the information indicates at least one of:
permissions of the first computing device,
account information of the first computing device, or
capabilities of the first computing device.

### Claim 20 (depends on 17)

The method of claim 17, wherein the computing device communicates in an untrusted system.
