《CEA-2027-A-2006.pdf》由会员分享，可在线阅读，更多相关《CEA-2027-A-2006.pdf（58页珍藏版）》请在三一文库上搜索。
1、 ANSI/CEA Standard A User Interface Specification for Home Networks Using Web-based Protocols ANSI/CEA-2027-A July 2006 NOTICE CEA Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchaser
2、s, 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 respect preclude any member o
3、r 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 CEA members, whether the stand
4、ard 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 patent owner, nor does it ass
5、ume 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 this standard, no position is t
6、aken 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 desiring to obtain such a lic
7、ense. 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 Standard and the IEC document can b
8、e 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 applicability of regulatory limitat
9、ions before its use. (Formulated under the cognizance of the CEA R7 Home Network Committee.) Published by CONSUMER ELECTRONICS ASSOCIATION 2006 Technology http:/www.w3.org/TR/1998/REC-DOM-Level-2-Core-20001113 -,-,- CEA-2027-A 5 11 1394TA Document 2002010 “A/VC Connection and Compatibility Managemen
10、t Specification 1.1”, January 2003 12 CEA-775.1, Web-enhanced DTV 1394 interface specification, February 2002 13 CR-css-tv-20030514 CSS TV Profile 1.0, W3C Candidate Recommendation 14 May 2003 14 REC-DOM-Level-2- 20001113 Document Object Model (DOM) Level 2 Style Specification, Version 1.0, W3C Reco
11、mmendation 13 November, 2000; http:/www.w3.org/TR/1998/REC-DOM-Level-2-Style-20001113 15 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 Profil
12、e, W3C Candidate Recommendation, 25 February 2004. Available at http:/www.w3.org/TR/2004/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
13、Recommendation 25 February 2004 http:/www.w3.org/TR/2004/CR-CSS21-20040225 19 Cascading Style Sheets, level 2 “CSS2 Specification” W3C Recommendation 12-May-1998 http:/www.w3.org/TR/1998/REC-CSS2-19980512 2.2 Informative References 20 CEA-775-B, DTV 1394 Interface Specification, July 2004 21 AV/C Di
14、gital Interface Command Set General Specification, version 3.0, April 15, 1998, 1394 Trade Association. 22 Firewire System Architecture, 2nd Ed., IEEE 1394a, published by Mindshare, Inc. and Addison Wesley, July 2002. 2.3 Normative Reference Acquisition 1394TA Standards: Contact the 1394 Trade Assoc
15、iation (TA), 1111 South Main Street, Suite 100, Grapevine, TX, USA; Phone 817-410-5750; Fax 817-410-5752; Internet http:/www.1394ta.org ANSI/CEA Standards: Global Engineering Documents, World Headquarters, 15 Inverness Way East, Englewood, CO USA 80112-5776; Phone 800-854-7179; Fax 303-397-2740; Int
16、ernet http:/; E-mail ECMA Documents: ECMA International, Rue de Rhone 114, CH-1204, Geneva; Phone +41 22 849 6000; Fax +41 22 849 6001 -,-,- CEA-2027-A 6 IETF Documents: Internet Engineering Task Force (IETF) Secretariat, c/o Corporation for National Research Initiatives, 1895 Preston White Drive,
17、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 Consortium Documents: World Wide Web Consortium (W3C); Internet
18、 http:/www.w3.org/ 2.4 Definitions 2.4.1 Conformance Several keywords are used to differentiate levels of requirements and optionality, as follows: may: A keyword that indicates flexibility of choice with no implied preference. shall: A keyword that indicates a mandatory requirement. Designers are r
19、equired 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 recommended.” 2.4.2 Glossary The following terms a
20、re used in this standard: 2027 File: An XML formatted file which contains descriptions of various properties of a service device to be controlled and the Logical Unit(s) it contains. Client Device: A device, or group of devices, consisting of a Renderer and a means of providing user input (such as a
21、 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. Controlled Device: A device being
22、 controlled, which contains a web server and various service functions; also called Service Device. Controller The functional part of the Client Device that is responsible for managing interactions with the user, including formation of the Top-Level UI. In a DTV, the controller is typically part of
23、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 of i
24、ndividual components (e.g., a digital terrestrial set-top box -,-,- CEA-2027-A 7 and an analog television; or a PC and attached monitor; or a handheld unit and associated display). Home Network Configuration Protocol (HNCP): A method to detect and resolve duplicate IP address assignments for CEA-775
25、.1 devices. Icon: A graphic object returned by a Logical Unit in response to a specific GET command from a network controllers browser. This object contains a bitmapped icon for the controlled device. Logical Unit: These are the items that are networked and for which a GUI is served. Each Logical Un
26、it presents its user interface to a web browser via a web server. A Logical Unit is an abstraction of a controlled service device (or part of a device or a group of devices) and its associated services. Node Unique Identifier: Abbreviated nuid. It is a 16 digit hexadecimal ASCII value for the 64-bit
27、 node unique 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 which provides a portion of the UI and/or control function for another device on the network. P
28、ush Method: 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 respon
29、se to a specific 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, this contains a web server and various service functions; also called Controlled Device or Logical Un
30、it. Status Frame: An XHTML object returned by a Logical Unit in response to a specific GET command from a network controllers browser. This object describes the state and other general information about the Logical Unit for display on the UI. Status Return: An XML element returned by a Logical Unit
31、in response to a specific polled GET command from a network controllers browser during an open control action. This object indicates whether the control action is complete or not; and if it is complete, how it was ended; and if not, suggests limits on where the user may browse based on device availa
32、bility. Top-Level UI: The full composite user interface created by the controller. Transparent Frame: An XHTML object returned by a Logical Unit in response to a specific GET command from a network controllers browser. This object provides information that is to be displayed on top of existing displ
33、ays and is used to convey exception information in the Push Method (see section 6). -,-,- CEA-2027-A 8 AVC Device Type: This is 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 section5.3.3 in ref 2
34、1. There are 32 possible 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 Type Id: Often rep
35、resented as type_id. It is an ASCII encoded hexadecimal 8 bit, 16 bit, 24 bit, value which encodes the subunit type and subunit id for a 1394 device as in section 5.3.3 AV/C address (subunit_type, subunit_ID) on page 9 of reference 21. Underlying Medium: The wires and I/O ports that deliver content
36、between networked devices. The Underlying Medium may consist of one or more combinations of non-network connections (i.e. point-to-point connections) and network connections between devices. 2.4.3 Abbreviations The following are abbreviations that are used in this standard: A/V Audio/Video A/VC Audi
37、o/Video Control AVHDD Audio/Video Hard Disk Drive CGI Common Gateway Interface CSS Cascading Style Sheets DHCP Dynamic Host Configuration Protocol DNS Domain Name Server DRM Digital Rights Management DTV Digital Television DVD Digital Versatile Disk EPG Electronic Program Guide GIF Graphics Intercha
38、nge Format GUI Graphical User Interface HNCP Home Network Configuration Protocol I/O Input/Output NIU Network Interface Unit PSIP Program and System Information Protocol RCU Remote Control Unit XML Extensible Markup Language XHTML Extensible HyperText Markup Language -,-,- CEA-2027-A 9 HTTP HyperTex
39、t Transfer Protocol IEEE Institute of Electrical and Electronics Engineers OSD On-Screen Display STB Set-Top Box UI User Interface 3 Architectural Model (Informative) The building block of this UI is focused on a collection of commonly controlled and related services called the Logical Unit. Each Lo
40、gical Unit presents its user interface to a web browser via a web server. A Logical Unit can represent: ? A single physical device ( e.g., a DVD player) ? A subset of the functions in a physical device (e.g., a tuner inside a DTV) ? A set of functions that span more than one physical device (e.g., a
41、udio control that includes a pre-amp and a power amplifier) Figure 3.1 shows 4 different Logical Units depicted by the shaded grey rectangular areas. These Logical Units are resident in three physical devices. Most Logical Units reside in a single device, some occupy the entire physical device, and
42、a few Logical Units may span several devices. Figure 3.1 Logical Units and Physical Devices -,-,- CEA-2027-A 10 The basic GUI and Remote Control Architecture for this specification are illustrated in Figure 3.2, which depicts two devices: an HDTV and an AVHDD. The HDTV contains a Web Browser for pre
43、sentation, and 3 Logical Units: 1. A controller to dispatch GUI control and form the top-level UI. 2. A TV tuner and EPG/PSIP server. 3. The TV decoders for picture and audio. The AVHDD functions as both a recorder and a content player. The figure may appear to be cluttered by many Web Servers, but
44、note that three of the function groups are contained within the HDTV. Multiple Web Servers can simply be multiple incarnations of a single web server in the HDTV. A Logical Unit refers to a virtual subunit, and may merely be a subset of a physical device. It presents a separately controllable set of
45、 functions (see notation in Section 4.6). There are 5 Logical Unit types: 1. Streaming Media Sources (“SourceOnly”) 2. Streaming Media Sinks (“SinkOnly”) 3. Streaming Media Sink and Source (“Either”) 4. Not a Streaming Media Sink or Streaming Media Source (“Neither”) 5. Not intended to be visible to
46、 the user (“NotVisible”) The type 5 controllers are ignored by all other controllers and extensions can be done by adding new Tag Fields with new definitions. Legacy devices will ignore the new Tag Fields. The 2027 File returned from each physical device describes Logical Units defined in that devic
47、e and their types. (See Section 4.6 for a complete description of the 2027 File.) The devices in Figure 3.2 may be defined as: The Picture Device type 1. The Tuner type 2. The AVHDD Logical Unit type 3. A web site - type 4. A controller Logical Unit is not visible and is of type 5. (A controller dev
48、ice is generally paired with a Web Browser and ignores all other controller devices.) -,-,- CEA-2027-A 11 Figure 3.2 Example Architecture of Logical Units and Physical Devices Please note that the controller depicted is more than just a web server. The controller need not actually be a web server or contain a web server. Please see the requirements in Section 4. 4 Requirements (Normative) 4.1 Networked Physical Devices A physical device shall consist of zero or more client we