Development and Implementation of an Adaptive HTTP Streaming Framework for H.264/MVC Coded Media
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
BIG-IP® Acceleration: Concepts
BIG-IP® Acceleration: Concepts Version 12.1.0 Table of Contents Table of Contents Introducing Acceleration..........................................................................................................11 Overview: Introduction to acceleration.............................................................................11 Origin web server load balancing..........................................................................11 About data centers................................................................................................12 Data compression.................................................................................................12 Data deduplication.................................................................................................12 Optimization of TCP connections..........................................................................12 Caching objects.....................................................................................................13 Optimization of HTTP protocol and web applications............................................13 Overview: BIG-IP Acceleration.........................................................................................14 Application management.......................................................................................14 Application monitoring...........................................................................................14 Deployment of Distributed BIG-IP Application Acceleration..................................14 Management -
Detecting Middlebox Interference on Applications
Detecting Middlebox Interference on Applications Shan Huang Felix´ Cuadrado, Steve Uhlig School of Electronic Engineering and Computer Science Submitted for the degree of Master of Philosophy to the University of London July 2017 Abstract Middleboxes are widely used in today’s Internet, especially for security and performance. Mid- dleboxes classify, filter and shape traffic, therefore interfering with application behaviour and performing new network functions for end hosts. Recent studies have uncovered and studied middleboxes in different types of networks. In order to understand the middlebox interference on traffic flows and explore the involved ASes, our methodology relies on a client-server architecture, to be able to observe both directions of the middlebox interaction. Meanwhile, probing with increasing TTL values provides us chances to inspect behaviour of middleboxes hop by hop. Implementing our methodologies, we exploit a large-scale proxy infrastructure Luminati, to de- tect HTTP-interacting middleboxes across the Internet. We collect a large-scale dataset from van- tage points distributed in nearly 10,000 ASes across 196 countries. Our results provide abundant evidence for middleboxes deployed across more than 1000 ASes. We observe various middle- box interference in both directions of traffic flows, and across a wide range networks, including mobile operators and data center networks. i Contents 1 Introduction3 1.1 Introduction.....................................3 1.2 Motivation......................................4 1.3 Contribution.....................................5 2 Literature Study6 2.1 Middleboxes Taxonomy..............................6 2.2 Middleboxes Today.................................7 2.2.1 Middleboxes in Enterprise Networks....................7 2.2.2 Middleboxes in ISP Networks.......................8 2.2.3 Middleboxes and Internet Censorship...................9 2.3 Detecting Method................................. -
(12) Patent Application Publication (10) Pub. No.: US 2016/0337426A1 Shribman Et Al
US 20160337426A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2016/0337426A1 Shribman et al. (43) Pub. Date: Nov. 17, 2016 (54) SYSTEM AND METHOD FOR STREAMING (52) U.S. Cl. CONTENT FROM MULTIPLE SERVERS CPC ........... H04L 65/4084 (2013.01); H04L 67/42 (2013.01); H04L 67/02 (2013.01); H04L (71) Applicant: Hols NETWORKS LTD., Netanya 65/608 (2013.01); H04N 21/6125 (2013.01) IL (72) Inventors: Derry Shribman, Tel Aviv (IL): Ofer Vilenski, Moshav Hadar Am (IL) (57) ABSTRACT (21) Appl. No.: 15/089,721 A system and a method for media streaming from multiple (22) Filed: Apr. 4, 2016 Sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that Related U.S. Application Data may include multiple Content Delivery Networks (CDNs) (60) Provisional application No. 62/161,553, filed on May and independent servers. Based on a pre-set criteria, such as 14, 2015, provisional application No. 62/173,411, the source delivery performance and cost, the client device filed on Jun. 10, 2015, provisional application No. part1tions the content into parts, allocates a source to each 62/210,081, filed on Aug. 26, 2015, provisional ap- part, and simultaneously receives media streams of the plication No. 623.08.29ified on Mar 15, 2016. content parts from the allocated sources. The server may be s1 - us s a Video-on-Demand (VOD) server, and the content may be Publication Classification a single file of a video data, Such as a movie. The delivery performance of the used sources is measured during the (51) Int. -
Http Status Codes
HTTP STATUS CODES This is a list of Hypertext Transfer Protocol (HTTP) response status codes. 1XX Informational responses An informational response indicates that the request was received and understood. It is issued on a provisional basis while request processing continues. It alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. The response 417 Expectation Failed indicates the request should not be continued.[2] 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so.[5] 102 Processing (WebDAV; RFC 2518) A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.[6] This prevents the client from timing out and assuming the request was lost. -
BIG-IP Acceleration
BIG-IP® Acceleration: Concepts Version 13.0.0 Table of Contents Table of Contents Introducing Acceleration............................................................................................................9 Overview: Introduction to acceleration............................................................................... 9 Origin web server load balancing............................................................................9 About data centers.................................................................................................. 9 Data compression................................................................................................. 10 Data deduplication.................................................................................................10 Optimization of TCP connections..........................................................................10 Caching objects.....................................................................................................11 Optimization of HTTP protocol and web applications............................................11 Overview: BIG-IP Acceleration.........................................................................................11 Application management.......................................................................................12 Application monitoring...........................................................................................12 Deployment of Distributed BIG-IP Application Acceleration..................................12