1、BRITISH STANDARD BSISO/IEC 10026-6:1995 Implementation of ISOISO/IEC10026-6:1995 Information technology OpenSystems Interconnection Distributed Transaction Processing Part 6: Unstructured Data Transfer ICS35.100.70BSISO/IEC10026-6:1995 This BritishStandard, having been prepared under the directionof
2、 the Information Systems Technology Assembly, was published under the authorityof the Standards Boardand comes into effect on 15November1995 BSI01-2000 The following BSI references relate to the work on this standard: Committee referenceIST/21 Draft for comment92/65684DC ISBN 0 580 24859 3 Committee
3、s responsible for this British Standard The preparation of this BritishStandard was entrusted to Technical Committee IST/21, OSI, Data management and open distributed processing, upon which the following bodies were represented: British Computer Society British Telecommunications plc CCTA (the Gover
4、nment Centre for Information Systems) Digital Equipment Co. Ltd. IBM United Kingdom Ltd. International Computers Limited Joint Information Systems Committee Level7 Ltd. Logica UK Ltd. National Computing Centre Ltd. National Health Services Nine Tiles K-net PSC International Ltd. Rank Xerox Ltd. SEMA
5、 Group Systems Ltd. X Open Company Ltd. Amendments issued since publication Amd. No. Date CommentsBSISO/IEC10026-6:1995 BSI 01-2000 i Contents Page Committees responsible Inside front cover National foreword ii Foreword iii Text of ISO/IEC10026-6 1BSISO/IEC10026-6:1995 ii BSI 01-2000 National forewo
6、rd This BritishStandard reproduces verbatim ISO/IEC10026-6:1995 and implements it as the UK national standard. This BritishStandard is published under the direction of the Information Systems Technology Assembly whose Technical CommitteeIST/21 has the responsibility to: aid enquirers to understand t
7、he text; present to the responsible international committee any enquiries on interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK. NOTEInternational and EuropeanStandards, as well as overseas st
8、andards, are available from Customer Services, BSI,389 Chiswick High Road, London W44AL. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of
9、 itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pagesi andii, theISO/IEC title page, pagesiitoiv, pages1 to8, an inside back cover andabackcover. This standard has been updated (see copyright date) and may have had amendm
10、ents incorporated. This will be indicated in the amendment table on the inside front cover.ISO/IEC10026-6:1995(E) ii BSI 01-2000 Contents Page Foreword iii Introduction 1 1 Scope 1 2 Normative references 1 3 Definitions 1 4 Abbreviations 1 5 Conventions 2 6 Unstructured Data Transfer in OSITP 2 7 UD
11、T ASE Specification 3 8 Conformance 3 Annex A (normative) Unstructured data transfer Procedures, abstract andtransfer syntaxes, and application context for octet string mapping 4 Annex B (informative) Unstructured data transfer Applicationcontextdefinition proforma 6 Annex C (informative) Unstructur
12、ed data transfer Exampleofabstractandtransfer syntax specification Inside back coverISO/IEC10026-6:1995(E) BSI 01-2000 iii Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardizati
13、on. National bodies that are members of ISO or IEC participate in the development of InternationalStandards 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 i
14、nterest. 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/IECJTC1. Draft InternationalStandards adopted by the joint tec
15、hnical committee are circulated to national bodies for voting. Publication as an InternationalStandard requires approval by at least75% of the national bodies casting a vote. InternationalStandard ISO/IEC10026-6 was prepared by Joint Technical Committee ISO/IECJTC1, Information technology, Subcommit
16、tee SC21, Open systems interconnection, data management and open distributed processing. ISO/IEC10026 consists of the following parts, under the general title Information technology Open Systems Interconnection Distributed Transaction Processing: Part 1: OSITP Model; Part 2: OSITP Service; Part 3: P
17、rotocol specification; Part 4: Protocol Implementation Conformance Statement (PICS) proforma; Part 5: Application context proforma and guidelines when using OSI TP; Part 6: Unstructured Data Transfer. Annex A forms an integral part of this part of ISO/IEC10026. Annex B and Annex C are for informatio
18、n only.iv blankISO/IEC10026-6:1995(E) BSI 01-2000 1 Introduction ISO/IEC10026 is one of a set of standards produced to facilitate the interconnection of computer systems. It is related to other International Standards in the set as defined by the Reference Model for Open Systems Interconnection (ISO
19、7498). The Reference Model subdivides the area of standardization for interconnection into a series of layers of specification, each of manageable size. The aim of Open Systems Interconnection is to allow, with a minimum of technical agreement outside the interconnection standards, the interconnecti
20、on of computer systems a) from different manufacturers; b) under different management; c) of different levels of complexity; and d) of different technologies. ISO/IEC10026-1, ISO/IEC10026-2 and ISO/IEC10026-3 define the OSI TP Model, OSITPService and OSI TP Protocol available within the Application
21、Layer of the OSI Reference Model. ISO/IEC10026-4 is the OSI TP PICS and ISO/IEC10026-5 defines the Application Context Proforma and Guidelines When Using OSI TP. This part of ISO/IEC10026 defines a model for unstructured data transfer within the OSI TP environment. UDT operates within the constraint
22、s specified for U-ASEs in ISO/IEC10026. UDT is not suitable for use outside the OSI TP environment. 1 Scope This part of ISO/IEC10026 provides a model for the transfer of application data for transaction processing applications whose application-specific protocol has not been standardized within the
23、 OSI environment. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC10026. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreemen
24、ts based on this part of ISO/IEC10026 are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. Members of IEC and ISO maintain registers of currently valid InternationalStandards. ISO/IEC9646-1:1994, Information technology Open Systems Interco
25、nnection Conformance testing methodology and framework Part1:General concepts. ISO/IEC9646-2:1994, Information technology Open Systems Interconnection Conformance testing methodology and framework Part2:Abstract Test Suite specification. ISO/IEC9646-3:1992, Information technology Open Systems Interc
26、onnection Conformance testing methodology and framework Part3: The Tree and Tabular Combined Notation (TTCN). ISO/IEC9646-4:1994, Information technology Open Systems Interconnection Conformance testing methodology and framework Part4: Test realization. ISO/IEC9646-5:1994, Information technology Open
27、 Systems Interconnection Conformance testing methodology and framework Part5:Requirements on test laboratories and clients for the conformance assessment process. ISO/IEC9834-1:1993, Information technology Open Systems Interconnection Procedures for the operation of OSI Registration Authorities Part
28、1:General procedures. ISO/IEC10026-1:1992, Information technology Open Systems Interconnection Distributed Transaction Processing Part1: OSI TP Model. ISO/IEC10026-2:1992, Information technology Open Systems Interconnection Distributed Transaction Processing Part2: OSI TP Service. ISO/IEC10026-3:199
29、2, Information technology Open Systems Interconnection Distributed Transaction Processing Part 3: Protocol specification. ISO/IEC10731:1994, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition of OSI services. 3 Definitions For the purposes of thi
30、s part of ISO/IEC10026, the definitions given in ISO/IEC10026-1 and the following definition apply: 3.1 non-OSI-standard a specification not formally approved by the recognized world-wide standardization bodies forOSI 4 Abbreviations Abbreviations used in this part of ISO/IEC10026 are defined in ISO
31、/IEC10026-1, except the following: UD Unstructured Data UDT Unstructured Data TransferISO/IEC10026-6:1995(E) 2 BSI 01-2000 5 Conventions This part of ISO/IEC10026 uses the conventions defined in ISO/IEC10731. 6 Unstructured Data Transfer in OSI TP 6.1 Purpose This part of ISO/IEC10026 defines two ap
32、proaches for transferring application data which allow non-OSI-standardized applications to operate in the OSI TP environment. UDT, thus, provides for the rapid migration of networked transaction programs which were originally written for operation in networks without facilities similar to those of
33、theOSI Application and Presentation Layers (i.e.,forinteroperation between heterogeneous systems). It should be emphasized that the second form of UDT described in6.2 (“restricted UDT”) should only be used in specialized circumstances, i.e.,where there is a need to exchange APDUs of existing applica
34、tions in an OSI TP environment. Adopting this approach will prevent applications from exploiting the important features of the Presentation Layer. 6.2 Model for UDT In order to transfer data between application programs (TPSUIs) in an OSI TP environment, the applications must make use of the facilit
35、ies of the Presentation Service. This part of ISO/IEC10026 does not define a service to offer Presentation facilities to the application; rather it assumes that the necessary elements of the Presentation Service will be made available to the application. NOTEIn a real implementation, it is assumed t
36、hat the API being provided for application communication (e.g.for “peer-to-peer” operation) would include a service that would be mapped directly to the relevant Presentation Layer facilities. In order to make correct use of the Presentation Layer, the application program must specify what abstract
37、and transfer syntaxes are to be used. UDT assumes that cooperating TPSUIs exchanging the APDUs of a non-standardized protocol will have a priori knowledge of the syntax and semantics of the protocol APDUs, thus enabling the TPSUIs to correctly generate and interpret the data being exchanged. The abs
38、tract and transfer syntaxes being used must be registered with an OSI registration authority operating under the procedures of ISO/IEC9834-1. The unambiguous names resulting from this registration are used to denote the application protocols syntaxes during Presentation negotiation. It is also neces
39、sary that the name of any application context being used be similarly registered. This registered application context name is used by ACSE; it implies the application layer semantics and mappings of all the application protocols that may be used during that instance of communication, including the o
40、ne (or more) using the UDT approach. UDT may be used in two ways as described below. 6.2.1 Using UDT with registered syntaxes The recommended approach is to register the application protocols abstract and transfer syntaxes, so that the resulting names may be used in transferring APDUs using Presenta
41、tion Services. (Normally, the P-Data service will be used to transfer APDUs, although other Presentation services may also be used, so long as this is done in a manner which will not interfere with TPs use of the Presentation Layer.) Typically, it will also be necessary to specify an application con
42、text name. Annex B contains an application context proforma that may be completed to yield a complete application context definition, for registration under the procedures of ISO/IEC9834-1. 6.2.2 Using UDT with a priori knowledge of application syntax In the case where it is not convenient to regist
43、er a non-OSI-standardized application protocols syntaxes, it may be possible to present application data values as sequences of octets. In support of this approach, Annex A provides generic abstract and transfer syntax names (together with an application context name) which can be used to support th
44、e mapping of any application protocols abstract and transfer syntax onto such a sequence of octets. In other words, these generic abstract and transfer syntax names can be used to provide a means whereby APDUs may be transferred without the need to register or more specifically define the applicatio
45、n protocol. It must be emphasized, however, that adopting this approach requires that cooperating TPSUIs have a priori knowledge of the syntax, semantics, and mapping of the APDUs; this is required if the TPSUIs are to correctly generate and interpret both the syntax and semantics of the messages th
46、us exchanged using the octet string mapping described in Annex A.ISO/IEC10026-6:1995(E) BSI 01-2000 3 7 UDT ASE Specification 7.1 Overview The UDT ASE is an essentially null ASE that acts as the User-ASE in the TP model when the application protocol requires no additional protocol support from the U
47、ser-ASE within the TPPM other than the specification of the mapping to the Presentation service. The UDT ASE has one service, UD-TRANSFER that models the transmission of data between the TPSUIs on a TP dialogue. The UD-TRANSFER service is subject to the constraints specified for the generic TP-DATA
48、specified in ISO/IEC10026-2 and ISO/IEC10026-3. The service relates to a particular dialogue. 7.2 Primitives and their parameters Primitive names: UD-TRANSFER request UD-TRANSFER indication 7.2.1 User-data is a parameter that carries the non-OSI-standardized protocol to be exchanged between cooperat
49、ing peer TPSUIs. 7.3 Sequence of primitives The sequence of primitives for the UD-TRANSFER service is defined by the following time sequence diagram: 7.4 Procedures When a TPSUI wishes to transmit an APDU, it issues a UD-Transfer request with the APDU as User-Data; this UD-Transfer request is mapped directly to the user data of an appropriate Presentation or TP service primitive, with the APDU being mapped according to the transfer syntax being used. The use made of Presentation services must be consistent with OSI TP
