ANSI INCITS ISO IEC 10026-6-1995 Information technology Open Systems Interconnection Distributed Transaction Processing - Part 6 Unstructured Data Transfer (Adopted by INCITS).pdf

1、INTERNATIONAL STANDARD ISOJIEC 10026-6 First edition 1995-07-01 Information technology - Open Systems Interconnection - Distributed Transaction Processing - Part 6: Unstructured Data Transfer Technologies de /information - lnterconnexion de syst b) under different management; c) of different levels

2、of complexity; and d) of different technologies. ISO/IEC 10026-1, -2 and -3 define the OS1 TP Model, OS1 TP Service and OS1 TP Protocol available within the Application Layer of the OS1 Reference Model. ISO/IEC 10026-4 is the OS1 TP PICS and ISO/IEC 10026-5 defines the Application Context Proforma a

3、nd Guidelines When Using OS1 TP. This part of ISO/IEC 10026 defines a model for unstructured data transfer within the OS1 TP environment. UDT operates within the constraints specified for U-ASEs in ISO/IEC 10026. UDT is not suitable for use outside the OS1 TP environment. 111 INTERNATIONAL STANDARD

4、0 ISO/IEC ISO/IEC 10026-6:1995(E) Information technology - Open Systems Interconnection - Distributed Transaction Processing - Part 6: Unstructured Data Transfer 1 Scope This part of ISO/LEC 10026 provides a model for the transfer of application data for transaction processing applications whose app

5、lication-specific protocol has not been standardized within the OS1 environment. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this part of ISO/IEC 10026. At the time of publication, the editions indicated were valid

6、. All standards are subject to revision, and parties to agreements based on this part of ISOfiEC 10026 are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. Members of IEC and IS0 maintain registers of currently valid international standard

7、s. ISO/IEC 9646-1:1994, Information technology - Open Systems Interconnection - Conformance testing methodology and framework- Part 1: General concepts. ISO/IEC 9646-2: 1994, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test

8、 Suite specification. ISO/IEC 9646-3: 1992, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN). ISOIIEC 9646-4: 1994, Information technology - Open Systems Interconnection - Conformance testing

9、 methodology and framework-Part 4: Test realization. ISOAEC 9646-5: 1994, Information technology - Open Systems Interconnection - Conformance testing methodology and framework-Part 5: Requirements on test laboratories and clients for the conformance assessment process. ISO/IEC 9834-1:1993 Informatio

10、n technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities- Part 1: General procedures. ISO/IEC 10026-1:1992, Information technology - Open Systems Interconnection - Distributed Transaction Processing -Part I: OSI TP Model. ISO/IEC 10026-2: 1992, Infor

11、mation technology - Open Systems Interconnection - Distributed Transaction Processing-Part 2: OSI TP Service. ISO/IEC 10026-3:1992, Information technology - Open Systems Interconnection - Distributed Transaction Processing-Part 3: Protocol specification. ISOIIEC 1073 1: 1994, Information technology

12、- Open Systems Interconnection - Basic Reference Model - Conventions for the definition of OSI services. 3 Definitions For the purposes of this part of ISO/IEC 10026, the definitions given in ISO/IEC 10026-l and the following definition apply: 3.1 non-OSI-standard: A specification not formally appro

13、ved by the recognized world-wide standardization bodies for OSI. 4 Abbreviations Abbreviations used in this part of ISO/IEC 10026 are defined in ISO/IEC 10026-1, except the following: UD unstnlctllred Data UDT Unstructured Data Transfer 5 Conventions This part of ISO/IEC 10026 uses the conventions d

14、efined in ISO/IEC 1073 1. ISO/IEC10026-6:1995(E) 0 ISO/IEC 6 Unstructured Data Transfer in OS1 TP 6.2.1 Using UDT with registered syntaxes 6.1 Purpose This part of ISO/IEC 10026 defines two approaches for transferring application data which allow non-OSI-standardized applications to operate in the O

