ISO IEC 24752-1-2014 Information technology - User interfaces - Universal remote console - Part 1 General framework《信息技术 用户接口 通用远程控制台 第1部分 通用框架》.pdf

《ISO IEC 24752-1-2014 Information technology - User interfaces - Universal remote console - Part 1 General framework《信息技术 用户接口 通用远程控制台 第1部分 通用框架》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 24752-1-2014 Information technology - User interfaces - Universal remote console - Part 1 General framework《信息技术 用户接口 通用远程控制台 第1部分 通用框架》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology User interfaces Universal remote console Part 1: General framework Technologies de linformation Interfaces utilisateur Console distance universelle Partie 1: Cadre gnral INTERNATIONAL STANDARD ISO/IEC 24752-1 Reference number ISO/IEC 24752-1:2014(E) Second edition 2014-12-15 I

2、SO/IEC 2014 ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on

3、the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso

4、.org Web www.iso.org Published in Switzerland ISO/IEC 24752-1:2014(E) ISO/IEC 24752-1:2014(E)Contents Page Foreword iv Introduction v 1 Scope . 1 2 Conformance . 1 2.1 URC 1 2.2 Target 2 3 T erms and definitions . 3 4 Universal remote console (URC) requirements . 9 4.1 General . 9 4.2 Discovery mana

5、gement 10 4.3 Session management 11 4.4 Socket management.13 4.5 Target-URC network link on the URC .18 4.6 Resource-URC network link (RUNL) on the URC 18 4.7 User interface generation .19 4.8 Security and privacy requirements 20 5 Target components and requirements .20 5.1 Discovery management 20 5

6、.2 User interface socket 21 5.3 User interface socket description 22 5.4 Target resources .22 5.5 Session management 25 5.6 Socket management.29 5.7 Target-URC network link (TUNL) on the target 35 5.8 Security and privacy requirements 36 6 Supplemental resources 36 6.1 General 36 6.2 Third party sup

7、plemental resources 36 6.3 Supplemental resources are optional 36 6.4 Format of supplemental resources .36 6.5 Forms of resource services 36 6.6 Supplemental atomic resources 37 6.7 Supplemental resource sheets .37 6.8 Supplemental grouping resources 37 6.9 Supplemental grouping sheets .37 6.10 Supp

8、lemental user interface implementation descriptions (UIIDs) .38 7 Networks 38 7.1 General 38 7.2 Target-URC network (TUN).38 7.3 Resource-URC network (RUN) .40 8 Security and privacy considerations 40 8.1 General 40 8.2 URC considerations 41 8.3 Target considerations .41 8.4 Network considerations .

9、41 Annex A (informative) Security and privacy Example scenarios 42 Annex B (informative) XML code examples 43 Bibliography .44 ISO/IEC 2014 All rights reserved iii ISO/IEC 24752-1:2014(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Co

10、mmission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity.

11、ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee,

12、ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordanc

13、e with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. De

14、tails of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an

15、 endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee

16、 responsible for this document is ISO/IEC JTC 1, Information technology , SC 35, User interfaces. This second edition cancels and replaces the first edition (ISO/IEC 24752-1:2008), which has been technically revised. ISO/IEC 24752 consists of the following parts, under the general title Information

17、technology User interfaces Universal remote console: Part 1: Framework Part 2: User interface socket description Part 4: Target description Part 5: Resource description Part 6: Web service integrationiv ISO/IEC 2014 All rights reserved ISO/IEC 24752-1:2014(E) Introduction This is the second edition

18、of this part of ISO/IEC 24752. The main purpose of the revision is an alignment with recent developments in the web service area, in particular with the new ISO/IEC 24752-6, along with an overall simplification of the specified technologies. This part of ISO/IEC 24752 is one of a set of Internationa

19、l Standards to facilitate operation of information and electronic products through remote and alternative interfaces and intelligent agents. The purpose of ISO/IEC 24752-1 is to facilitate the development and deployment of a wide variety of devices (from different manufacturers) that can act as univ

20、ersal remote consoles (URCs) for an equally varied range of target devices and services (targets), also from different manufacturers. It allows users to control any number of information and electronic products in their environment. The targets include both devices and services. They can range from

21、things as simple as light switches and thermostats to more complex items such as audio-visual equipment, home appliances, in-car electronics, web services, and any other devices or services that can be controlled electronically (or via information technology). Targets can be in the same location as

22、the individual who desires to control the target through the URC, or at any distance from the URC/user as long as there is some type of network connection between the URC and the target. This is possible since a URC provides the user with all of the necessary controls as well as the prompts and othe

23、r information displayed by the target. The URCs could be software running on common mainstream devices such as personal computing and information technology devices (e.g. computers, laptops, tablet computers, smartphones, cell phones, or other telecommunications devices). They could also be function

24、s implemented in assistive technology devices, or they could be devices which were specially built to function as URCs. They could be devices which were built to function primarily as a remote console for a particular family of products (e.g. a remote console designed to be part of a home audio-visu

25、al system), but could also serve to control any other devices compatible with this part of ISO/IEC 24752. They are similar to the behaviour of universal remote controls today, except for the following: a) they have much greater function and scope, b) they synchronize with the target in both directio

26、ns (i.e. they can display the current status of the target), c) they do not need to be programmed by the user (since they will automatically discover devices that are controllable in a users vicinity, discover the abstracted user interface of the targets, and present it in the way preferred by the u

27、ser and their URC), and d) they can be used out of sight of the product they are controlling. The URCs could be all visual, all tactile, or all verbal in nature, or any combination thereof, because this International Standard specifies the content of a target user interface independently from the fo

