| H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (rtsp)," http://www.ietf.org/rfc/rfc2326.txt, April 1998. |
....by equation (3) For simplicity, we suppose that the media objects are CBR (Constant Bit Rate) encoded. Note that with VBR (Variable Bit Rate) encoded media objects, the playback time of bu#ered data can be derived by another method (e.g. by using NPT (Normal Play Time) parameter in RTSP protocol [12]) Then the feedback timer is generated based on the playing time of bu#er data, as shown in equation (4) t pb i = 3) t fb i = K t pb i = K (4) where t pb i is playback time of bu#ered data, t fb i is feedback timer, D i is the amount of bu#ered data, and r pb i is the playback rate ....
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," IETF RFC 2326, April 1998.
.... is defined to be used either by applications that implement the SDP Offer Answer model [8] or by applications that use SDP to describe media and transport configurations in connection with such protocols as the Session Announcement Protocol (SAP) 15] or the Real Time Streaming Protocol (RTSP) [17]. There exist other potential signaling methods, which are not defined here. The XR blocks MAY be used without prior signaling. This is consistent with the rules governing other RTCP packet types, as described in [9] An example in which signaling would not be used is an application that ....
....of understanding the signaling. 5. 3 Usage Outside of Offer Answer SDP can be employed outside of the Offer Answer context, for instance for multimedia sessions that are announced through the Session Announcement Protocol (SAP) 15] or streamed through the Real Time Streaming Protocol (RTSP) [17]. The signaling model is simpler, as the sender does not negotiate parameters, but the functionality that is expected from specifying the rtcp xr attribute is the same as in Offer Answer. When a unilateral parameter is specified for the rtcp xr attribute associated with a media stream, the ....
H. Schulzrinne, R. Lanphier, and A. Rao, "Real time streaming protocol (RTSP)," RFC 2326, Internet Engineering Task Force, Apr. 1998.
.... is defined to be used either by applications that implement the SDP Offer Answer model [9] or by applications that use SDP to describe media and transport configurations in connection with such protocols as the Session Announcement Protocol (SAP) 15] or the Real Time Streaming Protocol (RTSP) [16]. There exist other potential signaling methods, which are not defined here. The XR blocks MAY be used without prior signaling. This is consistent with the rules governing other RTCP packet types, as described in [10] An example in which signaling would not be used is an application that ....
....of understanding the signaling. 5. 3 Usage Outside of Offer Answer SDP can be employed outside of the Offer Answer context, for instance for multimedia sessions that are announced through the Session Announcement Protocol (SAP) 15] or streamed through the Real Time Streaming Protocol (RTSP) [16]. The signaling model is simpler, as the sender does not negotiate parameters, but the functionality that is expected from specifying the rtcp xr attribute is the same as in Offer Answer. When a unilateral parameter is specified for the rtcp xr attribute associated with a media stream, the ....
H. Schulzrinne, R. Lanphier, and A. Rao, "Real time streaming protocol (RTSP)," RFC 2326, Internet Engineering Task Force, Apr. 1998.
....trip time. This information can be used by the sources to adjust their data rate. Other information such as email address, name and phone number are included in the RTCP packets, which allows all users to know the identities of the other users for that session. Real Time Streaming Protocol (RTSP) [36] is an out of band control protocol that allows the media player to control the transmission of the media stream including functions like pause resume, repositioning playback etc. The use of the RTP protocol above UDP provides for additional functionality required for reordering and time stamping ....
H. Schulzrinne, A. Rao and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC2326, April 1998.
....order to compute some quality of service parameters (3) This task is repeated for all available servers. It is advised to use the same protocols for the measurement which will be used for the real transmission. Typically, the streaming is initiated using the real time streaming protocol (RTSP, [7]) The data transfer itself is based on the real time transport protocol (RTP, 6] The advantage of RTP is the inclusion of elements such a sequence number and a timestamp in its header definition which can be used for the measurement and the analysis. The proposed quality of service ....
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP)," RFC 2326, IETF, April 1998.
....cache space occupied by the cached object layers is given by [ M;NIO ] 7 NIO a M;b NIO : 1) C. Stream Delivery The client directs its request for a quality stream of a video to its proxy server (for instance by using the Real Time Streaming Protocol (RTSP) [21]) If all the requested layers are cached in the proxy ( V Mdc ) the requested layers are streamed from the proxy over the local access network to the client. If layers are missing in the proxy V Mfe B , the proxy attempts to establish a connection to the appropriate origin server for the ....
H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force,, Apr. 1998.
....[5] based on control and transport IETF protocols, such as Real Time Streaming Protocol (RTSP) Real Time Transport Protocol (RTP) and Session Description Protocol (SDP) as fig. 1 shows. RTSP is an application level client server protocol, used to control the delivery of real time streaming data [6]. Both RTP and its related control protocol called Real time Transport Control Protocol (RTCP) convey media data flows over User Datagram Protocol (UDP) 7] RTP carries data with real time requirements while RTCP conveys information of the participants and monitors the quality of the RTP ....
....terminal and the streaming server. By means of RTSP messages, information about the encoding of the media and the corresponding UDP port number is exchanged. The SDP message [10] describes the streaming media the UE is about to receive. It should be noted that RTSP specification defined by IETF [6] does not mandate the use of the DESCRIBE method for this media initialization phase. However, in order to function properly, any RTSP based system must receive the description of the media one way or other. The 3GPP standard, defining the protocols and codecs for the transparent end to end PS ....
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)", IETF RFC 2326, 1998
....and reliable way well before the synchronous video data references it. In 1P environments for example, the Session Description Protocol (SDP) 23] can be used to define parameter sets that are conveyed reliably using Session Initiation Protocol (SIP) 22] or Real Time Streaming Protocol (RTSP) [26]. No redundancy coding techniques for headers are necessary, because there are no headers above the slice header due to the Parameter Set concept. The standardization process of the RTP payload specification for JVT [26] is still an ongoing process. However, the draft RTP payload specification is ....
....Session Initiation Protocol (SIP) 22] or Real Time Streaming Protocol (RTSP) 26] No redundancy coding techniques for headers are necessary, because there are no headers above the slice header due to the Parameter Set concept. The standardization process of the RTP payload specification for JVT [26] is still an ongoing process. However, the draft RTP payload specification is aligned to the goal of simple syntax specification and expects that NALUs are transmitted directly as the RTP payload except for the additional concept of aggregation packets. For packet switched real time services, the ....
[Article contains additional citation context not shown here]
A. Rao and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, Apr. 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Lanphier, R. and A. Rao, "Real time streaming protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, R. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
....RTP payload type values and the payload formats they represent for formats that do not have a predefined payload type value. Examples of such protocols include the Session Initiation Protocol (SIP) RFC 3261 [13] H. 323 [14] and applications using SDP (RFC 2327 [15] such as RTSP (RFC 2326 [16]) For simple applications, electronic mail or a conference database may also be used. The specification of such protocols and mechanisms is outside the scope of this document. 4 Byte Order, Alignment, and Time Format All integer fields are carried in network byte order, that is, most ....
.... sys utsname.h uname( #include global.h from RFC 1321 #include md5.h from RFC 1321 #define MD CTX MD5 CTX #define MDInit MD5Init #define MDUpdate MD5Update #define MDFinal MD5Final static u long md 32(char string, int length) MD CTX context; union char c[16]; u long x[4] digest; u long r; int i; MDInit ( context) MDUpdate ( context, string, length) MDFinal ( unsigned char ) digest, context) r = 0; for (i = 0; i 3; i ) r = digest.x[i] return r; md 32 Return random unsigned 32 bit quantity. Use type ....
Schulzrinne, H., A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," RFC 2326, April 1998.
....layer as well as the sampling rate and channel count are indicated in the payload. The RTP timestamp clock rate is always 90000, independent of the sampling rate. MPEG 1 audio field field name bits field field name bits 1 LARc[0] 6 39 xmc[22] 3 2 LARc[1] 6 40 xmc[23] 3 3 LARc[2] 5 41 xmc[24] 3 4 LARc[3] 5 42 xmc[25] 3 5 LARc[4] 4 43 Nc[2] 7 6 LARc[5] 4 44 bc[2] 2 7 LARc[6] 3 45 Mc[2] 2 8 LARc[7] 3 46 xmaxc[2] 6 9 Nc[0] 7 47 xmc[26] 3 10 bc[0] 2 48 xmc[27] 3 11 Mc[0] 2 49 xmc[28] 3 12 xmaxc[0] 6 50 xmc[29] 3 13 xmc[0] 3 51 xmc[30] 3 14 xmc[1] 3 52 xmc[31] 3 15 xmc[2] 3 53 ....
....7 RTP over TCP and Similar Byte Stream Protocols Under special circumstances, it may be necessary to carry RTP in protocols o#ering a byte stream abstraction, such as TCP, possibly multiplexed with other data. The application must define its own method of delineating RTP and RTCP packets (RTSP [24] provides an example of such an encapsulation specification. PT encoding media type clock rate channels name (Hz) 0 PCMU A 8000 1 1 reserved A 2 reserved A 3 GSM A 8000 1 4 G723 A 8000 1 5 DVI4 A 8000 1 6 DVI4 A 16000 1 7 LPC A 8000 1 8 PCMA A 8000 1 9 G722 A 8000 1 10 L16 A 44100 2 ....
Schulzrinne, H., A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (rtsp)," http://www.ietf.org/rfc/rfc2326.txt, April 1998.
No context found.
Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," IETF RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier: "Real Time Streaming Protocol (RTSP)", April, 1998, http://www.ietf.org/rfc/rfc2326.txt
No context found.
Schulzrinne H., Rao A., and Lanphier R. "Real Time Streaming Protocol (RTSP)". IETF RFC 2326, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," RFC 2326, IETF, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP)", IETF RFC 2326, 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, IETF, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, IETF, Apr. 1998.
No context found.
Schulzrinne H.; A. Rao; and R. Lanphier. 1998. "Real Time Streaming Protocol (RTSP)." IETF RFC 2326, (Apr).
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," IETF, RFC 2326, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (rtsp)," http://www.ietf.org/rfc/rfc2326.txt, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," Internet Request for Comments 2326, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier. Real time streaming protocol: RTSP. RFC 2326, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, RFC 2326 "Real Time Streaming Protocol (RTSP)", http://www.ietf.org/RFC/RFC2326.txt, April 1998
No context found.
Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, IETF, April 1998
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne et al., "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier. Real time streaming protocol: RTSP. RFC 2326, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, R. Lanphier, "Real Time Streaming Protocol (RTSP) ", IETF RFC 2326, Apr. 1998.
No context found.
Schulzrinne, H., Rao, A. and R. Lanphier: "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real time streaming protocol (RTSP)," Request for Comments (Proposed Standard) 2326, Internet Engineering Task Force,, Apr. 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," IETF RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," Tech. Rep., April 1998, RFC 2326.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)", RFC 2326, April 1998.
No context found.
H. Schulzrinne, A. Rao, and R. Lanphier, "Real Time Streaming Protocol (RTSP)," Tech. Rep., April 1998, RFC 2326.
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC