TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

More documents

Recommendations

Info

Step 4: After sending TRYING and RINGING message, User B (SIP terminal) sends 200 OK Message which notifies DMIF2SIP IWF that the connection has been done. If SIP User B supports the media capability advertised in the INVITE message send by DMIF2SIP IWF, it advertises the intersection of its own and User A’s capability in the 200 OK response. If SIP User B does not support the media capability advertised by DMIF2SIP IWF, it sends back a 400 Bad Request response with a 304 Warning h3eader field. Step 5: Upon receiving 200 OK response, the DMIF2SIP IWF sends a DS_SessionSetupConfirm message back to MPEG-4 DMIF Terminal and specifies the common set of capability advertised by 200 OK response. Step 6: The MPEG-4 DMIF terminal now is suitable to assign a local significance of the network session and must request a service within the network session. This task is performed by sending DS_ServiceAttachRequest message. Step 7: DMIF2SIP IWF receives DS_ServiceAttachRequest message which idenfies the services at the DMIF2SIP side. Step 8: The MPEG-4 DMIF Terminal request the establishment of a new media channel. Step 9: The DS_ChannelAddRequest message sends by MPEG-4 DMIF Terminal requests the establishment of new media channel. Step 10: DMIF2SIP IWF sends ACK message to SIP User B and it confirms that the two peers are capable of sending a receiving media. Step 11: Media channels are now done, media can flows between the MPEG-4 DMIF Terminal and SIP terminal. 6.2.3 SIP/DMIF Terminal Capability Matching The capability set of a terminal or a user agent refers to the set of algorithms for audio, video and data that it can support. It also conveys information about constraints in the selection of algorithms it may have. For example, due to limited bandwidth, a terminal may indicate that it can use either G.711 without video or G.723.1 with H.261 video [176]. Terminal Capability matching is required to check the ability of two peer and-systems to setup connections between them, and select the possible protocol stack supported. In case of DMIF and SIP, this stage is performing at session setup. SIP defines SDP as a protocol to describe SIP terminal capability whereas MPEG-4 DMIF uses DSM-CC as a format for capability description. When SIP UAC initiates the session with DMIF Terminal, it sends an INVITE request to DMIF. The capability descriptor is carried in this INVITE request throw SDP message. When DMIF Terminal initiates the session, it sends a DS_SessionSetupRequest to SIP terminal at this stage the capability descriptor is carried in the comptabilityDescriptor field part of DS_SessionSetupRequest message. The algorithm to find the common subset of capability descriptor maximal intersection of any two capability sets C1 and C2 is described in [177] and is given in what follows: 150
1. Set the result C to the empty set. 2. For each pair of capability descriptors (d1, d2), where d1 is from C1 and d2 is from C2, derive the permutations of alternative sets, s1 and s2. For each such permutation, where s1 is from d1 and s2 is from d2, intersect s1 and s2 (written as s=s1 ^ s2) and add s to C. 3. Remove duplicate entries from C. 6.2.4 SIP/DMIF Address Conversion Model 6.2.4.1 MPEG-4 DMIF Address Definition DMIF address is an URL that allows the DMIF layer at the originating DMIF to parse the network address in order to establish a session with the designated target DMIF and subsequently locate a service entity to enable it. Optionally the DMIF URL can be used to locate the source of an Elementary Stream in MPEG-4. The DMIF URL follows the generic syntax for new URL schemes defined in RFC1738 [182]. The DMIF URL on IP network consists of the following: xdmif://:@:/ or 6.2.4.2 SIP Address Format A SIP address can be either a SIP URL or any URI. The BNF of a SIP address is given below for reference: SIP-Address = (name-addr | addr-spec) name-addr = [display-name] “” addr-spec = SIP-URL SIP-URL = ”sip:” [ userinfo ”@” ] hostport url parameters [headers] userinfo = user [ ”:” password ] hostport = host [ ”:” port ] host = hostname | IPv4address url-parameters = *(”;” url-parameter) url-parameter = user-param | ... 6.2.4.3 Converting SIP Address to DMIF URL SIP address can be converted to DMIF URL facially. SIP-URL is copied verbatim to DMIF URL without any additional or supplement information. 151
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 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: Step 1: The MPEG-4 Terminal passes
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?