1、 CEA Standard A User Interface Specification for Home Networks Using Web-based Protocols CEA-2027-B October 2007 NOTICE Consumer Electronics Association (CEA) Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misunderstandings between
2、 manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publications shall not in any r
3、espect preclude any member or nonmember of CEA from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publications preclude their voluntary use by those other than CE
4、A members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by CEA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, CEA does not assume any liability to any p
5、atent owner, nor does it assume any obligation whatever to parties adopting the Standard, Bulletin or other technical publication. Note: The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of thi
6、s standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. The patent holder has, however, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants d
7、esiring to obtain such a license. Details may be obtained from the publisher. This CEA Standard is considered to have International Standardization implication, but the International Electrotechnical Commission activity has not progressed to the point where a valid comparison between the CEA Standar
8、d and the IEC document can be made. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applica
9、bility of regulatory limitations before its use. (Formulated under the cognizance of the CEA R7 Home Network Committee.) Published by CONSUMER ELECTRONICS ASSOCIATION 2007 Technology the specifics are left to the manufacturer, and are dictated by the currently active controller. RCU commands are spe
10、cified based on CEA-931-C. This standard assumes the preexistence of a home network that links the A/V devices, and a connection-management strategy for the dynamic interconnection of these devices as they are added to and removed from the network. Zero Configuration Networking with SSDP announcemen
11、t and service discovery has been specified since it requires minimum device services for efficient network configuration. The network configuration model is based on a client (Renderer plus RCU) and one or more servers). More than one Renderer may be present in a client device. Specifications are in
12、cluded for network applications including immediate connections, connections at a later time (such as programmed recording), and connections of known or unknown duration. A Personal Video Recorder (PVR) is an example of a device that may connect for an unknown duration to provide time-shift viewing.
13、 Numerous connection examples are provided. CEA-2027-B can accommodate future formats that may be implemented with auxiliary network devices such as an advanced (H.264) video decoder. Network management tools are specified that can logically bind such auxiliary devices to specific A/V devices. For e
14、xample, a display might be logically associated with an H.264 decoder while both units are connected as nodes to a home network, rather than through a dedicated wire. XML files (The “2027 File” defined in this standard) contained in each Logical Unit facilitate such logical associations. Other featu
15、res include; Devices can be linked through various Internet Protocol (IP) capable network technologies. This standard defines the application-layer communications protocols. 5CEA-2027-B The UI data is conveyed on the home network using web-based technology (XHTML, HTTP, etc.). The GUI is described u
16、sing XHTML data structures. The GUI is manageable with a browser that has the minimum capabilities that are defined in this standard. Navigation by mouse or cursor are not mandatory when this standard is applied to an HDTV A Logical Unit may manage multiple sub-devices using a mechanism defined in t
17、his standard. 6CEA-2027-B 2 References 2.1 Normative References The following standards contain provisions that, through reference in this text, constitute normative provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and
18、 parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. 1 IETF RFC 2616, HyperText Transfer Protocol HTTP 1.1, June 1999 2 IETF RFC 791, Internet Protocol (IP), J. Postel, September 1981 3 IETF RF
19、C 793, Transmission Control Protocol (TCP), J. Postel, September 1981 4 ECMAscript Language Specification (Third Edition), December 1999, ECMA-262.pdf, http:/www.ecma-international.org/publications/standards/Ecma-262.htm 5 CEA-931-C, Remote Control Passthrough for Home Networking, June 2007 6 CEA-20
20、14-A Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE), June 2007 7 Extensible Markup Language (XML) 1.0 (Third Edition) W3C Recommendation 04 February 2004 http:/www.w3.org/TR/2004/REC-xml-20040204 8 XHTML 1.0 The Extensible HyperText Markup Langu
21、age (Second Edition), W3C Recommendation 26 January 2000, revised 1, August 2002 http:/www.w3.org/TR/2002/REC-xhtml1-20020801/xhtml1.pdf 9 HTML 4.01 specification, W3C REC 24Dec1999, http:/www.w3c.org/TR/1999/REC-html401-19991224 10 IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax,
22、August 1998 11 REC-DOM-Level-2- 20001113 Document Object Model (DOM) Level 2 Core Specification, Version 1.0, W3C Recommendation 13 November, 2000; http:/www.w3.org/TR/1998/REC-DOM-Level-2-Core-20001113 12 1394TA Document 2002010 “A/VC Connection and Compatibility Management Specification 1.1”, Janu
23、ary 2003 13 CR-css-tv-20030514 CSS TV Profile 1.0, W3C Candidate Recommendation 14 May 2003 7CEA-2027-B 14 REC-DOM-Level-2- 20001113 Document Object Model (DOM) Level 2 Style Specification, Version 1.0, W3C Recommendation 13 November, 2000; http:/www.w3.org/TR/1998/REC-DOM-Level-2-Style-20001113 15
24、REC-DOM-Level-2- 20001113 Document Object Model (DOM) Level 2 Events Specification, Version 1.0, W3C Recommendation 13 November, 2000; http:/www.w3.org/TR/1998/REC-DOM-Level-2-Events-20001113 16 CSS Print Profile, W3C Candidate Recommendation, 25 February 2004. Available at http:/www.w3.org/TR/2004/
25、CR-css-print-20040225. 17 Portable Network Graphics (PNG) Specification (Second Edition). Available at http:/www.w3.org/TR/PNG 18 Cascading Style Sheets, level 2 revision 1 “CSS 2.1 Specification” W3C Candidate Recommendation 25 February 2004 http:/www.w3.org/TR/2004/CR-CSS21-20040225 19 Cascading S
26、tyle Sheets, level 2 “CSS2 Specification” W3C Recommendation 12-May-1998 http:/www.w3.org/TR/1998/REC-CSS2-19980512 RFC 2131 R. Droms, “Dynamic Host Configuration Protocol“, RFC 2131, March 1997. RFC 2132 Alexander, S., and Droms, R., “DHCP Options and BOOTP Vendor Extensions“, RFC 2132, March 1997.
27、 RFC 3927 Dynamic Configuration of IPv4 Link-Local Addresses, May 2005 Bridge2 IEEE 1394 Bridged over Coaxial Cable Part 2: L3 IP Bridges, TS 2006016, Revision 1a, April 11, 2007, 1394 Trade Association. Bridge3 IEEE 1394 Bridged over Coaxial Cable Part 3: FCP and CMP over IPv4, TS 2006021, Revision
28、 d0.5, March 19, 2007, 1394 Trade Association. SSDP Goland et. al., Simple Service Discovery Protocol/1.0 Operating without an Arbiter , October 28, 1999, IETF UPNP UPnPtm Device Architecture 1.0, Version 1.0.1, 2 December 2003, UPnP Forum. BasicDev Basic: 1.0 Device Definition Version 1.0 for UPnPt
29、mVersion 1.0 12 December 2002, UPnP Forum. 2.2 Informative References 20 CEA-775-B, DTV 1394 Interface Specification, July 2004 21 AV/C Digital Interface Command Set General Specification, version 3.0, April 15, 1998, 1394 Trade Association. 8CEA-2027-B 22 Firewire System Architecture, 2ndEd., IEEE
30、1394a, published by Mindshare, Inc. and Addison Wesley, July 2002. ZC Daniel H. Steinberg, Stuart Cheshire, “Zero Configuration Networking: The Definitive Guide,” First Edition December 2005 , ISBN: 0-596-10100-7, (http:/ Bridge1 IEEE 1394 Bridged over Coaxial Cable Part 1: MAC and PHY, TS 2006019,
31、Revision 1.0b, March 15,2007, 1394 Trade Association. BridgeArch IEEE 1394 Bridged over Coaxial Cable Requirements and Architecture, Revision 2, April 6, 2007, 1394 Trade Association. 2.3 Normative Reference Acquisition 1394TA Standards: Contact the 1394 Trade Association (TA), 1111 South Main Stree
32、t, Suite 100, Grapevine, TX, USA; Phone 817-410-5750; Fax 817-410-5752; Internet http:/www.1394ta.org The documents cited as IEEE 1394 Bridged over Coaxial Cable may be obtained from CEA by contacting standardsCE.org. ANSI/CEA Standards: Global Engineering Documents, World Headquarters, 15 Inverness
33、 Way East, Englewood, CO USA 80112-5776; Phone 800-854-7179; Fax 303-397-2740; Internet http:/; E-mail ECMA Documents: ECMA International, Rue de Rhone 114, CH-1204, Geneva; Phone +41 22 849 6000; Fax +41 22 849 6001 IETF Documents: Internet Engineering Task Force (IETF) Secretariat, c/o Corporatio
34、n for National Research Initiatives, 1895 Preston White Drive, Suite 100, Reston, VA 20191-5434, USA; Phone 703- 620-8990; Fax 703-620-9071; Internet www.ietf.org, IETF RFCs may be downloaded from www.ietf.org/rfc.html, IETF Internet drafts may be downloaded from www.ietf.org/ID.html World Wide Web
35、Consortium Documents: World Wide Web Consortium (W3C); Internet http:/www.w3.org/ UPnPtmDocuments 9CEA-2027-B UPnP Forum, http:/www.upnp.org/ 2.4 Definitions 2.4.1 Conformance Several keywords are used to differentiate levels of requirements and optionality, as follows: shall: A keyword that indicat
36、es a mandatory requirement. Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard. should: A keyword that denotes flexibility of choice with a strongly preferred alternative. Equivalent to the phrase “is recomme
37、nded.” may: A keyword that indicates flexibility of choice with no implied preference. 2.4.2 Glossary The following terms are used in this standard: 2027 Device: A CEA-2027-B compliant physical device 2027 File: An XML formatted file that contains descriptions of various properties of a service devi
38、ce to be controlled and the Logical Unit(s) it contains or is associated with. AVC Device Type: A 32 bit word where each bit represents a different category of AV/C Device type as defined by value in Table 5.3-1 Subunit type encoding on page 9 in Section 5.3.3 of reference 2021. There are 32 possibl
39、e values,0x0 to 0x1F, each represented by a bit. So bit 0 represents Video Monitors, bit 3 Disc recorder/player (audio or video), bit 4 Tape recorder/player (audio or video), bit 5 Tuners, bit 7 Video cameras. These are the current active device definitions. Bridge: A device which allows 1394 local
40、clusters to be connected over an extended length. (1394a cables are at a maximum of 4.5 m in length. A 1394 local cluster is a group of devices which are interconnected via a single local run of cables.). Client Device: A device, or group of devices, consisting of a Renderer and a means of providing
41、 user input (such as a remote control unit (RCU), front panel keys or a mouse). Control Frame: An XHTML object returned by a Logical Unit in response to a specific GET command from a network controllers browser. This object provides access to the controllable functions in a Logical Unit. 10CEA-2027-
42、B Controlled Device: A device being controlled, which contains a web server and various service functions; also called Service Device. Controller: The controller is responsible for managing interactions with the user, including formation of the Top-Level UI. In a DTV, the Controller is typically par
43、t of the control software. Also called “network controller” or “controller device”. Digital Television (DTV): A device that receives, decodes, and presents audio and video material that has been transmitted in a compressed form. The device can be a single unit, or it can be constructed from a number
44、 of individual components (e.g., a digital terrestrial set-top box and an analog television; or a PC and attached monitor; or a handheld unit and associated display). Icon: A graphic object returned by a Logical Unit in response to a specific GET command from a network controllers browser. This obje
45、ct contains a bitmapped icon for the controlled device. L3 Bridge: A bridge that uses protocols and methods above the MAC and PHY layer to interconnect two or more local 1394 clusters over an extended distance. Logical Unit: A Logical Unit is an abstraction of a Device (or part of a device or a grou
46、p of devices) and its associated services. Logical Units are the entities that are networked and for which a UI is served. Each Logical Unit presents its user interface to a browser via a server. Node Unique Identifier: Abbreviated nuid. It is a 16 digit hexadecimal ASCII value for the 64-bit node u
47、nique identifier associated with a 1394 device, see page 415 of 22. It is frequently termed the global unique identifier and abbreviated as guid. Proxy Code: This is code that resides in one device and provides a portion of the UI and/or control function for another device on the network. Push Metho
48、d: A method of providing exception information (i.e. for unusual events) from a Logical Unit by creating a continuous status update link. Renderer: A device, or group of devices, consisting of a decoder and a display unit. Service Banner: An XHTML object returned by a Logical Unit in response to a s
49、pecific GET command from a network controllers browser. The service banner contains user readable information related to a current content stream. Service Device: A device being controlled, which contains a web server and various service functions; also called Controlled Device or Logical Unit. Status Frame: An XHTML object returned by a Logical Unit in response to a specific GET command fr
