ISO 20242-2-2010 Industrial automation systems and integration - Service interface for testing applications - Part 2 Resource management service interface《工业自动化.pdf

1、 Reference number ISO 20242-2:2010(E) ISO 2010INTERNATIONAL STANDARD ISO 20242-2 First edition 2010-09-01 Industrial automation systems and integration Service interface for testing applications Part 2: Resource management service interface Systmes dautomatisation industrielle et intgration Interfac

2、e de service pour contrler les applications Partie 2: Interface de service pour la gestion de ressource ISO 20242-2:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the t

3、ypefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adob

4、e Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unl

5、ikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO 2010 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electron

6、ic or mechanical, including photocopying and microfilm, without permission in writing 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.org

7、Web www.iso.org Published in Switzerland ii ISO 2010 All rights reservedISO 20242-2:2010(E) ISO 2010 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .1 4 Symbols and abbreviated terms 1 5 Conventions for service definitions and

8、 procedures 2 5.1 General .2 5.2 Parameters .2 5.3 Service procedures .3 5.4 Service primitives and state diagrams3 6 Resource Management Services .4 6.1 Overview.4 6.2 List of services 5 6.3 Management support services.7 6.4 Input/output services 11 6.5 Extended services.28 6.6 Operating Support Se

9、rvices.32 6.7 States of RMS state machine .60 Annex A (informative) Implementation guidelines for RMSI Mapping of services to C/C+ function calls .64 Annex B (informative) Cascading of device drivers via RMSI77 Bibliography79 ISO 20242-2:2010(E) iv ISO 2010 All rights reservedForeword ISO (the Inter

10、national Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has

11、been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical st

12、andardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies

13、for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or

14、all such patent rights. ISO 20242-2 was prepared by Technical Committee ISO/TC 184, Automation systems and integration, Subcommittee SC 5, Architecture, communications and integration frameworks. ISO 20242 consists of the following parts, under the general title Industrial automation systems and int

15、egration Service interface for testing applications: Part 1: Overview Part 2: Resource management service interface The following parts are planned: Part 3: Virtual device service interface Part 4: Device capability profile template Part 5: Application program service interface Part 6: Conformance t

16、est methods, criteria and reports ISO 20242-2:2010(E) ISO 2010 All rights reserved vIntroduction The motivation for ISO 20242 stems from international automotive industries and their suppliers to facilitate the integration of automation and measurement devices, and other peripheral components for th

17、is purpose, into computer-based applications. It defines rules for the construction of device drivers and their behaviour in the context of an automation application, or a measurement application, or an automation and measurement application. The main goal of ISO 20242 is to provide users with: inde

18、pendence from the computer operating system; independence from the device connection technology (device interface/network); independence from device suppliers; the ability to certify device drivers with connected devices and their behaviour in the context of a given computer platform; independence f

19、rom the technological device development in the future. ISO 20242 will not force the development of new device families or the use of special interface technologies (networks). It encapsulates a device and its communication interface to make it compatible with other devices of that kind for a given

20、application. INTERNATIONAL STANDARD ISO 20242-2:2010(E) ISO 2010 All rights reserved 1Industrial automation systems and integration Service interface for testing applications Part 2: Resource management service interface 1 Scope This part of ISO 20242 defines a service interface that provides a gene

21、ric service access point for managing and operating the resources supported by the operating system of a computer and its peripherals, including special hardware on plug-in boards that are used in computer-assisted testing applications. The resource management service interface is intended to be imp

22、lemented in a manner that offers the exposed services of a computing platform adapter to be generic and independent of the operating system and its communication interfaces. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated re

23、ferences, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 20242-1, Industrial automation systems and integration Service interface for testing applications Part 1: Overview 3 Terms and definitions For the p

24、urposes of this document, the terms and definitions given in ISO 20242-1 and the following apply. 3.1 device driver software module providing an ISO 20242-specified interface with service functions to call a platform adapter to access physical devices 3.2 platform adapter software module providing a

25、 resource management service interface as defined in this part of ISO 20242, which encapsulates the computer platform, including the operating system, the hardware and its peripherals 4 Symbols and abbreviated terms CNF, Cnf Confirm (service primitive) IND, Ind Indication (service primitive) REQ, Re

26、q Request (service primitive) ISO 20242-2:2010(E) 2 ISO 2010 All rights reservedRMS Resource Management Services RMSI Resource Management Service Interface RSP, Rsp Response (service primitive) SAP Service Access Point 5 Conventions for service definitions and procedures 5.1 General This part of ISO

27、 20242 uses the descriptive conventions given in ISO/IEC 10731. The interface between the user of RMS and the provider of RMS is described by service primitives that convey parameters. Since data transmission aspects are outside the scope of ISO 20242, only the request and confirm primitives are use

28、d to describe events occurring at the RMS service provider. Indication and response primitives are used to handle events occurring at the RMS service provider. The service model, service primitives and sequence diagrams are abstract descriptions; they do not represent a specification for implementat

29、ion. Annex A contains rules for example implementations. 5.2 Parameters Service primitives, used to represent service user/provider interactions (see ISO/IEC 10731), convey parameters that indicate information used and exchanged in these interactions. This part of ISO 20242 uses a tabular format to

30、describe the component parameters of the RMS primitives, as shown in Table 1. The parameters that apply to each group of RMS primitives are set out in tables throughout the remainder of this part of ISO 20242. Each table consists of three columns, where the first column contains the name of the serv

31、ice parameter, the second column contains the input parameters of either the request or indication primitives, and the third column contains the output parameters of either the confirm or response primitives. One parameter (or part of it) is listed in each row of each table. Under the appropriate se

32、rvice primitive columns, the following codes are used to specify the type of usage of the parameter on the primitive and parameter direction specified in the column: a) M: parameter is mandatory for the primitive; b) C: parameter is conditional upon other parameters or upon RMS capabilities; c) S: p

