ISO-23004-7-2008.pdf

Reference number ISO/IEC 23004-6:2008(E) © ISO/IEC 2008 INTERNATIONAL STANDARD ISO/IEC 23004-7 First edition 2008-02-15 Information technology Multimedia Middleware Part 7: System integrity management Technologies de l'information Intergiciel multimédia Partie 7: Gestion de l'intégrité de système Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-6:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces 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 Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe 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 unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2008 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's 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 Web www.iso.org Published in Switzerland ii © ISO/IEC 2008 All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) © ISO/IEC 2008 All rights reserved iii Contents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions.1 3.1 Specification terms and definitions.1 3.2 Realization terms and definitions6 4 Abbreviated terms.7 5 Overview of interface suites.7 6 Integrity Management interface suites8 6.1 Interface suites for extraction and modification of the software configuration.8 6.2 Management activation interface suites.29 6.3 Support interface suites .39 7 Realization overview.49 7.1 Introduction49 7.2 System Integrity management mechanisms 49 7.3 Roles in System Integrity Management 50 8 System Integrity Management realization.51 8.1 Structural view.51 8.2 Behavior View56 8.3 Deployment view .60 8.4 Scenarios64 Annex A (informative) M3W component models .65 Annex B (informative) Example diagnostic checks.67 Annex C (informative) Example scenarios.70 Annex D (informative) Integrity Management example XML schema definitions.72 Bibliography76 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) iv © ISO/IEC 2008 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) 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. 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, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 23004 may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 23004-7 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information. ISO/IEC 23004 consists of the following parts, under the general title Information technology Multimedia Middleware: Part 1: Architecture Part 2: Multimedia application programming interface (API) Part 3: Component model Part 4: Resource and quality management Part 5: Component download Part 6: Fault management Part 7: System integrity management Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) © ISO/IEC 2008 All rights reserved v Introduction Software systems continuously evolve; both during their development and during deployment. To cater for an increasing demand for flexibility, the M3W architecture provides means for the dynamic replacement, removal and addition of components in a deployed system. This facility enables a number of new usage scenarios which can increase the value of a terminal. However, this facility also endangers the software integrity of the system and creates the need for terminal management activities that aim to maintain and (if necessary) restore software integrity. Ideally, a terminal is managed automatically, implying little or no human intervention. System Integrity management techniques aim to maintain/restore a consistent software configuration that is sufficient for a specific terminal. These techniques verify that component configurations “fit“ with a device, where the following fits have been identified. Business fit: This depends for example on whether or not a user has paid for certain components. Technical fit: This deals with whether or not components are for the “right“ platform, all required dependencies can be fulfilled, and design guidelines are obeyed. Resource fit: This deals with verifying that the resource demands of applications are in line with the capabilities of the terminal. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- INTERNATIONAL STANDARD ISO/IEC 23004-7:2008(E) © ISO/IEC 2008 All rights reserved 1 Information technology Multimedia Middleware Part 7: System integrity management 1 Scope This part of ISO/IEC 23004 defines the MPEG Multimedia Middleware (M3W) technology Integrity Management Architecture. It contains the specification of the part of the M3W application programming interface (API) related to Integrity Management as well as the realization. The M3W API specification provides a uniform view of the Integrity Management functionality provided by M3W. The specification of the realization is relevant for those who are making an implementation of an Integrity Management framework for M3W. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 23004-1, Information technology Multimedia Middleware Part 1: Architecture ISO/IEC 23004-3, Information technology Multimedia Middleware Part 3: Component model 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 Specification terms and definitions 3.1.1 API specification specification of a collection of software interfaces providing access to coherent streaming-related functionality 3.1.2 interface suite collection of mutually related interfaces providing access to coherent functionality 3.1.3 logical component coherent unit of functionality that interacts with its environment through explicit interfaces only 3.1.4 role abstract class defining behavior only 3.1.5 role instance object displaying the behavior defined by the role Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) 2 © ISO/IEC 2008 All rights reserved 3.1.6 attribute instance variable associated with a role NOTE Attributes are used to associate state information with roles. 3.1.7 signature definition of the syntactic structure of a specification item such as a type, interface or function in IDL NOTE For C functions, signature is equivalent to prototype. 3.1.8 specification item entity defined in a specification NOTE Data type, role, attribute, interface and function are examples of specification items. 3.1.9 qualifier predefined keyword representing a property or constraint imposed on a specification item 3.1.10 constraint restriction that applies to a specification item 3.1.11 execution constraint constraint on multi-threaded behavior 3.1.12 model type data type used for specification (modeling) purposes only NOTE Set, map and entity are example of model types. 3.1.13 model constant constant used for specification (modeling) purposes only 3.1.14 enum element type enumerated type whose values can be used to construct sets (bit vectors) of at most 32 values by logical or-ing 3.1.15 enum set type 32-bit integer data type representing sets of enumerated values 3.1.16 set type data type whose values are mathematical sets of values of a specific type NOTE Unlike enum sets, these sets may be infinite. 3.1.17 map type data type whose values are tables mapping values of one type (the domain type) to values of another type (the range type) NOTE Maps are a kind of generalized array. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) © ISO/IEC 2008 All rights reserved 3 3.1.18 entity type class of objects that may have attributes associated with them 3.1.19 interface-role model extended Unified Modeling Language class diagram showing the roles and interfaces associated with a logical component, and their mutual relations 3.1.20 logical component instance incarnation of a logical component: a configuration of objects displaying the behavior defined by the logical component 3.1.21 provides interface interface that is provided by a role or role instance 3.1.22 requires interface interface that is used by a role or role instance 3.1.23 specialization behavoral inheritance definition, by a role, of behavior which implies the behavior defined by another role NOTE A role S specializes a role R if the behavior defined by S implies the behavior defined by R, i.e. if S has more specific behavior than R. 3.1.24 diversity set of all parameters that can be set at instantiation time of a logical component, and that will not change during the lifetime of the logical component 3.1.25 mandatory interface provides interface of a role that should be implemented by each instance of the role 3.1.26 optional interface provides interface of a role that need not be implemented by each instance of the role 3.1.27 configurable item parameter that can be set at instantiation time of a logical component, usually represented by a role attribute 3.1.28 diversity attribute role attribute that represents a configurable item 3.1.29 instantiation process of creating an instance (an incarnation) of a role or logical component 3.1.30 initial state state of a role instance or logical component instance immediately after its instantiation Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=Boeing Co/5910770001 Not for Resale, 07/25/2008 05:08:05 MDTNo reproduction or networking permitted without license from IHS -,-,- ISO/IEC 23004-7:2008(E) 4 © ISO/IEC 2008 All rights reserved 3.1.31 observable behavior behavior that can be observed at the external software and streaming interfaces of a logical component 3.1.32 function behavior behavior of the functions in the provides interfaces of a role 3.1.33 streaming behavior input-output behavior of the streams associated with a role 3.1.34 active behavior autonomous behavior that is visible at the provides and requires interfaces of a role 3.1.35 instantiation behavior behavior of a role at instantiation time of a logical component 3.1.36 independent attribute attribute whose value may be defined or changed independently of other attributes and entities 3.1.37 dependent attribute attribute whose value is a function of the values of other attributes or entities 3.1.38 invariant assertion about a role or logical component that is always true from an external observers point of view NOTE In reality, the assertion may temporarily be violated. 3.1.39 callback interface interface provided by a client of a logical component whose functions are called by the logical component NOTE A notification interface is an example of this, but there may be other call-back interfaces as well, e.g. associated with plug-ins. 3.1.40 callback-compl