15、S1 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 the OS1 Application and Presentation Layers (i.e., for interoperation between heterogeneous systems). It sho

16、uld be emphasized that the second form of UDT described in 6.2 (restricted UDT) should only be used in specialized circumstances, i.e., where there is a need to exchange APDUs of existing applications in an OS1 TP environment. Adopting this approach will prevent applications from exploiting the impo

17、rtant features of the Presentation Layer. 6.2 Model for UDT In order to transfer data between application programs (TPSUIs) in an OS1 TP environment, the applications must make use of the facilities of the Presentation Service. This part of ISO/IEC 10026 does not define a service to offer Presentati

18、on facilities to the application; rather it assumes that the necessary elements of the Presentation Service will be made available to the application. NOTE - In a real implementation, it is assumed that the API being provided for application communication (e.g. for peer-to-peer operation) would incl

19、ude 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 and transfer syntaxes are to be used. UDT assumes that cooperating TPSUIs exchanging the APDUs of a no

20、n-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 abstract and transfer syntaxes being used must be registered with an OS1 registration authority operating

21、 under the procedures of ISO/IEC 9834-l. The unambiguous names resulting from this registration are used to denote the application protocols syntaxes during Presentation negotiation. It is also necessary that the name of any application context being used be similarly registered. This registered app

22、lication 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 one (or more) using the UDT approach. The recommended approach is to register the application protocol

23、s abstract and transfer syntaxes, so that the resulting names may be used in transferring APDUs using Presentation 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 interfe

24、re with TPs use of the Presentation Layer.) Typically, it will also be necessary to specify an application context 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/IEC 9834- 1

25、. 6.2.2 Using UDT with a priori knowledge of application syntax In the case where it is not convenient to register a non-OSI- standardized application protocols syntaxes, it may bc possible to present application data values as sequences of octets. In support of this approach, annex A provides gener

26、ic abstract and transfer syntax names (together with an application context name) which can be used to support the 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

27、 a means whereby APDUs may be transferred without the need to register or more specifically define the application 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 i

28、s required if the TPSUIs are to correctly generate and interpret both the syntax and semantics of the messages thus exchanged using the octet string mapping described in annex A. 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 whe

29、n the application protocol requires no additional protocol support from the User-ASE within the TPPM other than the specification of the mapping to the Presentation service. The UDT ASE has one service, LID-TRANSFER that models the transmission of data between the TPSUIs on a TP dialogue. The UD-TRA

30、NSFER service is subject to the constraints specified for the generic TP-DATA specified in ISO/IEC 10026-2 and 3. The service relates to a particular dialogue. UDT may be used in two ways as described below. 0 ISO/IEC ISO/IEC10026-6:1995(E) 7.2 Primitives and their parameters Primitive names: UD-TRA

31、NSFER request UD-TRANSFER indication Key: M : presence of the parameter is mandatory. = : indicates that a parameter value is semantically equal to the value of the parameter of the preceding primitive in the table. 7.2.1 User-data is a parameter that carries the non-OSI- standardized protocol to be

32、 exchanged between cooperating peer TPSUIs. 7.3 Sequence of primitives The sequence of primitives for the UD-TRANSFER service is defined by the following time sequence diagram: UD-TRANSFER indication 7.4 Procedures When a TPSUI wishes to transmit an APDU, it issues a UD- Transfer request with the AP

33、DU as User-Data; this UD- Transfer request is mapped directly to the user dam 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 OS1 TPs use of these services, a

34、nd is constrained by the SACF and MACF rules of TP. The use of Presentation may be more precisely determined by the application context definition which is in use, or by bilateral agreement. The user data parameter of the UD-Transfer request (i.e., the application dam being transmitted) will be sent

35、 as one or more presentation data values in the UDT presentation context. These may or may not be concatenated according to the SACF rules in force. On receipt, presentation data values received in a UDT presentation context are mapped to the user data of a UD- Transfer indication. It is the respons

36、ibility of the specifications of the abstract syntax, transfer syntax and application context (together) to ensure that the user data on a single UD-Transfer indication has the same value as the user data on the corresponding UD- Transfer request. 7.5 Collisions A collision of a UD-TRANSFER request

