CableCARD

The portion of the Telecommunications Act of 1996 which resulted in the creation of CableCARDs is known as Section 629, instructing the Federal Communications Commission (FCC) to: Multichannel video programming refers to cable or satellite television. A driving motivation of this passage was to foster the kind of consumer choices that resulted after the Federal government landmark Carterfone ruling requiring telephone companies to allow consumers to purchase third-party telephones for attachment to the phone company network. The thought was that consumers would benefit from wider choices due to competition between consumer electronics (CE) manufacturers unaffiliated with cable companies. The FCC was charged with working with the industry to carry out the directives of the 1996 law. On June 11, 1998, after securing proposals and recommendations from interested parties, the FCC ordered that cable companies would provide a separable security access device by July 1, 2000, which could be used by third-party devices to access digital cable networks. The separable security device was referred to in FCC regulations as a "Point of Deployment" (POD) module. After many requests for delay from the cable industry, the first CableCARD devices became available from third-party manufacturers in August 2004. Integration ban A major concern was that cable operators were not motivated to provide efficient security access mechanisms to equipment competitors. To address this, the FCC directed that by January 1, 2005, that cable operators must use the same separable access device available to third-parties and they were banned from providing equipment with an integrated security access mechanism. This rule is usually referred to as the "integration ban", and was unsuccessfully challenged in the courts and petitions to the FCC by the cable operators. The deadline was shifted forward twice until it went into effect on July 1, 2007. The ban on integrated security ended in December 2015. ==Technical overview==

CableCARD is a term trademarked by CableLabs for the Point of Deployment (POD) module defined by standards including SCTE 28, SCTE 41, CEA-679 and others. The physical CableCARD is inserted into a slot in the host (typically a digital television set or a set-top box) in order to identify and authorize the customer, and to provide proprietary decoding of the encrypted digital cable signal without the need for a proprietary set-top box. The cable tuner, QAM demodulator, and MPEG decoder are part of the host equipment. The card performs any conditional access and decryption functions, and provides a MPEG-2 transport stream to the host. The card also receives messages sent over the out-of-band signaling channel by the cable company's headend servers and forwards them to the host. CableCARDs may be used to access both standard definition and high definition channels as long as they are not part of a switched video system. (This applies to one-way devices only; two-way devices are capable of receiving and viewing switched video. The ability for one-way devices to receive and view switched video has changed with the addition of the Tuning Resolver Interface Specification. Tuning adaptors and tuning adaptor interfaces have been added to provide communication back to the headend needed for switched video.) CableCARDs are not necessary for viewing unscrambled digital cable channels if the user has a QAM tuner—a feature in some televisions and DVRs. CableCARD support is most common on higher end televisions that include a special slot for the CableCARD and a built-in cable tuner. The card acts like a unique "key" to unlock the channels and services to which the cable customer has subscribed, and the television's remote-control will also control the cable channels. Televisions that support CableCARD should be labeled by the manufacturer as "digital cable ready" (DCR). Interactive features such as video on demand rely on the CableCARD Host device being an OpenCable Host Device and have nothing to do with the physical card. This makes the common use of the phrase "CableCARD 2.0" as a requirement for video on demand misleading, since two way services have been provided with the actual cards from the very beginning. M-Cards are backward compatible with current CableCARD devices. In older CableCARD devices that do not support multiple streams, the card appears to be a single stream card. CE companies have long wanted M-Cards for their CableCARD 1.0 host devices in order to compete with devices that use multiple tuners. This is important for products such as Moxi and TiVo CableCARD DVRs, televisions with picture-in-picture and CableCARD-equipped personal computers, which need to record one show while a user is watching another. To enable this without an M-Card, these products would be required to use multiple S-CARDs. CableCARDs with personal computers Existing integrated cable set-top boxes perform four basic functions: • Enable receiving and selecting digital and analog cable channels • Uniquely identify the customer and authorize the features to which they have subscribed • Decode scrambled digital channels and premium programming such as movie channels • Provide interactive two-way communications for electronic program guides, pay-per-view, video on demand, or switched video streams New digital televisions and other devices that are labeled DCR (Digital cable ready) contain: • Built-in support for receiving digital cable channels (via an internal QAM tuner) • A slot for the current version of CableCARD, which allows decryption of encrypted digital channels The CableCARD 2.0 specification includes support for #1-4, interactive two-way communications; however it is unknown exactly when CableCARD 2.0 hosts and compatible servers will become available. Future devices which support CableCARD 2.0 are expected to be labeled '''''' "Interactive digital cable ready". Among other requirements, CableCARD 2.0 hosts will be required to provide the OpenCable Application Platform (OCAP), also known as Tru2way, to run programs downloaded from the cable company. Because the conditional access system is in software, it can be sent with the video as a form of digital rights management. The CableCARD Host Licensing Agreement and the DCAS agreement restrict the technologies that CE companies may use for distributing video from host devices. CE companies object to this expanding the notion of CableCARD network security issues to also include content protection issues. They prefer to deal with content owners directly with their standards and regard cable company protocols and formats as a transport only. CE companies wish to communicate video inside the home network using their own protected protocols and formats. The OpenCable Application Platform (OCAP) is a Java-based platform intended for use either with any security access scheme—whether it is CableCARD 2.0 devices or future downloadable security schemes. OCAP was tied to CableCARDs because, as it was imagined by CableLabs, the additional processing necessary for managing the communication with the cable company server would be performed, not on the cable company provided equipment (the CableCARD), but on the consumer electronics device—known as the CableCARD "Host". CE companies objected that OCAP is unnecessary for the simple task of managing two-way communications on the cable networks. The CEA perspective is that Java is not efficient for CE devices, and that cable companies are passing to CE manufacturers the costs of a software platform which they didn't need, and which won't run on their existing hardware architectures. The consumer electronics industry proposed in November 2006 that the CableCARD 2.0 specification be upgraded to include the provision for modified MCards that would support the communications necessary for VOD, PPV, and Switched Video. This card would be backward compatible with older cards, and support would be required for them on cable company servers by January 2008. These modified MCards would not allow two-way communication using current OCURs, which, by definition, are unidirectional. This so-called "OCAP-less" proposal was rejected by the NCTA for a variety of reasons elaborated on in the issues segment of this article. The technical advantage is that much less is assumed about the computing capability of the host, allowing the manufacturing cost to be significantly reduced. The disadvantage is that the MCard will be slightly more expensive, but the host will not necessarily be able to support the envisioned ecommerce and banking applications. CE companies argue that such a card fulfills the 1996 law's requirement that cable companies allow two-way communication on their networks, and that OCAP fulfills technical goals far in excess of those necessary for such two-way communications. ==Existing standard and certification procedures==

