AS/NZS ISO/IEC 14752:2003

1 - AS/NZS ISO/IEC 14752:2003 INFORMATION TECHNOLOGY-OPEN DISTRIBUTED PROCESSING-PROTOCOL SUPPORT FOR COMPUTATIONAL INTERACTIONS
4 - PREFACE
5 - CONTENTS
7 - 1 Scope
8 - 2 Normative References
8 - 2.1 Identical Recommendation | International Standards
8 - 2.2 Other Specifications
8 - 3 Definitions
8 - 3.1 Terms defined in the ODP Reference Model: Foundations
9 - 3.2 Terms defined in the ODP Reference Model: Architecture
9 - 3.3 Definitions for protocol support for computational interactions
9 - 3.3.1 access facility:
9 - 3.3.2 association:
9 - 3.3.3 association management facility:
9 - 3.3.4 basic interworking facility:
9 - 3.3.5 client-side:
9 - 3.3.6 deliver primitive:
9 - 3.3.7 invocation submit:
10 - 3.3.8 invocation deliver:
10 - 3.3.9 location facility:
10 - 3.3.10 server-side:
10 - 3.3.11 service primitive:
10 - 3.3.12 submit primitive:
10 - 3.3.13 termination deliver:
10 - 3.3.14 termination submit:
10 - 4 Abbreviations
10 - 5 Conventions
10 - 6 Overview
10 - 6.1 General Interworking Framework
11 - 6.2 Liaisons between channel objects
12 - 6.3 Facilities of the GIF
12 - 6.4 Computational operations and signals
13 - 6.5 Encoding of computational information
13 - 7 Interface references
13 - 8 Service model
13 - 8.1 Service primitives
14 - 8.2 Associations
15 - 9 Basic interworking facility
15 - 9.1 Request
15 - 9.1.1 Purpose
15 - 9.1.2 Request submit
15 - 9.1.3 Request deliver
15 - 9.1.4 Parameters
16 - 9.2 Result
16 - 9.2.1 Purpose
16 - 9.2.2 Result submit
16 - 9.2.3 Result deliver
16 - 9.2.4 Parameters
16 - 9.2.5 Effects
16 - 9.3 Cancel
16 - 9.3.1 Purpose
16 - 9.3.2 Cancel submit
17 - 9.3.3 Cancel deliver
17 - 9.3.4 Parameters
17 - 9.4 Abort
17 - 9.4.1 Purpose
17 - 9.4.2 Abort deliver
17 - 9.4.3 Parameters
17 - 9.4.4 Effects
17 - 9.5 State table for the Basic Interworking Facility
17 - 9.5.1 Client-side state table
18 - 9.5.2 Server-side state table
18 - 10 Access facility
18 - 10.1 Syntax-propose
18 - 10.1.1 Purpose
18 - 10.1.2 Syntax-propose submit
18 - 10.1.3 Syntax-propose deliver
18 - 10.1.4 Parameters
19 - 10.2 Syntax-advise
19 - 10.2.1 Purpose
19 - 10.2.2 Syntax-advise submit
19 - 10.2.3 Syntax-advise deliver
19 - 10.2.4 Parameters
19 - 10.2.5 Effects
19 - 10. 3 Access-cancel
19 - 10.3.1 Purpose
19 - 10.3.2 Access-cancel submit
19 - 10.3.3 Access-cancel deliver
19 - 10.3.4 Parameters
20 - 10.4 Access-abort
20 - 10.4.1 Purpose
20 - 10.4.2 Access-abort submit
20 - 10.4.3 Access-abort deliver
20 - 10.4.4 Parameters
20 - 10.4.5 Effects
20 - 10.5 State table for the Access Facility
21 - 11 Location facility
21 - 11.1 Location-query
21 - 11.1.1 Purpose
21 - 11.1.2 Location-query submit
21 - 11.1.3 Location-query deliver
21 - 11.1.4 Parameters
21 - 11.2 Location-advise
21 - 11.2.1 Purpose
21 - 11.2.2 Location-advise submit
21 - 11.2.3 Location-advise deliver
22 - 11.2.4 Parameters
22 - 11.2.5 Effects
22 - 11.3 Location-cancel
22 - 11.3.1 Purpose
22 - 11.3.2 Location-cancel submit
22 - 11.3.3 Location-cancel deliver
22 - 11.3.4 Parameters
23 - 11.4 Location-abort
23 - 11.4.1 Purpose
23 - 11.4.2 Location-abort deliver
23 - 11.4.3 Parameters
23 - 11.4.4 Effects
23 - 11.5 State table for the Location Facility
23 - 11.5.1 Client-side state table
23 - 11.5.2 Server-side state table
24 - 12 Association management facility
24 - 12.1 Association-request
24 - 12.1.1 Purpose
24 - 12.1.2 Association-request submit
24 - 12.1.3 Association-request deliver
24 - 12.1.4 Parameters
24 - 12.2 Association-accept
24 - 12.2.1 Purpose
24 - 12.2.2 Association-accept submit
24 - 12.2.3 Association-accept deliver
25 - 12.2.4 Parameters
25 - 12.3 Association-reject
25 - 12.3.1 Purpose
25 - 12.3.2 Association-reject submit
25 - 12.3.3 Association-reject deliver
25 - 12.3.4 Parameters
25 - 12.4 Association-close
25 - 12.4.1 Purpose
25 - 12.4.2 Association-close submit
25 - 12.4.3 Association-close deliver
26 - 12.4.4 Parameter
26 - 12.5 Association-abort
26 - 12.5.1 Purpose
26 - 12.5.2 Association-abort submit
26 - 12.5.3 Association-abort deliver
26 - 12.5.4 Parameter
26 - 12.6 State table for the Association Management Facility
28 - Annex A - Mapping to CORBA GIOP and IIOP
28 - A.1 Introduction
28 - A.2 Conventions
28 - A.3 Generic Inter-Orb Protocol
30 - A.4 Mapping of parameters
33 - A.5 GIOP Message encoding
33 - A.6 Internet Inter-Orb Protocol
33 - A.7 Mapping of Association management primitives to TCP events
34 - A.8 Interface references
35 - Annex B - Outline of mapping to DCE-CIOP

