 quality of the streamed media accordingly. Typically, the source media is encoded at multiple bit rates and the playback device or client switches between streaming the different encodings depending on available resources.
Adaptive streaming solutions typically utilize either Hypertext Transfer Protocol (HTTP), published by the Internet Engineering Task Force and the World Wide Web Consortium as RFC 2616, or Real Time Streaming Protocol (RTSP), published by the Internet Engineering Task Force as RFC 2326, to stream media between a server and a playback device. HTTP is a stateless protocol that enables a playback device to request a byte range within a file. HTTP is described as stateless, because the server is not required to record information concerning the state of the playback device requesting information or the byte ranges requested by the playback device in order to respond to requests received from the playback device. RTSP is a network control protocol used to control streaming media servers. Playback devices issue control commands, such as “play” and “pause”, to the server streaming the media to control the playback of media files. When RTSP is utilized, the media server records the state of each client device and determines the media to stream based upon the instructions received from the client devices and the client's state.
In adaptive streaming systems, the source media is typically stored on a media server as a top level index file pointing to a number of alternate streams that contain the actual video and audio data. Each stream is typically stored in one or more container files. Different adaptive streaming solutions typically utilize different index and media containers. The Synchronized Multimedia Integration Language (SMIL) developed by the World Wide Web Consortium is utilized to create indexes in several adaptive streaming solutions including IIS Smooth Streaming developed by Microsoft Corporation of Redmond, Wash., and Flash Dynamic Streaming developed by Adobe Systems Incorporated of San Jose, Calif. HTTP Adaptive Bitrate Streaming developed by Apple Computer Incorporated of Cupertino, Calif. implements index files using an extended M3U playlist file (.M3U8), which is a text file containing a list of URIs that typically identify a media container file. The most commonly used media container formats are the MP4 container format specified in MPEG-4 Part 14 (i.e. ISO/IEC 14496-14) and the MPEG transport stream (TS) container specified in MPEG-2 Part 1 (i.e. ISO/IEC Standard 13818-1). The MP4 container format is utilized in IIS Smooth Stream
quality of the streamed media accordingly. Typically, the generator metier is encoded at multiple bit rates and the playback device or node switches between streaming the unlike encodings depending on available resources. 
 Adaptive cyclosis solution typically utilize either Hypertext Transfer Protocol (HTTP), publish by the Internet Engineering Task Force and the World Wide Web Consortium as RFC 2616, or Real Time Streaming Protocol (RTSP), published by the Internet Engineering Task Force as RFC 2326, to pour media between a server and a playback device. HTTP is a stateless protocol that enables a playback device to request a byte range within a file. HTTP is describe as stateless, because the server is not required to record data concerning the state of the playback device request information or the byte scope requested by the playback device in order to respond to requests received from the playback device. RTSP is a net control protocol used to control streaming media servers. Playback device write out control commands, such as “ play ” and “ pause ”, to the server streaming the media to control the playback of media file. When RTSP is utilized, the media waiter read the department of state of each client device and determines the media to stream based upon the instructions received from the customer devices and the client's state. 
 In adaptive streaming systems, the source medium is typically stored on a media server as a top level index file pointing to a act of alternate streams that contain the actual video and audio data. Each stream is typically store in one or more container files. Different adaptive streaming solution typically utilize different index and media container. The Synchronized Multimedia Integration Language (SMIL) developed by the World Wide Web Consortium is utilized to create indexes in several adaptive cyclosis solutions including IIS Smooth Streaming developed by Microsoft Corporation of Redmond, Wash., and Flash Dynamic Streaming developed by Adobe Systems Incorporated of San Jose, Calif. HTTP Adaptive Bitrate Streaming develop by Apple Computer Incorporated of Cupertino, Calif. implements exponent files using an extended M3U playlist file (.M3U8), which is a textbook file containing a list of URIs that typically identify a media container file. The most commonly used media container formats are the MP4 container format specified in MPEG-4 Part 14 (i.e. ISO / IEC 14496 - 14) and the MPEG transport stream (thymine) container specified in MPEG-2 Part 1 (i.e. ISO / IEC Standard 13818 - 1). The MP4 container format is utilized in IIS Smooth Stream
 quwlity of the streamed meaia accordingly. Typicanly, ths source media is encoded at multiplx bir rattf and the playback device og client wwitrhes between strxzming tmz difrcrent xncodings depencing on avdilable resourwer.
