| OpenCable Set-top Box Architecture for Multimedia Delivery - Part II |
| The following article, written by Mukta L. Kar, Ph.D., a senior member of CableLabs technical staff, presents part II of an overview of digital set-top box architecture as it relates to an interoperable cable system design. Please see part I in Specs News & Technology from CableLabs, Volume 11, No. 1, January 2000. |
| Network Architecture The total coaxial cable spectrum is close to 1 GHz; however, most cable systems use less than 1GHz. Cable systems were built with different capacities54MHz350MHz; 54MHz450MHz; 54MHz550MHz; and 54MHz750MHzbased upon the need for channel capacity in different service areas. More recently some systems have been built with a capacity of up to 860 MHz. Traditionally the spectrum above 54 MHz has been chopped into a number of 6-MHz channels, each delivering one NTSC analog TV signal. A few years ago, the cable industry decided to add digital technology to their systems. To preserve existing analog services without interruption, a majority of the cable systems decided to use the spectrum above the current usage of 550 MHz750 MHz for the delivery of digital services. Additionally, one 6-MHz channel (traditionally known as the out-of-band (OOB) channel) was reserved for forward signaling purposes, such as delivering conditional access (CA) and management messages, interactive program guides (IPG), and other private data to set-top boxes (STBs). Compared to other broadcasting systems, the hybrid fiber/coaxial (HFC) cable network is much less susceptible to atmospheric noise and provides a better signal-to-noise ratio (SNR) at the receiving end. To take advantage of this, the cable industry selected a higher-order modulation system, quadrature amplitude modulation (QAM), as its digital modulation system; QAM provides larger digital bandwidth compared to 8-vestigial sideband (VSB) and quarternine phase shift keying (QPSK) used in terrestrial and satellite broadcasting systems, respectively. For example, 64-QAM modulation on a 6-MHz channel provides a digital bandwidth of 27 Mbps, whereas QPSK provides about 10 Mbps, and 8 VSB about 19.39 Mbps. However, for more robust transmission, QPSK modulation has been adopted for the OOB channel. Because signaling channels are different from service channels, STBs need two tunersone for tuning service channels and the other for the OOB channel. The cable industry made a decision to use a smaller digital bandwidth (1.5 Mbps-3.0 Mbps) for the OOB channel for simpler and less expensive implementation of OOB channel data demodulation and decoding in the STB. In order to support interactive program guides and other interactive services, upstream channels are a necessity; it was decided that the 0 MHz50 MHz portion of the cable spectrum should be used for upstream channels. OpenCable network architecture and terminal philosophy are based on the following: q Producing high-quality products q Meeting regulatory requirements q Competing effectively in retail markets q "Maximizing compatibility" q "Co-existing" with legacy terminals To promote compatibility with current implementations, most of the existing network architecture has been adopted, and enhancements have been added wherever necessary to support future extensibility. The spectrum allocation to support the OpenCable architecture is: q Forward application transport (FAT) channels, which carry MPEG-2 programs q Existing analog channels q Forward data channels (FDC) q Reverse data channels (RDC) FDC and RDC also are known as OOB channels, and frequency bandwidth for the delivery of analog and digital signals is 54 MHz to 860 MHz. One channel, in the 70 MHz130 MHz range, should be used for the OOB forward channel (OOB FDC); the OOB RDC channel should be in the 5 MHz42 MHz range. In existing architecture, most cable systems use the frequency bandwidth of 54 MHz550 MHz for the delivery of analog television programs, and 550 MHz750 MHz for digital signals. The spectrum allocated for separate delivery of analog signals will be reduced over time as analog channels are replaced by digital channels. One-way (uni-directional) and Two-way (bi-directional) NetworksMost cable systems have been built as uni-directional networks to deliver premium analog television content. Delivery of digital services, such as pay-per-view (PPV) and high-speed data services (Internet), requires two-way capability. A large number of systems have been upgraded to two-way networks. Still, a significant number of systems are one-way and are awaiting upgrades. If a cable operator wishes to provide two-way interactive services before network upgrades have been completed to fully support the OpenCable two-way network, a vendor-specific, hybrid approach, using the existing one-way network with a supplemental telephone return channel, may be used. Figure 3 shows a typical OpenCable STB architecture. The functional subsystems, excluding the blocks in dashed lines, may be used for delivery of one-way analog and digital signals. The 6-MHz tuner will tune any 6-MHz physical channel (carrying analog or digital signals). If the channel carries an analog signal, the NTSC demodulator will demodulate to the NTSC baseband. The NTSC baseband will then be input to a multimedia processor subsystem, where it will be modulated on top of a channel 3/4 RF carrier and output to a coaxial connector.
The 64/256 QAM demodulator in a digital channel will demodulate the channel to a digital baseband (27 Mbps for 64 QAM and 38.4 Mbps for 256 QAM). This digital baseband is a multiplex of programs, and each program in the multiplex can be encrypted or unencrypted. The multiplex will be passed on to the point-of-deployment (POD) security module. For a program in the clear, the POD does nothing to the multiplex and passes on to the demultiplex subsystem of the host. If the host-requested program is encrypted, the POD first checks with its access control subsystem, to verify that the host is authorized by the CA system for this content. If the host has the authorization, the POD picks the appropriate ECM (decryption key) from the inband multiplex and decrypts the selected multiplex program and passes the entire multiplex on to the demux (demultiplex) subsystem of the host. Before transporting across the POD-host interface, the unencrypted program will be re-encrypted for copy protection without any link to the CA system. Before that, the POD sends the key to the host using a Diffie-Helman key exchange technique so that host can decrypt the program. If the program is Main Profile at Main Level (MP@ML or SDTV), the program will be demultiplexed into audio/video/data elementary streams (ESs). The ESs will be decoded by the respective decoders. The decoded video and audio will be encoded by the multimedia subsystem into an analog NTSC signal, which will be output to a coaxial connector. A SPTS may be created out of the selected program. The SPTS or the entire multiplex can then be transmitted over the 1394 port. If the program is Main Profile at High Level (MP@HL or HDTV), then it is classified as a passthrough signal and will be transmitted over the 1394 link. Just prior to passing across this 1394 link, additional encryption also may be applied to the streams based on copy control instructions (CCI) received from the POD module. In the absence of a POD module, the output of the QAM demodulator will be input to the demux directly. If the desired program is in the clear (i.e., broadcast channels), the STB will transmit it over an RF channel or 1394 link. The multimedia subsystem also is responsible for creating a bitmap for the IPG. When an interactive program guide (IPG) is requested, the the system can overlay the IPG with analog video or it may transmit the IPG bitmap data over the 1394 link using the asynchronous transfer mode. As mentioned earlier, the cable system has an OOB signaling channel in addition to a large number of service channels. All OpenCable-compatible STBs are required to have two tuners. One tuner tunes to the desired service channel, while the second tuner will tune to the OOB channel. The OOB channel will be demodulated by the QPSK demodulator, the output of which is raw digital data without forward error correction (FEC). The POD module receives the raw data, performs FEC and recovers the baseband signal. The OOB data carries EMM (a conditional access message) and other data, such as systems information (SI), interactive program guides, tables and texts, and other management messages. The POD will separate the CA information and send the CA-unrelated data (electronic program guide (EPG) data, SI, etc.) to the host via the data channel. The CPU provides the user interface for STB and POD applications, in addition to other STB functionalities, such as coordinating host subsystem functions. In one-way cable networks, subscribers are required to contact their cable operator for services, such as PPV movies. The same is true for a one-way capable STB in a two-way cable network system. In a two-way system, the STB can communicate directly with headend equipment. This two-way capability enables subscribers to access digital interactive applications using a remote control unit. For example, while going through offerings using an IPG, subscribers can hi-light, select, and watch a channel by pressing one or more buttons. An adavanced STB also may have a cable modem subsystem with a third tuner as shown in Figure 3. The high-speed data modem may be integrated inside the STB. Integrating a CM inside a STB may present some technical issues, such as upstream transmitter use. The cable modem itself has an upstream transmitter built into it to communicate with the CMTS at the headend using QPSK/16-QAM modulated signals. The host now has two upstream transmitters and, based on the network capability available, has the option to use either one. For example, if DOCSIS high-speed data service is not yet available in a cable system, the CM upstream transmitter cannot be used. Various other scenarios are possible. A STB has to be properly configured during provisioning based on the network resources available in a cable system and the choice of services made by the subscriber. Retail ScenarioA consumer buys a STB from a retail store and, if he is not a cable subscriber already, contacts the local cable operator for service. Once connected to the local cable network, the consumer can then connect the STB to the cable and connect his DTV to the STBs digital output port. The STB alone (without a POD module) will enable viewing of clear channels (if available), such as terrestrial broadcast channels carried over cable. The STB has to be registered with the local cable operator before it can receive any encrypted channel. To view encrypted premium service channels, the consumer will need a POD module, and will need to contact their local cable operator to obtain one. Once the POD module is acquired, the consumer will need to insert it into the host (STB). The STB will detect the presence of a POD and using a piece of software, the STB also will verify the PODs status. If the POD is good, the following steps will take place before the POD will decrypt any encrypted channel in the inband multiplex. 1 Initialization. A process whereby the POD and the host exchange resources and capabilities. For example, based on memory resources available, they negotiate buffer size for control, command, and data packets. The POD checks the hosts copy protection capabilities or, simply, if the host has Diffie-Helman key exchange capability. Using this key, the POD will encrypt inband signals and transmit them across the interface to the host. The host has to receive the key from the POD to de-encrypt inband signals before further processing. 2 Authentication. As soon as the host asks for a premium channel, the POD asks for the hosts authentication. During this process, the host sends its 5C* certificate to the POD. In a two-way system, the POD sends the content of the 5C certificate and its own ID to the headend. The headend verifies the authenticity of both the host and the POD. If either of these devices is not genuine, or the devices are not compatible to each other, the headend will send the appropriate message to the POD, which will display a message on the television screen. For example, if the host is in the revocation list, the service will be denied. In a one-way system, the POD will itself verify some of the 5C certificate data and it will hash out a large number out of ID numbers of the POD and host. The POD then displays a text message, the phone number of the authorization center, and the hashed out number on the television screen asking the customer to contact the authorization center. The customer will need to call the authorization center and provide the hashed out number. Again, if both the POD and the host are authentic, service will begin. 3. Connection. Once the POD verifies the validity of the host, the connection of the POD with the host is accomplished with help from the headend. The headend sends data to the POD through a management entitlement message (EMM). After the data is received, the POD and the host are inseparablethe POD will not work with another host. Before a POD can work with another STB, the POD first has to be unconnected from the current STB and then a complete procedure for connection with a new host will be required. In cable networks, the EMM message is sent to the POD via an OOB channel; the host has no access to this message. OCI-C1: The STB Output InterfaceExisting STBs use coaxial cables and connectors as output interfaces for the delivery of analog NTSC signals. The cable industry has been looking for a low-cost, high-performance, robust interface to deliver digital signals from the STB to digital equipment. An interface based on IEEE 1394 is a good candidate for the following reasons: q The high-performance, low-cost bus supports simultaneously asynchronous (guaranteed delivery) and isochronous (guaranteed timing) transport on the same bus; q Plug-and-play features make it user-friendlylive attach/detach of devices prompts the network to self-configure and resume normal functioning; q Multiple devices are supported in a networked environment. CableLabs OpenCable initiative has selected the 1394 high-performance serial bus as the set-top box interface for future digital audio/video appliances and possibly to home networks. Since the set-top box will serve as the gateway to the cable networks programs and services, the versatile 1394 will be the bridge between the STBs diversity of applications and consumer electronic devices, including support for SDTV and HDTV on cable [reference 1].Figure 4 depicts a simple home entertainment environment with a few consumer electronics devices connected to each other using 1394 ports. A STB is the terminating node for cable at home. The 1394 ports in the STB are used as the simple home digital network interface. A DTV, DVCR, and digital camcorder are connected to this interface; it is assumed that the 1394 interface in the STB will have the capabilities required to be a root node, isochronous resource manager (IRM), cycle master and, optionally, bus manager (BM). The DTV and DVCR may have similar capabilities; the camcorder will have a less expensive four-wire 1394 interface. Available 1394 chips will have asynchronous and isochronous data transfer capabilities, and the cost difference between full-capability chips, and those with lower capability, will be minimal. Even if the power to the STB is turned off, the PHY layer, which will be kept alive using power from the bus (if it is connected to it), will act as a through-connection. Thus, a DVCR or a camcorder will be able to use the TV as a viewing monitor. Similarly, if the power to the STB and the DTV is turned off, the camcorder will be able to transfer digital audio/visual data to the DVCR for recording.
What will happen when two devices, such as a STB and a DTV with 1394 capabilities, are connected using a 1394 cable for television viewing? Any device attach/detach, or power turn on, will cause the bus to reset. Before the link is ready for data transfer, a sequence of handshake signals (packets) will be exchanged between the two devices to complete standard procedures, such as dynamic node address allocation, self-identification, arbitration for IRM, BM, and cycle master. The STB will then query the DTV to collect capability information. Some of the AV/C commands involved are shown in the following table.
Once the initialization sequence is completed, the STB/DTV pair is ready to interact. An example of how this interaction could occur is described here. A menu display, with buttons or icons on the DTV screen, will indicate that the link to the STB is ready; the following table details the basic sequence to view a television channel.
The DTV and the STB could support a default mode after power-up to select the last state (i.e., last television channel viewed), which is similar to current televisions. In this case, the above sequence would run automatically without user intervention. 1394 LimitationsAlthough the 1394 serial bus technology includes many advanced features, which make it user-friendly and, at the same time, high performing, there are a few limitations (please see reference [2]). The OpenCable architecture may be implemented in various ways as shown in Figure 5 (page 11). Figure 5a shows an implementation of the OC STB architecture as a stand-alone unit. Existing analog television or a DTV may be connected for viewing television channelsof course the analog output port will not provide HDTV channels. In Figure 5b, a STB may be embedded inside a DTV with a PCMCIA card slot for the POD. Figure 5c shows a way to augment the OC DTV with an enhanced STB in the future, when such enhanced services will be available.
Figure 5. STB Implementation and Logical Interfaces Acknowledgments The author would like to thank Don Dulchinos, Vice President, Advanced Platforms & Services, director of the OpenCable Project, for his support and encouragement, and David Broberg, Director, OpenCable Requirements, for reviewing this article. References 1. Home Digital Network Device Interface SpecificationsSCTE (Society of Cable Television Engineers) DVS (Digital Video Subcommittee) document number 194, 1999. 2. IEEE 1394The Multimedia Bus of the Future. Mukta L. Kar, Ph.D., Part I, SpecsTechnology, Volume 11, Number 5, July, 1998; Part II, SpecsTechnology, Volume 11, Number 7, October, 1998. |
| Specs News & Technology From CableLabs® ©Cable Television Laboratories, Inc. |