35.100.05 多层应用 标准查询与下载

ISO/IEC TR 14543-4:2002 信息技术.家用电子系统(HES)体系结构.第4部分:住宅和混用建筑内建筑的自动化

This technical report explores the similarities and differences between home and building control systems in an environment where both home and building control interact, namely, a mixed-use residential/commercial building. A logical model for linking building and home control systems is specified. Models showing the organization of application domains, such as energy management and lighting, are included. The option of managing an application domain with a single application controller versus a Fully Distributed System is considered. Methods for overall building management are presented.

Information technology - Home electronic systems (HES) architecture - Part 4: Home and building automation in a mixed-use building

CAN/CSA-ISO/IEC ISP 12068-2-2002(R2006) 信息技术 国际标准化概要 FDI 4 目录数据定义 OSI TP 目录的使用 第2部分：FDI 42 增强命名和寻址

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12068-2:1996. This is a text searchable PDF. 1 Scope ISO/IEC ISP 10616 profiles information to be stored within the Directory which is common to a variety of applications. ISO/IEC ISP 12068 augments this information with OSI TP specific information. Statements and conformance requirements stated in ISOIIEC ISP 10616 for the information profiled by ISO/IEC ISP 10616 are also valid for the OSI TP specific information profiled by this international Standardized Profile. ISO/IEC ISP 12068 specifies the use of the Directory, for OSI TP, using existing object class and attribute type definitions fr om the Directory specifications themselves, and additional definitions. These existing and additional definitions are also intended to support the use of the Directory by users of OSI TP applications. This part of ISO/IEC ISP 12068 defines those additional information which are needed to retrieve basic addressing informat ion for applications using the OSI TP service.

Information Technology - International Standardized Profile FDI 4 - Directory Data Definitions - Use of the Directory for OSI TP - Part 2: FDI 42 - Enhanced Naming and Addressing

GOST R 51954-2002 信息技术.超级计算应用环境框架(PSE10-HIP)

Information technology. Supercomputing application environment profile (PSE10-HIP)

CAN/CSA-ISO/IEC 14834-2001(R2009) 信息技术 分布式事务处理 XA 规范

This National Standard of Canada is equivalent to International Standard ISO/IEC 14834:1996. 1 Scope This International Standard specifies the XA interface: the bidirectional interface between a transaction manager and a r esource manager in an X/Open Distributed Transaction Processing (DTP) environment. The XA interface is not an ordinary Application Programming Interface (API); it is a system-level interface between DTP software components. This International Standard is technically identical to X/Open CAE Specification, Distributed Transaction Processing: The XA Specification (December 1991). Like that specification, this International Standard does not define the full aspects of the DTP model that pertain to communication.

Information Technology - Distributed Transaction Processing - The XA Specification

CAN/CSA-ISO/IEC ISP 11187-2-2001(R2005) 信息技术 国际标准化配置文件 AVT1n、AVT2n 虚拟终端基本类 应用程序配置文件 第2部分：通用支持层要求

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 11187-2:1996. 1 Scope 1.1 General The concept of Profiles for OSI, and the structure of the International Standardized Profiles that document them, are defined in ISO/IEC TR 10000-l. Such Profiles are divided into a number of different classes and sub-classes. Two of these classes contain sub-classes comprising functions of the Virtual Terminal Basic Class Service and Protocol specified in the base standards ISO 9040 and ISO 9041-l. These are the Application Profiles (A-Profiles) and the Interchange Format and Representation Profiles (F-Profiles). It is a requirement of ISO/IEC 9646-7 that the specification of a Profile shall provide a Profile Requirements List (Profile RL) which modifies the ICS proformas of the referenced base standards. A Profile specification may in addition provide a Profile Specific ICS proforma. This part of ISO/IEC ISP 11187 specifies a Common RL for the supporting layer protocols that shall be incorporated by reference into each VT Application Profile specified in other parts of ISO/IEC ISP 11187. 1.2 Position in the Taxonomy The taxonomy of International Standardized Profiles for OSI is laid down in ISO/IEC TR 10000-2. Within the classification scheme of this taxonomy, the OSI Profiles specified in this International Standardized Profile are in the Virtual Terminal sub-class of the class of Application Profiles. A Profile within this subclass has a Profile Identifier of the form AVTab, where ab is a structured numerical identifier that identifies the position of the Profile within two levels of the subdivision of the subclass. The value of a is a single digit but b is an integer that is not necessarily a single digit. In principle, the ISO Virtual Terminal model allows for multiple classes of operation, although at the time of publication of this International Standardized Profile, only the Basic Class has been defined. The value of the identifier component a distinguishes between the permitted modes of operation of the Virtual Terminal Service as follows: - a = 1 for A-mode (asynchronous mode) operation; - a = 2 for S-mode (synchronous mode) operation. Values of a greater than 2 are reserved for future developments. This International Standardized Profile ISO/ISP 11187 contains the specifications of the Profiles with identifiers of the form AVT1b and AVT2b. The component b distinguishes between different Application Profiles that make use of the same mode of operation. This part of ISO/IEC ISP 11187 may be incorporated by reference into the Profile RL for any profile with an identifier of the form AVT1b or AVT2b.

Information Technology - International Standardized Profiles AVT1n, AVT2n - Virtual Terminal Basic Class - Application Profiles - Part 2: Common Supporting Layers Requirements

