TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

More documents

Recommendations

Info

As explained, the Delivery layer is media unaware but delivery technology aware. It provides transparent access to the delivery of content irrespective of the technologies used (IP, ATM...). The boundary between the Sync Layer and the Delivery Layer is referred to DMIF Application Interface (DAI). It offers content location independent procedures for establishing MPEG-4 sessions and access to transport channels. Also it provides default DMIF signaling protocol which corresponding to the DMIF Network Interface (DNI). 6.1.2.1 MPEG-4 DMIF Architecture DMIF framework covers three major technologies: (1) interactive network technology, (2) broadcast technology and (3) the disk technology. An application accesses data through the DAI irrespectively whether such data comes from a broadcast source, from local storage or from remote server. In all scenarios the Local Application only interacts through DAI primitives. Figure 6-4 clarifies the DMIF aim. Local DMIF for Broadcast Remote DMIF (emulated) Remote App. (emulated) Broadcast source Local App DMIF Filter Local DMIF for Local Files Remote DMIF (emulated) Remote App. (emulated) Local Storage Local DMIF for Remote srv Sig map Network DAI DNI Sig map Remote DMIF (Real) Remote App DNI DAI Figure 6-4: MPEG-4 DMIF architecture 6.1.2.2 DMIF Layer MPEG-4 DMIF allows each delivery technology to be used for its unique characteristics in a way transparent to application developers. Figure 6-5 shows the composition of DMIF stack in conjunction with an IP-based underlying networking environment. MPEG-4 Application DMIF Application Interface DMIF Network Interface }DMIF TCP/UDP IP Figure 6-5: DMIF stack protocols with IP networks DMIF contains functionality needed to establish sessions and connections between an application running at server side and an application running at client side over transport networks. In general, DMIF provides the following functionalities: 144
• It assign a value (network session Identifier) to one session. This identifier encodes a unique session instance for network application and for the management of real time, QoS sensitive streams. • It allows interoperation between the client and the server. • It hides the delivery technology details from the DMIF User. • It ensures interoperability between end-systems (in the control plane). 6.1.2.3 DAI: DMIF Application Interface The DMIF Application Interface (DAI) allows the development of applications to support delivery technologies, regardless of network topology. The DAI defines the functions offered by the DMIF layer, and comprised the following classes of primitives: • Service primitives, which deal with the Control Plane, and allow the management of service session (attach and detach). • Channel primitives, which deal with the control Plane, and allow the management of channels (add and delete). • Data primitives, which deal with the User Plane, and serve the purpose of transferring data through channels. 6.1.2.4 DNI: DMIF Network Interface The DMIF Network Interface (DNI) abstracts the signaling between DMIF peers irrespectively of the supported delivery technologies. The parameters conveyed through the DNI are then normatively mapped onto network dependent native signaling when possible otherwise they are carried opaque to the native signaling. The DMIF Network Interface includes the following classes of primitives: • Session primitives, which allow the management of sessions (setup and release) • Service primitives, which allow the management of services (attach and detach) • Transmux primitives, which allow the management of a transmux (setup, release and config) • Channel primitives, which allow the management of channels (add and delete) 6.1.2.5 DMIF Communication Model To hide the delivery technologies to the end-user, DMIF uses a set of primitives (DAI primitives and DNI primitives). Figure 6-6 shows the workflow of message and primitive exchanged between two MPEG-4 DMIF terminals for session establishment. 145
Page 1:
UNIVERSITÉ DE VERSAILLES SAINT-QUE
Page 4 and 5:
Résumé Nous constatons aujourd’
Page 6 and 7:
3 Related Work ....................
Page 8 and 9:
5.5.1.2 Simulation Results.........
Page 10 and 11:
List of Figures Figure 1-1: Structu
Page 12 and 13:
Figure 5-15: End-to-end packet tran
Page 14 and 15:
Acknowledgments The first person I
Page 16 and 17:
[11] Toufik Ahmed, Guillaume Burida
Page 18 and 19:
d’accès. Les interactions de QoS
Page 20 and 21:
Métrique MAX_DELAY PREF_MAX_DELAY
Page 22 and 23:
1.1.2 Proposition dun Protocole d'E
Page 24 and 25:
des paquets RTP. Reste toujours le
Page 26 and 27:
Nous pouvons distinguer trois possi
Page 28 and 29:
1.1.2.5.2 Multiplexage des Flux El
Page 30 and 31:
l’horloge est par défaut égale
Page 32 and 33:
La valeur R TCP représente le déb
Page 34 and 35:
Pour ces raisons, nous nous intére
Page 36 and 37:
Telles que illustrés par la Figure
Page 38 and 39:
3. DMIF2SIP vérifie si son propre
Page 40 and 41:
utilisée optionnellement pour loca
Page 42 and 43:
Chapter 2 2 Introduction 2.1 Motiva
Page 44 and 45:
conditions. Based on end-to-end fee
Page 46 and 47:
Chapter 3 3 Related Work Nowadays,
Page 48 and 49:
• multicasting: it takes the stre
Page 50 and 51:
expensive, fixed delivery and recep
Page 52 and 53:
3.1.6 Static vs. Dynamic Channels T
Page 54 and 55:
environment because they require a
Page 56 and 57:
H.261 is called video codec for aud
Page 58 and 59:
VideoScene (VS) VideoObject (VO) Vi
Page 60 and 61:
The emphasis of MPEG-7 will be the
Page 62 and 63:
Temporal scalability involves parti
Page 64 and 65:
multitude of streams. It can switch
Page 66 and 67:
increased linearly in the absence o
Page 68 and 69:
3.2.2.1 End-to-End Retransmission R
Page 70 and 71:
correctly received block. The missi
Page 72 and 73:
epresent user traffic. The delay ca
Page 74 and 75:
3.2.5 IP Signaling Protocols for Pa
Page 76 and 77:
two H.323 endpoints or between an e
Page 79 and 80:
Chapter 4 4 Adaptive Packet Video T
Page 81 and 82:
4.1.1 Video Classification Model Pr
Page 83 and 84:
attributes can refer to the QoS par
Page 85 and 86:
In RBF, 2 D = X − is the distance
Page 87 and 88:
Figure 4-6: Experiment testbed In t
Page 89 and 90:
190 180 170 End-to-end delay MPEG-4
Page 91 and 92:
Sync Layer. The SL-packetized strea
Page 93 and 94:
conveyed by MIME format parameters
Page 95 and 96:
the same value. This timing informa
Page 97 and 98:
4.2.2.1 Fragmentation We propose to
Page 99 and 100:
Timestamp: Indicates the sampling i
Page 101 and 102:
When G is used as generator matrix,
Page 103 and 104:
4.2.3 Performance Evaluation Intens
Page 105 and 106:
0.3 0.25 our proposal classical app
Page 107 and 108:
lost packet at the receiver. Conseq
Page 109 and 110: marking scheme. The server must be
Page 111 and 112: The video server adds audio-visual
Page 113 and 114: Marker (TR3CM) [131] to mark the ba
Page 115 and 116: VO1 VO2 AVO Scenario Audio BL EL1 E
Page 117 and 118: Throughput (Kbits) 3000 2500 2000 1
Page 119 and 120: Throughput (Kbits) 3000 2500 2000 1
Page 121 and 122: 4000 3500 3000 2500 2000 1500 1000
Page 123 and 124: 45 40 Original Quality Received Qua
Page 125 and 126: Chapter 5 5 A Dynamic Packet Video
Page 127 and 128: The TCM algorithm is based on a tok
Page 129 and 130: BEGIN Initialize the classification
Page 131 and 132: User Profile (Token Bucket) Traffic
Page 133 and 134: 5.3.3 QoS Management Algorithm Spec
Page 135 and 136: Figure 5-7: Hierarchical aggregatio
Page 137 and 138: • Filters: to put packets into cl
Page 139 and 140: mechanism associated with the Drop
Page 141 and 142: Figure 5-16: Packets loss with IP D
Page 143 and 144: 5.5.2.3 Experimental Results Figure
Page 145 and 146: 1 MPEG-4 Based Layer Stream -AF11 M
Page 147 and 148: 0.2 0.18 MPEG-4 Based Layer Stream
Page 149 and 150: By using our PBNM tool, we allocate
Page 151 and 152: Id Condition Indicator Action 1 Net
Page 153 and 154: The proposed marking algorithm bett
Page 155 and 156: Chapter 6 6 A SIP/MPEG-4 Multimedia
Page 157 and 158: performed by many ways like SLA (Se
Page 159: 6.1.1.4 SIP Communication Model SIP
Page 163 and 164: 6.2.1 SIP2DMIF Subsystem The SIP2DM
Page 165 and 166: Step 1: The MPEG-4 Terminal passes
Page 167 and 168: 1. Set the result C to the empty se
Page 169 and 170: TCP/UDP port, our implementation us
Page 171 and 172: Control & Data Plan Video Rate Cont
Page 173 and 174: characteristics and relevance of ea
Page 175 and 176: References [1] Kazaa Media Desktop
Page 177 and 178: [43] B. Schuster, “Fine granular
Page 179 and 180: [79] D. Bansal and H. Balakrishnan,
Page 181 and 182: [115] N. Laoutaris, I. Stavrakakis,
Page 183 and 184: [154] W. Almesberger, J. H. Salim,
Page 185 and 186: Appendix A A Appendix A: Overview o
Page 187 and 188: Media aware Delivery unaware ISO/IE
Page 189 and 190: A.3.3 Scene Description Streams Sce
Page 191: This appendix presents structure ex
show all

TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

Create successful ePaper yourself

Delete template?

Save as template?