28、rm in which it is presented. Thus, URCs could be designed that an individual could talk to and, through the URC, the user could have speech access to any compatible target listed above without any of these targets having any voice recognition or voice control functionality themselves. A person might

29、, therefore, be able to say to their URC, “Record channel 12 and show me Law and Order”. Or they could lie in bed and say, “Set the alarm to 6:30 AM, start brewing the coffee at 6:00 AM, and now set the home security system to active”. Or, if ones spouse is already asleep, a person could pick up the

30、ir smartphone or any other compatible URC device and accomplish these same tasks silently either by calling up control panels or by issuing the instructions in writing. NOTE The URC framework does not provide the natural language control, but would provide all of the information and control necessar

31、y for control by a natural language processing URC. Note that, although a URC implementation can involve hardware, requirements on this hardware such as safety and design requirements are not within the scope of this International Standard. ISO/IEC 2014 All rights reserved v ISO/IEC 24752-1:2014(E)

32、A more detailed overview of the URC framework is provided on the OpenURC Alliances website, at h t t p :/o p e nu r c . org/urc-overview. 6vi ISO/IEC 2014 All rights reserved Information technology User interfaces Universal remote console Part 1: General framework 1 Scope ISO/IEC 24752 is a multi-pa

33、rt International Standard that facilitates operation of information and electronic products through remote and alternative interfaces and intelligent agents. This part of ISO/IEC 24752 defines a framework of components that combine to enable remote user interfaces and remote control of network-acces

34、sible electronic devices and services through a universal remote console (URC). It provides an overview of the URC framework and its components. 2 Conformance 2.1 URC A conforming URC shall conform to the URC requirements as specified in Clauses 4 and 8. Table 1 summarizes the requirements on URCs.

35、Table 1 Summary of URC requirements Requirement (“A URC shall ”) See subclause Retrieve documents from a target, including recognition of MIME types 4.2.3 Interpret a target description so that it can identify a target and open a control session with one of its sockets 4.2.4 Support the invocation o

36、f a targets locator function 4.2.5 Support an open session request to a target 4.3.2 Support a URC close session event to a target 4.3.5 Support an abort session event from a target 4.3.6 Track connection status information from the underlying network (TUN) 4.3.7 Synchronize values of socket variabl

37、es 4.4.2 Request invocation of a socket command, including support for local parameters and command state updates 4.4.3 Receive and acknowledge notifications, including support for stacking notifications and their states 4.4.4 Synchronize actual indices of socket sets and elements 4.4.5 Support the

38、timeout attribute on notifications 4.4.7 Provide at least one target-URC network link (see 7.2 for TUN requirements) 4.5.1 Support reception and updating of dynamic atomic resources at runtime 4.5.2 Provide a concrete user interface for a control session with a targets socket 4.7 Implement the secur

39、ity and privacy functions available from the implemented TUNs 8.2 INTERNATIONAL ST ANDARD ISO/IEC 24752-1:2014(E) ISO/IEC 2014 All rights reserved 1 ISO/IEC 24752-1:2014(E) 2.2 Target A conforming target shall meet all requirements specified in Clauses 5 and 8. Table 2 summarizes the requirements on

40、 targets. Table 2 Summary of target requirements Requirement (“A target shall ”) See subclause Have an instance identifier 5.1.2 Provide a fetch mechanism for its documents to be retrieved by URI, including support for MIME types (see NOTE below) 5.1.3 Provide exactly one target description with ref

41、erences to all socket descriptions, required resource sheets, and grouping sheet (see NOTE below) 5.1.4 Support locator functions 5.1.5 Provide one or more user interface sockets that collectively provide access to all of the func- tionality provided by the built-in user interface of the target 5.2.

42、2 Inside a targets socket are the following: the variables shall include all of the dynamic data on the target sockets state a user can perceive and/or manipulate, the commands shall include all of the target functions that can be called explicitly or implic- itly by users, and the n o t i f ic a t

43、ion s shall cover all exceptions that the target needs to inform the user about 5.2.3 Provide a user interface socket description for each of the targets sockets (see NOTE below) 5.3 Provide the required target resources in at least one natural language for the following: one grouping resource for e

44、very socket of the target, label resources (textual) 5.4.6 Support an open session request from a URC 5.5.1 Support a suspend session request from a URC 5.5.2 Support a resume session request from a URC 5.5.3 Support a close session event from a URC 5.5.4 Send an abort session event in case of user

45、session abortion 5.5.5 Track connection status information from the underlying TUN network 5.5.6 Send a session forward event to the URC in case of session forwarding 5.5.7 Create and maintain a session between a socket and the URC after a successful open session request 5.6.1 Indicate to the URC th

46、e availability of socket elements at runtime 5.6.3 Synchronize the socket variables between the socket and the URCs that participate in a joint session with the socket 5.6.5 Support command invocation requests from a URC (including handling of local parameters) and synchronization of command states

47、5.6.6 Support propagation of notification states and, for custom-type notifications, embedded varia- bles and commands, to the connected URCs, and acceptance of pertinent acknowledgments 5.6.7 Synchronize actual indices of socket sets and elements 5.6.8 Not rely on the URC doing the interpretation o

48、f socket element dependencies 5.6.92 ISO/IEC 2014 All rights reserved ISO/IEC 24752-1:2014(E) Requirement (“A target shall ”) See subclause Provide the following mechanisms with regard to user response timeouts: after a timeout extension return to the state of the task the user had reached prior to

49、the timeout, use the timeout attribute on notifications to represent timeout durations, note time out notifications in less than 10 seconds 5.6.10 Provide at least one target-URC network link (see 7.2 for TUN requirements) 5.7 NOTE As an alternative to having the target provide these documents (target description, socket descriptions, required atomic resources and grouping), they may be provided separately as supplemental resources, if the