VIDEO STREAMING OVER FULL DUPLEX NETWORK USING WEB SOCKETS

(1)

International Journal of Recent Advances in Engineering & Technology (IJRAET)

________________________________________________________________________

ISSN (Online): 2347 - 2812, Volume-2, Issue - 1, January, 2014 44

VIDEO STREAMING OVER FULL DUPLEX NETWORK USING WEB SOCKETS

1

Shweta Thakur,

²

V. A. Gulhane

1 Project Student M. Tech (CSE), G.H. Raisoni College of Engineering, Nagpur, India

2 G.H. Raisoni College of Engineering ,Nagpur, India Email : [email protected]

Abstract -The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted- in to communications . The security model used for this is the origin-based security model commonly used by web browsers. The procedure consists of an opening handshake followed by basic message framing. The goal of this technology is to provide a mechanism for browser- based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).The web socket protocol uses self signed certificate to provide security. Speed in videostreaming can be achived using full Duplex network.

Keywords: web sockets, HTML5, full duplex network, web browser.

I. INTRODUCTION

Historically, creating web applications that need bidirectional communication between a client and a server (e.g., instant messaging and gaming applications) has required an abuse of HTTP to poll the server for updates while sending upstream notifications as distinct HTTP calls. This results in a range of problems:

The server is required to use a number of different underlying TCP connections for each client: one for sending information to the client and a new one for each incoming message.

The wire protocol has a elevated overhead, with each client-to-server message having an HTTP header.

The client-side script is forced to maintain a map from the outgoing connections to the incoming connection to track replies.

A simpler solution would be to use a single TCP connection for traffic in both directions. That is what the WebSocket Protocol provides combined with the WebSocket API, it provides an substitute to HTTP polling for two-way communication from a web page to a remote server. Video-streaming is experiencing dramatic growth. Its use has been potentiated by the convergence of TV with the Internet, the emergence of new services. The real-time characteristic of video services demands infrastructures provided with efficient performance monitoring and failure recovery capabilities. Performance problems usually occur server- side or in the network. Network-related problems have standard solutions based on graceful degradation of video quality .the videostreaming must be done fast , multimedia services on these devices and draw a huge amount of mobile multimedia traffic. The average volume of video traffic on mobile networks has risen by 10 percentage points since 2011 - up to 50% from 40%.

In certain networks, video traffic is up to 69% of total traffic [2-3].

However, networks are sometimes unstable and smart phone frequently changes its network interfaces between 30/40 network and Wi-Fi network. Smartphone users usually use their own Wi-Fi networks for high speed and low charges, but they have poor connections when they move around due to short range of Wi-Fi. Also, it has a few meters of coverage in high attenuation indoor environment. In this section, we propose the architecture

(2)

International Journal of Recent Advances in Engineering & Technology (IJRAET)

________________________________________________________________________

of continuous player for HLS on heterogeneous network. The player is based on the standard HTML5 tags, JavaScript, and built-in video Player of web browser. Many implementations use a web browser to support direct and interactive communications, with voice, video, collaboration, and gaming. In these implementations, the web server acts as the signaling lane between these applications. Up till now, such applications have typically required the installation of plug-ins or non-standard browser extensions. In nearly one or two year, there has an new technology called RTCWeb or Web RTC that means the application can be run in any compatible browser and allow for high- quality realtime communications experiences within the browser without the need for a browser plug-in or Flash, Java, etc.

II. LITERATURE SURVEY

Failure prediction [1] Failure prediction provides an opportunity to gracefully handle failure before potential outages occur. Prediction models identify pre-failure patters of server behavior. It allows failure detection, load admittance, online learning and evaluation of models and recovery Virtualization [2] Virtualization techniques are used to migrate the server state and connection established with clients. Virtualization avoids the pre- reservation of resources in the failure host. Remote virtualization using websockets [3] .It uses new technologies to make remote virtualization accessible to anyone without the need to neither download any of the data nor need to specialized hardware to visualize it. Client side rendering can be become limited both in terms of storage space and processing power. RTC-web.[4] Application can be run in any compatible browser and allow for high quality real-time communication experiences within the browser without the need for a browser plug-in or extension in Flash java etc . 3D mass [5] .It provides feasible solution to address interpretable delivery of advanced 3D media application to home network.

It deals with heter9ogeneous application, latency requirement and generate different streaming format to fit with specific device capability. http polling or http long polling [6] This provides a solution on the polling technique that effectively handles the information push from server to client. With the long polling the server does not send an empty response immediately as there is no new messages are available for client. Instead the server holds the request until the new message is available or time out expand. XMLHttpRequest LongPolling& HTML5 [7] It is a form of long polling the client sends request to the server & the TCP connection carrying the HTTP request is kept open the server response to the client, after receiving the response the TCP connection is closed. The client sends another request to the server but no new messages have arrived at the server & it delays sending a response .The key limitation of this technique is that each interaction