CAN/CSA-ISO/IEC ISP 10615-6-2001(R2005) 信息技术 国际标准化配置文件 ADInn OSI 目录 第6部分：ADI32 DSA 对分布式操作的支持

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10615-6:1998. 1 Scope 1.1 General The Directory Standards define not only the protocol but also the behaviour of DSAs when they collaborate to carry out the purpose of the Directory. In order to achieve consistency and full interoperability, it is necessary to select from the options and interpretations laid down in the Directory Standards, and in particular within [ISO/IEC 9594-4 / CCITT X.518]. This part of ISO/IEC ISP 10615 specifies the behaviour of DSAs in exercising the DAP, the DSP, or both, that is required to carry out Distributed Operations in accordance with these requirements. The scope of this part of ISO/IEC ISP 10615 is to define: - Static capabilities that are required by DSAs in order to achieve acceptable levels of service in cooperation with other DSAs - Procedures, based on procedures given within the base standards, in the detail required to achieve consistency and interoperability - Protocol use, as required to implement the procedures. It is applicable to DSAs implementing the '88 Directory Standards [ISO/IEC 9594:1990 / CCITT X.500:1988]. It applies to all DSAs that contain a component of the distributed Directory, although many of its requirements are inapplicable to DSAs that do not support the invocation of DSP operations. Implementations claiming conformance to this part of ISO/IEC ISP 10615 may be based on either ISO/IEC 9594 or CCITT X.500 or both. There are no practical differences as far as this part of ISO/IEC ISP 10615 is concerned. This part of ISO/IEC ISP 10615 is not free-standing. Compliance with this part of ISO/IEC ISP 10615 requires compliance with ISO/IEC ISP 10615 parts 2 to 4 inclusive, and with normative references identified in those documents. Conversely, this part of the part of ISO/IEC ISP 10615 is applicable to DSAs which conform to other parts of ISO/IEC ISP 10615, and in particular to parts 2 (ADI12), 3 (ADI21) and 4 (ADI22). 1.2 Position within the taxonomy This part of ISO/IEC ISP 10615 is identified in ISO/IEC TR 10000-2 as ADI32 Directory - Distributed Operations - DSA Support of Distributed Operations. 1.3 Scenario In the Distributed Directory, one mode of interaction is the chaining (including multicasting) of enquiries in accordance with the procedures laid down in [ISO/IEC 9594-4 / CCITT X.518]. Another is the following of referrals and of embedded cont inuation references. In carrying out these procedures, a DSA is accessed by a DUA or another DSA, and carries out the requested action with or without ref erence to other DSAs. This part of ISO/IEC ISP 10615 is concerned with the information contained in a DSA to enable it to determine that other DSAs are involved, and with the procedures whereby other DSAs can be involved, by the use of chaining or referrals (Figure 1).

Information Technology - International Standardized Profiles ADInn - OSI Directory - Part 6: ADI32 - DSA Support for Distributed Operations

CAN/CSA-ISO/IEC ISP 10615-5-2001(R2005) 信息技术 国际标准化配置文件 ADInn OSI 目录 第5部分：ADI31 对分布式操作的 DUA 支持

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10615-5:1998. 1 Scope 1.1 General Although ISO/IEC 9594-4 / CCITT X.518 describes the DSA procedures relating to referrals and Search Continuation References, this part of ISO/IEC ISP 10615 does not define the DUA's role in acting upon these procedures. This part of ISO/IEC ISP 10615 specifies the behaviour of DUAs when they use DAP to access multiple DSAs in the course of making a single original enquiry without human intervention in the formulation of protocol. Multiple enquiries result from receiving continuation references embedded in referrals, list results or search results. DUAs which do not have the capability of following referrals or Search Continuation References without human intervention in the formulation of protocol are not within the scope of this part of ISO/IEC ISP 10615 for the purposes of conformance, although its recommendations may be of value. NOTE - The conformance requirements of this part of ISO/IEC ISP 10615 presume the scenario depicted in Figure 1: human intervention (if any) is restricted to the possibility of a go/ no-go decision; in the case of conformance testing, each such decision is presumed to be go. The scope of this part of ISO/IEC ISP 10615 is limited to matters of procedure in exercising the DAP protocol, and does not cover enhancements of service. It does not cover any (DAP) protocol encoding issues. NOTE - In the absence of this part of ISO/IEC ISP 10615, the implementor of a DUA with the capability of following continuation references automatically will need to make design decisions about the behaviour of the DUA when doing so. An aim of this part of ISO/IEC ISP 10615 is to minimise uncertainty and enhance consistency in making design solutions by means of functional standardisation. This part of ISO/IEC ISP 10615 adds no spurious complexity, given that the requirement pre-exists to follow continuation references automatically. 1.2 Position within the taxonomy This part of ISO/IEC ISP 10615 is identified in ISO/IEC TR 10000-2 as ADI31 Directory-Distributed Operations - DUA Support of Distributed Operations. 1.3 Scenario This part of ISO/IEC ISP 10615 profiles the autonomous behaviour of DUAs when Referrals or Search Continuation References are used by the Directory. A DUA creates an association to a DSA of its choice, and invokes an operation. The DSA may return a referral instead of a result, or the result may contain continuation references. The latter occur in the case of List or Search operations in which the DSA is unwilling or unable to complete the search, but is able to advise which other DSAs may be able to assist. The possible actions which may then be taken by a DUA, without human intervention except possibly the taking of a go/no-go decision, are specified in this part of ISO/IEC ISP 10615.

Information Technology - International Standardized Profiles ADInn - OSI Directory - Part 5: ADI31 - DUA Support for Distributed Operations

