downloadable conditional access systems (dcas) are already available, but the politics of the market are so muddled it looks like implementation of dcas has been pushed off for yet another year.
cable operators and their vendors had plans to have a downloadable conditional access system (dcas) commercially ready right about now. given how frequently dcas has been delayed in the past, it should come as no surprise that dcas has been delayed again, to sometime in 2009.
part of the most recent delay is manifested in a recasting of polycipher – the dcas development joint venture of comcast, time warner cable, and cox – a change that represents another short-term failure of the polycipher project.
implementation of dcas has been pushed off for yet another year.
polycipher’s first and most important goal was to create a dcas that would satisfy a mandate from the fcc to separate conditional access (ca) from set-top boxes in a more economical way than by using cablecards.
polycipher was unable to create a dcas in time to head off an fcc edict that forced cable operators to deploy cablecards with every new set-top installed, starting a year ago in july. that’s old news.
the other goal of polycipher would follow from the first; it was to break the death grip that motorola and cisco have on the set-top market by virtue of their duopoly position in the cable ca market.
if ca technology is broken out as a separable component of the set-top, however, then any set-top could be used, in combination with almost any ca technology, and the motorola-cisco set-top duopoly could be broken.
now polycipher is in the precarious position of relying on the very companies that have the most to lose if that second goal is met. the msos backing polycipher have invited the duopolists, along with a third ca vendor, to participate on the development of the polycipher dcas solution.
“sa, moto, and nds are the experts here, and we need their expertise,” said kevin leddy, time warner cable executive vice president of technology policy and product management.
the nds group provides ca and digital rights management (drm) technology for cablevision, as well as directv and other satellite tv providers around the world.
motorola and cisco not only have a set-top business to protect, but along with nds, they have also made big investments in developing cablecards.
polycipher, with the participation of both cable operators and cable equipment vendors, will continue to develop a dcas, leddy said. msos still desire a more economical alternative to cablecards.
but cable has a number of priorities and dcas is nowhere near the top of the list.
how did the cable industry get here, and where could it possibly be going with security? can dcas still graduate from a short-term disappointment to a long-term success, despite other security options?
the dcas story starts more than a decade ago. motorola and cisco already had their lock on the cable equipment market with proprietary systems that married their respective headend equipment with their respective set-tops. security technology deeply embedded in the set-tops and reiterated in the headend gear was the glue in those marriages.
but as cable grew, the consumer electronics (ce) industry began to lust after the set-top market. meanwhile, some consumers were complaining that if they were forced to have a set-top box, they should be able buy one at retail, which consumer advocates expected would be more economical than renting. cable operators began to daydream about a day when they wouldn’t have to buy and maintain all those boxes.
it would be possible to sell set-tops at retail if security systems were to be separated from set-top boxes. then ce manufacturers could build boxes, and the cable operators could provide a plug-in security module or download requisite software. consumers could buy any box they wanted.
congress tried to make it so with the passage of the 1996 communications act. a provision of the communications act included a mandate that the cable industry separate its security technology. the federal communications commission subsequently drafted rules on the specifics and commanded that cable have separable devices by 2000.
the fcc also decreed that cable would have to make available a separable security device usable by any third party by 2005.
the cable industry met the 2000 deadline. and, according to the ncta, the ce industry failed to show – there was nothing to put the devices into.
the consumer electronics association countered that the cable industry’s technology licensing provisions were unacceptable. the cea also objected to cable’s desire to have cablelabs test ce equipment to make sure it actually worked.
there had been some animosity between the cea and the ncta before all this, but the separable security issue served only to escalate it.
the spat between cable and consumer electronics has centered on the cablecard, a device containing ca circuitry that could be plugged in to almost any host with an appropriate slot for it. the problem has been a lack of agreement about how cablecards would be implemented.
the crux of the cablecard argument is that ce wants the simplest, least expensive solution possible. that turns out to be a one-way implementation – one in which signals can go to the tv, but cannot come back. the technology implementation the cea is proposing is called dcr (digital cable ready plus).
cable had always argued for a two-way implementation that would ensure that signals could go to and from the tv. one-way technology automatically bars interactive applications (these would come to include video-on-demand, startover and restart, interactive advertising, and others). two-way would support most of the newest cable products and features.
in 2004, single-stream cablecards (scards) became available from motorola, cisco, and nds. from 2004 to 2007, about 380,000 cable customers – less than one-half of one percent of all cable subscribers – requested one. during that time, only about 1 percent of all tvs sold with cablecard slots were being used with a cablecard.
and at first when they were installed, there often were technical problems. the cea and ncta squabbled about who was responsible for the technical problems, the low rate of adoption, and whether the cards were adequately promoted, explained, installed, etc.
furthermore, when ce companies made products that could take a cablecard (tivo is a notable example), the ce products themselves did not support two-way capabilities, so the two-way capabilities in cablecards was automatically mooted.
cable and ce could not cooperate, which stymied any development of a two-way solution that cable required. given that, the ncta asked the fcc for one postponement after another for the integration ban deadline in 2005, and the fcc complied.
until 2006, when the fcc decided enough was enough and damn the details; it had been 10 years since the communications act had been passed, and the cable industry would have to distribute set-top boxes with separate cablecards starting july, 2007.
but cablecards aren’t the whole of the situation. a critical corollary issue is the former opencable application platform (ocap), which earlier this year was renamed tru2way for reasons that become obvious in the context of the cablecard spat.
the cable industry proposed ce manufacturers adopt ocap as an alternative to dcr . ocap would make ce products truly two-way (tru2way – get it?).
by the way, cablelabs is to certify any two-way ce products, a notion the ce industry continues to oppose.
cablelabs has since made the testing process about as easy as it could and still use the word “test” with a straight face, but the cea remains adamantly against cablelabs testing on principle.
ce industry resistance is slowly eroding, however. tivo had been supplying its dvrs to directv, but by 2005 that relationship was souring. tivo wanted desperately to get its dvr technology in with another large service provider, and ended up getting a deal with comcast. for the longest time, that deal appeared to be a non-starter, but last year, comcast certified tivo’s ocap/tru2way software.
korean operators were among the first to embrace tru2way, and late in 2006, two of the largest korean ce manufacturers, lg and samsung, agreed to develop tru2way products.
“we need a global strategy. it has to be standards based, which means things like tru2way, java, mhp,” said stephen goldstein, samsung electronics america’s director, business development. “tivo makes it plain that they are no longer a box company, they’re a software company. but boxes are important to us. whatever we need to do to sell more, we will do that.”
panasonic eventually followed suit, and days ago, at the very end of may, so did sony.
all the while the disagreements raged about whether cablecards would be unidirectional or bidirectional, and who was supporting those capabilities, and how, the cable industry was simultaneously arguing that the cablecard itself was a problem. a better, less expensive, and – by the way, two-way – solution would be a dcas. not coincidentally, tru2way is a prerequisite for cable’s dcas.
the prospect of a dcas figured in to the case the cable industry made to the fcc to keep putting off the 2005 deadline for an integration ban.
but the industry had to actually produce a dcas; the integration ban could not be postponed forever.
in 2007, an operation called beyond broadband technology announced it had developed a low-cost open standard set-top with a downloadable security system.
bbt’s ceo bill bauer, and its coo tony swain, said they’ve got first silicon on the set-top chip, and have a headend controller that will work with the set-tops. bbt has also lined up a service provider to field test the system starting this month or next.
the bbt dcas was the impetus for a significant decision from the fcc. it had never been clear whether the fcc would accept dcas as a viable means of satisfying the separable security mandate.
when bbt introduced its dcas, the fcc issued a public notice that dcas does in fact satisfy that mandate, and noted that bbt’s dcas was an example. nonetheless, there’s confusion about the fcc’s approval.
widevine developed a dcas called widevine cypher that it first deployed six years ago, and is now being used by scores of service providers around the world, among them sprint. widevine has requested from the fcc a similar notice stating that its dcas satisfies the separable security mandate.
widevine’s request for a notice states that “several of widevine’s prospective customers have expressed an unwillingness to purchase the widevine cypher technology due to the lack of a public notice finding widevine’s cypher to be compliant with common reliance mandate.” the common reliance mandate is another reference to the integration ban.
an fcc spokesman told ced that the approval from the notice that mentions bbt applies to any dcas.
motorola and cisco also have dcas schemes, though each requires use of its own ca systems, which just keeps msos locked in to products from one or the other.
all of these alternatives have to contend with a dcas whose development several major msos have invested in.
in 2006, comcast, twc, and cox decided that if they wanted a dcas – one that did not come from motorola or cisco – they would have to do it themselves.
the three funded a project that would be managed by polycipher. the result would be a chipset and related technology that could be integrated into almost any product. the target date for introduction was 2008.
the integration ban in july of 2007 changed the situation. it became clear to the partners in polycipher that their dcas was not going to be ready by the deadline.
the argument had always been that putting cablecards in every box would be too expensive, which might lead one to expect that the integration ban would increase the sense of urgency to get dcas done, but no.
in practice, the percentage of set-tops installed with separable security is still small, and the costs are not mounting yet, twc’s leddy explained.
given that the pain level associated with cablecards is still fairly low, operators are paying attention instead to more pressing matters, such as rolling out more hd, and preparing for the digital transition in february 2009.
but if dcas is a lower priority, it is still a priority, leddy said. cablecards, he said, “are still a huge waste of money and resources. they’ll cost the industry $600 million a year. it’s naïve to think anyone can just absorb that.”
but maybe the amount cable has to absorb will be less, and perhaps tolerable. theoretically, with volume, the cost of cablecards will come down. if that happens, that’s just one more factor that may diminish the urgency to switch to some dcas scheme.
one other possibility would be if ce companies start making products that incorporate all the functions of a set-top, basically subsuming the set-tops and eliminating them as standalone products.
a third possibility would be if cable were to adopt drm technologies from companies such as microsoft or real networks. the whole reason to have ca, and the possible migration to dcas, is that content owners demand the security. but if drm provides that security, all bets might be off.
“owners of content have gotten comfortable with drm,” leddy observed. the cable industry could adopt drm technology. “it’s far cheaper for us.”