# US 2019/0379720 A1 · Server- and network-assisted dynamic adaptive streaming over hypertext transport protocol signaling

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

- Number: US 2019/0379720 A1
- Document ID: US20190379720A1
- Status: Published application
- Kind: A1
- Application number: 16/480,149
- Filed: 2017-04-14
- Published: 2019-12-12
- Earliest claimed: 2017-04-14
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Yifan YU; Ozgur OYMAN; Yuan ZHU
- Web page: https://patentgrep.com/patent/US20190379720A1

## CPC

- H04L 69/14: Multichannel or multilink protocols
- H04L 63/0281: {Proxies}
- H04L 63/166: {at the transport layer}
- H04L 65/1069: Session establishment or de-establishment
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L 65/764: {at the destination (reformatting of additional data in video clients H04N21/4355)}
- H04L 65/80: Responding to QoS
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure describe methods and apparatuses for server- and network-assisted dynamic adaptive streaming over hypertext transport protocol signaling.

## Claims

### Claim 1

One or more non-transitory, computer-readable media having instructions that, when executed, cause a server to:
set up a first leg of a transmission control protocol (“TCP”) connection between the server and a streaming client of a user equipment;
set up a second leg of the TCP connection between the server and a hypertext transfer protocol over transport layer security (HTTPS) server;
detect, in a ClientHello message transmitted from the streaming client to the HTTPS server, a transport layer security (“TLS”) extension that corresponds to a first server- and network-assisted dynamic adaptive streaming over hypertext transport protocol (“SAND”) message; and
modify a media presentation description (“MPD”) file based on the SAND message and cause the MPD file to be transmitted to the user equipment.

### Claim 2 (depends on 1)

The one or more non-transitory, computer-readable media of claim 1, wherein the SAND message is a first SAND message and the instructions, when executed, further cause the server to:
insert, in a ServerHello message transmitted from the HTTPS server, a second SAND message.

### Claim 3 (depends on 2)

The one or more non-transitory, computer-readable media of claim 2, wherein the first SAND message includes a status message or a metrics message and the second SAND message includes a parameters enhancing reception message.

### Claim 4 (depends on 1)

The one or more non-transitory, computer-readable media of claim 1, wherein the SAND message includes a user equipment authentication/authorization identifier (“UEAA ID”) and a service identifier (“ID”) and the instructions, when executed, further cause the server to:
authenticate or authorize the user equipment (“UE”) or over-the-top (“OTT”) streaming service based on the UEAA ID and the service ID; and
engage a SAND entity in a message exchange based on the authentication or authorization of the UE or OTT streaming service.

### Claim 5 (depends on 1)

The one or more non-transitory, computer-readable media of claim 1, wherein the instructions, when executed, further cause the server to:
extract the SAND message from the ClientHello message based on detection of the TLS extension.

### Claim 6 (depends on 1)

The one or more non-transitory, computer-readable media of claim 1, wherein the server is a packet-switched streaming service (“PSS”) server.

### Claim 7 (depends on 1)

The one or more non-transitory, computer-readable media of claim 1, wherein the server is a mobile edge computing server.

### Claim 8

A user equipment (“UE”) having circuitry to provide:
processing circuitry to implement an over-the-top (“OTT”) streaming client to:
establish a transmission control protocol (“TCP”) connection;
generate a message to establish a secured data path to a hypertext transfer protocol over transport layer security (HTTPS) server, the message to include a transport layer security (“TLS”) extension that corresponds to a server- and network-assisted dynamic adaptive streaming over hypertext transport protocol (“SAND”) message; and
communication circuitry coupled with the processing circuitry to cause the message to be transmitted to the HTTPS server.

### Claim 9 (depends on 8)

The UE of claim 8, wherein the message is a TLS handshaking message.

### Claim 10 (depends on 9)

The UE of claim 9, wherein the TLS handshaking message is a ClientHello message.

### Claim 11 (depends on 10)

The UE of claim 10, wherein the SAND message is a first SAND message and the OTT streaming client is further to:
receive a ServerHello message from a server; and
extract a second SAND message from the ServerHello message.

### Claim 12 (depends on 11)

The UE of claim 11, wherein the OTT streaming client is further to stream video over a TLS connection based on information from the second SAND message.

### Claim 13 (depends on 10)

The UE of claim 10, wherein the SAND message is to include a user equipment authentication/authorization identifier (“UEAA ID”) to identify a specific streaming service in the UE.

### Claim 14 (depends on 10)

The UE of claim 10, wherein the SAND message is to include a service identifier to identify a service registered by a mobile network operator.

### Claim 15 (depends on 8)

The UE of claim 8, wherein the OTT streaming client is further to:
receive a media presentation description (“MPD”) file; and
request media segments based on the MPD file.

### Claim at position 16

-24. (canceled)

### Claim 25

One or more non-transitory, computer-readable media having instructions that, when executed, cause a device to:
establish a transmission control protocol (“TCP”) connection;
generate a message to establish a secured data path to a hypertext transfer protocol over transport layer security (HTTPS) server, the message to include a transport layer security (“TLS”) extension that corresponds to a server- and network-assisted dynamic adaptive streaming over hypertext transport protocol (“SAND”) message; and
cause the message to be transmitted to the HTTPS server.

### Claim 26 (depends on 25)

The one or more non-transitory, computer-readable media of claim 25, wherein the message is a TLS handshaking message.

### Claim 27 (depends on 26)

The one or more non-transitory, computer-readable media of claim 26, wherein the TLS handshaking message is a ClientHello message.

### Claim 28 (depends on 27)

The one or more non-transitory, computer-readable media of claim 27, wherein the SAND message is a first SAND message and the instructions, when executed, further cause the device to:
receive a ServerHello message from a server; and
extract a second SAND message from the ServerHello message.

### Claim 29 (depends on 28)

The one or more non-transitory, computer-readable media of claim 28, wherein the instructions, when executed, further cause the device to stream video over a TLS connection based on information from the second SAND message.

### Claim 30 (depends on 25)

The one or more non-transitory, computer-readable media of claim 25, wherein the SAND message is to include a user equipment authentication/authorization identifier (“UEAA ID”) to identify a specific streaming service in the UE.

### Claim 31 (depends on 25)

The one or more non-transitory, computer-readable media of claim 25, wherein the SAND message is to include a service identifier to identify a service registered by a mobile network operator.
