TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

More documents

Recommendations

Info

6.1.1.1 SIP Components SIP is composed essentially of four logical entities: user agent, registrar, proxy server and redirect server. Figure 6-2 depicts the interaction between these components 1. UAC (User Agent Client): it is the caller application that initiates and sends SIP requests. 2. UAS (User Agent Server): it receives and responds to SIP requests on behalf of clients, accepts, redirects or refuses calls. 3. SIP Terminal: it supports real-time, two-way communication with another SIP entity with both signaling and media handling. SIP terminal contains UA. 4. Proxy: it contacts one or more clients or next-hop servers and passes the call requests further. It contains UAC and UAS. 5. Redirect Server: it accepts SIP requests, maps the address into zero or more new IP addresses and returns those addresses to the client. 6. Location Server: it provides information about a caller's possible locations to redirect servers and proxy servers. Figure 6-2: SIP network architecture 6.1.1.2 IETF SDP : Session Description Protocol Session Description Protocol (SDP) [141] is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. The purpose of SDP is to convey information about media streams in multimedia sessions to allow the recipients of a session description to participate in the session. Therefore terminal capability is described by SDP. 6.1.1.3 IETF SAP: Session Announcement Protocol Session Announcement Protocol (SAP) [147] is used to assist the advertisement of multicast multimedia conferences and other multicast sessions, and to communicate the relevant session setup information to prospective participants. SAP announces a multicast session by multicasting packets periodically a well-known multicast group. The packets contain a description of the session using SDP. 142
6.1.1.4 SIP Communication Model SIP is based on the request-response paradigm. To initiate a session, the UAC sends a request (called an INVITE) addressed to the person the caller want to talk to. The addresses are similar to mailto URL (sip:user@server). The message is not send directly to the called party but rather to the proxy. Then, the proxy delivers the message to the called party. The called party sends a response, accepting or rejecting the invitation, which is forwarded back to the caller in reverse order like undelivered mail in Internet. Figure 6-3: A SIP call-setup signaling Bellow is an example of SIP scenario: 1 User A (a@caller.com) calls User B (b@example.com). User A send INVITE message to the proxy of example.com (INVITE sip: b@example.com), then the proxy of example.com tell User A, that it is trying to connect to b@example.com 2 The proxy locates in which terminal (PC) the User B is logged currently. This task is performed by a REGISTER message send by User B when he turned on his SIP user agent client. This would allow that User B is actually at foo.example.com (sip: b@foo.example.com). The bindings registered are periodically refreshed. 3 The proxy send INVITE message to UAC of User B (INVITE sip:b@foo.example.com), this later replies the proxy with ringing informational message. The proxy informs the caller that is ringing at User B. 4 When B accepts the invitation an acknowledgement message (ACK) is sent, and the session is established, Media can then flow between User A and User B. Others ways, User B can rejects the invitation. Figure 6-3 shows an example of a basic configuration between 2 UAs using SIP protocol. 6.1.2 ISO/IEC 14496-6 (MPEG-4 DMIF) MPEG-4 DMIF is the control plane of MPEG-4 Delivery layer that allows applications to transparently access and view multimedia streams whether the source of the stream is located on an interactive remote end-system, the stream is available on broadcast media or is located on stored media [144]. 143
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: performed by many ways like SLA (Se
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?