CAN/CSA-ISO/IEC ISP 10611-4-01:2001 信息技术 国际标准化配置文件 AMH1n 消息处理系统 通用消息传递 第4部分：AMH12 和 AMH14 MTS Access (P3) 和 MTS 94 Access (P3)

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10611-4:1997. 1 Scope 1.1 General This part of ISO/IEC ISP 10611 covers access to a Message Transfer System (MTS) using the P3 MTS Access Protocol (see also figure 1). These specifications form part of the Common Messaging application functions, as defined in the parts of ISO/IEC ISP 10611, which form a common basis for content type- dependent International Standardized Profiles for MHS that will be de veloped. An MTA or an MTS-user which conforms to profile AMH12 as specified in this part of ISO/IEC ISP 10611 shall support an 'mts-access' application context and for the MTA also 'mts- forced-access' application context. The MTA or the MTS-user may additionally conform to profile AMH14 as specified in this part of ISO/IEC ISP 10611 shall support the 'mts-access-94' and 'mts- forced-access-94' application contexts. 1.2 Position within the taxonomy This part of ISO/IEC ISP 10611 is the fourth part of a multipart ISP identified in ISO/IEC TR 10000-2 as AMH1, Message Handling Systems - Common Messaging. This part of ISO/IEC ISP 10611 specifies the following profiles: AMH12 - MTS Access (P3) AMH14 - MTS 94 Access (P3) The AMH12 and AMH14 profiles may be combined with any T-Profiles (see ISO/IEC TR 10000) specifying the OSI connection-mode Transport service. 1.3 Scenario The model used is one of access to an MTS by an MTS-user - specifically, the intercommunication between a message transfer agent (MTA) and an MTS-user using the P3 protocol, as shown in figure 1. The AMH12 and AMH14 profiles cover all aspects of the MTS Abstract Service, as defined in clause 8 of ISO/IEC 10021-4, when realized using the P3 protocol.

Information Technology - International Standardized Profiles AMH1n - Message Handling Systems - Common Messaging - Part 4: AMH12 and AMH14 - MTS Access (P3) and MTS 94 Access (P3)

CAN/CSA-ISO/IEC ISP 11187-1-2001(R2005) 信息技术 国际标准化配置文件 AVT1n、AVT2n 虚拟终端基本类 应用程序配置文件 第1部分：通用 VT 协议要求

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 11187-1:1996. 1 Scope 1.1 General The concept of Profiles for OSI, and the structure of the International Standardized Profiles that document them, are defined in ISO/IEC TR 10000-1. Such Profiles are divided into a number of different classes and sub-classes. Two of these classes contain sub-classes comprising functions of the Virtual Terminal Basic Class Service and Protocol specified in the base standards ISO 9040 and ISO 9041. These are the Application Profiles (A-Profiles) and the Interchange Format and Representation Profiles (F-Profiles). The relationship between A-Profiles and F-Profiles is described in 7.3.2 of ISO/IEC TR 10000-1 and is as follows. Application Layer base standards require, implicitly or explicitly, the structure of information carried or referenced by them to be specified for each instance of communication. It is the purpose of F-Profiles to specify Information Objects that provide these structures. Particular functional requirements may then be met by the combination of an A-Profile with one or more F-Profiles. Establishment of a VT-association involves the selection by negotiation of a particular Virtual Terminal Environment profile (VTE-profile), and of particular values for any arguments of that VT E-profile. The VTE-profile specification, and possibly also the values of certain VTE-profile arguments, may in turn reference the definitions of VT control object types and assignment types. These VTE-profiles, control object types and assignmen t types are therefore Information Objects that require explicit reference within the VT protocol. Particular instances of these Information Objects are fully defined within the base standards, but the base standards also provide for further instances to be defined by registration. Each registered instance constitutes an F-Profile within the framework of ISO/IEC TR 10000. The Virtual Terminal Basic Class Service and Protocol may be used to realise a wide range of distinct functions. Particular functions may be realised through the selection of appropriate VT functional units, F-Profiles and other VTE- profile argument values. The specification of the selection required to realise a particular function and to promote interoperability constitutes a Virtual Terminal A-Profile within the framework of ISO/IEC TR 10000. The three International Registers of VT information objects and the specifications of VT Application Profiles are each published as a separate multi-part ISP as follows: - ISO/IEC ISP 11184 is the Register of VTE-profiles; - ISO/IEC ISP 11185 is the Register of control object type definitions; - ISO/IEC ISP 11186 is the Register of assignment-type definitions; - ISO/IEC ISP 11187 contains the specifications of VT Application Profiles. It is a requirement of ISO/IEC 9646-7 that the specification of an Information Object shall provide an Information Object Implementation Conformance Statement (ICS) proforma. This is a document in the form of a questionnaire or checklist to be completed by the supplier or implementor of an implementation for whi ch conformance is claimed to the Information Object concerned. It is also a requirement of ISO/IEC 9646-7 that the specification of a Profile shall provide a Profile Requirements List (Profile RL) which modifies the ICS proformas of the referenced base standards. A Profile specification may in addition provide a Profile Specific ICS proforma. This part of ISO/IEC ISP 11187 provides guidance on the interpretation of these requirements for Profiles of the Virtual Terminal Basic Class Service and Protocol. It also specifies a Common RL for the VT Protocol that shall be incorporated by reference into each VT Application Profile specified in other parts of ISO/IEC ISP 11187. 1.2 Position within the Taxonomy The taxonomy of International Standardized Profiles for OSI is laid down in ISO/IEC TR 10000-2. Within the classification scheme of this taxonomy, Profiles of the Virtual Terminal Registered Objects subclass of the class of Interchange Format and Representation Profiles (F-Profiles) have taxonomy identifiers of the form FVTabc. Profiles of the Virtual Terminal subclass of the class of Application Profiles requiring connection-mode Transport Service have taxonomy identifiers of the form AVTbc. In these identifiers, abc and bc are structured numerical identifiers in which values of a and b are single di gits but c is an integer that is not necessarily a single digit. These numerical identifiers identify the position of the Profile within the hierarchy of levels of subdivision of the subclass. The guidance on RLs and ICS proformas given in this part of ISO/IEC ISP 11187 is applicable to all Profiles in either of these two subclasses. The Common RL for the VT Protocol given in this part of ISO/IEC ISP 11187 is applicable to all Application Profiles with identifiers of the form AVT1c or AVT2c. Other parts of this ISP give either further common requirements or the specification of an individual Application Profile with an identifier of one of these forms. The value of the identifier component b in the identifiers AVTbc distinguishes between permitted modes of operation of the Virtual Terminal Service as follows: - b = 1 for Basic Class A-mode (asynchronous mode); - b = 2 for Basic Class S-mode (synchronous mode). Values of b greater than 2 are reserved for future developments.

