# US 2016/0261664 A1 · Indication for Partial Segment

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

- Number: US 2016/0261664 A1
- Document ID: US20160261664A1
- Status: Published application
- Kind: A1
- Application number: 15/054,214
- Filed: 2016-02-26
- Published: 2016-09-08
- Earliest claimed: 2015-03-02
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Osama Lotfallah; Carlos Marcelo Dias Pazos; Charles Nung Lo; Nagaraju Naik; Thomas Stockhammer
- Web page: https://patentgrep.com/patent/US20160261664A1

## CPC

- H04L 65/80: Responding to QoS
- H04L 65/612: for unicast
- H04L 65/65: Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
- H04L 65/762: {at the source (reformatting of additional data in video distribution servers H04N21/2355)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and devices of the various embodiments enable HTTP servers, such as HTTP servers providing segments to DASH clients according to the various embodiments, to pass incomplete versions of segments in response to segment requests from the DASH clients. The various embodiments may enable clients, such as DASH clients, to parse incomplete versions of segments.

## Claims

### Claim 1

A method for delivering an incomplete response to a media file request from a server to a client, comprising:
receiving a segment request in the server from the client, wherein the segment request indicates whether the client is capable of using an incomplete segment;
determining, in the server, whether a full segment associated with the segment request is available at the server;
determining, in the server, based on the segment request, whether the client is capable of using an incomplete segment in response to the full segment associated with the segment request not being available at the server; and
sending from the server to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment.

### Claim 2 (depends on 1)

The method of claim 1, wherein one or both of the indication that the response message includes the incomplete segment and the indication of one or more access positions for the incomplete segment are separate header fields in the response message.

### Claim 3 (depends on 1)

The method of claim 1, wherein the response message further includes an indication of a portion of a requested segment that is included in the incomplete segment included in the response message.

### Claim 4 (depends on 3)

The method of claim 3, wherein the indication of the portion of the requested segment that is included in the incomplete segment comprises an indication of a byte range within the requested segment that is included in the incomplete segment.

### Claim 5 (depends on 4)

The method of claim 4, wherein one or more header fields of the response message include the indication of the portion of the requested segment that is included in the incomplete segment.

### Claim 6 (depends on 5)

The method of claim 5, wherein the one or more access positions for the incomplete segment are located within the byte range within the requested segment that is included in the incomplete segment.

### Claim 7 (depends on 1)

The method of claim 1, wherein the one or more access positions is one or more intermediate byte positions in a byte range of a segment associated with the segment request.

### Claim 8 (depends on 7)

The method of claim 7, wherein at least one access position is outside an initial portion of the segment associated with the segment request.

### Claim 9 (depends on 8)

The method of claim 8, wherein the initial portion of the segment associated with the segment request is a first movie fragment header of the segment.

### Claim 10 (depends on 1)

The method of claim 1, wherein the one or more access positions are indicated in a File Delivery Table (FDT) describing a segment associated with the segment request.

### Claim 11 (depends on 10)

The method of claim 10, wherein the one or more access positions are indicated by one or more comma-separated byte positions in the FDT.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
determining in the server whether no bytes associated with the segment request are available at the server in response to determining that the client is capable of using an incomplete segment; and
sending from the server to the client an error message in response to determining that no bytes associated with the segment request are available at the server,
wherein sending from the server to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment comprises sending from the server to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment and determining that a byte associated with the segment request is available at the server.

### Claim 13 (depends on 12)

The method of claim 12, wherein the error message indicates that no bytes associated with the segment request are available at the server.

### Claim 14 (depends on 13)

The method of claim 13, wherein the error message includes a 416 status code.

### Claim 15 (depends on 1)

The method of claim 1, wherein the client is a DASH client and the server is a DASH server.

### Claim 16

A method for delivering an incomplete response to a media file request from a server to a client, comprising:
sending to the client from the server a message including an incomplete version of a media file and an extension header indicating one or more access positions for the incomplete version of the media file.

### Claim 17 (depends on 16)

The method of claim 16, wherein the extension header further indicates a byte range within a requested media file that is included in the incomplete version of the media file.

### Claim 18 (depends on 16)

The method of claim 16, wherein the client is a DASH client and the server is a DASH server.

### Claim 19

A server, comprising:
a processor configured with processor-executable instructions to perform operations comprising:
receiving a segment request from a client, wherein the segment request indicates whether the client is capable of using an incomplete segment;
determining whether a full segment associated with the segment request is available;
determining, based on the segment request, whether the client is capable of using an incomplete segment in response to the full segment associated with the segment request not being available; and
sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment.

### Claim 20 (depends on 19)

The server of claim 19, wherein the processor is configured with processor-executable instructions to perform operations such that one or both of the indication that the response message includes the incomplete segment and the indication of one or more access positions for the incomplete segment are separate header fields in the response message.

### Claim 21 (depends on 19)

The server of claim 19, wherein the processor is configured with processor-executable instructions to perform operations such that the response message further includes an indication of a portion of a requested segment that is included in the incomplete segment included in the response message.

### Claim 22 (depends on 21)

The server of claim 21, wherein the processor is configured with processor-executable instructions to perform operations such that the indication of the portion of the requested segment that is included in the incomplete segment comprises an indication of a byte range within the requested segment that is included in the incomplete segment.

### Claim 23 (depends on 22)

The server of claim 22, wherein the processor is configured with processor-executable instructions to perform operations such that one or more header fields of the response message include the indication of the portion of the requested segment that is included in the incomplete segment.

### Claim 24 (depends on 23)

The server of claim 23, wherein the processor is configured with processor-executable instructions to perform operations such that the one or more access positions for the incomplete segment are located within the byte range within the requested segment that is included in the incomplete segment.

### Claim 25 (depends on 19)

The server of claim 19, wherein the processor is configured with processor-executable instructions to perform operations such that the one or more access positions is one or more intermediate byte positions in a byte range of a segment associated with the segment request.

### Claim 26 (depends on 25)

The server of claim 25, wherein the processor is configured with processor-executable instructions to perform operations such that at least one access position is outside an initial portion of the segment associated with the segment request.

### Claim 27 (depends on 26)

The server of claim 26, wherein the processor is configured with processor-executable instructions to perform operations such that the initial portion of the segment associated with the segment request is a first movie fragment header of the segment.

### Claim 28 (depends on 19)

The server of claim 19, wherein the processor is configured with processor-executable instructions to perform operations such that the one or more access positions are indicated in a File Delivery Table (FDT) describing a segment associated with the segment request.

### Claim 29 (depends on 28)

The server of claim 28, wherein the processor is configured with processor-executable instructions to perform operations such that the one or more access positions are indicated by one or more comma-separated byte positions in the FDT.

### Claim 30 (depends on 19)

The server of claim 19, wherein the processor is configured with processor-executable instructions to perform operations further comprising:
determining whether no bytes associated with the segment request are available in response to determining that the client is capable of using an incomplete segment; and
sending to the client an error message in response to determining that no bytes associated with the segment request are available,
wherein the processor is configured with processor-executable instructions to perform operations such that sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment comprises sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment and determining that a byte associated with the segment request is available.

### Claim 31 (depends on 30)

The server of claim 30, wherein the processor is configured with processor-executable instructions to perform operations such that the error message indicates that no bytes associated with the segment request are available.

### Claim 32 (depends on 31)

The server of claim 31, wherein the processor is configured with processor-executable instructions to perform operations such that the error message includes a 416 status code.

### Claim 33 (depends on 19)

The server of claim 19, wherein the client is a DASH client.

### Claim 34

A server, comprising:
a processor configured with processor-executable instructions to perform operations comprising:
sending to a client a message including an incomplete version of a media file and an extension header indicating one or more access positions for the incomplete version of the media file.

### Claim 35 (depends on 34)

The server of claim 34, wherein the processor is configured with processor-executable instructions to perform operations such that the extension header further indicates a byte range within a requested media file that is included in the incomplete version of the media file.

### Claim 36 (depends on 34)

The server of claim 34, wherein the client is a DASH client.

### Claim 37

A server, comprising:
means for receiving a segment request from a client, wherein the segment request indicates whether the client is capable of using an incomplete segment;
means for determining whether a full segment associated with the segment request is available;
means for determining, based on the segment request, whether the client is capable of using an incomplete segment in response to the full segment associated with the segment request not being available; and
means for sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment.

### Claim 38 (depends on 37)

The server of claim 37, wherein one or both of the indication that the response message includes the incomplete segment and the indication of one or more access positions for the incomplete segment are separate header fields in the response message.

### Claim 39 (depends on 37)

The server of claim 37, wherein the response message further includes an indication of a portion of a requested segment that is included in the incomplete segment included in the response message.

### Claim 40 (depends on 39)

The server of claim 39, wherein the indication of the portion of the requested segment that is included in the incomplete segment comprises an indication of a byte range within the requested segment that is included in the incomplete segment.

### Claim 41 (depends on 40)

The server of claim 40, wherein one or more header fields of the response message include the indication of the portion of the requested segment that is included in the incomplete segment.

### Claim 42 (depends on 41)

The server of claim 41, wherein the one or more access positions for the incomplete segment are located within the byte range within the requested segment that is included in the incomplete segment.

### Claim 43 (depends on 37)

The server of claim 37, wherein the one or more access positions is one or more intermediate byte positions in a byte range of a segment associated with the segment request.

### Claim 44 (depends on 43)

The server of claim 43, wherein at least one access position is outside an initial portion of the segment associated with the segment request.

### Claim 45 (depends on 44)

The server of claim 44, wherein the initial portion of the segment associated with the segment request is a first movie fragment header of the segment.

### Claim 46 (depends on 37)

The server of claim 37, wherein the one or more access positions are indicated in a File Delivery Table (FDT) describing a segment associated with the segment request.

### Claim 47 (depends on 46)

The server of claim 46, wherein the one or more access positions are indicated by one or more comma-separated byte positions in the FDT.

### Claim 48 (depends on 37)

The server of claim 37, further comprising:
means for determining whether no bytes associated with the segment request are available in response to determining that the client is capable of using an incomplete segment; and
means for sending to the client an error message in response to determining that no bytes associated with the segment request are available,
wherein means for sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment comprises means for sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment and determining that a byte associated with the segment request is available.

### Claim 49 (depends on 48)

The server of claim 48, wherein the error message indicates that no bytes associated with the segment request are available.

### Claim 50 (depends on 49)

The server of claim 49, wherein the error message includes a 416 status code.

### Claim 51 (depends on 37)

The server of claim 37, wherein the client is a DASH client.

### Claim 52

A server, comprising:
means for sending to a client a message including an incomplete version of a media file and an extension header indicating one or more access positions for the incomplete version of the media file.

### Claim 53 (depends on 52)

The server of claim 52, wherein the extension header further indicates a byte range within a requested media file that is included in the incomplete version of the media file.

### Claim 54 (depends on 52)

The server of claim 52, wherein the client is a DASH client.

### Claim 55

A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a server processor to perform operations comprising:
receiving a segment request from a client, wherein the segment request indicates whether the client is capable of using an incomplete segment;
determining whether a full segment associated with the segment request is available;
determining, based on the segment request, whether the client is capable of using an incomplete segment in response to the full segment associated with the segment request not being available; and
sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment.

### Claim 56 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that one or both of the indication that the response message includes the incomplete segment and the indication of one or more access positions for the incomplete segment are separate header fields in the response message.

### Claim 57 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the response message further includes an indication of a portion of a requested segment that is included in the incomplete segment included in the response message.

### Claim 58 (depends on 57)

The non-transitory processor-readable storage medium of claim 57, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the indication of the portion of the requested segment that is included in the incomplete segment comprises an indication of a byte range within the requested segment that is included in the incomplete segment.

### Claim 59 (depends on 58)

The non-transitory processor-readable storage medium of claim 58, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that one or more header fields of the response message include the indication of the portion of the requested segment that is included in the incomplete segment.

### Claim 60 (depends on 59)

The non-transitory processor-readable storage medium of claim 59, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the one or more access positions for the incomplete segment are located within the byte range within the requested segment that is included in the incomplete segment.

### Claim 61 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the one or more access positions is one or more intermediate byte positions in a byte range of a segment associated with the segment request.

### Claim 62 (depends on 61)

The non-transitory processor-readable storage medium of claim 61, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that at least one access position is outside an initial portion of the segment associated with the segment request.

### Claim 63 (depends on 62)

The non-transitory processor-readable storage medium of claim 62, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the initial portion of the segment associated with the segment request is a first movie fragment header of the segment.

### Claim 64 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the one or more access positions are indicated in a File Delivery Table (FDT) describing a segment associated with the segment request.

### Claim 65 (depends on 64)

The non-transitory processor-readable storage medium of claim 64, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the one or more access positions are indicated by one or more comma-separated byte positions in the FDT.

### Claim 66 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations further comprising:
determining whether no bytes associated with the segment request are available in response to determining that the client is capable of using an incomplete segment; and
sending to the client an error message in response to determining that no bytes associated with the segment request are available, and
wherein the stored processor-executable instructions are configured to cause a server processor to perform operations such that sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment comprises sending to the client an incomplete segment in a response message including an indication that the response message includes the incomplete segment and an indication of one or more access positions for the incomplete segment in response to determining that the client is capable of using an incomplete segment and determining that a byte associated with the segment request is available.

### Claim 67 (depends on 66)

The non-transitory processor-readable storage medium of claim 66, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the error message indicates that no bytes associated with the segment request are available.

### Claim 68 (depends on 67)

The non-transitory processor-readable storage medium of claim 67, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the error message includes a 416 status code.

### Claim 69 (depends on 55)

The non-transitory processor-readable storage medium of claim 55, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the client is a DASH client.

### Claim 70

A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a server processor to perform operations comprising:
sending to a client a message including an incomplete version of a media file and an extension header indicating one or more access positions for the incomplete version of the media file.

### Claim 71 (depends on 70)

The non-transitory processor-readable storage medium of claim 70, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the extension header further indicates a byte range within a requested media file that is included in the incomplete version of the media file.

### Claim 72 (depends on 70)

The non-transitory processor-readable storage medium of claim 70, wherein the stored processor-executable instructions are configured to cause the server processor to perform operations such that the client is a DASH client.