33、arameter is a selected item; d) (blank): parameter is not conveyed by the RMS user or the RMS provider. ISO 20242-2:2010(E) ISO 2010 All rights reserved 3Table 1 Tabular format for service primitive parameters Parameter name REQ or IND CNF or RSP Argument M Parameter 1 M Parameter 2 C Result (+) S P

34、arameter 3 M Parameter 4 C Result (-) S Parameter 5 M 5.3 Service procedures 5.3.1 RMS confirmed services An RMS user submits a request primitive to the RMSI. It is implied that the service access point (SAP) exists. The corresponding service processing entity delivers a confirmation primitive to th

35、e user after all necessary interactions are finished or an error occurred. 5.3.2 RMS event handling The user creates a service access point (SAP) at RMSI for handling events. An event is signalled with an indication primitive at this access point. The user of RMSI issues a response primitive after a

36、ll necessary interactions are finished or an error occurred (see Figure 1). Interface SAP SAP Service provider confirm request local event indication response local service processorFigure 1 Handling local events with RMS 5.4 Service primitives and state diagrams If needed, UML state diagrams are us

37、ed to describe the behaviour of RMS. In such diagrams, only the service name is used to describe a state transition where no explicit state between request and confirm primitives is necessary see Figure 2 b). Otherwise an extra state of processing the service is denoted see Figure 2 a). ISO 20242-2:

38、2010(E) 4 ISO 2010 All rights reservedService Processing State service.request service.confirm RMS State X RMS State Y service RMS State U RMS State V A) B)Figure 2 State transitions caused by services 6 Resource Management Services 6.1 Overview The RMSI shall provide generic management support serv

39、ices, generic operating support services, and generic input/output services. The input/output services access another subjacent layer providing extended services. Extended services are introduced to describe the structure of loadable resources for different kinds of periphery interfaces (see Figure

40、3). NOTE 1 ISO 20242 does not define the methods for integrating entities with extended services into the RMS provider, as that will depend on the computer operating system and the programming language used for implementing service providers. However, the extended services need to be described to en

41、able the extension of input/output services for different peripheral interfaces without changing the RMS provider. See Annex A for an implementation example. NOTE 2 There are additional cascading methods described in Annex B for using the RMSI in more complex structures of device and equipment integ

42、ration. Resource Management Service Interface management support services input/output services operation support services extended services Extended Service InterfaceFigure 3 Service users and providers at the RMSI ISO 20242-2:2010(E) ISO 2010 All rights reserved 56.2 List of services 6.2.1 Generic

43、 management support services Generic management support services are used for handling the access to other services and for initiating (and loading, if necessary) extended service providers. Table 2 gives an overview of these services. Table 2 Generic management support services Service Name for ide

44、ntification Remarks Get Service Reference getFuncAddress Get the reference for a service by identifier (name and/or number) and version number. Initiate Periphery Interface Type io_initiate Get the identifier for a specified interface type and load an extended service provider for this type (if nece

45、ssary). Conclude Periphery Interface Type io_conclude Release a type identifier and close the extended service provider for this type (if existing). 6.2.2 Generic input/output services Generic input/output services are used for communication with real devices and for configuration and control of per

46、ipheral interfaces. Table 3 gives an overview of these services. Table 3 Generic input/output services Service Name for identification Remarks Open Periphery Interface Channel io_open Open a peripheral interface for data transmission and configure the interface. Reconfigure Periphery Interface Chann

47、el io_config Change the configuration of an interface without closing it, e.g. change transmission parameters. Read Data io_read Fetch received data at a peripheral interface. Write Data io_write Deliver data to a peripheral interface for transmitting. Execute Operation io_execute Execute an operati

48、on belonging to a peripheral interface channel. This is comparable to handling both read and write data with one service (data exchange). Cancel Communication io_cancel Cancel a Read Data, Write Data or Execute Operation service and prepare the interface for new requests. Get Periphery Interface Cha

49、nnel Status io_stat Investigate the status of a peripheral interface. Clear Read Buffer io_clear Delete the contents of the input buffer of a peripheral interface. Close Peripheral Interface Channel io_close Close a peripheral interface. Signal Event io_event Indicating a local event and responding to the event source. Generic input/output services are transferred to corresponding extended services (see Table 4) if an extended service provider is loaded for the specified type of interfac