Based on the framework of abstractions and concepts developed in the Reference Model for Open Distributed Processing. It defines how interactions between computational objects in a computational specification of a system relate to protocol support for those interactions in an engineering specification of that system.

This Recommendation | International Standard is based on the framework of abstractions and concepts developed in the Reference Model for Open Distributed Processing (ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 | ISO/IEC 10746-3).This Recommendation | International Standard defines how interactions between computational objects in a computational specification of a system relate to protocol support for those interactions in an engineering specification of that system. In particular it:– defines a General Interworking Framework (GIF);– within the GIF, defines a set of facilities each comprising a set of functionally-related service primitives as abstract definitions of the interactions of basic engineering objects and channel objects;– defines the parameters of the service primitives of the GIF;– defines the permitted sequence of the service primitives by means of state tables;– specifies, in annexes, the mapping of the GIF service primitives and their parameters to the messages and fields of particular protocols.As specified in this Recommendation | International Standard, the GIF defines protocol support for a pragmatic subset of the possible computational interactions defined in ITU-T Rec. X.903 | ISO/IEC 10746-3. It is also restricted in the features of the protocol support and the supported transparencies.The GIF, as specified here, defines:– support for computational operations, but not for streams;– support using stub, binder and protocol objects hierarchically, such that any interaction at the interworking reference point of the supporting protocol object supports liaisons of one of those objects or of the basic engineering object, and any interaction to support those liaisons is passed via that interworking reference point; and– interactions at a single interworking reference point, from the perspective of one side; interceptors are not explicitly considered;NOTE 1 – It is intended that the GIF could be extended, in a future amendment, to support streams and flows. The present specification is restricted to areas that are technically stable.The GIF supports at least some forms of:– access transparency; and– location transparency.The GIF as specified here also supports a limited equivalent of relocation transparency. Other transparencies are not addressed in this present specification.NOTE 2 – It is intended that the GIF could be extended, in future amendments, to support additional transparencies.The GIF does not explicitly model Quality of Service requirements.The application of security-related issues to the GIF are not included in the current text and are for further study.The set of mappings to particular protocols specified in annexes to this Recommendation | International Standard is not exhaustive. The GIF could be mapped to other protocols.NOTE 3 – In particular, a mapping to the DCOM protocol family would be a candidate for an additional annex.

First published as AS/NZS ISO/IEC 14752:2003.