Information Technology - International Standardized Profiles AVT1n, AVT2n - Virtual Terminal Basic Class - Application Profiles - Part 1: Common VT Protocol Requirements

CAN/CSA-ISO/IEC ISP 10613-19-2001(R2005) 信息技术 国际标准化配置文件 RA 中继无连接模式网络服务 第19部分：采用网络层安全协议的安全性 无连接模式 用于 RAnn.nn 配置文件

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10613-19:1998. 1 Scope 1.1 General ISO/IEC ISP 10613 is applicable to interworking units concerned with operating in the Open Systems Interconnection (OSI) environment. It specifies a combination of OSI base standards that collectively provide a Network Relay function for the connectionless-mode Network Service. This part of ISO/IEC 10613 specifies profile requirements for the provision of security services using cryptographic techniques with the Network Layer Security Protocol connectionless-mode. This part of ISO/IEC 10613 specifies profile requirements that are applicable to any type of subnetwork. 1.2 Position within the Taxonomy The taxonomy of profiles is specified in ISO/IEC TR 10000-2. This part of ISO/IEC ISP 10613 supports security services for any RA profile specified in ISO/IEC ISP 10613 (profiles relaying the connectionless-mode Network Service). Note: ISO/IEC TR 10000 currently does not identify security sub- profiles. Profiles based on this part of ISP 10613 can be referred t o as TAnnnS1, or TAnnnS1C if confidentiality is selected. 1.4 Security Services The following security services are within the scope of this profile: a) Data origin authentication b) Connectionless integrity Note: It is strongly recommended that some form of access control is supported. However, this may be achieved using local access control lists which are outside the scope of this profile. c) Access control using security labels (optional) d) Connectionless confidentiality (optional) e) Traffic flow confidentiality (optional) 1.5 Security Mechanisms This part of ISP 10613 provides no assurance as to the strength of the security mechanisms employed. This profile does not specify the cryptographic algorithms to be emplo yed.

Information Technology - International Standardized Profile RA - Relaying the Connectionless-Mode Network Service - Part 19: Security Employing the Network Layer Security Protocol - Connectionless-Mode, for RAnn.nn Profiles

CAN/CSA-ISO/IEC ISP 12068-1-2001(R2005) 信息技术 国际标准化概要 FDI 4 目录数据定义 OSI TP 目录的使用 第1部分：FDI 41 基本命名和寻址

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12068-1:1996. 1 Scope 1.1 General ISO/IEC ISP 10616 profiles information to be stored within the Directory which is common to a variety of applications. ISO/IEC ISP 12068 augments this information with OSI TP specific information. Statements and conformance requirements stated in ISO/IEC ISP 10616 for the information profiled by ISO/IEC ISP 10616 are also valid for the OSI TP specific information profiled by this international Standardized Profile. ISO/IEC ISP 12068 specifies the use of the Directory, for OSI TP , using existing object class and attribute type definitions from the Directory specifications themselves, and additional definitions. These existing and additional definitions are also intended to support the use of the Directory by users of OSI TP applications. This part of ISO/IEC ISP 12068 defines that additional information which is needed to retrieve basic addressing information for applications using the OSI TP service. 1.2 Position within the taxonomy ISO/IEC ISP 12068 is identified in ISO/IEC TR 10000-2 as Informat ion technology - International Standardized Profile FDI 4 - Directory data definitions - Use of the Directory for OSI TP. 1.3 Scenario An OSI TP application, by means of its associated DUA, obtains Directory information by accessing directly or indirectly one or more DSAs of the Directory (see figure 1).

Information Technology - International Standardized Profile FDI 4 - Directory Data Definitions - Use of the Directory for OSI TP - Part 1: FDI 41 - Basic Naming and Addressing

CAN/CSA-ISO/IEC ISP 12062-1-01:2001 信息技术 国际标准化配置文件 AMH2n 消息处理系统 人际消息传递 第1部分：IPM MHS 服务支持

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12062- 1:1998 Scope 1.1 General This part of ISO/IEC ISP 12062 contains the overall specifications of the support of MHS Elements of Service and associated MHS functionality in an Interpersonal Messaging (IPM) environment which are generally not appropriate for consideration only from the perspective of a single MHS protocol. These specifications form part of the Interpersonal Messaging application functions, as defined in the parts of ISO/IEC ISP 12062, and are based on the Common Messaging content type-independent specifications in ISO/IEC ISP 10611. Such specifications are in many cases applicable to more than one MHS protocol or are otherwise concerned with component functionality which, although it can be verified via protocol, is not just related to protocol support. They are therefore designed to be referenced in the MHS Interpersonal Messaging application prof iles ISO/IEC ISP 12062-2 (AMH21), ISO/IEC ISP 12062-3 (AMH22), ISO/IEC ISP 12062-4 (AMH23 and AMH25), ISO/IEC ISP 12062-5 (AMH24) and ISO/IEC ISP 12062-6 (AMH26), which specify the support of specific MHS protocols and associated functionality. The specifications in this part of ISO/IEC ISP 12062 are divided into basic requirements, which are required to be supported by all IPM MHS implementations, and a number of optional functional groups, which cover significant discrete areas of related functionality which are not required to be supported by all implementations. An overview of the scope and applicability of the AMH2n set of profiles and of the structure of this multipart ISP is provided in annex D. 1.2 Position within the taxonomy This part of ISO/IEC ISP 12062 is the first part, as common text, of a multipart ISP identified in ISO/IEC TR 10000-2 as AMH2, Message Handling Systems - Interpersonal Messaging (see also ISO/IEC TR 10000-1, 8.2 for the definition of multipart ISPs). This part of ISO/IEC ISP 12062 does not, on its own, specify any profiles.

Information Technology - International Standardized Profiles AMH2n - Message Handling Systems - Interpersonal Messaging - Part 1: IPM MHS Service Support