37、and indication are not treated as a collision but are each handled separately. 7.6 Disruption The UD-TRANSFER service does not disrupt any other service. The UD-TRANSFER service is disrupted by any service that disrupts the underlying service (i.e., P-DATA service or which ever other service is used

38、). If the UD- TRANSFER service is used with OS1 TP as the actual replacement for the TP-DATA service, then the disruption and purging rules given in ISO/IEC 10026-2 and -3 for the TP- DATA service apply. NOTES 1. In particular, abort and resynchronization services may disrupt the UD-TRANSFER. 2. If

39、the UD-TRANSFER service is mapped to another service, such as TP-BEGIN-DIALOGUE or TP-ABORT, then the disruption rules for that service apply. 8 Conformance To conform to this part of ISO/IEC 10026, a system shall implement the procedures specified in clause 7 or, in the case of UDT with a priori kn

40、owledge of Application Syntax, the conformance statement in A.2.11 shall apply. 3 ISO/IEC 10026-6:1995(E) 0 ISO/IEC Annex A (normative) Unstructured data transfer - Procedures, abstract and transfer syntaxes, and application context for octet string mapping This annex contains the procedures, abstra

41、ct and transfer syntax names, and a full application context which apply when a non-ISO-standardized application protocol is transferred as the value of an octet string (with a bilateral agreement between communicating TPSUIs). See 6.2.2. A.1 Procedures These procedures apply only when the applicati

42、on APDUs are transferred as a sequence of octets. A.l.l Receiving a UD-TRANSFER request Upon receipt of a UD-TRANSFER request, the application data contained in the user-data field is mapped to a single pdv (to ensure that all the application data is transmitted as a whole) for transmission (using t

43、he transfer syntax defined in A. 1.4) according to the mapping rules in A.2.8.1.4. NOTE - these procedures only apply to the UD-TRANSFER service, not to other services defined in ISO/IEC 10026-3. A.1.2 Receiving application data Upon receipt of a single presentation data value which is a presentatio

44、n context for restricted UDT, a UD-Transfer indication is generated whose user-data is mapped from the received pdv. A.1.3 Abstract syntax name The OBJECT IDENTIFIER (iso(1) standard(O) tp(10026) udt(6) generic-abstract-syntax(l) version( 1) can be used as an abstract syntax name for any application

45、 protocol whose detailed abstract syntax is defined elsewhere and is known Q priori to the communicating TPSUIs. This name is registered with this part of ISO/IEC 10026. A.1.4 Transfer syntax name The OBJECT IDENTIFIER (joint-isoccitt asnl(1) basic-encoding(l) is used as the transfer syntax name for

46、 the transfer syntax formed by taking an ordered sequence of octets (which is the representation of a value of an abstract syntax identified by the OBJECT IDENTIFIER in A.1.3, encoded in a manner that is also known a priori to the communicating TPSUIs) as the value of an ASN.l type OCTET STRING and

47、encoding this according to the Basic Encoding Rules, with the restriction that the primitive encoding shall be used. A single pdv shall be treated as a separate and complete value of the type ASN.l OCTET STRING. NOTE - The effect of this is that the sequence of octets passed from the sending TPSUI i

48、s prefixed with the tag for OCTET STRING and a length field, and is treated as the “single-ASN.l- type” of the “presentation-data-values” CHOICE by the presentation protocol. A.2 Application Context This clause contains the full application context for use when application APDUs are transferred as a

49、 sequence of octets as defined by the procedures in this annex. A.2.1 Application context name The OBJECT IDENTIFIER for this application context is (iso(1) standard(O) tp( 10026) udt(6) applicationcontext(2) This application context supports the serial execution of both application and provider supported transactions over an association. This name is registered with this part of ISO/IEC 10026. A.2.2 Purpose and scope The purpose of this application context is to provide the TPSUIs participating in a TP dialogue with an environment for exchanging application da