Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Contents
i
Technical Manual – Signaling & Protocols 2RTP and RTCP
The IP bearer voice services are transmitted based on UDP, which however doesn’t
take real-time service transmission into account (media stream synchronization, for
example), as it is designed to be dedicated to data stream transmission. So the
functionality of UDP needs to be expanded when real-time services are transferred
based on it. For that purpose, IETF defines a new protocol RTP (Real-time Transport
Protocol).
RTP provides real-time end-to-end data delivery services, such as interactive audio
and, including payload type identification, sequence numbering, time stamping and
delivery monitoring. RTP itself does not provide any mechanism to ensure timely
delivery or provide other quality-of-service guarantees, but relies on lower-layer
protocols to do so.
Real-time Transport Protocol (RTP): transports the information featured with real
time.
RTP Control Protocol (RTCP): monitors quality of service and the information
about members involving a transfer or a session.
RTP guarantees timely transmission and synchronization of audio and video; and
RCTP is used to monitor RTP and QoS. For details about the protocols, please refer
to related RFC documents. RTP does not address resource reservation and does not
guarantee quality-of-service for real-time services. The data transport is augmented
by RTCP to allow monitoring of the data delivery in a manner scalable to large
multicast networks, and to provide minimal control and identification functionality.
RTP/RTCP is designed to be independent from the underlying transport layer and
network layer.
1
Technical Manual – Signaling & Protocols 2RTP and RTCP
MRPU
Nb UP
RTP RTCP
UDP
IP
ETH
IP
Version 2 The field defines the version of RTP. The version defined
here is two.
2
Technical Manual – Signaling & Protocols 2RTP and RTCP
Extension (X) 1 If the extension bit is set to 1, the RTP header is followed
by exactly one header extension.
SSRC 32 The SSRC field identifies the RTP packet sender. This
identifier is chosen randomly, with the intent that no two
RTP packet senders within the same gateway will have
the same SSRC identifier. Although the probability of mul
tiple sources choosing the same identifier is low, all RTP
implementations must be prepared to detect and resolve
collisions. If a source changes its source transport addre
ss, it must also choose a new SSRC identifier to avoid b
eing interpreted as a looped source.
CSRC List 0-480 0 to 15 items, 32 bits each. The CSRC list identifies
CSRC in packets. The number of identifiers is given by
the CC field. At most 15 CSRC identifiers are defined
and are inserted by mixers, using the SSRC identifiers
RTCP defines several types of RCTP packets to carry a variety of control information
as shown in 2.3.2.
3
Technical Manual – Signaling & Protocols 2RTP and RTCP
RR (receiver report) Describe reception statistics from the gateways that are
receivers
Each RTCP packet begins with a fixed part similar to that of RTP data packets,
followed by structured elements that may be of variable length according to the
packet type but always end on a 32-bit boundary. The alignment requirement and a
length field in the fixed part make RTCP packets "stackable", that is, multiple RTCP
packets form a compound RTCP packet that is sent in a single packet of the lower
layer protocol, for example UDP. There is no explicit count of individual RTCP packets
in the compound packet since the lower layer protocols are expected to provide an
overall length to determine the end of the compound packet.
RTCP transmits RTP control packets based on the periodic transmission, using the
same distribution mechanism as the data packets. RTCP chiefly performs two functio
ns.
The primary function is to provide feedback on the quality of the data distribution.
The receiver diagnoses faults on transport lines and controls RTP packet
transfer according to the feedback information in RTCP packets. The feedback
function is accomplished through sending and receiving reports by RTCP.
RTCP carries a persistent identifier for a RTP source, which is called the
canonical name (CNAME). Since the RTP header may change if a conflict is disc
overed or a program is restarted, receivers require the CNAME to keep track of e
ach participant.
The interval between RTCP packets transmitted is varied randomly over the range
4
Technical Manual – Signaling & Protocols 2RTP and RTCP
[0.5, 1.5] times the calculated interval to avoid unintended synchronization of all
participants. The first RTCP packet sent after joining a session is also delayed by a ra
ndom variation of half the minimum RTCP interval in case the application is started at
multiple sites simultaneously.