CAN/CSA-ISO/IEC ISP 12072-2001(R2014) 信息技术 国际标准化概况 FDI5 目录数据定义 VT 目录的使用

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12072:1998. 1 Scope 1.1 General ISO/IEC ISP 10616 profiles information to be stored within the Directory which is common to a variety of applications. This International Standardized Profile augments this information with VT application specific information. Statements and conformance requirements stated in ISO/IEC ISP 10616 for the information profiled by ISO/IEC ISP 10616 are also valid for the VT application specific information profiled by this International Standardized Profile. This International Standardized Profile therefore profiles Directory information for use by VT applications and users of VT applications, using existing object class and attribute type definitions from the Directory specifications themselves, and additional definitions. This International Standardized Profile does not define any procedures covering how this Directory information shall be used either by VT applications or by users of VT applications. 1.2 Position within the taxonomy This International Standardized Profile is identified in ISO/IEC TR 10000-2 as 'Information technology - International Standardized Pro file FDI5 - Directory data definitions - VT Use of the Directory'. 1.3 Scenario A VT application, by means of an associated Directory User Agent (DUA), obtains Directory information by accessing directly or indirectly one or more Directory System Agents (DSAs) of the Directory (see figure 1).

Information Technology - International Standardized Profile FDI5 - Directory Data Definitions - VT Use of the Directory