Cable providers in the United States are required by the FCC to support the CableCARD 2.0 standard. The specification was developed by CableLabs, a research group run by a consortium of cable companies. Devices that use CableCARDs are known as "Hosts" and must be certified as compliant with the specification by CableLabs. The certification process can be lengthy and is performed in batches on a regular cycle every three months. The first test tool to verify compliance of OpenCable hosts with the CableCARD one-way single stream specifications, HPNX, was released by SCM and Digital Keystone in 2003. Subsequently, the HPNX Pro version, supporting two-way and M-card specifications, was released by Digital Keystone in 2006. The "M-UDCP Device Acceptance Test Plan" published by CableLabs defines how to use the HPNX Pro test tool to validate the OpenCable host devices. The first test tool to verify compliance of the CableCARD devices with the OpenCable specifications, Host Emulator Tool, and produced by Margi Systems, was first utilized by CableLabs to validate the Scientific Atlanta (Cisco) and Motorola POD devices in 2003 (POD was later renamed to CableCard). Cable companies in the United States are required to provide CableCARDs conforming to this specification, and must correct incompatibilities between their networks and certified CableCARD devices. The current CableCARD standard was borne out of an adversarial process between two main groups: cable companies represented by the National Cable & Telecommunications Association (NCTA) and consumer electronics companies represented by the Consumer Electronics Association (CEA). The portion of the CableCARD specs that could be agreed upon describe how one-way services work, so only the portion known as UDCP (Unidirectional Digital Cable Product) was required by the FCC. As it was the only thing required, most of the early devices were one-way capable; however all the actual CableCARDs produced were two-way capable. Many enhancements to the CableCARD standard including the optional Multi-Stream support became known as CableCARD 2.0. Optical cable services (e.g. Verizon Fios) are classified as cable services and must, by FCC rules, also support the CableCARD standard. In Canada, cable providers Cogeco and Shaw offer CableCARD-enabled DVRs. Video providers in Europe must conform to the DVB standard which is a more comprehensive open standard governed by independent standards bodies. CableCARDs can also support non-television functions and can act as a cable modem controller with the host providing modulation and demodulation functions and the card providing decoding and IP routing functionality; however this feature is rarely used and depends on the cable provider. ==Adoption==

There was much resistance from cable operators to the CableCARD rollout across the United States, preferring to support their own set-top boxes. The adoption proceeded slowly with 141,000 units by February 2006. The resistance softened somewhat with the July 2007 FCC ban on integrated security in set-top boxes, which required all new set-top boxes to use CableCARDs as their decryption mechanism. By June 2009, the top 10 "incumbent" U.S. cable operators had deployed more than 14 million operator-supplied set-tops with CableCARDs and 437,800 CableCARD modules for use in retail devices. The National Cable Television Association reported in April 2016 that only 621,400 CableCARDs were deployed for use in retail devices by the nine largest incumbent cable operators, compared to 55 million operator-supplied set-top boxes with CableCARDs. This indicates that the CableCARD failed to achieve the goal of a competitive retail market for set-top boxes. Outside the United States, CableCARDs were adopted only in South Korea, in pair with Nagravision and VideoGuard conditional access (CA) systems. U.S. adoptions of CableCARD were mostly paired with Cisco's PowerKEY (originally developed by Scientific Atlanta) and Motorola's (now Arris) MediaCipher CA systems. == Successor initiatives ==

In 2010, the Federal Communications Commission (FCC) issued a notice of inquiry for a successor system, called AllVid. Unlike CableCARD, AllVid intended to enable two-way services such as electronic program guides, pay-per-view, and video on demand. There are still many in the cable industry who are advocating that physical CableCARDs be dropped entirely. These cable companies prefer to move away from physical cards, and have proposed that a downloadable security component known as Downloadable Conditional Access System (DCAS) be used instead of a physical CableCARD. In this proposal, a custom security chip must be soldered into every compliant host; if a security scheme is compromised, a new security program can be downloaded to the host device. The FCC has not yet approved it. Consumer electronic companies advocate their proposal for more unfettered access to cable company networks, with CableLabs' role reduced to addressing only cable company interests of maintaining network stability and security. In September 2020, the FCC eliminated CableCARD support and reporting requirements by cable operators, recognizing that cable industry deployment and use of CableCARDs have been “disappointing”, and noting that competition has provided other options for consumer flexibility via streaming media over the Internet. ==See also==