home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Standards
/
CD2.mdf
/
ccitt
/
1992
/
t
/
t431.asc
< prev
next >
Wrap
Text File
|
1991-12-31
|
44KB
|
2,057 lines
Recommendation T.431
DOCUMENT TRANSFER AND MANIPULATION (DTAM) - SERVICES AND PROTOCOLS -
INTRODUCTION AND GENERAL PRINCIPLES
CONTENTS
0 Introduction
1 Scope and field of application
2 References
3 Definitions
4 Abbreviations
5 DTAM for telematic applications - General concepts
5.1 The approach to the integrated telematic applications
5.2 General communication functions
5.3 Communication support functions
5.4 Telematic protocol architecture (TPA) model
6 Overview of Recommendations T.431 to T.433
6.1 Recommendation T.431 - Introduction and general principles
6.2 Recommendation T.432 - DTAM service definition
6.3 Recommendation T.433 - DTAM protocol specification
7 Application rules for communication application profiles
7.1 General principle
7.2 Service class
7.3 Functional units
7.4 Communication support functions
7.5 Use of communication application profile
8 Service classes, functional units and communication support functions
8.1 Service classes
8.2 Functional units
8.3 Communication support functions
0 Introduction
Recommendation T.431 is one of a set of T.400 Series Recommendations to facilitate the interconnection of
telematic systems and terminals. It is related to other CCITT Recommendations in the set as defined by the Reference model
for open systems interconnection (X.200). The Reference model subdivides the area of standardization for interconnection into
a series of layers of specification, each of manageable size.
The T.430 Series of Recommendations define a document transfer and manipulation (DTAM) service and specify
a DTAM protocol available within the application layer of the reference model. The DTAM defined in this series of
Recommendations is one of the application service elements (ASE), which is specifically designed for document handling. It is
concerned with identifiable bodies of information which can be treated as documents, and which may be stored within open
systems or accessed, transferred and manipulated between application processes.
Recommendations T.431, T.432 and T.433 define general principles and application rules, basic DTAM service, and
protocol, respectively. They provide sufficient facilities to support DTAM and establish a framework for DTAM management.
Fascicle VII.7 - Rec. T.431 1
1 Scope and field of application
This Recommendation defines in an abstract way application rules of the DTAM service. Applications defined using
this series of Recommendations are specified in terms of service classes. A service class consists of a combination of
functional units and communication support functions. The combination of functional units and communication support
functions are:
1) Functional units provided by DTAM:
- association use control unit (kernel);
- capability unit;
- document transfer unit;
- document unconfirmed manipulation unit;
- document confirmed manipulation unit;
- typed data transfer unit;
- remote document management unit (see Note);
- remote document access unit (see Note);
- token control unit;
- reliable transfer management unit;
- exception report unit.
Note - The use of these functional units is left for further study.
2) Communication support functions:
- association control service element (ACSE) and presentation layer service;
- reliable transfer service element (RTSE) (see Note);
2 Fascicle VII.7 - Rec. T.431
- remote operation service element (ROSE) (see Note);
- session service (Recommendation X.215) according to the rule of Recommenda- tion T.62 bis;
- message handling system service element (STM-SE) (see Note).
Note - The use of these communication support functions is left for further study.
2 References
- Rec. T.62 bis: Control procedures for Teletex and Group 4 facsimile service based on
Recommendations X.215/X.225.
- Rec. T.400: Introduction to document architecture, transfer and manipulation.
- Rec. T.411: Open document architecture (ODA) and interchange format - Introduction and general
principles.
- Rec. T.412: Open document architecture (ODA) and interchange format - Document structures.
- Rec. T.414: Open document architecture (ODA) and interchange format - Document profile.
- Rec. T.415: Open document architecture (ODA) and interchange format - Open document interchange
format (ODIF).
- Rec. T.416: Open document architecture (ODA) and interchange format - Character content architectures.
- Rec. T.417: Open document architecture (ODA) and interchange format - Raster graphics content
architectures.
Fascicle VII.7 - Rec. T.431 3
- Rec. T.418: Open document architecture (ODA) and interchange format - Geometric graphics content
architectures.
- Rec. T.432: Document transfer and manipulation (DTAM) - Services and protocols - Service definition.
- Rec. T.433: Document transfer and manipulation (DTAM) - Services and protocols - Protocol
specification.
- Rec. X.200: Reference model of open systems interconnection for CCITT applications.
- Rec. X.208: Specification of abstract syntax notation one (ASN.1).
- Rec. X.209: Specification of basic encoding rules for abstract syntax notation one (ASN.1).
- Rec. X.210: Open systems interconnection (OSI) layer service definition convention.
- Rec. X.215: Session service definition for open systems interconnection for CCITT applications.
- Rec. X.216: Presentation service definition for open systems interconnection for CCITT applications.
- Rec. X.217: Association control service definition for open systems interconnection for CCITT applications.
- Rec. X.218: Reliable transfer: Model and service definition.
- Rec. X.219: Remote operations: Model, notation and service definition.
- Rec. X.225: Session protocol specification for open systems interconnection for CCITT applications.
- Rec. X.227: Association control protocol specification for open systems interconnection for CCITT
applications.
- Rec. X.400: Message handling systems: System and service overview.
3 Definitions
Unless explicitly indicated, all terms apply to the view of a system presented for the purpose of open systems
interconnection. This implies that the terms relate to a DTAM rather than to any real documents in local system.
The definitions are grouped into major categories, and ordered alphabetically within each category.
For the purpose of T.430 Series Recommendations, the following definitions apply:
3.1 DTAM service and protocol definitions
The following definitions are applied to Recommendations T.431 to T.433, in addition to the definitions defined in
other T.400 Series Recommendations:
4 Fascicle VII.7 - Rec. T.431
3.1.1 document bulk transfer
Bulk transmission of a document as a whole.
3.1.2 document bulk transfer and manipulation
An arbitrary combination of document bulk transfer and document manipulation.
3.1.3 document manipulation
Creation, deletion or modification of one or more constituents or substructures of a document.
3.1.4 DTAM user
That portion of the application entity which conceptually invokes the DTAM service.
Fascicle VII.7 - Rec. T.431 5
3.1.5 remote document access
Document selection and access rights via communication.
3.1.6 remote document management
Document creation or deletion via communication.
3.1.7 service element
A unit of standardization specifying a complete group of functions.
3.1.8 service primitive
The smallest defined interaction between the user and the provider of a communication service.
3.2 Reference model definitions
T.430 Series Recommendations are based on the concept developed in Recommendation X.200 and make use of
the following terms defined in it:
a) application-entity;
b) application-process;
c) application service element;
d) (N)-connection;
e) open system;
f) (N)-protocol;
g) (N)-protocol-control-information;
h) (N)-protocol-data-unit;
6 Fascicle VII.7 - Rec. T.431
i) (N)-service;
j) (N)-service-access-point;
k) (N)-service-access-point-address;
l) (N)-service-data-unit;
m) (N)-user-data;
n) user element.
3.3 Service convention definitions
T.430 Series Recommendations make use of the following terms defined in Recommendation X.210 as they apply
to the DTAM service:
a) confirm;
b) indication;
c) primitive;
d) request;
e) response;
f) service provider;
g) service user.
4 Abbreviations
Abbreviations defined in other Recommendations of T.400 Series apply also to this Recommendation. T.430 Series
Recommendations also use the following abbreviations:
ACSE association control service element
APDU application protocol data unit
Fascicle VII.7 - Rec. T.431 7
ASE application service element
DB document bulk transfer class
DM document manipulation class
DBM document bulk transfer and manipulation class
OSI open systems interconnection
PSAP presentation service access point
RTSE reliable transfer service element
ROSE remote operation service element
MHS-SE message handling system service element
TPA telematic protocol architecture
M mandatory
O optional
* At least one selection
- Not permitted
5 DTAM for telematic application - General concepts
5.1 The approach to the integrated telematic application
Recommendations T.400 Series specify the integrated approach for the telematic application by defining the
document transfer and manipulation (DTAM) which is the common communication function for telematic services located in
the OSI application layer.
DTAM provides document handling facilities in order to realize document bulk transfer, document manipulation,
document access and document management for various telematic applications such as G4 facsimile, mixed mode,
processable mode Videotex and so on.
5.2 General communication functions
DTAM provides the following general communication functions.
8 Fascicle VII.7 - Rec. T.431
5.2.1 Document bulk transfer
The communication function is subdivided into two functionalities. One is direct document transfer, the other is
indirect document bulk transfer as follows:
1) Direct document bulk transfer
In the direct document bulk transfer applications, a document generated at one system is transmitted to
another system such as Group 4 facsimile and mixed mode communications. In order to provide for efficient
general document transfer, CCITT defines a standard document architecture as the T.410 Series of
Recommendations.
Note - Direct transfer using IPM function is left for further study.
2) Indirect document bulk transfer
Indirect transfer using MHS X.400 Series of Recommendations is described in Annex E to Recommendation
T.411.
5.2.2 Remote document manipulations
An operation can be applied to one or more constituents or a bus-structure of document and/or the application
defined structures such as the operational structure. Operations applying to more than one constituent or sub-structure are
performed by applying the operation to each of the constituents or the sub-structures. The operations used by the application
have to obey certain rules. Detail specification of the operational structure is described in Recommendation T.441.
5.2.2.1Operations for manipulations
1) Create operation
The create operation effects the addition of a constituent to the document or to the application defined
structure.
Fascicle VII.7 - Rec. T.431 9
The create operation may carry the constituents, including the values applicable to the created constituent.
If attributes are not set by the operation, they are set to their default values (if defined) or remain undefined
otherwise. The relationship attributes of the superior are not implicitly modified by the create operation.
2) Delete operation
The delete operation provokes the deletion of the identified constituent and all subordinates. The
relationship attributes of the superior constituents are not implicitly modified by the delete operation.
Note - If content portions are deleted as subordinates of wither layout or logical structure, it is the
responsibility of the application to ensure that they also deleted for the complementary structure.
3) Modify operation
For the identified constituent, the modify operation assigns new values to the mentioned attributes.
Attributes not mentioned in a modify operation remain unchanged. Identification attributes are used in a
modify operation to identify the concerned constituent. They are set at the time of the creation of the object
or content portion and remain unchanged by modify operations. Other invariable attributes must not occur in
this operation.
Whenever applying one of the concerned operations, it is the responsibility of the application to ensure
consistency of the document.
4) Call operation
The call operation is used to read an object of the operational structure which contains a sequence of
DTAM protocol data unit which is applicable to the existing document.
5) Rebuild operation
The rebuild operation is for further study.
5.2.3 Remote document access
For further study.
5.2.4 Remote document management
For further study.
5.3 Communication support functions
DTAM makes use of the following services as a communication support function to exchange protocol elements
between telematic DTAM protocol machines (DTAM-PM):
a) the service of session layer defined in Recommendation X.215 according to the rule of
Recommendation T.62 bis.
b) the service of ACSE (association control service element) and the service of presentation layer.
Note - The use of RTSE (reliable transfer service element), ROSE (remote operation service element) and
10 Fascicle VII.7 - Rec. T.431
MHS-SE (message handling system service element) is left for further study.
5.4 Telematic protocol architecture (TPA) model
The DTAM operates between two telematic DTAM protocol machines (DTAM-PMs) in the application layer of OSI
model. Protocol elements are exchanged between DTAM-PMs, using the service of session layer as defined in
Recommendation X.215, or the services of ACSE (association control service element) and presentation layer services as
defined in Recommendation X.216. Telematic protocol architecture (TPA) model is shown in Figure 1/T.431. The application
layer protocol architecture illustrated in this figure is composed of ACSE, DTAM application service element, and DTAM user
elements.
Inclusion of MHS, RST and ROS elements in TPA is left for further study.
Fascicle VII.7 - Rec. T.431 11
Note - In some applications, APDUs defined in DTAM are directly mapped to session service defined in
Recommendation X.215.
FIGURE 1/T.431
A basic telematic protocol architecture (TPA) model
12 Fascicle VII.7 - Rec. T.431
6 Overview of Recommendations T.431 to T.433
6.1 Recommendation T.431 - Introduction and general principles
Recommendation T.431 provides information about T.430 Series of Recommendations as a whole by way of an
introductory description of the DTAM service and protocol, an overview of each of the Recommendations and a description of
their interdependencies. References necessary for all T.430 Series of Recommendations are given, and terms used
throughout all T.430 Series of Recommendations are defined. Conformance to T.430 Series of Recommendations is specified
and rules for defining communication application profiles are given.
6.2 Recommendation T.432 - DTAM service definition
Recommendation T.432 defines in an abstract way the services provided by an application- service-element, the
document transfer and manipulation service element (DTAM) to support applications in a distributed telematic systems
environment.
6.3 Recommendation T.433 - DTAM protocol specification
Recommendation T.433 specifies the protocol for the services provided by an application- service-element, the
document transfer and manipulation service element (DTAM) to support applications in a distributed telematic systems
environment.
7 Application rules for communication application profiles
Specific communication application profiles may be defined using this T.430 Series of Recommendations according
to the rules defined in this section. Definition procedure of a communication application profile is summarized in
Figure A═1/T.431.
7.1 General principle
Tables 1/T.431 and 2/T.431 define permissible combinations of a service class, communication support functions
and functional units that may be used to define a communication application profile during the lifetime of association.
A communication application profile must specify:
1) a service class;
2) functional units;
3) communication support functions,
that are conforming to this Recommendation.
Fascicle VII.7 - Rec. T.431 13
TABLE 1/T.431
Services associated with functional units
w
┌─────────────────────┬────────────────────────────────────┬────────────────────┬────────
─┐
│ │ │ Service classes │
│
│ Functional unit │ DTAM service
├──────┬──────┬──────┤Reference│
│ │ │ DB │ DM │ DBM │
│
├───┬─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U1 │Association use │Association use start │ M │ M │ M │
│
│ │control unit ├────────────────────────────────────┼──────┼──────┼──────┤
│
│ │ │Association use termination │ M │ M │ M │
│
│ │ ├────────────────────────────────────┼──────┼──────┼──────┤
│
│ │ │Association use forced │ │ │ │
│
│ │ │termination │ M │ M │ M │
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U2 │Capability unit │Capability │ O │ O │ O │
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U3 │Document bulk │Document bulk transfer │ M │ - │ M │
│
│ │transfer unit │ │ │ │ │
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U4 │Document │Document unconfirmed manipulation │ │ │ │
│
│ │manipulation unit│CREATE, DELETE, MODIFY, CALL, │ │ │ │
│
│ │(unconfirmed) │Others FS │ - │ M │ M │
│
├───┼─────────────────┼────────────────────────────────────┼──────┴──────┴──────┼────────
─┤
│U5 │Document │Document confirmed manipulation │ │
│
│ │manipulation unit│CREATE, DELETE, MODIFY, CALL, │ FS │
│
│ │(confirmed) │Others FS │ │
│
├───┼─────────────────┼────────────────────────────────────┼──────┬──────┬──────┼────────
─┤
│U6 │Typed data │Typed data transfer │ - │ O │ O │
│
│ │transmission unit│ │ │ │ │
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U7 │Token control │Token control │ O │ O │ O │
│
│ │unit │ │ │ │ │
14 Fascicle VII.7 - Rec. T.431
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U8 │Exception report │Exception reporting │ O │ - │ O │
│
│ │unit │ │ │ │ │
│
├───┼─────────────────┼────────────────────────────────────┼──────┼──────┼──────┼────────
─┤
│U9 │Reliable transfer│Activity control and │ │ │ │
│
│ │support unit │synchronization/resynchronization │ O │ - │ O │
│
│ │ │control │ │ │ │
│
├───┼─────────────────┼────────────────────────────────────┼──────┴──────┴──────┼────────
─┤
│U10│Remote document │FS │ FS │
│
│ │management unit │ │ │
│
├───┼─────────────────┼────────────────────────────────────┼────────────────────┼────────
─┤
│U11│Remote document │FS │ FS │
│
│ │access unit │ │ │
│
└───┴─────────────────┴────────────────────────────────────┴────────────────────┴────────
─┘
FS Further study
Service class abbreviations:
DB Document bulk transfer class
DM Document manipulation class
DBM Document bulk transfer and manipulation class
The following abbreviations are applied within the service class columns:
M Mandatory
O Optional
* At least one functional unit
- Not permitted
Fascicle VII.7 - Rec. T.431 15
TABLE 2/T.431
Summary of service classes
w
┌───────────────────────┬─────────────────────────────────────────────────────
────────────┐
│ Service classes │ DTAM communication support functions
│
├───────────────────────┼─────┬──────────────────────────────────────────────────────────
─┤
│ │ DB0 │ Direct mapping to session service
│
│
├─────┼───────────────────────────────────────────────────────────┤
│ Document bulk │ DB1 │ ACSE and presentation service
│
│ transfer (direct)
├─────┼───────────────────────────────────────────────────────────┤
│ │ DB2 │ ACSE and RTSE and presentation service (Note)
│
├───────────────────────┼─────┼──────────────────────────────────────────────────────────
─┤
│ │ DM1 │ ACSE and presentation service
│
│
├─────┼───────────────────────────────────────────────────────────┤
│ Document manipulation│ │
│
│
├─────┼───────────────────────────────────────────────────────────┤
│ │ │
│
├───────────────────────┼─────┼──────────────────────────────────────────────────────────
─┤
│ │ DBM1│ ACSE and presentation service (Note)
│
│ Document bulk
├─────┼───────────────────────────────────────────────────────────┤
│ transfer and │ DBM2│ ACSE and RTSE and presentation service (Note)
│
│ manipulation
├─────┼───────────────────────────────────────────────────────────┤
│ │ │
│
├───────────────────────┼─────┼──────────────────────────────────────────────────────────
─┤
│ Document bulk │ IDB1│ MHS-SE (Note)
│
│ transfer (Note)
├─────┼───────────────────────────────────────────────────────────┤
│ │ │
│
├───────────────────────┼─────┼──────────────────────────────────────────────────────────
─┤
│ Remote document │ RDA │
│
│ access (Note)
├─────┼───────────────────────────────────────────────────────────┤
│ │ │
│
├───────────────────────┼─────┼──────────────────────────────────────────────────────────
─┤
16 Fascicle VII.7 - Rec. T.431
│ Remote document │ RDM │
│
│ management (Note)
├─────┼───────────────────────────────────────────────────────────┤
│ │ │
│
└───────────────────────┴─────┴──────────────────────────────────────────────────────────
─┘
DB, DM, DBM, IDB, RDA and RDM are used to classify DTAM protocol architecture depending
on the combination of communication support functions.
Note - These service classes are left for further study.
7.2 Service class
Recommendation T.431 defines three service classes (Note), that are general
communication functions provided by DTAM:
1) document bulk transfer (direct);
2) document manipulation;
3) document bulk transfer and manipulation.
Recommendations T.432 and T.433 define all DTAM services and procedures as
application protocol that may be used in defining each service class. The application
profile must specify the required service class depending on the DTAM application profile
requirement.
Note - There may be other service classes such as document bulk transfer (indirect),
remote document access and remote document management. These service classes are left for
further study.
7.3 Functional units
Table 1/T.431 defines combinations of a service class and functional units.
Functional units are used to simplify the procedure as well as the application protocol.
Recommendations T.432 and T.433 define DTAM service and protocol that may be used in an
application profile. This section defines the rules for using functional units within an
application profile, as follows:
Fascicle VII.7 - Rec. T.431 17
1) The communication application profile must specify all functional units
conforming to a service class.
2) The communication application profile must specify all DTAM service primitives
that are associated with functional units.
3) The communication application profile must specify all parameter sets that are
associated with a DTAM service; these service primitives must include
parameters that are classified as mandatory in the Recommendation T.432.
4) The communication application profile may specify or exclude the use of any
DTAM service primitives that is classified as a user option in
Recommendation T.432.
5) The communication application profile may specify as mandatory the use of any
DTAM service primitives that is classified as a user option in Recommendation
T.432.
6) The communication application profile must specify value and default value of
DTAM protocol data handled by a functional unit.
7.4 Communication support functions
Table 2/T.431 defines permissible combinations of a service class and communication
support functions. Recommendation T.433 defines DTAM protocol in conjunction with the
association control service element (ACSE) and presentation service or session service
(X.215) according to the rule of Recommendation T.62 bis. This section defines the rules
for using communication support functions within an application profile, as follows:
- the application profile must specify all communication support functions
conforming to a service class.
7.5 Use of communication application profile
A single communication application profile is used for one association. The use of
more than one communication application profile during the lifetime of association is for
further study.
8 Service classes, functional units and communication support functions
Functional units and service classes are logical groupings of related DTAM services
defined in Recommendation T.432.
8.1 Service classes
Recommendations T.432 and T.433 define all DTAM services and procedures as
application protocol that may be used in defining each service class. Which functional
units are mandatory and which are optional in each service class; document bulk transfer,
document manipulation, and document transfer and manipulation are shown in Table 1/T.431.
8.1.1Document bulk transfer class
In terminal-to-terminal communications, there exist bulk document transfer
application transmitting documents as a whole, such as G4 facsimile and mixed-mode
communications. In this document bulk transfer applications, a document generated at one
system (terminal) is transmitted to another system (terminal).
The document bulk transfer class consists of:
a) association use control functional unit;
b) optionally, capability functional unit;
c) document bulk transfer functional unit;
18 Fascicle VII.7 - Rec. T.431
d) optionally, exception report functional unit;
e) optionally, token control functional unit;
f) optionally, reliable transfer support functional unit.
Fascicle VII.7 - Rec. T.431 19
8.1.2 Document manipulation class
In telematic document data base applications, parts of a document may be transferred
to generate a whole document sequentially, concatenating parts stored in different
resources. The only document manipulation class can be applied to this application.
The document manipulation class consists of:
a) association use control functional unit;
b) optionally, capability functional unit;
c) document manipulation functional unit (unconfirmed);
d) optionally, token control functional unit;
e) optionally, typed data transmission functional unit.
8.1.3Document bulk transfer and manipulation class
In addition to document transfer applications, there exist conversational
applications transmitting documents two-way interactively. This service class is achieved
by an arbitrary combination of document bulk transfer and document manipulation. For
example, in terminal-to-terminal communications, conversational applications include
interactive telematic services with handwriting and point, and interactive remote editing
of previously transmitted documents. In host access applications, special characteristics
of document architecture include the use of soft copy media. These enable partial
document manipulations such as modification or deletion of portions of the structured
document received from the host. In this application, document structure of a previously
transmitted document may be manipulated.
Note - In host-to-terminal communications, the structured document is transferred as
a body part for submission, delivery, filing and retrieval. Applicability to other host-
to-terminal communications, such as MHS, document filing and retrieval service, is left
for further study.
The document bulk transfer and manipulation class consists of:
a) association use control functional unit;
b) optionally, capability functional unit;
c) document bulk transfer functional unit;
d) exception report functional unit;
e) optionally, token control functional unit;
f) optionally, reliable transfer support functional unit;
g) optionally, typed data transmission functional unit.
8.1.4Remote document access class
For further study.
20 Fascicle VII.7 - Rec. T.431
8.1.5Remote document management class
For further study.
8.2 Functional units
8.2.1Association use control functional unit (kernel)
The DTAM provides the trigger for the use of the association provided in ACSE, and
controls association use during communication. Association use control unit supports
basic DTAM services for unique discrimination of both AEs, selection of functional units,
establishment, termination and abort of association use.
8.2.2Capability functional units
The DTAM capability functional unit provides the means for invocation or negotiation
of application and communication characteristics during an association being in effect up
to the next subsequent DTAM capability invocation.
Fascicle VII.7 - Rec. T.431 21
8.2.3Data transmission functional units
The DTAM provides document transfer methods, such as document bulk transfer,
document manipulation and typed data transmission. Data transmission unit consists of the
following three units:
a) Document bulk transfer functional unit
The DTAM has a function to transmit the document in bulk to the other DTAM
user under the communication environment negotiated by D-INITIATE service and
additionally by D-CAPABILITY service. The documents represented by ODIF (open
document interchange format) is transmitted using bulk document transfer unit.
b) Document manipulation functional unit (confirmed or unconfirmed)
In addition to the above bulk transfer, DTAM provides a function to partially
modify a document by generating, revising or deleting structures of an
existing document. The DTAM user uses this document manipulation unit to
manipulate structures in an existing document.
c) Typed data transmission functional unit
In host-access applications, data sent to the host by the user are
fundamentally unstructured retrieval commands and interrupts such as
transmission stop requests. The DTAM has a function to pass such data directly
on to the DTAM user as typed data. Typed data transmission unit transmits
commands for document filing, document retrieval and interrupt without
subjecting to token control.
8.2.4Session management functional units
The DTAM has control functions for conversational control provided by the session
layer.
a) Token control functional unit
Transmission rights required for document transfer and document manipulations
are controlled with token control unit.
b) Reliable transfer support functional unit
DTAM provides the activity control, synchronization/resynchronization control
unit, error recovery control unit.
8.2.5Exception report functional unit
DTAM provides the exception reporting service for exceptional condition occurred in
DTAM communication environment.
8.2.6Remote document access functional unit
For further study.
8.2.7Remote document management functional unit
For further study.
8.2.8Other functional units
The DTAM may use remote operation service (Recommendation X.219), reliable transfer
service (Recommendation X.218) and MHS (X.400 Series of Recommendations). They are left
for further study.
8.3 Communication support functions
This section defines permissible combinations of a service class and communication
support functions. Valid combinations of service classes and communication support
22 Fascicle VII.7 - Rec. T.431
functions are summarized in Table 2/T.431. Recommendations T.432 and T.433 define DTAM
services and procedures that specify two communication support functions: the association
control service element (ACSE) service and the presentation service (Recommendation
X.216) or session service (Recommendation X.215) according to the rule of
Recommendation T.62 bis. Other communication support functions such as MHS, RTS and ROS
element are left for further study.
Fascicle VII.7 - Rec. T.431 23
8.3.1Document bulk transfer class
a) Use of Recommendation T.62 bis (DB0)
Application protocol data units (APDU) defined in DTAM are directly mapped to
session service defined in Recommendation X.215 according to the rule of
Recommendation T.62 bis.
b) Use of ACSE and presentation layer service defined by X.200 (DB1)
Other telematic document bulk transfer service classes may be provided in
conjunction with the ACSE (Recommendation X.217) and the presentation service
(Recommen- dation X.216).
c) Use of ACSE, RTSE and presentation layer service defined by X.200 (DB2)
For further study.
8.3.2Document manipulation class
a) Use of ACSE and presentation layer service defined by X.200 (DM1)
The telematic document manipulation service classes may be provided in
conjunction with the ACSE (Recommendation X.217) and the presentation service
(Recommendation X.216).
8.3.3Document bulk transfer and manipulation class
a) Use of ACSE and presentation layer service defined by X.200 (DBM1)
Telematic document bulk transfer and manipulation service classes may be
provided in conjunction with the ACSE (Recommendation X.217) and the
presentation service (Recommendation X.216).
b) Use of ACSE, RTSE and presentation layer service defined by X.200 (DBM2)
For further study.
8.3.4Remote document access class (RDA)
For further study.
8.3.5Remote document management class (RDM)
For further study.
8.3.6Document bulk transfer class (indirect) (IDB1)
For further study.
24 Fascicle VII.7 - Rec. T.431
ANNEX A
(to Recommendation T.431)
This Annex summarizes the definition procedure of a communication application
profile. (See Figure A-1/T.431.)
FIGURE A-1/T.431
Defining procedure of communication application profile
Fascicle VII.7 - Rec. T.431 25