CAN/CSA-ISO/IEC ISP 12060-8-2001(R2005) 信息技术 国际标准化配置文件 OSI 管理 管理功能 第8部分：AOM253x 汇总对象（包括配置文件 AOM2531-AOM2539）

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12060-8:1996. 1 Scope 1.1 General This part of ISO/IEC ISP 12060 specifies the General summarization capabilities profile, AOM2531, which is applicable to end systems operating in the Open Systems Interconnection ( OSI) environment. AOM2531 specifies a combination of OSI standards which collectively provide General summarization capabilities. These capabilities include the ability to create and delete instances of Summarization managed object classes, retrieve and modify any attribute of Summarization objects, perform any action associated with instances of Summarization managed object classes, and report (both receive and send in the respective roles) any event associated with instances of the Summarization managed object classes. AOM2531 covers a full set of facilities that can be provided by a management platform such that complete freedom exists to dynamically monitor any appropriate resource. The specific profiles (AOM2532 - AOM2539) cover facilities associated with a single type of monitoring and calculation for any appropriate resource; these support the need to implement only those specific features required by the managed resource. This part of ISO/IEC ISP 12060 also specifies the Simple scanner object profile, AOM2532, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2532 specifies a combination of OSI standards which collectively provide Simple scanner object capabilities. These capabilities include the ability to create and delete instances of Simple scanner managed object class, retrieve and modify any attribute of Simple scanner objects, perform an action associated with instances of Simple scanner managed object cl asses, and report (both receive and send in the respective roles) any event associated with instances of the Simple scanner managed object class. AOM2532 can provide aggregated report of a set of sampled attribute values of the same type across a number of resources. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Dynamic simple scanner object profile, AOM2533, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environmen t. AOM2533 specifies a combination of OSI standards which collectively provide Dynamic simple scanner object capabilities. These capabilities include the ability to create and delete instances of Dynamic simple scanner managed object class, retrieve and modify any attribute of Dynamic simple scanner objects, and perform an action associated with instances of Dynamic simple scanner managed object classes. AOM2533 can provide aggregated report of a set of sampled attribute values of the same type across a number of resources on request only. The request specifies the resources to be monitored. This part of ISO/IEC ISP 12060 also specifies the Heterogeneous scanner object profile, AOM2534, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2534 specifies a combination of OSI standards which collectively provide Heterogeneous scanner object capabilities. These capabilities include the ability to create and delete instances of Heterogeneous scanner object class, retrieve and modify any attribute of Heterogeneous scanner objects, perform an action associated with instances of Heterogeneous scanner managed object classes, and report (both receive and send in the respective roles) any event associated with instances of the Heterogeneous scanner object class. AOM2534 can provide aggregated report of a set of sampled attribute values of the different types across a number of resources. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Buffered scanner object profile, AOM2535, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2535 specifies a combination of OSI standards which collectively provide Buffered scanner object capabilities. These c apabilities include the ability to create and delete instances of Buffered scanner object class, retrieve and modify any attribute of Buffered scanner objects, perform an action associated with instances of Buffered scanner managed object classes, and report (both receive and send in the respective roles) any event associated with instances of the Buffered scanner object class. AOM2535 can provide aggregated report similar to the Heterogeneous scanner but retains the sets of monitored values over a period of time and reports them together. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Mean scanner object profile, AOM2536, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2536 specifies a combination of OSI standards which collectively provide Mean scanner object capabilities. These capabilities include the ability to create and delete instances of Mean scanner object class, retrieve and modify any attribute of Mean scanner objects, perform an action associated with instances of Mean scanner managed object classes, and report (both receive and send in the respective roles) any event associated with instances of the Mean scanner object class. AOM2 536 can provide a report of the mean value of a set of sampled attribute values of the same type across a number of resources. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Mean variance scanner object profile, AOM2537, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2537 specifies a combination of OSI standards which collectively provide Mean variance scanner object capabilities. These capabilities include the ability to create and delete instances of Mean variance scanner object class, retrieve and modify any attribute of Mean variance scanner objects, perform an action associated with instances of Mean variance scanner managed object classes, and report (both receive and se nd in the respective roles) any event associated with instances of the Mean variance scanner object class. AOM2537 can provide a report of the mean and variance values of a set of sampled attribute values of the same type across a number of resources. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Percentile scanner object profile, AOM2538, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2538 specifies a combination of OSI standards which collectively provide Percentile scanner object c apabilities. These capabilities include the ability to create and delete instances of Percentile scanner object class, retrieve and modify any attribute of Percentile scanner objects, perform an action associated with instances of Percentile scanner managed object classes, and report (both receive and send in the respective roles) any event associated with instances of the Percentile scanner object class. AOM2538 can provide a report of the percentile, minimum, median, maximum and mean values of a set of sampled attribute values of the same type across a number of resources. The summary report can be generated according to a schedule, on request or both. This part of ISO/IEC ISP 12060 also specifies the Min Max scanner object profile, AOM2539, which is applicable to end systems operating in the Open Systems Interconnection (OSI) environment. AOM2539 specifies a combination of OSI standards which collectively provide Min Max scanner object capabilities. These capabilities include the ability to create and delete instances of Min Max scanner object class, retrieve and modify any attribute of Min Max scanner objects, perform an action associated with instances of Min Max scanner managed object class es, and report (both receive and send in the respective roles) any event associated with instances of the Min Max scanner object class. AOM2539 can provide a report of the minimum, maximum and mean values of a set of sampled attribute values of the same type across a number of resources. The summary report can be generated according to a schedule, on request or both. AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AO M2538, and AOM2539, also specifies use of a combination of standards that collectively provide the subset of the Common Management Information Service required by the profiles defined in this part of ISO/IEC ISP 12060. The support of the complete set of operation and notification services for scanner objects does not imply that all these features shall be used in all instances of communications. The selection of the features on an instance of communication depends on the requirements of the MIS-users. The definition and conventions used in this part of ISO/IEC ISP 12060 are specified in part 0 of ISO/IEC ISP 12059-0, Common definitions for management functions profiles. 1.2 Introduction AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AOM2538, and AOM2539 are applicable to end systems operating in an OSI environment in either the Manager role or in the Agent role. A system acting in the role of Manager is capable of requesting the specified set of operations upon scanner managed objects which are in the system acting the role of the agent. AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AOM2538, and AOM2539 provide facilities for monitoring and aggregating management information of resources in a system where tho se resources are represented by managed objects. They permit the creation of separate summarization managed objects each of which can observe and perform calculations on the values of attributes of managed objects representing resources. Facilities are provided for generation of summary reports at scheduled times. Figure 1 illustrates only one of those configurations, one in which one system is acting in a manager role and a further system is acting in an agent role. The roles of Manager and Agent may be determined in advance, for the duration of an association or the duration of a single management interaction. The application context is defined in the Systems Management Overview (ISO/IEC 10040). Note: Negotiation of functional units is optional. AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AOM2538, and AOM2539 require support for the protocol elements needed to provide the PT-GET, PT-SET, PT-CREATE, PT-DELETE, object creation reporting, object deletion reporting, attribute valu e change reporting and state change reporting services; this requires support of the protocol from the standards shown below. AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AOM2538, and AOM2539 reference the following standards: ISO/IEC 10164-1 ,,Object management function ISO/IEC 10164-2,,,,State management function ISO/IEC 10164-11,,Metric object and attributes ISO/IEC 10164-13,,Summarization function ISO/IEC 10165-2,,,,Definition of management information ISO/IEC 9595,,,,CMIS ISO/IEC 9596-1,,,,CMIP ISO/IEC 9072-1,2,,ROSE ISO 8649, 8650,,,,ACSE ISO/IEC ISP 11183-2,,CMISE/ROSE for AOM12-Enhanced Management Communication ISO/IEC ISP 11183-1,,Specification of ACSE, Presentation and Session ISO 8822, 8823 ,,,,Presentation ISO/IEC 8824, 8825,,ASN.1 ISO/IEC ISP 11183-1,,Specification of ACSE, Presentation and Session ISO 8326, 8327,,,,Session ISO 8326/Add.2 ISO 8327/Add.2 ISO/IEC ISP 11183-1,,Specification of ACSE, Presentation and Session AOM2531, AOM2532, AOM2533, AOM2534, AOM2535, AOM2536, AOM2537, AOM2538, and AOM2539 also specify the use of the subset of the Enhanced Management Communications profile (AOM12) that is required to support the above services. An end system implementing this profile can interwork with an end system implementing the same profile in a complementary role. A system implementing AOM12 is compatible with the communication aspects of AOM253n profiles. 1.3 Position within the Taxonomy This part of ISO/IEC ISP 12060 is identified in ISO/IEC TR 10000-2 as: AOMnn,,,,OSI Management AOM2,,,,Management functions AOM25,,,,Performance AOM253,,,,Summarization Objects AOM2531,,General Summarization Capability AOM2532,,Simple Scanner Object AOM2533,,Dynamic Simple Scanner Object AOM2534,,Heterogeneous Scanner Object AOM2535,,Buffered Scanner Object AOM2536 ,,Mean Scanner Object AOM2537,,Mean Variance Scanner Object AOM2538,,Percentile Scanner Object AOM2539,,Min Max Scanner Object

Information Technology - International Standardized Profiles - OSI Management - Management Functions - Part 8: AOM253x - Summarization Objects (including profiles AOM2531-AOM2539)

