TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

More documents

Recommendations

Info

• Step 3: The PDP pushes to the edge router (PEP) an update of QoS Management decision. These steps allow configuring correctly different policies related to the same traffic. We introduce the following policy rule: let us On event: If then . A Profile is used to determine when a policy rule applies, for instance given pairs of source and destination addresses. An Action is a performed by that the policy enforcement entity to traffic of a given profile. Examples of actions are marking, accepting or rejecting traffic. Example of policy rules: • Rule 1: Mark DSCP value EF on all packets with source addresses from 193.51.25.1 to 193.51.25.255 priority 0 • Rule 2: Mark DSCP value AF11 on all packets with destination address 200.200.200.100 priority 1 Assume, an audio application has subscribed to a particular Diffserv class (an Expedited Forwarding Class). Audio traffic is defined by a particular profile. In this example Diffserv class simply mean that the audio stream will be marked with the appropriate DSCP (EF PHB here). The administrator of the Diffserv domain configures the environment to support the Gold, Silver, Bronze and other services. Such configuration can be done through a Bandwidth Broker. Supporting different classes of service in the core network requires putting in place classifiers, which cause the devices to examine the Diffserv mark on the packet and then treat the traffic accordingly. These configurations do not change frequently because they are not associated with specific application or traffic but with the network management. Since, the application is signed up for the service, edge devices are configured to mark application’s traffic with the appropriate PHB. Based on the <strong>IP</strong> address and/or the port number, the administrator can set a policy that marks traffic coming from that address with EF PHB. In order for customized traffic going to audio application (e.g. feedback traffic, RTCP, client commands) to receive a Diffserv treatment, policy must be deployed to the opposite edge device of a Diffserv domain. When the audio application starts sending the data, the edge router must ensure; (1) the data sent by the audio server does not exceed what the application has subscribe-to (SLA) and (2) marking conforming traffic (in profile traffic) with the appropriate PHB (EF PHB in our example). In case of receiving out of profile traffic, the edge router requests a decision from the PDP. Since the PDP knows the current network state - because it receives monitoring information from different monitors installed in the network, it decides a new policy rule, for example dropping, marking or accepting out of profile traffic. This decision varies according to current network state. 116
5.3.3 QoS Management Algorithm Specification We have configured 3 rules named Rule1, Rule2 and Rule3 to deal with video traffic. The Policy Server can choose one rule among the several depending on information sent periodically by the monitors. The monitoring information concerns essentially the bandwidth usage of each link in the network. The calculation of shaped value of the bandwidth using Exponentially Weighted Moving Average (EWMA) is presented later. Below in Figure 5-6 our algorithm, this uses the predefined policy rules to make a decision depending on bandwidth usage in the network. Initialization: Start Bandwidth Monitor Mi for each Router i to calculate the available bandwidth BW i Lambda ← 0.2 // Fixed value for historical data X ←50% link capacity // Initial value of EWMA Min_th← 40% link capacity Max_th← 70% link capacity Loop: BW ← max(BW 1 , BW 2 , …,BW i ) //EWMA available bandwidth X X← (1-lambda) * BW + lambda * X if X < Min_th then Rule1: Accept video traffic (in and out profile) Mark video traffic with Gold else if Min_th
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: User Profile (Token Bucket) Traffic
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 and 160: 6.1.1.4 SIP Communication Model SIP
Page 161 and 162: • It assign a value (network sess
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?