SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?


To: D. K. G. who wrote (8733)10/3/2000 7:27:07 AM
From: justone  Respond to of 12823
 
Dennis:

Your last two posts referenced excellent web pages with two distinct views of
residential broadband: FTTH and HFC. However, I'd like to note the major
differences between the two and to suggest that this difference is not only between the two
articles, but exemplary of the differences between unfocused technical dreams of FTTH
and the careful practical approach of the cable industry.

The somewhat informal interview with Dr. Terry Shaw of cablelabs is very instructive.
Cablelabs is very focused not only on the technology but on the business services and
how to deploy them In its standards and specifications it reaches out into the core,
and is now reaching into the home, not to specify, but to discover what is there and
how to handle this for their customers. Cablelabs is an organization tightly controlled
by cable providers not vendors. This is why their specifications are over a year ahead
of even the IETF; this is why they are focused on management as well as deployment of
network; this is why they worry about market issues of reliability, performance, and
technical support in the home.

Their business model is driving the standards, vendors, and deployments. They want
first tv, then data, then phone, then interactive services, and this all must be thought out
carefully to interface with real networks and with home devices. It all must be
managed, and there must be conformance testing as well to ensure interoperability.
And this is reflected in the www.cablelabs.com specifications.

This reminds me of the GSM MOU, another provider driven committee, who were
wildly successful in deploying wireless phones. The added one revenue generating
feature after another, while at the same time deploying a rapidly growing infrastructure
for wireless: an amazing achievement.

Meanwhile, FTTH's business model, according to the article, sounds basically like "if
we build it they will come". It doesn't matter if it is PON, or 10G contention based
"ethernet", or 10G point to point ethernet, the focus is on the technology, not the
services.

The only thing that worries me about HFC is the upstream shared bandwidth. And I
suspect the reason this has not been addressed deeply (except by ATT's lighwire
architecture) is that they don't see a business reason for residential upstream. I confess,
despite my earlier rant on FTTH, I don't either. If you have an upstream need- for
example, if you have a server or a building a VPN- you have to pay business rates for
it. I don't see why residential users should subside business bandwidth hogs.

The only two exceptions might be a 'napster' like service where you are sharing your
disk with the public (but why does your neighbor have to pay for your generosity?),
and home video conference/distance learning. Even these could be handled by
adjusting HFC bandwidth allocations or building out DWDM network nodes. Of
course, it may also be true that this is a case of application blindness- you can't see
what is beyond the technology curve until you drive around it.

I'm beginning to believe that cable and HFC are unstoppable for residential broadband
access, the fastest growing telecom segment, at least in the 67% of homes in the US
that have access to cable service.



To: D. K. G. who wrote (8733)11/2/2000 9:10:41 PM
From: D. K. G.  Read Replies (1) | Respond to of 12823
 
The Skinny on Set-Tops

theneteconomy.com

Thin client, fat client – what’s the difference? Turns out, it’s plenty

By Jonathan Blum

Consider the set-top, that squat little box that connects most households to the wonderful world of television. It looks kind of bland, kind of functional. Definitely not sexy. But don't be fooled: That box could hold the keys to the broadband networking future.

If you think those keys are going to be easy to get to, think again. Actually delivering video is turning out to be tough.

"You get this eerie feeling when dealing with network folks that they are suddenly realizing how hard video is to do," says Scott Wilcox, senior vice president at Prasara Technologies, a provider of interactive software. "They almost sort of think it is going to scale like some Internet thing — which it absolutely positively will not."

A big holdup is the core operating system operators must use to offer video. The actual choice of software products, usually from either Microsoft, Liberate Technologies or OpenTV, is clouded by unfinished backbone networks, incompatible standards, contrary vendor visions and uncertain development paths. Plus the stakes could not be higher.

"We do frankly get a glimpse of the end of our business from our operating software systems choices," says Bill Weeks, chief strategic officer at Next Level Communications, a supplier of interactive TV technology. "We know that if we don't get this right, we could lose control of our destiny."

So complicated

Things did not start out that way. The software that controls set-tops used to be simple. Supplied by vendors like Microware and Wind River, the software boiled down to nothing more than an instruction set that changed the volume and channels of your TV and maybe offered a offer some pay-per-view content — usually stuff like Debbie Does Dallas or professional wrestling.