CAN/CSA-ISO/IEC ISP 10611-1-01:2001 信息技术 国际标准化配置文件 AMH1n 消息处理系统 通用消息传递 第1部分：MHS 服务支持

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10611-1:1997. 1 Scope 1.1 General This part of ISO/IEC ISP 10611 contains the overall specifications of the support of MHS Elements of Service and associated MHS functionality which are generally not appropriate for consideration only from the perspective of a single MHS protocol. These specifications form part of the Common Messaging application functions, as defined in the parts of ISO/IEC ISP 10611 , which form a common basis for content type-dependent International Standardized Profiles for MHS that will be developed. Such specifications are in many cases applicable to more than one MHS protocol or are otherwise concerned with component functionality which, although it can be verified via protocol, is not just related to protocol support. They are therefore designed to be referenced in the MHS Common Messaging application profiles ISO/IEC ISP 10611-3 (AMH11), ISO/IEC ISP 10611-4 (AMH12 and AMH14), ISO/IEC ISP 10611-5 (AMH13) and ISO/IEC ISP 10611-6 (AMH15), which specify the support of specific MHS protocols and associated functionality. The specifications in this part of ISO/IEC ISP 10611 cover the provision and use of features associated with the Message Transfer (MT) Service (MTS) (as defined in clause 8 of ISO/IEC 10021-1), together with those features associated with intercommunication with Physical Delivery (PD) Services (as defined in clause 10 of ISO/IEC 10021-1). Features which are associa ted with the Message Store (MS) and User Agent (UA) which are content type-independent are also covered. Features which are specific to a particular content type (including the provision of services by a UA to an MHS user) are covered in separate content type-dependent ISPs. The specifications in this part of ISO/IEC ISP 10611 are divided into basic requirements, which are required to be supported by all MHS implementations, and a number of optional functional groups, which cover significant discrete areas of related functionality which are not required to be supported by all implementations. An overview of the scope and applicability of the AMH1n set of profiles and of the structure of ISO/IEC ISP 10611 is provided in annex E. 1.2 Position within the taxonomy This part of ISO/IEC ISP 10611 is the first part, as common text, of a multipart ISP identified in ISO/IEC TR 10000-2 as AMH1, Message Handling Systems - Common Messaging. This part of ISO/IEC ISP 10611 does not, on its own, specify any profiles.

Information Technology - International Standardized Profiles AMH1n - Message Handling Systems - Common Messaging - Part 1: MHS Service Support

CAN/CSA-ISO/IEC ISP 10611-3-01:2001 信息技术 国际标准化配置文件 AMH1n 消息处理系统 通用消息传递 第3部分：AMH11 消息传输 (P1)（

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 10611-3:1997. 1 Scope 1.1 General This part of ISO/IEC ISP 10611 (AMH11) covers message transfer between message transfer agents (MTAs) using the P1 Message Transfer Protocol (see also figure 1). These specifications form part of the Common Messaging application functions, as defined in the parts of ISO/IEC ISP 10611, which form a common basis for content type-dependent International Standardized Profiles for MHS that will be developed. An MTA which conforms to profiles AMH11n as specified in this part of ISO/IEC ISP 10611 shall support a 'normal mode' OSI protocol infrastructure (AMH111) as required by both ISO/IEC 10021-6 and the ITU-T X.400 Recommendations, and may additionally support an 'X.410 mode' OSI protocol infrastructure (AMH112) as required, for ADMDs, by the ITU-T X.400 Recommendations. 1.2 Position within the taxonomy This part of ISO/IEC ISP 10611 is the third part of a multipart ISP identified in ISO/IEC TR 10000-2 as AMH1, Message Handling Systems - Common Messaging. This part of ISO/IEC ISP 10611 specifies the following profiles: AMH111 - Message Transfer (P1) - Normal mode AMH112 - Message Transfer (P1) - X.410(1984) mode The AMH11n profiles may be combined with any T-Profiles (see ISO/IEC TR 10000) specifying the OSI connection-mode Transport service. 1.3 Scenario The model used is one of two or more MTAs intercommunicating within a Message Transfer System (MTS) using the P1 protocol, as shown in figure 1. NOTE - In an ITU-T context, a domain may be treated as an MTA for the purposes of conformance to the AMH11n profiles. The AMH11n profiles cover all aspects of the MTA Abstract Service, as defined in clause 12 of ISO/IEC 10021-4, when realized using the P1 protocol.

