# US 2020/0288316 A1 · Method and system for mpquic over qsocks in wireless network

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

- Number: US 2020/0288316 A1
- Document ID: US20200288316A1
- Status: Published application
- Kind: A1
- Application number: 16/810,261
- Filed: 2020-03-05
- Published: 2020-09-10
- Earliest claimed: 2019-03-06
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Madhan Raj KANAGARATHINAM; Sujith Rengan JAYASEELAN; Gaurav SINHA; Bhagwan Dass SWAMI; Gunjan Kumar CHOUDHARY; Karthikeyan ARUNACHALAM
- Web page: https://patentgrep.com/patent/US20200288316A1

## CPC

- H04W 12/06: Authentication
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 69/162: {involving adaptations of sockets based mechanisms (secure socket layer H04L63/168)}
- H04L 69/164: Adaptation or special uses of UDP protocol
- H04W 80/06: Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless {(transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16)}
- H04L 63/166: {at the transport layer}
- H04L 69/163: In-band adaptation of TCP data exchange; In-band control procedures
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over Quick SOCKS (QSOCKS) in a wireless network is provided. The method includes receiving, by a QSOCKS server, a Client Hello (CHLO) message from a QSOCKS client device using a QSOCKS method tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (AUTH) procedures, selecting, by the QSOCKS server, a candidate client-supported SOCKS AUTH procedure from the plurality of client-supported SOCKS AUTH procedures, and transmitting, by the QSOCKS server, a reject packet using the QSKM tag to the QSOCKS client device, wherein the reject packet includes information indicating the selected candidate client-supported SOCKS AUTH procedure.

## Claims

### Claim 1

A method for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over Quick SOCKS (QSOCKS) in a wireless network, the method comprising:
receiving, by a QSOCKS server, a Client Hello (CHLO) message from a QSOCKS client device using a QSOCKS method (QSKM) tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (AUTH) procedures;
selecting, by the QSOCKS server, a candidate client-supported SOCKS AUTH procedure from the plurality of client-supported SOCKS AUTH procedures; and
transmitting, by the QSOCKS server, a reject packet using the QSKM tag to the QSOCKS client device,
wherein the reject packet includes information indicating the selected candidate client-supported SOCKS AUTH procedure.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, by the QSOCKS server, the CHLO message from the QSOCKS client device using a QSOCKS authentication (QSKA) tag, wherein the CHLO message comprises client credentials selected based on the selected SOCKS AUTH procedure, and wherein the QSKA tag contains a SOCKS AUTH sub-negotiation;
verifying, by the QSOCKS server, the credentials of the QSOCKS client device; and
transmitting, by the QSOCKS server, a QUIC Server Hello (SHLO) message using the QSKA tag in response to successful verification of the credentials.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
receiving, by the QSOCKS server, a QSOCKS request from the QSOCKS client device, wherein the QSOCKS request comprises a message format;
evaluating, by the QSOCKS server, the QSOCKS request based on source and destination addresses, and returning one or more reply messages;
initiating, by the QSOCKS server, a SOCKS session; and
transmitting, by the QSOCKS server, a QSOCKS response to the QSOCKS client device,
wherein a block of the QSOCKS response indicates a field corresponding to a type of the QSOCKS request, and
wherein the type is one of an asynchronous request type or a synchronous request type.

### Claim 4 (depends on 3)

The method of claim 3, wherein the message format of the QSOCKS request comprises an option to support at least one of transmission control protocol (TCP) or UDP over a Quick UDP Internet Connections (QUIC) protocol.

### Claim 5 (depends on 1)

The method of claim 1, wherein the plurality of client-supported SOCKS AUTH procedures comprises at least one of no authentication required, a generic security service application program interface (GSSAPI), a username, a password, an internet assigned numbers authority (IANA) assigned, a reserved, or an acceptable method.

### Claim 6

A method for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over Quick SOCKS (QSOCKS) in a wireless network, the method comprising:
transmitting, by a QSOCKS client device, a Client Hello (CHLO) message to a QSOCKS server using a QSOCKS method (QSKM) tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (AUTH) procedures; and
receiving, by the QSOCKS client device, a reject packet using the QSKM tag from the QSOCKS server,
wherein the reject packet includes information indicating a candidate client-supported SOCKS AUTH procedure which is selected by the QSOCKS server from the plurality of client-supported SOCKS AUTH procedures.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
transmitting, by the QSOCKS client device, the CHLO message to the QSOCKS server using a QSOCKS authentication (QSKA) tag, wherein the CHLO message comprises client credentials selected based on the selected SOCKS AUTH procedure, and wherein the QSKA tag contains a SOCKS AUTH sub-negotiation; and
receiving, by the QSOCKS client device, a Quick UDP Internet Connections (QUIC) Server Hello (SHLO) message using the QSKA tag from the QSOCKS server, in response to the QSOCKS server successfully verifying the credentials of the QSOCKS client device.

### Claim 8 (depends on 7)

The method of claim 7, further comprising:
transmitting, by QSOCKS client device, a QSOCKS request to the QSOCKS server, wherein the QSOCKS request comprises a message format; and
receiving, by QSOCKS client device, a QSOCKS response from the QSOCKS server, in response to the QSOCKS server initiating a SOCKS session by evaluating the QSOCKS request based on source and destination addresses,
wherein a block of the QSOCKS response indicates a field corresponding to a type of the QSOCKS request, and
wherein the type is one of an asynchronous request type or a synchronous request type.

