# US 2008/0306875 A1 · Method and system for secure network connection

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

- Number: US 2008/0306875 A1
- Document ID: US20080306875A1
- Status: Published application
- Kind: A1
- Application number: 11/761,156
- Filed: 2007-06-11
- Published: 2008-12-11
- Earliest claimed: 2007-06-11
- Assignees: eBay Inc.
- Inventors: Upendra Sharadchandra Mardikar
- Web page: https://patentgrep.com/patent/US20080306875A1

## CPC

- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- G06Q 20/3829: {involving key management}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/0838: {Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these (network architectures or network communication protocols for key exchange in a packet data network H04L63/061)}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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

Methods and systems for secure payment via a network are disclosed. In an example embodiment, a system includes components to receive a globally unique identifier (GUID) and a client-hello message from a client, generate a tag and sending the tag and a server hello message to the client, receive the tag, a client-key-exchange message, a change-c-spec message, an encrypted-finished message, and secured payload from the client, and send an encrypted-finished message and secured response payload to the client.

## Claims

### Claim 1

A server system comprising:
a first component to receive a globally unique identifier (GUID) and a client-hello message from a client;
a second component to generate a tag and send the tag and a server hello message to the client;
a third component to receive the tag, a client-key-exchange message, a change-c-spec message, an encrypted-finished message, and secured payload from the client; and
a fourth component to send an encrypted-finished message and secured response payload to the client.

### Claim 2 (depends on 1)

The system of claim 1 further including a fifth component to generate a session key.

### Claim 3

A client system comprising:
a first component to send a globally unique identifier (GUID) and a client-hello message to a server;
a second component to receive a tag and a server hello message from the server;
a third component to send the tag, a client-key-exchange message, a change-c-spec message, an encrypted-finished message, and secured payload to the server; and
a fourth component to receive an encrypted-finished message and secured response payload from the server.

### Claim 4 (depends on 3)

The system of claim 3 further including a fifth component to generate a session key.

### Claim 5

A method comprising:
receiving a globally unique identifier (GUID) and a client-hello message from a client;
generating a tag and sending the tag and a server hello message to the client;
receiving the tag, a client-key-exchange message, a change-c-spec message, an encrypted-finished message, and secured payload from the client; and
sending an encrypted-finished message and secured response payload to the client.

### Claim 6 (depends on 5)

The method of claim 5 further including generating a session key.

### Claim 7

A machine-readable medium comprising instructions, which when executed by a machine, cause the machine to:
receive a globally unique identifier (GUID) and a client-hello message from a client;
generate a tag and sending the tag and a server hello message to the client;
receive the tag, a client-key-exchange message, a change-c-spec message, an encrypted-finished message, and secured payload from the client; and
send an encrypted-finished message and secured response payload to the client.

### Claim 8 (depends on 7)

The machine-readable medium of claim 7 further including instructions operable to generate a session key.