That all changed in the mid-90s when deceptively powerful services called electronic program guides swept cable. An EPG is an entire channel of nothing more than a listing of what is on the other channels. Consumers loved these services, and network operators were more than happy to oblige them — and pick up a nice revenue stream from the ads that ran above the channel listings 24 hours a day.

There was just one catch: You couldn't even turn up the volume on those early systems without going through the EPG provider, usually Gemstar. "It really scared everybody," says Allan Thygesen, executive vice president of sales and business development at Wink Communications, which sells interactive e-commerce services. "The industry quickly saw that whoever controls that EPG in effect controls the set-top box and a big chunk of the network."

But there was no turning back. Cable operators knew their futures rode on making the transition to interactivity, even if they hadn't figured out how to protect their core businesses.

That's when the cable industry ran smack into the essential TV problem: the thin client vs. fat client debate. The client side set-top box is only half the advanced content equation; a big server, usually sitting in a network distribution point, is needed to work hand-in-hand with the set-top box. The delicate balance that these two machines must strike is the essential problem any broadband application manages.

Operators quickly divided into two camps about how to best manage that problem: those who felt the set-tops should be big fast computers, and those who thought the set-top should be as skinny as possible.

No fat chips

The thinnest of thin side is championed by OpenTV. OpenTV now has 9.3 million boxes deployed worldwide and firmly believes that all the heavy lifting should be done at the network distribution point using optimized code.

"That way more machines can run it," says Vincent Dureau, OpenTV's CTO. "We are seeing more interest from American network operators as they see the thin client approach offers them the largest possible audience."

Leading the fat side of the struggle is Microsoft. Its formidable PC experience leads Microsoft to claim that the set-top should handle all operations out on the very edge of the network, even if the network itself is not in place to offer the services. Microsoft is pushing its Windows CE to fill that need.

Liberate Technologies falls somewhere in the middle — literally. Liberate puts some intelligence in the set-top and some in the distribution point. Its main focus is on the middleware that connects the two sides. The end result is more flexibility — but more complexity as well.

A case of whatever

One of the ironies of the debate is that ultimately, the fat-client approach can do anything that the skinny approach can do, and vice versa. "What is perverse here is, from an engineering point of view, the choice really doesn't matter," says Dave Caputo, CTO at PixStream, a video technology supplier bought last month by Cisco Systems. "Anything can be done in either approach."

Why? The base operating system is hilariously simple. The tricky work is done by middleware applications that run on top of the operating systems. These middle-ware apps broker the transactions between the client set-top and main central server, therefore leveraging the network. But functionality can be put on either the client or the server side, depending on the solutions. So the middleware is crucial. "It's the most important application from our point of view," says Charlier Tritschler, senior vice president of marketing at Liberate. "It's no accident that we offer the only pure-play middleware product."

Depending on how that middleware is configured, Internet applications based on Java, Cold Fusion or HTML can work on the platform. Liberate makes great hay about how its standard is open and light enough to run on most new boxes and still offer powerful services.

Network differences

The lack of consensus on the set-top front is not totally the fault of the vendors. Each and every network operator has its own plan about to how best offer service, and each built its network accordingly. The end result: Every single network is slightly (and maddeningly) different.

"It is simply impossible for a casual observer to understand how complex and specific every particular operator's solution is," says Scott Swix, director of systems architecture development at BellSouth. "We simply will not make judgments on any product without literally teams of engineers and an extensive qualifying process."

Software woes don't end there. Each application that rides on top of middleware, such as e-commerce apps and e-mail, requires a different server at the network distribution point that must function with the rest of the applications and servers. How these apps and servers actually will fit together is a significant unknown at this point.

One big criticism of Liberate's one-size-fits-all middleware approach is that its scalability is suspect, or at least it hasn't been demonstrated. After all, if the modern interactive network evolves to be as feeble and confused as the modern PC, the networking business has created a royal headache for itself.

Because the systems themselves really don't exist yet, it's still too early to call a winner. Although Open-TV claims that there will be 10 million homes with interactive set-tops by the end of this year, at most only half of those homes are connected to digital networks, and even fewer are connected to digital networks that support interactivity.

"What the operators are asking for is very challenging," says Weeks of Next Level. "The fact still remains that if you are looking for a reliable, provisionable, remote monitored system, there just is no real standard as of now."

But there are plenty of choices.