Signaling which version information to use on byte-range file repair
Systems, methods, and devices of various embodiments enable signaling one or more capabilities of servers, such as web servers or content delivery network (CDN) servers, to use file version information, such as MD5s (message digest 5 (MD5) algorithm hash values) and/or entity tags (ETags), to computing devices for byte-range file repair.
1. A computing device, comprising:
a processor configured with processor-executable instructions to perform operations comprising:
determining whether a description of a service includes an entity tag (ETag) value for a file in response to determining that byte-range file repair is needed to repair the file wherein the description of the service is an Associated Delivery Procedure Description (ADPD) metadata fragment;
generating a partial Hypertext Transfer Protocol (HTTP) GET request for byte-range file repair including the ETag value in an If-Match header element in response to determining that the description of the service includes the ETag value;
determining whether an attribute of the ADPD metadata fragment indicates a server supports using an MD5 as the ETag value in response to determining that the ADPD metadata fragment does not include the ETag value; and
generating a partial HTTP GET request for byte-range file repair including the MD5 as the ETag value in an If-Match header element in response to determining that the attribute of the ADPD metadata fragment indicates the server supports using the MD5 as the ETag value.
2. The computing device of claim 1 , wherein the description of the service is a File Delivery Table (FDT).
3. The computing device of claim 1 , wherein the processor is configured with processor-executable instructions to perform operations further comprising:
generating a partial HTTP GET request for byte-range file repair without including an If-Match header element in response to determining that the attribute of the ADPD metadata fragment does not indicate the server supports using the MD5 as the ETag value.
4. The computing device of claim 3 , wherein the service is an evolved Multimedia Broadcast Multicast Service (eMBMS) service.
5. A method, comprising:
determining, at a computing device, whether a description of a service includes an entity tag (ETag) value for a file in response to determining that byte-range file repair is needed to repair the file by the computing device, wherein the description of the service is an Associated Delivery Procedure Description (ADPD) metadata fragment;
generating, at the computing device, a partial Hypertext Transfer Protocol (HTTP) GET request for byte-range file repair including the ETag value in an If-Match header element in response to determining that the description of the service includes the ETag value;
determining whether an attribute of the ADPD metadata fragment indicates a server supports using an MD5 as the ETag value in response to determining that the ADPD metadata fragment does not include the ETag value; and
generating a partial HTTP GET request for byte-range file repair including the MD5 as the ETag value in an If-Match header element in response to determining that the attribute of the ADPD metadata fragment indicates the server supports using the MD5 as the ETag value.
6. The method of claim 5 , wherein the description of the service is a File Delivery Table (FDT).
7. The method of claim 5 , further comprising:
generating, at the computing device, a partial HTTP GET request for byte-range file repair without including an If-Match header element in response to determining that the attribute of the ADPD metadata fragment does not indicate the server supports using the MD5 as the ETag.
8. The method of claim 7 , wherein the service is an evolved Multimedia Broadcast Multicast Service (eMBMS) service.
9. A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a computing device to perform operations, comprising:
determining whether a description of a service includes an entity tag (ETag) value for a file in response to determining that byte-range file repair is needed to repair the file, wherein the description of the service is an Associated Delivery Procedure Description (ADPD) metadata fragment;
generating a partial Hypertext Transfer Protocol (HTTP) GET request for byte-range file repair including the ETag value in an If-Match header element in response to determining that the description of the service includes the ETag value;
determining whether an attribute of the ADPD metadata fragment indicates a server supports using an MD5 as the ETag value in response to determining that the ADPD metadata fragment does not include the ETag value; and
generating a partial HTTP GET request for byte-range file repair including the MD5 as the ETag value in an If-Match header element in response to determining that the attribute of the ADPD metadata fragment indicates the server supports using the MD5 as the ETag value.
10. The non-transitory processor-readable storage medium of claim 9 , wherein the stored processor-executable instructions are configured to cause a processor of a computing device to perform operations such that the description of the service is a File Delivery Table (FDT).
11. The non-transitory processor-readable storage medium of claim 9 , wherein the stored processor-executable instructions are configured to cause a processor of a computing device to perform operations further comprising:
generating a partial HTTP GET request for byte-range file repair without including an If-Match header element in response to determining that the attribute of the ADPD metadata fragment does not indicate the server supports using the MD5 as the ETag value.
12. The non-transitory processor-readable storage medium of claim 11 , wherein the stored processor-executable instructions are configured to cause a processor of a computing device to perform operations such that the service is an evolved Multimedia Broadcast Multicast Service (eMBMS) service.