between client & server is experienced in the form of HTTP request response , resulting in significant overhead & delay. HTML5 Websocket [8] This technique is designed to overcome the limitation of XHR polling. The websocket runs over a long-lived TCP socket to deliver the bidirectional stream and this makes it significantly more efficient than XHR polling.

HTML5 technology [9] Medial players which are based on DirectX ,Flash and ActiveX have many problems such as installation failure, maintenance , security defects etc.HTML5 video tag is very excellent for static video files. It is not suitable for streaming live video.

Comet technology[10] achieving bidirectional communication is a way to solve the problems mentioned. However, when data is received or a timeout terminates the connection, the browser reconnects and waits for the next update, this could result in more communication overhead, and comet technology consumes server's bandwidth and resources greatly because of maintaining two connections, Web tree [11]

The tree structure is a very popular way to show information, it is widely used in web applications, has the advantages of intuitive and convenient, especially in expressing the directory structure, hierarchy, etc.

Currently, most web tree component is based on AJAX technology. AJAX Technology [12] AJAX has proven successful for providing dynamic content without reloading pages.HTML & HTML5 [13] Hyper Text Markup Language is the main markup language for web pages. HTML5 is a new creation of HTML standards.

With the development of HTML5, it has extensive range of applications in the multimedia direction. This latest standard first describes the Video and Audio tag, and then elements of Video and Audio pointing out that the support of the current browser to Video and Audio format.MPEG DASH[14] standard and developed using a GStreamer media framework , can be integrated into an HTML5 enabled web browser. Through a non- standard interface, the GStreamer adaptive streaming client can be controlled by a JavaScript engine implemented in the web browser.

III. PROBLEM STATEMENT

Current web relies on HTTP for communication which is a request-reply protocol. To achieve desktop like (real-time) experience, programmers use techniques like polling, long polling and streaming. All of these methods use HTTP protocol to communicate with the server. Every request sent to server over HTTP contains lot of unnecessary header information describing where this request came from, where it’s heading, the user agent information, etc. This information adds a lot of overhead on bandwidth in real-time scenarios. Secondly, this is not a full-duplex communication. Which means client and server cannot send and receive message at the same time.

Also the current videostreaming is done over http which is half duplex network, whenever the client wants to

(3)

International Journal of Recent Advances in Engineering & Technology (IJRAET)

________________________________________________________________________

make connection with the server for some data it will send the request to the client the server makes the connection with the client and reply to it & the connection is closed. For another request the same procedure is repeated similarly for n request n no of times the request is send to the client and the connection is made. This procedure is time consuming & it makes unnecessary overhead of maintaining the connection.

IV. ARCHITECTURE

The Web Socket Protocol enables two-way communication between a client and remote host. The protocol consists of handshaking followed by basic message framing. In handshaking the client first sends the request for connection i.e. the request for handshaking , the requests are managed in the form of queue. After the queue management the connection is established between the client & the server, the handshaking is done & the queue is updated.

Once the client and server have both sent their handshakes, and if the handshake be successful, then the data transfer starts. This is a two-way communication channel where each side can, independently send and receive the data. After a successful handshake, clients and servers transfer data back and forth in conceptual units referred to in this specification as "messages". On the wire, a message is composed of one or more frames.

The WebSocket message does not necessarily correspond to a particular network layer framing, as a fragmented message may be split by an intermediary. A frame has an related type. Each frame belonging to the same message contains the same type of data. There are types for textual data , binary data and control frames.

This version of the protocol defines six frame types and leaves ten reserved for further use. To prove that the handshake be received, the server has to take two pieces of information and combine them to form a response.

The first part of information comes from the |Sec- WebSocket-Key| header field in the client handshake . The second is the Sec-WebSocket-Accept header field.

The |Sec-WebSocket-Accept| header field indicates whether the server is willing to accept the connection or not. If present, this header field must include a hash of the client's nonce sent in |Sec-WebSocket-Key|. Any other value must not be interpreted as an acceptance of the connection by the server. These fields are checked by the WebSocket client for scripted pages. If the |Sec- WebSocket-Accept| value does not match the expected

value, if the header field is missing, or the connection will not be established if the HTTP status code is not 101, and WebSocket frames will not be sent.

V. WEBSOCKET

Web Socket uses single socket to push and pull information between the browser and the server in fullduplex communication this will not only avoid the problem of comet's connection and portability, but also be able to achieve higher efficiency than AJAX long polling. At present, the HTML5 WebSocket is the principal mechanism for promoting the web full-duplex real-time communication. It uses single socket to push &

pull information between the browser and server in full duplex communication.

WebSocket connection establishment model, WebSocket protocol is essentially a TCP. To establish a Web Socket connection, the client and server upgrade from the HTTP protocol to the Web Socket protocol during their initial handshake [8], once established, Web Socket data frames can be sent back and forth between the client and the server in full-duplex mode, and this connection will continue to exist until the client side or server side close the connection initiatively. The Web Socket API defines mainly four callback methods:

onopen, onmessage, onclose and

onerror to deal with event trigger during the WebSoceket connection. It is very suitable for real-time web applications.

VI. EXPECTED RESULT

The user can access the video very fast. The time required for extracting the video is less. To play the

(4)

International Journal of Recent Advances in Engineering & Technology (IJRAET)

________________________________________________________________________

video, every time it is not necessary to download the flash player.

VII. CONLUSION

Web Socket uses single socket to push and pull information between the browser and the server. In full duplex communication, this will not only avoid the problem of comet's connection and portability, but also be able to achieve higher efficiency . At present, the HTML5 WebSocket is the principal mechanism for promoting the web full-duplex real-time communication. In this paper we proposed the web socket protocol for video streaming over full duplex network. It also solves the problem of browser incompatibility.

REFERENCES

[1] Carlos Augusto Cunha*, Luis Moura e Silva ,“SHStream :self-healing Framework for HTTP Video-Streaming” ,IEEE/ACM international symposium on Cluster ,Cloud, and Grid Computing ,512 2013 13^th

[2] Jong-Ho Lee and Oh-Soon shin,”Full-Duplex Relay Based on Distributed Beam forming in

Multiuser MIMO Systems”,IEEE

TRANSACTIONS ON VEHICULAR

TECHNOLGY ,VOL,62,NO 4, MAY 2013 [3] Andrew Wessels, Mike Purvis, Jahrain Jackson,

Syed Rehman,”Remote Data Visualization through Websockets” 2011 Eighth International Conference on Information Technology: New Genrations,1050

[4] Lin Li,Xiping Zhang,”Research On The Integration of RTCWeb Technology with IP Multimedia Subsystem” 5th International Congress on Image and Signal Processing (CISP 2012),1158

[5] Sachin Agrwal,” Real-time Web Application Roadblock: Performance Penalty of HTML Sockets”. IEEE ICC 2012 - Communication QoS, Reliability and Modeling Symposium 1225 [6] Tetsushi Watanabe ,Shinsuke Kobashi,”A Low

Latency and Intuitive Control Video Streaming System”,The 1^st IEEE Global Conference on Consumer Electronics 2012,1.

[7] Guolei Zhu, Fang Zang, Wei Zhu, Yayu Zheng,”HTML5 Based Media player for Real-

Time Video Surveillance” 2012 5^th International Congress on Image and Signal Processing(CISP 2012),245.

[8] JIANG Feng-Yan, DUAN Hui-Chuan

“Application Research of Web Socket Technology on Web Tree Component”. 2012

INTERNATIONAL SYMPOSIUM ON

INFORMATION TECHNOLGY IN MEDICINE AND EDUCATION,889.

[9] Xing Yan, Lei Yang, Shanzhen Lan, Xiaolong Tong,”Application of HTML5 Multimedia”.

2012 International Conference on Computer Science and Information Processing (CSIP),871.

[10] Chen Li-Li, LIU Zheng-Long ,”Design of Rich Client Web Architecture Based on HTML5”

2012 Fourth International Conference on Computational and Information Sciences,1009.

[11] T. Stockhammer, “Dynamic adaptive streaming over http –: standards and design principles,” in Proceedings of the second annual ACM conference on Multimedia systems, ser.

MMSys ’11. New York, NY, USA: ACM, 2011, pp. 133–144.

[12] I. Sodagar, “The mpeg-dash standard for multimedia streaming over the internet,”

Multimedia, IEEE, vol. 18, no. 4, pp. 62 –67, April 2011. T. Riihonen, S. Werner, and R.

Wichman, “Mitigation of loopback self- interference in full-duplex MIMO relays,” IEEE Trans. Signal Process.,vol. 59, no. 12, pp. 5983–

5993, Dec. 2011.

[13] Victoria Pimentel , Bradford G. Nickerson.

“Communicating and Displaying Real-Time Data with WebSocket “,IEEE computer Society,July/August 2012,45

[14] MinSeok JANG*, Hyeontak OH*, Jinhong YANG*, Jun Kyun CHor *, Keuneun KIM **, Ilkwon CHO **,”Implementation of Continuous HTTP Live Streaming using Playback Position Request Mechanism in Heterogeneous Networks”ICACT 2103,990 ,Jan 27-30,2013 [15] E.Quacchio, G. Brono, M.Grangetto,”AN

HTML5 PLAYER FOR A GSTREAMER BASED MPEG DASH CLIENT ”

