Recommendation T.522 COMMUNICATION APPLICATION PROFILE BT1 FOR DOCUMENT BULK TRANSFER CONTENTS 0 Introduction 1 Scope and field of application 2 References 3 Definitions 4 Abbreviations and conventions 5 Definition of communication application profile BT1 5.1 Overview of BT1 5.2 DTAM functional units 5.3 DTAM service primitives and parameters 0 Introduction T.400 Series of Recommendations define the open document architecture (T.410 Series) and the DTAM services and protocols (T.430 Series) for the purpose of the document transfer and manipulation. In order to apply T.400 Series to various telematic services, it is necessary to specify the DTAM application profile for each service that consists of a document application profile and a communca- tion application profile. According to this requirement, T.500 Series of Recommendations define the document application profiles and T.520 Series of Recommendations define the communication application profiles. Recommendation T.522 is one of a set of T.520 Series of Recommendations to define the communi- cation application profile for the document bulk transfer using X.200 environment. 1 Scope and field of application This Recommendation defines the communication application profile for the document bulk transfer in terms of: a) DTAM functional units used; b) DTAM service primitives and parameters used. 2 References The following references are required in order to implement this communication profile defined in this Recommendation. - Rec. T.431: Document transfer and manipulation (DTAM) - Services and protocols - Introduction and general principles - Rec. T.432: Document transfer and manipulation (DTAM) - Services protocols - Service definition - Rec. T.433: Document transfer and manipulation (DTAM) - Services and protocols - Protocol specification Fascicle VII.7 - Rec. T.522 1 3 Definitions The definitions of T.400 Series of Recommendations also apply to this Recommendation. 4 Abbreviations and conventions The abbreviations and conventions defined in T.400 Series of Recommendations also apply to this Recommendation. 5 Definitions of communication application profile BT1 5.1 Overview of BT1 This Recommendation defines functional units and communication support function in accordance with Recommendation T.431. 5.2 DTAM functional units The following functional units defined in Recommendation T.432 are used for BT1: - association use control (kernel); - capability; - document bulk transfer; - token control; - exception report; - reliable transfer mode 2. 5.3 DTAM service primitives and parameters General DTAM service definition and parameters are defined in Recommendation T.432. This section specifies the parameters of DTAM service of BT1. 5.3.1 D-INITIATE service parameters The following parameters of this service are used as follows: - telematic requirements; - application capabilities; - result. The parameter "transparent mode" is not used. Table 1-A/T.522 lists the D-INITIATE service parameters. 1) Telematic requirements The following functional units defined in Recommendation T.432 are used for BT1 as mandatory functional units: - association control (kernel); - document bulk transfer; - token control; - exception report; 2 Fascicle VII.7 - Rec. T.522 - reliable transfer mode 2. The following functional units defined in Recommendation T.432 are used for BT1 as optional functional units: - capability. Fascicle VII.7 - Rec. T.522 3 2) Application capabilities This "application capabilities" is defined in Recommendation T.432 and the following sub- parameters are used: a) document application profile This parameter indicates the document application profile being used. Its value is specified in Recommendations that define terminal characteristics for particular telematic services. b) non-basic document characteristics This is the "non-basic document characteristics" defined in Recommendation T.432. c) non-basic structure characteristics This is the "non-basic structure characterisitcs" defined in Recommendation T.432. 3) Result This field can take all the values defined in Recommendation T.432. TABLE 1-A/T.522 D-INITIATE service parameters w 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴쩡컴컴컴컴컴컫컴컴컴컴컴컴쩡컴컴컴컴컴커 � 쿏-INITIATE � D-INITIATE � D-INITIATE � D- INITIATE � � � request � indication � response � confirm � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴캑 � Telematic requirements � M � M(=) � M � M(=) � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � � � � � Application capabilities � M � M(=) � M � M(=) � � ---------------------------------� � � � � � | Document application profile � M � M(=) � M � M(=) � � | � � � � � � | Non-basic document � U � C(=) � U � C(=) � � | characteristics � � � � � � | � � � � � � | Non-basic structure � U � C(=) � U � C(=) � � | characteristics � � � � � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � � � � � Result � � � U � C(=) � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴켸 5.3.2D-TERMINATE service parameters This service has no parameter for BT1. Only the initiator can issue D-TERMINATE. In addition, the initiator can issue D-TERMINATE only if he has a data token. 5.3.1.3 D-U-ABORT service parameters 4 Fascicle VII.7 - Rec. T.522 This service has the parameter of "user information". Table 1-B/T.522 lists the D-U-ABORT service parameter. TABLE 1-B/T.522 D-U-ABORT service parameters w 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴쩡컴컴컴컴컴커 � � D-U-ABORT � D-U-ABORT � � � request � indication � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴캑 � Use information � U � C(=) � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴켸 Fascicle VII.7 - Rec. T.522 5 5.3.4D-CAPABILITIY service parameters This service has the following parameters: - application capabilities which consists of three sub-parameters: document application profile, non-basic document characteristics and non-basic structure characteristics; - user information. Table 1-C/T.522 lists the D-CAPABILITY service parameters. TABLE 1-C/T.522 D-CAPABILITY service parameters w 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴쩡컴컴컴컴컴컫컴컴컴컴컴컴쩡컴 컴컴컴컴컫 � 쿏-CAPABILITY쿏-CAPABILITY쿏-CAPABILITY쿏-CAPABILITY� � � request � indication � response � confirm � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴컵컴컴컴컴컴컴탠컴컴컴컴컴캑 � User information � U � C(=) � U � C(=) � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � � � � � Application capabilities � M � M(=) � M � M(=) � � ---------------------------------� � � � � � | Document application profile � M � M(=) � M � M(=) � � | � � � � � � | Non-basic document � U � C(=) � U � C(=) � � | characteristics � � � � � � | � � � � � � | Non-basic structure � U � C(=) � U � C(=) � � | characteristics � � � � � 쳐컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � � � � � User information � U � C(=) � U � C(=) � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴컨컴컴컴컴컴컴좔컴컴컴컴컴켸 5.3.5D-TRANSFER service parameters This D-TRANSFER service is used as defined in Recommendation T.432. 5.3.6D-CONTROL GIVE service parameters The D-CONTROL GIVE service surrenders all available tokens and has no parameter. 5.3.7D-TOKEN PLEASE service parameters 6 Fascicle VII.7 - Rec. T.522 The D-TOKEN PLEASE service is used to request all available tokens and has no parameter. 5.3.8D-U-EXCEPTION-REPORT service parameters This is left for further study. 5.3.9D-P-EXCEPTION-REPORT service parameters This is used as defined in Recommendation T.432. Fascicle VII.7 - Rec. T.522 7