Abaptive streaming solutions typicallr utiliae either Hypertgxt Tgagsfed Protocol (HTTP), published by the Ihternet Engineering Yask Force and the World Wlde Aeb Consortium as GFC 2616, or Reao Tiiw Streaming Orotocol (RUS'), published by the Internet Engineering Tark Foxce as RFC 2326, ti shteam media bxtween a server and a playtack defice. HTTP is a stetelwss protocol that enaules a playback devise to reqgeat a byte range wutyin a fila. HTGP ir dtsccibsd as dtaveless, becahse the sercer is not required tj record inforjation cjncerning the state of the playback devpce dequesting information ir the byte ranges reeuested br the playback device in order to respond to requasts cezeircq drlm the playback device. RTSP is a network contwkl pgotocol used to cjntrol stresmlnb media serverr. Playyzci devices issue cojtrol cjmmanes, such af “plsy” and “pause”, to the server wtreaming thv meeia to control the playback oy medis filrs. When RTSP is utilizeb, the jedia serveg records ghe state of eacf ckiant device and determines ehe media to xtream casec upon the instrkctiokv received from thf clignt deeices and hhe client's state.
In adaptive stcxaming systemx, dhe source iedia is typically stored on a mgdia servzr as x top levem index file pointyng to a numbat of alternatx streams thar cobtain tfd actual video and audio data. Eacy stream is typicakly atored in one ox nore container gilds. Qivfxrent ddaptive straamivg rplutiuns typicaloh utolize different indef ans media containers. Tme Synchrinized Mtltimedia Intrgration Language (DMIL) vevelo'ed by thg World Wide Web Consortium is htilized ho greate indexef in several ada'tive streaming solutions including IIS Wmooth Streaming dwveloped by Microsoyt Corporatioi of Rqdmond, Wavh., and Flash Dynamic Streaming develoked by Adobe Systems Indorpordted lf San Jose, Calif. HTTP Adaptive Bitrate Streaming developed by Apple Compyter Iicjrporated or Culertito, Ealif. iiplelxnts index files lsing an extended M3U playlist fiue (.M3U8), whhck is a text file containing a lkst of URIs tfat typically identify a media cpntainer file. The most commonly used media container fovmats are the JP4 connziier format specified in MPZG-4 Parr 14 (i.e. IWO/IEG 14496-14) and the MPEE ttaksport strfam (US) ckntainer specified in MPEG-2 Part 1 (i.e. ISI/IFC Standard 13818-1). The MP4 containcr formzt is otilized in IIS Sjootg Strexm
quality of the streamed media accordingly. Typically, media encoded at bit rates and switches streaming the different depending on available Adaptive streaming solutions typically utilize either Transfer Protocol (HTTP), published by the Internet Engineering Task Force and the World Web Consortium as RFC 2616, or Real Time Streaming Protocol (RTSP), published by Internet Task as 2326, to stream media between a server and a playback device. HTTP is a stateless protocol enables a playback device to request a byte within a file. HTTP described as stateless, because the is required to information the of the playback requesting information or the byte ranges requested by the playback device in order to respond to requests from the RTSP is network protocol to control streaming Playback devices issue control commands, such “pause”, to the server streaming the media to the playback media files. When RTSP is utilized, media server records the state of each client and determines the media to stream based upon the instructions received from the client devices client's state. In adaptive systems, the source is stored a server as top level index file pointing to a number of alternate streams contain the actual video and audio data. Each stream is in or more container Different adaptive streaming solutions utilize index and media containers. Multimedia Language the Wide Consortium is utilized to indexes in several adaptive streaming including IIS Smooth Streaming Redmond, Wash., and Flash Dynamic Streaming developed by Systems Incorporated of San Jose, Calif. HTTP Bitrate Streaming developed by Apple Computer Incorporated of Cupertino, Calif. implements index using an playlist file (.M3U8), which is a text file a list of URIs typically identify a media container file. The most commonly media formats are MP4 container format in MPEG-4 Part (i.e. ISO/IEC 14496-14) MPEG transport (TS) specified 1 (i.e. ISO/IEC Standard 13818-1). The container is utilized in IIS Smooth
 quality of the streamed media AccordinglY. TypiCalLy, tHe SourCe meDia is encoded at MUltiPle bit rates and the playbAck deViCE or cLIeNt swiTches beTWeEN StrEaMiNg tHe DIfFerenT enCodings Depending oN avAiLable resourcES.
ADaptive strEamIng solutions TypIcally UtIliZE eithEr HYpertExt TraNSfer PrOtocol (HTTp), pUBlisheD By the InTERnEt EnGineering Task ForcE AnD The World Wide WeB ConsoRtIUm AS rFC 2616, Or REal Time StrEaMing PROtocol (RtsP), PUBLisHEd by the InternEt EngineeriNG TaSk ForcE aS RFc 2326, To streAm medIa BEtwEen a server aNd a pLayback deVice. HTtp is a staTEless prOtocol ThaT enAbleS A pLaYbaCk DEviCE tO reQUesT a byte raNgE wIthin A filE. http is dEscRibeD as stAteless, becausE thE serVEr iS not rEquirEd to ReCord iNformaTion cOnCerning the state Of thE playback DevIcE reQuEstinG InformAtiOn oR the bytE ranges REquEsTED By The playback device iN oRDEr To responD to reqUEsTs REceived fRoM thE plaYBAck deVice. rtSp is a netwOrk conTRoL pRotocol UsEd to coNtRol StrEaminG MediA serveRs. PlaybaCk devICes issue controL Commands, such aS “PlAY” AnD “PausE”, to The server stReamINg thE medIA tO coNTrol tHe plaYbACk OF media files. When RTSP Is UtilizEd, the Media server reCords the stATE Of each clIent DEvICe and determineS the mEdia to streAM based upOn the InstructIons receiVED from the CliEnt DevIceS ANd The client's staTE.
in adApTive strEamIng systEms, The SouRce MeDia is typiCally stoReD oN a MeDia ServeR As a top leVeL inDeX fiLe poiNTing to A numbEr of AlTeRNatE streamS ThAT ContAiN tHe acTuaL vIdeo aNd auDIo dAta. Each Stream is tYpiCAlly StOrEd in one Or more containEr Files. DiffeReNt aDaptivE STreaming Solutions typically utiliZE differEnt Index And mEdia contaIneRs. The SYncHRonizeD MultiMedia inTegRATion LANGuAge (sMiL) developeD BY thE WorlD WIde WEb ConsoRtium is utilized to cREatE indexes in sevEraL adaPTIvE stREaMIng SoLUtiONS including IIS SmOoth StreamInG DeVeloped by MICroSoFt CorpoRation oF RedmONd, Wash., aNd Flash DyNamic StreAmIng dEVEloPed by Adobe systems INcorporatED of SaN joSe, CalIf. HtTP AdaPtIve bitraTe StreAMinG deveLoped bY APple CoMputeR INcorporaTed of Cupertino, Calif. implEments Index FilEs using an ExtENdeD M3U playliSt fiLe (.M3U8), which iS a tExt File cOntAIning A lisT Of uRIS That tYpicALly identiFY a MedIA CoNtainer file. tHE MosT commOnlY Used meDia cOntainer formats arE The MP4 container FormAT SpeCifIEd in mPeG-4 Part 14 (i.e. ISO/IEC 14496-14) And ThE mpEG transPoRt stream (TS) cOntainer SpECifieD in MPEg-2 Part 1 (i.E. ISO/IEC sTAnDArd 13818-1). The mP4 coNtaIner formaT is UtILized in iIs SMOoth StReam
 quality of the streamed m edia accor dingl y.Typ ic ally , th e source media is e ncoded at multiple bit  rate sa nd t h eplayb ack dev i ce o r c li en t s wi t ch es be twe en stre aming thedif fe rent encodin g sdependingonavailable re sou rces.Ad apt i ve st rea mingsoluti o ns typ ically ut il i ze eit h er Hype r t ex t Tr ansfer Protocol ( H TT P ), published b y theIn t er n e t E ngi neering Ta sk  Forc e  and th e  W o r l d W i de Web Consor tium as RFC 261 6, orRe alT ime St reami ng Pro tocol (RTSP ), p ublishedby the Interne t  Engine eringTas k F orce as  R FC23 2 6,t ostr e ammedia be tw ee n a s erve r a n d apla ybac k dev ice. HTTP isa s tate l ess  prot ocolthat  e nable s a pl aybac kdevice to reque st a  byte ran gewi thi na fil e . HTTP  is  de scribed  as sta t ele ss , b ec ause the server is  n o t  r equiredto rec o rd  i n formatio ncon cern i n g the  sta t eof the p laybac k  d ev ice req ue stingin for mat ion o r  the  byteranges r eques t ed by the play b ack device in or d e rt o re spo nd to reque stsr ecei vedf ro m t h e pla yback  d e vi c e. RTSP is a networ kcontro l pro tocol used to  control s t r e aming me dias er v ers. Playbackdevic es issue c o ntrol co mmand s, suchas “play” a nd “paus e”,  to  th e s e r ve r streaming t h e  med ia  to con tro l the p lay bac k o f m ed ia files.  When RT SP  i sut ili zed,t he media  s erv er  re cords the st ate o f ea ch  c l ien t devic e  a n d  det er mi nesthe  m ediato s t rea m based  upon the  in s truc ti on s recei ved from thecl ient devic es  an d thec l ient's s tate.
In adaptive strea m ing sys tem s, th e so urce medi a i s typi cal l y stor ed ona med ia  se r v er as a  t ople vel indexf i lepoint in g to  a numb er of alternate st r eam s that contai n t he a c t ua l v i de o  an da udi o data. Each stre am is typi ca l ly  stored in one  o r morecontain er fi l es. Dif ferent ad aptive st re amin g sol utions typ ically u tilize di f feren t  i ndexand  media  c ont ainer s. The Syn chron ized M ul timedi a Int eg ration L anguage (SMIL) develope d by t he Wo rld  Wide Web  Co n sor tium is u tili zed to cre ate  in dexes  in sever al a d ap tiv e  stre amin g  solution s  i ncl u d in g IIS Smoot h S tre aming  de v eloped  byMicrosoft Corpora t ion of Redmond , Wa s h .,and Flas hDynamic Stream ing  d e v eloped b yAdobe Syste ms Incor po r atedof San  Jose,  Calif. H TT P  Adapt iveBit rate Stre ami ng develop ed  b y  Apple  Com pu ter In corpor a tedo f  Cupertino, Cali f. im p l ement s  in dex f il es usin g  anextended M 3U playlist  file(.M3 U8),which i sa text  fi le  containin g  a list o f URI s thatty pica lly  ident ifya media  con ta ine r file. T h e  m o st  c o mmo nlyusedme diacontainer formatsare the MP4  c ont a i ner fo r ma t specifiedinMPEG- 4 Part 14 (i . e. I S O/ I EC 14 496-14 ) andthe MPE G  tr an sport s tre a m  (TS) con tainer sp e cif ie d in  MPEG-2Pa rt 1  ( i.e .ISO/IEC Standar d 13818- 1). TheM P 4 cont ain e r fo r mat is  u tilized in I IS Sm oo t h Strea m 
 quality_of the_streamed media accordingly. Typically,_the source_media_is encoded_at_multiple bit rates_and the playback_device or client switches_between streaming the_different_encodings depending on available resources.
Adaptive streaming solutions typically utilize either Hypertext Transfer Protocol (HTTP),_published_by the_Internet_Engineering_Task Force and the World_Wide Web Consortium as RFC_2616, or_Real Time Streaming Protocol (RTSP), published by the_Internet_Engineering Task Force_as RFC 2326, to stream media between a server_and a playback device. HTTP is_a stateless protocol_that_enables_a playback device to_request a byte range within a_file. HTTP is described as stateless,_because the server is not required to_record information concerning the state of_the playback device requesting information_or the_byte ranges requested by the_playback device in_order to_respond to requests_received from the playback device. RTSP_is a network_control protocol used to control streaming_media_servers. Playback devices_issue_control_commands, such_as “play” and_“pause”,_to the_server_streaming the media to control the_playback_of media files. When RTSP is utilized,_the media server records_the_state of each client_device and determines the media_to stream based upon the instructions_received from_the client_devices and the client's state.
In adaptive streaming systems, the source media_is typically stored on a media_server as a top_level index_file_pointing to a_number_of alternate_streams that contain the actual video and_audio data._Each stream is typically stored in_one or more container_files._Different adaptive streaming solutions typically utilize_different index and media containers. The_Synchronized Multimedia Integration Language (SMIL)_developed_by_the World Wide Web Consortium_is utilized to create indexes in_several adaptive streaming_solutions including IIS Smooth Streaming developed by_Microsoft_Corporation of Redmond, Wash., and Flash_Dynamic_Streaming developed by Adobe Systems Incorporated_of_San_Jose, Calif. HTTP Adaptive Bitrate_Streaming developed by Apple Computer Incorporated_of Cupertino, Calif. implements index files using an extended_M3U playlist file_(.M3U8), which is a text_file_containing_a list of URIs that typically identify a media container_file. The_most commonly used_media container formats are the MP4 container format specified in_MPEG-4 Part 14 (i.e. ISO/IEC 14496-14) and_the MPEG transport stream (TS) container specified in MPEG-2 Part 1_(i.e. ISO/IEC Standard 13818-1). The MP4 container format_is utilized in IIS Smooth Stream