Flylib.com

Books Software

 
 
 

3.7 References


3.7 References

[298M] SMPTE 298M, Universal Labels for Unique Identification of Digital Data, 1997 www.smpte.org

[AAF-ASSOC] The AAF Association www.aafassociation.org.

[AAF-SDK] The AAF Software Development Kit aaf. sourceforge .net.

[ATSC] Advanced Television Systems Committee (ATSC) www.atsc.org

[FTP] File Transfer Protocol RFC959, 10.1985, IETF ftp://ftp.rfc-editor.org/in-notes/rfc959.txt

[HTTP1.0] Hypertext Transfer Protocol, HTTP/1.0, RFC1945, 05.1996, IETF ftp://ftp.rfc-editor.org/in-notes/rfc1945.txt

[HTTP1.1] Hypertext Transfer Protocol, HTTP/1.1, RFC2616, 06.1999, IETF ftp://ftp.rfc-editor.org/in-notes/rfc2616.txt

[HTTPS] HTTP over TLS (HTTPS), RFC2818, 05.2000, IETF ftp://ftp.rfc-editor.org/in-notes/rfc2818.txt

[ICMP] Internet Control Message Protocol, RFC 792, 09.1981, IETF ftp://ftp.rfc-editor.org/in-notes/rfc792.txt

[IPv4] Internet Protocol version 4, RFC 791, 09.1981, IETF ftp://ftp.rfc-editor.org/in-notes/rfc791.txt

[JavaTV] JavaTV API TechnicalOverview, Version 1.0 java.sun.com.

[MIME] Multipurpose Internet Mail Extensions (MIME) Part 1: RFC 2045 (updated by RFC 2184, RFC2231) ftp://ftp.rfc-editor.org/in-notes/rfc2045.txt; Part 2: RFC 2046 (updated by RFC 2646) ftp://ftp.rfc-editor.org/in-notes/rfc2046.txt; Part 3: RFC 2047 (updated by RFC 2184, RFC2231) ftp://ftp.rfc-editor.org/in-notes/rfc2047.txt; Part 4: RFC2048 (updated by RFC 3023) ftp://ftp.rfc-editor.org/in-notes/rfc2048.txt

[OCAP] CableLabs, Open Cable Architecture Platform (OCAP) www.cablelabs.com

[RTSP] Real-Time Streaming Protocol (RTSP), RFC 2326, 04.1998, IETF ftp://ftp.rfc-editor.org/in-notes/rfc2326.txt

[RTP] RTP: A Transport Protocol for Real-Time Applications, RFC 1889, 01.1996, IETF ftp://ftp.rfc-editor.org/in-notes/rfc1889.txt

[TCP] Transmission Control Protocol RFC 793, 09.1981, IETF ftp://ftp.rfc-editor.org/in-notes/rfc793.txt

[TFTP] Trivial-FTP Protocol ftp://ftp.rfc-editor.org/in-notes/rfc1350.txt

[TLS] The Transport Layer Security (TLS) Protocol version 1.0, RFC 2246,1999, IETF ftp://ftp.rfc-editor.org/in-notes/rfc2246.txt

[UDP] User Datagram Protocol, RFC 768, 08.1980, IETF ftp://ftp.rfc-editor.org/in-notes/rfc768.txt

[URI] Uniform Resource Identifiers (URI), RFC 2396, 8.1998, IETF ftp://ftp.rfc-editor.org/in-notes/rfc2396.txt

[VID-EDIT] Applied-Magic applied-magic.com

[VRML] ISO/IEC 14772-1, The Virtual Reality Modeling Language , 1997 www.w3.org/MarkUp/VRML/


Chapter 4. iTV Receivers

Chapter Objectives

  • Present technologies integrated in receivers

  • Describe architecture components

  • Present issues to be addressed

  • Discuss related standards

iTV receivers can be regarded as a meeting point of services delivered by multiple providers to which viewers can subscribe. The data from which these services are made is flowing into the receiver through both MPEG-based Digital TV broadcast(s) and IP-based return channel(s). Once iTV content data is received, numerous application layer technologies are used to process the data and launch the application.

This chapter is intended to serve as an introductory overview rather than a complete reference. It reviews expectations from receivers, some of the transport processing internals, and application processing internals. Hardware block diagrams are presented, as well as protocols and software stacks.