# US 2003/0070068 A1 · Method and system for providing client privacy when requesting content from a public server

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

- Number: US 2003/0070068 A1
- Document ID: US20030070068A1
- Status: Published application
- Kind: A1
- Application number: 09/972,523
- Filed: 2001-10-05
- Published: 2003-04-10
- Earliest claimed: 2001-10-05
- Assignees: General Instrument Corporation
- Inventors: Alexander Medvinsky
- Web page: https://patentgrep.com/patent/US20030070068A1

## CPC

- H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks}
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- 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 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 2209/60: Digital content management, e.g. content distribution
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Method and system for providing client privacy on the Internet when the client requests content from a public application server. The method is well-suited to key management protocols that utilize the concept of tickets. The client name or identity is encrypted in all key management messages where the client is requesting a ticket for a specific application server. The key management messages are between the client and a key distribution center (KDC) and between the client and the specific application server. The KDC does not provide the client name or identity in the clear in such messages. This prevents the client's identity from being linked with the content provided by the specific application server, which results in improved user privacy.

## Claims

### Claim 1

A method of providing client privacy when requesting content from an application server, comprising the steps of:
receiving a request for a ticket granting ticket (TGT ticket) from a client;
generating the TGT ticket with an identity of the client encrypted therein;
sending the TGT ticket to the client;
receiving a request for a service ticket (ST ticket) for the application server from the client that includes the TGT ticket and that does not provide the identity of the client in the clear;
generating the ST ticket with the identity of the client encrypted therein; and
sending the ST ticket to the client without providing the identity of the client in the clear.

### Claim 2 (depends on 1)

A method in accordance with claim 1, wherein the step of receiving a request for a TGT ticket comprises the step of receiving a request for a TGT ticket with an authentication server.

### Claim 3 (depends on 1)

A method in accordance with claim 1, wherein the step of generating the TGT ticket comprises the step of generating the TGT ticket with an authentication server.

### Claim 4 (depends on 1)

A method in accordance with claim 1, wherein the step of sending the TGT ticket to the client comprises the step of sending the TGT ticket to the client as part of an authentication server reply message.

### Claim 5 (depends on 1)

A method in accordance with claim 1, wherein the step of receiving a request for an ST ticket for the application server comprises the step of receiving a request for an ST ticket for the application server with a ticket granting server.

### Claim 6 (depends on 1)

A method in accordance with claim 1, wherein the request for an ST ticket for the application server specifies the application server's identity.

### Claim 7 (depends on 1)

A method in accordance with claim 1, wherein the step of generating the ST ticket comprises the step of generating the ST ticket with a ticket granting server.

### Claim 8 (depends on 1)

A method in accordance with claim 1, wherein the step of sending the ST ticket to the client comprises the step of sending the ST ticket to the client as part of a ticket granting server reply message.

### Claim 9 (depends on 1)

A method in accordance with claim 1, wherein the step of sending the TGT ticket to the client comprises the step of sending the TGT ticket to the client without providing the identity of the client in the clear.

### Claim 10 (depends on 1)

A method in accordance with claim 1, wherein the step of sending the TGT ticket to the client comprises the step of sending the TGT ticket to the client along with a copy of the client's own authorization data in read-only form.

### Claim 11

A system for providing client privacy when requesting content from an application server, comprising:
an authentication server configured to receive a request for a ticket granting ticket (TGT ticket) from a client, generate the TGT ticket with an identity of the client encrypted therein, and send the TGT ticket to the client; and
a ticket granting server configured to receive a request for a service ticket (ST ticket) for the application server from the client that includes the TGT ticket and that does not provide the identity of the client in the clear, generate the ST ticket with the identity of the client encrypted therein, and send the ST ticket to the client without providing the identity of the client in the clear.

### Claim 12 (depends on 11)

A system in accordance with claim 11, wherein the authentication server and the ticket granting server form at least part of a key distribution center (KDC).

### Claim 13 (depends on 11)

A system in accordance with claim 11, wherein the authentication server is further configured to send the TGT ticket to the client as part of an authentication server reply message.

### Claim 14 (depends on 11)

A system in accordance with claim 11, wherein the authentication server is further configured to send the TGT ticket to the client without providing the identity of the client in the clear.

### Claim 15 (depends on 11)

A system in accordance with claim 11, wherein the ticket granting server is further configured to send the ST ticket to the client as part of a ticket granting server reply message.
