1、 ANSI/CTA Standard Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE) ANSI/CTA-2014-B (Formerly ANSI/CEA-2014-B) January 2011 NOTICE Consumer Technology Association (CTA) Standards, Bulletins and other technical publications are designed to serve th
2、e public interest through eliminating misunderstandings between 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
3、, Bulletins and other technical publications shall not in any respect preclude any member or nonmember of the Consumer Technology Association from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards,
4、 Bulletins and other technical publications preclude their voluntary use by those other than Consumer Technology Association members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by the Consumer Technolog
5、y Association in accordance with the American National Standards Institute (ANSI) patent policy. By such action, the Consumer Technology Association does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard, Bulletin or other techn
6、ical 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 taken with respect to the validity of this claim or of any patent rights in connection
7、 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 license. Details may be obtained from the publisher. This document does not purport to a
8、ddress all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this document to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. This document is copyr
9、ighted by the Consumer Technology Association and may not be reproduced, in whole or part, without written permission. Federal copyright law prohibits unauthorized reproduction of this document by any means. Organizations may obtain permission to reproduce a limited number of copies by entering into
10、 a license agreement. Requests to reproduce text, data, charts, figures or other material should be made to the Consumer Technology Association. (Formulated under the cognizance of the CTA R7 Consumer Electronics Networking Committee.) Published by CONSUMER TECHNOLOGY ASSOCIATION 2015 Technology htt
11、p:/www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113 12 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/2000/REC-DOM-Level-2-Style-20001113 13 REC-DOM-Level-2-20001113 Document Object Model (DOM) L
12、evel 2 Events Specification, Version 1.0, W3C Recommendation 13 November 2000; http:/www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113 14 REC-DOM-Level-2-20030109 Document Object Model (DOM) Level 2 HTML Specification, Version 1.0, W3C Recommendation 9 January 2003; http:/www.w3.org/TR/2003/REC-DOM
13、-Level-2-HTML-20030109 16 Graphics Interchange Format version 89a, (c)1987,1988,1989,1990, CompuServe Incorporated, Columbus, Ohio, http:/www.w3.org/Graphics/GIF/spec-gif89a.txt 17 Portable Network Graphics (PNG) Specification (Second Edition), W3C Recommendation 10 November 2003, http:/www.w3.org/T
14、R/PNG 18 Interface KeyEvent, W3C Working Draft, 23 September 1999, http:/www.w3.org/TR/1999/WD-DOM-Level-2-19990923/events.html#Events-KeyEvent 19 RemoteUIServerDevice:1 Device Template Version 1.01,UPnP Standardized DCP, Sept. 2004, http:/www.upnp.org/standardizeddcps/documents/RemoteUIServerDevice
15、1.0.pdf 20 RemoteUIServer:1 Service Template Version 1.01, UPnP Standardized DCP, September 2004, http:/www.upnp.org/standardizeddcps/documents/RemoteUIServerService1.0.pdf 21 RemoteUIClientDevice:1 Device Template Version 1.01,UPnP Standardized DCP, Sept. 2004, http:/www.upnp.org/standardizeddcps/d
16、ocuments/RemoteUIClientDevice1.0.pdf 22 RemoteUIClient:1 Service Template Version 1.01, UPnP Standardized DCP, September 2004, http:/www.upnp.org/standardizeddcps/documents/RemoteUIClientService1.0.pdf 23 Extensible Markup Language (XML) 1.0 (Third Edition), W3C Recommendation 04 February 2004, http
17、:/www.w3.org/TR/2004/REC-xml-20040204/ 24 Transport Layer Security Working Group, SSL Protocol Version 3.0, November 18, 1996, http:/www.mozilla.org/projects/security/pki/nss/ssl/draft302.txt CEA-2014-B 5 25 IETF RFC 1123, Requirements for Internet Hosts - Application and Support, Oct 1989, http:/ww
18、w.ietf.org/rfc/rfc1123.txt 27 Cascading Style Sheets Level 2 (CSS2), W3C Recommendation, 12 May 1998, http:/www.w3.org/TR/1998/REC-CSS2-19980512/ 28 Cascading Style Sheets, level 2 revision 1 (CSS 2.1), W3C Candidate Recommendation 23 April 2009, http:/www.w3.org/TR/2009/CR-CSS2-20090423/ 31 JPEG Fi
19、le Interchange Format, Version 1.02, Eric Hamilton, C-Cube Microsystems, September 1, 1992. http:/www.w3.org/Graphics/JPEG/jfif3.pdf 32 IETF RFC 3268, Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS), http:/www.ietf.org/rfc/rfc3268.txt 33 ConnectionManager:1 Service
20、 Template Version 1.01, UPnP Standardized DCP, June 2002, http:/www.upnp.org/standardizeddcps/documents/ConnectionManager1.0.pdf 34 AVTransport:2 Service Template Version 1.01, UPnP Standardized DCP, May 2006, http:/www.upnp.org/specs/av/UPnP-av-AVTransport-v2-Service-20060531.pdf 35 The XMLHttpRequ
21、est Object, W3C Working Draft, 19 November 2009, http:/www.w3.org/TR/2009/WD-XMLHttpRequest-20091119/ 36 CSS 3 Basic User Interface Module, W3C Candidate Recommendation 11 May 2004, http:/www.w3.org/TR/2004/CR-css3-ui-20040511/ 37 UPnP Device Architecture 1.1, 2008, UPnP forum, http:/www.upnp.org/sp
22、ecs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf 38 REC-DOM-Level-2-20001113 Document Object Model (DOM) Level 2 Views Specification, Version 1.0, W3C Recommendation 13 November 2000; http:/www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/ 39 Element Traversal Specification, W3C Recommendation, 22 De
23、cember 2008, http:/www.w3.org/TR/2008/REC-ElementTraversal-20081222/ 40 ISO 3166-1, Codes for the representation of names of countries and their subdivisions - Part 1:Country codes, http:/www.iso.org/iso/english_country_names_and_code_elements 41 Scalable Vector Graphics (SVG) Tiny 1.2 Specification
24、, W3C Recommendation, 22 December 2008, http:/www.w3.org/TR/2008/REC-SVGTiny12-20081222/ 42 ETSI TS 102 822, “TV Anytime” part 3 Metadata, http:/www.etsi.org/website/technologies/tvanytime.aspx 43 ANSI/CEA-766-C, U.S. and Canadian Rating Region Tables (RRT) and Content Advisory Descriptors for Trans
25、port of Content Advisory Information Using ATSC Program and System Information Protocol (PSIP), April 2008. 44 ISO/IEC15938-5, MPEG-7 Part 5 Multimedia description schemes, 2003. 45 ETSI EN 300 468, Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems, 2003. 46
26、 IETF RFC 2617, HTTP Authentication: Basic and Digest Access Authentication, http:/www.ietf.org/rfc/rfc2617.txt 47 IETF RFC 5019, The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments, http:/www.ietf.org/rfc/rfc5019.txt CEA-2014-B 6 48 ETSI TS 102 809 v1.1.1,
27、 “DVB signalling and carriage of interactive applications and services in Hybrid broadcast/broadband environments”, January 2010, http:/www.etsi.org/deliver/etsi_ts/102800_102899/102809/01.01.01_60/ts_102809v010101p.pdf 49 ATSC A/53 Part 4, MPEG-2 Video System Characteristics, 7 August 2009, http:/w
28、ww.atsc.org/standards/a_53-Part-4-2009.pdf 50 ISO 8601, Data elements and interchange formats - Information interchange -Representation of dates and times, 2004. 51 IETF RFC 2397, The “data“ URL scheme, http:/www.ietf.org/rfc/rfc2397.txt 52 CSS Color Module Level 3, W3C Working Draft, 21 July 2008,
29、http:/www.w3.org/TR/2008/WD-css3-color-20080721/ 53 ISO 639-2, Codes for the representation of names of languages- Part 2: Alpha-3 code, 1998, http:/www.loc.gov/standards/iso639-2/php/code_list.php 2.2 Informative References The following references provide relevant information for the CEA-2014 stan
30、dard. 54 Universal Remote Console over HTTP Protocol Specification. URC Consortium. 55 IETF RFC 3986, Uniform Resource Identifiers (URI): Generic Syntax, January 2005, http:/www.ietf.org/rfc/rfc3986.txt 56 IETF RFC 2732, Format for Literal IPv6 Addresses in URLs, December 1999, http:/www.ietf.org/r
31、fc/rfc2732.txt 57 Associating Style Sheets with XML documents Version 1.0, W3C Recommendation 29 June 1999, http:/www.w3.org/TR/xml-stylesheet/ 58 Avoiding click-to-activate, M. Wilton-Jones, http:/www.howtocreate.co.uk/noclicktoactivate.html 59 DVB-SI CA_System_ID allocation table, http:/ 60 IETF R
32、FC 1321, The MD5 Message-Digest Algorithm, http:/www.ietf.org/rfc/rfc1321.txt CEA-2014-B 7 2.3 Reference Acquisition 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; Internet http:/; E-mail
33、 ECMA Documents ECMA International, Rue de Rhne 114, CH-1204, Geneva; Phone +41 22 849 6000; Fax +41 22 849 6001 IETF Documents Internet Engineering Task Force (IETF) Secretariat, c/o Corporation for National Research Initiatives, 1895 Preston White Drive, Suite 100, Reston, VA 20191-5434, USA; Pho
34、ne 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 http:/www.w3.org/ DLNA Documents DLNA Admi
35、nistration, C/O VTM, Attn: Membership Services. 5440 SW Westgate Drive, Suite 217, Portland, OR 97221; USA Phone: 503.297.0426, Fax: 503.297.1090, Internet: http:/www.dlna.org/; Email: admindlna.org; Reference Acquisition: http:/www.dlna.org/industry/certification/guidelines/Order_the_DLNA_Guideline
36、s.pdf UPnP Documents UPnP Forum, http:/www.upnp.org/ CEA-2014-B 8 3 Conventions and Definitions 3.1 Conventions The following keywords are used to differentiate levels of requirements and optionality, as follows: SHALL - A keyword that indicates a mandatory requirement. Designers are required to imp
37、lement all such mandatory requirements to assure interoperability with other products conforming to this standard. Equivalent to the term “MANDATORY” OR “(MAN)”. SHOULD - A keyword that denotes flexibility of choice with a strongly preferred alternative. Equivalent to the term “RECOMMENDED”. MAY - A
38、 keyword that indicates flexibility of choice with no implied preference. Equivalent to the term “OPTIONAL”. Obsolete - Indicates a requirement that has been either replaced or removed in this revision of the specification (as noted). Devices that need to remain compatible with previous revisions of
39、 this specification may be required to implement the previously stated behavior(s). It is expected that replaced requirements will support backward compatibility with previous revisions of CEA-2014. Updated - Indicates requirements with (minor) editorial changes and/or complementary information to t
40、he behavior specified by previous revisions of this specification. The changes between CEA-2014 revision A and B are informatively described in Annex BB. yellow highlighting - used to draw special attention to subtle but important distinctions. All properties for the Javascript APIs defined in this
41、document, excluding Annex I, SHALL be read-write, unless specifically marked with keyword “readonly”. 3.2 Definitions and Acronyms For the purposes of this standard, the following definitions apply: 2-Box Model - Short for 2-Box Remote UI Configuration Model as described in Section 4.1.2. 3-Box Mode
42、l - Short for 3-Box Remote UI Configuration Model as described in Section 4.1.3. 3rdParty Notification - The Remote UI Server is able to send a notification message that appears on the Remote UI Client at any time, without the need to interact with the Remote UI Server, e.g. to receive caller ID mes
43、sages, printer status messages, etc. A/V Control Point (AVCP) - This is the unit of functionality that is responsible for setting up the connection between a compatible Digital Media Server and an A/V renderer. A/V Client/Renderer (AVC) - A device (or a group of cooperating devices) that is responsi
44、ble for the actual rendering/playback of A/V content. If this device is discoverable in an UPnP network, it is called a Digital Media Renderer (DMR). A/V Server (AVS) A device (or a group of cooperating devices) that offers A/V content. If this CEA-2014-B 9 device is discoverable in an UPnP network,
45、 it is called a Digital Media Server (DMS). Browser Area - The rectangular area as specified in Section 5.2.3 that the Remote UI Client has made available for rendering CE-HTML content served by a Remote UI Server. Digital Media Player (DMP) - A device (or a group of cooperating devices) that implem
46、ents an A/V Control Point and has an A/V renderer. Digital Media Renderer (DMR) - A device (or a group of cooperating devices) that implements the UPnP A/V MediaRenderer device template. Digital Media Server (DMS) - A device (or a group of cooperating devices) that implements the UPnP A/V MediaServe
47、r device template. i-Box Model - Short for i-Box Remote UI Configuration Model as described in Section 4.1.1. i-Box Server - A Level 0 Remote UI Server that does not reside in the same subnet as the Remote UI client. In-Session Notification - The Remote UI Server is able to send a notification messa
48、ge during a UI interaction to update the UI dynamically without the need to reload the XHTML-page. Remote UI - A user interface offered by an application running on a Remote UI Server that can be accessed via the network by one or more Remote UI Clients. Remote UI Client (RUIC) - A device (or a grou
49、p of cooperating devices) that provides a way of rendering and interacting with one or more remote user interfaces. Remote UI Server (RUIS) - A device (or a group of cooperating devices) that offers one or more Remote UIs. UI Control Point (UICP) - This is the unit of functionality that is responsible for setting up the connection betw
