Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
CableCARD
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===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 guide]]s, [[pay-per-view]], video on demand, or [[switched video]] streams New [[digital television]]s 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 '''iDCR''' "[[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 (programming language)|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 [[National Cable & Telecommunications Association|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.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)