FCC Record, Volume 25, No. 5, Pages 3497 to 4389, April 5 - April 23, 2010 Page: 4,284
The following text was automatically extracted from the image on this page using optical character recognition software:
across carriers. We seek comment on these expectations, as well as on the specific elements we believe
would be necessary to bring the concept to fruition. For example, in a petition for rulemaking filed in the
wake of NBP PN #27, Public Knowledge suggests that an AllVid-type device would require "standards
for (1) a physical connection, (2) a communication protocol, (3) authentication, (4) service discovery, and
(5) content encoding."4 We seek comment on Public Knowledge's proposal, as well as the list of
functions discussed in detail below that we believe would be necessary to implement the AllVid
concept." We seek comment on any other functions for which standards would be necessary to develop
an AllVid adapter. In this Section, we also seek comment on standards for the adapters, with the
understanding that these standards may not encompass the entire universe necessary to develop and
deploy AllVid adapters.
25. AlVid Equipment. The AllVid equipment would be designed to operate specifically with one
MVPD and offered through the MVPD's preferred mechanism, whether leased or sold at retail,
manufactured by one company or competitively. We foresee two possible physical configurations for the
AllVid equipment. In the first configuration, the AllVid equipment would be a small "set-back" device,
capable of communicating with one navigation device or TV set and providing at least two simultaneous
video streams to allow for picture-in-picture and to allow subscribers to watch a program on one channel
while recording a program on another channel. In the second configuration, the AllVid equipment would
act as a whole-home gateway, capable of simultaneously communicating with multiple navigation devices
within the home, and providing at least six simultaneous video streams within the home (which would
allow picture-in-picture in three different rooms), possibly through a modular system that could
accommodate more streams as necessary. We seek input on each of these configurations and whether one
of these configurations is more appropriate than the other, or if there are other superior configurations that
should be considered.
26. Physical connection. The 100-BASE-TX Ethernet could act as the physical layer technology
used to connect the AllVid adapters with navigation devices. 100-BASE-TX Ethernet operates at speeds
adequate to allow transfer of multiple high definition MPEG-2 signals (nominally 15 Mbps each), and it
has developed as a de facto connection for data transmission. Current and next-generation audio-visual
equipment has and will continue to include Ethernet ports for connectivity for the foreseeable future.
Therefore, adoption of Ethernet as the physical connection for AllVid adapters and navigation devices
could enable compatibility with existing devices. In addition, the ubiquity of Ethernet could allow the
AllVid adapter and navigation device manufacturers to defray costs to a large extent. We seek comment
on these predictions. We seek comment on whether using Ethernet for the physical connection would be
limiting if lnternet video were not passed through the AllVid adapter. We also seek comment on any
other physical connectors (for example, Multimedia over Coaxial Cable ("MoCA")) that could serve as
the bridge between AllVid adapters and retail navigation devices, or whether the Commission would need
to mandate a physical layer technology at all.
27. Communication Protocol. Internet Protocol ("IP") could act as the communication protocol
between the AllVid adapter and navigation devices. Like Ethernet, IP is the de facto standard protocol for
data transmission, and current and next-generation audio-visual equipment is capable of handling IP
communication. As a widely adopted protocol, IP is familiar to hardware and software developers, which
would allow the retail market to flourish for smart video devices. We seek comment on whether IP would
be the best choice for an AllVid communication protocol. We also seek comment on any other
communication protocols that could serve as a standardized communication protocol between AllVid
adapters and retail navigation devices.
47 Public Knowledge et al Petition for Rulemaking, CS Docket No. 97-80, GN Docket Nos. 0947, 09-51, and 09-
137, at 35 (filed Dec. 19, 2009).
4 See infra ~ 25-36.
Federal Communications Commission
Here’s what’s next.
This book can be searched. Note: Results may vary based on the legibility of text within the document.
Tools / Downloads
Get a copy of this page or view the extracted text.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current page of this Book.
United States. Federal Communications Commission. FCC Record, Volume 25, No. 5, Pages 3497 to 4389, April 5 - April 23, 2010, book, April 2010; Washington D.C.. (digital.library.unt.edu/ark:/67531/metadc28495/m1/801/: accessed January 22, 2019), University of North Texas Libraries, Digital Library, digital.library.unt.edu; crediting UNT Libraries Government Documents Department.