Information Technology - International Standardized Profiles AMH1n - Message Handling Systems - Common Messaging - Part 3: AMH11 - Message Transfer (P1) (

CAN/CSA-ISO/IEC ISP 11186-1-2001(R2005) 信息技术 国际标准化配置文件 FVT3nn 虚拟终端基本类 属性分配类型定义寄存器 第1部分：FVT321 字体分配类型 No. 1

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 11186-1:1996. 1 Scope 1.1 General The concept of Profiles for OSI, and the structure of the International Standardized Profiles that document them, are defined in ISO/IEC TR 10000-l. Such Profiles are divided into a number of different classes and sub-classes. Two of these classes contain sub-classes comprising functions of the Virtual Terminal Basic Class Service and Protocol specified in the base standards ISO 9040 and ISO 9041. These are the Application Profiles (A-Profiles) and the Interchange Format and Representation Profiles (F-Profiles). The relationship between A-Profiles and F-Profiles is described in 7.3.2 of ISO/IEC TR 10000-l and is as follows. Application Layer base standards require, implicitly or explicitly, the structure of information carried or referenced by them to be specified for each instance of communication. It is the purpose of F-Profiles to specify such information structures. Particular functional requirements may then be met by the combination of an A-Profile with one or more F-Profiles. Establishment of a VT-association involves the selection by negotiation of a particular Virtual Terminal Environment profile (VTE-profile), and of particular values for any arguments of that VTE-profile. The VTE-profile specification, and possibly also the values of certain VTE-profile arguments, may in turn reference the definitions of VT control object types and attribute assignment types. These VTE-profiles, control object types and attribute assignment types are therefore Information Objects that require explicit reference within the VT protocol. Particular instances of these Information Objects are fully defined within the base standards, but the base standards also provide for further instances to be defined by registration. Each registered instance constitutes an F-Profile within the framework of ISO/IEC TR 10000. The Virtual Terminal Basic Class Service and Protocol may be used to realise a wide range of distinct functions. Particular fun ctions may be realised through the selection of appropriate VT functional units, F-Profiles and other VTE- profile argument values. The specification of the selection required to realise a particular function and to promote interoperability constitutes a Virtual Terminal A-Profile within the framework of ISO/IEC TR 10000. The three International Registers of VT information objects and the specifications of VT Application Profiles are each published as a separate multi-part ISP as follows: - ISO/IEC ISP 11184 is the Register of VTE-profiles; - ISO/IEC ISP 11185 is the Register of control object type definitions; - ISO/IEC ISP 11186 is the Register of attribute assignment type definitions; - ISO/IEC ISP 11187 contains the specifications of VT Appli cation Profiles. This part of ISO/IEC ISP 11186 contains the definition of a font assignment type that enables a font assignment value to be specified as a font resource property-list in accordance with ISO/IEC 9541-1. The properties that may be included in the property-list are specified as a subset of the properties defined for a character cell font. Particular provision is made for font resources in which the height and width of a character cell are integer multiples of the height and width of the character boxes that comprise the graphical images considered by the VT service. Provision is also made for the use of both left- to-right and right-to-left writing modes and for the coexistence of both modes in the display object.

Information Technology - International Standardized Profiles FVT3nn - Virtual Terminal Basic Class - Register of Attribute Assignment Type Definitions - Part 1: FVT321 - Font Assignment Type No. 1

CAN/CSA-ISO/IEC ISP 11186-2-2001(R2005) 信息技术 国际标准化配置文件 FVT3nn 虚拟终端基本类 属性分配类型定义寄存器 第2部分：FVT311 ISO/IEC 10646 的指令集分配类型

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 11186- 2:1996. 1 Scope 1.1 General The concept of Profiles for OSI, and the structure of the International Standardized Profiles that document them, are defined in ISO/IEC TR 10000-1. Such Profiles are divided into a number of different classes and sub-classes. Two of these classes contain sub-classes comprising functions of the Virtual Terminal Basic Class Service and Protocol specified in the base standards ISO 9040 and ISO 9041. These are the Application Profiles (A-Profiles) and the Interchange Format and Representation Profiles (F-Profiles). The relationship between A-Profiles and F-Profiles is described in 7.3.2 of ISO/IEC TR 10000-1 and is as follows. Application Layer base standards require, implicitly or explicitly, the structure of information carried or referenced by them to be specified for each instance of communication. It is the purpose of F-Profiles to specify such information structures. Particular fun ctional requirements may then be met by the combination of an A-Profile with one or more F-Profiles. Establishment of a VT-association involves the selection by negotiation of a particular Virtual Terminal Environment profile (VTE-profile), and of particular values for any arguments of that VTE-profile. The VTE-profile specification, and possibly also the values of certain VTE-profile arguments, may in turn reference the definitions of VT control object types and attribute assignment types. These VTE-profiles, control object types and attribute assignment types are therefore Information Objects that require explicit reference within the VT protocol. Particular instances of these Information Objects are fully defined within the base standards, but the base standards also provide for further instances to be defined by registration. Each registered instance constitutes an F-Profile within the framework of ISO/IEC TR 10000. The Virtual Terminal Basic Class Service and Protocol may be used to realise a wide range of distinct functions. Particular functions may be realised through the selection of appropriate VT functional units, F-Profiles and other VTE- profile argument values. The specification of the selection required to realise a particular function and to promote interoperability constitutes a Virtual Terminal A-Profile within the framework of ISO/IEC TR 10000. The three International Registers of VT information objects and the specifications of VT Application Profiles are each published as a separate multi-part ISP as follows: - ISO/IEC ISP 11184 is the Register of VTE-profiles; - ISO/IEC ISP 11185 is the Register of control object type definitions; - ISO/IEC ISP 11186 is the Register of attribute assignment type definitions; - ISO/IEC ISP 11187 contains the specifications of VT Application Profiles. This part of ISO/IEC ISP 11186 contains the definition of a repertoire assignment type for which a repertoire assignment value identifies a subset of the Universal Multiple-Octet Coded Character Set specified in the multi-part standard ISO/IEC 10646.

Information Technology - International Standardized Profiles FVT3nn - Virtual Terminal Basic Class - Register of Attribute Assignment Type Definitions - Part 2: FVT311 - Repertoire Assignment Type for ISO/IEC 10646

CAN/CSA-ISO/IEC ISP 12062-2-01:2001 信息技术 国际标准化配置文件 AMH2n 消息处理系统 人际消息传递 第2部分：AMH21 IPM 内容

This National Standard of Canada is equivalent to International Standard ISO/IEC ISP 12062-2:1997. 1 Scope 1.1 General This part of ISO/IEC ISP 12062 covers the interchange of messages between Interpersonal Messaging (IPM) User Agents (UAs) (see also figure 1). These specifications form part of the Interpersonal Messaging application functions, as defined in the parts of ISO/IEC ISP 12062, and are based on the Common Messaging content type-independent specifications in ISO/IEC ISP 10611. 1.2 Position within the taxonomy This part of ISO/IEC ISP 12062 is the second part of a multipart ISP identified in ISO/IEC TR 10000-2 as AMH2, Message Handling Systems - Interpersonal Messaging (see also ISO/IEC TR 10000-1, 8.2 for the definition of multipart ISPs). This part of ISO/IEC ISP 12062 specifies the following profile: AMH21 - IPM Content The AMH21 profile may optionally be combined with profiles AMH23, AMH24, AMH25 or AMH26 (see annex D of ISO/IEC ISP 12062- 1) specifying OSI MHS communications protocols and supporting services for an IPM UA. 1.3 Scenario The model used is one of indirect interchange of interpersonal messages (content types 22 and 2) between IPM UAs via an intermediate Message Transfer System (MTS), as shown in figure 1. The provision of, and access to, the MTS is outside the scope of this profile. The MHS services and functions covered by the AMH21 profile are specified in ISO/IEC 10021-7. There are no OSI upper layer services and protocols within the scope of the AMH21 profile.

Information Technology - International Standardized Profiles AMH2n - Message Handling Systems - Interpersonal Messaging- Part 2: AMH21 - IPM Content

CAN/CSA-ISO/IEC ISP 12072:2001 信息技术 International Standardized Profile FDI5 Directory data definitions VT Use of the Directory

Information technology - International Standardized Profile FDI5 - Directory data definitions - VT Use of the Directory