IPTV systems are best designed as hierarchical distributed storage systems with hierarchical network bandwidth. Bandwidth and storage requirements decrease at the edge of the network. Neighborhood nodes need to be the size they've already become to support MPEG VOD, and only need a fraction of the coax bandwidth available (which can ride on existing coax already carrying analog and digital broadcast). An edge server, router, and modem are needed at the neighborhood node for HFC. Shows being watched by one or more STBs are cached locally, progressively copied from the headend when needed if not already edge cached, and overwritten by least used algorithm when no longer needed. Multicast is routed directly from headend over optical to coax (or other last mile delivery). =20 All it takes to support niche programming technically is a one time file copy from anywhere in the world to the headend server (and some EPG exposure, inclusion in a virtual channel, or some other discovery mechanism). But, as you say there are plenty of business reasons it might not happen on a cable IPTV system. So, I say the biggest difference is that you can be supplying 10,000 different "channels" on a node with last mile bandwidth that can only handle maybe 10 channels, and backbone bandwidth that may average 1,000 "channels" of simultaneous downloads and multicast streams (but typically has vastly more capacity with 10GigE routers). Contrast that with a parallel and synchronous cable plant that has every wire carrying every TV channel all the time (very poor frequency reuse, throughput limited to the weakest link last mile bandwidth). =20 [RH] "How are all these 100's and maybe 1000's of "niche" producers going to be paid?" Advertising? I hear there's about a billion dollars lying around following the most recent and most dismal Upfront. Whatever Google and the numerous professional and amateur video Internet portals don't get will be looking for eyeballs to spend on, the more targeted the better (i.e. higher CPM). Kilroy Hughes -----Original Message----- From: opendtv-bounce@xxxxxxxxxxxxx [mailto:opendtv-bounce@xxxxxxxxxxxxx] On Behalf Of Richard Hollandsworth Sent: Sunday, July 09, 2006 23:12 To: opendtv@xxxxxxxxxxxxx Subject: [opendtv] Re: 060707 Free Friday Fragments (Mark's Monday Memo) The biggest differences between current MPEG2 architecture and IPTV is that the former is not very error/delay tolerant and hence must be either streamed from a "local" server or a dedicated "pipe" must be guaranteed from a remote server to the user. That means the MSO has to "manage" it all the way....which will be difficult when "niche" programs come off of servers located all over the place... How are all these 100's and maybe 1000's of "niche" producers going to be paid? MSO's shouldn't have to negotiate a contract with every "source": be they music concert venues, music groups, individual artists, religious groups, hobby, travel, collecting....not to mention independent film/p*rn producers... IPVT may permit near-real-time delivery if you have a big enough pipe, but I would expect the cable "niche program" VOD/PPV implementations to establish a connection to a server. The server could be local or remote, maintained by the MSO Central Office, a religious group, in the U.K., wherever. The server could dump it to your DVR for playback at your convenience, with wait times dependent on the server. If there is a charge, expect to see it reflected on your monthy bill... Advantages: robust error control, easy interconnections, fairly easy billing/vendor payout and fits into high speed I-N upgrade architecture with minimal impact on existing HFC wiring.... For example splitting nodes and allocating more capacity on I-N QAM carrier(s) to each user. Note that FiOS ONT provides (shared) 622 MHz down and 155 MHz up on same fibre as 55-870 GHz TV spectrum. And that's just one fibre... holl_ands =09 --------------------------------- Sneak preview the all-new Yahoo.com. It's not radically different. Just radically better.=20 =20 =20 ---------------------------------------------------------------------- You can UNSUBSCRIBE from the OpenDTV list in two ways: - Using the UNSUBSCRIBE command in your user configuration settings at FreeLists.org=20 - By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. ---------------------------------------------------------------------- You can UNSUBSCRIBE from the OpenDTV list in two ways: - Using the UNSUBSCRIBE command in your user configuration settings at FreeLists.org - By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.