1、American National StandardDeveloped byfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Universal Remote ConsoleANSI INCITS 389-2005ANSIINCITS389-2005Copyright American National Standards I
2、nstitute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,
3、-ANSIINCITS 389-2005American National Standardfor Information Technology Protocol to Facilitate Operation ofInformation and Electronic Productsthrough Remote and AlternativeInterfaces and Intelligent Agents Universal Remote ConsoleSecretariatInformation Technology Industry CouncilApproved August 12,
4、 2005American National Standards Institute, Inc.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard requires review by ANSI that therequirem
5、ents for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement me
6、ans much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclu
7、de anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any
8、 American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on th
9、e titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Sta
10、ndards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2005 by Information Technology Industry Council (ITI
11、)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have reques
12、ted that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of pub
13、lication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is
14、 made or impliedthat licenses are not required to avoid infringement in the use of this standard.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Stand
15、ards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ContentsPageForeword .ivIntroduction .vi1 Scope. 12 Conformance . 13 Normative References . 24 Terms, Definitions and Abbreviated Terms 25 Overview 105.1 General 1
16、05.2 Major Components of the URC framework 135.3 Essential Components. 145.4 Target URC Synchronization . 155.5 URC and Component Interaction. 156 Universal Remote Console (URC) Requirements 166.1 General 166.2 Discovery Management . 166.2.1 General 166.2.2 Support for Target Discovery. 166.2.3 Retr
17、ieving Documents from the Target 166.2.4 Interpretation of the Target Description . 166.2.5 Invocation of a Targets Locator Function 166.3 Session Management 176.3.1 General 176.3.2 URC Open Session Request . 176.3.3 URC Suspend Session Request 176.3.4 URC Resume Session Request. 176.3.5 URC Close S
18、ession Event. 176.3.6 Support for Abort Session Event 186.3.7 Established Connection . 186.3.8 Support for Session Forwarding 186.4 Socket Management 186.4.1 General 186.4.2 Synchronization of Variables and Calculation of Variable Values . 186.4.3 Command and Synchronization of Command State 196.4.4
19、 Notification Receipt and Acknowledgment. 186.4.5 Support for Socket Element Dependencies. 206.4.6 User Response Timeouts 206.5 Target-URC Network Link (TUNL) on the URC . 206.6 Resource-URC Network Link (RUNL) on the URC 216.6.1 General 21i6.6.2 Locating Resource Services 216.7 User Interface Gener
20、ation 21Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHSPage7 Target Components and Requirements. 227.1 Discovery Management . 227.1.1 General 227.1.2 Support for Document Deployment
21、. 227.1.3 Target Description . 227.1.4 Locator Functions 237.2 User Interface Socket 237.2.1 General 237.2.2 Socket Elements 237.2.3 Documents for Sockets 247.3 Socket Description. 247.4 Target Resources 257.4.1 User Interface Implementation Descriptions (UIIDs) . 257.4.2 Atomic Target Resources 267
22、.4.3 Core Resources. 277.4.4 Conformance in a Natural Language. 287.5 Session Management 287.5.1 Support for URC Open Session Request 287.5.2 Support for URC Suspend Session Request. 287.5.3 Support for URC Resume Session Request 297.5.4 Support for URC Close Session Event 297.5.5 Abort Session Even
23、t 297.5.6 Established Connection . 297.5.7 Session Forwarding . 307.6 Socket Management 307.6.1 General 307.6.2 Synchronization of Variables and Calculation of Variable Values . 307.6.3 Command and Synchronization of Command State 317.6.4 Notification Reception and Acknowledgment 317.6.5 URC Side In
24、terpretation of Socket Element Dependencies 327.6.6 User Response Timeouts 327.7 Target-URC Network Link (TUNL) on the Target 328 User Interface Implementation Descriptions (UIIDs) . 339 Supplemental Resources. 339.1 General 339.2 Formats for Supplemental Resources . 3410 Networks 3410.1 General 341
25、0.2 Target-URC Network (TUN) 3510.2.1 General 3510.2.2 Unique Network Identifier 3510.2.3 Support for Discovery 35ii -,-,-Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page10.2
26、.4 Support for Document Deployment 3510.2.5 Support for Session Management 3610.3 Resource-URC Network (RUN) . 3611 Security and Privacy Considerations . 3711.1 Overview 3711.2 General 3711.3 URC considerations . 3811.4 Target considerations. 3811.5 Network considerations 38Figure 1 Overall structur
27、e and components of the URC framework. 12Tables1 Overview of components, their functions and references to further information. . 102 Overview of Resource types defined by this standard and ANSI INCITS 393-2005. 11Annex A XML Code Examples . 39A.1 Target Description Example. 39A.2 Socket Description
28、 Example 41A.3 Core Presentation Template Example . 42A.4 Resource Sheet Example 43iiiCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Foreword (This foreword is not part of Ameri
29、can National Standard ANSI INCITS 389-2005.)This American National Standard is one in a series on the operation of informationand electronic products through remote and alternative interfaces and intelligentagents. The goal of this standard is to provide a framework of components that com-bine to en
30、able remote User Interfaces and remote control of network-accessible elec-tronic devices and services through a Universal Remote Console (URC).This document contains one annex. It is informative and is not considered part of thestandard.Requests for interpretation, suggestions for improvement or add
31、enda, or defect re-ports are welcome. They should be sent to the InterNational Committee for Informa-tion Technology Standards (INCITS), ITI, 1250 Eye Street, NW, Suite 200,Washington, DC 20005.This standard was processed and approved for submittal to ANSI by the InterNation-al Committee for Informa
32、tion Technology Standards (INCITS). Committee approvalof this standard does not necessarily imply that all committee members voted for itsapproval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name
33、 of RepresentativeAIM Global Dan Mullen Charles Biss (Alt.)American National Standards Institute . Lisa Rajchel Apple Computer, Inc. David Michael Electronic Industries Alliance Edward Mikoski, Jr. Henry Cuschieri (Alt.)EMC Corporation Gary Robinson Farance, Inc. Frank Farance Hewlett-Packard Compan
34、y. Karen Higginbottom Steve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation Ronald F. Silletti Institute for Certification of Computer Professionals. Kenneth M. Zemrowski Thomas Kurihara (Alt.)IEEE . Judith Gorman Richard Holleman (Alt.)Robert Pritchard (Alt.)Intel Norbert Mikula Dave Thewlis (Alt.)
35、Philip Wennblom (Alt.)Lexmark International . Don Wright Dwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation . Isabelle Valet-Harper Don Stanwyck (Alt.)Mike Ksar (Alt.)National Institute of Standards b) Functions implemented in assistive technology devices;c) Devices that were specially built
36、 to function as Universal Remote Consoles; ord) Devices that were built to function primarily as Remote Consoles for a particularfamily of products (e.g., a Remote Console designed to be part of a home audiovisualsystem), but could also serve to control any other devices compatible with this stan-da
37、rd.Universal Remote Consoles work like universal remote controls today, except that:a) They have much greater function and scope:b) They synchronize with the Target in both directions (i.e., they can display the cur-rent status of the Target);c) They dont need to be programmed by the user (since the
38、y will automatically dis-cover devices that are controllable in the users vicinity, and discover the abstracteduser interface of the Targets and present it in the way preferred by the user and his/her URC); andd) They can be used out of sight of the product they are controllingThe URCs could be all
39、visual, all tactile, or all verbal in nature (or any combinationthereof), because this standard specifies the content of a Target user interface inde-pendently from the form in which it is presented. Thus, URCs could be designed thatan individual could talk to them. Through the URC, the user could t
40、herefore havespeech access to any compatible Target listed above, even if the Target does nothave any voice recognition or voice control functionality. viCopyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted witho
41、ut license from IHS-,-,-A person might, therefore, be able to say to their URC, “Record channel 12 and showme Law and Order“. Or they could be laying in bed and say, “Set the alarm to 6:30AM, start brewing the coffee at 6:00 AM, and now set the home security system toactive“. Or, if ones spouse is a
42、lready asleep, a person could pick up their PDA, orany other compatible URC device, and accomplish these same tasks silently eitherby calling up control panels or by issuing the instructions in writing. (The URC frame-work does not provide the natural language control, but would provide all of the i
43、nfor-mation and control necessary for control by a natural-language-processing URC.)viiAMERICAN NATIONAL STANDARD ANSI INCITS 389-2005American National Standard for Information Technology Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interface
44、s and Intelligent Agents Universal Remote Console 11 Scope This standard is part of a set of standards to facilitate operation of information and electronic products through remote and alternative interfaces and intelligent agents. The purpose of this standard is to provide a framework of components
45、 that combine to enable remote User Interfaces and remote control of network-accessible electronic devices and services through a Universal Remote Console (URC). This standard provides an overview of the URC framework and its components. The following additional standards are provided separately and
46、 specify specific languages and components of the URC framework. ANSI INCITS 390-2005: Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - User Interface Socket Description ANSI INCITS 391-2005: Protocol to Facili
47、tate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - Presentation Template ANSI INCITS 392-2005: Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agent
48、s - Target Description ANSI INCITS 393-2005: Protocol to Facilitate Operation of Information and Electronic Products through Remote and Alternative Interfaces and Intelligent Agents - Resource Description 2 Conformance A conforming Target shall implement: At least one Target-URC Network Link as spec
49、ified in 7.7; A Target Description, as specified in 7.1.3; One or more Sockets that, when considered together, cover the full functionality of the target, as specified in 7.2; The Core Resources required to conform in at least one natural language (see 7.4.4); and The Target components and requirements as specified in clause 7. Copyright American National Standards Institute