### Claim 9 (depends on 8)

The method of claim 8, wherein the message format of the QSOCKS request comprises an option to support at least one of transmission control protocol (TCP) or UDP over a QUIC protocol.

### Claim 10 (depends on 6)

The method of claim 6, wherein the plurality of client-supported SOCKS AUTH procedures comprises at least one of no authentication required, a generic security service application program interface (GSSAPI), a username, a password, an internet assigned numbers authority (IANA) assigned, a reserved, or an acceptable method.

### Claim 11

A Quick SOCKS (QSOCKS) server for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over QSOCKS in a wireless network, the QSOCKS server comprising:
a memory;
a transceiver; and
at least one processor coupled to the memory and the transceiver,
wherein the at least one processor is configured to:
receive a Client Hello (CHLO) message from a QSOCKS client device using a QSOCKS method (QSKM) tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (SOCKS AUTH) procedures,
select a candidate client-supported SOCKS AUTH procedure from the plurality of client-supported SOCKS AUTH procedures, and
transmit a reject packet using the QSKM tag to the QSOCKS client device, and
wherein the reject packet includes information indicating the selected candidate client-supported SOCKS AUTH procedure.

### Claim 12 (depends on 11)

The QSOCKS server of claim 11, wherein the at least one processor is further configured to:
receive the CHLO message from the QSOCKS client device using a QSOCKS authentication (QSKA) tag, wherein the CHLO message comprises client credentials selected based on the selected SOCKS AUTH method, and wherein the QSKA tag contains a SOCKS AUTH sub-negotiation,
verify the credentials of the QSOCKS client device, and
transmit a Quick UDP Internet Connections (QUIC) Server Hello (SHLO) message using the QSKA tag in response to successful verification of the credentials.

### Claim 13 (depends on 12)

The QSOCKS server of claim 12,
wherein the at least one processor is further configured to:
receive a QSOCKS request from the QSOCKS client device, wherein the QSOCKS request comprises a message format,
evaluate the QSOCKS request based on source and destination addresses, and return one or more reply messages,
initiate a SOCKS session, and
transmit a QSOCKS response to the QSOCKS client device,
wherein a block of the QSOCKS response indicates a field corresponding to a type of the QSOCKS request, and
wherein the type is one of an asynchronous request type or a synchronous request type.

### Claim 14 (depends on 13)

The QSOCKS server of claim 13, wherein the message format of the QSOCKS request comprises an option to support at least one transmission control protocol (TCP) or UDP over a QUIC protocol.

### Claim 15 (depends on 11)

The QSOCKS server of claim 11, wherein the plurality of client-supported SOCKS AUTH procedures comprises at least one of no authentication required, a generic security service application program interface (GSSAPI), a username, a password, an internet assigned numbers authority (IANA) assigned, a reserved, or an acceptable method.

### Claim 16

A Quick SOCKS (QSOCKS) client device for Multipath Quick User Datagram Protocol (UDP) Internet Connections (MPQUIC) over QSOCKS in a wireless network, the QSOCKS server comprising:
a memory;
a transceiver; and
at least one processor coupled to the memory and the transceiver,
wherein the at least one processor is configured to:
transmit a Client Hello (CHLO) message to a QSOCKS server using a QSOCKS method (QSKM) tag, wherein the CHLO message comprises a plurality of client-supported SOCKS Authentication (AUTH) procedures, and
receive a reject packet using the QSKM tag from the QSOCKS server, and
wherein the reject packet includes information indicating a candidate client-supported SOCKS AUTH procedure which is selected by the QSOCKS server from the plurality of client-supported SOCKS AUTH procedures.

### Claim 17 (depends on 16)

The QSOCKS client device of claim 16, wherein the at least one processor is further configured to:
transmit the CHLO message to the QSOCKS server using a QSOCKS authentication (QSKA) tag, wherein the CHLO message comprises client credentials selected based on the selected SOCKS AUTH procedure, and wherein the QSKA tag contains a SOCKS AUTH sub-negotiation, and
receive a Quick UDP Internet Connections (QUIC) Server Hello (SHLO) message using the QSKA tag from the QSOCKS server, in response to the QSOCKS server successfully verifying the credentials of the QSOCKS client device.

### Claim 18 (depends on 17)

The QSOCKS client device of claim 17, wherein the at least one processor is further configured to:
transmit a QSOCKS request to the QSOCKS server, wherein the QSOCKS request comprises a message format, and
receive a QSOCKS response from the QSOCKS server, in response to the QSOCKS server initiating a SOCKS session by evaluating the QSOCKS request based on source and destination addresses,
wherein a block of the QSOCKS response indicates a field corresponding to a type of the QSOCKS request, and
wherein the type is one of an asynchronous request type or a synchronous request type.

### Claim 19 (depends on 18)

The QSOCKS client device of claim 18, wherein the message format of the QSOCKS request comprises an option to support at least one transmission control protocol (TCP) or UDP over a QUIC protocol.

### Claim 20 (depends on 16)

The QSOCKS client device of claim 16, wherein the plurality of client-supported SOCKS AUTH procedures comprises at least one of no authentication required, a generic security service application program interface (GSSAPI), a username, a password, an internet assigned numbers authority (IANA) assigned, a reserved, or an acceptable method.
